EQ Report
EQ Report (G-Q-R)
Extended report with CAN OBD-II data (CAN01). Combines information from the CQ report with vehicle ECU parameters.
Recommended use: Light vehicles with OBD-II protocol. For heavy vehicles with J1939, use ER Report.
Compatible platforms: Wialon and RedGPS have native support for EQ format, enabling integration without additional development.
Generate report
GEQbbc[;@dd..dd]See G Command for parameter details.
Query current position
QEQResponse
REQAABBBBBBCCCCCCDDDDDDDDEEEEEEEEEFFFGGGHHIIJJJKKKKKKKKLMNNOOPPPPQRSS;CANFIELD1=VALUE1,...,CANFIELDn=VALUEnGPS fields structure (CQ base)
| Field | Length | Description |
|---|---|---|
| AA | 2 | Report number (00-FF) |
| BBBBBB | 6 | Date (DDMMAA) |
| CCCCCC | 6 | Time (HHMMSS) |
| DDDDDDDD | 8 | Latitude (DDMMMMM) |
| EEEEEEEEE | 9 | Longitude (DDDMMMMM) |
| FFF | 3 | Speed (km/h) |
| GGG | 3 | Heading (degrees) |
| HH | 2 | IGN+IN inputs (hex) |
| II | 2 | XP outputs (hex) |
| JJJ | 3 | Battery voltage (tenths of V) |
| KKKKKKKK | 8 | Total odometer (meters, hex) |
| L | 1 | GPS Power: 0=Off, 1=On |
| M | 1 | GPS Fix Mode: 2=2D, 3=3D |
| NN | 2 | PDOP (decimal integer) |
| OO | 2 | Number of satellites |
| PPPP | 4 | Seconds since last pos. (hex) |
| Q | 1 | Modem Power: 0=Off, 1=On |
| R | 1 | GSM registration status |
| SS | 2 | CSQ signal level |
CAN OBD-II Fields
CAN data is appended at the end of the frame, separated by ; and in ID=VALUE format:
| ID | Parameter | Unit | Description |
|---|---|---|---|
| 1 | VIN | - | Vehicle identification number |
| 2 | RPM | rpm | Engine revolutions per minute |
| 3 | Wheel speed | km/h | Speed reported by ECU |
| B | Odometer | km | Vehicle total odometer |
| 14 | Fuel consumed | L | Total fuel consumption |
| 15 | Fuel level | % | Tank percentage |
| 2A | Coolant temp. | C | Coolant temperature |
| 2C | Oil pressure | kPa | Engine oil pressure |
CAN fields are optional. If the ECU doesn’t provide a parameter, the field will appear empty (ID=).
Example with valid data
>REQ00210918170359-2778100-064258570001517F000000000049D13010900001516;1=1M8GDM9A_KP042788,2=2200,3=45,B=66010,14=30000,15=75,2A=90,2C=340;ID=037883;*01<GPS Data
| Field | Value | Interpretation |
|---|---|---|
| Date | 210918 | 21/09/2018 |
| Time | 170359 | 17:03:59 |
| Latitude | -2778100 | 2778.100’S |
| Longitude | -06425857 | 6425.857’W |
| Speed | 000 | 0 km/h |
| Heading | 151 | 151 |
CAN Data extracted
| ID | Value | Interpretation |
|---|---|---|
| 1 | 1M8GDM9A_KP042788 | Vehicle VIN |
| 2 | 2200 | 2200 RPM |
| 3 | 45 | 45 km/h (ECU speed) |
| B | 66010 | 66,010 km odometer |
| 14 | 30000 | 30,000 L consumed |
| 15 | 75 | 75% fuel |
| 2A | 90 | 90C coolant |
| 2C | 340 | 340 kPa oil |
Example with invalid data
When the ECU doesn’t respond or has no data available:
>REQ00000000000000-2780656-064296830000117F00000010836F1130112FFFF1117;1=,2=,3=,B=,14=,15=,2A=,2C=;ID=2326;*01<Empty fields (1=,2=,...) indicate that the ECU didn’t provide those values.
Comparison with ER Report
| Feature | EQ | ER |
|---|---|---|
| CAN Protocol | CAN01 (OBD-II) | CAN00 (J1939) |
| Vehicles | Light | Heavy |
| CAN Fields | VIN, RPM, speed, etc. | RPM, accelerator, engine hours, etc. |
| Value format | Integers/String | Decimals with 2 digits |
CAN Configuration
To enable OBD-II data reading, configure the CAN module:
>CAN01,1<See CAN Commands for detailed configuration.
Typical usage
// Periodic report with ECU data every 30 seconds
>STD01E00030<
>SRL01E;TRG=TD01+;CND=IGN;ACC={GEQ01L}<
// Event report with CAN data
>SRL35E;TRG=IN00+;ACC={GEQ35H}<Recommended alternative
For new projects where you need greater control over reported parameters, consider using custom reports Ux + UC + ECU. This allows:
- Selecting only necessary parameters
- Reducing frame size
- Using descriptive field names
Version notes
Availability: Firmware v1.00.00+ for Spider IOT and Smart IoT.