[leo]

Hi @cytoplyu@gmail.com, apologies for the delay.

dev_idle and vehicle_dev_idle are in fact cumulative values, dev_idle is the devices hardcoded value that increments until there’s a device change.

while vehicle_dev_idle is a user editable offset from the dev_idle.

In most cases these are identical.

your best bet to get the time that a vehicle spends in Idle is to either use the counters API or the rawdata api with a resampled request.

example:

 

https://pegasus1.pegasusgateway.com/api/counters?vehicles=2600&from=2019-10-05T00:00:00&to=2019-10-05T23:59:59&tz=America/New_York&tz=America/New_York

https://pegasus1.pegasusgateway.com/api/rawdata?vehicles=2600&from=2019-10-05T00:00:00&to=2019-10-05T23:59:59&tz=America/New_York&fields=dev_idle,vehicle_dev_idle&resample=event_time&freq=31D&how=dev_idle:diff,vehicle_dev_idle:diff&tz=America/New_York

in both responses the data is returned in seconds.

"dev_idle": 4261.0

 

 

 

[leo]

The rawdata API has different fields for the odometer of a device and each field has it’s own function.

vo – Virtual odometer, raw value from the device, calculated by the GPS positions
dev_dist – Adjusted odometer, fills nulls values and has useful filters
vehicle_dev_dist – Odometer defined by the user, this value is commonly set as the odometer of the vehicle, and it increments along with the dev_dist value.

Use
vo – should not be used, it’s a raw value that can be null from the device
dev_dist – should be used to calculate distances traveled, it has filters fills null values
vehicle_dev_dist – since this value is user editable, it’s useful to know the total final value of the vehicle’s odometer.

When you use the ECU monitor accesory, the value can come in as:
ecu_distance – raw value from the vehicle’s engine
ecu_dist – adjusted value with filters and no null values
vehicle_ecu_dist – engine odometer editable by the user, increases with the ecu_dist

Use
ecu_distance – should not be used, it can contain null values
ecu_dist – should be used to know the actual total distance traveled by the vehicle
vehicle_ecu_dist – it’s optional, but we have seen cases where the odometer on the vehicle’s dashboard is not the same as the odometer being read by the ECU monitor.

The vehicle’s odometer can be edited from the application using the Vehicle Counters app, visit the following forum for more information.
How to set the odometer of a vehicle

[leo]

Estimado,

En la proxima liberacion del firmware quedara de esta manera:

>QPV;GM<
>RPV;GM http://maps.google.com/maps?q=32.875687,-117.210678 ;ID=356612021234567< Saludos,

• This reply was modified 10 years, 9 months ago by leo.

[leo]

Estimado,

Disculpa la demora en responder su tema.

Este desarrollo es algo que lo hemos planeado para un lanzamiento futuro en el firmware del Syrus.

Muchas gracias pos su sugerencia.

[leo]

Hola Amanda,

Has intentado con la versión 2.1.20? La mas reciente?
El comando para actualizar a esta versión es el: >SXAFU0C< Una vez hecho puedes hacer las pruebas nuevamente y dejarnos saber. La otra cosa es que si se puede hacer un downgrade de firmware: Para bajar a la version 2.0.51 este seria el comando: >SXAFU1http://dctserver.com/otap/f/2y0a51/std/;syrmag;3620afd5;< Saludos,

[Author]

Posts