Update the point list, wiring reference and operating sequence together, recording which device and function belong to each changed input or output. Keep the previous and approved configuration references available to the service team. Test the affected signals and dependencies before handover so the physical installation, documentation and controller behavior describe the same arrangement.
Controls and interfaces
I/O controller for access equipment
An I/O controller receives equipment states and sends configured commands through its inputs and outputs. It connects compatible field devices to the access sequence, with wiring, electrical ratings and fault behavior defined for the installed equipment.
- Role
- Field equipment interface
- Points
- Project defined
- Electrical data
- Model documentation
Sequence first
An I/O controller connects field signals to the operating sequence.
Inputs receive states from connected equipment; outputs issue configured commands. Start with the actual signals and required behavior before selecting the controller.
How many inputs and outputs are needed?
List every source, destination and required state: detection, equipment feedback, commands and any project-specific signals. Count the required points and identify their electrical characteristics. Compare that list with the selected controller’s documentation before confirming capacity.
Can any reader or barrier be connected?
No. Match interface type, voltage, wiring and output ratings to each connected device. The I/O controller does not by itself establish credential compatibility or access permissions; those depend on the approved reader and access-system architecture.
Define behavior when a signal or connection is lost
Document timing, manual operation, interlocks and the required response to power, communication or device faults. Test the controller with the real connected equipment and approved wiring. Do not assume an input or relay alone provides a safety function.
Field connections
Give every input and output a clear role.
The controller connects field states and commands through the electrical interfaces supported by its model.
-
Inputs
Identify the connected device and the state each input represents.
-
Control sequence
Define how the system uses those states, including unavailable or fault conditions.
-
Outputs
Map each command to the intended equipment and its compatible electrical interface.
Technical Characteristics
| Specification | Details |
|---|---|
| Relay Outputs | 16 channels |
| Relay Rating | 2 A @ 24 VDC / 120 VAC |
| Digital Inputs | 16 channels |
| Analog Inputs | 8 channels (0–10 V) |
| Network | Gigabit Ethernet |
| Power Supply | 24 VDC / 120–240 VAC |
| Dimensions | 300 × 200 × 150 mm |
| IP Rating | IP54 |
| Operating Temperature | -20°C to 60°C |
Equipment details
From field inputs to equipment commands
The I/O controller links field signals to equipment commands. A point list records what enters the controller, what leaves it and what each state means.
| Component or use | How it fits the system |
|---|---|
| Inputs | A connected detector or other field device supplies a state for the operating sequence to use. |
| Outputs | The controller sends a command to connected equipment through the interface selected for that device. |
| Barrier example | A lane sequence can combine a detector input with a barrier command. The wiring and interlocks define how those signals interact. |
| Service record | Keep the point list and wiring diagram with the installation so a technician can trace each device and test its response. |
Configuration: Point count, current and voltage ratings, protocols, power, dimensions and environmental ratings depend on the selected model.
Equipment questions
Practical details for planning, operating and maintaining this equipment.
No. A command shows that an action was requested; confirming physical movement requires the feedback or observation defined for the installation. Identify which equipment states are available and how operators should interpret them. Test a normal action and the agreed failure cases rather than treating an output change as proof that the lane is open.
Project review
Engineer the field sequence before selecting the controller.
Share the point list, equipment interfaces, operating sequence, electrical services and fail-state requirements for review.