As I already wrote, I made a general design change of the communication interface. It is currently in a newFeature branch. The UART communication is ready and must be tested. Only thenRF24 communication is not ready and still a hard bunch of work because a protocol must be implemented and this then adapted to the interface. The problem is: At the moment I can't find the time and motivation to do this.
Behind that are some considerations from personal site and community driven:
- it seams that long term nRF communication in this project is not in the main focus of the community. So maybe I will do all the work for nothing...
- There are so many features where I want to put my focus on, that the motivation for nRF shrinks
- Other for me personal important projects beside software wait for my attention (Publication of my printed board drive, A new carbon board with battery case etc., and, and...)
- It is summer!!
- I ordered a feather and that's the way I want to go in long term.
At the moment we have a working version of the nRF implementation (ArduBoardControl V0.6.2 with VescUartControl V0.1.4). There are some bugs only in the calculation of telemetric values that I can fix at next (When will not focus on nRF
). So ArduBoardControl V 0.6.x will be in future not anymore supported with new features. Sorry folks. I will switch completely to Feather/bluetooth.
If there is somebody out there who will take over the implementation of nRF to the new interface will get my support in explanation of the new interface and the planned design of the communication protocol for the nRF as well in testing.
As soon as I get my feather board and I setup my hardware, I will test the newFeature branch and bring it then to the master branch. The last stable Version 0.6.x of the ArduBoardControl (including the bug fix in the telemetry) will then be tagged and available as release. I will have then have a new major release 1.x.x with the new interface.
I hope you can accept my decision made.