Recent content by robhafey

I got my answer from TBS. There were 2 related problems. I had previously defined channel 8 to be LQ. So my mix on channel 8 wasn't getting sent. To make it work I needed to put the receiver in 12 channel mode. I then moved my channel 8 mix to channel 9 and BOOM it worked.

Having a strange issue with my Tango 2 setup. I mapped the mixes for arm, acro/angle/horizon, and buzzer just fine. I also added a mix for gps rescue. The issue is that I can't get betaflight to recognize more than AUX 1,2,3. When I select auto my 4th switch does nothing. I can swap the...

Yeah, I also used Oscar's LQ tutorial. I realized when I got to the field that I had forgotten to do the dst channel setup for the new receiver. So my LQ value was stuck at 49. At first it freaked me out but once I realized the numbers weren't changing I knew it wasn't connected. I am going...

I got the replacement receiver through TBS. The first problem I had was that the frequency was wrong. That fixed some of the problems but I still had receiver warnings. This new Nano seems a lot better although my LQ display wasn't working for this flight. Will be able to see some numbers...

Sorta boring flight but was able to test my replacement Nano receiver. This one had no receiver warnings when DJI goggles had 1 bar of reception. Last receiver was obviously faulty. Next I need to beef up DJI range with AXII HD antennas.

My unused, never bound FrSky X-Lite. Comes with charger and 4 batteries. https://www.ebay.com/itm/224193404936

Yeah, it wasn't trivial. Because I wasn't getting stick input I thought I had mucked something up with the wiring. Check that 10 times, it was ok. And then I updated the firmware on the Tango 2 and the receiver wouldn't bind. I did the update again, downgraded to 4.0.0 and then things bound...

Crossfire now working. I ended up sticking with the stock wiring which worked once I went through a bit of hell getting my Tango 2 updated. Looking forward to less range anxiety!

No answer from iFlight so I just figured it out myself by reading more about the DJI air unit. Having both won't work because R1 is SBUS which has to be dedicated. I was thinking that the TX/RX was used for comm with the controller but no, that is for the googles/OSD. So I am going ahead with...

Finland :) I wonder where the initial GPS coordinates are stored? I am guessing Betaflight does that? Maybe problem with internal RAM? Or maybe it is on the GPS? I'll have to read up on that.

I don't know much about the GPS but maybe it isn't getting a reference starting position?

I agree it might not be worth it but I want to at least see if it is possible. It really boils down to having something working and then mucking it up to try something different. I sent the question to iFlight to see what they say. If it is a no go then I'll just follow their wiring diagram...

I just got my Crossfire Nano receiver and was curious if I could leave the DJI receiver connection and then add the crossfire receiver on another UART? I would like to be able to switch between them in Betaflight. Here is the wiring diagram. They say to disconnect R1 and GND and then...

That makes sense and certainly easier to just remove the pins. I am curious however if I can leave RX & Ground connected and use a different UART so I can swap back and forth between transmitters in Betaflight.

Next big question. I just pulled all the Crossfire stuff out of the box and am looking at doing the connection. I was hoping to leave the DJI unit wiring alone , connect the CF on another UART, and then disable the DJI transmitter UART. But from the description below it looks like they want...