Table Of Contents

Module Operating Modes

    Last Modified: May 15, 2018

    • The module runs in Unprogrammed Mode when you first install and power on the module.
    • While the User Program is downloading, the module runs in User Program Download mode.
    • After a successful download, the module changes to Verification Mode.

      In Verification Mode, the User Program is running normally.

    • Perform validation procedures on your system while in Verification Mode.
    • Change the mode to Operational Mode from your project in LabVIEW once validation of the system is complete.

    The module will run in Operational Mode until one of the following things happen:

    • You change the mode back to Verification Mode in LabVIEW.
    • You cycle external power to the module.
    • User-configured diagnostics or automatic self-diagnostics trigger Fail-safe Mode.

    The module FPGA stops the User Program when the module changes from Verification Mode to Operational Mode or from Operational Mode to Verification Mode. If you enable auto start, the User Program will restart after the module changes modes. If you do not enable auto start, you will need to restart the User Program from LabVIEW.


    Latched faults persist when the module changes operating mode. For more information on fault latching, refer to the Fault Latching section.

    The RIO Scan Interface monitors and returns the module operating mode. You can view or change the operating mode in the Properties window in the LabVIEW project or with the Invoke Node in your LabVIEW VI.

    Table 1. Module Operating Modes
    Mode What Is Happening What to Do Next
    Unprogrammed Mode
    • Hardware state out of the box
    • User Program is not written to the module
    • Vsup/Status LED flashes
    • Develop the User Program in the Functional Safety Editor
    • Download the User Program to the module
    User Program Download Mode
    • User Program is downloading to the module
    • Vsup/Status LED flashes
    • Verify the mode updates to Verification Mode
    • Verify the Build Number and the Program GUID update
    Verification Mode
    • User Program has downloaded to module and is running normally
    • User Program requires verification
    • Vsup/Status LED flashes
    • Use this mode to perform necessary verifications based on system design
    • Monitor system for detected faults
    • Set module to Operational Mode
    Operational Mode
    • User Program is running on the module
    • Vsup/Status LED is on
    • Perform maintenance and proof tests as determined by your safety plan
    • Monitor system for detected faults
    Fail-safe Mode
    • All outputs are de-energized
    • User Program stops running
    • Vsup/Status LED flashes
    • Internal Fault LED flashes
    • LabVIEW returns fault status information
    • Respond to fault as determined by user safety plan
    • Cycle external Vsup to the module
    • Restart the User Program
    • Return the module to Operational Mode as defined by your safety plan

    Recently Viewed Topics