[Ovmsdev] OBD extended diag session
ovms at soko.cc
Tue Aug 18 19:02:25 HKT 2020
Yeah, I've also thought about VCDS but when I used it during charging it
was just for a couple of minutes and the ignition was on all the time as
I was getting a hole bunch of data and values from it...
So another fork of the whole e-Up via OBD project I should investigate.
It doesn't get boring for sure :D
On 18.08.2020 12:41, Michael Balzer wrote:
> integrating the 12V DC converter with the main charger can be
> convenient, as the 12V battery also will need to be charged from the
> main battery. But it doesn't look like it's done that way on the eUp.
> I guess the charger only provides these additional calculations when
> another unit requested them. As the other unit goes offline, the
> charger stops providing after some timeout. You'll need to know which
> unit talks in what way to the charger -- but the gateway won't let you
> see that. I think you'll need to get access to the unfiltered bus to
> see what's actually going on.
> Or maybe the VCDS continues displaying these values? Then you can log
> & mimic what that does.
> Am 18.08.20 um 12:00 schrieb Soko:
>> Hi Michael,
>> Just to make sure: I'm talking about charging the main battery, not
>> the 12V battery. But I didn't check the status of the 12V battery.
>> But it would be weird to happen 2 times during a charging process
>> exactly after 20 mins.
>> What I did is to log a complete main battery charge. Results/Details
>> see here:
>> To your 2nd email:
>> Yes, the values are for the DC converter of the main battery, not the
>> one for the 12V battery. All values are from this ECU:
>> On 18.08.2020 11:54, Michael Balzer wrote:
>>> was the charger actually working, i.e. charge in progress? If not,
>>> maybe it goes asleep as soon as the 12V aux battery is topped off,
>>> and another ignition state change simply reactivates the topping off
>>> Am 16.08.20 um 16:28 schrieb Soko:
>>>> Hi guys,
>>>> Question for the CAN and ECU experts:
>>>> I am logging into the battery charger ECU on my eUp via the
>>>> extended diag session code. Otherwise I get 7F as reply.
>>>> I am interested in the power efficiency (pe) and power loss (pl)
>>>> It seems though as they have another timeout than the ext diag
>>>> session as I am polling it every 5 seconds. So ext diag is "always
>>>> But after 20 minutes during charging the values change from the
>>>> realistic ones to pe=100% and pl=0. To get the real values back I
>>>> have to unlock the car and turn the ignition. Then I can turn off
>>>> and lock the car again.
>>>> Now to the question: Is this behaviour somehow known from other
>>>> vehicles as well or can it be an error in my code not sending the
>>>> ext diag msg correctly?
>>>> Although when I dont send it at all I dont get even a value for pe
>>>> and pl, just the 7F error msg.
>>>> So do you think it is possible to get those values for longer than
>>>> 20 mins without having to turn the ignition? Or am I out of luck
>>>> here as it seems to be some VW specific thing...
>>>> OvmsDev mailing list
>>>> OvmsDev at lists.openvehicles.com
>>> Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
>>> Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
>>> OvmsDev mailing list
>>> OvmsDev at lists.openvehicles.com
>> OvmsDev mailing list
>> OvmsDev at lists.openvehicles.com
> Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
> Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
> OvmsDev mailing list
> OvmsDev at lists.openvehicles.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OvmsDev