Skip to Content

ER Report

ER Report (G-Q-R)

Extended report with CAN J1939 data (CAN00). Combines information from the CQ report with vehicle ECU parameters.

Recommended use: Heavy vehicles (trucks, buses, machinery) with J1939 protocol. For light vehicles with OBD-II, use EQ Report.

Compatible platforms: Wialon and RedGPS have native support for ER format, allowing integration without additional development.


Generate report

GERbbc[;@dd..dd]

See G Command for parameter details.

Query current position

QER

Response

RERAABBBBBBCCCCCCDDDDDDDDEEEEEEEEEFFFGGGHHIIJJJKKKKKKKKLMNNOOPPPPQRSS;CANFIELD1=VALUE1,...,CANFIELDn=VALUEn

GPS field structure (CQ base)

FieldLengthDescription
AA2Report number (00-FF)
BBBBBB6Date (DDMMYY)
CCCCCC6Time (HHMMSS)
DDDDDDDD8Latitude (DDMMMMM)
EEEEEEEEE9Longitude (DDDMMMMM)
FFF3Speed (km/h)
GGG3Heading (degrees)
HH2IGN+IN inputs (hex)
II2XP outputs (hex)
JJJ3Battery voltage (tenths of V)
KKKKKKKK8Total odometer (meters, hex)
L1GPS Power: 0=Off, 1=On
M1GPS Fix Mode: 2=2D, 3=3D
NN2PDOP (decimal integer)
OO2Number of satellites
PPPP4Seconds since last pos. (hex)
Q1Modem Power: 0=Off, 1=On
R1GSM registration status
SS2CSQ signal level

CAN J1939 Fields

CAN data is added at the end of the frame, separated by ; and in ID=VALUE format:

IDParameterUnitDescription
2010RPMrpmEngine revolutions per minute
5000Accelerator position%Accelerator pedal percentage
1030Fuel consumptionLTotal fuel consumption
4201Fuel level%Tank percentage
1020OdometerkmTotal vehicle odometer
1010Wheel speedkm/hSpeed reported by ECU
2012Coolant tempCCoolant temperature
2013Oil pressurekPaEngine oil pressure
2020Engine hourshEngine Hours / Hour meter
3010Trip fuelLFuel consumed in current trip

CAN values are reported with decimals (e.g.: 1000.00). If the ECU doesn’t provide a parameter, the field will show error code !3.


CAN status codes

CodeMeaning
=VALUEValid data received from ECU
!3No information (ECU didn’t respond)

Example with valid data

>RER00090719144856-2778101-06425853000214FF00115000000AD13011000001511;2010=1000.00,5000=0.00,1030=10000.00,4201=50.00,1020=20000.00,1010=60.00,2012=15.00,2013=100.00,2020=13.00,3010=0.13;#0009;ID=037222;*5A<

GPS Data

FieldValueInterpretation
Date09071909/07/2019
Time14485614:48:56
Latitude-27781012778.101’S
Longitude-064258536425.853’W
Speed0000 km/h
Heading214214

Extracted CAN J1939 Data

IDValueInterpretation
20101000.001000 RPM
50000.000% accelerator (foot off pedal)
103010000.0010,000 L total consumed
420150.0050% fuel in tank
102020000.0020,000 km odometer
101060.0060 km/h (ECU speed)
201215.0015C coolant
2013100.00100 kPa oil pressure
202013.0013 engine hours
30100.130.13 L in current trip

Example with invalid data

When the ECU doesn’t respond or has no available data:

>RER00000000000000-2780656-064296830000117F00000010836F1130112FFFF1118;2010!3,5000!3,1030!3,4201!3,1020!3,1010!3,2012!3,2013!3,2020!3,3010!3;ID=2326;*7F<

The !3 code in each field indicates that the ECU didn’t provide information for that parameter.


EQ vs ER Comparison

FeatureEQ (OBD-II)ER (J1939)
ProtocolCAN01CAN00
VehiclesLight (cars, SUV)Heavy (trucks, buses)
Value formatInteger/StringDecimals (2 digits)
Engine hoursNoYes (2020)
Accelerator positionNoYes (5000)
Trip fuelNoYes (3010)
VINYesNo

CAN Configuration

To enable J1939 data reading, configure the CAN module:

>CAN00,1<

See CAN Commands for detailed configuration.


Typical usage - Truck fleets

// Periodic report with ECU data every 30 seconds >STD01E00030< >SRL01E;TRG=TD01+;CND=IGN;ACC={GER01L}< // Report on prolonged idle event >SRL35E;TRG=RL00+;ACC={GER35H}< // Report when engine turns off (to capture totals) >SRL40E;TRG=IGN-;ACC={GER40H}<

For new projects where you need more control over reported parameters, consider using custom Ux + UC + ECU reports. This allows:

  • Select only necessary parameters
  • Reduce frame size
  • Use descriptive field names

Version notes

Availability: Firmware v1.00.00+ for Spider IOT and Smart IOT.


Compatibility

C5Legacy
SP-IoT
SM-IoT
MT
C3
UL
SP
ZE-IoT
Last updated