Getting Started with IOcan¶

This guide is intended for users who install, wire, and configure the IOcan device. It focuses on safe initial setup, first power-up, and basic validation of communication with the ECU and transmission.

It does not cover mechanical installation, vehicle-specific wiring, or detailed configuration logic.

1. Intended Audience and Assumptions¶

This guide assumes the following:

• The user has practical knowledge of CAN bus, including:
  • twisted-pair wiring
  • termination rules
  • basic network topology
• For vehicle installations:
  • the mechanical installation is complete
  • the engine can start and idle with a stable RPM
• For bench testing:
  • a stable power supply is available
  • the supply can provide at least 12 V and 5 A to power transmission electronics

This guide focuses only on electrical integration and logical setup of IOcan.

2. Important Notices and Disclaimers¶

IOcan is intended for off-road use only.

IOcan will execute exactly what the configuration requests. Incorrect configuration may result in unexpected or unsafe behavior. The user is fully responsible for ensuring that the configuration is correct, validated, and tested safely.

Each installation is different. There is no universal configuration that is safe for all vehicles or transmissions.

The user is responsible for safety during testing.

Bench vs Vehicle Use

• Bench mode:
  • CAN communication testing
  • transmission diagnostics readout and erase
  • flashing transmission software
  • flashing IOcan firmware
  • modifying IOcan configuration (even without a transmission connected)
• Vehicle mode:
  • ECU integration
  • live engine interaction
  • drivetrain testing

Power and Wiring Safety

• In a vehicle installation, a 30 A fused BAT+ supply is recommended.
• On a bench, a current-limited power supply is strongly recommended.
• The transmission is a critical powertrain component.
• All vehicle wiring must be done to a high automotive standard.
• Temporary connectors, solder-less blocks, or WAGO-style connectors are not acceptable in a vehicle.
• Proper crimping is required. Soldering is strongly discouraged as it leaves the flux residues in the wires which causes the wires to corode and stiffen.

3. Minimal Required Interface to the Vehicle or ECU¶

The minimal interface required for IOcan to operate consists of five connections:

• KL30 / BAT+ (constant battery supply)
• KL15 / IGN / Wake-up
• KL31 / GND / Chassis ground
• CAN High
• CAN Low

These connections allow IOcan to:

• wake up
• communicate on the CAN bus
• read required signals from the ECU or other modules

Supplying Missing Signals

If required signals are not available on CAN, they can be supplied using IOcan inputs:

• Analog inputs
• 0–12 V or 0–5 V depending on input
• can be converted into analog-based signals
• can be processed as digital signals
• resistor divider mode allows multiple buttons on a single analog input
• Frequency inputs
• intended for speed-based signals
• engine speed
• wheel speed
• similar pulse-based signals

4. First Power-Up Using USB (Safe Mode)¶

The safest first power-up is performed using USB only.

• Connect IOcan to a PC using a USB-C cable.
• IOcan can be powered directly from the USB port.

In this mode, the user can:

• flash IOcan firmware
• modify and save IOcan configuration
• prepare the device before connecting vehicle or bench power

Transmission power is not active in USB-only mode.

This is the recommended starting point for all installations.

5. First Power-Up with Vehicle or Bench Power¶

After USB verification, IOcan can be powered from the vehicle or bench supply.

• Connect BAT+, GND, and KL15.
• When KL15 is asserted:
• IOcan becomes active on the CAN bus
• CAN communication is enabled
• transmission power and wake-up outputs are available

At this stage, the user should verify:

• IOcan is detected by the configuration tool
• CAN communication is present
• input signals behave as expected

This step confirms that wiring and basic configuration are correct.

6. CAN Bus Wiring Guidelines¶

• CAN wires must be twisted.
• Stubs should be as short as possible.
• The CAN bus must be terminated with 120 Ω resistors at each end.

Termination Rules

• IOcan has switchable internal 120 Ω termination.
• If IOcan termination is enabled:
  • IOcan must be installed at the end of the bus
  • only one additional termination resistor is used on the opposite end
• If two devices have internal termination enabled they must be installed at opposite ends of the bus

USB-only CAN operation may work in limited cases, but most ECUs require proper power and ignition to operate correctly. For reliable operation, all ECUs and modules should be fully powered.

Bench setups allow more flexibility, but vehicle wiring must be done with great care.

7. Transmission Connection and First Startup¶

Transmission wiring depends on the specific transmission being used. Detailed wiring information is provided on transmission-specific pages.

The minimal transmission connections are:

• power
• wake-up
• ground
• CAN bus

IOcan supplies both power and wake-up signals to the transmission. External relays are not required.

Base Configuration Requirement

Before the first startup:

• a base configuration must be flashed to IOcan
• this configuration defines:
• which CAN ports are used
• which transmission is expected

After first startup:

• transmission parameters should be visible in the datalogger
• no communication-related fault codes should be present

8. ECU Signal Integration and Validation¶

The user must either:

• select a supported ECU profile
• or configure CAN signal mapping manually

Common required signals include:

• engine RPM
• throttle position
• oil pressure
• brake pedal status

If required signals are missing or invalid:

• IOcan will detect the condition
• a fault will be set accordingly

Current Draw Check

With a full valve body installed and the engine off:

• observed current through IOcan should not exceed approximately 2 A

This serves as a basic sanity check.

9. Final Configuration and Next Steps¶

After basic communication and power-up are confirmed, the user must finalize the configuration:

• verify signal scaling and correctness
• configure shifter logic
• confirm engine parameter ranges
• test behavior in controlled conditions

Further documentation:

• configuration concepts
• supported transmissions
• vehicle-specific integration guides
• diagnostics and logging

This completes the initial setup process and prepares the system for detailed configuration and testing.