Our GSatMicro product has gone through many software iterations (as outlined in the wiki documentation). Newer GSatMicros communicate using an extremely efficient binary format that includes authentication and (optionally) encryption, ensuring reduced airtime costs while retaining information security.
However, older GSatMicros communicated using plain-text Lua commands. Our GSatTrack tracking platform automatically translates your commands, such as parameter updates, into the correct format for transmission to the GSatMicro. But in the case of very old GSatMicros (pre-version 1), even the Lua commands may not be working. If this is the case, you can issue correct commands manually by going to Send Command > Raw Commands on the tracking platform. The format for pre-version 1 Lua commands are only slightly different than the ones outlined in the documentation. Instead of specifying parameters using "settings.<parameter>" you simply use the <parameter> name in quotes.
Version 1: settings.flash(settings.sleep, 300)
Pre-Version 1: settings.flash("sleep", 300)
Version 1: settings.flash(settings.sos_sleep, 300)
Pre-Version 1: settings.flash("sos_sleep", 300)
As always, if you encounter any trouble working with your GSatMicro, simply contact us for assistance.
You'll first want to change the reporting format of the Micro to one of our public formats as it is likely still in the default proprietary format which we do not have documentation on:
0 = Proprietary format
1 = 10 byte format
2 = 18 byte high resolution format
We have an encoding/decoding library written in C# that you can reference here that handles all the to-mobile and from-mobile messages:
We also have a "cheat sheet" for the 18 byte format that you can reference here: