[Ovmsdev] V3 size and arrangement

Sat May 20 05:46:52 HKT 2017

What about iTead Nextion displays?
Despite having to use a Windows app to design the interface (then update the display directly or with a file on an uSD for everyone else), the display itself uses plain light UART to communicate... The new ones have extra gpios and sound generation... Cheap enough, the only thing that bothers me is that they are closed source otherwise.

JB

--
Julien Banchet +33651886877

On 19 May 2017, 23:28 +0200, Greg D. <gregd2350 at gmail.com>, wrote:
> I'm using this one with my Raspberry Pi. http://www.mcmelectronics.com/product/83-16786 There's also a larger one. I have it mounted separate from the Pi itself, which is perhaps an issue (ugly cables), but the larger pixel count makes the full X environment usable. Resistive touch overlay seems to work well with a stylus / fingernail, where capacitive touch and finger is too sensitive in a bouncing car, and too imprecise for many apps..
>
> Which leads me to a question: Architecturally, is it better to have the display hosted directly on the OVMS module, or to have it talk to an off-board server such as the Pi, or have both of them meet up somewhere in the Cloud?
>
> Greg
>
> P.s. Also another preference here for option (A). I think a thinner board will go better under the dash (glove box) of the Roadster, where a thicker box would extend down and perhaps be visible. But, I don't think it's a show-stopper either way.
>
>
> Michael Balzer wrote:
> > Here's a 3.5 inch TFT touch screen for Arduino compared to the V2 box.
> >
> > It's this one:
> > http://hobbycomponents.com/shields/642-mcu-friend-35-colour-tft-touch-screen
> >
> >
> >
> >
> >
> > The TFT module itself is just 3mm thick:
> >
> >
> >
> >
> > This kind of display would already make a great dashboard addition.
> >
> > But we should select one with a proper touch layer adjustment, this one from mcufriend has blind areas at two screen edges (calibration won't help with that).
> >
> > Regards,
> > Michael
> >
> >
> > Am 19.05.2017 um 16:40 schrieb Mark Webb-Johnson:
> > > I see what you are saying. Using a raspberry pi with a 3.5" display as an example, that doesn't fit at all on the old OVMS v2 case, but would fit on our side-by-side option (A) board. In fact, the Raspberry pi style cases are a pretty good size. A bit bigger than OVMS v2, but still reasonable. For example, the case below is 4" x 2.8" x 1.25" (deep). 100mm x 70mm x 30mm. That is a pretty nice size. Those 3.5" SPI touch panel displays are about U$10 for quantity 1. I wonder if we could squeeze this down to something exactly the same size as a raspberry pi? With the same mounting holes. There are a lot of cases around for that, and many 3D printing templates for something to be customized. The width is about right, but we would have to go to a stacked arrangement. Something big enough for a 3.5" display. Mark On 19 May 2017, at 8:56 PM, Michael Balzer <dexter at expeedo.de> (mailto:dexter at expeedo.de) wrote:
> > > > That looks great :) From a first test (A) should still fit in the Twizy glove box, so should fit in other mounting places as well. As mentioned earlier I think a touch screen would make a nice addon, and (A) seems to be better for mounting a large display directly to the board. That should still make a nice & handy box. I think (B) would become very clunky with a large display. So I'm tending towards (A). Regards, Michael
> > > > > Am 19.05.2017 um 08:23 schrieb Mark Webb-Johnson: But, having seen it and held it, I'm now having second thoughts about the layout. As you can see from the attached pictures, the expansion slots are each about 60mm x 45mm. Putting two of those on the board makes it about 9.5cm x 9.5cm square. Height will be similar (a little bit taller) than the current OVMS v2. This is a first draft run only, just to confirm the components, but as you can see there is quite a lot of blank space and traces for the two expansion slots. That, and the sheer number of connectors we have, dominate the board. Let's call this arrangement (A). There was an alternative arrangement that I considered a while back. That would be to have just one expansion slot, but use stackable connectors (so multiple boards could be piggybacked on each other). In that arrangement, the expansion slot could be either vertical or horizontal, with a vertical arrangement being close in size to the existing OVMS v2
  (but th
e height would need to be much taller to accommodate the piggybacked expansion boards). Let's call this arrangement (B). It doesn't change the wiring. Just the size and arrangement of components on the board, as well as the box housing this all. (A) ends up with a 1" wider+taller box of about the same thickness, while (B) ends up with a box about the same width and height, but significantly thicker. To me, it seems that (A) is more automotive, and (B) more hobbyist. What do people think?
> > > >
> > > > -- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 (tel:02333%20/%20833%205735) * Handy 0176 / 206 989 26 (tel:0176%20/%20206%20989%2026) _______________________________________________ OvmsDev mailing list OvmsDev at lists.teslaclub.hk (mailto:OvmsDev at lists.teslaclub.hk) http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
> > > >
> > > >
> > > > _______________________________________________ OvmsDev mailing list OvmsDev at lists.teslaclub.hk (mailto:OvmsDev at lists.teslaclub.hk) http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
> > -- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 (tel:02333%20/%20833%205735) * Handy 0176 / 206 989 26 (tel:0176%20/%20206%20989%2026)
> >
> > _______________________________________________ OvmsDev mailing list OvmsDev at lists.teslaclub.hk (mailto:OvmsDev at lists.teslaclub.hk) http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
> _______________________________________________
> OvmsDev mailing list
> OvmsDev at lists.teslaclub.hk
> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20170519/ff653ca7/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 1.2
Type: application/octet-stream
Size: 246421 bytes
Desc: not available
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20170519/ff653ca7/attachment.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 1.3
Type: application/octet-stream
Size: 238973 bytes
Desc: not available
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20170519/ff653ca7/attachment-0001.obj>