Does anyone know if you can use the AS3X Receiver USB Interface to update a Frsky rx in place of the Frsky STK tool? I have one lying around and I'm just curious if it'd work. I understand dsmx is a different protocol, but is the process of sending information the same? The devices look very similar and I know people have used USB to TTL adapters to update Frsky rx's. Thanks in advance!

(20-Apr-2024, 01:19 PM)baevans11 Wrote: Does anyone know if you can use the AS3X Receiver USB Interface to update a Frsky rx in place of the Frsky STK tool? I have one lying around and I'm just curious if it'd work. I understand dsmx is a different protocol, but is the process of sending information the same? The devices look very similar and I know people have used USB to TTL adapters to update Frsky rx's. Thanks in advance!

How does it connect to the FrSky Receiver? Which FrSky receiver? Don't you connect to the FrSky receiver using the Smart Port? There is no Smart Port on the Spektrum receiver.

Yes, the STK tool is a USB dongle but it also connect to the FrSky receiver via Smart Port. 

frsky-s-port-tool-kit-stk.html

The Spektrum USB interface is also another USB dongle but it has a different plug on the receiver end and I am sure the circuitry is very different.

https://www.horizonhobby.com/product/usb...lQQAvD_BwE

OTOH you don't need a STK Tool to update firmware on your FrSky receiver. You can copy the firmware to the micro SD card and plug that onto the FrSky transmitter. Then take a servo connector with female plug on both ends. You need to swap the red and black wire. You better google that or watch a YouTube video so you don't fry anything. Mark the swapped end as transmitter end. Then plug that into the lower 3 pins on your transmitter external module bay and plug the non-swapped end to the smart port on your receiver. Then you can update the firmware to the receiver using the transmitter.

(20-Apr-2024, 06:42 PM)SeismicCWave Wrote: How does it connect to the FrSky Receiver? Which FrSky receiver? Don't you connect to the FrSky receiver using the Smart Port? There is no Smart Port on the Spektrum receiver.

Yes, the STK tool is a USB dongle but it also connect to the FrSky receiver via Smart Port. 

frsky-s-port-tool-kit-stk.html

The Spektrum USB interface is also another USB dongle but it has a different plug on the receiver end and I am sure the circuitry is very different.

https://www.horizonhobby.com/product/usb...lQQAvD_BwE

OTOH you don't need a STK Tool to update firmware on your FrSky receiver. You can copy the firmware to the micro SD card and plug that onto the FrSky transmitter. Then take a servo connector with female plug on both ends. You need to swap the red and black wire. You better google that or watch a YouTube video so you don't fry anything. Mark the swapped end as transmitter end. Then plug that into the lower 3 pins on your transmitter external module bay and plug the non-swapped end to the smart port on your receiver. Then you can update the firmware to the receiver using the transmitter.

Thanks for the reply! Yeah that's how I've been programming my RX's. I just came across the two USB adapters from Spektrum & Castle and I was just wondering if they would work in place of the Frsky STK tool. I'll attach pics & links.

Spektrum TX/RX USB Programming Cable, Laptop https://a.co/d/6Pb8KUm

Castle Link V3 USB Programming Kit https://a.co/d/cPlvs3n

(21-Apr-2024, 03:17 PM)baevans11 Wrote: Thanks for the reply! Yeah that's how I've been programming my RX's. I just came across the two USB adapters from Spektrum & Castle and I was just wondering if they would work in place of the Frsky STK tool. I'll attach pics & links.

Spektrum TX/RX USB Programming Cable, Laptop https://a.co/d/6Pb8KUm

Castle Link V3 USB Programming Kit https://a.co/d/cPlvs3n

I have more trouble messing with connecting various RC related hardware to the computer using the USB port. They really annoyed me and 9 times out of 10 they don't work. It has to be the correct cable (lots of USB cables are charge only and not compatible with data), Windows driver, protocols, this and that.

When I can connect a device to a computer and get them working I wept with joy. 

So my motto has always been use what is recommended unless I want to keep banging my head against the wall. 

So my question is how badly do you want to bang your head against the wall.

I know for sure the Castle Creation dongle will NOT work. They only work with their speed controller. I am very doubtful for a Spektrum dongle to work with FrSky. For that matter I even have issues with two of my STK Tool to work with my FrSky devices. 

So, once you found a reliable way to update firmware, keep using that same method over and over. Unless you want to try and bang your head against the wall. It depends on how hard your head is.......

(21-Apr-2024, 08:22 PM)SeismicCWave Wrote: I have more trouble messing with connecting various RC related hardware to the computer using the USB port. They really annoyed me and 9 times out of 10 they don't work. It has to be the correct cable (lots of USB cables are charge only and not compatible with data), Windows driver, protocols, this and that.

When I can connect a device to a computer and get them working I wept with joy. 

So my motto has always been use what is recommended unless I want to keep banging my head against the wall. 

So my question is how badly do you want to bang your head against the wall.

I know for sure the Castle Creation dongle will NOT work. They only work with their speed controller. I am very doubtful for a Spektrum dongle to work with FrSky. For that matter I even have issues with two of my STK Tool to work with my FrSky devices. 

So, once you found a reliable way to update firmware, keep using that same method over and over. Unless you want to try and bang your head against the wall. It depends on how hard your head is.......

Ok thanks for all your help! I kinda figured that, but figured I'd ask around. Thanks again!

I updated the xm+ to XM+_ACCST_2.1.2_FCC.frk and I'm running OpenTX 2.3.15-otx (1004ef7c) but I just can't get it to bind to the Betafpv F4 1S 5A AIO Brushless Flight Controller on my Meteor 75 Pro to save my life! Odk if I'm flashing the wrong file to the rx, cause there's 3 FCC versions, the one I wrote above, a D16, and a D8. I assume flashing the file I did writes both the 16 & 8 to the rx correct? I even tried just flashing the D16. I have the XJT on my Taranis x9d+ set in mode, channel range is 1-16, then when I hit bind I choose Telem 1-8 on (but I've tried the other on/off options too). I am holding down the bind button on XM+ while I plug in lipo (this is after I flashed and hooked it back up of course). I keep the TX 1 meter or so away. I get a solid red & green light on rx, but no flashes. Then I unplug and turn both off and restart, but then I just get a red flashing light on xm+ I have UART1 set to serial RX & FrSky and I also have Serial/UART & SBUS set in the receiver tab in Betaflight, but I never get any of the bars to even light up in the rx tab. I'm wondering if there is something I need to change via CLI? Or will it not work because my TX is 2.3 and rx is 2.1? I thought they would only both need to be 2.x.x This problem is killing me cause there has to be a way. Now it's mostly cause I don't want to admit defeat lol. I'm admittedly a bit rusty on my fpv knowledge because I took a few years off and have only gotten back in it for a couple of months. Could the fact that I jumped quite a few years in the upgrading of my Taranis x9d plus be an issue? It was running firmware from at least 3+ years then I updated to latest version.

(22-Apr-2024, 05:58 PM)baevans11 Wrote: Ok thanks for all your help! I kinda figured that, but figured I'd ask around. Thanks again!

I updated the xm+ to  XM+_ACCST_2.1.2_FCC.frk and I'm running OpenTX 2.3.15-otx (1004ef7c) but I just can't get it to bind to the Betafpv F4 1S 5A AIO Brushless Flight Controller on my Meteor 75 Pro to save my life! Odk if I'm flashing the wrong file to the rx, cause there's 3 FCC versions, the one I wrote above, a D16, and a D8. I assume flashing the file I did writes both the 16 & 8 to the rx correct? I even tried just flashing the D16. I have the XJT on my Taranis x9d+ set in mode, channel range is 1-16, then when I hit bind I choose Telem 1-8 on (but I've tried the other on/off options too). I am holding down the bind button on XM+ while I plug in lipo (this is after I flashed and hooked it back up of course). I keep the TX 1 meter or so away. I get a solid red & green light on rx, but no flashes. Then I unplug and turn both off and restart, but then I just get a red flashing light on xm+ I have UART1 set to serial RX & FrSky and I also have Serial/UART & SBUS set in the receiver tab in Betaflight,  but I never get any of the bars to even light up in the rx tab. I'm wondering if there is something I need to change via CLI? Or will it not work because my TX is 2.3 and rx is 2.1? I thought they would only both need to be 2.x.x This problem is killing me cause there has to be a way. Now it's mostly cause I don't want to admit defeat lol. I'm admittedly a bit rusty on my fpv knowledge because I took a few years off and have only gotten back in it for a couple of months. Could the fact that I jumped quite a few years in the upgrading of my Taranis x9d plus be an issue? It was running firmware from at least 3+ years then I updated to latest version.

To really trouble shoot you need to get back to basic. First of all you need to get the XM+ working with your Transmitter. What I would do in your case is to unsolder the XM+ from the flight controller. Connect a separate 5V power source to the XM+ and bind. Once you are sure the XM+ is bound to the transmitter you then can move forward. BetaFlight does not do anything to help you bind the XM+ unless it is a SPI baked in receiver on the flight controller.

No D8 and D16 is not that same thing. FrSky had many receivers over the years and they used different protocols. First there were the V series receiver. Then they had the D series receivers. That's the D8 firmware you are talking about. Then they went to the X series receivers which had the issues. These all run on what FrSky called ACCST. After that they went with something called ACCeSS which is not compatible. The XM+ receiver is an X series receiver and they run on the ACCST protocol. The original version was ACCST V1 which had issues. So they up dated with ACCST V2. Since you flashed ACCST 2.1.2 you should have the ACCST V2.

Now the question is that you flashed the XM+ to ACCST V2, have you flashed your XJT module on your transmitter to ACCST V2 also/ ACCST V1 and V2 are no compatible.

You need to flash ACCST V2 on your transmitter XJT module for the XM+ to bind.

Once you did that you can use D16 Telemetry or no telemetry channels 1 through 8.

https://www.frsky-rc.com/important-firmw...accst-d16/

If you have issues with the ACCST V2 firmware you may need to downgrade your XM+ to the ACCST firmware to V1.X and to make sure the XJT module is running version V1.

Yes I am sorry but this is all very confusing but I am only the messenger and I have nothing to do with FrSky. I personally used FrSky for 12 years and now I am almost exclusively using ExpressLRS.

Once you solved the XM+ binding to the transmitter issue then you can solder the XM+ back to the flight controller. Then you can use BetaFlight and set the UART port and sBus etc. 

This really has nothing to do with FPV and your skill with FPV. It is just a confusing part (Protocol) from using the FrSky radio. Unfortunately FrSky is not the only radio with all the confusion either.

The other confusing issue is that the XM+ receiver is small but only has sBus output and you cannot even see if the output is working or not unless you have a device to read sBus (which I do because I want to see if they are working). Another way to tell besides from the LED lights is to see if the telemetry is working on the transmitter screen. If you use D16 channels 1 to 8 with telemetry your transmitter should have a little icon that shows the strength of your RSSI signal.

(22-Apr-2024, 05:58 PM)baevans11 Wrote: Ok thanks for all your help! I kinda figured that, but figured I'd ask around. Thanks again!

I updated the xm+ to  XM+_ACCST_2.1.2_FCC.frk and I'm running OpenTX 2.3.15-otx (1004ef7c) but I just can't get it to bind to the Betafpv F4 1S 5A AIO Brushless Flight Controller on my Meteor 75 Pro to save my life! Odk if I'm flashing the wrong file to the rx, cause there's 3 FCC versions, the one I wrote above, a D16, and a D8. I assume flashing the file I did writes both the 16 & 8 to the rx correct? I even tried just flashing the D16. I have the XJT on my Taranis x9d+ set in mode, channel range is 1-16, then when I hit bind I choose Telem 1-8 on (but I've tried the other on/off options too). I am holding down the bind button on XM+ while I plug in lipo (this is after I flashed and hooked it back up of course). I keep the TX 1 meter or so away. I get a solid red & green light on rx, but no flashes. Then I unplug and turn both off and restart, but then I just get a red flashing light on xm+ I have UART1 set to serial RX & FrSky and I also have Serial/UART & SBUS set in the receiver tab in Betaflight,  but I never get any of the bars to even light up in the rx tab. I'm wondering if there is something I need to change via CLI? Or will it not work because my TX is 2.3 and rx is 2.1? I thought they would only both need to be 2.x.x This problem is killing me cause there has to be a way. Now it's mostly cause I don't want to admit defeat lol. I'm admittedly a bit rusty on my fpv knowledge because I took a few years off and have only gotten back in it for a couple of months. Could the fact that I jumped quite a few years in the upgrading of my Taranis x9d plus be an issue? It was running firmware from at least 3+ years then I updated to latest version.

The FrSky ACCST V2.x.x firmware doesn't offer a D8 variant of the ACCST protocol. It only utilises the D16 variant. The firmware file options are no RSSI, RSSI on Channel 8 (Auxiliary channel 4), or RSSI on Channel 16 (Auxiliary channel 12). If you flash the XM+_ACCST_2.1.2_FCC.frk firmware file the XM+ won't send an RSSI value to the FC on any of the channels which means you won't be able to display the RSSI value in the OSD of your goggles. If you flash the XM+_ACCST_2.1.2_FCC_RSSI8.frk firmware file, the XM+ will send an RSSI value to the FC on Channel 8, and if you flash the XM+_ACCST_2.1.2_FCC_RSSI16.frk firmware file, the XM+ will send an RSSI value to the FC on Channel 16. So the latter two allow you to display the RSSI value in the OSD of your goggles.

There are no compatibility issues using OpenTX 2.3.15 with the FrSky receivers. I have an old XM+ in my spares box and it was binding perfectly fine to my X9D+ when it was running that same version of OpenTX, although admittedly that was on ACCST 1.x.x. I never moved any of my FrSky gear to ACCST 2.x.x.

Do as SeismicCWave suggested by getting the XM+ to bind to your Taranis X9D+ without it even being connected to an FC.

@SeismicCWave - This issue is a continuation of another thread HERE. The OP is supposedly already has ACCST 2.x.x installed on the internal XJT module of his/her X9D+ and doesn't want to flash back to ACCST 1.x.x because other working quads are already on ACCST 2.x.x. Personally I would have stayed well away from ACCST 2.x.x after all of the drama that FrSky caused when they released it. Until I moved over to using TBS Crossfire and ExpressLRS, I remained on ACCST 1.x.x with my FrSky receivers and they worked perfectly fine other than crappy range of the ACCST protocol in general. FrSky only originally released ACCST 2.x.x to try and prevent third parties manufacturing (clone) receivers that ran on FrSky firmware. There is a whole discussion thread about that at the link below...

https://intofpv.com/t-beware-frsky-accst...x-firmware

(22-Apr-2024, 10:05 PM)SnowLeopardFPV Wrote: The FrSky ACCST V2.x.x firmware doesn't offer a D8 variant of the ACCST protocol. It only utilises the D16 variant. The firmware file options are no RSSI, RSSI on Channel 8 (Auxiliary channel 4), or RSSI on Channel 16 (Auxiliary channel 12). If you flash the XM+_ACCST_2.1.2_FCC.frk firmware file the XM+ won't send an RSSI value to the FC on any of the channels which means you won't be able to display the RSSI value in the OSD of your goggles. If you flash the XM+_ACCST_2.1.2_FCC_RSSI8.frk firmware file, the XM+ will send an RSSI value to the FC on Channel 8, and if you flash the XM+_ACCST_2.1.2_FCC_RSSI16.frk firmware file, the XM+ will send an RSSI value to the FC on Channel 16. So the latter two allow you to display the RSSI value in the OSD of your goggles.

There are no compatibility issues using OpenTX 2.3.15 with the FrSky receivers. I have an old XM+ in my spares box and it was binding perfectly fine to my X9D+ when it was running that same version of OpenTX, although admittedly that was on ACCST 1.x.x. I never moved any of my FrSky gear to ACCST 2.x.x.

Do as SeismicCWave suggested by getting the XM+ to bind to your Taranis X9D+ without it even being connected to an FC.

@SeismicCWave - This issue is a continuation of another thread HERE. The OP is supposedly already has ACCST 2.x.x installed on the internal XJT module of his/her X9D+ and doesn't want to flash back to ACCST 1.x.x because other working quads are already on ACCST 2.x.x. Personally I would have stayed well away from ACCST 2.x.x after all of the drama that FrSky caused when they released it. Until I moved over to using TBS Crossfire and ExpressLRS, I remained on ACCST 1.x.x with my FrSky receivers and they worked perfectly fine other than crappy range of the ACCST protocol in general. FrSky only originally released ACCST 2.x.x to try and prevent third parties manufacturing (clone) receivers that ran on FrSky firmware. There mis a whole discussion thread about that at the link below...

https://intofpv.com/t-beware-frsky-accst...x-firmware

Thanks Snow. I try to stay current but sometimes cannot keep up with all the posts. I used FrSky for many years. Starting with their PPM on the V series receiver because that helped me in reducing the number of cables connecting between the Rx and the Fx. I started having issues when I went to the X series receivers. I was losing more flying vehicles than ever. I was losing quads but I never attributed that to the ACCST V1 uncommand down elevator issue. Then I started back flying fixed wings with PWM output and the uncommanded down elevator issues were very apparently. I have since updated every FrSky to ACCST V2 or the UNI firmware but I hardly fly them since. I started to get RSSI warnings when I flew too far. ExpressLRS solved all those trouble so I started to migrate. 

I always thought FrSky released ACCST V2.X because there were just too many people having the uncommanded down elevator issues. I never saw that the FrSky ACCST V2.X not being compatible with certain equipment. For that matter I have all those equipment they mentioned in the webpage but I hardly use them now.

So yes I am a bit out of touch with FrSky equipment nowadays.

(22-Apr-2024, 06:56 PM)SeismicCWave Wrote: To really trouble shoot you need to get back to basic. First of all you need to get the XM+ working with your Transmitter. What I would do in your case is to unsolder the XM+ from the flight controller. Connect a separate 5V power source to the XM+ and bind. Once you are sure the XM+ is bound to the transmitter you then can move forward. BetaFlight does not do anything to help you bind the XM+ unless it is a SPI baked in receiver on the flight controller.

No D8 and D16 is not that same thing. FrSky had many receivers over the years and they used different protocols. First there were the V series receiver. Then they had the D series receivers. That's the D8 firmware you are talking about. Then they went to the X series receivers which had the issues. These all run on what FrSky called ACCST. After that they went with something called ACCeSS which is not compatible. The XM+ receiver is an X series receiver and they run on the ACCST protocol. The original version was ACCST V1 which had issues. So they up dated with ACCST V2. Since you flashed ACCST 2.1.2 you should have the ACCST V2.

Now the question is that you flashed the XM+ to ACCST V2, have you flashed your XJT module on your transmitter to ACCST V2 also/ ACCST V1 and V2 are no compatible.

You need to flash ACCST V2 on your transmitter XJT module for the XM+ to bind.

Once you did that you can use D16 Telemetry or no telemetry channels 1 through 8.

https://www.frsky-rc.com/important-firmw...accst-d16/

If you have issues with the ACCST V2 firmware you may need to downgrade your XM+ to the ACCST firmware to V1.X and to make sure the XJT module is running version V1.

Yes I am sorry but this is all very confusing but I am only the messenger and I have nothing to do with FrSky. I personally used FrSky for 12 years and now I am almost exclusively using ExpressLRS.

Once you solved the XM+ binding to the transmitter issue then you can solder the XM+ back to the flight controller. Then you can use BetaFlight and set the UART port and sBus etc. 

This really has nothing to do with FPV and your skill with FPV. It is just a confusing part (Protocol) from using the FrSky radio. Unfortunately FrSky is not the only radio with all the confusion either.

The other confusing issue is that the XM+ receiver is small but only has sBus output and you cannot even see if the output is working or not unless you have a device to read sBus (which I do because I want to see if they are working). Another way to tell besides from the LED lights is to see if the telemetry is working on the transmitter screen. If you use D16 channels 1 to 8 with telemetry your transmitter should have a little icon that shows the strength of your RSSI signal.

Thanks so much for this! It's truly helpful.??? I will follow this advice and update this post asap. I'm definitely thinking of migrating over to ExpressLRS. It really seems like an inevitably at this point. I've been trying to study up on it so I know most of the ins and outs of what I need to do and best equipment to buy. FPV has never been easy on the amirite! ??