Crazyradio PA No Wireless Connection [SOLVED]
Posted: Thu Apr 01, 2021 2:25 am
Hello,
My issue is mainly regarding the Crazyradio PA and its connection to the crazyflie when trying to scan for a channel. In normal cases in the past, when in bootloader mode, the drone would find the radio to be 0/80/2M and then would be able to fly by python programming via the terminal. However, recently, something has happened which prevents the scanner to detect the correct channel and instead always reads "0/0/2M" which when connecting to the drone, does not show any movements in the fly control page on VM when moving the drone by hand. Since the correct channel is 80, I have tried to change the code as well as add additional pieces which directly work on channel 80. However, nothing has changed or worked. Below are some of the work I have done to try and fix this with no results:
1. Constant reset of drone to bootloader and scan on Virtual Machine (PA dongle selected for USB) -> (always reads 0/0/2M)
2. Using crazyflie-firmware packages of 2019, 2020(cf2), and 2021(cf2) from PC to try step 1 again -> (again reads 0/0/2M)
3. Changing everything, including the mentioned code parameters, to the new channel 0 to see a probable change ->(during run of python code for i.e. swarmSequenceCircle.py, there is a long pause without any events until battery runs out)
4. Tried scanning with crazyflie on first mode(on mode) -> (when on first mode, nothing can be scanned therefore no interface)
5. Building the crazyflie-firmware code with 0/80/2M parameters for radio, adding that inside the makefile, and trying bootloader scan -> (no result) 6. Trying step 5 with programming the crazyflie on bootloader with the modified cf2.elf -> (no result)
7. Tried to "upgrade" PA w/ given directions on VM, dongle would automatically disconnect and not allow further progress -> (no result)
8. Changing parameters of crazyflie on configure 1.0 (2.0 doesn't work) based on 0/0/2M and 0/80/2M ->(no result, code won't run says multiple packets lost and error in swarm part of the code) 9. Tried USB drone connection with the same process on either 0/0/2M or 0/80/2M parameters on the code i.e. swarmSequenceCircle.py to run -> (no result)
10. Interesting bug: The drone would not work until a glitch happened where I pressed the power button for too long causing only the M2 LED to flash. I disconnected the battery to be able to use the power button again and when writing 2019 firmware on the drone, it detected 0/80/2M and actually flew when running the code. After that, unfortunately, it did not work anymore(meaning detection of 0/80/2M) and when the same glitch steps were taken, nothing changed like it did before
Please help me understand what my issue is since this is very important to me to get this connection to work so I can test the drone.
My issue is mainly regarding the Crazyradio PA and its connection to the crazyflie when trying to scan for a channel. In normal cases in the past, when in bootloader mode, the drone would find the radio to be 0/80/2M and then would be able to fly by python programming via the terminal. However, recently, something has happened which prevents the scanner to detect the correct channel and instead always reads "0/0/2M" which when connecting to the drone, does not show any movements in the fly control page on VM when moving the drone by hand. Since the correct channel is 80, I have tried to change the code as well as add additional pieces which directly work on channel 80. However, nothing has changed or worked. Below are some of the work I have done to try and fix this with no results:
1. Constant reset of drone to bootloader and scan on Virtual Machine (PA dongle selected for USB) -> (always reads 0/0/2M)
2. Using crazyflie-firmware packages of 2019, 2020(cf2), and 2021(cf2) from PC to try step 1 again -> (again reads 0/0/2M)
3. Changing everything, including the mentioned code parameters, to the new channel 0 to see a probable change ->(during run of python code for i.e. swarmSequenceCircle.py, there is a long pause without any events until battery runs out)
4. Tried scanning with crazyflie on first mode(on mode) -> (when on first mode, nothing can be scanned therefore no interface)
5. Building the crazyflie-firmware code with 0/80/2M parameters for radio, adding that inside the makefile, and trying bootloader scan -> (no result) 6. Trying step 5 with programming the crazyflie on bootloader with the modified cf2.elf -> (no result)
7. Tried to "upgrade" PA w/ given directions on VM, dongle would automatically disconnect and not allow further progress -> (no result)
8. Changing parameters of crazyflie on configure 1.0 (2.0 doesn't work) based on 0/0/2M and 0/80/2M ->(no result, code won't run says multiple packets lost and error in swarm part of the code) 9. Tried USB drone connection with the same process on either 0/0/2M or 0/80/2M parameters on the code i.e. swarmSequenceCircle.py to run -> (no result)
10. Interesting bug: The drone would not work until a glitch happened where I pressed the power button for too long causing only the M2 LED to flash. I disconnected the battery to be able to use the power button again and when writing 2019 firmware on the drone, it detected 0/80/2M and actually flew when running the code. After that, unfortunately, it did not work anymore(meaning detection of 0/80/2M) and when the same glitch steps were taken, nothing changed like it did before
Please help me understand what my issue is since this is very important to me to get this connection to work so I can test the drone.