Litterbug,
Happy Easter and thanks for your reply. The plane is a 40" wingspan, foamboard, high-wing, 2-aileron, profile v-tail of my own design. I used 2 transmitters for the setup and tests - a Spektrum DX5 (no mixes, no dual-rate, no exponential, no subtrims, nothing programmable) and a DX7. With both transmitters the Aura was doing all the mixing for the v-tail. It also was doing the servo reversing, subtrims, etc. There was never any problem with binding the rx to the tx.
I tried doing the no-computer setup, but button accessibility was an issue so I used the Config Tool. I reversed the left aileron to account for the mechanical setup of the servos on the wing and everything was fine there. No matter what combinations of reversals (left, right, neither, both) I used for the ruddervators, at least one surface was always out of whack. The best I could get was the no-gyro mode worked correctly, but the rudder in the 3- and 6-axis mode moved the wrong way. But when I reversed the rudder at the tx, all was well. This was the same whether I used the DX5 or DX7.
So I had what looked to be a completely functioning system - it bound to either tx, the controls all moved in the correct direction in all modes - no gyro, 3-axis, 6-axis and take-off assist, the subtrims were correct for all surfaces and the modes switched correctly according to the correct tx switch. All the settings remained correct even through power cycles. In 3- and 6-axis stabilization mode, when I moved he plane I could hear the servos respond and could see the control surfaces move in the correct direction. In 6-axis, the more I displaced the plane, the more the surfaces moved. In short, everything worked correctly and the plane was ready for its maiden flight. I even did some short taxiing in my basement.
So while I appreciate your kind offer of helping me make sure that everything is correctly hooked up, I'm pretty sure I had that nailed. But thanks anyway.
What I do need help with is what happened next. I was unhappy with that rudder reversal on the tx, so I decided to keep experimenting with the config to see if I could get rid of it. I saved a copy of the acf file so I could get back to where I was in case I broke the config. Then I changed the v-tail type to see if I could get rid of the tx reversal. After a half hour of switching reversals and stuff, it wasn't working, so I decided to just live with the tx rudder reversal for now and re-loaded the saved config file and cycled power. The ruddervators did not move correctly. After another hour of trying to get them to work, I decided to do a factory reset of the Aura and then reload the config file. I followed the instructions in the FT video using the conversion file and then reloaded the config file. Still no joy. So I tried converting again and this time I got the same problem the OP had - the infinite sensor calibration with the flashing blue light. The device is not dead because I can bind it to either tx and I can connect to it with the Config tool. I was able to convert it again, update the firmware to 1.16 and convert it again and bind it again.
What happens now when I power on with the transmitter already on - the rear control surfaces move once, then settle to their neutral positions. The receiver's orange LED comes on indicating that it is bound to the transmitter (if I turn off the transmitter the light goes out). The blue LED blinks 6 times, pauses, blinks 6 times, pauses, repeats the cycle until power is removed.
So that's what I need help fixing. How to get it to finish the sensor calibration so it can continue booting up. It went from ready to maiden to a brick with no hardware changes at all. The only thing that changed was loading a previously working config file, resetting it to factory default and upgrading the firmware, none of which should have bricked it. I've tried powering it on while propping the plane level (according to a spirit level I put on top of the fuselage), I've waited hours for it to complete and nothing makes a difference. So any help would be appreciated.
Thanks
Happy Easter and thanks for your reply. The plane is a 40" wingspan, foamboard, high-wing, 2-aileron, profile v-tail of my own design. I used 2 transmitters for the setup and tests - a Spektrum DX5 (no mixes, no dual-rate, no exponential, no subtrims, nothing programmable) and a DX7. With both transmitters the Aura was doing all the mixing for the v-tail. It also was doing the servo reversing, subtrims, etc. There was never any problem with binding the rx to the tx.
I tried doing the no-computer setup, but button accessibility was an issue so I used the Config Tool. I reversed the left aileron to account for the mechanical setup of the servos on the wing and everything was fine there. No matter what combinations of reversals (left, right, neither, both) I used for the ruddervators, at least one surface was always out of whack. The best I could get was the no-gyro mode worked correctly, but the rudder in the 3- and 6-axis mode moved the wrong way. But when I reversed the rudder at the tx, all was well. This was the same whether I used the DX5 or DX7.
So I had what looked to be a completely functioning system - it bound to either tx, the controls all moved in the correct direction in all modes - no gyro, 3-axis, 6-axis and take-off assist, the subtrims were correct for all surfaces and the modes switched correctly according to the correct tx switch. All the settings remained correct even through power cycles. In 3- and 6-axis stabilization mode, when I moved he plane I could hear the servos respond and could see the control surfaces move in the correct direction. In 6-axis, the more I displaced the plane, the more the surfaces moved. In short, everything worked correctly and the plane was ready for its maiden flight. I even did some short taxiing in my basement.
So while I appreciate your kind offer of helping me make sure that everything is correctly hooked up, I'm pretty sure I had that nailed. But thanks anyway.
What I do need help with is what happened next. I was unhappy with that rudder reversal on the tx, so I decided to keep experimenting with the config to see if I could get rid of it. I saved a copy of the acf file so I could get back to where I was in case I broke the config. Then I changed the v-tail type to see if I could get rid of the tx reversal. After a half hour of switching reversals and stuff, it wasn't working, so I decided to just live with the tx rudder reversal for now and re-loaded the saved config file and cycled power. The ruddervators did not move correctly. After another hour of trying to get them to work, I decided to do a factory reset of the Aura and then reload the config file. I followed the instructions in the FT video using the conversion file and then reloaded the config file. Still no joy. So I tried converting again and this time I got the same problem the OP had - the infinite sensor calibration with the flashing blue light. The device is not dead because I can bind it to either tx and I can connect to it with the Config tool. I was able to convert it again, update the firmware to 1.16 and convert it again and bind it again.
What happens now when I power on with the transmitter already on - the rear control surfaces move once, then settle to their neutral positions. The receiver's orange LED comes on indicating that it is bound to the transmitter (if I turn off the transmitter the light goes out). The blue LED blinks 6 times, pauses, blinks 6 times, pauses, repeats the cycle until power is removed.
So that's what I need help fixing. How to get it to finish the sensor calibration so it can continue booting up. It went from ready to maiden to a brick with no hardware changes at all. The only thing that changed was loading a previously working config file, resetting it to factory default and upgrading the firmware, none of which should have bricked it. I've tried powering it on while propping the plane level (according to a spirit level I put on top of the fuselage), I've waited hours for it to complete and nothing makes a difference. So any help would be appreciated.
Thanks
