Hi Kaity, it seems weird that your Taranis has to be switched to Spektrum in Cleanflight, unless you're using a DSMX receiver and an Orange module in the QX7. If you saw my earlier post, that's what I've been fantasising about buying. But the old Spektrum DX7S seems to be working now, so I think I'll stick with it.

I felt it was weird at first too, but that is the way the mapping works out. The Qx7 is mapped TAER and not AETR as both Cleanflight and Betaflight wish they were mapped.

Whoopy-doo, I'm in the air! I couldn't resist a sneaky little first hover in the dead of night when I'd finished setting it up, but this morning I started up the Tyrant properly and used up a battery getting a feel of it. The default Angle Mode in Cleanflight seems about right for me while get to know the aircraft and I have Horizon and Acro Modes on the other positions on the switch when I progress.

So a big thank you to Tom BD Bad for the detailed advice that got me going and also to Kaitylynn and the others who chipped in about safety and Arming. All duly noted. I still have a lot to learn and I haven't fired up the goggles yet with the Tyrant. I've a long way to go with LOS before I try and fly the Tyrant FPV.

Thanks for getting me started, and I'll log in with my progress and any questions I might have.

Cheers

Andrew

(03-Jan-2018, 10:16 PM)Droning Martyn Wrote: Hi Ubute
Welcome.
I have a similar story flying rc helis in the past.....more repairing than flying to be honest.
Got my first diatone gt200 drone in December thinking it would be easy.? Im part way up the himalayan  mountain of learning that is required althought actually enjoying the experience.
This is a great forum that has loads of advice, support and information.
Enjoy?

Hi Droning Martin

How are you going with the GT200? I hope you're enjoying it as much as I am.
I'm feeling gradually more confident as I fly the Tyrant 150 up and down the paddock, side to side in front of me. I'm doing figure eights, turning both inwards and outwards at the ends. Sort of coordinated turns. Haven't been brave enough to fly a complete circle in front of myself yet although I can do it with the toy drones. This is pretty much where I got to with the helis in the '80's, so I'm pretty chuffed.
The Tyrant has stood up to a couple of low speed crashes, but this morning I was reminded of a basic lesson. When it was passing fairly close one of the motors came adrift and down it came quite hard. All four screws had fallen out of the motor housing. All the other motors were pretty loose too. I'd been too preoccupied with the software setup of this pre-built quad that I didn't pay attention to the basic airframe. I should have checked and loc-tited all screws BEFORE they fell out.
Anyway, I got to practice my limited soldering skills because one of the wires from the ESC to the motor had broken off. The ESCs almost touch the motors on the 150 so it was tight. Fortunately nothing else was broken and the Tyrant is back in the air.

Progress update.
This morning I started flying full circuits and practicing nose in hovering. It's not so hard in angle mode, you just have to not be intimidated by the quad staring right at you. I'm definitely not ready for fpv yet but I might put a camera on a docile conventional aircraft and see how I go.

(21-Jan-2018, 08:45 AM)Ubute Wrote: I should have checked and loc-tited all screws BEFORE they fell out.

Blue thread locker on every metal to metal screw connection is not an optional step!

Hi folks,
I'm looking for some help setting up an Eachine QX65.

I've connected it to Cleanflight and performed the binding process with my Spektrum DX7S and it seems to bind ok. Everything's working correctly in the Receiver tab, but in the Modes tab I can't get it to arm. I've set the range for it to arm when I throw the Gear switch but nothing happens. The ARM channel in Cleanflight doesn't turn green when the switch is in the up position like the Angle and Horizon modes do when the Aux2 switch is in the appropriate position.

Disconnected from Cleanflight and powered by a battery the QX65 seems to bind ok, the red and white lights go steady when I turn the transmitter on. The little blue LED on the flight controller starts flashing faster when I throw the Gear switch and then goes back to steady flashing after a couple of seconds. It never glows solid like it's supposed to when it's armed.

I hope it's not a fault with the QX65.

Just to confirm you did click save and reboot/save (can't remember if it reboots from mode tab) in the modes tab, before moving to a different tab?
Does your switch show slider movement in the RX tab?

Yes, I carried out the instructions carefully, saving each step. The QX65 manual gives instructions for binding using the CLI, and you enter "save" after each step. I did the whole thing twice with the same result.

Yes, toggling the switches on the DX7S makes the little green marks move around in the sliders on the screen and I've set the range, the green bar, so the green mark is within the range when the switch is in the up position.

I've set AUX2, my three-way flaps switch, to work with ANGLE mode and HORIZON mode. The box on the left lights up green when the switch is in the appropriate position, but that doesn't happen with the ARM switch, although the little green tag moves and I've set the range to cover it when it's on. The QX65 just won't arm.

Have you calibrated the accelerometer in BF?
Anyone else got any ideas, TBH I'm kinda clutching at straws now!?

Actually I used Cleanflight initially and I did calibrate the accelerometer. Someone on the RCGroups forum said I should be using Betaflight as the manual says, not Cleanflight, so last night I did the bind process again using Betaflight. It recognised all the settings I'd done in Cleanflight and to me it all seemed exactly the same, right down to the sub-trim travel adjustments I'd made. And it still doesn't arm, although it's definitely getting a signal from the AUX1 switch (Gear). When I hit the switch the blue flashing LED changes its rhythm from steady even flashing to a short burst of double flashes for about a second and then reverts to the steady flashing. It does this both when connected to Betaflight/Cleanflight and when disconnected and running on a battery.

Now that you have betaflight. Go to the CLI and type "status" and post what it says.

Ok, here's what I get:

CLI

# status


System Uptime: 40 seconds
Voltage: 1 * 0.1V (0S battery - NOT PRESENT)
CPU Clock=72MHz, GYRO=MPU6000, ACC=MPU6000
SD card: None inserted
Stack size: 2048, Stack address: 0x10002000
I2C Errors: 0, config size: 2043, max available config: 4096
CPU:17%, cycle time: 133, GYRO rate: 7518, RX rate: 49, System rate: 9
Arming disable flags: RXLOSS CLI

That last line seems to say something?

Was your TX on when you got this status? If so, the FC is not getting signal according to the RXLOSS flag.

https://github.com/betaflight/betaflight...e-&-Safety

Sorry, silly me. I didn't think about the TX, I just plugged in the QX.

Anyway, here's the result of "status" with the TX turned on as well.

$M>lY±ÿ(S
CLI

# status
System Uptime: 35 seconds
Voltage: 2 * 0.1V (0S battery - NOT PRESENT)
CPU Clock=72MHz, GYRO=MPU6000, ACC=MPU6000
SD card: None inserted
Stack size: 2048, Stack address: 0x10002000
I2C Errors: 0, config size: 2043, max available config: 4096
CPU:16%, cycle time: 136, GYRO rate: 7352, RX rate: 90, System rate: 9
Arming disable flags: THROTTLE ANGLE CLI

#

So, is this something about my throttle settings?