No memory reported by System State Publisher in DSM (cRIO-9067)

[MichaelBalzer]

HI all,

I'm running into an unexpected restart issue (the same problem I posted about several months ago - cRIO-9067 Real-time unexpected error restart (Hex 0x661). I noticed the status LED blinking 4 times, meaning the RT software was restarted twice due to an unexpected crash. The cRIO-9067 manual suggests it's a memory leak issue, and to check the memory usage. So I've gone to check the memory usage of the controller via the DSM, only to be greeted with 0 MBs and NaNs:

Is there any reason why the memory usage isn't being reported? Is there another way to check memory usage of the cRIO?

Given my experience with this particular cRIO I'm beginning to wonder if there's some deeper issue with it, possibly bad RAM or something else in hardware.

[Queue-tip]

Hey there,

I am assuming you have already reformatted and reinstalled software to the cRIO, as cited in the linked forum post. There is a chance that something was corrupted during the NI-RIO download and installation, in which case, you could reinstall RIO on your machine. 

Before that, I would try monitoring the CPU and memory programmatically as outlined in the following KnowledgeBase article:

'How Do I Monitor Available Storage Space on a LabVIEW Real-Time Controller?'

http://digital.ni.com/public.nsf/allkb/4BCAB18196B0728686256BDC0076921C?OpenDocument

This method is significantly more precise than the DSM method s the data is being generated and displayed through the RTOS rather than over the network (DSM executes on your host PC).

Hope this helps!

~ Q ~