NORTHARENGINEERING INTELLIGENT SYSTEMS
☰
SolutionsProductsSafety videosInsightsTechnology🇻🇳 VI🇬🇧 ENRequest a quote
🇻🇳VI🇬🇧EN

TECHNOLOGY 03 / VEHICLE INTEGRATION

CAN / I/O

Open CAN / I/O for integration and upgrades.

A safety system becomes practical when it can read vehicle state, drive lamps or buzzers, connect sensors and adapt to different platforms without a complete redesign.

●Technical update: 25.08.2026
NORTHAR CAN / I/O technology illustration
CAN / I/OTích hợp mô-đun / Modular integration
ARCHITECTURE OVERVIEW

A metric only matters when measured across the whole system.

NORTHAR separates sensing, processing, interface and output layers. CAN carries vehicle-state and device messages; digital or analog I/O connects simple signals, relays, lamps, buzzers and interlocks.

REFERENCE HARDWARE KIT

The hardware behind this configuration.

The kit is configured around the vehicle, voltage, warning zones and available interfaces. The image represents an OEM-neutral design; the final model and appearance may change after manufacturer selection.

  • Sealed modular ECU
  • CAN / CAN FD gateway
  • Isolated input/output module
  • Relay and fuse block
  • 24 V power module
  • Service cable, harnesses and sealed connectors
Reference hardware kit for CAN / I/O technology
OEM REFERENCE CONFIGURATION — NOT THE FINAL COMMERCIAL MODEL

DESIGN PRINCIPLES

Three layers behind the core capability.

Presented at architecture level; the final commercial configuration depends on the vehicle survey and safety requirements.

01

Modular interfaces

Each layer has a defined connector and role so a sensor or HMI can change without replacing the entire system.

02

Vehicle-specific signal mapping

CAN IDs, bus speed, voltage levels and I/O logic follow the documentation of each vehicle.

03

Separate warning from intervention

Operator warnings are different from automatic braking or motion inhibition; every intervention needs its own safety assessment.

TECHNOLOGY COMPARISON

No single sensor or protocol fits every application.

TechnologyStrengthTrade-offRole in NORTHAR
Discrete I/O

Simple, testable and compatible with lamps, buzzers and relays.

Limited diagnostics and increasing wire count as signals grow.

A foundational compatibility layer for legacy vehicles and accessories.

CAN 2.0

Widely used, robust and suited to compact control data.

Lower payload and data capacity than CAN FD.

Primary path for integration with existing vehicles.

CAN FD

Larger payload and a faster data phase when the entire network supports it.

Requires compatible controllers, transceivers and nodes.

Upgrade path for additional sensing, diagnostics and faster service.

Ethernet

High bandwidth for cameras and central compute.

More complex network architecture, security and connectivity.

Added in advanced configurations rather than replacing CAN and I/O everywhere.

UPGRADEABLE ARCHITECTURE

Extend one layer without replacing everything.

The roadmap is managed by hardware, software and per-vehicle configuration versions.

CURRENT01

Configurable CAN + I/O

Connect vehicle state, lamps, buzzers, HMI and sensors through vehicle-specific mapping.

UPGRADE02

CAN FD and service bootloader

Increase transfer capacity and support controlled software updates through a service port.

EXTEND03

Ethernet gateway

Connect cameras, edge computers or fleet systems when high bandwidth is required.

MAINTAIN04

Configuration versions and change log

Manage per-vehicle configurations, track releases and support rollback to a stable version.

TECHNICAL REFERENCES

Cross-checked with manufacturers and industry bodies.

STMicroelectronics — STM32H743/753 interfaces↗CAN in Automation — CAN FD↗

Evaluate CAN / I/O for your vehicle.

Share the vehicle model, dimensions, speed and blind zones. NORTHAR will propose a configuration and validation plan.

Talk to an engineer →