Wire and test Axis inputs and outputs

Wire an input contact and a relay output with a light or buzzer, set up the ports in Cloud, test an output from Site controls, and fix an offline device.

Content updated Applies to version 2.7.0 Print view kalytera-cloud site-io axis inputs outputs wiring site-controls troubleshooting
Contents

After adding the Axis I/O device (Add an Axis I/O device to a Site), wire its ports, set them up in Cloud and test an output from Site controls.

Wire an input and an output

Follow the device's installation guide for terminals and ratings:

  • Input contact: wire a potential-free (dry) contact, such as a door contact or a key switch, between an input terminal and the device's ground. With the input's normal state set to open circuit, the input reports active when the contact closes; with closed circuit, when it opens.
  • Output with a light or buzzer: switch the light or buzzer through a relay rated for its voltage and current, with its own power supply. Never connect a load beyond the output's rating directly to the device.
  • For a door strike, let the device time each pulse, or use a strike with its own relock timer: a pulse that Cloud times stays on while the Site's connection is down.

Set up the ports

On the Equipment tab, select Settings on the device.

  1. Give the port a recognizable name, such as Entrance buzzer, and select Save. Turn Use in Cloud off for a port Cloud should leave alone: it takes no On or Pulse, though Off still works, and as an input it raises no alarms.
  2. For an input, select Edit beside Alarms: and choose When should this input raise alarms?: Not an alarm source, Follows arming groups or Always active. Set Alarm when, the Alarm severity and Ignore changes shorter than (milliseconds, 0–60000), and select Save alarm settings. To send its alarms to the Site's alarm receiving centres, also set Alarm receiving centre zone (1–999) and Partition (0–99). How inputs join arming groups is in Cloud arming and site controls.

For a device added directly, Device settings changes a port on the device itself: Name on the device, Type, Active when, When it's on (Hold or Pulse, with Pulse length (seconds, 1–65)) and Resistor configuration. Before changing a port, turn an input's alarms off, or switch an output off and turn its Use in Cloud off. When the type changes, tick I've checked what's wired to this port. Then select Save to the device. Through a Bridge, change ports on the device.

When a port changes on the device, Cloud takes the new setup at its next reading, and arming groups and output policies that use the port must be approved again. A port switched between input and output reads Unknown: for a direct device, select Use the device's type in Device settings and turn Use in Cloud on again; through a Bridge, set the port back on the device. New device credentials go under Connection and sign-in > Save connection for a direct device, or Device sign-in > Change credential through a Bridge.

Test an output from Site controls

The outputs' buttons sit under their device in the I/O devices list, under Site controls in Monitor, and in an alarm's detail.

  1. Check the output's state, On or Off, and the device's Updated time.
  2. Select On. The command is sent at once, without a confirmation. It shows Requested; waiting for the Site, then Sent; waiting for a result, and finally Output read-back confirmed: On. The light or buzzer should switch on.
  3. Select Off; it reads back Output read-back confirmed: Off.
  4. For a timed switch, enter the seconds next to Pulse and choose Timed by the device, up to 65 seconds, or Timed by Cloud, up to 3600. A pulse timed by the device ends even if the connection drops, and Cloud also switches the output off soon after as a safeguard. An output set to pulse on the device shows a single Pulse button with its length.

If the result reads Result unknown or The command result is not confirmed, look at the light or buzzer, select Check status, and send the command again only if needed: Cloud never repeats it on its own. Automatic stop unconfirmed: check the output. means Cloud keeps trying to switch it off, and raises an Output stop unconfirmed alarm.

When the device shows offline

A device reads Online while it reports no problem and was read in the last 30 seconds, and Offline otherwise. The Site's Overview lists it under Offline equipment. If one of its inputs raises alarms, Cloud also raises an I/O module offline alarm.

  • Through a Bridge: first check the Bridge Agent under Cameras > Devices, on the Bridge Agents card.
  • Otherwise open the device's Settings, select Refresh devices, and read the code after Connection problem:.
Problem shownWhat to check
device_transport_unavailableThe address, the network and, over HTTPS, the device's certificate.
device_operation_timed_outThe device answers too slowly or not at all: its power, cable and address.
device_authentication_failedThe device username and password, and that the device allows Digest authentication.
physical_identity_changed or physical_identity_in_useA different device answers at the address, or this device is in service elsewhere.
device_proof_unavailableThe device reported no serial number or I/O ports: its firmware and the account's rights.

A command on this device has an uncertain outcome. does not block new commands. Once the device reports again, an administrator can select Resolve….