Tips to Troubleshoot Connection from your Tracker to GpsGate's Cloud Platform

Have you added your asset to GpsGate and configured your tracker, but it's still showing "Asset status: Never seen" or isn't reporting its position? Don't worry, this is almost always fixable! 

This guide walks you through the most common causes and how to diagnose each one, specifically for users using GpsGate Cloud.

Checklist:

1. GpsGate General verification
2. Is the tracker actually powered on?
3. Connectivity - SIM Card
4. Is the tracker properly installed?
5. Can the tracker get a GPS fix?
6. Terminal traffic
7. Check the tracker Firmware
8. Still not working?
9. Quick SMS command reference

Step 1: GpsGate General verification:

• Please ensure that your platform is running the latest versions of all plugins, and that the tracker you're trying to connect to is listed among the supported devices.
• Ensure all assets have been created in your application, and verify that the registered IMEI matches the one on the tracker. If you are using the SMS command, please verify that all steps have been followed correctly.

Once you've confirmed these points, you can proceed with the next troubleshooting steps.

Step 2: Is the tracker actually powered on?

This one sounds obvious, but it happens more often than you'd think. The tracker needs power to do anything, including respond to SMS commands. Check the following:

• Hardwired trackers: verify the ignition or constant power wire is properly connected and the vehicle's fuse hasn't blown.
• Battery-powered trackers: check the battery level or try placing the unit on external power.
• LED indicators: most trackers have status LEDs. Consult the hardware manual for what each blinking pattern means.

If the tracker powers up but still doesn't appear in GpsGate, keep reading.

Step 3: Connectivity - SIM Card

The tracker needs a working SIM card and an active mobile data plan to communicate with GpsGate Cloud. Sometimes a voice-only SIM won't work. 

• Verify APN Settings: Check the APN, APN Username, and APN Password with your SIM provider to ensure the correct setup. 
• SMS Reply: If SMS was used for tracker setup and the tracker doesn’t respond to the SMS command within 30 seconds, verify that the phone number used for the tracker is correct. An incorrect phone number will prevent the SMS command from reaching the tracker. Also, confirm the SIM card can receive and send SMS messages.
• Confirm Activation and GPRS Access: Ensure the SIM card is active and has GPRS enabled, as it is sometimes disabled. You can verify by testing the SIM in a mobile phone with a web browser or by asking your provider.
• Check for Credit: If using a prepaid SIM, confirm there is sufficient credit.
• Disable SIM PIN Code: Either disable the SIM’s PIN code or confirm the tracker can handle it. Use a mobile phone’s security settings to disable the PIN if necessary.

Step 4: Is the tracker properly installed?

An incorrectly wired or mounted tracker can cause all sorts of erratic behavior: intermittent connectivity, false ignition readings, GPS noise, or just complete silence. Please double-check:

• That power and ground wires are making solid, clean contact.
• The GPS antenna (if external) has a clear line of sight to the sky and isn't routed near interference sources like radio equipment.
• The tracker is mounted with the correct orientation per the manufacturer's instructions (relevant for trackers with internal accelerometers).
• No wires are pinched, frayed, or connected to the wrong terminals.

When in doubt, re-read the hardware installation guide for your specific model. Tracker manufacturers publish detailed installation instructions for every tracker in their Manuals/Wiki

Step 5: Can the tracker get a GNSS fix?

A tracker that can't see the sky can't report a position. GNSS signals don't pass through metal roofs, concrete walls, or dense urban canyons very well. If the tracker was just installed indoors for testing, move it outside and give it a few minutes.

Look for the number of GNSS Satellites: Ideally, you want to see more than 3 (3D fix) visible satellites. A value of 0 means no fix at all. If GPS is stuck at 0 and the tracker is outdoors with a clear view of the sky, the antenna may be faulty or improperly routed.

Step 6: Terminal traffic

The Terminal is a valuable tool for checking server-tracker communication. Any data sent by the tracker will appear here. Read how to use the terminal here.

• No Traffic in Terminal: If there is no traffic, the tracker may not be sending data.  
• Invalid data in Terminal: A position is invalid when the tracker sends non-updated or unreliable position information.

Note: Depending on the tracker manufacturer, the tracker may require 10-15 minutes to update a valid position.

Step 7. Check the tracker Firmware

The terminal window displays a "Data is invalid" message. Some tracker manufacturers require the latest firmware for their trackers to function and report data correctly.

Please verify with the tracker manufacturer for the latest firmware release and update your tracker if necessary.

8. Still not working?

If you've worked through all of the above and the tracker still isn't showing up, here are a few more things worth checking before reaching out to support:

• Verify the server address and port in the tracker config. For GpsGate Cloud, confirm you're using the correct hostname assigned to your Cloud instance. This is visible in your GpsGate Cloud Welcome email.
• Check the device protocol. Make sure the tracker is configured to use the correct protocol supported by GpsGate (e.g., Teltonika/Codec 8 or Codec 8 Extended). A protocol mismatch means the server receives data it can't parse.
• Review the device logs. If you have access to the tracker configuration via USB, the device logs can show exactly what the tracker is trying to send and whether it's getting a response from the server.
• Try a different SIM or network. If you suspect a carrier issue, test with a known-working SIM to rule out network-level blocking.

If none of the above resolves it, contact GpsGate Support with the tracker's IMEI number, the SMS responses you received, and a description of what you've already tried. The more context you give, the faster they can help.

Quick SMS command reference

SMS commands are one of the most useful tools you have when troubleshooting a tracker that isn’t connecting. Unlike the platform UI, SMS works independently of the data connection, so even if the tracker can’t reach the server, you can still query it directly and get a real-time response back on your phone. It’s a fast, reliable way to cut through the guesswork.

The examples throughout this guide use Teltonika FMB SMS/GPRS trackers, but the same approach applies to virtually any GPS tracker that supports SMS configuration. The command syntax will vary by manufacturer, so check your tracker’s documentation for the equivalent commands, but the diagnostic logic is the same: power, GPS fix, data connectivity, and server settings.

Usually, trackers' SMS commands have a structure; in this example, the structure is the following:

<SMS login><space><SMS password><space><command><space><value>

• If you have set SMS login and password: login pass getinfo
• If SMS login and password are not set, leave two spaces before the command:   getinfo

To configure your credentials, send the following command (replace the values as needed):

Once sent, your tracker will reply to confirm that the command was received and saved. Let's move on. To verify the tracker's GNSS status, send it this SMS command:

In the response, look for GNSS: ideally, you want to see GPS:3 (3D fix). A value of 0 means no fix at all. If GPS is stuck at 0 and the tracker is outdoors with a clear view of the sky, the antenna may be faulty or improperly routed. 

You can also request the last known GNSS position directly:

If you get back valid latitude and longitude values, the GNSS is working. If not or if the coordinates look frozen, the tracker likely hasn't acquired a fix yet.

To check the modem and data connection status, send:

Look for GPRS:1 in the response; that means the modem has successfully registered on the data network. If you see GPRS:0, the SIM isn't connected to data. Common reasons:

• The SIM isn't activated yet (contact your provider).
• The APN settings are wrong for your carrier.
• The SIM has run out of data.
• The SIM is a voice-only plan with no data included.

Did you recently change the server settings?

If you migrated a tracker from a different server or re-pointed it to GpsGate Cloud, the tracker may take a while to switch. Teltonika trackers can hold onto old server configurations, and in some cases, it can take up to an hour before they start sending data to the new destination. To speed this up, you can reset the tracker:

If the tracker still isn't connecting after the reset, you can force it to flush all stored connection data and re-initialize with the current server settings

Where:
1.# - IMEI.
2.# - APN.
3.# - LOGIN.
4.# - PASS.
5.# - IP.
6.# - PORT
7.# - MODE (0-TCP/1-UDP).
Note: You can select one or multiple options.

Also, you can delete all records from the SD card.

Summary: