<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
The vehicle type name is no configuration parameter, it's a fixed
property of the vehicle class.<br>
<br>
The vehicle to use is configured by the vehicle type only.<br>
<br>
Regards,<br>
Michael<br>
<br>
<br>
<br>
<div class="moz-cite-prefix">Am 12.08.20 um 20:24 schrieb Chris van
der Meijden:<br>
</div>
<blockquote type="cite"
cite="mid:1597256653.8344.11.camel@arachnon.de">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<div>Sorry, I'm just not sure if we are talking about the same
param ...</div>
<div><br>
</div>
<div>We now define VWUP.T26A like this</div>
<div><br>
</div>
<div>MyVehicleFactory.<span class="pl-smi">RegisterVehicle</span><VWeUpT26>(<span
class="pl-s"><span class="pl-pds">"</span>VWUP.T26<span
class="pl-pds">"</span></span>, <span class="pl-s"><span
class="pl-pds">"</span>VW e-Up (Komfort CAN)<span
class="pl-pds">"</span></span>);</div>
<div><br>
</div>
<div>Before the splitting we had ("VWUP", "VW e-Up") at
RegisterVehicle. </div>
<div><br>
</div>
<div>My question is do I need to change "VW e-Up" to <span
class="pl-s"><span class="pl-pds">"</span>VW e-Up (Komfort
CAN)<span class="pl-pds">"</span></span>) in the upgrade
function or is this done automaticly when I change "VWUP" to
"VWUP.T26".</div>
<div><br>
</div>
<div>Thanx</div>
<div><br>
</div>
<div>Chris</div>
<div><br>
</div>
<div>Am Mittwoch, den 12.08.2020, 19:57 +0200 schrieb Michael
Balzer:</div>
<blockquote type="cite"> Config → Vehicle → Vehicle name<br>
<br>
It doesn't have a technical use yet, it won't get filled
automatically. It's just a free vehicle name (as the placeholder
says).<br>
<br>
Regards,<br>
Michael<br>
<br>
<div class="moz-cite-prefix">Am 12.08.20 um 19:34 schrieb Chris
van der Meijden:<br>
</div>
<blockquote type="cite"
cite="mid:1597253679.8344.7.camel@arachnon.de">
<meta http-equiv="Content-Type" content="text/html;
charset=UTF-8">
<div>Hey Michael</div>
<div><br>
</div>
<div>Thanx.</div>
<div><br>
</div>
<div>Does the human readable vehicle ID description ("VW e-Up
(Komfort CAN)") matter at all, or will it be filled out
automaticly by the new vehicle ID configuration? If not, how
do I set that param?</div>
<div><br>
</div>
<div>Regards</div>
<div><br>
</div>
<div>Chris</div>
<div><br>
</div>
<div>Am Mittwoch, den 12.08.2020, 19:18 +0200 schrieb Michael
Balzer:</div>
<blockquote type="cite"> Chris,<br>
<br>
yes, that would do. But…<br>
<br>
a) you shouldn't overwrite the vehicle name, that's a user
configuration, and<br>
<br>
b) if you would overwrite the vehicle name, you would set
"name" in "vehicle", not "vehicle.name" in "auto" (which
doesn't exist).<br>
<br>
Regards,<br>
Michael<br>
<br>
<br>
<div class="moz-cite-prefix">Am 12.08.20 um 18:59 schrieb
Chris van der Meijden:<br>
</div>
<blockquote type="cite"
cite="mid:1597251590.8344.5.camel@arachnon.de">
<meta http-equiv="Content-Type" content="text/html;
charset=UTF-8">
<div>Hi Michael</div>
<div><br>
</div>
<div>I found some time for the "hanging upgrade" issue
since we splitted the vehicle ID from VWUP to VWUP.T26
and VWUP.OBD.</div>
<div><br>
</div>
<div>Would this code in ovms_config.cpp within
OvmsConfig::upgrade() prevent the "hanging" after an
upgrade?</div>
<div><br>
</div>
<div>// Migrate vehicle ID VWUP to VWUP.T26</div>
<div>if (GetParamValue("auto", "vehicle.type") == "VWUP")</div>
<pre> {</pre>
<pre> S<span style="white-space: pre-wrap;">etParamValue("auto", "vehicle.type", "VWUP.T26");</span></pre>
<pre><span style="white-space: pre-wrap;"> </span>S<span style="white-space: pre-wrap;">etParamValue("auto", "vehicle.name", "VW e-Up (Komfort CAN)");</span></pre>
<pre><span style="white-space: pre-wrap;"> }</span></pre>
<div><br>
</div>
<div>If so, I would put that in a pull request as soon as
we have a new "release worthy" version?</div>
<div><br>
</div>
<div>Thanx for checking.</div>
<div><br>
</div>
<div>Greetinx</div>
<div><br>
</div>
<div>Chris</div>
<div><br>
</div>
<div>Am Freitag, den 31.07.2020, 11:34 +0200 schrieb
Michael Balzer:</div>
<blockquote type="cite"> Chris,<br>
<br>
the framework shouldn't get stuck if a vehicle cannot be
loaded, it should fall back to booting without a
vehicle. I'll have a look at that.<br>
<br>
Btw, to automatically update user configurations, you
can extend OvmsConfig::upgrade(). Users shouldn't need
to take care of special update preparations.<br>
<br>
Regards,<br>
Michael<br>
<br>
<br>
<div class="moz-cite-prefix">Am 31.07.20 um 11:05
schrieb Chris van der Meijden:<br>
</div>
<blockquote type="cite"
cite="mid:1596186326.2615.2.camel@arachnon.de">
<meta http-equiv="Content-Type" content="text/html;
charset=UTF-8">
<div>Welcome to my trial and error T26A world :-))</div>
<div><br>
</div>
<div>This morning I flashed the new T26A/OBD version
to my OVMS. After the OTA flash the device did not
come back to the networks. Only USB terminal access
was left.</div>
<div><br>
</div>
<div>The reason was, that I did no remove the old
vehicle config "VWUP" before flashing and rebooting.
The new image has "VWUP.T26" and "VWUP.OBD" as
vehicle config, but no more "VWUP". So the device
could not find its vehicle config and got stuck.</div>
<div><br>
</div>
<div>From the USB terminal I bootet back to OTA_0,
said in the vehicle config that my vehicle was a
Nissan Leaf and then booted back to OTA_1. The
device came up with the new firmware and I could
change the vehicle config to "VWUP (Komfort CAN)".</div>
<div><br>
</div>
<div>Everything is now running fine ...</div>
<div><br>
</div>
<div>I will write this down in the documentation for
the e-Up.</div>
<div><br>
</div>
<div>Greetinx</div>
<div><br>
</div>
<div>Chris</div>
<div><br>
</div>
<div><br>
</div>
<div>Am Freitag, den 31.07.2020, 09:50 +0200 schrieb
Michael Balzer:</div>
<blockquote type="cite"> Soko,<br>
<br>
you only had the door open, but not turned on the
car? If there are additional buses, they may be
switched off until the car is turned on…<br>
<br>
The OBD connector scheme is the general pin
assignment, I meant the specific VW e-Up schematics.
But if you don't see any voltages with the car
turned on, that's bad news.<br>
<br>
There may still be some command interface for the
OBD gateway to enable live data, but without any
info about the gateway, it will be hard to even find
out how to address it.<br>
<br>
Regards,<br>
Michael<br>
<br>
<br>
<div class="moz-cite-prefix">Am 31.07.20 um 09:06
schrieb Soko:<br>
</div>
<blockquote type="cite"
cite="mid:d26bd0bc-4f57-d727-1b86-183c030fbbb3@soko.cc">
<meta http-equiv="Content-Type"
content="text/html; charset=UTF-8">
<p>Hey guys,</p>
<p>If I did nothing wrong I have bad news:</p>
<p>@Michael:<br>
With OBD port schematics I think you mean this <a
class="moz-txt-link-freetext"
href="https://en.wikipedia.org/wiki/On-board_diagnostics#OBD-II_diagnostic_connector"
moz-do-not-send="true">https://en.wikipedia.org/wiki/On-board_diagnostics#OBD-II_diagnostic_connector</a><br>
Specifically if there are some other pins used
than the standard CAN pins 6 and 14.<br>
So I had the drivers door open, no key in
ignition and measured the voltages of all pins
in relation to pin 5 (signal ground). There is
no voltage on any pin besides 2.5V on 6 and 14,
and 12V on 16 of course. So there are no hidden
CAN buses (or any other signals) afaict.</p>
<p>@Mark:<br>
Thanks for the hint with the can log. It's way
easier than RE Tools for just checking if there
is any traffic.<br>
Having said that... there is no traffic
whatsoever besides what I am polling and the
reply. Even when ignition is on I only see the
poll and the reply on the can log</p>
<p>So it seems devmarxx was right: The gateway
shields everything and there are even no other
hidden signals on the OBD port.</p>
<p>I'm happy to try any other ideas you guys have.
Just let me know!</p>
<p>Soko<br>
</p>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">On 31.07.2020 02:11,
Mark Webb-Johnson wrote:<br>
</div>
<blockquote type="cite"
cite="mid:9A478EA0-DC29-4367-A25D-9407EAEB2E8F@webb-johnson.net">
<meta http-equiv="Content-Type"
content="text/html; charset=UTF-8">
If you are just looking for traffic on the CAN
bus, a simple can log would be the easiest.
Assuming you are on USB console, it is:
<div class=""><br class="">
</div>
<blockquote style="margin: 0 0 0 40px; border:
none; padding: 0px;" class="">
<div class="">OVMS# log level verbose
canlog-monitor</div>
<div class="">OVMS# can log start monitor crtd</div>
</blockquote>
<div class="">
<div><br class="">
</div>
<div>If you are using ssh, you need to add a:</div>
<div><br class="">
</div>
</div>
<blockquote style="margin: 0 0 0 40px; border:
none; padding: 0px;" class="">
<div class="">
<div>OVMS# log monitor yes</div>
</div>
</blockquote>
<div class="">
<div><br class="">
</div>
<div>To stop the logging:</div>
<div><br class="">
</div>
</div>
<blockquote style="margin: 0 0 0 40px; border:
none; padding: 0px;" class="">
<div class="">
<div>OVMS# can log stop</div>
</div>
</blockquote>
<div class="">
<div><br class="">
</div>
<div>Documentation here:</div>
<div><br class="">
</div>
</div>
<blockquote style="margin: 0 0 0 40px; border:
none; padding: 0px;" class="">
<div class="">
<div><a
href="https://docs.openvehicles.com/en/latest/crtd/can_logging.html"
class="" moz-do-not-send="true">https://docs.openvehicles.com/en/latest/crtd/can_logging.html</a></div>
</div>
</blockquote>
<div class="">
<div><br class="">
</div>
<div>
<div class="">
<div>For my work, I personally prefer this
arrangement:</div>
<div><br class="">
</div>
</div>
<blockquote style="margin: 0px 0px 0px 40px;
border: none; padding: 0px;" class="">
<div>OVMS# can log start tcpserver
transmit gvret-b :23</div>
</blockquote>
<div class="">
<div style="caret-color: rgb(0, 0, 0);
color: rgb(0, 0, 0);"><br class="">
</div>
</div>
<div style="caret-color: rgb(0, 0, 0);
color: rgb(0, 0, 0);">And then I use <a
href="https://www.savvycan.com/"
class="" moz-do-not-send="true">SavvyCAN</a> on
a laptop to connect over wifi and work.</div>
<div style="caret-color: rgb(0, 0, 0);
color: rgb(0, 0, 0);"><br class="">
</div>
</div>
<div>Regarding the ‘re’ system, it is a
work-in-progress, and not currently
documented. It is still kind of a mess at
the moment (particularly for multiplexed
message IDs), as I continue to work on DBC
integration. That said, it is basically
functional.</div>
<div><br class="">
</div>
</div>
<div>To start it:</div>
<div><br class="">
</div>
<blockquote style="margin: 0 0 0 40px; border:
none; padding: 0px;" class="">
<div class="">
<div>OVMS# re start</div>
</div>
</blockquote>
<div class="">
<div><br class="">
</div>
<div>To stop it:</div>
<div><br class="">
</div>
</div>
<blockquote style="margin: 0 0 0 40px; border:
none; padding: 0px;" class="">
<div class="">
<div>OVMS# re stop</div>
</div>
</blockquote>
<div class="">
<div><br class="">
</div>
<div>To see discovered IDs:</div>
<div><br class="">
</div>
</div>
<blockquote style="margin: 0 0 0 40px; border:
none; padding: 0px;" class="">
<div class="">
<div>OVMS# re list</div>
</div>
</blockquote>
<div class="">
<div><br class="">
</div>
<div>It will (by default) listen on all open
CAN buses, and show you the discovered ID,
message count, interval (in ms), and last
message seen.</div>
<div><br class="">
</div>
<div>It has some rudimentary ability to
monitor active polling protocols with ‘re
obdii extended <min> <max>’ (or
standard), specifying the range of IDs used
by the ECUs.</div>
<div><br class="">
</div>
</div>
<div class="">
<div>Regards, Mark</div>
<div><br class="">
<blockquote type="cite" class="">
<div class="">On 30 Jul 2020, at 11:56 PM,
Soko <<a href="mailto:ovms@soko.cc"
class="" moz-do-not-send="true">ovms@soko.cc</a>>
wrote:</div>
<div class="">
<meta http-equiv="Content-Type"
content="text/html; charset=UTF-8"
class="">
<div class="">
<p class="">@devmarxx: Is there any
doc/guide on how to use this RE
Tools?</p>
<p class="">@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.</p>
<p class="">Until you have yours you
have to settle with me unfortunately
;)</p>
<p class="">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. <br class="">
</p>
<p class="">But as you said: I have
still have to poll this, even if I
find a status.</p>
<p class="">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 ;)</p>
<p class="">So if you can point me in
any direction what to try - or what
you would do - I happy to dig into
it.</p>
<p class="">Soko</p>
<p class="">PS: Any idea when you'll
get your Mii?<br class="">
</p>
<div class="moz-cite-prefix">On
30.07.2020 17:14, Michael Balzer
wrote:<br class="">
</div>
<blockquote type="cite"
cite="mid:193a06ae-81aa-52a0-047e-6bde5107dbdc@expeedo.de"
class="">
<meta http-equiv="Content-Type"
content="text/html; charset=UTF-8"
class="">
If only I had my Mii already…<br
class="">
<br class="">
If the OBD port is shielded from the
CAN traffic, you need to poll some
device. ECU = Engine Control Unit =
device 01.<br class="">
<br class="">
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.<br class="">
<br class="">
It's bad needing to continuosly poll
to get the live status data. Is
possibly another, unfiltered CAN bus
available at the OBD port?<br
class="">
<br class="">
Regards,<br class="">
Michael<br class="">
<br class="">
<br class="">
<div class="moz-cite-prefix">Am
30.07.20 um 16:43 schrieb Soko:<br
class="">
</div>
<blockquote type="cite"
cite="mid:c46c65de-ae20-f2db-4c2b-052843756691@soko.cc"
class="">
<meta http-equiv="Content-Type"
content="text/html;
charset=UTF-8" class="">
<p class="">Ahhh OK, I've found
OvmsVehicle::virtual void
TickerXXX(uint32_t ticker);<br
class="">
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...<br
class="">
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 :(<br
class="">
</p>
<p class="">Afaik there is only
the sharkcow's list below,
reverse engineered by him from
ODBeleven.</p>
<p class="">(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.</p>
<p class="">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...</p>
<p class="">And as there is no
other vehicle from
VW,Seat,Skoda,Audi,etc. in OVMS.
So I have no cheat-sheet :(</p>
<p class="">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.<br class="">
</p>
<p class="">What do you think?</p>
<p class="">Soko<br class="">
</p>
<div class="moz-cite-prefix">On
30.07.2020 16:17, Michael Balzer
wrote:<br class="">
</div>
<blockquote type="cite"
cite="mid:429f9711-74bd-828c-0c9c-3872f9b0bfac@expeedo.de"
class="">
<meta http-equiv="Content-Type"
content="text/html;
charset=UTF-8" class="">
Soko,<br class="">
<br class="">
nice progress :-)<br class="">
<br class="">
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.<br
class="">
<br class="">
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.<br class="">
<br class="">
CAN tx errors can be caused by
other issues as well, so should
generally not be interpreted
that way.<br class="">
<br class="">
But… are you sure there are no
status frames on the bus? Have
you done a can log or tried the
re tool?<br class="">
<br class="">
Regards,<br class="">
Michael<br class="">
<br class="">
<br class="">
<div class="moz-cite-prefix">Am
30.07.20 um 14:43 schrieb
Soko:<br class="">
</div>
<blockquote type="cite"
cite="mid:dfef03ed-b0e1-1fda-7eab-de5b6e49cc67@soko.cc"
class="">Hi guys, <br
class="">
<br class="">
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% <br class="">
<br class="">
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. <br
class="">
<br class="">
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 <a
class="moz-txt-link-freetext"
href="https://www.goingelectric.de/wiki/Liste-der-OBD2-Codes/"
moz-do-not-send="true">https://www.goingelectric.de/wiki/Liste-der-OBD2-Codes/</a>).
<br class="">
<br class="">
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. <br
class="">
<br class="">
Any suggestions? <br class="">
<br class="">
thanks <br class="">
<br class="">
Soko <br class="">
<br class="">
<br class="">
<fieldset
class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
OvmsDev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OvmsDev@lists.openvehicles.com" moz-do-not-send="true">OvmsDev@lists.openvehicles.com</a>
<a class="moz-txt-link-freetext" href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev" moz-do-not-send="true">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a>
</pre>
</blockquote>
<br class="">
<br class="">
<fieldset
class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
OvmsDev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OvmsDev@lists.openvehicles.com" moz-do-not-send="true">OvmsDev@lists.openvehicles.com</a>
<a class="moz-txt-link-freetext" href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev" moz-do-not-send="true">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a>
</pre>
</blockquote>
<br class="">
<fieldset
class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
OvmsDev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OvmsDev@lists.openvehicles.com" moz-do-not-send="true">OvmsDev@lists.openvehicles.com</a>
<a class="moz-txt-link-freetext" href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev" moz-do-not-send="true">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a>
</pre>
</blockquote>
<br class="">
<br class="">
<fieldset
class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
OvmsDev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OvmsDev@lists.openvehicles.com" moz-do-not-send="true">OvmsDev@lists.openvehicles.com</a>
<a class="moz-txt-link-freetext" href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev" moz-do-not-send="true">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a>
</pre>
</blockquote>
</div>
_______________________________________________<br class="">
OvmsDev mailing list<br class="">
<a
href="mailto:OvmsDev@lists.openvehicles.com"
class="" moz-do-not-send="true">OvmsDev@lists.openvehicles.com</a><br
class="">
<a class="moz-txt-link-freetext"
href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev"
moz-do-not-send="true">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a><br
class="">
</div>
</blockquote>
</div>
<br class="">
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
OvmsDev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OvmsDev@lists.openvehicles.com" moz-do-not-send="true">OvmsDev@lists.openvehicles.com</a>
<a class="moz-txt-link-freetext" href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev" moz-do-not-send="true">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a>
</pre>
</blockquote>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
OvmsDev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OvmsDev@lists.openvehicles.com" moz-do-not-send="true">OvmsDev@lists.openvehicles.com</a>
<a class="moz-txt-link-freetext" href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev" moz-do-not-send="true">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a>
</pre>
</blockquote>
<br>
<pre>_______________________________________________
OvmsDev mailing list
<a href="mailto:OvmsDev@lists.openvehicles.com" moz-do-not-send="true">OvmsDev@lists.openvehicles.com</a>
<a href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev" moz-do-not-send="true">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a>
</pre>
</blockquote>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
OvmsDev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OvmsDev@lists.openvehicles.com" moz-do-not-send="true">OvmsDev@lists.openvehicles.com</a>
<a class="moz-txt-link-freetext" href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev" moz-do-not-send="true">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a>
</pre>
</blockquote>
<br>
<pre>_______________________________________________
OvmsDev mailing list
<a href="mailto:OvmsDev@lists.openvehicles.com" moz-do-not-send="true">OvmsDev@lists.openvehicles.com</a>
<a href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev" moz-do-not-send="true">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a>
</pre>
</blockquote>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
OvmsDev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OvmsDev@lists.openvehicles.com" moz-do-not-send="true">OvmsDev@lists.openvehicles.com</a>
<a class="moz-txt-link-freetext" href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev" moz-do-not-send="true">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
</pre>
<pre>_______________________________________________
OvmsDev mailing list
<a href="mailto:OvmsDev@lists.openvehicles.com" moz-do-not-send="true">OvmsDev@lists.openvehicles.com</a>
<a href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev" moz-do-not-send="true">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a>
</pre>
</blockquote>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
OvmsDev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OvmsDev@lists.openvehicles.com" moz-do-not-send="true">OvmsDev@lists.openvehicles.com</a>
<a class="moz-txt-link-freetext" href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev" moz-do-not-send="true">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
</pre>
<pre>_______________________________________________
OvmsDev mailing list
<a href="mailto:OvmsDev@lists.openvehicles.com" moz-do-not-send="true">OvmsDev@lists.openvehicles.com</a>
<a href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev" moz-do-not-send="true">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a>
</pre>
</blockquote>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
OvmsDev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OvmsDev@lists.openvehicles.com">OvmsDev@lists.openvehicles.com</a>
<a class="moz-txt-link-freetext" href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
</pre>
</body>
</html>