EdgeTX
QX7 (XJT) - FrSky D8 loss of connection
Is there an existing issue for this problem?
- [X] I have searched the existing issues
What part of EdgeTX is the focus of this bug?
Transmitter firmware
Current Behavior
I have an FrSky QX7 and a number of old whoops with SPI FrSky D8 receivers. Some time ago I updated the QX7 to the latest OpenTx and then found that on power up, they usually (not always) did not connect. The details are below, but I have just changed to latest EdgeTx (2.8.4) to see if the issue was solved there, but it is exactly the same.
With the radio powered, power the quad, and it doesn't connect - probably 8 times out of 10. On the other 2 times, it does. This only happens with the internal XJT module in use, and set to D8. Other quads on FrSky D16 using the internal module have no issue, and if I use an iRangeX 4in1 JR bay module instead, the quads connect every time. I do not think therefore it is a faulty XJT module as it works fine for D16. Its firmware has not being changed - the problem occurred after a change to the main Tx firmware.
The way out of it is quite simple - go into the main setup menu, press bind, wait a few seconds, press bind again (to stop it), and it connects fine. Once connected it stays connected, and note also there is no need to put the receiver into bind mode.
The quad can be powered down and up again, and it will reconnect fine, but if the QX7 model is changed, or if the transmitter is powered off and on again, the problem reoccurs.
I am pretty sure it coincided with the firmware update, never a problem before that.
I hoped it would be solved with a change to EdgeTx, but it isn't.
NOTE EdgeTx version is actually 2.8.4 not 2.8.2, but selector below does not include it.
Expected Behavior
Power on radio, power up quad, and it should connect every time - assuming the quad has already been correctly bound.
Steps To Reproduce
Power on radio, power up quad, and providing the protocol is D8 on the internal XJT module it probably will not connect. Briefly turn bind on and off again, and it will then connect. If the radio os powered off, or the model is changed, the problem will reoccur. If only the quad is powered off and on, it won't.
Version
2.8.4
Transmitter
FrSky Q X7 / Q X7S (ACCST)
Operating System (OS)
Windows
OS Version
No response
Anything else?
No response
OK, will test this within the next 2 days (currently away).
On 5 Sept 2023, 12:07, at 12:07, Raphael Coeffic @.***> wrote:
@nmw01223 could you please re-test with the latest
2.9.0release?-- Reply to this email directly or view it on GitHub: https://github.com/EdgeTX/edgetx/issues/3613#issuecomment-1706411229 You are receiving this because you were mentioned.
Message ID: @.***>
Hey I am having the same problem, was this ever solved?
FrSky Qx7 (ACCST) Mobula6 (the original with FrSky SPI) on D8
Upgraded from OpenTX to EdgeTX 2.11.0 (the final version compatible with the Qx7) Whenever I power on the TX it forgets the bind and have to rebind as @nmw01223 described above.
I also upgraded my mobula6 to Betaflight to 4.3.2 which I believe to be about the last BF version to support my CRAZYBEEF4FR AIO and FrSky SPI.
As I understand it, where an AIO uses FrSky SPI the FrSky firmware has to be integrated into the BF firmware. I have also read that the FrSky firmware on TX and FC/RX need to match. Does this mean that we would potentially need to flash the Qx7 internal module firmware to match what is on the FC/ SPI RX?
And does that mean that if we downgrade the BF firmware to 4.2.x then we will potentially have the correct FrSky firmware integrated and it will all work correctly?
If this checks out we might be able to work out what FrSky firmware version is integrated into BF 4.3.2 (or whatever version you are using) then we could flash the corresponding firmware onto the Qx7 internal module?
Another complication is that all the FrSky internal module firmware versions are confusing as they do not have a specific Qx7 ACCST firmware download page as they do for the Qx7 ACCESS... There is an XJT firmware download page which people on forums seem to reference as the correct firmware for the Qx7 ACCST, can anyone confirm this?
If anyone can clear any of this up it would be much appreciated!
It works!
For any future readers using a Qx7 and Mobula6 running Betaflight 4.3.2 Updating the internal module of the Qx7 to the v2.1 firmware (XJT_ACCST_2.1.0_FCC.frk) made it remember binds with FrSky SPI, AIO FC boards running Betaflight 4.3.2
From memory BF 4.2 works with pre v2.x FrSky firmware such as v1.7 (e.g. XJT_NONEU_170317.frk) But I wasn't able to pinpoint which version of BF implemented the switch and this may vary between board manufacturers. I did read somewhere that in BF configurator in the receiver tab you can choose whether you are using FrSky_X_v1 or FrSky_X_v2 but as I am using FrSky_D8 for 8 channels instead of FrSky_X which gives 16 channels to keep latency down.