1 Overview
This article covers internet connectivity troubleshooting for Ruptela tracking devices. It is intended for users who need to identify why a device is not sending data or is failing to connect to a mobile network.
Connectivity issues can originate from several layers: physical installation, SIM card configuration, device settings, or the mobile network itself. This guide walks through each layer in order — from the most common and quickest checks to more advanced diagnostics — so that the root cause can be identified efficiently.
2 General Recommendations
2.1 Latest Device FW/extFW Version
Always verify that the device has been updated to the latest firmware and extended firmware (FW/extFW).
Using outdated firmware may cause issues such as:
Missing functionality introduced in recent firmware releases.
Bugs or performance limitations were fixed in later versions.
Updating to the latest firmware is necessary to avoid known bugs and ensure the overall stability of the tracking device. Using the most recent firmware reduces the risk of errors, unexpected behavior, or communication issues.
2.2 Latest CFG Version
Confirm that the configuration file (CFG) was created using the latest configurator tool and uploaded to the device after the firmware update.
Creating and applying the configuration using the latest software versions prevents compatibility issues between firmware and configuration files.
3 Physical SIM Card Inspection
Ensure that the SIM card is inserted with the microchip facing down, as shown in the image below. The SIM card slot has a pictogram that shows the correct orientation.
4 Configuration Basics
4.1 APN Settings
The device requires correct APN settings to connect to the GSM/GPRS network. APN values are provided by your SIM card provider — always verify with them before entering.
4.2 Auto APN
If you use multiple SIM card providers, enable Auto APN. This feature automatically selects the correct APN for the detected provider.
⚠️ Warning: Always validate Auto APN settings with your SIM card provider. Auto APN may not work correctly for all providers in all regions.
4.3 Enable the Temporary Blacklist (900 s)
The temporary blacklist prevents the device from repeatedly connecting to a failing network operator. Set it to 900 seconds.
💡 Tip: To verify or enable the temporary blacklist via SMS, see: GPRS status is 0.
4.4 Enable the Correct Bands for the Region
Required for all 4G devices, especially LTE-M. Enabling the wrong bands is a common cause of connectivity failure when a device enters a new country.
5 Diagnostic IO Parameters
Add the following diagnostic IO parameters to the device configuration. These provide real-time data that helps identify the root cause of connectivity issues.
IO ID | Name | Values |
27 | GSM/UMTS Signal Level | 0 – No signal |
150 | GSM/UMTS Operator | Unique mobile operator code (MCC+MNC) |
418 | GPRS Status | 0 – Disconnected | 1 – Connected |
762 | Network Technology | 0 – GSM (2G) |
763 | Network Registration Status | 0 – Not registered, not searching |
5.1 How to Enable IO Parameters
You can enable IO parameters in the configuration by pressing on IO Events (Options):
Select a free IO slot, find the needed parameter, and press enable:
All enabled parameters:
6 Troubleshooting Options
Use the methods below to investigate the device's current connectivity state. They can be used independently or in combination, depending on what is available.
6.1 Checking LED Patterns
LED patterns provide a quick visual indicator of device status. Refer to the device User Manual, under Technical Information, available at doc.ruptela.com.
Depending on the pattern, you can determine whether the device is connected to the network.
⚠️ Warning: LED indication patterns can vary depending on the device model you are using.
6.2 Verifying Settings via Advanced Configurator
After applying the recommended diagnostic IO parameters, use Tools → Live IO Data (for testing ONLY!) in the Advanced Configurator to verify the device status in real time.
Check the following IO values to understand the device's current state:
GPRS Status – Is the device connected?
GSM/UMTS Signal Level – Is signal strength acceptable?
GSM/UMTS Operator – Which operator is the device registered to?
Network Technology – Is it on the expected network (2G/4G/LTE-M)?
Network Registration Status – Is registration successful or denied?
💡 Tip: We recommend keeping these diagnostic IO parameters enabled for future troubleshooting of network connectivity issues.
6.3 SMS Diagnostic Commands
If GSM is available, the following SMS commands provide useful diagnostic information.
6.3.1 gsminfo
Returns mobile network and GPRS status information. Use this first to determine whether the device sees a network and whether GPRS is connected.
6.3.2 getapn
Returns the current APN, username, password, IP, port, and protocol settings from the device. Use this to verify that the correct APN is configured.
7 Overall Troubleshooting Checklist
Work through this checklist from top to bottom. Each group maps to a section in this article. Tick each item as you confirm it.
7.1 Hardware & Physical Setup
☐ Device is powered from a 9–12 V source (not USB-only).
☐ SIM card is inserted with the microchip facing down and correctly seated in the SIM slot.
☐ SIM card security PIN is disabled.
☐ A non-prepaid, industrial-grade SIM is used (if operating above 40 °C).
7.2 SIM Card & Provider Portal
☐ SIM card is active in the provider portal.
☐ Data plan is enabled with available balance or quota.
☐ Device IMEI is not blocked on the provider side.
☐ APN settings are confirmed with the SIM provider.
☐ Provider-specific APN or network restrictions are reviewed.
7.3 Device Configuration
☐ APN is correctly configured, or Auto APN is enabled for multi-provider setups.
☐ Temporary Blacklist is set to 900 s.
☐ Correct frequency bands for the region are enabled (critical for 4G/LTE-M devices).
☐ Optional: Diagnostic IO parameters added:
IO 27,150,418,762,763.
7.4 Live Diagnostics
☐ LED pattern checked against the device User Manual.
☐ Live IO Data (Tools → Live IO Data) reviewed for signal, operator, GPRS status, and network technology.
☐ SMS command
gsminfosent and response reviewed.☐ SMS command
getapnsent and APN settings verified.
8 Escalation
If all the above steps are completed and you cannot identify the root cause, provide the following information to the support team in advance:
Configuration file taken from the device.
LED pattern description (a video recording is preferred).
SMS command responses (
gsminfo,getapn) and a Live IO Data screenshot, or recorded data with diagnostic IOs enabled.Device log collected according to the basic troubleshooting guide, section Device Diagnostics via Terminal Tool.