Hi Sandi
Currently the device can push any kind of data to the server, and we are working on making the dashboard be able to display custom data, so that you can push X data to the server, and then configure a widget to show that data on the dashboard.
Can you elaborate about what data you are retrieving? formats etc?
Best regards
/Malte
Hi Malte,
All I had done was monitor the state of charge and cell voltages via the terminal by issuing obd.send 7E4#022101 through to 7E4#022105.
7E4#022101 and 7E4#022105 provide BMS related data like charge current, SoC, Batt DC voltage, etc.
I used this to convert the data from 7E4#022101 and 7E4#022105.
The returned data format was similar to (for 7E4#022101):
7EC#103D6101FFFFFFFF
7EC#213E264826480300
7EC#22080D6E0D0D0D0D
7EC#230D0D0D000DB326
7EC#24B2270000920000
7EC#259D5600009DF800
7EC#260039E100003782
7EC#2700131FEE0D0157
7EC#280000000003E800
The only responses relevant are those starting with #21 to #28…
For the individual cell voltages, one needs to query 7E4#022102, 7E4#022103 and 7E4#022104 according to this table: https://github.com/JejuSoul/OBD-PIDs-for-HKMC-EVs/blob/master/Ioniq%20EV/extendedpids/Hyundai_Ioniq_EV_BMS_cell_data.csv
Each byte in the response refers to one cell. Convert each HEX value to Dec and divide by 50 to get the correct voltage for each cell.
It was interesting watching as the voltages of some cells increased before the others and so on. But all cells were always within one LSB of each other.
What I would do with this data is to log it at regular intervals (every minute maybe) while the car is charging and then one can compare the dynamics of the charge process between standard charge and quick charges to help isolate potential issues (not sure that Hyundai would take any custom suggestions though), but it will be interesting to see.
On the other end (discharging) I really want to be able to plot vehicle speed versus instantaneous current drawn from the battery and rate of discharge (SoC) to better understand how different driving impacts on the range of the car.
Early days yet…
Regards
Sandi
Hi Sandi,
Just gonna jump in this conversation. Absolutely solid work from your side. You seems to be a couple of steps ahead of what we are working on at the moment.
In one of the upcoming releases (one of the two next ones), we are going to make it so that you can configure the widgets on the dashboard to include whatever data you have logged on your bus. This could be BMS data from your car.
For now you could actually write your own code module, which parses the result of the obd.send command. You can do that from the cloud. The data can be logged locally if you want and then everything from your side is ready when the Cloud is.
Again, really cool work.
best
Peter
Hi Peter,
Thanks! 
Yes, I saw that one can now upload python scripts via the cloud. Haven’t tried it out yet as I was waiting to finish upgrading my system to RPi3.
Will get back into the game soon.
Once I have something working, I will open a dedicated thread on the subject.
On the subject of widgets, will it be possible to fully customize the dashboard in the future releases, so that we can remove widgets? The current, default, set are not of much use to EV users. 
Thanks
Sandi
Hi Sandi,
Yes that will definately be possible. We hope to be able to add this feature in one of the next release.
best
Peter
Hi all,
So, the first part of the EV update is here. This update contains the possibilities to add your own codes specific to your EV. You can now add specific formulas to each code, to make sure it’s formatted correctly. This should make it possible for you to add a code, setup a logger for the code and then have the code visualized in the dashboard. See this guide on how to get started with everything:
The next update will contain more about how to configure the trips settings for the EV.
best
Peter
Like that ? But seem not work. It’s miss something …
I just added SOH and SOC for the Hyundai Kona to the community library - I think this will be the same for the Hyundai Ioniq and Kia eNero.
To test, add single quotes around the header and hit run.
$ obd.query SOC_Display mode=220 pid=105 header='7E4' bytes=54 formula='bytes_to_int(messages[0].data[38:39])/2' unit=% baudrate=500000
protocol=6 verify=false force=true
value: 99
_stamp: '2019-03-04T18:21:05.640377'
_type: soc_display
unit: '%'
$ obd.query SOH mode=220 pid=105 header='7E4' bytes=54 formula='(bytes_to_int(messages[0].data[31:32])*256+bytes_to_int(messages[0].data[32:33]))/10' unit=% baudrate=500000 protocol=6 verify=false force=true
value: 100
_stamp: '2019-03-04T19:16:47.213884'
_type: soh
unit: '%'Thank’s
But i can’t find it …
I’m not sure … maybe something needs to be done by the autopi folks. I see -
Note SOC_Display and SOH towards the bottom.
Maybe try 2018 ?
Yes. Thanks. I found all in kona EV 2018
Very thank you
So we need to make widget now, isn’t it ?
Ok. Thanks. And before make widgets, we need to do this ?:
And I have this error …
Yea, there is a known issue -
So
header='7E4'
rather than
header=7E4
plord do you use custom can settings or standard autodetect ? my code return NO VALUE
I have [6] ISO 15765-4 (CAN 11/500) at 500000 baud. I think it was auto detected.
Ok but do you ve idea about NO VALUE
About ‘…’ I can’t save, value is not accepted
@Malte please update code to resolve quote issue, therefore is useful an editor text box to modify directly and save
at now I use custom code to collect data manually !
