Find your next step

1. Get the platform settings

   Obtain the server address, port and supported device type from the platform provider. Create the object with the identifier it requires.

2. Configure the tracker

   Set mobile-data access and server settings, write the configuration, and enable the telemetry fields you need.

3. Verify incoming data

   Inspect actual incoming platform messages, not only values in Configurator. Do not copy a port from another model or platform.

4. For your own server

   Implement the NTCB/FLEX identification, mask negotiation and acknowledgements described in the examples.

The current list of supported vehicles and available CAN decoding files is published in DRC.

1. Check the wiring and voltage

   Connect CAN High to CAN High and CAN Low to CAN Low. With the vehicle electronics active, measure each line relative to vehicle ground. Both lines are typically close to 2.5 V when the bus is recessive. During communication, CAN High rises toward approximately 3.5 V and CAN Low falls toward approximately 1.5 V, so a multimeter may show an averaged value within these ranges.

   If a multimeter is unavailable, a device input configured as an analog input can be used temporarily to check the line voltage. Disable voltage averaging so changes are not smoothed out.

2. Check for raw CAN traffic

   Enable the CAN interface and use Passive mode for the initial test. Open CAN Spy, select the CAN interface of the connected device and run Auto Detect to identify the baud rate. You can also select the baud rate manually and click Start.

   When the connection is correct, captured messages appear in the Messages table. If the baud rate is detected but only about five messages or fewer are visible, try another CAN connection point. If no baud rate is detected, recheck or swap CAN High and CAN Low and verify that the selected twisted pair is actually a supported CAN bus.

3. Configure decoded data transmission

   After raw messages are visible, select the correct decoding file in CAN Spy and write it to the device. Then open the device configuration and enable transmission of the required decoded parameters on the Data Transfer tab before writing the configuration to the device.

1. Check the device

   In NTC Configurator, verify power, cellular registration, GNSS validity and values from connected CAN equipment and sensors.

2. Check transmission

   Enable the required fields in Protocol Settings and write the configuration to the device.

3. Check the platform

   Verify incoming messages and timestamps, then check sensor mapping, units and displayed values. Updating values in Configurator alone does not prove that the complete installation is working.

4. Test actual events

   Test the configured ignition, inputs and connected equipment under the intended operating conditions before completing the installation.

Whenever the installation permits, connect the tracker’s power input directly to the vehicle’s low-voltage battery through the fuse specified in the wiring diagram. The battery is generally the most stable available supply point.

Avoid taking power from accessory circuits, lighting circuits or other loads when possible. Switching and voltage fluctuations at these points can cause resets or unreliable operation.

Connect GND directly to the battery’s negative terminal or to a reliable vehicle ground. The contact point must be clean and secure. Avoid painted, corroded or mechanically unstable grounding points.

Always follow the connection diagram for the exact device model.

All Navtelecom tracker models in the START, SMART and SIGNAL series support an operating supply voltage of 9.5–47 V DC.

All models include power-input overvoltage protection up to 200 V. This is a protection rating, not an extended operating range: do not power the tracker above 47 V DC.

All models also include reverse-polarity protection. These protections do not replace correct wiring or the required fuse.

Send the following information in one request so Technical Support can begin investigating without asking for basic details:

1. Device identification

   Exact model and IMEI

2. Software versions

   Device firmware version and the version of NTC Configurator used

3. Configuration

   The current device configuration file

4. Issue description

   What you expected, what actually happened, and the exact date, time and time zone of the problem. Mention whether the issue can be reproduced.

5. Telemetry data for the affected period

   Always attach the relevant telemetry interval. It can be downloaded over a USB cable, through the mobile application, or remotely through NTC Configurator/RCS.

6. Relevant debug log

   For cellular issues, record a GSM debug log. For connected equipment or interface issues, record the applicable RS-232 or RS-485 debug log. These debug logs can be recorded only while the device is connected by USB.

A precise timestamp and the complete supporting data significantly reduce diagnostic time.

Send *?DIAG 1 by SMS to the phone number of the SIM installed in the tracker, then follow the branch that matches the result.

If the issue remains, connect to NTC Configurator when possible, check Telemetry Data and send the configuration, diagnostic reply and telemetry from the affected period to Technical Support.