Hanwha Vision IO Box Trigger

Trigger IO ports on a Hanwha Vision SPM-4210 device.

Overview

The Hanwha Vision IO Box Trigger node writes data to a Hanwha Vision SPM-4210 device over the network. This node makes it easy to build common use cases such as triggering alarms, controlling devices, etc.

Inputs & Outputs

  • Inputs : 1, Media Format : Raw Video
  • Outputs : 1, Media Format: Raw Video
  • Output Metadata : None

Pipeline usage

Place this node after the analytics or event node referenced by trigger. follow keeps the selected output synchronized with the condition; activate or deactivate acts when the condition becomes true and can optionally pulse. Confirm port numbering and active-open/active-closed behavior against the SPM-4210 wiring before deployment.

Properties

PropertyDescriptionTypeDefaultRequired
triggerDrive an IO port with the value of this condition.trigger-conditionnullYes
actionAction to take on the remote IO port when the trigger condition becomes true. When set to 'Follow condition', the port is activated or deactivated as the condition becomes true or false, respectively. Options: Follow condition (follow); Activate (activate); Deactivate (deactivate).enumfollowYes
io_portComma separated IO port numbers to act on. Refer to your device's documentation for supported IO port listing.stringnullYes
pulse_durationDuration of Activate or Deactivate pulse in seconds. 0 means no pulse. Only used when the action is set to 'Activate' or 'Deactivate'.number0No
ip_addressIP address of the Hanwha Vision SPM-4210 device.stringnullYes
usernameAuthentication usernamestringnullYes
passwordAuthentication passwordstringnullYes
use_httpsWhether to use a secure HTTPS connection for the request.boolfalseNo
insecureWhether the TLS certificate used for the HTTPS connection should be verified. Conditional on use_https being true.boolfalseNo
output_typeOutput type. Options: Active Closed (closed); Active Open (open).enumclosedYes
debugDebugboolfalseNo

Output Metadata

Node does not insert any output metadata; upstream metadata continues through the pipeline


Did this page help you?