<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Greg,<br>
<br>
thanks for testing & feedback.<br>
<br>
I'm working on the Twizy web UI now. If you'd like to implement the
obd2ecu configuration, add it to the obd2ecu module. Have a look at
the rt_web module for an example on how to extend the webserver from
another module, it's really easy.<br>
<br>
For the PID mapping, I think a tabular form like for the Wifi config
would be suitable. You can copy that form as a template, it's in the
web_cfg module and consists of three methods:<br>
<ul>
<li>HandleCfgWifi -- main handler & Javascript<br>
</li>
<li>OutputWifiTable -- table view</li>
<li>UpdateWifiTable -- table controller<br>
</li>
</ul>
The Javascript for adding and deleting table rows can be used for
any table form, you just need to change the row template.<br>
<br>
Regards,<br>
Michael<br>
<br>
<br>
<div class="moz-cite-prefix">Am 04.03.2018 um 04:47 schrieb Greg D.:<br>
</div>
<blockquote type="cite"
cite="mid:a504c5e2-144d-4498-4969-2a684f2e702f@gmail.com">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
Hi Michael,<br>
<br>
Looks good! <br>
<br>
The order for starting the obdii ecu task and the vehicle it draws
data from isn't critical; nothing bad will happen if by some
chance the OBDII device starts requesting information before the
vehicle task makes it available. I suppose, the "most correct"
sequence would start the vehicle task, then the obdii ecu task,
then enable the ext12v power last, but in practice and by design
there is no issue with starting any of them in pretty much any
order. Worst case, the device it would get zeros if it wins the
race, but I catch those internally and prevent the apparent lack
of a running ICE engine from causing the device to shut down by
supplying dummy information.<br>
<br>
The only thing missing in the web server, I suppose, would be a
way to customize the PID-to-Metric mapping. I supply a default
for the most common ones, but there are many more possible if you
are using, say, an ELM 327 dongle with Torque-like application.
Changing the mapping is easily done through the shell (unless you
want to tackle that with the web server too). 'config set
obd2ecu.map <pid> <metric>' to set the mapping, and
'obdii ecu list' to display the mapping and current values.<br>
<br>
Thanks for doing this!<br>
<br>
Greg<br>
<br>
<br>
<div class="moz-cite-prefix">Michael Balzer wrote:<br>
</div>
<blockquote type="cite"
cite="mid:3910604d-9c23-0cf5-5960-461c3f555b58@expeedo.de">
<meta http-equiv="Content-Type" content="text/html;
charset=utf-8">
Greg,<br>
<br>
I've just added ext12v and obd2ecu to the auto init system &
web config.<br>
<br>
So except for the metric set command, you should now be able to
start your module without a script.<br>
<br>
The autostart sequence is slightly different from yours, the
obd2ecu init is done after the vehicle module init, as I see the
vehicle module as the data provider for the obd2ecu module --
correct me if I'm wrong.<br>
<br>
Can you please verify the start sequence is working as expected?<br>
<br>
Regards,<br>
Michael<br>
<br>
<br>
<div class="moz-cite-prefix">Am 25.02.2018 um 22:08 schrieb Greg
D.:<br>
</div>
<blockquote type="cite"
cite="mid:2e10a9a9-d3b1-66c5-314e-a643b0574af7@gmail.com"><br>
Here's my system.start event file:<br>
<blockquote><tt>OVMS > vfs cat
/store/events/system.start/mystartup</tt><br>
<tt>obdii ecu start can3</tt><br>
<tt>power ext12v on</tt><br>
<tt>wifi mode client gregnet3</tt><br>
<tt># power simcom on</tt><br>
<tt>vehicle module TR</tt><br>
<tt>server v2 start</tt><br>
<tt>metric set v.b.soc 55</tt><br>
<tt>OVMS > </tt><br>
</blockquote>
(Before you ask, the setting of the soc metric is so that I
can see the server is actually talking to the module, when the
module's on the bench.)<br>
</blockquote>
<br>
<pre class="moz-signature" cols="160">--
Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
OvmsDev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OvmsDev@lists.teslaclub.hk" moz-do-not-send="true">OvmsDev@lists.teslaclub.hk</a>
<a class="moz-txt-link-freetext" href="http://lists.teslaclub.hk/mailman/listinfo/ovmsdev" moz-do-not-send="true">http://lists.teslaclub.hk/mailman/listinfo/ovmsdev</a>
</pre>
</blockquote>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
OvmsDev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OvmsDev@lists.teslaclub.hk">OvmsDev@lists.teslaclub.hk</a>
<a class="moz-txt-link-freetext" href="http://lists.teslaclub.hk/mailman/listinfo/ovmsdev">http://lists.teslaclub.hk/mailman/listinfo/ovmsdev</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="160">--
Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
</pre>
</body>
</html>