[Ovmsdev] HUD Connected to OVMS not working

Sun Oct 16 15:52:38 HKT 2022

Michael,

did you check the SW_12V level with the HUD connected?

Regards,
Michael

Am 16.10.22 um 06:36 schrieb Michael Geddes:
> Thanks for the response Greg.
>
> I tried what you suggested and it still doesn't turn on. (The 'on/off' 
> is a slider switch rather than a momentary button)
>
> I also went into Jaycar and tried this simple HUD: 
> https://www.jaycar.com.au/gps-speedometer-head-up-display-with-obdii-data/p/LA9036?gclid=CjwKCAjwtKmaBhBMEiwAyINuwAF-ZMXvydGdYsUu--w37CmHr6mf1Emx_o2shbA3IvUNUQ4k-ZWtcBoCwQoQAvD_BwE
> Results were the same (didn't have time to find any settings though - 
> as I got permission to try it before I bought it).
>
> I also confirmed that the cable is wired exactly as specified (no 
> more, no less) including 120ohm resistor.
>
> I'm starting to think there's an issue with the OVMS board itself!?
>
> //.ichael
>
> On Sun, 16 Oct 2022 at 02:09, Greg D. <gregd2350 at gmail.com> wrote:
>
>     Hi Michael,
>
>     Yeah, odd.
>
>     I see in the description that there's a power switch on the side
>     of the unit, so that will probably interact with the voltage
>     transition.  After turning Ext12v on, and pushing the on/off
>     button on the HUD unit, I would expect it would turn on.  After
>     that, transitioning Ext12v on/off should trigger the unit to turn
>     on/off as well.
>
>     Assuming you do get it running, what I would suggest is to create
>     a pair of Events to force Ext12v on and off when the car state
>     transitions.  For my car, the states are vehicle.on and
>     vehicle.off, but yours might be different. In the "on" event
>     script I also stop and restart the obd2ecu process, as that will
>     clear the CAN3 bus hang that I've experienced.  It's a long shot,
>     but perhaps the HUD isn't turning on because it's not seeing CAN
>     traffic.  You might try the 12v off / ecu stop / ecu start / 12v
>     on sequence manually and see if that wakes the HUD up.
>
>         OVMS# vfs cat /store/events/vehicle.on/myevent
>         power ext12v off
>         obdii ecu stop
>         obdii ecu start can3
>         power ext12v on
>
>         OVMS# vfs cat /store/events/vehicle.off/myevent
>         power ext12v off
>
>     Good luck!
>
>     Greg
>
>
>     Michael Geddes wrote:
>>     More information:
>>
>>     I'm definitely getting power on the OVMS -> OBDII cable.  11
>>     volts when the car is off, and 12.6 volts when the car is on. I'm
>>     assuming this is quite deliberate. (And like 0.2 volts when the
>>     power to the ext12v is off).
>>
>>     By default, the HUD was needing (according to docs - probably)
>>     13.2v to trigger it to turn on.. so I connected it directly to
>>     the car OBD and changed that setting to 11.5 volts.
>>
>>     When I turned the car off (still connected directly).. the HUD
>>     remained on as it was still getting > 12V.. so the setting
>>     definitely worked.
>>
>>     Unfortunately when I then connected the OVMS to the OBDII and the
>>     OVMS -> OBDII cable to the HUD - it still didn't turn on. :(  (oh
>>     and yes - "power ext12v on".
>>
>>     Any thoughts on this would be welcome.
>>
>>     //.ichael
>>
>>
>>     On Sat, 15 Oct 2022 at 07:15, Michael Geddes
>>     <frog at bunyip.wheelycreek.net> wrote:
>>
>>         Hi all,
>>         Anybody got any experience with HUDs?
>>
>>         I bought this simple HUD from FastTech:
>>         https://www.fasttech.com/products/9686283
>>         When connected direct to the OBDII port, it powers on and
>>         seems to function. When I connect it to the OVMS module with
>>         the standard https://www.fasttech.com/products/9652027 the
>>         HUD doesn't even power on.
>>
>>         It's stated draw is 200ma which afaict should be fine.  I'm
>>         pretty sure the 12V power is getting to PIN 16... though I
>>         will try again to make sure. I only have a crappy little
>>         Multimeter.
>>
>>         On the Troubleshooting it states:
>>            "HUD only available for cars with OBD2 and EU-OBD
>>         agreements ... HUD Products don't support JOBD and OBDI
>>         protocol."
>>
>>         The OBD HUD connector has the following pins:
>>
>>         4* Chassis
>>
>>         5* Signal Ground
>>
>>         6 CAN High
>>
>>         7 *ISO9141 K Line*
>>
>>         14 CAN Low
>>
>>         15 *ISO9141 L Line*
>>
>>         16 Vehicle Battery +ve
>>
>>         * Long pins
>>
>>
>>         These are the standard OVMS supplied pins:
>>
>>         4 Chassis Ground
>>
>>         5 Chassis Ground
>>
>>         6 CAN H (Primary)
>>
>>         14 CAN L (Primary)
>>
>>         16 +12V
>>
>>         So obviously the main difference is the lack of K / L lines
>>         in the OVMS ... but I wouldn't have thought that would have
>>         prevented it from powering up.
>>
>>         Does anybody have any thoughts on this?
>>
>>         //.ichael
>>
>>
>>
>>     _______________________________________________
>>     OvmsDev mailing list
>>     OvmsDev at lists.openvehicles.com
>>     http://lists.openvehicles.com/mailman/listinfo/ovmsdev
>
>
> _______________________________________________
> OvmsDev mailing list
> OvmsDev at lists.openvehicles.com
> http://lists.openvehicles.com/mailman/listinfo/ovmsdev

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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20221016/be60c5da/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 203 bytes
Desc: OpenPGP digital signature
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20221016/be60c5da/attachment.sig>