LibrePilot Forum
General Category => LibrePilot2Go => Topic started by: Sen on August 07, 2019, 03:02:17 pm
-
Hello,
I am currently trying to set up the Bluetooth connection between a smartphone and a CC3D through a HC06 Bluetooth module. It is not my first time and I have already managed to make it work fine, but for some reasons [...] I had to re-update the librepilot firmware on my CC3D board and now I have an issue.
The symptoms are quite similar with this previous post :
https://forum.librepilot.org/index.php?topic=4153.0
Execpted that I carefully checked the connection between the HC 06 and the CC3D.
Bluetooth icon is green and the 4 squares icon is blinking red :
WARNING
UAVO problem.
Check the OPLink connection and/or try reducing the serial link speed
FC UAVO Version : 00000000
LP2Go UAVO Version : 086dc116
I alreadly tryed with different serial speed, but the warning remains inchanged.
Any help would be greatly appreciated!
-
hi,
FC UAVO Version : 00000000
Seems LP2Go do not retrieve the UAVO from board...
Is the board flashed with rel-16.09 and running ?
Check the port (Main or Flexi) used by bluetooth module, set as Telemetry in Hardware tab.
Remember also the telemetry stream goes to USB if connected to the computer.
-
Thanks for your reply,
I tryed with flashing different releases for understanding prupose: from 15.09 to the last 16.09 'next' version (r782). Everytime I made sure to match the LP2Go UAVO Version with the GCS UAVO Hash. Hoped different behaviour, but not.
I am using the Flexi-IO port, PPM + telemetry. No USB connected when I was trying to use the Bluetooth telemetry.
-
I am using the Flexi-IO port, PPM + telemetry.
So you are using a Revolution board, not a CC3D.
With Bluetooth module blinking red there is also a pairing/communication issue between computer and module.
-
Yes, correct, I have a Revo board. Sorry for the mistake.
I never tried before to pair the module with my computer. I just did it now and I had a fixed red light on the module when I connected on COM 6 in GCS. And see attached what happened in GCS.
-
Did you set the baudrate for at least 57600 bauds ?
How about the Tx/Rx bars in bottom/right corner ?
-
Baud is set to 57600, see the capture of the hardware tab.
I also attached captures of the Tx/Rx bars in two cases :
- when USB is connected
- and when Bluetooth on COM 6 is connected
-
Check if the Bluetooth module is configured with 57600 as well, maybe he reverted back to default (9600bds) and since you are playing with AT commands you can give a try with 115200.
-
Thank you very much! It works fine again now! ;D
I just needed to set the baud to 115200. I configured the Bluetooth module last year and I even don't remember why I configured it like that. I was sure it was 57600 bauds but I was wrong...