11-27-2011 09:16 PM
LV 10.0.1
cFP RT 6.0.8
cFP 2100
I have written a communications test program that runs on compact field points.
It works on: cFP 2220 (4 Ports) cFP 2200 (1 port)
It doesn't work on: cFP 2100 (1 port present, 0 Ports detected)
The symptom is the com port drop down list is empty.
Manualy entering an "invalid" comport doesn't work.
Does anyone have any thoughts?
Screen Grabs:
Correctly working on 2200
Faulty 2100
installed S/W
Solved! Go to Solution.
11-28-2011 11:45 AM
Hi Timmar,
From the information you provided it does seem that you are doing things correctly (for others, the instructions can be found here).
I'd like you to try/check a few things:
1) Can you perform a console out on the 2100? (instructions here) This should be able to confirm that the serial port is functioning.
2) Make sure the console out switch (switch 5) on the controller is off when trying to run your program.
3) What options is selected for the VISA Class? (right-click on the control, see below)
Have a great day,
Chris V
11-28-2011 08:27 PM
Console out was a success, So the port is in working order.
I am using "Instr" Class.
It works on 2200 and not 2100, in theory the code should be portable between devices, right?.
Tim L.
11-29-2011 09:43 AM
Hi Timmar,
Yes, I too thought that it should be portable. However, when I was doing some testing with this, I noticed that the different controllers showed different behaviors using different VISA Classes.
Did you try any of the other classes? I'm think specifically Serial Instr.
Have a great day,
Chris V
11-29-2011 06:12 PM
I tried Serial (a more specific class), the result did not change.
Did you use a 2100?
Tim L.
11-30-2011 01:03 PM
Hi Tim L.,
Something that I did fail to mention earlier is that the cFP-2100 is running a different operating system than your cFP-22xx's. The 2100 is a Phar Lap ETS controller and the 22xx's are VxWorks. This could be causing the different behavior.
Two things to check:
1) Are you connected to the cFP in the project when trying to select the COM port, or are you developing in offline mode? For the Phar Lap ETS controller I believe it will be necessary to be connected before the COM ports will show up.
2) Is the controller in the project a 2100, or is it a 22xx that you simply changed the IP address of? If you simply changed the IP address, it would be a good idea to add a 2100 to the project and then drag your VIs under it, so that we are sure LabVIEW is compiling the VIs for the correct operating system.
Have a great day,
Chris V
11-30-2011 03:34 PM
Done all of that, Add target -> Add vi -> deploy
When working on a 2220, 2200, PXI or PC, the com ports don't show in the dropdown up until it is first deployed.
I have made sure that I follow the same steps.
When I get to work this morning I will see if I can get it to work on LV8.6 on a much older RT operating system.
I suspect I may be looking down the barrel of yet another cFP software bug,
Tim L
12-01-2011 07:48 AM
I have had this same issue the past couple days, cFP-2210 (VxWorks), LV 2010 SP1 Fieldpoint Driver packaged 6.0.8 . Connecting to the cFP unit has resolved my issue. Right click the cFP device in the project and select connect, the green LED next to the unit in the project should light up.
I don't remember having to do a live connection with previous versions of LV to get the visa resource control/constant to populate.
12-01-2011 04:24 PM
Hi TimL,
Did you make a new target in your project for the 2100, or just change the IP address to your 2100?
Have a great day,
Chris V
12-01-2011 07:37 PM
I always add new target and then ctrl-Drag the test application into it..
I now have 6 Compact fieldpoints in my system, 4x2220, 1x2200, 1x2100
The 2100 is the only one misbehaving.