Skip to main content
CFG tool - checking CFG or DIFF files (SP)
Albert Basiul avatar
Written by Albert Basiul
Updated over 7 months ago

THIS TOOL IS FOR INTERNAL USE ONLY.

The CFG check tool is used to assist in checking settings that can easily be missed, reducing the risk of human error when troubleshooting a CFG file or creating a DIFF file.

The tool:

  • Checks specific settings in CFG files and warns of any potential issues/provides recommendations

  • Lists what CFG IDs are changed by applying a DIFF file.

Please note that this tool is not meant to be a replacement for general troubleshooting.

Check the attachment at the bottom of the page to download the tool.

Using the tool

  1. Download the attached ZIP file below and extract the files into any directory or new folder

  2. Put the CFG or DIFF file in the same directory as the tool and drop it onto the “cfgtool_x.x.x.exe” executable file:

    mceclip0.png
  3. You might receive a warning from Windows Defender about an unrecognised app, run the app anyway:

    mceclip1.png
    mceclip2.png
  4. A terminal window should pop up. If you’re opening a CFG file the table might be too wide for the window, simply resize it or maximize it to make the table look right. You might also need to scroll up if there is a lot of text.

Example of an opened CFG file:

mceclip3.png

Example of an opened DIFF file:

mceclip4.png

CFG warnings

The primary function of the tool is to warn of any potential issues or provide recommendations based on some settings in the CFG file.

The tool is currently capable of checking the following (more will be added in the future):

Data sending/connection settings:

  • IP1 =/= IP2, Two Servers turned off

  • IP1 or Port1/Port2 are empty

  • APN name is empty

  • TT2 IP used, wrong protocol/port selected

  • TT2 IP used, “Newest record first” used

  • Periodical redirect is on, “Period” > 0

  • Send data without GPS fix/Offline tracking is on

  • Identification string used

  • Send only record data if triggered by time, distance or course is on

  • Data sending > Period is 0

Data consumption:

  • Coefficient data generation high (distance, time with engine or radial)

  • DMP connection frequency higher than twice a day

  • J1939 + DTC with TT2 IP

Location accuracy:

  • Not every GNSS constellation enabled

  • Antenna selection set to Internal or External

GSM settings:

  • Temporary blacklist not enabled

  • Network mode check added

Phone and SMS:

  • Use ID in SMS commands enabled

Other

  • IP1 is TT2, accident reconstruction is on

  • Eco-Drive beeper/buzzer

  • "Send I/O data with v1.1 protocol" disabled

DIFF file output

If you open a DIFF file with the tool you will get a list of unparsed and parsed IDs – these are all the IDs that the DIFF will change in the CFG of the device.

Unparsed IDs – unknown/unnamed CFG IDs

Parsed IDs – known/named CFG IDs, mostly taken from here: https://doc.ruptela.com/articles/#!tracking-devices-publication/configuration-parameters

In the future, Parsed IDs will be properly formatted to make their values easy to read.

For example, if you created a DIFF file that only changes IP1, then you should see something like this:

mceclip5.png

You can see that there is only one parameter with “Parameter name – IP1 server address”.

If other unplanned changes were made (in this example some Eco Drive settings were changed as well) you might see more IDs:

mceclip6.png

You can see that besides “IP1 server address” there is also “Beeper enabled” and 1 more unparsed ID. If you only need to change IP1 it would be better to try and make the DIFF file from scratch.

This might also be useful if a client was applying DIFF files and some settings changed unexpectedly, the DIFF file can be checked with this tool.

NOTES:

  • This tool is not very useful for checking IO parameters, as it currently doesn’t parse IO parameters.

  • Since the tool doesn’t check IO parameters well, changing CAN modes (FMS, LCV, HCV etc.) can result in a lot of unparsed IDs being listed because of IO parameter disabling/enabling, so the tool is not very useful for checking that either.

Reading DIFF parameter values

If needed, you can check the values of CFG IDs in the DIFF file output. In the future, Parsed IDs will be properly formatted to make their values easy to read.

For now, if you want to check their values in the list, the general rules to read them are:

  1. If the parameter contains text (e.g., IP address) you will likely see the value in ASCII:

  2. If it contains numbers (e.g., Port), you will likely see the value in Decimal

  3. If it is a parameter with two states (on/off, checkbox, e.g., Two Servers) you will see the value in Decimal (0 – off, 1 – on)

There are exceptions like GNSS constellations or Send data without GPS fix/Offline Tracking, but the above should be enough for checking the value of a basic parameter. You can also look at the Configuration parameters document to reference the values and their meanings for each known parameter.

Did this answer your question?