Casainho, Nick,
I created a wiki page to describe the L1, L2/L3 data structure
https://github.com/OpenSource-EBike-firmware/SW102_LCD_Bluetooth/wiki/DataStructure
I tried my best to grep it out of the 850c code (and motor firmware)
But can you review and correct if needed.
I don't know the meaning of the fields (I can assume a lot out of the names) => can somebody complete the short description.
Next step : determine which ones need to be available on BLE ( and in which modus read/readwrite ....)
Once we agree on the (BLE) datafields I can try to create a POC of a custom Gatt server code and start on the android app
Casainho,
In a previous post you mentioned you will be focusing on the 850c, but aren't there parts that can be in common ?
If we take the L1, L2/L3 as a common structure I would assume that the uart handling is the same for both.
I created a wiki page to describe the L1, L2/L3 data structure
https://github.com/OpenSource-EBike-firmware/SW102_LCD_Bluetooth/wiki/DataStructure
I tried my best to grep it out of the 850c code (and motor firmware)
But can you review and correct if needed.
I don't know the meaning of the fields (I can assume a lot out of the names) => can somebody complete the short description.
Next step : determine which ones need to be available on BLE ( and in which modus read/readwrite ....)
Once we agree on the (BLE) datafields I can try to create a POC of a custom Gatt server code and start on the android app
Casainho,
In a previous post you mentioned you will be focusing on the 850c, but aren't there parts that can be in common ?
If we take the L1, L2/L3 as a common structure I would assume that the uart handling is the same for both.