Administrator Guide/IO: Difference between revisions
Created page with "= IO Settings = {{ChapterHeader|summary=Safety AI prefers dry contact to communicate with external parties and supports Event Gates IPIO as the default IO device. This section explains IO settings that can be defined with the Config Manager.}} == The Need == Once '''Safety AI''' detects objects in certain conditions and raises events it optionally needs to alert external parties that may benefit from this information. Among several communication techniques '''Safety AI'..." |
|||
| Line 30: | Line 30: | ||
* '''Mute Alert Input:''' '''Safety AI''' can send a predefined email notification to specificed users when the system is muted. To enable that feature, VIS must know which IPIO input is used for activating the stand-by (mute) function. | * '''Mute Alert Input:''' '''Safety AI''' can send a predefined email notification to specificed users when the system is muted. To enable that feature, VIS must know which IPIO input is used for activating the stand-by (mute) function. | ||
* '''Type ID:''' As of version 28 only IPIO is supported. | * '''Type ID:''' As of version 28 only IPIO is supported. | ||
{{AdminGuideNavigation}} | {{AdminGuideNavigation|next=Administrator_Guide/Events|previous=Administrator_Guide/Vislets}} | ||
Latest revision as of 10:50, 18 August 2026
IO Settings
Chapter Overview
Safety AI prefers dry contact to communicate with external parties and supports Event Gates IPIO as the default IO device. This section explains IO settings that can be defined with the Config Manager.
The Need
Once Safety AI detects objects in certain conditions and raises events it optionally needs to alert external parties that may benefit from this information. Among several communication techniques Safety AI chooses dry contact for integration with third parties and supports the Event Gates IPIO as the VIS integrated IO device.
In order to define the state of any output during any given event, an IO device must be registered in the first place. This can be done at the IO Modules page of the Config Manager.
Using IPIO
Thig guide does not cover how to manage the IPIO device but only focuses it's configuration to integrate with VIS. For details of IPIO administration see IPIO Users's Guide.
Managing IO Devices
IO Modules
Config Manager application has a page dedicated to IO devices. It lists current registered devices and allows to add new and alter existing ones.
Adding and Updating an IPIO
If an existing IPIO is selected it can be modified or else a new IPIO can be registered. To delete just click the bin icon next to each registered IPIO.
Required Information
Following information must be provided to register an IPIO:
- Display name: visible on video log and events page of the Config Manager.
- Username and password: valid credentials to log on a given IPIO.
- IP Address: make sure IPIO is accessible on the network.
- Port: TCP port IPIO uses to accept incoming requests. If you are not sure what port a given IPIO is using refer to the IPIO User's Guide.
- Heartbeat Pin: This setting tells VIS which output to use for the heartbeat.
- Red IL: For legacy purposes only - do not use, will be deprecated.
- Mute Alert Input: Safety AI can send a predefined email notification to specificed users when the system is muted. To enable that feature, VIS must know which IPIO input is used for activating the stand-by (mute) function.
- Type ID: As of version 28 only IPIO is supported.