[Ovmsdev] Time, Apps, 3.1.007, and others

[Mark Webb-Johnson]

> - Using BT, to avoid a full-blown and BOM heavy display, maybe an nRF5 chip based display (there are ILI drivers for everything nowadays :-) ) It’s a different dev path, but it’s overall far less complexe than ESP
> - Maybe stick to Wifi (the web socket is already there for streaming metrics) and pick an ESP8266 ? It’s marginally cheaper but still, could be easier


The idea was to use the same code base. Also make something perhaps useful to normal ESP32 users (to increase usability and quantities). It it hard to find a 3.5” display in a case, with a decent microcontroller (enough flash, ram), and wifi/bluetooth.

The problem with using wifi between OVMS v3 and this is that means access point mode, which makes things messy for internet access. Also power hungry. Bluetooth is slower, but lower power and GATT seems to suit our needs. Very scriptable. But for something standalone, Wifi is very useful.

I’m not really sure where this side-project is going. It just seemed like an itch I wanted to scratch. The issue is getting the price down (which means dropping features and that always hurts). We can simply put the display + ESP32 module + CP2102 in a box, and that would be cheap and simple. But, it seems that we have all this capability and it seems dumb not to use it.

Regards, Mark.

> On 15 Jun 2018, at 2:18 PM, Julien “JaXX” Banchet <jaxx at jaxx.org> wrote:
> 
> Hi,
> 
> If you’re going that way:
> - Using BT, to avoid a full-blown and BOM heavy display, maybe an nRF5 chip based display (there are ILI drivers for everything nowadays :-) ) It’s a different dev path, but it’s overall far less complexe than ESP
> - Maybe stick to Wifi (the web socket is already there for streaming metrics) and pick an ESP8266 ? It’s marginally cheaper but still, could be easier
> 
> Jb./.
> 
> On 15 Jun 2018 at 07:01 +0200, Mark Webb-Johnson <mark at webb-johnson.net>, wrote:
>> 
>> The original idea was for a companion display to work alongside OVMS (perhaps using bluetooth GATT to talk to OVMS v3.1 modules). But using the same firmware framework seems sensible, and it ends up being pretty similar to a full OVMS v3.1.
> _______________________________________________
> 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/20180615/074db30c/attachment.htm>