I'm not aware of anyone getting anything out of the OBD2 port yet; it seems that Volvo lock it down in some way

 

See this thread, seems some have worked it out and even reverse engineered it but just one fleet tracking company, needs shared in the public domain

Remote access to car data with Geotab and ABRP

For the past 2 weeks, my car was equipped with a Geotab GO, an ODB-Dongle with OTA access to the cars onboard data, e.g. position, SoC, charging status, etc. This enabled Geotab to reverse engineer OBD access OTA. Using the latest firmware installed OTA this morning, I can now monitor my car...

www.polestar-forum.com

 

I know that the EVNotify bunch are working on gaining access to the Polestar OBD information at the moment too, which would be great as they have a good app for monitoring charging etc and it also hooks into ABRP. Then maybe we can finally see where all the energy is going in the first 10 minutes .

 

Anyone tried hooking up an OBD reader to the PS2 recently? Would love to have an equivalent to “Scan my Tesla” or “Leaf Spy” apps for our car.

Interestingly, I hooked up what’s called a “Saavy” OBD device for my Valentine One radar detector. It serves as a power source and it mutes the alerts below a set speed (which is adjustable). This seems to be working well on my PS2, so this device must be able to access at least the speed from the OBD port.

 

I tried my old ICE status reader OBD2 and App ... nothing.

Until someone rights an app like Leaf Spy, then I don't think we will get anything.

However, a better chance we will get an App through the Google Store in the car first.

 

I tried to connect using Torque Pro (paid-for version) and it tried all protocols known to man (probably including Klingon) and it couldn't get any kind of connection. I believe Volvo OBD2 ports are locked down and have to be used with authorised equipment, though I'm sure someone will somehow reverse engineer the "I'm a Volvo service computer, give me all your data" handshake.

 

OBD2 ports are locked down and have to be used with authorised equipment

They are not locked down, but seem to use a sligthly modified version of the Volvo protocol as I remember from my discussions with Geotab. The Geotab OBD2 dongle is working fine - the other apps would just have to add proper support for the protocol.

 

Anyone seen any updates on this anywhere? Would be fun to have access to this kind of data to confirm how battery preheating and such changes from OTA to OTA. Geotab still the only ones to work this out?

 

Funny you ask. Geotab has just contacted me about this. I expect to be able to give you an update within the next week(s).

 

Quick update: Geotab is making good progress with getting more data from ODB. One disappointing result is that they can't get battery temperature, though

 

Thanks for the update! The battery temperature would have been really useful though...

 

Hello, are they any further with this?

 

Surprising that Polestar can legally lock the ODB2 port for third party to access? … I think the whole point of regulation about cars having to provide ODB2 output as of certain year is for third parties to have access to it? Hence all cars known to man can have at least some basic set of codes read, erased etc.

Puzzled a bit by this to be honest …

 

The only part of the OBD-II port that's mandatory is error code reporting, and specifically errors relating to emissions.

 

yeah…apparently EVs are not obligated to comply with ODBC2 regulation at all (at least in US). I was assuming wrong, since my current Kia Soul EV has fully functioning port and I could easily read whole bunch of stuff through one of the many apps available.

This will be potentially a ”right to repair“ fight down the road … because, I just don’t quite see how with this mentality, will EVs like P2 get fixed in the future by a third party shop, especially once warranty is gone … it’s not like all the third party shops will seize to exist, right?

 

Any new developments on this OBD topic? I installed and used VDASH last week but it really did not show me much. In addition the VDASH user interface is a bit odd and I could not clear all error codes with VDASH. It cleared some but not all from what I could tell. Not sure if that is a VDASH software issue or P2 OBD communication issue or me not being familiar with VDASH. An app like CARISTA would be awesome for the P2.

 

I would also be highly interested. There is a bunch of 1FFF0xxx messages on the OBD2/can bus when the vehicle is idle, and also 7E2, 7E5 etc...

The VIN is in 1FFF0300. The battery temperature must be in there, too. I did a commercial battery test, and they had the values just from the OBD port.

 

I found my old BlueDriver OBD reader recently (got it for getting DEQ smog ready) for my ICE cars. I was pleasantly surprised to see it had the PS2 listed and got this limited output in Neutral:

 

Apparently it supports both UDS and pure CAN communication. I found the Odometer in the data - it's the 1FFF0120 entry:

can0 1FFF0120 [8] E0 7E 53 00 00 C0 00 00

My odometer is at 32.339 which equals 0x7E 53. I wonder what will happen if it hits 65535 km (FF FF) - will the E0 value change, or will It shift to the next two digits (00).

 

You don't have to use byte size chunks. I would imagine that 65536 would be E1 00 00 and EF FF FF would be a million km's.

 

Agree. Could be, although I assume in 2022 they would allow for more than a million.
Made some progress. 1FFF0120 contains the odometer:

can0 1FFF0120 [8] E0 7E 53 00 00 C0 00 00
7E 53 = 32.339 km

 

And 1FFF00A0 contains the gear:


can0 1FFF00A0 [8] 00 00 00 00 00 00 58 19 => P
can0 1FFF00A0 [8] 00 00 00 00 00 00 59 16 => R
can0 1FFF00A0 [8] 00 00 00 00 00 00 5A 16 => N
can0 1FFF00A0 [8] 00 00 00 00 00 00 5B 16 => D

 

Maybe it's worth contacting the devs of the open source EVNotify with the PID data you've found so far to see if they'll add it to their app.

 

If it helps anyone I have written an application for reading data over ODB2 that runs on a Wifi-enabled ODB2 dongle (Macchina A0) which I use in my Polestar 2 to log SoC, ODO, 12V battery voltage, outside temperature, VIN, speed and gear.
The accelerator pedal position readings could also be added since these are part of the standard PIDs and easy to find information about (I.e. https://en.wikipedia.org/wiki/OBD-II_PIDs).
I have implemented the ODO and gear reading using the information found on this forum in this thread and others.
My main use for it is to read SoC and from that calculate how long time it will take to charge and control when the car charges from that information.
In any case, I guess it could serve as an example for anyone trying to get this information from the car.

I have tried to write it in a general way so that it could work on other cars which is why it includes some 11 bit addressing things. Polestar 2 uses 29 bit addresses so it is not really relevant for Polestar 2 specifically.

You can find it on GitHub: GitHub - olalid/esp32_EVSoCReader: Reads electric or hybrid vehicle battery state of charge and sends to MQTT server.

 

Very nice! I'm looking to integrate the P2 in my home assistant installation. Already have the Fiat500e integrated. Already show added % SoC for the P2 on my dash, calculated as you suggest on GitHub. Interesting: when the charger (Wallbox) starts charging, HA queries the Fiat to see if that is the connected car, if not, HA assumes it is the PS. Long way around, but it works.

 

Hi all - does anyone know where someone has shared the Polestar 2 PIDs including SoH and cell voltages etc? Just trying to build my own app for my Polestar 2! Thanks E

 

I use the OBDLink LX scanner with Car Scanner Pro app and you do get useful info but not as much as some other EVs but at least you get important temperature and charging data.

View attachment 1000010299.png

 

@SOOP if you go to "All sensors" in Car Scanner, is there anything for state of health for HV battery?

 

With Car Scanner you get a lot of data, except for the SOH.

 

You are can contact the app support via Settings > Contact developer and see if it is possible to add the State of Health metrics. They did help me put in a configuration parameter for the Polestar EVs as I used to choose the Volvo configuration.

 

I finally figured out how to read the SoH with OBD2 by picking up bits and pieces here and there on the internet and snooping the CAN bus.

So, in short, you need to send the following CAN message: 0x1DD01635: 0x03 0x22 0x49 0x6d 0x00 0x00 0x00 0x00

0x1DD01635 is the address of the "BECM" (Battery management control module). 0x03 is the number of valid bytes following, 0x22 indicates an UDS message, and 0x496d is the DID we want to read.

The BECM will then respond with: 0x1EC6AE80: 0x07 0x62 0x49 0x6d XX XX XX XX.

0x1EC6AE80 is the "tester address", where responses are sent. 0x07 is the number of valid bytes following, 0x62 indicates that it is a response to a 0x22 request (bit 0x40 set + 0x22) and 0x49, 0x6d is the DID it is responding to. The 4 bytes after that is the SoH in 0.01% units.

My car responds with 92.10% after 160000 km.

 

I finally figured out how to read the SoH with OBD2 by picking up bits and pieces here and there on the internet and snooping the CAN bus.

😍
WOAH!

you'll receive the Order of Lenin for this, Captain!

 

Check this link out as they mention analysis in 2024 found Generally EV batteries last 15-20 years and on average batteries degrade by 1.8% per year.

https://www.geotab.com/au/blog/ev-battery-health/