LabVIEW 2013 SP1 Real-Time "Scheduler Assertion Error: C0000005"

[gsti]

Hello,

our real-time system crashes after a couple of days with the following message at the console:

Scheduler Assertion Error: C0000005

Interrupt Disabled. Scheduler Enabled. If you have enabled serial console error

logging, detailed error info could be found in that console. Contact National Inst

ruments with the output of the serial console. Crash log

or memory dump cannot be created for this type of error.

We use the real-time software on a generic desktop PC

(ASUS Z87-Plus mainboard, i7-4770K, 4GB RAM, Intel SSD, 6 ethernet adapters)

with a FPGA board PCIe-7842R.

The first ethernet adapter is disabled,

the second adapter with DHCP enabled (192.168.0.xxx) serves as interface to a windows 7 based display computer,

adapter 3-6 use static IP addresses in a different subnet (192.168.200.xxx)

The communication between CPU and FPGA board uses Target-Host DMA and generates an interrupt every msec.

The system load is about 20%.

Any ideas to isolate the problem?

How can we enable serial console error logging?

Thanks for your help

Gerhard

[Elisa_D.]

Hello Gerhard,

the console error logging is actually for cRIO controllers and not RT desktops. When you get the error, are you connecting or disconnecting any hardware?

Can you run a simple program on the RT and see if the error is reproducible? Or modify the existing program to make it error out faster?

It probably depends on the code which you are running. Could you explain briefly what you have programmed?

Thank you

[AbeP]

Do NI PXI's have this ability too?  I also receive the message after a stack overflow on my NI PXIe-1065:

"If you have enabled serial console error logging, detailed error info could be found in that console."

And currently trying to figure out if I can create this log and view the results.

thanks,

[Bauer_CT]

I realize this thread is old, but I have the same problem and haven't found an answer yet.

I'm very eager to find the detailed error info that could be found in that console. 

I'm using a PXI RT controller. The crash seems to be related to dynamic/asynchronous VI calls but it is very sporadic.

If there is in fact no such console available for PXI RT then how am I supposed to work with NI Tech support to find out why their controller is crashing? I can't just guess and check programming changes until something doesn't crash. I thought it was working when it didn't crash all day Tuesday but then I got one yesterday afternoon after a few hours of running. And then one this morning after a few minutes of running.