Features

Troubleshooting

Q: Why am I not receiving position reports?

A: There are a number of possible causes for a lack of reports being received

  1. The unit must have active Iridium SBD service. Ensure the unit has been activated for Iridium SBD service.

  2. Routing for the device may be configured incorrectly. Ensure the SPNet configuration is set for the Device Routing IP Addresses and Ports

  3. The unit may be low on power or off. Is the unit powering up and attempting a transmit cycle as described in the getting started section? If not, follow the getting started section to turn the unit on. If the unit only turns on for less than 10 seconds, make sure the unit has adequate charge (while on, the power LED should flash 2-5 times; if only flashing once, the battery may be low).

  4. The unit does not have a clear view of the sky. EEnsure the unit has a clear view of the sky with the antenna pointed up and not obscured.

Console/Terminal Behavior

The core functionality is driven by an eLua that connects to the RS232, USB CDC, and BLE SPP ports. Any characters entered on any of the ports will be echoed to all ports. From this console, you can run your first script by simply typing 'print("Hello World!")' and pressing enter to execute.

To connect to RS232, simply connect to a RS232 level port (+/- 12VDC, not TTL level) at 115200,8N1

To connect via USB, simply connect and install drivers from this page if you are running Windows, or if you are running Linux or Mac, the drivers are already included.

Q: Why am I getting incorrect position reports?

A: There are two likely causes for this situation:

  1. The DirectIP routing may be configured incorrectly. Ensure that the unit is configured for the  Device Routing IP Addresses and Ports

  2. If you are north of 45 N latitude or south of 45 S latitude and are getting incorrect locations and have correct routing information, contact support for a firmware update.

Q: What kind of GSM modem does GSatMicro X use ?

A: The GSM enabled version of GSatMicro ("GSatMicro X") uses one of these GSM modems:

  • UE866-EU: EMEA/APAC 3G modem. Frequency bands:

  • UMTS/HSPA: 900/2100 MHz

  • GSM/GPRS: 900/1800 MHz

  • ME310G1-WW: Worldwide 4G LTE-M and NB-IoT modem (see this link for more details about LTE-M and NB-IoT coverage). Frequency bands:

  • 4G: B1, B2, B3, B4, B5, B8, B12, B13, B18, B19, B20, B25, B26, B27, B28, B66, B71, B85

  • 2G: B2, B3, B5, B8

To find out the version of modem used in your GSatMicro X:

  1. Connect the modem to the PC using an USB cable.
  2. Connect a terminal emulator to the GSatMicro's serial port.
  3. Run gsm.setpower(1)
  4. Wait a few seconds for the command above to complete (you should see a list of AT commands issued by the modem driver after setpower is complete).
  5. Run gsm.diag()
  6. In the output of the command above, look for the AT+CGMM command and its response, which contains the modem version. For example:
> gsm.diag()3#TX#msg:AT+CGMM3#RX#UE866-EU3#T#model=UE866-EU3#RX#OK

Q: How can I get the list of available GSM networks ?

A: Connect the modem to the PC using an USB cable and follow the steps below:

  1. Connect a terminal emulator to the GSatMicro's serial port.
  2. Run gsm.setpower(1)
  3. Wait a few seconds for the command above to complete (you should see a list of AT commands issued by the modem driver after setpower is complete).
  4. Run gsm.command("AT+CFUN=4\r")
  5. Wait for an OK on the terminal (which indicates that the command above is completed).
  6. Run gsm.command("AT+CFUN=1\r")
  7. Wait for an OK on the terminal (which indicates that the command above is completed).
  8. Run gsm.command("AT#CSURV\r")

The last command above will display a list of all available network commands, followed by a "Network survey ended" message when the command completes. Note that this command takes a long time to complete.

Previous
Lua Functions