# MCP4725 Odd Behavior - does not update with number directly

**URL:** <https://forum.xod.io/t/mcp4725-odd-behavior-does-not-update-with-number-directly/5393>\
**Category:** XOD Programming Questions\
**Created:** [August 14, 2021, 10:39am UTC](https://forum.xod.io/t/mcp4725-odd-behavior-does-not-update-with-number-directly/5393 "2021-08-14T10:39:24Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![xodballxod](https://avatars.discourse-cdn.com/v4/letter/x/f475e1/32.png) [@xodballxod](https://forum.xod.io/u/xodballxod)\
**Post date:** [August 14, 2021, 11:24am UTC](https://forum.xod.io/t/mcp4725-odd-behavior-does-not-update-with-number-directly/5393/2 "2021-08-14T11:24:12Z")

</div>

SOLVED: Have to slow down the other I2C devices…

> [@Having some trouble with I2C MCP4725](https://forum.xod.io/t/having-some-trouble-with-i2c-mcp4725/3944/7):
>
> 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.

 ![image](https://canada1.discourse-cdn.com/flex027/uploads/xod/original/2X/3/3c9db0a51daa3a5e055ebc88478bec5dd3e5dc34.png)

But, really, the library should have pulled out the UPD node (send), instead of updating on change.  
 ![image](https://canada1.discourse-cdn.com/flex027/uploads/xod/original/2X/7/77f131bd26ee0d80f0673d7cc60c29f5995434a1.png)

[mcp4725.xodball](https://forum.xod.io/uploads/short-url/kT9rNhBEL6DodFHgjwNzDGN8rvX.xodball) (18.8 KB)

---

_[View the full topic](https://forum.xod.io/t/mcp4725-odd-behavior-does-not-update-with-number-directly/5393)._