![]() provide a new translation for configurator, or help us maintain the existing ones (see below).Next place is the github issue tracker:īefore creating new issues please check to see if there is an existing one, search first otherwise you waste people's time when they could be coding instead! The best place to start is the Betaflight Slack (registration here). If you want to contribute to our efforts financially, please consider making a donation to us through PayPal. # Cleanflight/NAZE 1.12.If you want to contribute financially on an ongoing basis, you should consider becoming a patron for us on Patreon. I feel like this is progress, but still not good enough. Other than that the settings are the same as they would be with my FrSky module in the TX. I set the Model up on the TX to "PROTO DSM2" and "DSMTYPE: DSM2only" I'm using a Turnigy 9XR with an OrangeRx 2.1 module. I've tried setting up switches to arm but nothing seems to work. The green LED (next to GND) blinks slowly and never stops. Ok sloscotty, I reflashed it to your exact setup there and now when I plug in the battery the motors don't go crazy!.but I can't get it to respond to anything. I compared my dump with yours and noticed a couple of things (may or may not be applicable). (0, 02:58 PM)sloscotty Wrote: I am running Cleanflight/NAZE 1.12.0 on mine (this is what it came with). Most of the other stuff where we have common variables looks OK (upon quick glance). I also have a looptime variable that is not in your dump. Looks like you have Oneshot125 turned on - I do not. I am running Cleanflight/NAZE 1.12.0 on mine (this is what it came with). (0, 02:27 PM)jamesw Wrote: Ok, then my TX is definitely bound. ![]() Also you can see that I have "motor_pwm_rate=16000", again because someone with my same issue said that worked for them, but I've tried 32000 with the same problem.ĭo you notice anything in these instructions that looks incorrect? Because that's what I've followed each time I've flashed it (and followed the very first time I set it up without flashing it to a different firmware). However I've also flashed it as a Naze32 and had the same problems. I flashed it most recently to AlienFlight because I had seen someone with my same issue saying that worked for them. Just in case it's helpful here is a dump from the Betaflight configurator. Then do what you need with your Tx to bind. After 5-10 seconds, it will start to blink rapidly - this indicates the on-board Rx is in bind mode. The red light will blink slowly at first. To enter binding mode, turn off your transmitter, and plug in the FC (via USB is OK). (0, 02:22 AM)sloscotty Wrote: When bound (and detecting your transmitter), the red led at the front of the FC should light solid. I did read somewhere someone with this exact issue set their "pwm_motor_rate=16000" and it fixed it for them but not for me. ![]() I added a new Model to the TX and set it to use DSM2. I use that with an FrSky module and a D4r receiver. I have a fully built 210 quadcopter with Naze32 that works fine. I am unable to plug in USB and battery at the same time because that supposedly fries this board. When I plug in a battery, the motors just go straight to full power and the quadcopter isn't responsive to any commands from the TX. Also in Cleanflight if the TX is turned on the numbers on the Receiver tab are all 998 instead of 1500 (if the TX is off). The reason I think it worked is that if the TX is turned on, the LED on the Pico doesn't flash red but is solid. Initially I had problems binding until I saw advice to "literally touch the antenna from the RX and TX together during binding" and that appeared to work. Got it all set up using these instructions. I just picked up a Quanum Pico flight controller (which is the same thing as a Micro SciSky FC) and an OrangeRx (version 2.1) module for my Turnigy 9xr receiver. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |