LabVIEW
Interfacing APS 7050 AC power supply to LabVIEW through Ethernet
@Andrey_Dmitriev wrote:I was never ever able to set this for my device. At this point MAX gets "frozen" and not allow me to continue:
Regardless if I pressed "Next >" or "Done" it stay on this dialog.
But technically its not much differences if I will communicate with device using VISA Alias or directly with TCP/IP functions. May be with VISA a little bit more convenient in term of termination char, etc (or may be VISA have some known devices, which is not my case), but TCP/IP also works if used accurately, there are just pure ASCII commands, nothing more.
According to the link present in the post you answered to, the APS-7000 device uses a fixed port number 2268. Are you sure your device uses port number 1026 as used in your MAX screen shot?
@rolfk wrote:According to the link present in the post you answered to, the APS-7000 device uses a fixed port number 2268. Are you sure your device uses port number 1026 as used in your MAX screen shot?
Yes, of course, I think different devices have different port numbers, I don't have APS-7000, but have MFG-2230M instead, and this is what happened if I will put 2268 here and try to validate:
And how it looks with 1026:
Also TCP over 1026 works properly (I don't think that this device have two ports - one for TCP and another one for VISA).
So, the validation passed, and when I hit Next the MAX will allow me to enter Name for Alias, but when proceed to the next stage, then it gets frozen and not responding any longer. If I will kill NIMAX from Task Manager, then still not functional, after some attempts to start, tells me about corrupted database
The ndevice list will be empty, and finally I have to restart whole PC to get MAX running back. Very buggy. I believe, is something wrong with installation, and may be if I will reinstall everything from the scratch, then it will work, but I have tons of NI software including FPGA, RT, cRio, some cams, etc, and everything working properly, but this particular part - not.
In respect to VISA it actually depends. If you use a SOCKET VISA TCP resource, you do need to specify the port number since you are communicating directly on socket level, the same as what the TCP nodes do. The difference is mainly in what termination character you can configure (none or one selectable character in VISA, only CR-LF with the native TCP nodes).
VISA also knows about an INSTR resources for TCP connections. This is using the VXI11 aka HiSlip aka LXI protocol. These three are not exactly the same but related to each other, with VXI11 being the basic and the others extending on that. Here you do usually not specify any port number since this protocol uses by default the port number 4880 (it's obviously designed by someone who was working with GPIB, which is the IEEE-488 standard 😁).
VXI-11 also supports device discovery through UDP, so that any connected device should announce itself automatically when you scan for instruments on the network. For such resources a lot more of things are working more or less seamlessly, while for a SOCKET resource you have to handle everything yourself.
It seems the device connection works fine but when trying to register the alias something goes pretty wrong. This would be likely a corrupted installation of part of NI-VISA or NI-MAX.
