Why did PXI RT reboot itself?

[Claire_Reid]

Hi Ben,

I will try and find a reference that explains the RT error log. Hopefully will have an update soon!

[Claire_Reid]

Sorry for the delay. The Real-Time error logs are interpretted the same way as the LabVIEW internal errors. The important information (the call stack) is the same: CPP file, line number, cause and pointer crawl. The LV RT DAbort doesn't have a cause, which happens when a crash in lvrt.dll doesn't propagate a cause to the PharLaps RTOS. The additional information in the LV RT log is just configuration information for our developers to reference.

Please see the following links about LabVIEW CPP files:

LabVIEW Internal Errors (Failure in XXX.c / XXX.cpp at line YYY)

While Running LabVIEW, I Receive a Failure Message

[nate]

Thanks for letting me now about the crash log, but that still does not tell me much.

Also, I looked at the links to the memory check.  That is for drive memory, not RAM memory.  While the application does use the drive occasionally, it does not write very much information to it.  And the information that is written to it overwrites the previous information so I don't think that the issue is related to drive memory. 

[Claire_Reid]

Hey Nate,

It can't help to check the available storage space. If you could follow THIS KnowledgeBase article, at least we can eliminate areas that could be causing the problem.

In the meantime I will also be looking into your issue.

[Claire_Reid]

Also, are you running the VISA Find Resources vi?