<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body><div>Hi Michael,</div><div><br></div><div>thanx for the merge. Looking forward to the new official release :-)</div><div><br></div><div>I will edit the documentation and make a new pull request for that. From there on I will take your advice on triggering the pull requests on important changes.</div><div><br></div><div>Greetinx</div><div><br></div><div>Chris</div><div><br></div><div>Am Mittwoch, den 18.03.2020, 12:39 +0100 schrieb Michael Balzer:</div><blockquote type="cite">
Chris,<br>
<br>
I'll merge the Android PR this evening, probably also directly
publish a new App version for this.<br>
<br>
Create pull requests whenever you think it's appropriate. Good
practice is creating PRs on bug fixes and on completed feature units
or important changes. We announce new major releases on this list,
asking for any open developments that should be included.<br>
<br>
The whole documentation is part of the git repository so can be
changed by you as well. The intro page is created from the top level
"README.md" file.<br>
<br>
Regards,<br>
Michael<br>
<br>
<br>
<div class="moz-cite-prefix">Am 18.03.20 um 08:25 schrieb Chris van
der Meijden:<br>
</div>
<blockquote type="cite" cite="mid:1584516349.2417.3.camel@arachnon.de">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<div>Super! Thank you very much.</div>
<div><br>
</div>
<div>This feels realy good :-)</div>
<div><br>
</div>
<div>As we have rapid changes of the code and the documentation,
can you tell me how often it is best practice to create new pull
requests?</div>
<div><br>
</div>
<div>Oh, and is it possible to link the VW e-Up documentation in
the introduction page:</div>
<div><br>
</div>
<div><a href="https://docs.openvehicles.com/en/latest/introduction.html" moz-do-not-send="true">https://docs.openvehicles.com/en/latest/introduction.html</a></div>
<div><br>
</div>
<div>Thanx again</div>
<div><br>
</div>
<div>Greetinx</div>
<div><br>
</div>
<div>Chris</div>
<div><br>
</div>
<div>Am Mittwoch, den 18.03.2020, 13:44 +0800 schrieb Mark
Webb-Johnson:</div>
<blockquote type="cite">
<div class=""><br class="">
</div>
It looks workable to me. I have merged in the firmware pull
request, and will leave the Android one up to Michael.
<div class=""><br class="">
</div>
<div class="">Congratulations! Looking forward to seeing how
this develops over time.</div>
<div class=""><br class="">
</div>
<div class="">Documentation has appeared online now:</div>
<div class=""><br class="">
</div>
<blockquote style="margin: 0 0 0 40px; border: none; padding:
0px;" class="">
<div class=""><a href="https://docs.openvehicles.com/en/latest/components/vehicle_vweup/docs/index.html" class="" moz-do-not-send="true">https://docs.openvehicles.com/en/latest/components/vehicle_vweup/docs/index.html</a></div>
</blockquote>
<div class=""><br class="">
</div>
<div class="">I think this should still be treated as
experimental for the moment, until we have had time to get
some experience with it.</div>
<div class=""><br class="">
</div>
<div class="">Regards, Mark.<br class="">
<div><br class="">
<blockquote type="cite" class="">
<div class="">On 18 Mar 2020, at 5:22 AM, Chris van der
Meijden <<a href="mailto:chris@arachnon.de" class="" moz-do-not-send="true">chris@arachnon.de</a>>
wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<meta http-equiv="Content-Type" content="text/html;
charset=UTF-8" class="">
<div class="">
<div class="">Dear all,</div>
<div class=""><br class="">
</div>
<div class="">after some ups and downs I think we now
have now enough functionality to officialy ask for
commit to my pull request for integration of the VW
e-Up to the OVMS master :-)</div>
<div class=""><br class="">
</div>
<div class="">An overview of the supported and tested
(yes, with a real VW e-Up :-)) features you can find
here</div>
<div class=""><br class="">
</div>
<div class=""><a href="https://github.com/devmarxx/Open-Vehicle-Monitoring-System-3/blob/master/vehicle/OVMS.V3/components/vehicle_vweup/docs/index.rst" class="" moz-do-not-send="true">https://github.com/devmarxx/Open-Vehicle-Monitoring-System-3/blob/master/vehicle/OVMS.V3/components/vehicle_vweup/docs/index.rst</a></div>
<div class=""><br class="">
</div>
<div class="">I also added the car to the Android app.
The app is working flawless with the car, so I
believe that my pull request for the app also can be
committed.</div>
<div class=""><br class="">
</div>
<div class="">We will of course continue the
development of our module. One major working area is
still the remote climate control. This is more
complicated than I hoped. We are now connected to
the car directly through the comfort CAN bus to get
easy access to some simple ID's. But we probably
need to think about connecting to OBD for polling
ID's for climate control and more battery
information. This should preferably be done over
bluetooth to avoid laying new wires in the car.</div>
<div class=""><br class="">
</div>
<div class="">So therefor I would also like to ask for
a brief status on bluetooth in OVMS. Bluetooth does
not compile for me, but I just tried it once without
getting into it deeper. At the moment I'm more
focussed on "the great moment" of getting my pull
request for the OMS master committed :-)</div>
<div class=""><br class="">
</div>
<div class="">Looking forward to the next steps.</div>
<div class=""><br class="">
</div>
<div class="">Regards</div>
<div class=""><br class="">
</div>
<div class="">Chris </div>
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
<div class="">Am Sonntag, den 01.03.2020, 08:26 +0100
schrieb Chris van der Meijden:</div>
<blockquote type="cite" class="">
<div class="">Hi Michael,</div>
<div class=""><br class="">
</div>
<div class="">thanx a lot for your nice and helpfull
comments. I made some corrections.</div>
<div class=""><br class="">
</div>
<div class="">Please feel free to take an other look
at the code on future occasions. I really
appreciate the remarks :-)</div>
<div class=""><br class="">
</div>
<div class="">Greetinx</div>
<div class=""><br class="">
</div>
<div class="">Chris</div>
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
<div class="">Am Samstag, den 29.02.2020, 17:05
+0100 schrieb Michael Balzer:</div>
<blockquote type="cite" class=""> Chris,<br class="">
<br class="">
some first comments:<br class="">
<ul class="">
<li class="">Please don't use TAB indentation,
only spaces, or add a ".editorconfig". Tabs
have different width depending on the editor
& environment. Default indentation step
for most of the code is two (2) spaces, except
for some submodules (which have .editorconfig
files as necessary, for example the zip
module). See <a href="https://editorconfig.org/" class="" moz-do-not-send="true">https://editorconfig.org/</a></li>
<li class="">ms_v_bat_12v_voltage is by default
provided by the housekeeping from the OVMS ADC
(supply voltage), there is currently no
defined way to override this (maybe we should
introduce one?). If you set the metric, you
will let the CAN data fight against the ADC
measurement (see housekeeping.cpp). The
advantage of the ADC measurement is it works
all the time, not only while the CAN bus is
online.<br class="">
</li>
<li class="">Checking ms_v_env_awake staleness
to detect the switch-off will have a delay of
120 seconds, but I assume that's just a
temporary solution. I bet there is some way to
read the state from CAN.<br class="">
</li>
</ul>
Overall, nice & clean & good remarks.<br class="">
<br class="">
Btw, a typical CAN value scaling would be 100/256.<br class="">
<br class="">
Regards,<br class="">
Michael<br class="">
<br class="">
<br class="">
<div class="moz-cite-prefix">Am 26.02.20 um 09:07
schrieb Chris van der Meijden:<br class="">
</div>
<blockquote type="cite" cite="mid:1582704426.2227.1.camel@arachnon.de" class="">
<div class="">I do have some "first code" now.</div>
<div class=""><br class="">
</div>
<div class="">We found some CAN-ID's for the
e-Up, so we could start the work on some real
functionality.</div>
<div class=""><br class="">
</div>
<div class="">At this stage we have:</div>
<div class=""><br class="">
</div>
<div class="">- SoC (hopefully)</div>
<div class="">- VIN</div>
<div class="">- Speed</div>
<div class="">- 12 volt battery current</div>
<div class=""><br class="">
</div>
<div class="">This should be enough to bring
first action within the app, i.e. battery bar
and parking notice.</div>
<div class=""><br class="">
</div>
<div class="">I would like to invite you to take
a look at the code here:</div>
<div class=""><br class="">
</div>
<div class=""><a href="https://github.com/devmarxx/Open-Vehicle-Monitoring-System-3/blob/master/vehicle/OVMS.V3/components/vehicle/vehicle.cpp" moz-do-not-send="true" class="">https://github.com/devmarxx/Open-Vehicle-Monitoring-System-3/blob/master/vehicle/OVMS.V3/components/vehicle/vehicle.cpp</a></div>
<div class=""><br class="">
</div>
<div class="">and give me some feedback. I wrote
the code "blind" and everything is untested
because I don't have an OVMS v3 yet (it is on
its way) and our e-Up has also not arrived yet
(hoping for week 18 ...). So any hint on how
to do better is welcome.</div>
<div class=""><br class="">
</div>
<div class="">Thanx in advance.</div>
<div class=""><br class="">
</div>
<div class="">Regards</div>
<div class=""><br class="">
</div>
<div class="">Chris</div>
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
<div class="">Am Mittwoch, den 05.02.2020, 12:47
+0100 schrieb Chris van der Meijden:</div>
<blockquote type="cite" class="">
<div class="">It will take it's time though
...</div>
<div class=""><br class="">
</div>
<div class="">At the moment I'm waiting for
our e-Up to be delivered. Hopefully in April
and that is where the real fun starts.</div>
<div class=""><br class="">
</div>
<div class="">I forgot to mention my website
with my experiences with OVMS for the Leaf
and load of other stuff around e-mobility:</div>
<div class=""><br class="">
</div>
<div class=""><a href="http://www.arachnon.de/wb/pages/en/nissan-leaf/ovms.php" moz-do-not-send="true" class="">http://www.arachnon.de/wb/pages/en/nissan-leaf/ovms.php</a></div>
<div class=""><br class="">
</div>
<div class="">Just to complete my introduction
:-)</div>
<div class=""><br class="">
</div>
<div class="">Chris</div>
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
<div class="">Am Mittwoch, den 05.02.2020,
12:20 +0100 schrieb Michael Balzer:</div>
<blockquote type="cite" class="">
<div class="moz-cite-prefix">A quick
addition:<br class="">
<br class="">
Chris' work will be covering at least
three new vehicles. The same vehicle drive
train & electronics is used on…<br class="">
<ul class="">
<li class="">VW e-Up<br class="">
</li>
<li class="">SEAT Mii electric <br class="">
</li>
<li class="">ŠKODA CITIGOe iV<br class="">
</li>
</ul>
…also called "the new trio". These are
very attractive vehicles with a good
balancing of price and capabilities, and
very good efficiency.<br class="">
<br class="">
It's quite possible the code can also
partially be used on other VW vehicles
(e-Golf, ID.3?), as VW tends to reuse
components & protocols.<br class="">
<br class="">
Regards,<br class="">
Michael<br class="">
<br class="">
<br class="">
Am 05.02.20 um 10:44 schrieb Chris van der
Meijden:<br class="">
</div>
<blockquote type="cite" cite="mid:1580895853.4613.2.camel@arachnon.de" class="">
<div style="" class="">Dear OVMS-devs,</div>
<div style="" class=""><br class="">
</div>
<div style="" class="">my name is Chris
van der Meijden (devmarxx) and I just
started a new project on integrating the
VW e-Up into OVMS.</div>
<div style="" class=""><br class="">
</div>
<div style="" class="">I mailed with
Michael and he provided me with usefull
procedure hints. I forked OVMS V3 and
the Android code into my github account <a href="https://github.com/devmarxx?tab=repositories" moz-do-not-send="true" class="">https://github.com/devmarxx?tab=repositories</a> and
commited my changes to the code there. I
also started a pull request, but there
is no hurry, because my vehicle code is
just a template at the moment (like the
Fiat 500 e code). The Android code is
complete, but Michael is quite right
that it would confuse the users to
suddenly see the VW e-Up when there is
still no functionality, so no hurry
there too.</div>
<div style="" class=""><br class="">
</div>
<div style="" class="">My experience on
OVMS so far is, that have been playing
with the code for about 4 years. It
started all because at that time I could
not use the Android app on my
Cyanogenmod phone due to the "google
services" popup. I checked out the
source code, removed the google check
line and voila I could use the app with
my Twizy and with my server :-)</div>
<div style="" class=""><br class="">
</div>
<div style="" class="">Later we bought a
Nissan Leaf and I came in contact with
Tom Parker. I had already set up the
OVMS V2 toolchain, so it was very nice
that I could use Tom's code to get the
climate control of the Leaf to work.
Always nice mail contact with Tom.
Amazing the we can work together in New
Zealand and Germany without ever have
met. That where good times :-)</div>
<div style="" class=""><br class="">
</div>
<div style="" class="">So now we bought a
VW e-Up, that will be delivered
hopefully in April. So I thought now is
a good time to get started with OVMS for
the VW e-Up. I decided to connect to the
vehicle not over the OBD connector, but
through the OCU plug of the VW e-Up. By
doing so I hope to bypass the
complicated VW CAN TP2.0 protocoll and I
will have direct access to the the VW
comfort CAN. Time will tell if that is
the right decission.</div>
<div style="" class=""><br class="">
</div>
<div style="" class="">I started a thread
at the german goingelectric forum. Here
I'll post my "adventures" (in German)
and I hope to find some co-coders there
too <a href="https://www.goingelectric.de/forum/viewtopic.php?f=50&t=54620" moz-do-not-send="true" class="">https://www.goingelectric.de/forum/viewtopic.php?f=50&t=54620</a></div>
<div style="" class=""><br class="">
</div>
<div style="" class="">Well .. So far my
little introduction. </div>
<div style="" class=""><br class="">
</div>
<div style="" class="">Looking forward to
do some happy coding together.</div>
<div style="" class=""><br class="">
</div>
<div style="" class="">Greetinx</div>
<div style="" class=""><br class="">
</div>
<div style="" class="">Chris</div>
<br class="">
<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="">
<pre class="">_______________________________________________
OvmsDev mailing list
<a href="mailto:OvmsDev@lists.openvehicles.com" moz-do-not-send="true" class="">OvmsDev@lists.openvehicles.com</a>
<a href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev" moz-do-not-send="true" class="">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a>
</pre>
</blockquote>
<pre class="">_______________________________________________
OvmsDev mailing list
<a href="mailto:OvmsDev@lists.openvehicles.com" moz-do-not-send="true" class="">OvmsDev@lists.openvehicles.com</a>
<a href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev" moz-do-not-send="true" class="">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a>
</pre>
</blockquote>
<br class="">
<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="">
<pre class="">_______________________________________________
OvmsDev mailing list
<a href="mailto:OvmsDev@lists.openvehicles.com" class="" moz-do-not-send="true">OvmsDev@lists.openvehicles.com</a>
<a href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev" class="" moz-do-not-send="true">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a>
</pre>
</blockquote>
<pre class="">_______________________________________________
OvmsDev mailing list
<a href="mailto:OvmsDev@lists.openvehicles.com" class="" moz-do-not-send="true">OvmsDev@lists.openvehicles.com</a>
<a href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev" class="" 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">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a><br class="">
</div>
</blockquote>
</div>
<br class="">
</div>
<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>_______________________________________________
OvmsDev mailing list
<a href="mailto:OvmsDev@lists.openvehicles.com">OvmsDev@lists.openvehicles.com</a>
<a href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a>
</pre></blockquote></body></html>