3.9 not generating trips consistently

SveinHa8 years ago

Hi all.

Have been using Traccar 3.9 for a few days and there seems to be some problems generating trips.

My tracker sends position data every minute when the car is running (tracker connected to ignition switch). I can follow the car on the map and data is stored as "Route" with all position points visible but only occationally I find "Trip" data. Example: Today the car was started at 07:43 and driven continously to 07:57, a distance about 15 km at speed mostly between 50 and 60 km/h. I would assume there would be generated a trip a few minutes after the car was stopped, after trip timeout was run out but even a few hours later there is no trip data, only Route.

The configuration file do not have entrys for trip calculations so I assume the default values at 500 meters and 300 seconds apply, they should work fine bur trips still don't appear as I would expect.

Any good ideas what to look for?

SveinHa8 years ago

Route, Events and Summary seems ok, only Trips missing.

abyss8 years ago

Hello,

Only last trip is not showed? Or any trip?

Also, please, could you check speed value in the first and in the last position of possible trip.

SveinHa8 years ago

Speed value is NOT zero in first or last position and it will probably only be zero every now and then since the tracker fires up when the car does and need some time to get position fix and report it to Traccar.

Here is one complete route which did NOT end up in a trip, hope it is readable:

							
Report type:	Route						
                            
Device:	L322						
Group:	Default						
Period:	2016.12.30 00:00:00 - 2016.12.30 09:00:00						
                            
Valid	Time	Latitude	Longitude	Altitude	Speed	Address	Attributes
SANN	2016.12.30 07:43:31	59,291850	5,292100	0 m	57.0 km/h	Rv47, Kopervik, Rogaland, NO	status=00000000  charge=true  ignition=false  odometer=0  ip=2.150.48.99  distance=103.98  totalDistance=108451.6
SANN	2016.12.30 07:44:01	59,295630	5,292193	0 m	62.0 km/h	Rv47, Kopervik, Rogaland, NO	status=00000000  charge=true  ignition=false  odometer=0  ip=2.150.48.99  distance=420.82  totalDistance=108872.42
SANN	2016.12.30 07:44:31	59,300830	5,291502	0 m	70.5 km/h	Rv47, Rogaland, NO	status=00000000  charge=true  ignition=false  odometer=0  ip=2.150.48.99  distance=580.19  totalDistance=109452.61
SANN	2016.12.30 07:45:01	59,305757	5,287025	0 m	73.4 km/h	Rv47, Rogaland, NO	status=00000000  charge=true  ignition=false  odometer=0  ip=2.150.48.99  distance=604.57  totalDistance=110057.18
SANN	2016.12.30 07:45:31	59,311168	5,288477	0 m	76.9 km/h	Rogaland, NO	status=00000000  charge=true  ignition=false  ip=2.150.48.99  distance=608.04  totalDistance=110665.22
SANN	2016.12.30 07:46:02	59,316903	5,291575	0 m	74.9 km/h	Rv47, Rogaland, NO	status=00000000  charge=true  ignition=false  ip=2.150.48.99  distance=662.24  totalDistance=111327.46
SANN	2016.12.30 07:46:32	59,321055	5,291145	0 m	39.9 km/h	Rv47, Rogaland, NO	status=00000000  charge=true  ignition=false  odometer=0  ip=2.150.48.99  distance=462.81  totalDistance=111790.27
SANN	2016.12.30 07:47:02	59,325270	5,286515	0 m	64.4 km/h	575 Karmøyvegen, Rogaland, NO	status=00000000  charge=true  ignition=false  odometer=0  ip=2.150.48.99  distance=537.87  totalDistance=112328.14
SANN	2016.12.30 07:47:32	59,329477	5,282653	0 m	65.9 km/h	520 Karmøyvegen, Rogaland, NO	status=00000000  charge=true  ignition=false  odometer=0  ip=2.150.48.99  distance=517.09  totalDistance=112845.23
SANN	2016.12.30 07:48:02	59,333252	5,278920	0 m	55.0 km/h	478 Rv47, Rogaland, NO	status=00000000  charge=true  ignition=false  odometer=0  ip=2.150.48.99  distance=470.67  totalDistance=113315.9
SANN	2016.12.30 07:48:33	59,337477	5,276622	0 m	48.2 km/h	Rv47, Rogaland, NO	status=00000000  charge=true  ignition=false  odometer=0  ip=2.150.48.99  distance=488.09  totalDistance=113803.99
SANN	2016.12.30 07:49:03	59,340662	5,276112	0 m	54.8 km/h	Rv47, Rogaland, NO	status=00000000  charge=true  ignition=false  odometer=0  ip=2.150.48.99  distance=355.73  totalDistance=114159.72
SANN	2016.12.30 07:49:33	59,342655	5,275343	0 m	41.6 km/h	Rogaland, NO	status=00000000  charge=true  ignition=false  odometer=0  ip=2.150.48.99  distance=226.14  totalDistance=114385.86
SANN	2016.12.30 07:50:03	59,347032	5,274807	0 m	28.7 km/h	Rogaland, NO	status=00000000  charge=true  ignition=false  ip=2.150.48.99  distance=488.16  totalDistance=114874.02
SANN	2016.12.30 07:50:34	59,351212	5,276805	0 m	56.8 km/h	E134, Rogaland, NO	status=00000000  charge=true  ignition=false  ip=2.150.48.99  distance=478.94  totalDistance=115352.96
SANN	2016.12.30 07:51:04	59,354522	5,277307	0 m	11.4 km/h	237 Karmøyvegen, Rogaland, NO	status=00000000  charge=true  ignition=false  ip=2.150.48.99  distance=369.57  totalDistance=115722.53
SANN	2016.12.30 07:51:34	59,357948	5,276618	0 m	53.3 km/h	2 Peder Skeievegen, Avaldsnes, Rogaland, NO	status=00000000  charge=true  ignition=false  odometer=0  ip=2.150.48.99  distance=383.45  totalDistance=116105.98
SANN	2016.12.30 07:52:04	59,361810	5,278167	0 m	51.4 km/h	156 Karmøyvegen, Rogaland, NO	status=00000000  charge=true  ignition=false  ip=2.150.48.99  distance=438.76  totalDistance=116544.74
SANN	2016.12.30 07:52:34	59,365270	5,279797	0 m	28.2 km/h	112 E134, Rogaland, NO	status=00000000  charge=true  ignition=false  ip=2.150.48.99  distance=396.11  totalDistance=116940.85
SANN	2016.12.30 07:53:04	59,365203	5,274168	0 m	51.1 km/h	31 Torvastadvegen, Rogaland, NO	status=00000000  charge=true  ignition=false  odometer=0  ip=2.150.48.99  distance=319.35  totalDistance=117260.2
SANN	2016.12.30 07:53:35	59,366358	5,267932	0 m	53.3 km/h	80 Torvastadvegen, Rogaland, NO	status=00000000  charge=true  ignition=false  odometer=0  ip=2.150.48.99  distance=376.41  totalDistance=117636.61
SANN	2016.12.30 07:54:05	59,368952	5,261600	0 m	57.9 km/h	127 Torvastadvegen, Rogaland, NO	status=00000000  charge=true  ignition=false  odometer=0  ip=2.150.48.99  distance=460.78  totalDistance=118097.39
SANN	2016.12.30 07:54:35	59,371725	5,255582	0 m	62.8 km/h	169 Torvastadvegen, Rogaland, NO	status=00000000  charge=true  ignition=false  odometer=0  ip=2.150.48.99  distance=460.24  totalDistance=118557.63
SANN	2016.12.30 07:55:05	59,375468	5,251055	0 m	63.0 km/h	216 Torvastadvegen, Rogaland, NO	status=00000000  charge=true  ignition=false  odometer=0  ip=2.150.48.99  distance=489.43  totalDistance=119047.06
SANN	2016.12.30 07:55:35	59,377128	5,251032	0 m	48.5 km/h	180-200 Fv843, Rogaland, NO	status=00000000  charge=true  ignition=false  ip=2.150.48.99  distance=184.8  totalDistance=119231.86
SANN	2016.12.30 07:56:06	59,377387	5,254897	0 m	25.7 km/h	15 Bjørgestien, Rogaland, NO	status=00000000  charge=true  ignition=false  ip=2.150.48.99  distance=221.04  totalDistance=119452.9
SANN	2016.12.30 07:56:36	59,379078	5,256717	0 m	23.8 km/h	41 Bjørgestien, Rogaland, NO	status=00000000  charge=true  ignition=false  ip=2.150.48.99  distance=214.74  totalDistance=119667.64
SANN	2016.12.30 07:57:06	59,379965	5,258415	0 m	6.7 km/h	61 Bjørgestien, Rogaland, NO	status=00000000  charge=true  ignition=false  odometer=0  ip=2.150.48.99  distance=137.9  totalDistance=119805.54
SANN	2016.12.30 07:57:06	59,379965	5,258415	0 m	6.7 km/h	61 Bjørgestien, Rogaland, NO	status=00000000  charge=true  ignition=false  odometer=0  ip=2.150.16.249  distance=0.0  totalDistance=119805.54
SveinHa8 years ago

Heading slightly messed up, it is Altitude that is 0, Speed is 57.0 km/h on the first line.

abyss8 years ago

Trips detector relies on speed. You can play with event.motion.speedThreshold parameter to adjust speed less than that considered to be parking. But if your trip starts from 57 km/h it will not help.

I think you need adjust behavior of your device to switch on earlier, improve antenna or something.
Your device should report some small speed at the beginning and at the end of trip to be correctly detected.

SveinHa8 years ago

That means that I have to power my tracker 24/7 which in turn uses a lot of data when tha car is parked.

I had hoped that "device lost" would be equal to "Parked" or "End trip". As long as the tracker powes up with the car, it will be a normal situation that the first logging is far from zero speed.

SveinHa8 years ago

A few days ago, I had the tracker powered on 24/7 and it generated lits of trips with the car stationary:

Report type:	Trips							
                                
Device:	L322							
Group:	Default							
Period:	2016.12.25 00:00:00 - 2016.12.25 09:00:00							
                                
Start	                Start Address	                End	                End Address          	Duration	        Length   	Top speed	Average speed	Spent Fuel
2016.12.25 01:06:55	61 Bjørgestien, Rogaland, NO	2016.12.25 01:27:55	61 Bjørgestien, Rogaland, NO	0 h 21 min 0 s	0.0 km	0.5 km/h	0.1 km/h	-
2016.12.25 02:07:56	61 Bjørgestien, Rogaland, NO	2016.12.25 02:13:56	61 Bjørgestien, Rogaland, NO	0 h 6 min 0 s	0.0 km	0.2 km/h	0.1 km/h	-
2016.12.25 03:07:00	61 Bjørgestien, Rogaland, NO	2016.12.25 03:24:00	61 Bjørgestien, Rogaland, NO	0 h 17 min 0 s	0.0 km	0.3 km/h	0.1 km/h	-
2016.12.25 03:39:02	61 Bjørgestien, Rogaland, NO	2016.12.25 03:49:03	61 Bjørgestien, Rogaland, NO	0 h 10 min 1 s	0.0 km	0.1 km/h	0.0 km/h	-
2016.12.25 05:52:08	61 Bjørgestien, Rogaland, NO	2016.12.25 05:57:08	61 Bjørgestien, Rogaland, NO	0 h 5 min 0 s	0.0 km	0.1 km/h	0.0 km/h	-
2016.12.25 06:33:10	61 Bjørgestien, Rogaland, NO	2016.12.25 06:41:10	61 Bjørgestien, Rogaland, NO	0 h 8 min 0 s	0.0 km	0.1 km/h	0.1 km/h	-
2016.12.25 07:47:13	61 Bjørgestien, Rogaland, NO	2016.12.25 07:57:14	61 Bjørgestien, Rogaland, NO	0 h 10 min 1 s	0.0 km	0.2 km/h	0.1 km/h	-
2016.12.25 08:14:14	61 Bjørgestien, Rogaland, NO	2016.12.25 08:23:15	61 Bjørgestien, Rogaland, NO	0 h 9 min 1 s	0.0 km	0.7 km/h	0.2 km/h	-
Anton Tananaev8 years ago

As abyss pointed out, trips use speed value. Your device reported speed when stationary, so you see several trip. You can fix it by increasing threshold.

SveinHa8 years ago

Ok, thanks for info. That means that when the tracker is connected to the car's ignition, it will only rarely generte trips. As long as the route is generated reliably, Traccar it do the job well enough. Maybe a future upgrade may handle my situation.

Anton Tananaev8 years ago

You don't need a future update. You just need to configure Traccar. Every use case is different, so it's not possible to have defaults that work for everybody. You need to tweak parameters to make them work for you.