[Ovmsdev] VW e-Up read/poll via OBD is working
Chris van der Meijden
chris at arachnon.de
Fri Jul 31 00:32:50 HKT 2020
"@devmarxx: Is there any doc/guide on how to use this RE Tools?"
Here is a link:
https://docs.openvehicles.com/en/latest/plugin/retools/README.html
Not much I'm afraid, but it can bring you on track ...
Chris
Am Donnerstag, den 30.07.2020, 17:56 +0200 schrieb Soko:
> @devmarxx: Is there any doc/guide on how to use this RE Tools?
>
> @Michael: Yeah, I know. You would have done my 1-day work in 5
> mins. I know C++ but I don't know the OVMS framework. But its
> like
> with any project: The issue is not the language, its the
> framework.
>
> Until you have yours you have to settle with me unfortunately ;)
>
> My cousin has a working VCDS HEX interface and I have an
> y-adapter so I can listen with an ELM327 adapter to the
> commands
> VCDS is sending. Maybe I can find any car status there. Device
> 09
> is a good hint.
>
>
>
> But as you said: I have still have to poll this, even if I find a
> status.
>
> I can't say (of course) if there's another CAN bus @ OBD port.
> All this CAN/OBD/Bus stuff is completely new to me.. ModBus
> RTU/TCP, MBus etc. I would know ;)
>
> So if you can point me in any direction what to try - or what you
> would do - I happy to dig into it.
>
> Soko
>
> PS: Any idea when you'll get your Mii?
>
>
>
> On 30.07.2020 17:14, Michael Balzer
> wrote:
>
>
>
>
> >
> > If only I had my Mii already…
> >
> >
> >
> > If the OBD port is shielded from the CAN traffic, you need to
> > poll
> > some device. ECU = Engine Control Unit = device 01.
> >
> >
> >
> > I would suspect the basic car status info to be available
> > from
> > device 09 (central electrics), but it seems no PIDs have been
> > RE'd
> > from there yet. So maybe you need to derive the info from
> > some
> > other mode/status register.
> >
> >
> >
> > It's bad needing to continuosly poll to get the live status
> > data.
> > Is possibly another, unfiltered CAN bus available at the OBD
> > port?
> >
> >
> >
> > Regards,
> >
> > Michael
> >
> >
> >
> >
> >
> > Am 30.07.20 um 16:43 schrieb Soko:
> >
> >
> >
> > >
> > > Ahhh OK, I've found OvmsVehicle::virtual void
> > > TickerXXX(uint32_t ticker);
> > >
> > > Got it! This was exactly my issue as I didn't know
> > > about any
> > > function which gets called regularly so I could check
> > > something like this...
> > >
> > > It's not an ideal situation though: I just can slow
> > > down the
> > > poll after my fail-counter gets too high as I need to
> > > check
> > > when the car gets powered again. So all I can do is
> > > polling,
> > > lets say every 60 secs when the car is off, and
> > > increase it
> > > once its on. But there is now way around this 60-sec
> > > polling
> > > if the only thing I can do is poll :(
> > >
> > >
> > > Afaik there is only the sharkcow's list below, reverse
> > > engineered by him from ODBeleven.
> > > (dev)marxx exlpained to me: There is a gateway between
> > > the
> > > CAN-Buses and the OBD Connector in all VW-AG vehicles
> > > which
> > > only replies to polls and also acts as security gateway
> > > if you
> > > want to write to the buses.
> > > So I think I cannot really do a can log or use re tool as
> > > the
> > > OBD interface stays quiet if I'm not polling it...
> > > And as there is no other vehicle from
> > > VW,Seat,Skoda,Audi,etc.
> > > in OVMS. So I have no cheat-sheet :(
> > > Anyhow... I would need to poll one ECU (is this the
> > > correct
> > > therm?) which doesn't shuts down... or maybe the issue
> > > is the
> > > OBD-gateway shutting down.
> > >
> > >
> > > What do you think?
> > > Soko
> > >
> > >
> > > On 30.07.2020 16:17, Michael Balzer
> > > wrote:
> > >
> > >
> > >
> > > >
> > > > Soko,
> > > >
> > > >
> > > >
> > > > 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?
> > > >
> > > >
> > > >
> > > > Regards,
> > > >
> > > > Michael
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > 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-Cod
> > > > > es/).
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > 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
> > > > >
> > > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > _______________________________________________
> > > > OvmsDev mailing list
> > > > OvmsDev at lists.openvehicles.com
> > > > http://lists.openvehicles.com/mailman/listinfo/ovmsdev
> > > >
> > > >
> > >
> > >
> > >
> > >
> > > _______________________________________________
> > > 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
> >
> >
> >
> >
> > _______________________________________________
> > OvmsDev mailing list
> > OvmsDev at lists.openvehicles.com
> > http://lists.openvehicles.com/mailman/listinfo/ovmsdev
> >
> >
>
>
>
> _______________________________________________
> OvmsDev mailing list
> OvmsDev at lists.openvehicles.com
> http://lists.openvehicles.com/mailman/listinfo/ovmsdev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20200730/75ffef96/attachment.htm>
More information about the OvmsDev
mailing list