Please Note This forum exists for community support for the Mango product family and the Radix IoT Platform. Although Radix IoT employees participate in this forum from time to time, there is no guarantee of a response to anything posted here, nor can Radix IoT, LLC guarantee the accuracy of any information expressed or conveyed. Specific project questions from customers with active support contracts are asked to send requests to

Radix IoT Website Mango 3 Documentation Website Mango 4 Documentation Website

How does Use multiple write commands only option really work?

  • I've read the help page and several forum posts describing things that the "Use multiple write commands only" option has helped fix, but what I am still unsure of, is how it actually works.

    When we chose that option while troubleshooting why commands being issued to a pump were being overwritten we didn't see any differences in the results. That may be because it just wasn't the fix, or we are trying to send the commands in a way that is incompatible with the multiple write option.

    For our setup we have a scripting data source that uses multiple .set commands in a row to turn a modbus water pump on and set several addresses as we need. Will checking the multiple commands box spool up a certain number of commands, or wait a few milliseconds for the various set commands to be issued and spit out the consecutive registers as one command to the pump?

    Or, would we have to change the way we set the register values in our scripting data source to better suit the multiple write commands option?


  • @cmusselm that setting may help depending on what you are doing. That setting will effectively send a short value to a register if it is 2 bytes according to the point locator's modbus data type. If it is > 2 bytes then no matter what it will send an array to the slave and likely will write > 1 register.