11 System States and Conditions for the Vision System ToC Previous Next

11.6 Structuring of Vision System State information ToC Previous Next

11.6.7 Nonscheduled Time (NST) ToC Previous Next

The vision system is not working because no production was scheduled. This also covers things like operator training on the system.

Example:

An application specific extension of the base states:

E10 vendor / application specific extension  
PRD Acquisition ACQ CAM A
        ACQ CAM B
    Processing  
SBY Waiting for PREPARE  
    Waiting for START  
ENG Recipe Editing  
    Calibration  
SDT Maintenance  
    Cleaning Optics A
        Optics B
UDT Software Related Error  
    Hardware Related Error  
NST Powered Off  
    Operator Training  

If the system is in state “ACQ CAM A” the current path would be “PRD/Acquisition/ACQ CAM A

The tree-like E10 scheme may be extended to the right by getting more specific on the current state of action the system is performing. As in the original E10 scheme, at every time the system has to choose exactly one state (rightmost field of a branch) it is currently in. To be compatible to clients understanding only the basic E10 states the system has to give the “/” separated path running along the branch of that tree starting from the base E10 state to the current state.

The same scheme should be used to structure error states. Every error information carries such path information to enable generic clients without deeper application knowledge to get a basic understanding of the possible error cause. The following basic error paths shall be used. As above this model may be expanded to the right as needed.

Table 138 – Basic error paths

UDT Software Related Error  
    Hardware Related Error Computing Unit
        Sensor Unit
        Controller Unit
        Lighting Unit

The system can only be in one specific state (leaf of the tree), although errors can occur in more than one leaf simultaneously. In this case the system still has to select exactly one system state to be published.

There are two different approaches possible:

  1. The system selects the most severe error and publishes its path as the current system state.
  2. The system truncates the path to the last element common for all active errors. The system may select one approach fitting to the current application.

Example:

A system is in an Error State and there are currently two errors active. The system uses application specific extended error classes:

  • UDT/Hardware Related Error/ Sensor Unit/Camera A/Fan Fail
  • UDT/Hardware Related Error/Lighting Unit/LED A/Over Temperature

Possibility 1:

The system decides that an over temperature is the most severe error and publishes “UDT/Hardware Related Error/Lighting Unit/LED A/Over Temperature“ as its system state.

Possibility 2:

The system publishes the truncated path “UDT/Hardware Related Error” as its current system state.

Previous Next