CRIO 9802 Error 65000

Hi all,
i tried the LabVIEW example "NI 9802 RT Access (Host)", with which i want to mount one SD card. I everytime get the attached error message. I already used chkdsk to correct the SD card and there are no errors on it. It's no problem to write file from the FPGA, but to mount from RT result's in this error.
I use LabVIEW 8.6. NI RIO 3.0.1 is installed on the cRIO.
Can someone guide me to a solution.
Thanks.
Alex
Message Edited by -_ALEX_- on 02-06-2009 10:02 AM
Solved!
Go to Solution.
Attachments:
Error65000.PNG ‏8 KB

Hi John,
thanks for letting me know that the new NI Rio is available.
I installed the new driver, but unfortunately a got a new Problem. It is possible to Mount and Unmount the SD Card, but i can’t ftp to it.
I tried to connect via Microsoft IE, and received following message:
Does anybody have an idea why?
Thanks
Message Edited by -_ALEX_- on 02-20-2009 11:13 AM
Attachments:
mount.JPG ‏25 KB

Similar Messages

Error 65550: CRio 9802

Hi everybody,
I was running example "NI 9802 RT Access" from a 9074 writing to a 9802 but I got the following error:
Error 65550 occurred at cRio-91XX_MountSdDrive.vi
Possible reason(s):
CompactRIO: A problem was found in the file system. Remove the SD card and run CHKDSK.
Running CHKDSK returns no problems. Any idea what's causing this error?
Thanks a lot.
Solved!
Go to Solution.

Dhasa
This is a known issue for the NI RIO 3.0.1 driver, you can fix it by upgrading the NI RIO 3.1
Please repost if that does not fix it.
-Hunter

UDP with cRIO and error 113

Hi all,
i'm using the UDP protocol to exchange information between a PC and a cRIO; the first is the master, the second is the slave.
In the cRIO i developed a piece of code in order to realize a loopback, so that the message sent from the PC is sent back to the PC itself as it has been received, without any modification.
First, i tried sending a short message (100 B) from the PC to the cRIO; in this case, no problem at all
Then, i tried sending a long message (20 kB) from the PC to the cRIO; in the cRIO code, the error number 113 was raised when trying to send back the message to the PC (calling the UDP write function)
What can be the origin of the different behaviour between the PC and the cRIO? Seems to be a question of buffer size... Can it be dependent of the OS? How can i increase it in the cRIO?
Thanks!
aRCo

Hi aRCo,
According to Wikipedia (https://en.wikipedia.org/wiki/User_Datagram_Protocol), the max. theoretical limit for a UDP datagram is 8 bytes for header + 65,527 bytes of data (65,535 bytes in total). However, "the practical limit for the data length which is imposed by the underlying IPv4 protocol is 65,507 bytes (65,535 − 8 byte UDP header − 20 byte IP header)". The wiki article goes on to say that larger packets are possible with Jumbograms.
As for the NI documented limits of 8K, this would appear to be a LabVIEW-imposed limitation. (Perhaps this was related to an earlier limitation of the UDP protocol that has since been upgraded. If I recall correctly, the Windows version of LabVIEW also had this 8K limitation in the past.)
Perhaps NI relaxed this limit, or maybe you have jumbo packets enabled on youir PC, and this is allowing more throughput (-- of course both of these possibilities are only speculation on my part).
In any event, if you limit the UDP packet size to the documented 8K limitation, your code should probably be fine across all LV platforms. (How's that for stating the obvious..?)
Anyway, good luck with your application.
-- Dave
www.movimed.com - Custom Imaging Solutions

CRIO disconnects from Ethernet network and stops responding to pings

We are running a cRIO application that periodically disconnects from the Ethernet network even though the VI continues to run on the cRIO.
The application has two parallel loops. One loop reads data from the FPGA and writes it to a RT FIFO. The second loop opens a TCP connection to a remote host, reads data from the RT FIFO, and transmits the data to the remote host. We have instrumented each loop to send messages to the serial port that indicate their status. When the cRIO disconnects, both loops continue to send their status messages to the serial port. The first loop happily continues reading data from the FPGA and writing it into the RT FIFO. The RT FIFO overwrites the oldest data when it fills up to keep it from overflowing. The second loop reports a TCP write timeout (tcp write error 56) around the time that the cRIO disconnects, after which it closes the existing TCP connection and then repeatedly tries to open a new TCP connection (each attempt times out after a 5 second delay).
All that appears normal and usually the connection is automatically restored. Occasionally, however, the cRIO is not able to re-open the TCP connection. Furthermore, the cRIO stops responding to pings from the remote host. On two occasions, the cRIO was finally able to open a new connection after 30-40 minutes. Other than that, the only way we've found out of this dilemma is to reboot the cRIO.
The frequency of the disconnects and the time before they occur doesn't seem connected to whether or not the cRIO is set to run the application at startup or if the application is run via an interactive VI window on the remote computer.
It is possible that the disconnects have something to do with which computer the cRIO is connected to, as the problems seem to happen much more frequently (often within minutes) when the cRIO is sending data to a laptop running Windows XP, but it can run for hours when sending data to a rackmount server running Windows Server 2003. Everything else (the speed and size of data being sent, the ethernet hub and cables, the VI running on the remote computer) is the same.

We're done most of the testing with a 9014 real time controller and a 9104 chassis. However, we've also seen similar behavior with 9014/9103 and 9102/9101 combinations.
The 9014 cRIO normally runs at around 50% CPU usage and less than 40% memory usage when the data is flowing steadily. The RT System Monitor did not indicate a spike in either before the cRIO disconnected.
Measurement and Automation Explorer is not able to connect to the cRIO after it disconnects. We tried pinging the cRIO from a different computer, but that also failed.
After disconnecting, the cRIO sends error messages to the serial port while trying to open a new TCP connection. It reports an error 56 (time-out error) 3 or 4 times (for a total duration of 15 or 20 seconds) and then reports an error 42 (generic error) at least 10 times per second for 18 seconds, and then switches back to 15 seconds of timeouts, and so on. When getting error 42, it ALWAYS gets it for 18 seconds straight. It usually gets error 56 for 15 seconds (3 timeouts) but sometimes for 20 seconds (4 timeouts).
When the cRIO disconnects, it can't be contacted by any computer through the ethernet port, yet the link lights still show that it is connected. If its connected directly, both the green and orange link lights on the cRIO light up, but when it is connected through the 10 Mb hub, only the orange link light lights up, but the hub shows that the cRIO is connected to it. In spite of this, it is still impossible to ping the cRIO in either scenario.
It is possible that, in addition to what computer the cRIO is connected to, the errors could be related to whether the cRIO has a direct connection to a computer or if it is connected through a hub. Today, we have only managed to get errors when the cRIO is directly connected to a laptop (one error after 1.5 minutes, one after 10 minutes, one after 7 minutes, etc.) There were no disconnects when the cRIO was connected to a 10 Mbps hub for more than half an hour.
Do any of those symptoms give you clues about what is happening?
Thanks!

Rio system software conflict resolution

I noticed the following Conflict Resolution report when trying to start running a LabVIEW 2012 application on an NI-9074 cRIO.
Errors were detected in the target log when connecting to the target:
LabVIEW: Failed to load shared library vxsntpc.out. Ensure that the library is present on the RT target. Use MAX to install NI software or FTP to transfer custom libraries to the RT target.
LabVIEW: Failed to load shared library niDiscSvc.out. Ensure that the library is present on the RT target. Use MAX to install NI software or FTP to transfer custom libraries to the RT target.
LabVIEW: Failed to load shared library niorbs.out. Ensure that the library is present on the RT target. Use MAX to install NI software or FTP to transfer custom libraries to the RT target.
Select "Apply" to ignore these errors and continue with deployment.
NI-MAX reports that the host has newer versions of some cRIO software components than are on the cRIO. I tried to update them using NI-MAX, but got a message that Network Variable Engine 12.0.0, Network Streams 1.2, System State Publisher 3.0.0, and Variable Client Support for LabVIEW RT 12.0.0 all require LogosXT 5.4.0. I'm not sure what this means.
Are the updates available on the host for LabVIEW 2013? How do I discover the components that load vxsntpc.out, niDiscSvc.out, and niorbs.out?
Thanks,
Hamilton Woods

Christian,
Thanks for your reply.
On Friday evening, per NI suggestion, I installed the latest system configuration. That did not eliminate the problem. On Monday morning, per NI suggestion, I reformattted the cRIO and reinstalled the system software. That fixed the problem.
Hamilton Woods

Is NI-9802 memory module compatible witn NI-cRIO 9081????

hello,
I an working on NI-cRIO 9081 using NI-9467 GPS module and 9795 WSN gateway. Now i want to load this data into NI-9802 memory card module, but i am getting a error code 65010 showing that you cant mount or unmount SD card on this cRIO 9081. Can somebody give me a sugestion related to this problem ?????
i am waiting for response

Here is an example VI that ships with LabVIEW that may help. You can change the Write to Text File to Write to Binary File.
Applications Engineer
National Instruments
Attachments:
9802.zip ‏5 KB

Want to ftp to NI 9802 through cRIO 9014

Can the cRIO 9014 access the 9802's SD memory cards directly as disks?
If I use the cRIO 9014 as an ftp server, can I download/upload files directly to the 9802's SD memory cards from the an external computer, via ftp?
It initially looks to me like only the FPGA, not the 9014, sees the 9802 directly, which means the answer to my questions is NO, unless there's a device driver for VxWorks.
Does anyone know more?
Thanks

Hi,
Thanks for the good information. I was running into the same problems in my application. I would like to make a few clarifications though.
First: Most of the file I/O functions available to you on the function pallet boil down to primitive file functions, so it is not necessary to restrict yourself to using only primitive file functions, one can use the Write To Spreadsheet File vi for example.
Second: As stated in the KB article here http://digital.ni.com/public.nsf/allkb/6BA5F76568ECADA68625742D006A0356 a property OR method node can be used in the FPGA vi to resolve the shared resource conflict indicated by Error -65549. So if you application already used one of the methods, it is not necessary to go out of you way to use a property node referencing the 9802. However, if you application does not use one of the 9802 methods, using a property node that references the 9802 is the method that uses the least amount of FPGA resources to resolve the conflict.
I hope this helps anyone that comes across this post and has the same problems that I was having.
I would like to thank Matt Rings, one of NI's embedded gurus and Chris Nelson my local NI sales rep for helping me out with this issue.
Message Edited by Gravy Train on 06-09-2008 10:37 AM
Message Edited by Gravy Train on 06-09-2008 10:37 AM

NI 9802 File Error 11

Hello All!
I encountered a problem while file logging on an SD card which is
installed in NI 9802. There are 169 binary files already in the SD
card, when the 170th file is to be created an error with code 11 comes
out. Please help me to remove this error.
Software:
LV 8.5.1
cRIO 2.4
Hardware:
cRIO 9012
NI 9802
Regards
Mani

Brandon,
I still have a few issues and thought that maybe you could help me out here. I have now managed to save my files in my SD card via the 9802 module using the standard RT scan engine method attached with the original post. However, I cannot find a way to download my files to my local machine. I am using the std FTP functions (please see attached) but I get the typical file not found error. I saw that there is also a download option through the FPGA invoke method but this method has absolutely no other info in or out of it.. So where does it download the file(s)??
Also note that although my card is mounted as u: (getting this from the mount sd card invoke method), ftping
ftp://xxx.xx.xx.xxx/u:/
returns that there is no such location..
Any thoughts?
Thanks a lot, Harry
Attachments:
dl_rio.jpg ‏121 KB

I am recieving an Error code when I try to compile a program to an FPGA chp in a cRIO but I don't know what the code means.

This is the message that I am recieving when I compile to the cRIO I am working with.
FATAL_ERRORortabilityortDynamicLib.c:358:1.27 - dll open of library
   <C:/NIFPGA85/Xilinx\bin\nt\libGenXstTask.dll> failed due to an unknown
   reason.   Process will terminate. For more information on this error, please
   consult the Answers Database or open a WebCase with this project attached at
   http://www.xilinx.com/support.
I have no idea what this means. Thank you in advance for the help.

UtahTiger;
First let me ask a few basic questions
What version of LV are you using?
What OS is your development machine?
When in the compile process does this error occur?
Can you compile other (blank) VI's, id the problem with this particular project?
Have you been able to compile this project before. what changed?
Once I know a little more about your system we can narrow down the source of your error.
Message Edited by Huter on 04-29-2009 04:16 PM

Error when running simulation with SIT 2010 on a cRIO 9073, what do I need to install on the cRio?

Hi.
I am trying to run a simulink model on a cRio 9073 using SIT 2010. I succesfully created the FPGA vi and the lvbit file in order to map input/outputs to the model. I also created the DLL and OUT for the model.
When I run the interface VI on my computer, everything seems OK, until I get the following error and I am not able to run the simulation. I found a similar post earlier that suggests that I need to install the shared variable engine or the Simulation Interface Toolkit on my cRio. I tried to do both using MAX but could not find neither of the suggested installations.
Thanks for the help!
Items.viNI_SIT_driversupportVIs.lvlibIT Probe Model Items.vi loaded with errors on the target and was closed.
LabVIEW: Failed to load shared library SITs.*robeSignals:C. Ensure that the library is present on the RT target. Use MAX to install NI software or FTP to transfer custom libraries to the RT target.
Items.viNI_SIT_driversupportVIs.lvlibIT Probe Model Items.vi loaded with errors on the target and was closed.LabVIEW: Failed to load shared library SITs.*robeSignals:C. Ensure that the library is present on the RT target. Use MAX to install NI software or FTP to transfer custom libraries to the RT target.

Hola jarcTec;
Este tipo de error suena suele ocurrir cuando no se tienen las librerías apropiadas instaladas en el cRIO. Te recomendaría que abrieras MAX, debajo de la pestaña de Remote Systems selecciones tu dispositivo>> software, click derecho e instalar software. Aquí debes asegurarte que las librerías que te faltan estén instaladas en el cRIO. En Custom Installation selecciona SIT como opción para instalar en el cRIO tal y como se muestra en las imagenes.
Espero esta información te sea de utilidad
Exito en tu aplicación
Marisol

Not able to create OUT file with "nidll_vxworks" in Matlab for use with the LabVIEW SIT 2010 and a cRio 9073, sh.exe error

I am trying to compile an OUT file for my Simulink model using "nidll_vxworks" and run it using the Simulation Interface Toolkit for a cRIO 9073 . I am able to compile the DLL file using "nidll" and succesfully run the simulation using my PC as the host.
I already downloaded the "gccdist" and "vxworks61gccdist" folders and copied them to "c:" When I build the model in Sumulink I get the following error at the end of the process (at the same time windows tells me that "sh.exe" has stopped working). If it matters I am running Windows 7 64bits, but using Matlab 2009b 32bits and LabView 2010 32 bits. ANY HELP WILL BE APPRECIATED. "QofV" is the name of my Simulink model and I changed to "XXX" parts of the file path.
### Linking ...
rm -f "QofV.out" ctdt.c;nmppc QofV.o QofV_data.o rtGetInf.o rtGetNaN.o rt_logging.o rt_look.o rt_look1d.o rt_nonfinite.o nidll_main.o rt_sim.o ode8.o | tclsh c:/gccdist/WindRiver/vxworks-6.3/host/resource/hutils/tcl/munch.tcl -c ppc > ctdt.c
abnormal program termination
C:\Users\XXX\AppData\Local\Temp\make426012.sh: fork failed: no child processes [1]
make: *** [QofV.out] Error 1
### Real-Time Workshop build procedure for model: 'QofV' aborted due to an error.
>>
### Linking ...rm -f "QofV.out" ctdt.c;nmppc QofV.o QofV_data.o rtGetInf.o rtGetNaN.o rt_logging.o rt_look.o rt_look1d.o rt_nonfinite.o nidll_main.o rt_sim.o ode8.o | tclsh c:/gccdist/WindRiver/vxworks-6.3/host/resource/hutils/tcl/munch.tcl -c ppc > ctdt.c
abnormal program termination
C:\Users\XXX\AppData\Local\Temp\make426012.sh: fork failed: no child processes [1]make: *** [QofV.out] Error 1 ### Real-Time Workshop build procedure for model: 'QofV' aborted due to an error.>>
### Linking ...rm -f "QofV.out" ctdt.c;nmppc QofV.o QofV_data.o rtGetInf.o rtGetNaN.o rt_logging.o rt_look.o rt_look1d.o rt_nonfinite.o nidll_main.o rt_sim.o ode8.o | tclsh c:/gccdist/WindRiver/vxworks-6.3/host/resource/hutils/tcl/munch.tcl -c ppc > ctdt.c abnormal program termination C:\Users\XXX\AppData\Local\Temp\make426012.sh: fork failed: no child processes [1]make: *** [QofV.out] Error 1 ### Real-Time Workshop build procedure for model: 'QofV' aborted due to an error.>>
Solved!
Go to Solution.

Hello jarcTec,
I am not sure right now if you can do it, but this tutorial might help, also everything was made in Winddows 7 in this one.
http://zone.ni.com/devzone/cda/tut/p/id/11654
Take a quick look and let me know if it works!!!
Luis Fernando
National Instruments Cono Sur
Ingeniería de Campo y Consultoría
http://chile.ni.com/

Why do I keep getting error -65581 when trying to use a cRIO 9024 and c series modules

I am simply trying to send out a digital high on DIO0 of a 9401 c series module and I get the following error every time.
Error -65581 occurred at Shared Variable in Send True Value Out.vi
Possible reason(s):
CompactRIO: (Hex 0xFFFEFFD3) The FPGA personality currently running on the CompactRIO chassis does not support the RIO Scan Interface in this slot.
This error or warning occurred while writing the following Shared Variable:
\\NRL-CMG-cRIO\NI 9401-1\DIO0
\\170.126.209.52\NI 9401-1\DIO0
Any help would be greatly appreciated.
Nate
Solved!
Go to Solution.

NMAYO,
In your project view can you right click on the chassis in the cRIO and make sure that it is set for Scan Mode and not FPGA mode? Also, In the measurement and automation explorer you can check the cRIO and verify that it has Scan Engine Support installed on it. The tutorial below shows how to reformat a cRIO and install software on it, the later steps on software will allow you to check your cRIO.
Reformatting a CompactRIO Real-Time Embedded Controller
Ben Sisney
FlexRIO V&V Engineer
National Instruments

Shared Variable Initial value not licenced error with cRIO

Hello Everyone,
I've a project that will be deploed on cRIO. This project was created on a different machine and didn't have any error regarding the shared variables. when I transfered the project to the computer connected to the cRIO, I have this error with all shared variable. The error message says that:
1. Initial Values: Not Licenced or can't be edited outside of LabVIEW.
2. Logging: Not Licenced or can't be edited outside of LabVIEW.
attached are two images for the error i have.
Can I have help with this issue?
Thanks in advance
Attachments:
1.png ‏134 KB
2.png ‏142 KB

Good day,
Sounds like you are using the DSC module features on your code and you forgot to activate the runtime system on that machine. If you have access to the NI License Manager, please check the status of the license.
We need an active license for the second message but, for the first one you can try to program your own initial values for all of your network-published shared variables by initializing whenever the PC is started. During the initialization portion of your code, you can just write a constant value to the shared variables so the values are the same initial values every time it is run.
Regards,
Alejandro | Academic Program Engineer | National Instruments

RT cRIO: Shared Variable Engine Errors

This is an app written in LV2011 running on a cRIO-9076 (Scan mode), with the August release of software installed on it.
I have gown to great lengths to try an optomize my code, I have reached an impasse. The VERY FIRST TIME I run the code on the target (be it via a self-starting EXE or targeting from my Windows development machine I am able to read and write to several shared variables, but then when I access them again (possibly when I am starting a couple timed loops and the processor is very high) I get this:
Error -1950679023 occurred at Shared Variable in targetIdleLoop.vi->ZDAQ_cRIO_Target_Main.vi
Possible reason(s):
LabVIEW: (Hex 0x8BBB0011) The connection to the server was disconnected.
This error or warning occurred while writing the following Shared Variable:\\ZeeAero-RIO1\variables - network - RT (separate)\RTStatus\\10.10.10.10\variables - network - RT (separate)\RTStatus
If I go back to the Dev machine and restart the code, I don't get this error; it only happens after a reboot.
BUT on this second run (or subsequent VI starts), when we get to that same point, a client priogram running on Windows and reading a network variable successfully suddenly gets:
LabVIEW: -1950679035 (Hex 0x8BBB0005) Unable to locate variable in the Shared Variable Engine. Deployment of this variable may have failed.
Which lasts a minute or so, then goes away. The code is made to loop, and when it loops back through this point there are no errors at all.
So, to recap:
1st Run after reeboot, 1st loop :Error on Target (0x8BBB0011), connection to server disconnected
Subsequent Runs, 1st loop: Error on Windows Client (0x8BBB0005) Unable to locate variable in the Shared Variable Engine. Deployment of this variable may have failed.
Subsequent Runs, 2nd+ loop: No error
Here is a link to a screenshot of the installed SW on the Target:
EDIT: I should mention that there are three loops running in parallel on this app; 1 is a Timed-loop (at the moment) set to a period of 10ms with 100 priority, #2 is also a timed loop and is set to 3ms with priority = 50 and the third is a WHILE loop with a 50ms wait. The error occurs during the WHILE init phase, which happens once per run, not repeatedly.
Solved!
Go to Solution.

This is killing me. It's obviously something to do with when the Timed loops start AND when I access the network variables.
See the screenshot below.
Note that I read and write to several network variables in Subroutines to the left of this screenshot at startup. The starting of the timed loops causes the issue with the shared variables. (also note that the periods are set to 100ms and 99ms in my testing after the initial 1st loop.
Now look at the Wait at the bottom set to 10 seconds. In this case, it will work. There is no error at breakpoint 37 if I wait around 10s. If I DON'T wait the 10 seconds, there is an error after the check on the BOOL "stop - Network" variable that NEVER GOES AWAY. If I look at the CPU monitor, there is an initial bump in the cpu when starting the loops, and then it drops to about 15%. But if I don't have that 10s wait, there is ERR 0x8BBB0011 and the CPU spikes to 75% every 5 seconds and it never goes away.
And that's only the 1st loop after reboot. The 10s makes this work, but I still have an issue with it once I start doing individual runs (loops).

CRIO application works in interactive mode but broken VIs reported in error log when run built application on target

I have been getting more than my fair share of grey hairs the past few days because of this. Over the past few months this almost never happened. Lately, after a seemingly minor change to some serial communications code, hardly a single build works without throwing errors like this:
#OSVers: 6.3
#OSBuild: Jun 6 2014, 09:14:16
#AppName: /c/ni-rt/system/lvrt.out
#Version: 14.0
#AppKind: AppLib
#AppModDate:
InitExecSystem() call to GetCurrProcessNumProcessors() reports: 1 processors
InitExecSystem() call to GetNumProcessors() reports: 1 processors
InitExecSystem() will use: 1 processors
starting LabVIEW Execution System 306708506 Thread 0 , capacity: 1 at [3507679466.00933790, (19:24:26.009337710 2015:02:24)]
starting LabVIEW Execution System 306708507 Thread 0 , capacity: 1 at [3507679470.59560204, (19:24:30.595601929 2015:02:24)]
starting LabVIEW Execution System 2 Thread 0 , capacity: 24 at [3507679481.25993776, (19:24:41.259937648 2015:02:24)]
starting LabVIEW Execution System 2 Thread 1 , capacity: 24 at [3507679481.25993776, (19:24:41.259937648 2015:02:24)]
starting LabVIEW Execution System 2 Thread 2 , capacity: 24 at [3507679481.25993776, (19:24:41.259937648 2015:02:24)]
starting LabVIEW Execution System 2 Thread 3 , capacity: 24 at [3507679481.25993776, (19:24:41.259937648 2015:02:24)]
Thread consumption suspected: 3 Try starting 4 threads
starting LabVIEW Execution System 2 Thread 4 , capacity: 24 at [3507679515.59324312, (19:25:15.593243004 2015:02:24)]
starting LabVIEW Execution System 2 Thread 5 , capacity: 24 at [3507679515.59324312, (19:25:15.593243004 2015:02:24)]
starting LabVIEW Execution System 2 Thread 6 , capacity: 24 at [3507679515.59324312, (19:25:15.593243004 2015:02:24)]
starting LabVIEW Execution System 2 Thread 7 , capacity: 24 at [3507679515.59324312, (19:25:15.593243004 2015:02:24)]
Thread consumption suspected: 8 Try starting 1 threads
starting LabVIEW Execution System 2 Thread 8 , capacity: 24 at [3507679515.73854351, (19:25:15.738543576 2015:02:24)]
and
#Date: TUE, FEB 24, 2015 04:47:22 PM
#OSName: VxWorks
#OSVers: 6.3
#OSBuild: Jun 6 2014, 09:14:16
#AppName: /c/ni-rt/system/lvrt.out
#Version: 14.0
#AppKind: AppLib
#AppModDate:
InitExecSystem() call to GetCurrProcessNumProcessors() reports: 1 processors
InitExecSystem() call to GetNumProcessors() reports: 1 processors
InitExecSystem() will use: 1 processors
starting LabVIEW Execution System 306708506 Thread 0 , capacity: 1 at [3507670087.84041262, (16:48:07.840412710 2015:02:24)]
starting LabVIEW Execution System 306708507 Thread 0 , capacity: 1 at [3507670092.45153570, (16:48:12.451535843 2015:02:24)]
starting LabVIEW Execution System 2 Thread 0 , capacity: 24 at [3507670103.11840487, (16:48:23.118404925 2015:02:24)]
starting LabVIEW Execution System 2 Thread 1 , capacity: 24 at [3507670103.11840487, (16:48:23.118404925 2015:02:24)]
starting LabVIEW Execution System 2 Thread 2 , capacity: 24 at [3507670103.11840487, (16:48:23.118404925 2015:02:24)]
starting LabVIEW Execution System 2 Thread 3 , capacity: 24 at [3507670103.11840487, (16:48:23.118404925 2015:02:24)]
VI_BROKEN (0): [VI "NC serial comms protocol.lvlibet Lower Temperature Limit.vi" (0x04667310)]
VirtualInstrument:etOrClearBadVILibrary - now VI is bad on [VI "NC serial comms protocol.lvlibet Lower Temperature Limit.vi" (0x04667310)]
this->flags=33563136, compilerError=6
VI_BROKEN (0): [VI "Heater Control HAL.lvclass:Write Heater Control Active.vi" (0x058c4e98)]
VirtualInstrument:etOrClearBadVILibrary - now VI is bad on [VI "Heater Control HAL.lvclass:Write Heater Control Active.vi" (0x058c4e98)]
this->flags=50340352, compilerError=6
VI_BROKEN (0): [VI "NI_LVConfig.lvlibave Config File.vi" (0x047b7e90)]
VirtualInstrument:etOrClearBadVILibrary - now VI is bad on [VI "NI_LVConfig.lvlibave Config File.vi" (0x047b7e90)]
this->flags=33563136, compilerError=6
and so on.
This is using a cRIO 9074 running CompactRIO recommended software set 14.0.1 .
These errors happen right at startup. Memory use is steady in interactive mode, about 20 MB contiguous memory is unallocated out of 128 MB. I have taken pains to prevent allocation and follow cRIO besta practices non concatenated strings array building in loops etc). CPU is 50-60% when running interactive mode.
Really at my whit's end here, I have tried the various combination of enabling / disabling debugging in the RTEXE, disconnecting typedefs etc. I have not noticed a pattern.
Regards,
MarkCG

Hello MarkCG,
What minor changes did you make to the serial communication code? Posting the VI or a screenshot of the VI with the modifications which caused the RTEXE to stop functioning could be useful to troubleshoot the issue.
Regards,
J_Bou

CRIO 9802 Error 65000

Similar Messages

Maybe you are looking for