[Ovmsdev] LCD Car Mount Display

Wed Apr 4 15:09:06 HKT 2018

I admit I like the Plug’n’Play side of your approach (and power piloted with the 12V line, zero waste). But true, if a 3.5” Nextion is a bearable is $26 (for my “micro" vehicle that’s fine), a 5” doubles the figure :-/ That said it removes a lot of the needed work on the comms side, a stupid uC+CAN to act as a modem for a text base protocol. (Or yeah, an ESPxxxx for more comms now that they come cheapish)
Where someone could see the advantage of choosing the display+case they want for a common protocol, the downside would be being dependant on iTeads’ Windows only software if they ever want to customise anything (not being open is my main critic actually)
A bare display would ask for plenty of work on the software side, (+ more guts for graphics (dual SPI seems ok though) ), making it harder for customisation.

Honestly, I don’t have any opinion to balance between these options

Yeah, on the RasPi, I’m struggling with threading mqtt and kivy altogether, I used to have a more flexible brain as well :-) the idea it to have it portable as an android app to allow upcycling an old android tablet/phone

JB./.

On 4 Apr 2018 at 07:04 +0200, Mark Webb-Johnson <mark at webb-johnson.net>, wrote:
>
> I do like the Nextion displays, but the price is crazy. Four to five times that of a bare display. The idea here is to do this as cheap as possible (I am aiming for below US$50, but not sure if we can get it to that level). The ESP32 WROVER devkit (with display, but without enclosure) is around US$60.
>
> With the ESP32 platform, the data and CAN buses come for free (ok, not quite - perhaps US$2 for the CAN transceiver circuitry). I do agree that a simple two-wire power+gnd approach using wifi/bluetooth connectivity is fine for us, but for other users having an external hard-wired connectivity option may be useful. If price becomes an issue, we can leave the circuit supporting it, but just don’t solder those components in place.
>
> I know that I would love a simple programmable display that can talk to a CAN bus. Then people can do the software without having to worry about hardware. Could also stick these on the wall around the house for home automation control. Lots of interesting fun projects for a 3.x” display in a case, with a wifi/bluetooth controller.
>
> Regards, Mark.
>
> P.S. Very cool RaspPi. Love the video.
>
> > On 2 Apr 2018, at 11:39 PM, Julien “JaXX” Banchet <jaxx at jaxx.org> wrote:
> >
> > Oh, nice !
> >
> > Was sorta thinking of another approche for the (accessory display to an existing OVMSv3), since the ovms has comms (Wifi, BT soonish), having something simpler/lighter without the needs for a data or can bus. The whole display would only need
> > And indeed, an ESP has guts for that on it’s own, display could be something like an iTead HMI display which are still cheap for the small screens
> >
> > Otherwise, more hackable/educational , a RaspPi :
> > https://twitter.com/happyjaxx/status/980459861543739393
> >
> > (Piggybacking the websocket to stream events and metrics, whose speed and power only ticks once a second oddly, gotta dig into that, was just logging it for now to replay at home, will have to play with Kivy a bit more for some bling-bling graphics)
> >
> > JB./.
> >
> >
> > On 2 Apr 2018 at 17:24 +0200, Geir Øyvind Vælidalo <geir at validalo.net>, wrote:
> > > I could be interested in something like that. When driving long trips with the Kia, there’s definitely some values that would be very nice to be able to see all the time, like ideal range, average consumption since trip started, charging status, charging speed in kWh and km/h and more.
> > >
> > > Geir
> > >
> > > Sendt fra min iPhone
> > >
> > > 2. apr. 2018 kl. 14:24 skrev Mark Webb-Johnson <mark at webb-johnson.net>:
> > >
> > > >
> > > > Having completed the v3.x hardware, and being a complete masochist for this, I’m now working with China to see what is possible as a display (for OVMS and other projects).
> > > >
> > > > The idea is to have a small enclosure that includes:
> > > >
> > > > • A 3.5” backlit LCD display.
> > > > • Four touch buttons (as touch-screen too hard to use in a moving vehicle) - Up, Down, Enter, Back/Cancel.
> > > > • A WROVER32 (probably 4MB flash to keep costs down, but perhaps 16MB is possible). This has 4MB SPIRAM.
> > > > • MicroSD or SD card slot (full speed 4 wire).
> > > > • USB for firmware flashing and console access.
> > > > • Bluetooth
> > > > • Wifi
> > > > • Connection for:
> > > >
> > > >     • Power (12V regulated)
> > > >     • Data (async bus)
> > > >     • CAN (one single CAN bus)
> > > >
> > > > • Expansion via internal GPIO headers
> > > > • OVMS firmware
> > > >
> > > >
> > > > This could be a display for OVMS, or in general be a very flexible form of in-car or general purpose hacker display.
> > > >
> > > > The entire project would be geared towards getting the cost down. I’m trying to get an idea of what we can get this done for.
> > > >
> > > > What do people think? Is this any use?
> > > >
> > > > Regards, Mark.
> > > >
> > > > 1] Easily obtainable enclosure
> > > >
> > > > The idea being to use this along with a standard car mount (perhaps magnetic - there are lots)
> > > > <T29ba5XNxXXXXXXXXX_!!1821337140.jpeg>
> > > > <TB2CXEYiRTH8KJjy0FiXXcRsXXa_!!1846091269.jpg>
> > > > <TB2BE7_sFXXXXchXXXXXXXXXXXX_!!2158137177.jpg>
> > > >
> > > > <T260HcXz4aXXXXXXXX_!!1821337140.jpg>
> > > >
> > > >
> > > >
> > > > 2] Other examples, for comparison
> > > > <1f6d36f5$1$162845d3397$Coremail$guangzhouxinghai$163.com>
> > > > <be0923f$4$162845d3397$Coremail$guangzhouxinghai$163.com>
> > > > <39c78b1e$3$162845d3397$Coremail$guangzhouxinghai$163.com>
> > > >
> > > > _______________________________________________
> > > > 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
> > _______________________________________________
> > 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20180404/b3cb26b3/attachment.htm>