09-25-2006 07:34 PM
09-26-2006 04:40 PM
09-27-2006 03:29 PM
Hi Andy,
Thanks for your reply.
I have trimmed the LabVIEW program down as much as possible and deleting all hardware-related parts. The attached Datasocket Troubleshooting.vi reproduces the oberved cross-talk between some of the data socket channels. The original program operates an automated vacuum system switching pneumatic valves, reading pressure transducers, etc. The controls on the user interface represent some of the valves of the system, TRUE (green) corresponding to the Valve OPEN state, and FALSE (red) to the Valve CLOSED state. I could reproduce the error by clicking on the valves in the following sequences
Cross-talk between Valve 1 and Valve 10: Left click on 10>10>1>1
Cross-talk between Valve 1 and Valve 11: Left click on 11>11>1>1
Cross-talk between Valve 1 and Valve 12: Left click on 12>12>1>1
Note that the hardware is not affected by this cross-talk, i.e., the physical valve 10 (or 11, 12, respectively) does not open/close when valve 1 is actuated. But it gets very confusing (and potentially dangerous) when the user interface shows a different status of the vacuum system than the hardware.
No cross-talking has been observed between any of the other controls in this example. However, in a similar program, I have also observed cross-talk between channels 2 and 2x and channels 3 and 3x (x=0-9).
BTW, I have LabVIEW version 7.
I am looking forward to hearing from you.
Peter
10-04-2006 08:27 AM - edited 10-04-2006 08:27 AM
Message Edited by Andy F. on 10-04-2006 08:28 AM
10-04-2006 10:15 AM
Sorry. I thought these files were included. Here is the complete zip file. Please let me know, if it takes longer to troubleshoot this. Thanks for your help.
Peter
10-05-2006 04:47 PM
10-05-2006 05:11 PM
Thank you, Andy, for looking into this. I tested the vi that you sent me, and I also have the impression that your changes fixed the problem. I will let you know in case that the issue occurs again. Thank you very much for your help.
Peter