How long does MyAdmin retain the date for a device's last GPS record and last engine record?I have been reviewing several devices in MyAdmin and noticed that even though some units previously had valid GPS and engine data, after a certain period of time, the field changes to 'No data.' I am attaching a sample image for reference. I would appreciate it if anyone could clarify the retention logic or why these fields eventually revert to 'No data'.

Data retention period for "Last GPS" and "Last Engine" records in MyAdmin

Hello team,I'm reviewing the default idling rule in our databases. I don't understand the part about the "Duration Between GPS Logs," which is set to be less than 3 minutes and 21 seconds by default.My confusion is this: as I understand it, if the device has the ignition on but doesn't detect movement, it logs a GPS location every 100 seconds using the CurveTimeOut. Since 100 seconds (1 min 40 s) is always less than 3 min 21 s, the rule's condition will always be met. Can you please explain how the "Duration Between GPS Logs" value is calculated and what the purpose of this part of the rule is?  

Understanding the MyGeotab Idling Rule: Duration Between GPS Logs

page-user page-user-joel-ruiz-1365 template-account-profile page-status-200 theme-harmony user-guest

Company

Title

How long does MyAdmin retain the date for a device's last GPS record and last engine record?I have been reviewing several devices in MyAdmin and noticed that even though some units previously had valid GPS and engine data, after a certain period of time, the field changes to 'No data.' I am attaching a sample image for reference. <img src="/forum/plugins/gcs-uploads/files/069Pd000012t5CNIAY.png" alt="image" />I would appreciate it if anyone could clarify the retention logic or why these fields eventually revert to 'No data'.

Good day everyone: Based on your comments, the GO device does not have any additional communication or functional failures; your wish is to repair it without the need for replacement. We cannot open the GO devices, as doing so invalidates the warranty. Therefore, repair is not a viable option. Our experience shows us two paths: If the device is 100% functional (apart from the LED failure) and there is no risk of confusion or misinterpretation by the installer in the field, I recommend leaving it as is. If there is any possibility that the LED failure could cause confusion or misinterpretation in the field, replacement is the best option. We have had cases of fully functional equipment with burnt-out LEDs that, to prevent errors, we ultimately finalized with a replacement. In summary: If it works and doesn't cause confusion: Leave it. If it could cause confusion: Replace it.

Go Device Repeating Sequence of Fading Lights

Hi <a href="/user/solomen-dorrell-2107" data-id="2107" data-value="SDorr-2107" data-denotation-char="@" class="text-decoration-none mention">@SDorr-2107</a>​  I am sharing this <a href="https://support.geotab.com/geotab-drive/doc/drive-app-driver" target="_blank">link</a> with you which provides a step-by-step guide on what you need to do. The app is available for Android and iOS devices; you can download the app from the Play Store or the App Store and follow the steps mentioned in the link to configure it. Regards

What's the website link to log onto geotab drive?

Hello <a href="/user/joe-raap-2061" data-id="2061" data-value="JRaap-2061" data-denotation-char="@" class="text-decoration-none mention">@JRaap-2061</a>​ : The record you are mentioning to us is a debug record and not a diagnostic one. The GO device has a GPS module and a logic for recording valid GPS coordinates that is capable of determining when a point is genuine or false. When there are GPS interferences, the logic cannot accurately determine if the point is true or false. What is this based on? It's based on the quality of the satellite signal reception. Normally, in ideal conditions, for a device to have good GPS signal reception, it needs to have a good quantity of satellites "in sight." What things could interfere with satellite signals?1. ObstaclesImagine you are in a dark place, you can't see anything, and a person is guiding you only with their voice. Suddenly a wall or an object causes you not to hear clearly where the voice is coming from, and that confuses you. The same happens with GPS signals; their direction is from the satellite to the GO device. Ideally, for the GO to "hear" the satellite's voice correctly, there shouldn't be anything interposed. So, imagine what things might be between the satellite and the device: Clouds, rain, hills, mountains, buildings, metal roofs, metal parts of the vehicle that cause the strength of the satellite's "voice" to weaken and the GO to become confused. For this, check the location where the device is installed. Is it beneath or inside something metallic? Are there large metallic things very close, especially above the device? Normally, the GO device doesn't show this type of interference with the debug log you mention, but rather registers it as a weak or poor GPS signal. 2. DistortionsImagine the same example from the previous point, but now, external noises or additional voices make you unable to understand what the guiding voice is telling you or where the voice is coming from. Well, there are elements, technologies, or devices that generate a similar effect. For example, there are radiofrequency and Bluetooth transmitters for music playback that generate frequencies which create noise and cause the GPS signals to be distorted and become so weak that the GO device doesn't "hear" or understand them. Also, through experience, we have encountered other types of devices, such as tracking cameras that could have these effects. The current in the vehicle's cables or harnesses also generates magnetic frequencies that could interfere with GPS signals. Radiocommunication devices, wireless chargers, and even illegal Jammers among others can have these effects. It is in these types of situations that the GO registers the debug record you mention—when the GPS signal is not poor, but suffers an abrupt drop in intensity and quality, and this is generally due to external distortions. I recommend you check if the vehicle mentioned does not have any of the elements I already mentioned, and that the device is not installed and secured near elements that handle a lot of cables or in the middle of them, near radio emitters, Bluetooth, and things like that. You can try to move it away from these as much as possible using an additional extension, without exceeding the safe extension limit, which I believe is between 1.5 and 2 meters. I hope this is helpful.

GPS JAMMING

Hello <a href="/user/eishifun" data-id="1044" data-value="EishiFUN" data-denotation-char="@" class="text-decoration-none mention">@EishiFUN</a>​ Thank you very much for the clear explanation. I understand it perfectly now.As you explained, the "Duration Between GPS Logs" rule isn't meant to detect idling itself, but rather to ensure the GPS is working correctly and that the speed data is reliable before the idling event is triggered.I appreciate the help.

Hello team,I'm reviewing the default idling rule in our databases. I don't understand the part about the "Duration Between GPS Logs," which is set to be less than 3 minutes and 21 seconds by default.<img src="/forum/plugins/gcs-uploads/files/069Pd00000aWkmBIAS.png" alt="image.png" />My confusion is this: as I understand it, if the device has the ignition on but doesn't detect movement, it logs a GPS location every 100 seconds using the CurveTimeOut. Since 100 seconds (1 min 40 s) is always less than 3 min 21 s, the rule's condition will always be met. Can you please explain how the "Duration Between GPS Logs" value is calculated and what the purpose of this part of the rule is?

Viimane tegevus

Data retention period for "Last GPS" and "Last Engine" records in MyAdmin

Understanding the MyGeotab Idling Rule: Duration Between GPS Logs