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

Hi Eishi and Felipe, thank you both for your responses and for looking into this. @Felipe_Hoffa, to answer your question: we are looking to interpret the sequence of events for device cellular connectivity health monitoring, specifically to calculate accurate uptime and availability metrics. To give you a bit more background on our current process, we have been using a report template from the &quot;Log Data and Collisions&quot; module, and recently implemented a script that queries <code>debugData</code> via the MyGeotab API. I appreciate any insights you and the MCP team can share on this!

Extracting DebugData (debug records) via the MyGeotab MCP Connector

Hi everyone, When downloading a requested video from the GO Focus Plus, it appears that the audio track is saved in an independent folder, completely separate from the video file. How can I merge both the video and audio files into a single playback file? Is there a recommended tool or a native method to do this automatically? Thank's in advance!

How to merge separate audio and video files from GO Focus Plus downloads?

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!

"GNSS: Signal strength indicated by carrier-to-noise ratio (dBHz) of the strongest satellite signal detected" record meaning

Hi everyone, What is the meaning of the 'Cellular modem signal strength' status record found under 'Engine Measurements' section? Additionally, what are its possible values (such as dBm or RSSI ranges) and their meanings regarding network quality? Thanks in advance!

"Cellular modem signal strength" record meaning

Hi everyone, What is the exact meaning of the 'Cellular modem radio access technology ' status record found under 'Engine Measurements' section? Additionally, what are its possible values and their respective meanings? Thanks in advance!"

"Cellular modem radio access technology" record meaning

<a data-id="1044" data-value="EishiFUN" data-denotation-char="@" href="/user/eishifun" class="text-decoration-none mention">@EishiFUN</a> Thank you so much for the detailed explanation. This guidance provides great clarity. We truly appreciate your time and support with this inquiry!

Hi everyone, I am currently evaluating advanced device troubleshooting capabilities and would like to know if it is possible to query or stream DebugData (debug records) directly through the MyGeotab MCP Connector. While we can successfully stream standard telematics data (such as LogRecords, StatusData, etc.) using the MCP Connector, I haven't found specific documentation regarding the synchronization of the <code>DebugData</code> API object. For instance, we are interested in evaluating various debug record types to monitor device health, such as:<ul><li><code>ModemConnectionSuccess</code></li><li><code>GprsModemPowerOff</code></li><li><code>DebugErrorRestartModemManager</code> (these are just a few examples of the debug logs we would like to analyze)</li></ul> Has anyone successfully pulled the <code>DebugData</code> object through the MCP Connector, or is it currently limited to standard API calls? If it's not supported yet, is there any roadmap to include it?

Hi everyone, What is the meaning of the 'Cellular modem signal strength' status record found under 'Engine Measurements' section? Additionally, what are its possible values (such as dBm or RSSI ranges) and their meanings regarding network quality? Thanks in advance!

page-user page-user-david-atayde-8256 template-account-profile page-status-200 theme-harmony user-guest

Company

Title

A broadcast-only group for receiving Geotab integrations news and updates!

Integrators Group

Hi everyone, We are currently evaluating the performance and connectivity of GO9B devices. In our evaluation strategy, we established that logs associated with the <code>GprsModemPowerOff</code> state do not necessarily imply a loss of connectivity. We consider this to be the standard operational behavior of the device when the vehicle is stationary and transmitting data at 30-minute intervals. Since our measurement methodology accounts for this time with the GPRS module disabled, this period is excluded from the actual disconnection calculation. This allows us to obtain a more accurate assessment of the average device availability (uptime) during the analyzed period. When analyzing our data to confirm this, we found a clear power cycle sequence in the devices that validates this behavior: the system transitions from <code>GprsModemPowerOff</code> to <code>GprsModemPowerOn</code> and finally to <code>ModemConnectionSuccess</code>. However, a question has arisen internally regarding whether the presence of the <code>GprsModemPowerOff</code> log is completely normal within the device's communication cycle. My main question is: Does this state actually affect connectivity time and should it decrease the uptime percentage, or is it correct to exclude it from the total calculation as we have been doing? I did some research and found a related query here: <a href="https://support.geotab.com/community/post/2194/records-found-in-collisions-and-log-data" target="_blank">https:&#x2F;&#x2F;support.geotab.com&#x2F;community&#x2F;post&#x2F;2194&#x2F;records-found-in-collisions-and-log-data</a>, but I would like to get specific guidance on how this impacts availability metrics. Kind regards,

Hi Eishi, Thank you for the quick response and for clarifying how the platform currently handles these downloads. That feature will definitely streamline the process for us and significantly improve the experience for our end-users once it goes live. I will keep an eye out for future updates on this.  Have a great one!