01-21-2010 11:22 PM
Solved! Go to Solution.
01-22-2010 04:40 PM
TCPIP0::169.254.47.101::3000::SOCKET
Is there something else that needs to be specified or not specified when using VISA on the CRIO? Or is it just not supported?
Thanks
01-22-2010 06:29 PM - edited 01-22-2010 06:29 PM
Yes, you should be able to use VISA command on your Real Time VI so you can communicate over the built in serial port. In order to do this you will need to make sure you have the VISA driver installed on the cRIO.
Check out this example that shows how to set up a serial server/client between your cRIO and Host.
Serial Data Transfer Between cRIO and Host
01-23-2010 11:40 AM
For ethernet??? If I wanted to use the serial port that would be great, but I have two instruments that I need to communicate with which is why I chose a hub ethernet solution. Am I missing something?
01-25-2010 09:33 AM
If you want to use a premade Ethernet instrument driver you need to make sure it is compatible with the Real Time OS. Otherwise you can just use simple TCP/IP commands to build your own. You should be able to do most basic types of internet communication.
Hunter
01-26-2010 09:58 AM
klessm1,
Actually Ethernet resources are supported by VISA on cRIO targets. The passport, NiViEnet.out, should be installed to /ni-rt/system/vxipnp/VxWorks/bin/. If the passport is indeed installed on your system, could you tell us a little bit more on what you meant by "not work"? How exactly are you interacting with the SOCKET resource and what error did you receive?
01-26-2010 11:18 AM
I will check if it is there, but I made a call to NI support yesterday and they came up with the same conclusion that it wasn't supported. It may be because I am using a 9004 controller?
Here was my test: I have my laptop, crio, and ethernet instrument (socket only) hooked to a hub (not a router). Everything is set to the same subnet.
I perform a VISA open and close on TCPIP0::169.254.47.101::3000::SOCKET from my host and pass back the error. No error as I can establish the connection.
I then move the same vi over to the crio target and run it there. I get a VISA open error - not enough information or device not present in the system.
Also, when setting up a TCP instrument from max on the crio, it does not allow me to continue (indicates it is not supported).
Note this instrument cannot be run using the LAN based instrument configuration (TCPIP0::169.254.47.101::INST0::INSTR) from host or crio, only the socket configuration.
The NI support guy said he looked it up in a table some where that indicated that it was not supported?
01-26-2010 01:52 PM
klessm1,
I'm not sure what table were used, it was probably out-dated. As of VISA 4.4, the Enet passport is supported on cRIOs. If you are using an older version, you might want to upgrade to the latest VISA (download Link).
01-26-2010 03:24 PM
I have VISA 4.5.1 and VISA Server 4.5.1 on that system. For some reason that crio (9004) did not have the vxworks directory on it. Maybe it needs to be scrapped and reloaded. A 9072 that I have does have that directory. I will try a quick TCIP test on that (I can't use this one for the solution though because it doesn't have enough memory).
Kind of off topic, but one of the reasons I did not reload it while debuggin ws that everything looked up to date (RIO 3.2.1) and it also had NI-CAN 2.6.3 on it. When going through the reload it indicated it was going to remove the NI-CAN, but we need it for a CAN module we are using. I have NI-CAN installed (I even reinstalled it from a download), but it doesn't seem to show up. Would I need to use the drivers DVD to do a special install for CAN for realtime on my host instead of just the NI-CAN drivers that can be downloaded seperately? I know it is off topic and all, but since I have a crio expert here.
01-26-2010 05:39 PM