Info: Renault AAOS VHAL does weird stuff.

[Ixam97]

This is strange behaviour I encountered while a tester used my app on his Megane E-Tech.

Renault seems to have a broken implementation of the Vehicle Hardware Abstraction Layer, causing it to report implausible values to apps using it. In case of EVMap this affects die displayed state of charge in the vehicle infos:

The SoC did not change at all. The logs made by my app tester revealed the following:

16.02.2023 03:28:15.755: Display distance unit: 35
16.02.2023 03:28:15.755: Car name: BCB, Renault, 2021
16.02.2023 03:28:15.755: Max battery Capacity: 6553500.0 // (0xffff * 100).toFloat() ???
// ...
16.02.2023 03:28:15.915: Additional data:
    Speed in m/s:        0.0
    Power in mW:         17857.145 // 18W while charging with 11kW
    Gear selection:      4
    Connection status:   true
    Battery level in Wh: 34700.0
    Ignition state:      3
    Ambient temperature: 11.0
// ...
16.02.2023 03:30:54.113: DRIVE STATE: CHARGE -> PARKED
// ...
16.02.2023 03:30:56.469: Additional data:
    Speed in m/s:        0.0
    Power in mW:         Infinity // (confused unga bunga)
    Gear selection:      4
    Connection status:   false
    Battery level in Wh: 35000.0
    Ignition state:      3
    Ambient temperature: 11.0

There is nothing that can be done inside of an app to fix what ever this c*** is, except for maybe setting a fixed battery capacity value.

Since this is nothing that hurts EVMap's primary functions this isn't a big issue (while tt is for my own developement 🙃). This is just meant to be a little side note if anyone driving a Renault complains about this.