RT 9 reboots when creating a probe

[AnthonV]

Hi, I've had RT 9 reboot itself many times today in debug mode.  A reboot is always immediately preceded by me creating a probe on a wire.  It doesn't seem to matter what type of wire (even something as simple as an error cluster).  It doesn't always happen though, say about 30% of the time when creating a probe.

Even if the probe is created before deploying, once it reaches the probe it will reboot.

I am running RT 9 on a desktop PC.

Any help will be appreciated!

Thanks.

[George_P_Burdell]

AnthonV-

Please take a look at the KnowledgeBase Article listed below and make sure your PC is compatible with running the RTOS.  This seems like a compatibility issue.  Please post back here with the results and if this is the reason for this strange behavior.

KnowledgeBase 4LEHIQ4N: How Can I Test My PC for Compatibility with LabVIEW Real-Time or LabWindows/CVI Real-Time for Desktop ETS?:
http://digital.ni.com/public.nsf/allkb/9209361E17708D548625744A007FF353?OpenDocument

[AnthonV]

Thanks George, I'm sure the PC is compatible as this never happened using 8.6.1.  Its only since I upgraded to 9 that this behaviour started.  I have managed to reduce its frequency by waiting for things to 'settle' (that is - wait until the code has run for about 30 seconds) before I create the probe.  If the probe is created while editing, the crash happens more often than not when the code starts running.

[George_P_Burdell]

AnthonV-

I have a few more questions for you about your system and setup:

1. So your PC does pass this test?
2. How are you viewing your code running on your RTPC? 
3. Is it from a remote front panel, or connected to your development machine and watching shared variables? 
4. Are you modifying this code on your development machine and deploying it to your RTPC?

[AnthonV]

Hi,

1) Yes the PC passes the test, although I am using a PCI NIC as the built-in network chipset isn't supported on this DELL quad core.

2,3,4) Ultimately this RTPC will run headless and when we run in this manner we interface to it using TCP packets from a HMI (also programmed in LabVIEW).  But while we are ironing out bugs we are using the remote front panel with the diagram visible so that we can probe wires if required.  We still don't trust shared variables (in real-time applications) so there is none of that in the code.  At milestones we 'deploy' the code to the RTPC so that it will execute at startup, but mostly we run it by pressing the execute arrow.

[George_P_Burdell]

AnthonV-

If you use simpler code, such as a case structure connected to a Boolean button that will probe when it is pressed, does this same behavior occur?  Is this consistant with other RT systems you have running LabVIEW 2009?

[AnthonV]

No doesn't happen in simple cases.  I think it might have to do with probes on large datastructures when all cores are running at 100%, and even then it is a sporadic event.  Thanks for the help so far - I'll try to get a repeatable case and then repost here.

Cheers

[George_P_Burdell]

AnthonV-

That would be very beneficial in assisting us with diagnosing your issue.  From there we can help you figure out what exactly is happening.