I was thinking of working on some HID/HUD/Accessory code for the OVMS, communicating either over Wifi (with AP or AP+Client mode), BLE, or simply streaming over an UART built on EGPIOs (the last one suffering less latency and being probably more memory tight but needs HW mods)
The “Accessory” mode would simply stream out data, and eventually accept input, all in something close to the protocol meant for Nextion’s HMI Displays

For talking directly to Apps, the intention is to expose metrics using bluetooth BLE GATT. This would probably be the most suitable approach for a HUD.

For talking to Apps via a server, ovms v3 will use MQTT.

UART/WIFI would also be possible, but would require building a protocol. Perhaps also MQTT?

Regards, Mark.

On 4 Jan 2018, at 8:30 PM, Julien “JaXX” Banchet <jaxx@jaxx.org> wrote:

Hi all ! And Happy New Year
Back after an unexpected seasonal depression :-/

I can also recommend Kivy, though, for smartphones, I’m still a PhoneGap fan (AppFramework seems nice as well)
Raspi+Disp is running Kivy anyhow, as I believe Python is better suited for educational purposes, easy to hack, and has nice support for Pi’s.

I was thinking of working on some HID/HUD/Accessory code for the OVMS, communicating either over Wifi (with AP or AP+Client mode), BLE, or simply streaming over an UART built on EGPIOs (the last one suffering less latency and being probably more memory tight but needs HW mods)
The “Accessory” mode would simply stream out data, and eventually accept input, all in something close to the protocol meant for Nextion’s HMI Displays

Really need to kick myself.

JB./.


On 4 Jan 2018 at 13:15 +0100, Andreas Ecker <aecker2@gmail.com>, wrote:

Kivy is a great framework for cross-platform development for Android, iOS, Linux, Windows and OSX: https://kivy.org/#home
_______________________________________________
OvmsDev mailing list
OvmsDev@lists.teslaclub.hk
http://lists.teslaclub.hk/mailman/listinfo/ovmsdev