Page 13 of 13

Re: Decyphering iMiEV and iON CAR-CAN message data

Posted: Thu Oct 18, 2018 9:48 am
by priusfan
As you are using an OBDLINK LX, you should send the following sequence:
"ATZ" & Chr(13) ' reset dongle
"ATSP6" & Chr(13) ' CAN 11 bits @ 500k
"ATE0" & Chr(13) ' Echo OFF
"ATH1" & Chr(13) ' Header ON
"ATL0" & Chr(13) ' no crlf
"STFAP 374, FFF" & Chr(13) ' put pass filter B_SoC
"STM" & Chr(13) ' read frames

You should receive only frames with id 374, they look like this:
374 B8 BC 00 00 43 3F 4E 00
the SoC is in the second data byte BC
BC converted to dec = 188
formula to apply:
SoC= (X- 10) / 2
SoC= 89% (188- 10) / 2

What you started to develop is not the right way to start with....

Xavier

Re: Decyphering iMiEV and iON CAR-CAN message data

Posted: Thu Oct 18, 2018 10:26 am
by Ghost128k
many thanks for the code!
i try it with the raspberry as soon as posible and tell the results.
Thanks again.

Re: Decyphering iMiEV and iON CAR-CAN message data

Posted: Sun Dec 30, 2018 11:00 pm
by Serhge
how to solve a problem ?

Image

https://ibb.co/N2Kr4R5

Re: Decyphering iMiEV and iON CAR-CAN message data

Posted: Mon Dec 31, 2018 3:26 am
by kiev
What was the length of your CAN data capture--i suspect you either need a longer time slice or need to hold the last value until it is updated.

The cell PIDs are not sent out in any order, nor at any regular frequency--some seem to show up more than others. i don't know if this is due to PID ranking (lower number PIDs have higher priority), or due to controller (no need to report a value that hasn't changed from the previous scan cycle).

Re: Decyphering iMiEV and iON CAR-CAN message data

Posted: Mon Dec 31, 2018 9:37 am
by Serhge
Such a mistake is not just me.
Perhaps there is an error in the work with the order of blocks and the number of cells.
it is not clear in what config and how to fix

Re: Decyphering iMiEV and iON CAR-CAN message data

Posted: Tue Feb 19, 2019 8:49 am
by CZeroOwner
You are right Serhge. This is an error in the presentation. The battery contains 22 blocks of 4 cells. The blocks are arranged in 12 modules, 10 with 2 blocks and 2 with one block each. The temperature sensors are between cells in each block. That means 66 temperature readings for 88 cells. I just released a new version of OBDZero version 3 which presents the voltages and temperatures in a way that corresponds to this arrangement of cells and sensors. This also brings OBDZero in line with other programs such as Canion. If anyone has been collecting cell data I can send a list that shows how to convert the old OBDZero cell numbers to the new system. All the voltage and temperature reading should be in the files they just need renaming. You can also send the data in e.g. a comma separated text and I will try and convert it.

kiev is also right. Not all cell PIDs are captured by OBDZero in each program cycle. It takes up to 20 cycles or about 2 minutes before all of the cells have been outdated.