<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
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>
</body>
</html>