What is an IP I/O Module?
An IP I/O Module or Ethernet Relay is a network-enabled digital input/output device that allows users to connect and control inputs, outputs, or both over the internet or their IT network.
Such IP I/O modules enable the integration of 3rd party hardware devices with Nx Witness (for example, door sensors, alarm panels, fire systems, locks, etc.). Sensors such as a door switch, smoke detector, IR detector, or glass break detector (used for triggering an alarm event) can be connected as inputs. Output ports can be connected to control devices or relays, for instance, to open/close doors or turn on/off lights upon alarm.
Supported I/O Modules
These supported I/O modules will appear in the Resource Tree and can be added to any layout (requires an I/O license):
- Advantech ADAM 6050 Ethernet Remote I/O
- Advantech ADAM 6052 Ethernet Remote I/O
- Advantech ADAM 6060 Ethernet Remote I/O
- Axis A9161 Network I/O Relay Module
- AXIS P8221 Network I/O Audio Module
Note: The models listed above are confirmed to work, but it is likely that more models are compatible since they use the same API. Please confirm with your Advantech or Axis supplier to ask which models share the same codebase, and most likely will work, before applying them in a production environment.
To Add and Configure an IP I/O Module in Nx Witness:
- Plug the device into your network on the same subnet as your Server(s).
- Supported I/O Devices will be automatically discovered and shown in the Resource Panel.
- To enable the device, you will need an I/O License, so make sure you have the proper licenses activated before continuing below.
- To enable an I/O device, right-click on the device to open the Settings dialog and toggle the Use License switch to green.
- In the Recording tab, operators can enable and schedule recording of audio. This tab is only shown if the I/O device supports audio.
- In the I/O Ports tab of the I/O Module settings, operators can define the Type of connection on each port (Input/Output), the default state (Open/Closed), can add custom names on each port, and can define the standard pulse time in ms for configured outputs.
- If you are using multiple Inputs and Outputs from the device, we recommend checking the "Enable tile interface" in the lower left-hand corner of the dialog. This will generate a responsive tiled interface for the I/O that can be displayed in the Viewing Grid.
The compatible I/O devices will make it possible to create rules in the Nx Desktop interface to utilize all the capabilities of the I/O device. The inputs can be used as an Action and the outputs as the Events in the Nx Rules Engine.
I/O on the cameras
Some camera models have an input, an output, or both on the device itself. A Professional license is sufficient for these I/O connections. To confirm if these I/O can be used, they must be activated under Relays in ONVIF Device Manager and available in the Nx Rules Engine.
Other Ethernet relay options
There are devices available that cannot be added to Nx Witness and displayed in the viewing grid, but can be used in conjunction with Nx Witness.
Such devices are called Ethernet Relay units and can usually be controlled by sending an HTTP request as an action to the Ethernet Relay units to trigger an output of the Ethernet relay unit. Also, it is often possible to send an HTTP request from the Ethernet Relay Unit to Nx Witness, where it will be received as a Generic Event to trigger any Action in the Nx Rules Engine.
Many Ethernet Relay units in the market can be controlled through a Generic Event event and associated Action, such as GJD IPAnything or Allnet IP Control Units (setup is shown in this video).
If you have any questions related to this topic or you want to share your experience with other community members or our team, please visit and engage in our support community or reach out to your local reseller.
Is it possible to use an input to validate a schedule for a rule?
IE input opened and time period of schedule valid then carry out Analytic event/https request
Use case: Alarm system disarmed with an output turned on (wired into the input on an IO) rule for line crossing detection invalidated by the state of the input.
Alarm armed, input closes and rule becomes valid line crossing used to trigger third party notification/alarm system via output.
My apologies for the late reply, but the answer is no if you want to do it via the Nx Desktop client.
The answer is yes if you do it through the API with the help of the /ec2/saveEventRule but it would require a programmer to write a small program to run the various API calls.
Rule validation is something that we are desperate to be able to do.
I have been told that it is in the road map? Can you confirm?
For 4.1 it isn't scheduled, nor is it scheduled for 4.2.
If you like such feature, please inform your reseller about it or submit the idea to our community in the New Feature Ideas section.
Article is closed for comments.