[Ovmsdev] Feedback request: HUD sleep behavior work-around
mark at webb-johnson.net
Tue Oct 24 13:59:12 HKT 2017
OK. Pulled it in.
P.S. I think you’ll always get that when merging upstream. It records the merge. #notagitmaster
> On 24 Oct 2017, at 1:52 PM, Greg D. <gregd2350 at gmail.com> wrote:
> Hi Mark,
> I found a small issue with the detection of the flow control CAN frames. Nothing important, but I went ahead and pushed a fix, along with a change to the RPM code so that a stopped vehicle will be seen as idling at 500 RPM + a little jitter. Otherwise real RPM + jitter. This push also fixes the display of battery SoC in the fuel flow Liters / Hr field. 0-100% shows as 0-10.0, plus or minus a little conversion math precision.
> p.s. Why do I sometimes get an implied commit text edit when I do a merge from upstream/master? No overlap in changed files that I can see...
> Greg D. wrote:
>> My HUD has a switch on the power line too. I discovered that if the vehicle is moving (speed in kph > 0) the RPM doesn't seem to matter. But if not moving, and RPM under about 500, it's lights out. Or "display flame out", whichever you prefer :).
>> Mark Webb-Johnson wrote:
>>> I’ve got two.
>>> The first doesn’t sleep (supposedly). It has a manual on/off switch on the OBDII power line.
>>> The second supposedly goes to standby mode after a configurable time after “engine flame out” (love those Chinese google translations).
>>> I’ll have a look at the second one (which is the one I like the most anyway) to see what it says about configurability (“flame out” rpm threshold, and time setting).
>>> Regards, Mark
> OvmsDev mailing list
> OvmsDev at lists.teslaclub.hk
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OvmsDev