Labview Ethernet

[Dinah Lianes]

Mydevice is a volume pressure controller (VPC, e.g. Wille pump), and we try to link it to the PC end for instrument control and data monitoring, but it cannot be recognised by the PC end (the developed Labview driver), and neither on NI-MAX, not sure if there is anything additional to be installed or configured while using LABVIEW for such purpose ?

Perhaps to expand on what wiebe said, any Ethernet devices you have seen in MAX before are either NI ethernet devices such as a Compact DAQ, or they are regular test devices that use the LXI-11 communications standard, and in both cases where they show up automatically the network setup has to have them on a local subnet that it can find them via discovery.

Other Ethernet devices can of course be used but won't show up in MAX automatically... you have to either add them manually or address them directly from your program and not even put them in MAX. Starting with a ping is good, though I have run across the occasional instrument that won't respond to ping but will still connect otherwise. What you really need to get started is to know the IP address and port number of the device, and the communications protocol it uses (for instance, does it use Telnet, MODBUS, Ethernet/IP, HTTP, etc.).

Thank you, I actually tried Ping on the command box, but still not quite right, probably I should ask for the right IP address and Port number from the Device supplier ? or I can create a new one from my side ?

Hello, actually I also tried the diffrent ways as indicated from the NI webs, e.g. ping using 'cmd' , but it seems probably I should ask for the right IP address and Port number from the Device supplier ?

And while many instruments come with a default network setting, quite often to use DHCP in which case the device will either receive a network address from your local DHCP server and in lack of that an address from the auto address network range 169.254.x.x.

3) If your device is pretty old it may also use more obscure methods like bootp and similar. The manual of your device will need to explain in detail how that works but it is involved and requires command line magic and modifications on your computers network tables that are generality only possible with Admin privileges.

Recently , I have bought an Gaussmeter IGM11 to measure the magnetic intensity. I try to establish a communicate with LAN (ethernet) between PC and IGM11. I have set static IP address to my PC as well. My pc has 192.168.222.004 and Gaussmeter IP address is 192.168.222.003. This configuration works well with the companies software even showing some result in company software.

when I come to Labview, I am trying to configure IGM11 to PC with the help of NI MAX. I try to communicate with NI MAX by adding TCP/IP instrument but no response from the instrument, just its showing visa sesson couldn't open. Please could you help me.

I have lots of Ethernet interfaced instruments that do not like to play nice with MAX. This happened to us a few weeks ago with a Keysight 5071C network analyzer. We tried a few times with max and gave up and used the IP address in the target software.

The manual that can be found is a bit sparse with specific information to how to communicate to it through Ethernet. It says that it supports SCPI like commands but only details how to do that through RS-232.

The only thing I could find is that it supports RFC-854 aka Telnet over Ethernet. This is absolutely not the same as LXI or VXI-11 as it is often called. And VISA knows two types of TCP communications. One is the TCP-INSTR resource type which requires a device to implent the LXI/VXI-11 standard to be recognizable. The other is TCP-SOCKET which only defines that communication is through TCP-IP but everything else is up to you to implement correctly. TCP-IP has no built in facility to discover random devices. That is the task of higher, application specific protocols such as LXI/VXI-11. Telnet has not any discovery facility in itself either. And MAX, respective NI-VISA does not know about the zillion possible protocols on top of TCP-IP. Either a device supports LXI/VXI-11 and can be discovered as INSTRUMENT or it doesn't and can not be automatically discovered by MAX/NI-VISA.

Your device does only support Telnet if the datasheet can be believed. That means it is up to you to write a LabVIEW driver to correctly communicate with it. Most likely once you have connected to the right port number (most likely 23 for Telnet) you should be able to send it commands and receive answers. But there is no automatisme here. It is all up to you to do the right thing!

You can create an explicit TCP-SOCKET resource in MAX or simply use one in LabVIEW to pass to the VISA functions. The syntax is "TCPIP::::::SOCKET". The hostname you have to find out from the settings in the instrument, the port number should be 23 if the manual is to be believed. And then you should be able to write the SCPI commands to it as indicated in the manual and receive responses. Do not forget to append a carriage return and/or linefeed to every command you send. This is the character (sequence) that is send to the device when you hit the enter key in a terminal session and is typically the indication to a device that the command is complete and can now be parsed.

Thank you so much for your indetailed explanation. I am trying the the way you suggestion in NI-MAX and LabView. I have creat the explicit TCP socket resource in NI-MAX but it was not taking the RAW socket and getting error.

I have tried with out configuring into NI-MAX; I have directly written or pass syntax (TCPIPO::192.168.222.003::23::SOCKET) to VISA function (Visa resource) in LabView though its not getting configured into Labview, getting errors. Could you please tell me do I need to install any driver for my instrument. I am attaching the picture of my program for your reference. Looking forward to hear from ypou soon.

Hi,

we are trying to have a small UI on Labview 2016 for remote usage via dashboard server. i am able to send commands and see their effect immediately, but i dont seem to get any reply from the robot controller.

i have tried with socket test app and it works

in labview i have tried

I would like to know what this data corresponds to Universal robot masterboard.

it remains same whenever it is run, even after restart.

i am just trying find a way to create a license for distributing the software

it is in Motherboard data these are last 4 bytes except

rob2.JPG937456 57.4 KB

As the specification mentions, these values are used only internally by PolyScope.

They might be the same in any robot or change without notice, so I do not recommend using these in your application.

For UDP, I have no problems, packets are sent to the second interface as I want. I think it work because there is a "net address" input on the "UDP Open" VI so the system can choose the right interface.

I assume you need to use the TCP listener function and according to this KB article, you can specify on which address you want to listen. So yes, you should be able to use a specific ethernet interface.

Basically, the decision which NIC to use is up to the OS and I believe that normally it would choose based on the subnet of the address you're trying to connect to and those of the NICs - I don't know what the IP address is (maybe it's in the subnet of the wrong card?), but the subnets of the NICs certainly appear to be different from each other (10.0.0.0 and 192...).

On Windows, I believe you can set the routing tables to have some more control of this (although I don't know if you would be able to force something to go through the "wrong" NIC), but I have no idea how much control you would have over this on Phar Lap. I would suggest some searching. Here are a couple of relevant links:

I can get InstaCal to see the network device with no issues. but when i try to setup the channels for the program and select browse option on the labview screen comes blank. Any help or what am I doing wrong?

Afterwards, I closed InstaCal and launched LabVIEW 2022. I selected the ULx for NI LabVIEW file 'Measure Temperature.llb' in order to test the 'ULx Acq Temperature Sample.vi'. I was able to select my device and acquire temperature data. Please test this example with your TC-32 device.

the problem was with my PC and network setting. I added a 4 port nic card to the system. when i switch the tc-32 network to the onboard it work fine with Instacal and InstaCal needs to be close to have labview work and call the device. so I reset all network port in windows 10 and the system works great.

I have a R1 brain with some analog and digital I/O and I would like to read and write these with labview in order to command & control & loggin it. I made a first try to communicate with opto22 with ethernet modbus/tcp and it has been a dead end.

Is there a way to communicate with R1 brain through ethernet and labview (12 sp1) ? If someone could give me a Vi example which works or explain me how I can do it.

The end goal of our needs is to have our SNAP-PAC-R1 run various strategies that we could initiate/terminate through labview.

That being the end result, it is my job to begin this process. So I am trying to just force the first coil on my SNAP-IDC-32D located on module 2.

I see from form 1465 that scratch pad bits have the starting address FFFF F0D8 0000, and then the next 127 bytes are also allocated for use as individual bits to be read/written to/from. (Confirm please? :D)

I recognize that 2049 should be converted to hex, which is 801 in hex, and then I use 8 as my Starting Address Hi and 01 as my Starting Address Lo, not as described above. I mean I tried both but neither was successful.

Hello everyone,

I am new to the community and to programming in general. I have a UR10 robot and the FTS300 in combination with 2F gripper of Robotiq.

I would like to run a test and connect the robot with the Labview to extract some data.

I want to get a high signal when I am touching the piece I am testing and also to get the time and the distance while I am doing the test.

I know that is really general informations,ut if you can explain to me how I can make the connection,I would be grateful.

3a8082e126