Hi Jona,
(Not sure why this is a different thread than the other one I replied to. Maybe I just don't understand how these mailing lists work. Sorry.)
I'll just re-mention what I told Andreas on the other thread:
The reason for my UDS polling questions is because I want to implement some of the data from this project: http://obd-amigos.linuxtech.net/
I'm interested in reading the real battery SOH (like ODIS does) and possibly the battery cells. But I was wondering how best to do it in OVMS. This shouldn't be something that is done often (and isn't needed to either). I'm thinking only once per charge session maybe? Or should it be on a per-request basis, meaning the user needs to ask for it and then it will read it on the next charge for example?
I have already prepared the UDS read commands to implement to accomplish this, but I was wondering if there was a historical reason in the e-golf OVMS history as to why UDS wasn't used or if there was any 'lessons learned'.
Nick