<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Thanks, Mark.<br>
<br>
The metrics table wasn't hard to fill in, at least for the
Roadster. I just searched in the source code for all the <span
class="pl-c1">SetValue() calls, and checked off what was being
set. Cross checked that with the live metrics list that is being
reporting from my car, for sanity.<br>
<br>
Unfortunately, a quick glance at the other cars wasn't quite so
simple, so I'd like some help. Should be easy for the primary
authors, as they know where to look for such things.<br>
<br>
I've got the table imported, but need to figure out how to have
the table header repeat on each page. Thanks for doing the other
editing!<br>
<br>
Greg<br>
<br>
</span><br>
<div class="moz-cite-prefix">Mark Webb-Johnson wrote:<br>
</div>
<blockquote type="cite"
cite="mid:47141E05-0A59-44D9-8A6A-A41EB829F37B@webb-johnson.net">
<pre wrap="">Greg,
Looks good. I’ve copied it into the user guide, and sent you a link with edit rights.
I haven’t copied in the vehicle metrics table. That seems like quite a lot of work (to enter and maintain), but probably worthwhile.
Regards, Mark.
</pre>
<blockquote type="cite">
<pre wrap="">On 28 Mar 2018, at 5:19 AM, Greg D. <a class="moz-txt-link-rfc2396E" href="mailto:gregd2350@gmail.com"><gregd2350@gmail.com></a> wrote:
Hi folks
In a fit of prose, if not Shakespeare, I took a pass at creating the
documentation chapter for the OBD2ECU task. Comments, corrections, and
general feedback is requested. Is there anything significant missing?
Mark, if this looks acceptable, can it be posted to the Google Doc, or
send me an invite such that I can do so?
Note that I don't have any reference material on the OBDII-to-DB26
cable, other than the wiring. If we eventually have a purchase source,
that should get referenced, or lacking that, perhaps pointers to where
the connectors can be purchased? Placeholders are noted, but only
that. For the EEs in the group, a question: I have both signal and
chassis grounds connected together on the OBDII connector; should they
be, or just signal ground?
I think it would also be helpful to include a table of what metrics are
available (supported) on what vehicles, as an aid to those who want to
remap things for monitoring on an OBDII HUD or Dongle. A glance at the
available documentation didn't turn up anything, so I took a first pass
at the table. See the attached, which includes what I know of the
Roadster's implementation (since I have one and have studied the code a
bit). I would rather not try to guess at the other cars. Could the
various vehicle authors contribute their columns to the table? Send me
an updated spreadsheet, and I will do the merge.
Thanks!
Greg
<OVMS Metrics Table.xlsx><obd2ecu documentation.txt>_______________________________________________
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>
<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>
</body>
</html>