i have a fiat 500e hatchback 42 kw
iw would love to have OBD connection with ABRP, i there any way to help you ?
Just want to mention, we should also take care about the hatchback with the lower capacity (23,7 kWh/ 21,3 kWh netto usable), don't know if the same upper/lower fix SOC-values will work for this. I can provide some SOC-data / reports if needed
hy there. i am very glad to read that it works also with fiat 500e. please could you tell which dongle do you recommend? also for the security. thank you
I just added the poor mans fix with 5% top and bottom buffer until we get the proper display soc value. Also i added another command that hopefully should avoid the jumping values. Please try it again and let me know how it works.
From what I can see today it looks pretty promising. SoC looks good and so far no jumping values. Thanks so much!
Prior to your changes I was down to 2% and the App read 7%. Last night I fully charged which seemed to be after the update (also pushed the report bug button after the balancing finished at 07.04.2023 00:34). The App read a SoC of 100% correctly. After driving a bit there was a delta ob about 1.5 so sometimes 1 other times 2% difference.
App 94% Car 96%
App 82% Car 83%
Power Cruise Control showed 38.389kWh, when the car was fully changed. Just in case this is any help.
I can confirm. No jumping values (tested with power cruise control dongle). The SOC difference is between 1% and 2% (tested between 80% and 90%).
The application is definitely usable for me now. Thanks.
I also noted little deviations now between 1 and 2%.
@Samuel: you wrote that you put 5% buffer to both ends. Actually 4,7 kWh equals 11,2%, not 10%. You might want to give 5,6% buffer on both ends for us to try if this eliminates the little differences.
I think it might be a bit more buffer up top since the 5% at the bottom match very well in my test, but since you are right about the 11,2% I think it might be 5% at the bottom and 6,2% at the top.
Hi , something i noticed this weekend, when I brake and the car regenerates , ABRP always shows a positive value in the realtime data screen.
As for the wrong SoC there is one thing someone of you could do, so i can check this value myself. Either at a pretty high or at a pretty low SoC connect ABRP to your car via OBD, wait until it read OBD values a few times (you can see when the OBD dongle blinks, or the timestamp updates in the car settings page, where you see the telemetry values).
Then go to settings, scroll down to end, where there is a toggle button "show bug report button" and enable it, start a random route (calculate a route and click the navigate button) and then the bug report button should be visible on the map.
Once you click it, it will upload some data and logs to our servers and i can check the SoC command from that log. As the SoC command seems to contain multiple SoC values, one of these should be the right one, i just need to check which one.
The click on the bugreport button will copy a URL (you will see a short notification about that), please send that one to firstname.lastname@example.org and i will be able to check the logs. Also include the real soc the car reported at that time, so i can compare the values.
I just made first test (not with the described debug option but will do within the next days). All I can say is that I can't confirm the 5% shown below. For me it was 65% (Car) and 63% (OBD), so 2 % (points). Could also be 3 % (multiplied with 0,97). Will provide further data with lower SOCs.
SOC : exactly 5% less than what is show in the car.
91 in car -> 86 in ABRP
90 -> 85
89 -> 84
Degradation : 0% ? happy .. but ..no. (09/2020 - 48500Km)
Outside Temp : ok
Battery Temp : seems right
Power : ok
Location : Ok
Thanks. Let's wait for more feedback to see how the SOC compares. Maybe it's different among some model variants.
Is there a "simple" IOS/Android App that I can install to provide data to help u ?
SOC reports 5% lower than what is show in the Display, degradation is at 0% (possible but unlikely).
All other values seem fine.
Hi Samuel! Here are some data from my 500e Icon 42Kwh. It is true the SOC deviates a bit from what is shown to the user in the dashboard and what we can see from the OBD. I noticed that from 100 to 50 it deviates a bit then it gets correct from around 50's into the 20's and then it deviates again around 3 digits. Car Scanner also reports the same value for SOC. All the other values are pretty much correct.
Guess that's because the 500 has a 42kwh battery but only 37,3kwh usable so about 90% usable. So 100% charged should be around 95% OBD. At 50% ist should match and at 0% display it should read 5% on OBD. Same Buffer on top and bottom
Pedro, i commented again in your gist:
There are other values in the SoC command we could try which look promising. Could you please check?
After a short drive some values seem to have some issues sometimes and are sometimes correct. Battery temperature one time is correct with 9.0°C but the shows 95°C which should be 9.5°C I guess. Also the high voltage value 366V and 353V seem correct, 880V does not. Degradation looks all over the place. Power seem ok. SoC has the difference between gross and net SoC.
At start: Display 68% -> OBD 65%
At arrival: Display 52% -> OBD 51%
Compared the temperature values with power cruise control
Samuel, assuming that 37,3 kWh are used net from 42 kWh gross and the unused 4,7 kWh are split equally to the lower end and the top end of the battery, it is pretty easy to calculate the correct SoCs. I have done this in an Excel File., but unfortunately I cannot upload it here. I do not know whether this might help or not, or if there is a way to get the right values directly via OBD, but if you can implement calculations into ABRP for the SoC it might help. I have made screenshots to show you the formulas for two different ways to calculate the values.
@Thomas Kramm, as noone else reported these jumps in values, it could also be related to your dongle, that it reports data in a different format or something like that. Which one did you use?
@Connor_67 i would prefer to get the right values from OBD, i think we should be able to get it, so i would come back to this if we can not get it.
I can confirm those jumps.
Degradation, Temperature and Voltage seem to vary between plausible values and incorrect ones.
Which dongle do you use? We had these jumps on other cars with certain OBD dongles and it was gone when the user switched to another dongle. The reason was pretty simple, some dongles just don't respect the set headers and return the values from multiple ECU, which results in data from other ECUs that is not relevant.
I have another idea though, which we could try later on too if more people report issues.
@Samuel_ABRP I used the one that came in the Power Cruise Control Kit. Any other recommendations?
That one should be fine, i guess it is because we use a command, that might not be supported by every ELM327 version, i'll update the commands later and let you know, then we can check if it improves the weird values.
Ok. After work I plan to find an available AC charger and fully charge so I can check the fully charged OBD SoC/kwh to validate or correct my 5% upper and lower buffer assumption.
Please check the first response at top of this issue, if you can send me some data on a lower or higher soc value, those assumptions might not be relevant anymore, as i might be able to check this from returned data when compared to real data.
Hi guys i was able to retrieve the information from my fiat 500e.
In the gist i'm sharing the used init_commands, data_commands the returned data and the calculations to retrieve it. I'm also sharing print-screens from Car Scanner APP terminal that i used to get the information.
Very nice, thanks a lot. I will convert this into our own format and let you know when it is available.
The Jeep Avenger is a native Stellantis (rather based on what came from PSA before the fusion) car, those normally have the same PIDs all over their cars, so i would probably try those Stellantis PIDs we have first on that car.
Please add this car also with live data directly from ODB2 dongle?
Quando sarà possibile usufruire del servizio OBD per Fiat 500e?
If you want to speed up things you could provide a Json in this format:
I just saw that Car Scanner added support for the new 500e and i tested it on my 500e and it works really well! Is there any possibility to retrieve the PIDs and the calculations made so we can use them here on ABRP?
IoBroker has an adapter. You can read a lot on the Fiat. But how do you get things converted for Abrp?
Yep, got it. But my question is about the interface from your car to IoBroker running on RaspPi. Or are you saying, that this is just theory, meaning: IoBroker would show something in case there would be data but actually there is nothing ? Do you see real data from your 500e in IoBroker ? Regards Wolfgang
Just revisited your screenshot: Yes, looks like real data. But how do you get it from your 500e ?
yes i see the real dates. iobroker gets them from fiat. an adapter is written that connects to fiat like the fiat app and fetches its data from there.
Ok, thanks, got it. So this works just like Tronity: They read the data through the Fiat APP/API. But what we are searching here is CAN-Bus real time data during driving through an OBD adapter. But interesting anyway, thanks.
We know that one exists, but we wanted to make ABRP connect directly with the OBD dongle so we can have all the information necessary for the trips. And Power Cruise Control is a anual paid app just to see a bit of information, is a bit much.
Hi, has anything changed in regards of the 500e integration ? I have also one and would be also interested to use ABRP with a ODB2 Dongle for live data. Thanks Wolfgang
Hi, Will the new Fiat 500e 2020 Hatchback 42kWh get supported by the new live data from OBDII
Hi, is the Fiat 500e 2020 Hatchback 42kWh supported by the new live data from obd2 ?
Hi, any news about the Fiat 500e ODB PIDs ? I would love to use APRP with ODB2 real time data. If I can help on the reverse engineering, I've got a Vgate iCar Pro V2.3 which I can use with an Android or Windows APP. Best regards from France !
Hi, we are dependent on user or community input here. So if you know the commands let us know and we will integrate them immediately.
Hi Jean i came across a list of commands and PIDs for the 500e but i can't seem to be able to use them on my end to check if they work.
"22013C1" //AMBIENT regex 18DAF140
"22A0093" //CELL STATS regex 18DAF144
"22A00A1" //AMPERE regex 18DAF144
"22A0102" //SOC regex 18DAF144
"22A0115" //VOLT regex 18DAF144
"22A0292" //CAPACITY regex 18DAF144
"22A0404" //SOH regex 18DAF144
"22A0421" //12V BATT regex 18DAF144
"22F1A0A" //VIN regex 18DAF140
this looks very promising. Exactly what we need. What i still can't see here though is how to calculate the values from the response. Do you also have a calculation for the values? I can add these commands later and enable it for testers and give you that role for testing, so you can send us some data to verify the responses.
That's the thing, i don't have any examples of the responses that i get for each PID so i can't validate the calculations for the different values.
If you know any way i can use on android of mac to test this commands i would appreciate it.
I have a 500e and an ODB2 dongle. If someone could advise me on a OBD app (IOS) that works on a PID basis, then I could probably take some measurements. What the app should so is just poll PIDs x,y,z (the ones that Pedro mentioned above) in a raw way (no interpretation of the data) and then store it e.g. in a CSV that I might then evaluate on my PC. With that I might find out about the formulas that are needed to translate these raw values to what is needed by ABRP to do its magic. Regards Wolfgang
[sorry for the response delay]
Thanks for the info Pedro !
I've made some testing with Car Scanner Pro App and found some of those PIDs.
I'll try to manualy enter the AT command sequence, and see if I get a result.
Wolfgang, the new version of Car Scanner Pro APP support the Fiat 500e BEV (2020-). There are some data translation errors, but it give a lot of information about the car ! Enable log and you'll get a lot of interesting PIDs.
Hi, I'm about to add support for Fiat 500e according to the list above, however i noticed that there seem to be PIDs of multiple ECUs (18DAF140 and 18DAF144), so the above filter in the init sequence will probably not work with both of them. Could you maybe post a link to where you got the PIDs from so i can have a closer look? Or would anyone be able to provide the correct PIDs in a format like this:
This would even speed it up a lot more.
I use a dongle "Power Cruise Control" and the Power Cruise Application on my Fiat 500e 2021.
i ll be happy if I could use this dongle in ABRP.
But , there is no option to "link" a dongle with the 500e.
And if I set another car (ie : Opel Corsa-e)
- Detect scan
- connect to the ble dongle
- and ... obviously , fail on step 3 ...
If you can provide the OBD commands that work with the 500e we will happily add it.
I think I've found it