Go to documentation repository
Page History
...
Commands to manage the Peridect+ parent object are described in the table:
| Function menu command | Function |
|---|---|
| Reboot | Reboot the Peridect+ device |
| Switch to Active – Master | Control all outputs. External control isn’t possible in this mode |
| Switch to Active – Combined/Master | Control all system components according to the specified settings, control all outputs, and control all components with external commands |
| Synchronize time | Write the current server time to all Peridect+ controllers |
| Switch to Active – Slave | Control all system components according to the specified settings. All components can only be controlled using external commands |
| Switch to Active – Combined/Slave | Control all system components according to the specified settings and control all outputs. When an external command is received, the parent object of the Peridect+ integration module switches to the Switch to Active – Slave mode. If after a certain time the reception of external commands stops, the parent object of the Peridect+ integration module switches to the Switch to Active – Master mode. This mode allows the system to remain operational when the software is turned off |
The Peridect+ parent object can have the following states:
| Connection established | |
| Connection lost | |
| Unknown | |
| Active – Master | |
| Active – Slave | |
| Active – Combined/Master | |
| Active – Combined/Slave | |
| Service – Configuration | |
| Service – Storing data from LCP1 | |
| Service – Storing data from LCP2 | |
| Service – Logging input values and detector values | |
| Service – Logical links testing | |
| Invalid license |
| Note | ||
|---|---|---|
| ||
Events that occurred after the connection to the Peridect+ parent device was broken are not recorded to the device controller after the connection is restored. |
...