03-May-2017, 04:44 PM (This post was last modified: 05-May-2017, 08:48 AM by Frosty.)
Hi!
I'm having trouble with my first build, which is a race quadcopter. I decided to post here as I feel this may be a newbie issue.
I have all the hardware connected and working. Configuration in Betaflight is underway and going well, all for one hiccup.
When I try disabling horizontal mode my buzzer starts going crazy. Is there any way to diagnose this? I'm not sure what information about my setup maybe useful so I'll just try to answer best if you need more details. Although I may start with the following:
FC: Revo F405 Reciever: X4RSB Transmitter: Q X7
Aux1 (SD switch on Taranis) is used to switch between Armed + Armed and Air Mode Aux2 (SA switch on Taranis) is used to switch Horizon mode on and off
I tried disabling horizon mode all together, but that only sets off the buzzer until I set horizon mode back on again.
03-May-2017, 06:33 PM (This post was last modified: 03-May-2017, 06:36 PM by Frosty. Edit Reason: added info )
(03-May-2017, 05:24 PM)unseen Wrote: That's an odd one Frosty!
I'm scratching my head here. Can you upload a picture of how you have set things up on the modes tab?
Sure thing, here you go.
Currently the sliders cover both switch states (up/down), but if I adjust them to i.e. 1800 - 2100 and save settings, the buzzer starts going crazy. If I flip the switch into the range the buzzer goes quiet.
[edit] Also, if I remove horizon mode all together the buzzer wont stop whining whatever the switch position.
Well, I'm baffled, but I do see something that might be a clue.
At the top of the screen, it says your Revo is connected to a battery but that the battery only has 4V. Maybe the Horizon thing is just a coincidence and the beeper is warning that you have a low battery?
Quote:Tone sequences Buzzer tone sequences (square wave generation) are made so that : 1st, 3rd, 5th, .. are the delays how long the beeper is on and 2nd, 4th, 6th, .. are the delays how long beeper is off. Delays are in milliseconds/10 (i.e., 5 => 50ms). Sequences available in Cleanflight v1.9 and above are :
Code:
0 GYRO_CALIBRATED 20, 10, 20, 10, 20, 10 Gyro is calibrated 1 RX_LOST_LANDING 10, 10, 10, 10, 10, 40, 40, 10, 40, 10, 40, 40, 10, 10, 10, 10, 10, 70 SOS morse code 2 RX_LOST 50, 50 TX off or signal lost (repeats until TX is okay) 3 DISARMING 15, 5, 15, 5 Disarming the board 4 ARMING 30, 5, 5, 5 Arming the board 5 ARMING_GPS_FIX 5, 5, 15, 5, 5, 5, 15, 30 Arming and GPS has fix 6 BAT_CRIT_LOW 50, 2 Battery is critically low (repeats) 7 BAT_LOW 25, 50 Battery is getting low (repeats) 8 NULL multi beeps GPS status (sat count) 9 RX_SET 10, 10 RX is set (when aux channel is set for beep or beep sequence how many satellites has found if GPS enabled) 10 ACC_CALIBRATION 5, 5, 5, 5 ACC inflight calibration completed 11 ACC_CALIBRATION_FAIL 20, 15, 35, 5 ACC inflight calibration failed 12 READY_BEEP 4, 5, 4, 5, 8, 5, 15, 5, 8, 5, 4, 5, 4, 5 GPS locked and copter ready 13 NULL multi beeps Variable # of beeps (confirmation, GPS sat count, etc) 14 DISARM_REPEAT 0, 100, 10 Stick held in disarm position (after pause) 15 ARMED 0, 245, 10, 5 Board is armed (after pause ; repeats until board is disarmed or throttle is increased)
These are in "On" "Off" duration (easiest to think of "long" "short"). Do you recognize the pattern that your beeper is making? It might (or might not) lead somewhere.
(03-May-2017, 08:19 PM)unseen Wrote: Well, I'm baffled, but I do see something that might be a clue.
At the top of the screen, it says your Revo is connected to a battery but that the battery only has 4V. Maybe the Horizon thing is just a coincidence and the beeper is warning that you have a low battery?
4V is from powering the FC via USB. I tried powering the FC via LiPo, and have the same issue.
These are in "On" "Off" duration (easiest to think of "long" "short"). Do you recognize the pattern that your beeper is making? It might (or might not) lead somewhere.
Thanks sloscotty, unfortunatley my buzzer sound doesn't coincide with any of the beeping schemes provided. Mine is a constant undisturbed high pitch beep that can only be disabled with Horizon mode on.
I'll try to create a new configuration, while avoiding configuring horizon mode and see if that helps. BTW, is there a way to export a profile's configuration to view in txt mode? Maybe even display an entire configuration in CLI?
Also, I suppose I can try a different buzzer. Could it be that the one I'm currently using is incompatible? During the startup sequence, everything sounds fine. I resolidered it from an old graphics card. I couldn't a datasheet for it online so I assumed it'll work.
04-May-2017, 09:47 AM (This post was last modified: 04-May-2017, 10:06 AM by Frosty.)
I found how to dump the configuration. I put it up on google docs, hoping this may shed some light on what may be going on: link
Also, I'm wondering if setting angle mode may help? i.e. switch SH will toggle between Horizon and Angle mode. I'll give it a try when I have my FC at hand.
(03-May-2017, 09:41 PM)Frosty Wrote: 4V is from powering the FC via USB. I tried powering the FC via LiPo, and have the same issue.
Thanks sloscotty, unfortunatley my buzzer sound doesn't coincide with any of the beeping schemes provided. Mine is a constant undisturbed high pitch beep that can only be disabled with Horizon mode on.
I'll try to create a new configuration, while avoiding configuring horizon mode and see if that helps. BTW, is there a way to export a profile's configuration to view in txt mode? Maybe even display an entire configuration in CLI?
Also, I suppose I can try a different buzzer. Could it be that the one I'm currently using is incompatible? During the startup sequence, everything sounds fine. I resolidered it from an old graphics card. I couldn't a datasheet for it online so I assumed it'll work.
It turns out that this is a known problem. I see that your board is flashed with the REVO target. Flash it with the AIRBOTF4 target instead and your buzzer woes will be solved!
04-May-2017, 08:28 PM (This post was last modified: 05-May-2017, 08:12 AM by Frosty.)
(04-May-2017, 09:56 AM)unseen Wrote: It turns out that this is a known problem. I see that your board is flashed with the REVO target. Flash it with the AIRBOTF4 target instead and your buzzer woes will be solved!
You are a genius, this helped and the constant beep has gone away!
I flashed AirbotF4 with full FC erase enabled. Did the trick!
The following 1 user Likes Frosty's post:1 user Likes Frosty's post • unseen