_White_Background_square_1920px.png?width=256&height=96&name=FLEETWATCH%20Fleet%20Information%20Technology%20by%20S%26A%20Systems%2c%20Inc%20(06_28_2021)_White_Background_square_1920px.png)
Fleetwatch FMS · Vehicle Modules
JX Odometer Configurations
The JX55 and JX200 modules read the odometer from the vehicle’s data network. The configuration number set on the JX tells it which network message to read the odometer from, and whether the JX odometer can be set to match the dashboard.
Read-Only vs. Settable
|
Read-only
The JX reports exactly what the vehicle’s ECM reports. It can’t be adjusted to match the dashboard, but it doesn’t drift.
Configs 017, 019, 049, and J1708 config 00
|
Settable
An odometer value can be entered into the JX to match the dashboard. Small differences can build up over time, so it needs re-calibrating with the MR55 at each PM.
Configs 929 (preferred), 161 and 673 (legacy), and J1708 config 97
|
Recommendation
Use Configuration 017 (J1939) or Configuration 00 (J1708) unless a specific policy requires the JX to match the dashboard display. If a settable J1939 config is needed, use 929. Configs 161 and 673 are legacy and should be replaced with 929 whenever possible.
J1939 Network Configurations (JX55 and JX200)
| Config | Odometer source | Details |
|---|---|---|
| 017 | SPN 245 Total Vehicle Distance PGN 65248 (0xFEE0) |
Recommended
Read-only
The JX odometer can’t be adjusted to match the dashboard.
If the ECM is replaced, this value may reset to 0. Program the life-to-date odometer back into the new ECM whenever the engine manufacturer allows it. If that’s not possible, switch the JX to config 929 so its odometer can be set, keeping in mind that small differences may develop.
|
| 929 | SPN 245 Total Vehicle Distance PGN 65248 (0xFEE0) |
Settable
Preferred settable config
An odometer value can be entered into the JX to match the dashboard. Re-calibrate with the MR55 at each PM. Use 929 in place of legacy configs 161 and 673 whenever possible.
Over long distances, expect about 1% drift, usually with the JX reading higher than the dashboard because of rounding and conversion factors.
|
| 161 | SPN 245 Total Vehicle Distance PGN 65248 (0xFEE0) |
Legacy
Settable
No engine/idle hours
Legacy configuration. Use 929 instead whenever possible.
Settable like 929, but does not report engine hours or idle hours. Re-calibrate with the MR55 at each PM.
|
| 673 | SPN 245 Total Vehicle Distance PGN 65248 (0xFEE0) |
Legacy
Settable
Engine + idle hours
Legacy configuration. Use 929 instead whenever possible.
Settable like 929, and supports engine hours and idle hours. Re-calibrate with the MR55 at each PM.
Known issue: the “update config” byte never clears, which in rare cases can cause other buses to also be set to 673.
|
| 049 | SPN 917 High-Resolution Total Vehicle Distance PGN 65217 (0xFEC1) |
Read-only
Electric buses
A high-resolution alternative to SPN 245, giving more accurate distance tracking. Commonly used on BYD and Proterra electric buses. The odometer can’t be programmed into the JX.
|
| 019 | PGN 60143 (0xEAEF) |
Read-only
Identical to config 017, except it reads the odometer from PGN 60143 instead of PGN 65248.
|
| 050 | High-Resolution Vehicle Trip Distance PGN 65217 (0xFEC1) |
Sets the JX odometer to the last valid high-resolution vehicle trip distance value received from the J1939 network.
|
Fleet-Specific Configurations
These configurations were built for specific bus models. Don’t use them on other vehicles.
| Config | Vehicles | Details |
|---|---|---|
| 2337 | Gillig/Kiepe buses (Dayton) | The dashboard odometer on these buses reads 5 times higher than the JX. Set the Miles Run Factor in Data Tools to 0.2 to compensate (see below). |
| 051 | Volvo-built Nova battery-electric buses (Milwaukee Transit) | Reads Volvo’s custom odometer message, PGN 65408 (0xFF80), which is only present on these buses. Sets the JX odometer to the last valid value received. |
JX200PRO-Only Configurations
| Config | Odometer source | Details |
|---|---|---|
| 016 | Pulse input (ST-55 emulation) |
PRO with GHI + PIC processors only
Emulates the ST-55 using the Sw pin on the green connector where the J1939 cable normally plugs in. Mileage increases each time the unit receives enough pulses to match the special ST-55 tire factor. That tire factor is set with its own ST-55 tire factor command, so it doesn’t interfere with the regular JX tire factor.
|
| 233 | GPS |
PRO only
Settable
Uses GPS to measure distance traveled, which becomes the source for the master odometer. The odometer can be set, and the JX then tracks distance driven using GPS.
|
J1708 Network Configurations
| Config | Odometer source | Details |
|---|---|---|
| 00 | PID 245 Total Vehicle Distance |
Recommended
Read-only
The J1708 equivalent of config 017. The JX odometer can’t be adjusted to match the dashboard.
If the ECM is replaced, this value may reset to 0. Program the life-to-date odometer back into the new ECM whenever the engine manufacturer allows it. If that’s not possible, switch the JX to config 97 so its odometer can be set, keeping in mind that small differences may develop.
|
Miles Run Factor
The Miles Run Factor is set per vehicle in Data Tools under Vehicles › Odometer/Service Data tab › Odometer.
| Vehicles | Miles Run Factor |
|---|---|
| Gillig/Kiepe buses using config 2337 | 0.2 |
| All other vehicles | 1.0 |
The Miles Run Factor field (bottom right). Leave it at 1.0 unless the vehicle is a Gillig/Kiepe bus on config 2337.
Not sure which configuration a vehicle needs? Contact Fleetwatch Support.