Hello dear Fernando Brochetto,
Thank you for your proposal. I have prepared a little information and comments on your idea.
we use the trackers in a mode that when they are without GPRS, they send first the last location and then the buffered messages. This always cause counters to be calculated in a wrong way, creating an inaccuracy of the data received by the platform (always for greater).
I think you know there are currently 2 methods of processing in the Wialon:
1. Real-time Data Processing and data recalculation (events system).
2. Processing messages from the Database upon Request.
When you say recalculations, you are talking about the first method, which is not applied everywhere. For example, at the moment, the counters values in the Wialon Hosting interface (in the tooltip, for example) are calculated by messages (the second method) in online mode. In this regard, the messages coming from the black box are processed correctly and should not cause any problems.
Based on the above, we can conclude: since the interface in the calculation of counter values does not use events, no recalculation is required.
I can't say that there can't be problems with the counters for other reasons, so you need to deal with specific cases and look for the cause (e.g. the Timeout and Maximum interval between messages options are only accounted for in reports and do not work for online counters, so there may be issues with the calculation of the counters).
If you have any questions about the counters, please send cases for review in private messages.
Other thing is that sometimes the mobile app doesn't show any trip when the delay of messages is too long (more than three days, for example)
Indeed, in a trip situation there may be a discrepancy between the mobile app and the Hosting, in particular due to black box messages. This is because messages uploaded from the black box older than one day are not included in the events for online registration. It is therefore necessary to recalculate the events in one of two ways:
1) contacting technical support;
2) changing the settings. You can change the unit properties in Advanced, Trip Detector, Sensors tabs and after 15 minutes the data will be recalculated automatically (you can change to another value, save and then return the required value afterwards). However, the recalculation period is dynamic, i.e. if you open the mobile app's trip history for example for 10 days, the trips in that period will be recalculated.
The platform could have a new improvement, a task for recalculating data for a X period, this would fix the error of counters and sync the data between the mobile app and Wialon.
As for adding a new button (new function) to user interface, it is not a new suggestion - we have already discussed this issue some time ago. But here we have some concerns about frequency of using it: if users use it too often (I think you know that undiscovered buttons are used not only when needed, but also for fun), then we may get a very heavy load on servers, which can lead to incorrect calculation of events.
What conclusion can be formulated: at the moment we need to improve the registration of events, taking into account messages from the black box older than 24 hours. In this case, the events will be recalculated taking into account these messages, respectively, there will be no discrepancies that you describe.
We have already created such a task. When I have news on the implementation timeline, I will let you know.
Business Analyst, Wialon