Hello everyone,

We are currently working on a diagnostic and performance analysis for GO Anywhere Plus cellular connectivity across different regions in Mexico. Since our devices rely on roaming profiles, tracking the specific local carrier they connect to is critical for our coverage mapping.

For our GO9 and GO9B devices, we successfully extract the active carrier using the DebugData object. When filtering by the ModemConnectionSuccess reason, the base64/hex data contains the MCC and MNC in the first 12 characters. For example, a hex value like 333334303230c00000000000000000 translates to 334020, allowing us to identify the carrier perfectly.

However, we are facing a roadblock with our GO Anywhere Plus devices (which operate with Telenor SIMs in Mexico). When querying the exact same ModemConnectionSuccess debug reason for these devices, the DebugRecordDataInHex returns a generic string such as 000000000000010000000000000000. This payload does not contain the MCC/MNC string.

Because the GO Anywhere Plus relies heavily on roaming across different local networks (like Telcel, Telefonica, AT&T, etc.), identifying the active carrier is essential for our troubleshooting and performance metrics.

My questions for the community and Geotab engineers are:

1. Is the MCC/MNC data logged differently for the GO Anywhere Plus firmware during a connection success event?
2. Is there an alternative DebugRecordReason, a specific StatusData diagnostic ID, or another API endpoint where we can extract the currently connected carrier or MCC/MNC for the GO Anywhere Plus?

For reference, next screenshots showing the DebugRecord examples from MyGeotab.

GO9:

GO Anywhere Plus device:

Any guidance or documentation on how to retrieve this specific network data for the GO Anywhere family would be greatly appreciated.

Thank you!