MCP4725 Odd Behavior - does not update with number directly

[xodballxod]

I’m using the e/MCP4725 library, and it works fine in 2 scenarios, and doesn’t work in another (direct number wire). Basically, can work with deprecated triangle wave, but not the updated triangle wave. I couldn’t get it to update with any kind of number wired directly, even when changing the number to trigger the pulse-on-change inside the mcp4725 node.

1. Works using the example node with the library, with the deprecated triangle-wave node, directly wired to the mcp4725

2. Works using updated triangle-wave node only when going through a select node.
   

   

3. Does not work when updated triangle wave is wired directly?
   

   

I can’t get the MCP4725 to output the number I want, for example, through map. The thing doesn’t update through MAP node, either.

Doesn’t not work through a buffer node, either.

Can anybody help understand this behavior? @evgenykochetkov
mcp4725.xodball (21.6 KB)

[xodballxod]

SOLVED: Have to slow down the other I2C devices…

Having some trouble with I2C MCP4725

MCP4725 nodes update when VAL changes. But when both are at A1, both use the bus at the same time and it is blocked, so the defer delays one node. Now A0 and A2 readings are in loop, it could update every a set time. Can also set a time to A1, instead of a loop, you can use clock or throttle node.

But, really, the library should have pulled out the UPD node (send), instead of updating on change.

mcp4725.xodball (18.8 KB)

[xodballxod]

Seams like a potential safety issue with the i2c communication. The clocks can’t match, or one dominates the i2c bus. In my case, the ADS1115 appears to dominate. If you choose different clock speeds, then the speeds have to be out of phase… and never match on moment to UPD, I’m not sure the best way to get that…

One option is to use prime numbers, but I’m not sure if they could overlap ever…

A Flip-Flop could be used for just 2 i2c devices, assuming you want them sampling at the same rate

But, what happens if you have a lot of i2c devices? Then, you need a new node that XOD doesn’t have in the the CORE, the Select-Pulse Node (but doesn’t work for this)

Select Variadic Out Pulse

For multi function projects that are menu driven could use a node with variadic output of the select, can make one with nth-input style, or one with select style, I’ve got a non-variadic version here, where VAL matches whatever IN (which could just be an integer), then the corresponding pulse pulses out. Would there be a way to make this variadic? [image] Another way to think about it. We would want the NONE to be to the left of the variadic output. [image]

But, that node method doesn’t work! Likely has something to do with the time to write and read-back from the I2C bus… I’m not sure, but not all methods work…

Now, if all the I2C devices want to be read as fast as possible, then you can make a daisy chain, but have to add the DONE pulse node out of the MCP4725, and place a defer. Using BUS instead of wires, naming convention can be “DEV#-out”, and the last I2C DEVICE wired back to the start.

I’m not sure if it would be possible for XOD to handle the I2C networking managing, automatically?