Please reference the general Lua interface documentation here: http://www.eluaproject.net/doc/v0.9/en_refman_gen.html

First up is a common item which is how the device is wired, as the outputs are not “driven”, they are “relay” outputs. When the output is active, it sinks current to ground, and when not active, the pin is high Z (but not high voltage). To use the output pin as a high/low IE VCC/GND output, you would wire a pullup resistor on the output.

You must activate your SBD services first by contacting your Airtime service vendor and initiating activation. Once activated, you will be able to proceed with your configurations by following instructions in the Wiki: https://www.gsattrack.com/wiki/GSatMicro.ashx

The GSatMicro does support the PECOS format for short position. The long position format could be supported as well. Since the GSatMicro is quite flexible in terms of programming and message packing, the scripting capabilities make it quite easy to build features like this.

Yes. All of GSE's hardware is made in the USA. This includes the GSatMicro, GSatMicro OEM, GSatMicro X, GSatMicro-DoD, the MCG-101, and the Aurora.

Yes. Once you’ve removed the GSatMicro from its box, underneath you will find the charging and configuration cable. It may look like a standard charging cable for an M2M device with its black matte finish and 3 end split with over mold, but it's much more. On one end, you’ll notice a well-founded “GSatMicro” print on it with a white arrow facing down which will go into the GSatMicro’s charging port, that is located under the black rubber cap up top of the GSatMicro. On the other side of the cable end, you’ll see the GSE logo over mold, which divides that end to a USB port, RS232, and DC Power & I/O.

Full details can be found here under an article: “What Comes in the Box”: https://www.gsatmicro.com/community/articles/inside-look-gsatmicro-whats...

The GSatMcro can rest on the shelf for years without needing to be charged. For self-powered operation, or operation on USB, an optional 2500 mAh LiPo battery pack can be added. This battery pack was custom designed with special LiPo materials to achieve a 20% increase in battery density. Also, the size was custom built to fit within the outline of the GSatMicro board for an efficient stackable design.

Power and Battery Power Connections: USB DC Input (4.5V to 5.5V)
High Voltage DC Input (7.5V to 36V) (protected to 40V DC)
Battery Type: Internal LiPo 2500mAh with PTC
Battery Charge Time USB: 4-6 hours
Battery Charge Time DC: 2-3 hours

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.

Example commands:
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
settings.flash(settings.report_format, 1)

We have an encoding/decoding library written in C# that you can reference here that handles all the to-mobile and from-mobile messages:
https://github.com/darren1713/GSatMicroPublic

We also have a "cheat sheet" for the 18 byte format that you can reference here:
https://docs.google.com/spreadsheets/d/1hul-GmAiQQc3RCVPAT5al8BFWF549DuA...

Estimated: 800

Yes you can dim or disable the LEDS with the led mask configuration setting scaling from 255 to 0 brightness