LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

RT target works OK in volatile mode but does not when deployed in non-volatile mode.

I have developed several applications using the NI cRIO-9073 Integrated chassis. The applications work perfectly well in volatile mode (development), but when I come to deploy the the RT target as an executable the application does not work. Now, I ran the LabVIEW Real-Time 1 Solution application and the same problem occured, in this case, the USER1 LED came on then went off as if an error occured. I finally trapped an error around the shutdown stage, attached, funny thing is though the error code doe not make sense as I am not using the FPGA, running in scan mode, however, I could be missing something.

 

(Note: I have obviously modified the Real-Time 1 course solution to use my existing hardware)

 

Now this is where it gets puzzling, 3 years ago I did the old RT course, LabVIEW Real-Time Application Development, I have now run the solution for this course, on the same target as the RT1 solution and it works!!!

 

I have contacted NI support with no solution to this problem. In the meatime I have a NI cRIO-9704 on order and when it arrives I will try again.

 

I really need to know, however what is going on here, does anyone out there have any Ideas? have you experienced any similar problems?

 

Thanks

 

Neil

 

Certified-LabVIEW-Associate-Dev_rgb.jpg

0 Kudos
Message 1 of 5
(2,536 Views)

Note to self - Include attachment...

 

Error Log


Status: TRUE

Code: -65589

Source: Shared Variable in Chamber Control.vi->RT Main.vi

This error or warning occurred while reading the following Shared Variable:
\\NI-cRIO9073-0180F3D1\Thermocouple Mod\Temperature-cRIO
\\localhost\Thermocouple Mod\Temperature-cRIO

 

Error -65589 occurred at an unidentified location

Possible reason(s):

CompactRIO:  The FPGA VI you are running does not contain the DMA FIFOs that the RIO Scan Interface requires. Ensure that the modules under the Chassis item in the project match the modules in the chassis, and recompile the FPGA VI.

 

 

0 Kudos
Message 2 of 5
(2,512 Views)

Any chance you can zip up your whole project and add it as an attachment, or even better, simplify it down to just enough code to cause the error and then attach that?

0 Kudos
Message 3 of 5
(2,501 Views)

I have added an attachment, last time I tried this didn't work...

 

If you can see the attachment, this is the RT1 Solution modified to use my hardware.

0 Kudos
Message 4 of 5
(2,485 Views)

@dagon wrote:

I finally trapped an error around the shutdown stage, attached, funny thing is though the error code doe not make sense as I am not using the FPGA, running in scan mode, however, I could be missing something.


Yes, you are running the FPGA in Scan Mode. On a cRIO, all IO is through the FPGA, so you are using the FPGA in Scan mode to read temperatures and set outputs. I have no experience with the Scan Engine and shared variables so unfortunately I can't help here, but search through the help and the NI web site. Maybe there's something you need to do in order to properly deploy the shared variables and scan engine as part of a compiled application.

0 Kudos
Message 5 of 5
(2,471 Views)