06-13-2017 10:53 AM
Yes. A different address has been assigned to each pump. My test scenario only has 2 pumps. The command functions, with the pump multi drop address in it, do work for a specific pump, and not the other. I thought if I could differentiate the reply message from a specific pump it would clear out the clutter.
06-13-2017 11:47 AM
You will have to parse the returned strings, using the address as your differentiation. You had me confused through much of this thread with the "232 bus", which really is one port, one device, except in, as a previous post said, a "kludge". If you use an array to store the various parameters that might be returned by a device, indexed on device number, then you will have the various devices' info available all sorted out. My first cut would use an "Action Engine" (a.k.a LV2 global, Uninitialized Shift Register, etc.).
06-13-2017 12:22 PM
Putnam is correct. This entire thread is misnamed. 232 <> 485.
Let's fix the name of this thread.