Teltonika fmb920 ECO DRIVING

Youssef7 months ago

Hi,
I have ECO DRIVING activated in teltonika fmb920 and all my settings are correct in the tracker side. Therefore in my Traccar device details table all IO's are there, but don't have io253 and io254 related to eco driving. Any suggestions?

Anton Tananaev7 months ago

If you don't see it, probably your device is not reporting those IOs.

Youssef7 months ago

Normally the fmb920 does support it on teltonika configurator it is activated on the device.

Anton Tananaev7 months ago

If you don't trust me, you can check raw data in the logs to confirm.

Youssef7 months ago

Sorry I am here because I trust you. I am just reporting what I have got from the device and what teltonika says in their Data Sending Parameters ID. Anyway thank you Anton.

Rodolfo6 months ago

Hi Youssef, you should look for positions with attribute alarm:
The position attribute must contain an event with 253 as its value, and an alarm attribute with one of these values: "hard_cornering" | "hard_acceleration" || "hard_braking".

The traccar decoder already performs the conversion step for the friendly name.

Sasa Ahlan5 months ago

Thanks Rodolfo, I saw io253, but none for io254 which is green driving value.
My device send both io: 253 and 254, but I don't see io254 in traccar.
Is this not supported yet, or something I missed?

Anton Tananaev5 months ago

If you don't see io254, it means your device is not reporting it.

Sasa Ahlan5 months ago

Hello Anton, thanks for replying my message. I have set the configurator to allow teltonika fmb920 send to both servers, first server of gps-server cloud and second server is traccar at my laptop. there is io254 in gps-server but none in traccar. What could be causing the device sending this io into one server and not to other server ?

Anton Tananaev5 months ago

That's something you should ask Teltonika.

Sasa Ahlan5 months ago

Hello Anton, and I checked in the source code (TeltonikaProtocolDecoder.java), there is no id of 254.
There is id of 253 (green driving type) but none id of 254 (green driving value).
I copy here for reference:

        register(252, fmbXXX, (p, b) -> {
            p.set(Position.KEY_ALARM, b.readUnsignedByte() > 0 ? Position.ALARM_POWER_CUT : null);
        });
        register(253, null, (p, b) -> {
            switch (b.readUnsignedByte()) {
                case 1:
                    p.set(Position.KEY_ALARM, Position.ALARM_ACCELERATION);
                    break;
                case 2:
                    p.set(Position.KEY_ALARM, Position.ALARM_BRAKING);
                    break;
                case 3:
                    p.set(Position.KEY_ALARM, Position.ALARM_CORNERING);
                    break;
                default:
                    break;
            }
        });

        register(636, fmbXXX, (p, b) -> p.set("cid4g", b.readUnsignedInt()));
        register(662, fmbXXX, (p, b) -> p.set(Position.KEY_DOOR, b.readUnsignedByte() > 0));
Anton Tananaev5 months ago

And your point is?

Sasa Ahlan5 months ago

Is that because of that part of coding causing io254 not recorded in attributes? or not? Give me a clue at which point to debug so that I can ensure teltonika is sending the same data. Thanks in advance for your help.

Anton Tananaev5 months ago

No, it's not the issue. I already gave you a clue, but you ignored it.

Sasa Ahlan5 months ago

Ok then, I will update the configurator to switch the main server with second server, and see the results.