06-15-2007 10:43 AM
06-15-2007 10:49 AM
It looks like you are trying to use a one lane road for 2 cars. The serial data can't be tagged for each unit on the same port, so you are sending both commands intermixed to both the units. The responses are likely mixed as well.
Imagine using a water tube and sending blue and red dye down it... once the colors mix in the tube, you can't tell what color your supposed to recieve at the other end. You need separate tubes... or in your case, com ports, for parallel operation.
06-15-2007 10:54 AM
06-15-2007 10:56 AM

Using the Abort button to stop your VI is like using a tree to stop your car. It works, but there may be consequences.06-15-2007 10:59 AM
06-15-2007 11:08 AM
I will check what Ed tells me. But I can't do something like :
Query1 (com5, address2... writing operation 1 ms) --> Query2 (com5, address3... writing operation 1 ms) --> Waiting 80ms because of my devices --> Read1 (com5, address2.... reading operation 1ms) ---> Read2 (com5, address3... reading operation 1ms)
I can't just specified the address on which device I want to read and then the others. Or I stuck to read all the address on the same port at same time?
06-15-2007 11:09 AM
06-15-2007 11:15 AM
I'm a newby in that kind of things, but if a specified an address for a reading operation (if it's possible) i will know what device has responded me. If I cannot do that kind of things with RS485, can I do it with an another communication type ?
Many thanks
06-15-2007 11:23 AM
06-15-2007 02:04 PM
@Doyon wrote:
I'm a newby in that kind of things, but if a specified an address for a reading operation (if it's possible) i will know what device has responded me. If I cannot do that kind of things with RS485, can I do it with an another communication type ?
Many thanks
TCP and USB both support multiple connections. A lot of test equipment now has either TCP/IP and/or USB control.
Ed

Using the Abort button to stop your VI is like using a tree to stop your car. It works, but there may be consequences.