[Ovmsdev] V3 size and arrangement

[Mark Webb-Johnson]

I've got the first OVMS v3 development board in my hands now. The components seem fine, and I'm finalizing the QC program that checks everything to make sure all is ok. 16MB flash with OTA capability, Wifi, Bluetooth, 3xCAN bus, lots of GPIO, switched 12V, power by USB/12V, SD card reader/writer, optional 2G/3G/4G modem (with GPS), two expansion slots, USB, and an external expansion connector - all look good.

Both 3G and 4G development expansion boards are also being made now, and I should have those next week.

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 the 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?

In the meantime, on with development (now that at last I have a target in my hands).

Mark

-------------- next part --------------
A non-text attachment was scrubbed...
Name: image1.jpeg
Type: image/jpeg
Size: 224610 bytes
Desc: not available
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20170519/18a6cf7e/attachment-0014.jpeg>
-------------- next part --------------

-------------- next part --------------
A non-text attachment was scrubbed...
Name: image2.jpeg
Type: image/jpeg
Size: 264370 bytes
Desc: not available
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20170519/18a6cf7e/attachment-0015.jpeg>
-------------- next part --------------

-------------- next part --------------
A non-text attachment was scrubbed...
Name: image3.jpeg
Type: image/jpeg
Size: 184293 bytes
Desc: not available
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20170519/18a6cf7e/attachment-0016.jpeg>
-------------- next part --------------

-------------- next part --------------
A non-text attachment was scrubbed...
Name: image4.jpeg
Type: image/jpeg
Size: 302658 bytes
Desc: not available
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20170519/18a6cf7e/attachment-0017.jpeg>
-------------- next part --------------

-------------- next part --------------
A non-text attachment was scrubbed...
Name: image5.jpeg
Type: image/jpeg
Size: 196565 bytes
Desc: not available
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20170519/18a6cf7e/attachment-0018.jpeg>
-------------- next part --------------

-------------- next part --------------
A non-text attachment was scrubbed...
Name: image6.jpeg
Type: image/jpeg
Size: 135459 bytes
Desc: not available
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20170519/18a6cf7e/attachment-0019.jpeg>
-------------- next part --------------

-------------- next part --------------
A non-text attachment was scrubbed...
Name: image7.jpeg
Type: image/jpeg
Size: 786807 bytes
Desc: not available
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20170519/18a6cf7e/attachment-0020.jpeg>