11-08-2009 08:43 PM
Hi There,
I need help for this very nusual problem. I installed the all components in the LabVIEW development suite on my host PC, which has Win XP OS. I have purchased licence for the real time module but FPGA module. My hardware is a cRIO, a reconfigurable chassis, a expansion chassis, a digital input module, a digital output module and two analogue input modules. From begainning, whole system worked fine. I built a test project to get data from or send data to I/O modules without any trouble.
Some days after, the program was no longer working. When I tried to create a new target, the error message shows "Failed to create C serial module". The further description is as follows:
"The FPGA target is busy. Stop any VIs that are running on or communicating with the FPGA target and try again. If you are using a CompactRIO chassis, it may be programmed for Scan Interface. In the LabVIEW Project, open Chassis Properties, change the Programming Mode to LabVIEW FPGA Interface, and deploy the chassis settings."
If I keep going, there is only cRIO appear in the project explore. I can't go any further from there. Even the application, which was working, can't run. In mean time, two things I have done were:
1. FPGA module 30 day evaluation has expired. In fact, I didn't use FPGA module at all.
2. I ran the Execution Trace Toolkit with an example.
I installed same software on a laptop and another PC, they are all working fine. (the software are still in 30 day evaluation).
Could someone help?
RTI-NI
11-09-2009 02:21 PM
Hi rtini,
You probably have a VI running on the cRIO that may be blocking you. In that dialog window, you should be able to continue anyways and stop any running programs (i.e. hit OK and it will redeploy settings and disconnect running VIs).
You can also try restarting the cRIO and seeing if that helps; it should stop running programs. Did you build a startup executable? If so, when you reboot, you'll need to make sure that the NOAPP switch is on.
When you mention that you try to create a new target, are you talking about adding the cRIO again? You may want to remove the old target first, then add the new one.
11-09-2009 11:17 PM
Hi Kyle,
There is no VI running in the cRIO. I even reformated the cRIO, but it still can't detect C Modules. With the same cRIO and setup, It works on other PCs. One of them with unexpired FPGA module and other one without FPGA module installed. The problem seems in that particual PC, which has FPGA module expiring history. I am thinking that it may store some information in the registra key some where while FPGA module expired, but I have no idea to find out.
Regards,
RTINI
11-10-2009 09:06 AM
Is the network configuration unique on the computer that is not working?
If you are not on the same subnet as your cRIO controller, that can cause the FPGA to not be discovered.
Kurt
11-10-2009 02:46 PM
Hi RTINI,
How are you connected to the cRIO? As Kurt mentioned, if you are using a crossover cable or a switch, you may want to check the IP Addresses of the host and the cRIO to see if they're on the same subnet.
11-10-2009 03:29 PM
Hi Kurt and Kyle,
I use a router to connect cRIO and the host PCs and they are on same subnet. All host PCs still can detect cRIO; only one of them can't find C serial modules
Regards,
RIONI
11-10-2009 03:47 PM
Hi RTINI,
Both computers should have the same software installed (Check the versions in MAX to verify) and if you're not using the FPGA Module, then the scan engine only requires Real-Time and the NI-RIO 3.0+ driver. Also, did you uninstall the FPGA Module from that machine? If not, try to deactivate the license in the NI License Manager (Start»All Programs»National Instruments, right-click the license and select Deactivate).
11-10-2009 05:37 PM
11-11-2009 04:27 PM
Hi rtini,
You may have to try uninstalling all the software to make this work. Does the NI License Manager still show an FPGA license?
11-12-2009 03:57 PM
Hi Kyle,
I have uninstalled all NI software and deleted the relevant registry keys, reinstalled softwaer except FPGA module. But the problem is still there.
Regards,
RTINI