Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Info: Renault AAOS VHAL does weird stuff. #269

Open
Ixam97 opened this issue Feb 16, 2023 · 1 comment
Open

Info: Renault AAOS VHAL does weird stuff. #269

Ixam97 opened this issue Feb 16, 2023 · 1 comment
Labels
android-auto api-limitation Issues that cannot be solved due to a limitation at the data source bug Something isn't working

Comments

@Ixam97
Copy link
Contributor

Ixam97 commented Feb 16, 2023

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:

image

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.

@johan12345
Copy link
Collaborator

Oh, thanks for the info! Hm yeah, we could set a fixed capacity value, but I guess the app can not really find out whether it's the 40 or 60 kWh variant.
Maybe it helps to report this in Google's issue tracker, but I guess it's rather something that Renault themselves need to fix... 😕

Also, based on the screenshot, it seems that the car doesn't have a compass sensor that is exposed to Android apps - same as on the Polestar.

@johan12345 johan12345 added bug Something isn't working api-limitation Issues that cannot be solved due to a limitation at the data source android-auto labels Feb 18, 2023
johan12345 added a commit that referenced this issue Feb 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
android-auto api-limitation Issues that cannot be solved due to a limitation at the data source bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants