- You are here: Home > I hear it is different, but what is the GSatMicro?
You are here
I hear it is different, but what is the GSatMicro?
To start with, the Micro is not specifically a tracking device, it is a processing engine that has access to transmit and receive data over the global Iridium satellite network, position information, sensors, etc. It has a very powerful virtual machine on board that allows realtime processing of scripts by compiling and executing without any external tools.
The basic scripts on the unit will power up GPS, get a position, and then compress and transmit that information over the satellite network, but this is entirely script based. Where other script engines utilize compilers on a host to design a script and them compile or compress it to byte code so the smaller onboard microcontroller can execute it, the Micro contains all of this on board. This opens up so many elements of flexibility to the system design.
A typical system would have a complicated development environment installed on a host, and the scripts designed in that environment, and then compiled to much simpler byte code that a microcontroller can process, and then flashed to the microcontroller. In reality, the microcontroller doesn't know what it's running since those scripts live on the host computer. Also, you cannot retrieve scripts from the terminal because you cannot go back from bytecode->scripts so you have to maintain local copies and track which scripts are on what terminals. In contrast, the Micro holds the raw scripts on the terminal as the compiler lives on board. This means we have a very powerful yet small compiling engine.
Lets take a simple example where you want to process built in accelerometer information. You connect to the console via serial port, USB, or bluetooth (they are all the same) and type the function you wish to test on the console "for i=0,100,1 do; accel.getaccel(); end", press enter, and you have already tested your script functionality. This example will dump 100 continuous accelerometer readings to the console and then return. Then you can add your own processing of the data, control external inputs/outputs, send/receive data over satellite, etc. You can start imagining the possiblities but I like to think of the core of the Micro as a processing engine between ANY and ALL of the built in interfaces: satellite, GPS, Bluetooth, USB, encryption, serial port, analog inputs, digital outputs, accelerometer, battery/charging information, temperature, and shock/motion. Most importantly, the core is a simple API style interface that means you can integrate the Micro core into your product offering, extend it's functionality with external interface and programs. Design your own IOS/Android Bluetooth applications, SCADA control devices, custom management solutions, or use it just like it is out of the box.