Skip to main content
Trip history cannot be loaded
Albert Basiul avatar
Written by Albert Basiul
Updated over 7 months ago

Description:

TT2 will stop trip calculations if too many ignition changes are detected in a very short time. This is to prevent TT2 servers from collapsing due to excessive trip calculation jobs.

When this happens, the following message will be shown in the History module of the object affected:

mceclip0.png

Common causes:

This issue is caused by excessive ignition state changes and it usually relates to a DIN short circuiting (changing from 0 to 1 many times in a short time).

mceclip1.png

Required information:

Information initially needed in order to troubleshoot the issue (plus who needs to provide it)

IMEI or other object identifier

Steps:

1- Login to LCM superadmin.

2- Go to Objects.

3- Search the object and click on View/Edit

4- Ascertain Ignition detection source.

mceclip2.png

5- Login as admin to client's TT2 account.

6- Go to Analyse by coordinates of said object and check if ignition detection source is reliable or not.

mceclip3.png
  • If it has too many ignition changes in a very short time frequently it should be discarded and an alternative ignition detection source should be selected in LCM objects settings: Power Supply Voltage, Speed, RPM, etc).

  • If excessive ignition change has only been a temporary issue, ignition source can be kept as it is.

7- Login to https://tt2-admin.ruptela.com/ (use your general credentials)

8- Go to Incompatible objects.

9- Search object by TT2 id.

10- Click on Resolve.

mceclip1.png

Trip calculation is now unblocked, but will be blocked again if excessive ignition is detected again.

Further reading:

Did this answer your question?