Hi Michael,

Looks good! 

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.

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.

Thanks for doing this!

Greg


Michael Balzer wrote:
Greg,

I've just added ext12v and obd2ecu to the auto init system & web config.

So except for the metric set command, you should now be able to start your module without a script.

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.

Can you please verify the start sequence is working as expected?

Regards,
Michael


Am 25.02.2018 um 22:08 schrieb Greg D.:

Here's my system.start event file:
OVMS > vfs cat /store/events/system.start/mystartup
obdii ecu start can3
power ext12v on
wifi mode client gregnet3
# power simcom on
vehicle module TR
server v2 start
metric set v.b.soc 55
OVMS >
(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.)

-- 
Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
Fon 02333 / 833 5735 * Handy 0176 / 206 989 26



_______________________________________________
OvmsDev mailing list
OvmsDev@lists.teslaclub.hk
http://lists.teslaclub.hk/mailman/listinfo/ovmsdev