Why The Trip Odometer (io_199) always 0?

[Win]

FMB001, Why the Trip Odometer (io_199) always 0?

Wialon

prior=0, event_io_id=240, total_io=33, io_239=1, io_240=1, io_80=5, gsm=5, io_21=5, io_200=0, io_69=1, io_113=100, io_263=1, io_303=0, io_251=0, io_246=0, io_252=0, pdop=2.1, io_181=21, hdop=1, io_182=10, pwr_ext=12.715, io_66=12715, io_24=0, lac=1206, io_206=1206, pwr_int=4.128, io_67=4128, io_68=0, io_13=9, io_17=65394, io_18=65529, io_19=65505, io_15=1000, mcc=510, mnc=10, io_241=51010, io_199=0, io_16=62248878, io_12=2263724, io_449=1716075, io_11=894447750000, io_238=0, io_14=2591315, iccid=8944477500002591315

[Patrick_Sangalang]

Hello @Win,

I hope you are doing well. It seems that you were looking at the start of the event id 240 (Movement occurs), in this case, the Trip odometer would not be calculated as it is the start of the Trip.

Recommending you check on the proceeding records to confirm if there were Trip meters that were added to parameter 199.

I hope this helps.

Kind regards,
Patrick

[Win]

Hi Patrick,

thank you for your reply, I checked all the messages, all io_199 values are zero.

one example:

prior=1, event_io_id=239, total_io=38, io_239=1, io_240=1, io_80=5, gsm=0, io_21=0, io_200=0, io_69=1, io_1=0, io_113=100, io_263=1, io_30=0, io_31=21, io_33=0, io_35=22, io_37=32, io_38=252, io_759=1, pdop=1.4, io_181=14, hdop=0.7, io_182=7, pwr_ext=12.079, io_66=12079, io_24=32, cell_id=0, io_205=0, lac=0, io_206=0, pwr_int=4.1, io_67=4100, io_68=11, io_13=14, io_15=1000, io_36=1063, io_52=17, io_241=0, io_199=0, io_16=63859000, io_12=2284702, io_4=0, io_389=63859, io_390=270, io_11=894447750000, io_14=2591315, iccid=8944477500002591315, vin=MHRRW1880NJ202703

[Patrick_Sangalang]

Hello @Win,

Good day! Could you help to check if you have enabled the Trip Settings Feature on the Configurator?

I suspect, you only enabled the I/O Parameter in the Configurator but did not put priority on the Feature settings.

Kind regards,
Patrick S.

[Win]

20241103a.zip (7.0 KB)

the .cfg