So our business has an increasing number of customers that track Trips and Stops for business purposes.
We've turned on report.trip.useIgnition (True) for one of the newer ones due to the way they drive to customers or around customer properties, and it looks good. Just to confirm though, do these two still apply when the ignition is turned off:
- report.trip.minimalTripDistance (default, 500 metres)
- report.trip.minimalTripDuration (default, 300 seconds)
I am assuming so, because the logic would state that "Use Ignition will indeed mark a Stop, but it won't be considered as a new trip if the distance or time travelled after the ignition was turned back on did not exceed either of these values".
So I guess the real question is why wouldn't I make report.trip.useIgnition set to True in the config file.
You wouldn't if the ignition value is inaccurate, which is pretty common.
Of course, duh. Yes, that was the answer I needed.
We do have customers whose devices track ignition by voltage and with modern smart charging systems it's highly inaccurate. For our immobiliser systems its 100% reliable but that's not every vehicle.
So our business has an increasing number of customers that track Trips and Stops for business purposes.
We've turned on report.trip.useIgnition (True) for one of the newer ones due to the way they drive to customers or around customer properties, and it looks good. Just to confirm though, do these two still apply when the ignition is turned off:
I am assuming so, because the logic would state that "Use Ignition will indeed mark a Stop, but it won't be considered as a new trip if the distance or time travelled after the ignition was turned back on did not exceed either of these values".
So I guess the real question is why wouldn't I make report.trip.useIgnition set to True in the config file.