LabWindows/CVI Idea Exchange

Community Browser
About LabWindows/CVI Idea Exchange

Do you have a feature idea for how to improve LabWindows/CVI? Submit and vote on ideas now!
  1. Browse by label or search in the LabWindows/CVI Idea Exchange to see if your idea has previously been submitted. If your idea exists, be sure to vote for the idea by giving it kudos to indicate your approval!
  2. If your idea has not been submitted click New Idea to submit a product idea. You should submit a separate post for each idea. Watch as the community gives your idea kudos and adds their input.
  3. Give kudos to other ideas that you would like to see implemented!
  4. NI R&D will review ideas that have been submitted and update the status.

Note: the LabWindows/CVI Idea Exchange is not the appropriate forum to submit technical support questions.

The LabWindows/CVI R&D team is committed to reviewing every idea submitted via the LabWindows/CVI Idea Exchange. However, we cannot guarantee the implementation of any LabWindows/CVI Idea Exchange submission.

Top Kudoed Authors
User Kudos Count
1
1
cancel
Showing results for 
Search instead for 
Did you mean: 
Post an idea

+ Implement Modbus RTU master/TCP client protocol support in CVI

How about Ethernet/IP or EtherCAT support.  It exists in Labview.  It has been around for over a decade.

0 Kudos

Hi,

 

it's an old question, see here, but so far I have not heard about a practical solution. The quest is to find all instruments on a local LAN that are switched ON (and connected to the LAN, of course). Unfortunately, viFindRsrc does not work. Pinging all possible addresses seems not a viable solution due to the required time, either. So it's possible to detect all serial instruments, all instruments connected via GPIB, but until now there is no standalone solution (i.e.without involving NI-MAX) to detect instruments on a local LAN... Smiley Sad

 

Thanks,

Wolfgang