30 - GNX has traveled DISTANCE_INTERVAL meters since last DISTANCE event was queued

31 - GNX main supply voltage has been below POWER_DOWN_VOLTAGE for at least 2 minutes

32 - User application on UART or Ethernet interface sent a text message

33 - GNX received a RESETGNX10 command

34 - GNX received a RESETPVTQ command

35 - GNX started OTAP process, triggering the sending of its position queue

36 - Magnetic card reader input detected

37 - Indicates that a PTO is active while the vehicle is moving, and that this has been the case for a period of time

38 - Must follow the previous PVT. Indicates that either the PVT went inactive, OR the vehicle stopped moving

39 - Indicates that the GPS module is signaling a short-circuit on the antenna connection

40 - Indicates that the GPS module is signaling a open-circuit on the antenna connection

41 - Indicates that the cellular modem signal strength (RSSI) has been above the defined threshold RSSI_IN_COVERAGE for the hysteresis time

42 - Indicates that the cellular modem signal strength (RSSI) has been below the defined threshold RSSI_OUT_COVERAGE for the hysteresis time

43 - Indicates that the SIM was removed from the GNX (GPRS modems only)

44 - Caused by pushing of external panic button which can be configured to be connected to any of the four switch inputs

45 - If external tempsensor is connected this indicates a high-temperature condition (levels are parameterized)

46 - As above, but a low temperature event

48 - If a backup battery is fitted this PVT indicates that main power was restored

49 - If a backup battery is fitted this PVT indicates that main power was disconnected

50 - If a backup battery is fitted this PVT indicates that backup power was restored

51 - If a backup battery is fitted this PVT indicates that main power was disconnected or fell to a low level (discharged)

54 - If the GNX is not making a current GPS position fix when the ignition goes from off to on (e.g. when parked in a garage) then this event captures the first position fix made following the ignition change

55 - If the analog A2D input is configured to act as a voltage based PTO (see param 164) then this event captures the transition from below the specified voltage to above the specified voltage

56 - If the analog A2D input is configured to act as a voltage based PTO (see param 164) then this event captures the transition from above the specified voltage to below the specified voltage

99 - If a port expander or Jbox peripheral is connected to a GNX5P then this indicates that the peripheral was connected or disconnected, or that the supplementary PTO inputs on the port expander changed. Connection and disconnection can be due to the GNX powering and de-powering the peripheral according to parameters 56, 60

106 - On GNX devices equipped with some Ublox GSM/HSPA modems this event signifies that the modem has detected interference that is preventing a data connection

107 - Input summary event: gives summary of action on the ignition and PTO inputs since the last event. Can be a useful daily summary of activity

108 - On GNX devices with a ublox GPS receiver with software version 7 and above this event will show if the GPS receiver thinks that the lack of position fix may be for jamming reasons. This has been found to be prone to false positives so please bear this in mind

109 - occurs if the GNX reads the VIN code of the vehicle. The VIN code is appended to the reason code/reason text column (9 or 10)

110 - See parameter 113: indicates start of towing

111 - See parameter 113: indicates end of towing

112 - See parameter 113: indicates ongoing towing

113 - See parameter 112 (TEMP_INTERVAL). Optional event code indicating that the server has enabled a temporary higher reporting rate from the GNX

117 - Event indicating possible tampering with the GNX while the vehicle is parked. Enabled by parameter 177

118 - currently only supported on OBD: this event occurs when the fuel level changes by more than 25%

119 - Gxxx.08.xx and newer firmware: indicates that the GNX has reached its MAXDATAUSAGE limit

120 - Gxxx.08.xx and newer firmware: indicates a change in status of the connection to the vehicle’s bus (J1939, OBD)

121 - Experimental. This is an attempt to capture large excursions from the mean in RPM and engine load without requiringconfiguration on a per-vehicle basis (since all vehicles have different RPM ranges). Just enable theevent 121 and it should be sent when the RPM exceeds 2xaverage RPM, or when engine calculatedload exceeds 80%: in the event the reported RPM (column 77) and Engine load (column 76) valuesare the maximum detected during the excursion

122 - (DLO – driver log out) – can be optionally triggered by CANCEL_DRIVER_ID or byONE_WIRE_ENABLE=a.b.x55 – this event is disabled by default for backward compatibility