major scan engine fault handling on cRIO

[MarkCG]

In the NI Scan Engine Faults help page http://zone.ni.com/reference/en-XX/help/371361H-01/lvioscanhelp/faults/  it is mentioned that

"

Note  Some I/O hardware drivers implement fault handling behavior in response to major faults. Refer to the specific hardware documentation for information about fault handling behavior.

"

Where , specifically, is this info found? I'm curious what actually happens when a major fault occurs. I'd like to configure my scan engine faults so that a missing or unexpected cRIO module on the cRIO chassis will cause the outputs the go to a safe state. I can do a lot and accomplish this with RT side programming but I'd like to know what I can do with the built in fault handling capabilities of the scan engine before doing that.

Anyone know?

[natasftw]

It wouldn't make much sense for that phrase to apply to the situation you're discussing.  It's talking about modules having error handling for internal faults.  Why would you want NI to determine how to handle your application every time you don't have another module inserted?  This would mean you'd never be able to move the module to another slot.  You wouldn't be able to use an individual module. 

If you want to handle "faults" specific to your system, you'll need to handle those.  If you want to know more about the ones referenced in the blurb you cited, go check the individual module's spec sheet.

[MarkCG]

if you go into the scan engine configuration menu for your real time target you'll see you can define the fault level for a number of error codes. Many of those error codes are of the form "a module is expected in slot X but no module was found". By default the fault level seems to be set to "minor".

So not really specific to the module at all. Those error codes are referring to a mismatch between the scan engine as configured in your project and deployed, and the physical modules as they are in the chassis.

You can get a list of these scan engine faults programmatically or view them through the distributed system manager... I assure you what I am talking about (scan engine faults) do not in any way prevent you from changing module assignments. You can test it yourself by yanking a module when the scan engine is running.

Let me re-phrase the question... What state does the scan engine go to when it encounters a "major" fault?