Trip reports not working properly (6.10)
Ignition seems not being taken into account, altough I can see in each device when it's on or off so is properly reported by devices and received and processed by traccar server.
Are you doing reports for more than one day? If yes, I recommend trying for one day to see if it works.
If still not, you should check raw positions and see why trips are not triggering correct.
Hello Anton, thanks for your anser.
Trips for today give only one instance but is only a drift, not any actual trip. (any device)
I can see all devices realtime in their actual position, can watch them move and positions report gives everything correctly.
¿What you call raw positions?
Positions report.
Positions report comes perfect.
What do you mean by perfect? You should check the data from that report against the trips logic to see why it's not working.
I don't understand what your speaking about. ¿what trips logic?
Positions report shows all positions from the vehicle from start to finish at the defined time lapse correctly reporting ignition on and motion, while showing no motion on certain long periods when the vehicle is stopped and reporting ignition off.
Altough, trips report shows only the times when the vehicle is stopped and has a drift while ignition off and nothing when in motion with ignition on and having LONG displacements. (if that's the trip logic you meant)
traccar.xml has no related parameters defined since none made it work correctly.
The only thing that might be outside the scope is report.trip.minimalNoDataDuration (which I never used/redefined) but devices have ignition on and off reporting, and trips are not being defined by it's use, altough I had report.trip.useIgnition enabled.
Will try some changes anyway.
Minimal.no.data.duration = 600 the same.
report.trip.useignition = true the same.
report.fastthresold = 604800 and asking a 2 day report... the same.
trip report for past week or this week gives me a drift from the first day of the week
I know, I read it already, but it's all as it should be and still trips are not correctly calculated/shown.
I take my bike and go out on a 40 minutes trip (way more than report.trip.minimalTripDuration=default), stoping only on red lights and some intersections, never more than 300 seconds. (5 minutes, an eternity for report.trip.minimalParkingDuration=default)
Let my bike at the store door for over one hour (way more than report.trip.minimalParkingDuration=default) and get back home making the same 18.5 Km city trip. (way more than report.trip.minimalTripDistance=default)
My bike GPS receives 12V from ignition, so it reports when is on and of... And no matter what I use on report.trip.useIgnition the result is the same.
I get a trip only for ONE drift INSIDE THE GARAGE at the selected period start, no mather if 2 days, 1 week or the whole month chosen. That drift is no more than 50m.
And yet, igntion on and off gets shown in the events report, while each and every position is shown in the positions report.
Might this be something inherited from some error in prior versions?
Something inside the database, some stored config that might have gotten corrupt?
There's no point in guessing. You should just check the data.
Ok, I found something.
When the device stops, next position/s get filtered by static filters. (log says)
After 5 minutes (and all this positions filtered by static filters, so none saved) device stops sending reports because enters power saving mode.
So there's no 0 speed gap on time. Next report is a motion one, with speed as soon as the device detects motion and leaves power saving.
The problem is, If I disable static filter, devices that have no power saving will keep filling the database with useless positions. (the reason I enabled it in the first place)
And also, in past versions, trips were correctly reported with this same settings and the same devices.
¿perhaps something changed in the logic now makes this "odd" behavior to occur with same settings?
Since Traccar 5.xx I have not being able to properly see the trips.
Some versions back (still 6.xx, some early version/s) trips directly didn't appear. Then I read about some parameters, which I changed and trips started to be properly reported.
(report.trip.minimalTripDuration, report.trip.minimalTripDistance, report.trip.minimalParkingDuration, report.trip.minimalNoDataDuration)
But then, after some update (lost track of it) they were not working again.
I added "report.trip.useIgnition" and it made no difference. (so I removed it again, but never removed former 4 parameters)
Now I'm in the last version and trips still not properly reported. Only trips with values UNDER those defined/forced in the former 4 parameters are being reported. So I'm getting trip reports about just GPS drift while parked.
Removed former 4 parameters keeping useIgnition and now ALL the trips of the day are reported AS ONE trip, altough my device reports ignition.
Also added "report.fastThreshold" with value for 1 month and I receive a java error. Value for 1 week gives me only 1 drift report from last sunday.
I tought still without adding any of this parameters, trips for the day should be correctly reported/calculated, since default values are good enough for most cases, but yesterday I made a 2 way trip with almost 1 hour pause between stop and start to get back and is reported as ONE full trip.
Other devices get ALL DAY trips reported as only one trip, and most cases pauses are long enough. (1/2 hour)