LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Ethernet Communication Problems

Solved!
Go to solution

Hello,

 

Please I need your advice. I am trying to control two different instruments, both using ethernet connection, from the same computer. Every instrument (one is use fieldpoint and the other one compact fieldpoint) is controlled from its own vi. When I tried to use differnt iak file (one for every instrument) they didn't work. Thus, I made a common iak file for both vis. It seemed that everyhting work properly at first, however with the time progress there were a lot of communication problems, like temperatures were lost (didn't measured etc.) Could you please have any idea why this happen? Finally, is it correct to control both instruments from the same computer or this is a risk situation?

 

Looking forward to hearing from you

0 Kudos
Message 1 of 4
(2,940 Views)

I think I found what causes the problem.

 

Thanks anyway

0 Kudos
Message 2 of 4
(2,923 Views)

Could you please post how you found what was the problem and how you solved it? It will be useful for others who will look for such problems. Remember to close the thread by accepting solution.

 

Thanks,

Mathan

Message 3 of 4
(2,913 Views)
Solution
Accepted by topic author LW42

Hello Mathan,

 

I am not sure if it is worth while since it has nothing to do with complicated communication data but with a mistake that I have done. However, I am sharing my experience.

During my effort to make the two vis running simultaneously from the same computer, by a mistake I had created two identical iak files (every of which was the join of the two preexist iak files) but with different names e.g “Device 1 and 2” and “Device 1 plus 2”; I am referring to the name that appears in the View Configuration tab of Fieldpoint Device Selection. Thus, some of my Fieldpoint  express vis was calling  the “Device 1 and 2” iak and some others calling the “Device 1 plus 2” iak. Although both iak were identical, the Fieldpoint express vis that were calling the wrong iak name didn’t work properly making the corresponding vi to operate faulty or in other cases stop.

 

Best Regards

0 Kudos
Message 4 of 4
(2,894 Views)