[Ovmsdev] VW e-Up read/poll via OBD is working

Michael Balzer dexter at expeedo.de
Thu Jul 30 22:17:53 HKT 2020


nice progress :-)

If you can't detect vehicle state by listening to regular status CAN
frames, you can check the time since the last poll reply in the per
second ticker.

As poll replies normally come in fast, you should be able to detect a
switch-off by a small timeout, say 3 seconds… probably need to add a
counter, as a single poll may get lost / ignored.

CAN tx errors can be caused by other issues as well, so should generally
not be interpreted that way.

But… are you sure there are no status frames on the bus? Have you done a
can log or tried the re tool?


Am 30.07.20 um 14:43 schrieb Soko:
> Hi guys,
> Want to report success on connecting and reading my VW e-Up via OBD
> cable using the Poller. As you can see in the screenshot of the log
> attached I get an IncomingPollReply(..) call and an SoC value of 33.333%
> Once I turn of the ignition and lock the car though I don't get any
> replies no more (line D 793813) and then I get can1 errors... I'm
> polling with 10 seconds intervall.
> I know that this is as it should be... but my issue is: I don't have
> any way to know if the ignition is on, the key is in, the car is
> running, the car is charging as the PIDs are not known for such values
> (afaik by the lists of sharkcow
> https://www.goingelectric.de/wiki/Liste-der-OBD2-Codes/).
> So what would be the best approach to change the different polling
> states? Can I somehow get called (in my vehicle-class) if an can-error
> is thrown? Then I would increase the poll frequency.
> Any suggestions?
> thanks
> Soko
> _______________________________________________
> OvmsDev mailing list
> OvmsDev at lists.openvehicles.com
> http://lists.openvehicles.com/mailman/listinfo/ovmsdev

Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
Fon 02333 / 833 5735 * Handy 0176 / 206 989 26

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20200730/227e4384/attachment.htm>

More information about the OvmsDev mailing list