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

In the realm of binary messaging, here's an all-encompassing solution that shows how to pack and transmit binary.

The first thing we are going to run is a quick "in memory" function that makes converting from something easy to enter on the console (ASCII) hex characters to binary. One binary byte (8 bits) is represented by 2 hex bytes (also 8 bits). This in-memory function will make it easy to enter pairs of hex characters to convert to binary.

In your application, you can take a binary string and parse it out to the appropriate hex characters.

Each command must be less than 100 characters, so let's create some strings that are about 70 characters. Then we will take 48 hex bytes and convert them to 24 binary bytes, and append them to a "tx" variable.

Remember the maximum binary MO payload for the satellite modem is 340 bytes.

Last step is actually transmitting this "tx" variable with a simple "iridium.transmit(tx)"

Code Example:

function hex2bin(str) a='' for c in str:gmatch".." do a=a..string.char(tonumber(c,16)) end return a end
tx=hex2bin("1b4c75615100010404040401000000000000000000000000"))
tx=tx..hex2bin("00000202e005000005000000414000001c40000105000000"))
tx=tx..hex2bin("00000202e005000005000000414000001c40000105000000"))
...
iridium.transmit(tx)

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

First, be sure to generate the binary payload using the GSatMicroPublic C# library which generates the proper HMAC signing.
Make sure you also enter the actual IMEI of the device into this library for the correct HMAC key
For the command, make sure there is a “\r” on the end so it gets executed.

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.

The GSatMicro-DoD is specifically for your government customers that wish to leverage the Iridium Airtime contract and advanced services provided by a government program called Enhanced Mobile Satellite Services (EMSS).

EMSS is a capability provided by the DOD that features global data transfer and securable voice communications. The service allows real-time access to other EMSS users, the Sensitive but Unclassified (SBU) Voice and commercial U.S. and international telephone networks through the Iridium satellite network.

Global Satellite Engineering (GSE) is an approved EMSS Partner and all of our hardware which includes the GSatMicro Series, MCG-101, and Aurora are approved to function on the Departement of Defense Gateway. Some of the requirements of becoming an EMSS partner include current status as an Iridium Certified partner/developer, and that our products are made in the USA. In addition, GSE performs the necessary flashing of the Iridium modem within the GSatMicro which is a requirement to function on the DoD Gateway. The Iridium Airtime contract under the EMSS program offers the Government Mission Partners unlimited fixed-price usage. Airtime rates are fixed and will not increase based on usage, number of devices or subscribers added to the EMSS gateway, making approved products all that more attractive to the EMSS mission partners.

Note that our MCG-101 requires a SIM card to function and that it accepts the EMSS issued SIM card allowing it to function on the DoD Gateway. More information on the MCG-101 can be found here: https://www.gsat.us/products/mcg-101

More on the Aurora: https://www.gsat.us/products/aurora

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...