CAN function reference
Your device has two independent CAN ports, CAN1 and CAN2. Each port is given one job by the CAN function setting:
Settings template → Hardware → CAN1 or CAN2 → CAN function ID → Add → CAN function
The option you pick answers two questions at once:
What the port does — read vehicle parameters, download tachograph files, capture raw traffic, and so on.
When the port is active — always, or only while a chosen signal is present.
Outside its trigger the port is switched off completely, which is how you keep the device from draining the vehicle battery while it is parked.
Recommended starting point: CAN_base_b on IN5. This applies to heavy vehicles too — see J1939 below.
For the step-by-step configuration walkthrough, see CAN bus set up. For the CAN scripting API, see CAN BUS functions.
1. Choose a function by what you want to achieve
I want to… | Use this function | Also needs |
|---|---|---|
Read parameters from a car, van or light truck (fuel level, RPM, mileage, doors…) | CAN_base_b | A Vehicle model from the CAN database |
Read parameters from a truck, bus or other FMS/J1939 vehicle | CAN_base_b with a J1939 / FMS profile — see the note below | A Vehicle model from the CAN database |
Download DDD files from a smart tachograph, and read live driver data | Tachograph read | Tachograph settings, company card, connection to VU plug C |
Capture raw CAN traffic so a new vehicle can be added to the CAN database | CAN dump read (or CAN dump read (ACK)) | Tachograph application configured as file server |
Read agricultural implement data | ISOBUS | Guidance display with Task Controller, ISOBUS access key |
Handle a custom protocol yourself from a device script | Script access | A script using the CAN API |
Switch the port off | Sleep | — |
2. Choose when the port is active
Most functions come in several variants that differ only in the activation trigger.
Trigger in the option name | Port is active when… | Typical use |
|---|---|---|
always | Permanently, from power-up | Vehicles where the CAN bus never sleeps, or where you must not miss data |
on IN5 | Input 5 is present — normally wired to ignition | The usual choice. Reads while the vehicle is in use, sleeps while parked |
on IN7 | Input 7 is present — internally wired to engine running (from power supply voltage) | Stricter than IN5: only while the engine actually runs |
on Signal1 | Static signal S1 is set | Remote or conditional control — see below |
(Sleep) | Never — the port stays off | Disabling an unused port |
About Signal1. S1 is not a physical input. It is a virtual signal you set yourself — from a scenario in the logic template, from a server command, or by SMS. Use it when the CAN port should follow your own condition rather than a wire. For example, you can keep a dump capture switched off until you remotely enable S1 on a vehicle that reported a fault.
Battery note. Prefer a triggered variant over always. A port left permanently active keeps the transceiver powered and, on some vehicles, keeps the bus itself awake.
3. Function reference
CAN_base_b — vehicle parameters
The standard way to read parameters from any vehicle that has a profile in the CAN database: cars, vans and light commercials, and also trucks and buses through a J1939 / FMS profile. This is the recommended function for almost every installation.
Requires a Vehicle model (CAN file) selected under Hardware → CANx → Vehicle model. The model tells the device which identifiers carry which parameters.
The bit rate comes from the Vehicle model and is confirmed against live traffic before use, so you do not set it manually.
Whether the device transmits anything is decided by the Vehicle model. Most models are listen-only. Models that read request-based parameters send diagnostic requests, and those require the device to be wired directly into the vehicle.
Choose the parameters you want reported under Data recording → Simple or Extended.
If your vehicle is not in the CAN database, capture a CAN dump read instead and send the file to support so the model can be built.
Variants: CAN_base_b on IN5 · on IN7 · always
J1939 — trucks, buses and heavy vehicles
Reads standard FMS / J1939 parameters. No Vehicle model is required.
Recommended: use CAN_base_b with a J1939 / FMS profile instead.
The CAN database contains J1939 and FMS profiles, and CAN_base_b decodes J1939 messages directly from them. For a heavy vehicle this is the better choice:
No bit rate guesswork. The profile carries the bit rate and the device confirms it against live traffic. With the dedicated J1939 function you must pick 250 or 500 kbit/s yourself, and the wrong choice yields no data at all.
More parameters. You get the standard J1939 content plus anything else the profile describes for that vehicle, rather than a fixed built-in set.
Updated without a firmware change. Profiles are maintained in the CAN database, so added parameters and fixes reach you by selecting an updated Vehicle model.
One way of working. Same configuration flow as every other vehicle — pick a Vehicle model, then pick your parameters.
Keep the dedicated J1939 function for vehicles where no suitable profile exists yet, or where you deliberately want a read that does not depend on a profile. If you need a profile for a vehicle that has none, capture a CAN dump read and send it to support.
If you do use the dedicated function:
Pick the variant that matches the bus: 250 kbit/s or 500 kbit/s. The device does not switch between them, so the wrong choice means no data at all.
Listen-only: the device never transmits.
Variants: J1939 (250kbit) on IN5 · on IN7 · always — J1939 (500kbps) on IN5 · on IN7 · always
Tachograph read — DDD download and live driver data
Downloads tachograph files (VU and driver card) remotely and reports live tachograph data such as driver IDs, activity states, odometer and VIN.
Connect the CAN port to the VU plug C CAN bus. On FMS 500 Tacho, CAN2 is reserved for the tachograph and cannot be used for vehicle parameters.
A company card must be inserted at the card server, and the tachograph file server settings must be filled in (address and port, default port 7511).
The bit rate is detected automatically — 250 or 500 kbit/s.
The device holds a diagnostic session with the tachograph, so it does transmit on this bus.
Variants: Tachograph read (always) · on IN5 · on IN7 · on Signal1
CAN dump read — capture raw traffic
Records roughly 20 seconds of raw CAN traffic into a .can file and delivers it to the tachograph application, where you can forward it to support. This is how an unsupported vehicle gets added to the CAN database.
The bit rate is scanned automatically — nothing to configure.
Capture repeats until you change the setting back, so remember to restore the normal function afterwards.
Best results are obtained with the engine running. When sending the file to support, include vehicle brand, model, year, and the mileage and fuel level shown on the dashboard.
Two variants, and the difference matters:
Variant | Behaviour on the bus |
|---|---|
CAN dump read | Fully passive. The device listens only and does not even acknowledge frames, so it is invisible to the vehicle. Use this by default. |
CAN dump read (ACK) | The device joins the bus normally: it acknowledges frames and can send the diagnostic requests defined by the selected Vehicle model. Use it when the parameters you need are request-based and do not appear in a passive capture. Requires a direct wired connection — it cannot work through a contactless reader. |
Variants: CAN dump read on Signal1 · on IN5 · on IN7 — CAN dump read (ACK) on Signal1 · on IN5 · on IN7
ISOBUS — agricultural implements
Reports operating values from ISO 11783 implements, up to three at a time, on sensor IDs 0xEFF8, 0xEFF9 and 0xEFFA.
Fixed 250 kbit/s.
The device must be on the same bus as the guidance display and the implements, and the display must have the Task Controller function enabled. Devices supporting ISOBUS version 3 or later are required.
The device is a passive listener in the sense that it requests nothing itself — the values it reports are the ones the Task Controller already asks for.
ISOBUS must be unlocked with a functionality access key.
Variants: ISOBUS on Signal1 · on IN5 · always
Script access — custom protocols
Hands the port over to a device script. The script sets the bit rate, installs filters, and reads or writes frames through the CAN scripting functions.
Nothing is decoded automatically — no vehicle parameters are produced by the device itself.
This function must be selected before any CAN scripting will work on that port.
What appears on the bus is entirely up to your script.
Sleep — port off
The port is shut down: no reception, no transmission, transceiver disabled. Use it for a port you are not using, or as the parked state of a vehicle.
4. What the device puts on the bus
Worth checking before installation, especially on vehicles where an actively transmitting device is not acceptable.
Function | Does the device transmit? |
|---|---|
Sleep | No — the port is disabled |
CAN dump read | No — listen-only, frames are not even acknowledged |
J1939 (250kbit / 500kbps) | No — listen-only |
CAN_base_b | Depends on the Vehicle model: listen-only unless the model uses diagnostic requests |
ISOBUS | Yes — acknowledges frames, but requests nothing |
CAN dump read (ACK) | Yes — acknowledges frames and may send diagnostic requests |
Tachograph read | Yes — runs a diagnostic session with the tachograph |
Script access | Whatever the script does |
5. Every option at a glance
Option | Function | Active when |
|---|---|---|
CAN_base_b on IN5 | Vehicle parameters | IN5 present |
CAN_base_b on IN7 | Vehicle parameters | IN7 present |
CAN_base_b always | Vehicle parameters | Always |
J1939 (250kbit) on IN5 | FMS / J1939, 250 kbit/s | IN5 present |
J1939 (250kbit) on IN7 | FMS / J1939, 250 kbit/s | IN7 present |
J1939 (250kbit) always | FMS / J1939, 250 kbit/s | Always |
J1939 (500kbps) on IN5 | FMS / J1939, 500 kbit/s | IN5 present |
J1939 (500kbps) on IN7 | FMS / J1939, 500 kbit/s | IN7 present |
J1939 (500kbps) on always | FMS / J1939, 500 kbit/s | Always |
Tachograph read | DDD download + live tacho data | Always |
Tachograph read on IN5 | DDD download + live tacho data | IN5 present |
Tachograph read on IN7 | DDD download + live tacho data | IN7 present |
Tachograph read on Signal1 | DDD download + live tacho data | S1 set |
CAN dump read on IN5 | Passive raw capture | IN5 present |
CAN dump read on IN7 | Passive raw capture | IN7 present |
CAN dump read on Signal1 | Passive raw capture | S1 set |
CAN dump read (ACK) on IN5 | Raw capture, device active on bus | IN5 present |
CAN dump read (ACK) on IN7 | Raw capture, device active on bus | IN7 present |
CAN dump read (ACK) on Signal1 | Raw capture, device active on bus | S1 set |
ISOBUS on IN5 | ISO 11783 implement data | IN5 present |
ISOBUS on Signal1 | ISO 11783 implement data | S1 set |
ISOBUS always | ISO 11783 implement data | Always |
Script access | Port controlled by script | Always |
Sleep | Port off | Never |
Which triggers exist for which function
Not every combination is offered. Blank cells are not available.
Function | always | on IN5 | on IN7 | on Signal1 |
|---|---|---|---|---|
CAN_base_b | ✔ | ✔ | ✔ |
|
J1939 (250kbit) | ✔ | ✔ | ✔ |
|
J1939 (500kbps) | ✔ | ✔ | ✔ |
|
Tachograph read | ✔ | ✔ | ✔ | ✔ |
CAN dump read |
| ✔ | ✔ | ✔ |
CAN dump read (ACK) |
| ✔ | ✔ | ✔ |
ISOBUS | ✔ | ✔ |
| ✔ |
Script access | ✔ |
|
|
|
Sleep | ✔ |
|
|
|
If you need a combination that is not listed — ISOBUS on IN7, for example — contact support.
6. If you are not receiving data
Check the function matches the vehicle. Almost every installation should use CAN_base_b with a Vehicle model, including heavy vehicles. If you are using the dedicated J1939 function, the wrong bit rate produces nothing at all.
Check the trigger. With on IN5 or on IN7, the port is off unless that input is present. Confirm the input is actually wired and reported.
Check the Vehicle model. With CAN_base_b, no model means no parameters.
Check the parameters are selected under Data recording.
Check the physical connection. CAN1 is the orange pair, CAN2 the yellow pair; either port can be connected to either CAN line of the vehicle.
Values look wrong rather than missing? Parameters are reported in FMS protocol units and may need a coefficient to match the dashboard reading.
Still nothing — capture a CAN dump read and send the file to support with the vehicle details.
Related pages
CAN bus set up — step-by-step configuration walkthrough
CAN bus dump file — how to capture and send a dump
CAN BUS functions — CAN scripting API reference
CAN-bus configuration — physical connection and logic template
Why CAN parameter value differs from the value on the vehicle dashboard?