LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Monitor multiple devices on 232 bus

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. 

0 Kudos
Message 11 of 13
(578 Views)

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.).

Putnam
Certified LabVIEW Developer

Senior Test Engineer North Shore Technology, Inc.
Currently using LV 2012-LabVIEW 2018, RT8.5


LabVIEW Champion



0 Kudos
Message 12 of 13
(573 Views)

Putnam is correct.  This entire thread is misnamed.  232 <> 485.

 

Let's fix the name of this thread.

0 Kudos
Message 13 of 13
(565 Views)