I had a quick look through the debug log for a vehicle travelling out of coverage, and when it goes out of coverage it shows up as 'GprsSendingDataTimeout', along with a bunch of other messages: <img class="ql-image" src="/forum/plugins/gcs-uploads/files/1791253460812-2026-10-06-12_47_55-fc-debug-log_20261005_220836.xlsm-excel.png"/>

GprsModemPowerOff debug log and its impact on uptime calculation

The GO device's accelerometer does provide information for Hard Events (harsh driving), but its availability depends on the service plan: • Base plan: Accelerometer data is not available for harsh driving exception rules. In this plan, the device mainly uses GPS data for tracking and speed. Although the accelerometer detects movement to wake up the device, it doesn't send detailed G-force records to the server. • Pro and ProPlus plans: These are the only plans that support full accelerometer features, including detecting harsh braking, acceleration, and sharp turns. If your client needs to monitor Hard Events, they'll need to upgrade the service plan to Pro or ProPlus.

How are harsh events measured in Base Mode?

Hi Cristian, good morning In my experience, I've installed several firmware updates, and the only one that fixed the “GPS” issue is the BETA version. You could try this version, or maybe the stable version works on some devices. Best regards.

Which is the most stable firmware version at the moment?

<a data-id="1748" data-value="EChan-1748" data-denotation-char="@" href="/user/echan-1748" class="text-decoration-none mention">@EChan-1748</a> The GO10 device has a &quot;Last Gasp&quot; ability but the GO9 doesn't, the GO9 just turns off when the power is removed (providing you're not using an IOX-Battery).

GO9 survival time without battery power

<a data-id="9561" data-value="DRich-9561" data-denotation-char="@" href="/user/drich-9561" class="text-decoration-none mention">@DRich-9561</a> When I add a new asset into MyGeotab database, the odometer field is blank so I have to enter the reading manually. That could be why it's only displaying the odometer reading. Is the harness the correct one for the year model of the F450 &amp; could it possibly be classified as a 'heavy-duty' vehicle given the size (different harness)??? I found this on support page. https:&#x2F;&#x2F;support.geotab.com&#x2F;en-GB&#x2F;harnesses&#x2F;installation&#x2F;doc&#x2F;harness-identify I'm sure they'll publish more info - might pay to submit a feedback form as well 🙂 Goodluck.

Newly installed GO10 device not activating

Hi <a data-id="10053" data-value="PBala-10053" data-denotation-char="@" href="/user/pbala-10053" class="text-decoration-none mention">@PBala-10053</a> , Great question and one that comes up fairly often for mixed fleets. Thank you for asking it here in our community. You're right that GPS-only configured devices won't populate the Fuel &amp; EV Usage Reports — those reports rely on fuel consumption data pulled from the vehicle's OBD&#x2F;CAN bus, which plant and machinery assets often don't expose in the same way as on-road vehicles. Here are some options worth exploring depending on your equipment: 1. J1939&#x2F;CAN-capable equipment Some larger plant assets (excavators, tractors with modern electronics) have J1939 CAN bus support. If the equipment exposes fuel consumption diagnostics on the CAN bus, a GO device wired directly into the J1939 connector — rather than a standard OBD port — may be able to read that data. Whether this is possible depends on the specific make and model and what the OEM exposes on the bus. 2.IOX-AUX with a fuel level sensor The IOX-AUX module allows you to connect analog sensors to your GO device. A fuel tank level sensor can give you tank level readings over time, from which consumption can be inferred — though it's not as clean as a direct consumption diagnostic. 3. Fuel transaction data import If your fuel is dispensed through fuel cards or a site-based fuel management system, Geotab supports importing fuel transaction data via the FuelTransaction API. This won't give you real-time telemetry but does allow you to track fill-ups and costs against assets in MyGeotab. 4. Managing it outside the platform For assets where none of the above is practical, many organisations do manage fuel for plant equipment through a separate fuel management system and use Geotab purely for location and utilisation (engine hours, idle time) on those assets. It's worth noting that off-highway and plant equipment is a recognised gap in the current platform — so I'd also love to hear from others in the community how you're handling this today, as Praveen asked. Real-world experience here is really valuable. Feel free to reach out if you have any questions. We are here to help. Have a great day! Eishi FUN

Plant Machinery Fuel Monitoring in Geotab

<a data-id="8241" data-value="Tony_M" data-denotation-char="@" href="/user/tony_m" class="text-decoration-none mention">@Tony_M</a> Thank you - that was my thought as well but just wanted confirmation from another brain! I've adjusted my report to include rpm to reflect true idling.

Battery/Power isolators - trucks/heavy plant

Hi, thank you for your patience — I followed up with our team and wanted to share what they confirmed. I've consolidated their detailed answer here so it's easier to work through, but let me know if you'd like more depth on any part. ### Heartbeat behavior For a GO9 operating in normal Sleep Mode, the firmware documentation describes the following behavior: - When the vehicle ignition is turned off, the device enters Sleep Mode. - The device sends a heartbeat approximately every 30 minutes for the first 72 hours. - After 72 hours, the heartbeat interval changes to approximately every 23 hours. (<a href="http://support.geotab.com" target="_blank">support.geotab.com</a> (<a href="https://support.geotab.com/en-GB/go-devices/installation/doc/firmware" target="_blank">https:&#x2F;&#x2F;support.geotab.com&#x2F;en-GB&#x2F;go-devices&#x2F;installation&#x2F;doc&#x2F;firmware</a>)) This behavior should be understood as the normal GO9 Sleep Mode behavior. Other conditions can affect the heartbeat cycle, including Low Power Mode, device-disabled mode, low-voltage conditions, device family, and firmware version. For example, Low Power Mode is separately documented as reducing heartbeats to every 23 hours. (<a href="http://support.geotab.com" target="_blank">support.geotab.com</a> (<a href="https://support.geotab.com/help/mygeotab/device-management/device-statuses-and-settings/device-modes" target="_blank">https:&#x2F;&#x2F;support.geotab.com&#x2F;help&#x2F;mygeotab&#x2F;device-management&#x2F;device-statuses-and-settings&#x2F;device-modes</a>)) ### 1. When does isDeviceCommunicating become false? isDeviceCommunicating is not determined by checking whether a heartbeat arrived at one exact scheduled time. For a standard GO device, the current MyGeotab server logic evaluates the timestamp of the latest available status, GPS, or fault data: - If the last stored state is driving, the server uses an approximately 10-minute communication threshold. - If the last stored state is stopped, the server uses an approximately 24-hour communication threshold. Accordingly, if a device has entered the 23-hour heartbeat cycle and then loses power, the server does not simply wait for one specific expected heartbeat and immediately mark the device offline. It evaluates whether the latest received data has exceeded the applicable server-side communication threshold. The value can therefore be understood as an elapsed-time assessment from the latest qualifying data. The result may become visible when the next API request, UI refresh, or server health evaluation occurs. The public device-status guidance describes an hourly health-check evaluation, so the observed transition can occur somewhat after the nominal threshold—for a standard GO device, approximately 24 hours after the last qualifying data, plus the evaluation delay. (<a href="http://support.geotab.com" target="_blank">support.geotab.com</a> (<a href="https://support.geotab.com/community/sdk-api/sdk-api-other-general/2540/how-long-does-geotab-s-cloud-infrastructure-logic-behind-the-heartbeat-data-element-waits-before-sending-a-disconnected-status-message-via-api-for-go09-devices-without-backup-battery" target="_blank">https:&#x2F;&#x2F;support.geotab.com&#x2F;community&#x2F;sdk-api&#x2F;sdk-api-other-general&#x2F;2540&#x2F;how-long-does-geotab-s-cloud-infrastructure-logic-behind-the-heartbeat-data-element-waits-before-sending-a-disconnected-status-message-via-api-for-go09-devices-without-backup-battery</a>)) The server-side property also uses the latest status&#x2F;GPS&#x2F;fault timestamp; it is not limited to a dedicated heartbeat record. Other device families and configurations may use different thresholds, so the exact result depends on the device model, firmware, and enabled modes. ### 2. How is “stationary” defined? There are two related concepts to distinguish. For platform trip and stop recognition, MyGeotab documents a stop as occurring when: - the ignition is turned off; or - the vehicle remains below approximately 1 km&#x2F;h for more than 200 seconds. Stops shorter than 200 seconds while the ignition remains on—for example, waiting at a traffic light—are not recorded as stops in trip history. (<a href="http://support.geotab.com" target="_blank">support.geotab.com</a> (<a href="https://support.geotab.com/help/mygeotab/reports/safety-reports/idling-time" target="_blank">https:&#x2F;&#x2F;support.geotab.com&#x2F;help&#x2F;mygeotab&#x2F;reports&#x2F;safety-reports&#x2F;idling-time</a>)) This explains the 200-second behavior mentioned in the discussion. However, it should not automatically be interpreted as the complete firmware rule for every heartbeat mode. For the GO9 heartbeat schedule specifically, the firmware documentation describes the transition into Sleep Mode in terms of the ignition being turned off. The device may determine ignition using engine data, a three-wire ignition connection, or trip-tracking&#x2F;two-wire logic. Depending on the vehicle and installation, this can involve RPM, road speed, voltage changes, or accelerometer-based movement detection. (<a href="http://support.geotab.com" target="_blank">support.geotab.com</a> (<a href="https://support.geotab.com/en-GB/go-devices/installation/doc/firmware" target="_blank">https:&#x2F;&#x2F;support.geotab.com&#x2F;en-GB&#x2F;go-devices&#x2F;installation&#x2F;doc&#x2F;firmware</a>)) Therefore, “stationary” should not be interpreted as GPS position simply remaining unchanged. ### 3. What resets the 72-hour stationary period? The firmware release notes document a fix to restore the normal 30-minute heartbeat period after the device enters the 23-hour heartbeat cycle and a subsequent ignition-off event occurs. (<a href="http://support.geotab.com" target="_blank">support.geotab.com</a> (<a href="https://support.geotab.com/es-ES/go-devices/installation/doc/firmware-notes" target="_blank">https:&#x2F;&#x2F;support.geotab.com&#x2F;es-ES&#x2F;go-devices&#x2F;installation&#x2F;doc&#x2F;firmware-notes</a>)) Based on that documentation, if the vehicle is stationary for more than 72 hours, the ignition is turned on, and the vehicle is then turned off again, the device is expected to restart the normal heartbeat sequence after the new ignition-off event— approximately 30-minute heartbeats for the first 72 hours, assuming normal Sleep Mode and firmware that includes this behavior. A READY-state transition by itself is less certain. Whether READY is treated as an ignition event depends on the vehicle's signals and the device's ignition-detection method. A READY transition that is not recognized as an ignition-state change should not be assumed to reset the heartbeat cycle. Similarly, Low Power Mode or other special device modes may override the normal Sleep Mode behavior. ### Summary For a standard GO9 in normal Sleep Mode: - The 30-minute heartbeat period applies for the first 72 hours after entering Sleep Mode. - The heartbeat then changes to approximately every 23 hours. - isDeviceCommunicating is a separate server-side assessment based on the age of the latest qualifying device data and the device's stored driving&#x2F;stopped state. - A missed heartbeat does not necessarily cause an immediate disconnect indication at the exact expected heartbeat time. - A subsequent recognized ignition cycle is expected to restart the normal heartbeat sequence, while a READY-only transition requires device- and vehicle-specific confirmation. To confirm the behavior for a particular vehicle, we would need the device model, serial-number prefix, firmware version, ignition-detection method, and whether Low Power Mode, High Frequency Update, or another special mode is enabled. Feel free to reach out if you have any other questions. We are here to help. Have a great day! Eishi FUN

Clarification on heartbeat intervals and isDeviceCommunicating behavior

<pre data-language="plain">I believe this is the one with the most detailed information regarding what you are asking about:
https:&#x2F;&#x2F;support.geotab.com&#x2F;en-GB&#x2F;mygeotab&#x2F;mygeotab-add-ins&#x2F;doc&#x2F;collision-detect-guide</pre>

G-FORCE OF A GO

Hey <a data-id="1203" data-value="Gus_Rubio10" data-denotation-char="@" href="/user/gus_rubio10" class="text-decoration-none mention">@Gus_Rubio10</a> , Great question! Thank you for asking it in our community. There are a few common reasons why a GO device may fail to read the VIN from a vehicle's computer. I used an AI tool to help compile this answer, so please let me know if anything needs clarification. The GO device reads the VIN by querying the engine ECU over the CAN bus. Whether this succeeds depends on how the vehicle manufacturer implemented that part of the ECU firmware. The most common reasons it fails are: - VIN not programmed in the engine ECU — especially after an ECM replacement, the VIN sometimes needs to be manually re-entered using manufacturer diagnostic software and is often skipped - The ECU returns a manufacturer-internal ID instead of the ISO VIN — some manufacturers store an internal build or calibration number in the VIN register rather than the standard 17-character VIN - ECU security lockout — newer ECU firmware versions on some makes require an authenticated diagnostic session before exposing the VIN. Without it, the ECU ignores the request entirely - CAN bus connection issue — if the device is operating in two-wire mode or is connected to the wrong CAN segment, it has no path to the engine ECU It is also possible a loose installation is causing this issue. its hard to say without looking the specific case but I hope this helps give you some things to look into. If the engine VIN cannot be read automatically, the most reliable workaround is to enter it manually in the device settings in MyGeotab. Please let us know if you have any follow-up questions - happy to help! Have a great day! Eishi FUN

¿Why do some GO9 devices not automatically decode the VIN?

Hi, you can also check the compatibility of your unit with the technology; if the odometer reading isn't very stable, this could be the reason.

Odometer not updating for GO device

Hi everyone, What is the exact meaning and operational threshold for the 'GNSS: Signal strength indicated by carrier-to-noise ratio (dBHz) of the strongest satellite signal detected' status record found under 'Engine Measurements' section? Additionally, what are the typical or optimal ranges (in dBHz) for this metric, and what do lower values mean regarding GPS tracking health, signal blockage, or potential interference? Thanks in advance!