ROSINA

CANA-4 · the setup page

Set up from a phone

The module carries its own WiFi and its own page. Every setting an ECU could ask for is on it: the bit rate, the identifiers, the byte order, what each input is wired to and what it should read. No app, no cable, no laptop in the engine bay. These are the page's own screens, drawn by the firmware a unit runs.

The page

First run, then four tabs
The setup page's first screen: the question whether this module is one end of its CAN bus, with a diagram for each answer.
First run. One question before anything else: is this module one end of its bus? A diagram for each answer, and the terminator is set from it. After that, the page is four tabs.
The Inputs tab: four inputs, each with its sensor and its live reading.
Inputs. Each input's sensor, chosen from the presets, with its live reading. Calibrate by holding the sensor at a value you know and typing what it should read.
The CAN tab: bit rate, identifiers, byte order and rate, with the frame layout.
CAN. Bit rate, identifiers, byte order and rate, and behind them the whole frame table. The layout comes out as text and as a DBC file.
The Bus tab: the bus state, the counters and what to check.
Bus. The bus from the module's side: acknowledged frames, errors, other traffic, and what to check when it has stopped transmitting.
The Unit tab: firmware update, settings backup, units and the measured 5 V rail.
Unit. Firmware updates, a settings backup, display units, and the measured 5 V reference.

How it works

The EGA5 and EGA12 have no page. They are amplifiers: two calibration points in your ECU's own software, and the setup guides walk each platform through it.

Why one module reads on any ECU: CAN, plainly. The rest of the module: specs and wiring.