search

mikeller / opentx

OpenTX custom firmware for Transmitters
10 stars 0 forks source link

RX Loss. #5

Open Sm1thson opened 5 years ago

Sm1thson commented 5 years ago

I flashed this firmware on a QX7 in September, One of my quads was fine (DYS F4 AIO, R9M receiver BF3.5.1 (and subsequently 3.5.2)),

The other quad (Matek F405, R-XSR, BF3.5.1) repeatedly got RXLOSS when I armed and the control link noticeably went on off on off on off (causing 'robotic' flying)), I'd done other bits to the quad so I just assumed user error and put it to the side to look at later (not thinking it might be the QX7 firmware). When I went to fix it amongst other things I put an R9M on it and updated it to BF3.5.2, the RX loss problem went away and I thought nothing more of it.

I just fixed (broken motor) my micro (still on BF 3.2.2, on a (none genuine) Omnibus F3 target, XM+ RX) for winter , went to arm and just get RX loss.

I looked back at my notes and realised the previous RX Loss issue coincided with flashing this fork of open TX

I flashed the none forked open TX 2.2.2 and no RX loss problems on the micro.

Not sure what combination of gear is causing this but figured this should be reported.

mikeller commented 5 years ago

@Sm1thson: That's interesting. I assume you got the RXLOSS when using the QX7's internal TX module? Do you know what firmware version the TX module is running? Have you tried updating the TX module firmware to the latest version?

Sm1thson commented 5 years ago

I'll try the TX module firmware, good shout its at least 1.5 year old firmware in there. I'm busy until next week but will report back once I've done it.

Sm1thson commented 5 years ago

Sorry for the mega delay, had a little FPV break as life got in the way.

Ive flashed the internal XJT module with FW version 170317, and the X7 with your latest 2.2.2 still no joy and getting RXloss to the point my micro usually doesnt arm.

Its a mystery, but TBH now I only have my micro on 2.4GHz and for everything else Im on R9M so am going to run a nightly of 2.2.3 (in EU so really need flex as their none flex EU firmwares are not up to scratch).

So I'm happy to leave it as an unsolved mystery as no one else has said they have the issue.