Ethernet connection with LABView is insufficient

[Михаил Бабаев]

Hi everybody

We have a problem connecting with device driver for moving platform via Ethernet(UDP). The main problem in device connection in NI MAX. When we were trying connect device with LABView using NI MAX we got an error: VISA: (Hex 0xBFFF0011) Insufficient location information or the device or resource is not present in the system. Although when we ping needed address in CMD - everything work. We have used the common program for checking response from device in LABView (test.vi) and we have gotten errors: the first - "Error -56 Timeout When Communicating Between LabVIEW and Network Devices" and Error 66 like that. 

Our device driver should work in the following way, so we send commands via UDP as bytes sequance to our motion device and it will move. Depending on bytes sequance the motion device must execute different commands. 

We already shut down Windows firewall and open ports, still no effect.

 

[crossrulz]

I don't think VISA works with UDP.  It will work with TCP.  So you are going to have to use the UDP functions to communicate with this device.

[Rolf Kalbermatter]

crossrulz is very correct. VISA only supports TCP/IP and that in two flavors. The first with the ::INSTR postfix is according to the VXI-11 standard that provides a resource discovery service (ala Bonjour) on the device that allows NI Max to query for connected devices and query their specific settings. The second variant uses the ::SOCKET postfix and is raw TCP/IP communication. The resource specifier needs in that case also a port number in addition to the IPv4 device address.

UDP communication in LabVIEW is only possible with the UDP native nodes in LabVIEW. No NI-MAX will be getting harmed nor in any other way getting involved in this!

[Михаил Бабаев]

On 8/7/2023 at 4:59 PM, Rolf Kalbermatter said:

crossrulz is very correct. VISA only supports TCP/IP and that in two flavors. The first with the ::INSTR postfix is according to the VXI-11 standard that provides a resource discovery service (ala Bonjour) on the device that allows NI Max to query for connected devices and query their specific settings. The second variant uses the ::SOCKET postfix and is raw TCP/IP communication. The resource specifier needs in that case also a port number in addition to the IPv4 device address.

UDP communication in LabVIEW is only possible with the UDP native nodes in LabVIEW. No NI-MAX will be getting harmed nor in any other way getting involved in this!

So we try to use UDP functions. There are only open, multicast open, write, read, close. We are sending data through UDP Write to device IP. First problem, we are not understanding how we need to built a sequnce in UDP protocol,how it must look like? We need to send 0 0 0 0 2 0 in one command, each number is 1 byte. Second we do not understend how to recive information  from device, because UDP Read dose give Error 56/66. What should we do to force UDP Read to actualy read the device. We tried to open one port, then opened several, nothing seems to work, device stil answering to ping command in cmd but not in Labview. Is there any solutions?

[drjdpowell]

Maybe if you posted what device you are trying to talk to, and perhaps pointed to the manual, you might get better help.