What's new
By:
Aloft Forums

Welcome to Aloft Forums. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

Universal ACCST Firmware (UNI)

OK - Seems we are ready for the next level of testing. We are looking for a few folks that can put some hours of flight time in on this new firmware.

If you are interested in helping us test this new firmware, and are in a position where you have decent enough weather going into winter where you can still fly, we would love to hear from you. At this point the firmware has been very refined and tested, but we would like to accrue more hours of flight time before we release. While I do think this is a release candidate, care should be used, and I would not suggest putting it in a highly valued plane just yet.

If you are interested and would be able to fly during these cooler months, please reply here.

Thanks!
 
Where I live I can fly all year.

I would be able to test the firmware on G-Rx8 receivers running RXSR or XM+ as redundant, provided that I would be able to revert firmware to standard FRSKY if need be.

While this would be my preferred arrangement I have examples of all FRSKY ACCST receivers, any of which I could use for testing if that would help.
 
Wow! This is great! I always thought that Frsky should just fix the code in ACCST V1 before moving on and making things more complex w ACCST V2 and/or ACCESS. I continue to fly FCC version of ACCST V1 and have never had a problem thus far. If the Tx and rx were too close (less than two feet) I'd get the "telemetry lost" warning but not an issue really. Just move the tx a few inches away! Problem solved. Nice to know this will be corrected when working on the bench however. Nice!

So will this new firmware be available for the ACCST transmitters as well as the receivers?

Thanks,
Kirk
 
It isn't needed for the transmitter. The receiver automatically binds to the transmitter protocol (V1/V2, FCC/EU-LBT).
Features:
The V1 (USM) bug, while still present, is very significantly mitigated. The main problem of losing synchronisation is removed, many packets that would cause the USM are rejected and if a USM does occur, it will be corrected as soon as a valid packet is received (most likely within 18mS unless you have very severe interference).
Channel 8 may optionally be configured to output SBUS instead of a servo signal.
Channel 4 may optionally be configured to output SBUS instead of a servo signal.
The SBUS signal may optionally be inverted.
The firmware also supports "Dual Bind". Once you have bound one transmitter, you may bind to a second transmitter. When this bind takes place, the information for the first transmitter is saved.
If you now power the first transmitter on and enter bind mode (second Tx off), then when you power the Rx on (no need to press the bind button) it will bind back to the first transmitter, now keeping the second transmitter details ready to rebind to that one.
Only one transmitter is actually bound at any one time and so able to operate servos etc.
Normally the servo outputs are at an 18mS pulse rate. There is an option to enable a 9mS rate, then each channel may be selected to be either 9mS or 18mS.
The individual servo outputs may be mapped to the control channels, any output may be selected to be for any channel.

Mike
 
MikeB said:
The firmware also supports "Dual Bind". Once you have bound one transmitter, you may bind to a second transmitter. When this bind takes place, the information for the first transmitter is saved.
Click to expand...
Dual Bind (or whatever FrSky calls it) is the ONLY reason I was interested at ALL in ACCESS. This feature is awesome.
 
Great work Mike! After using your D8 to D16 firmware on D4R I can't wait to test/use the D16 firmware on X receivers.
 
Thanks for the feedback guys. I'll reach out to you in about 1 week, waiting to get some receivers in from FrSky. We will burn the new firmware onto them and get them out to you. Sound good?

The new firmware is not ready for the other receivers yet. We have been focused on the X8R and near twin X6R first, and once they are given the green light for release we can then get to work on firmware for the other ACCST receivers.

Many thanks!
 
I fly almost daily . I have been flying since 1982 .. I can fly these receivers for you as I only use Frsky ..I fly a Horus x10s express . I fly ERskytx that Mike ported to the Horus for us if that makes a difference . Mike is the GURU .. Anyway I can help if needed

Allen
 
I have been using Frsky for years all different types with no trouble, except stalling out and crashing. I use multi-module as well, I built my own originally. I switched to ver2 with no problems. I use opentx and ersky or what ever they call it these days, as well. I could test for you if you need any more testers. tedbmoss@cox.net
 
Wayne said:
There is not a day that we do not hear from customers that are having binding issues due to the V1 or V2 firmware binding issues. While it is simple for us to explain, the solution can be a bit ugly to incorporate for many users. There must be a better solution? Well, we got tired of waiting for something better.

A Universal ACCST Firmware!
I'd like to share a rather large project that we have been working on at Aloft along with some of the other Service Dealers in Europe and the UK. We have teamed up with an RC guru to develop new receiver firmwares for many of the FrSky ACCST receivers. The goal is a better user experience with the FrSky ACCST protocol products. ALL FrSky transmitters can use ACCST (also known as D16), from the very first Taranis to the current X20 and everything in between.

What can it do?
Receivers with this new firmware will be able to bind to the following:
  1. FCC Version of ACCST V1
  2. FCC Version of ACCST V2
  3. EU Version of ACCST V1
  4. EU Version of ACCST V2
Yep, you get all four of these in a single simple to use receiver. No more switching out firmwares and going insane. During the normal bind process, the receiver automatically switches until it finds the version your transmitter is running. How simple is that?

If you are using V1 in your transmitter the new Universal Firmware mitigates the V1 bug to the point it is of very little concern. Mike has also added some magic to reduce or remove the typical signal swamping that occurs when the transmitter is very close to the transmitter, you know the good old message: "Telemetry lost. Telemetry Found." warnings. Everything else works like you would expect it to. Servos run when you plug them in, Sbus is there, all the normal telemetry, and maybe a couple of tricks that you can turn on via a LUA script on your transmitter.

Is it Ready?
Not just yet, but getting very close to for our first receiver, the X8R. We have several BETA testers helping us to test this firmware around the globe, we want to be very careful and make sure we are checking and confirming everything we can think of.

Our plan is to have this firmware for all currently available ACCST receivers except for the S6R and S8R as they are far more complex.

What do you think, interested? Let us know your thoughts.
Click to expand...
Sounds great but what is it going to cost us customers? I have multiple FrSky receivers and could not afford to get new ones? Is there going to be a charge for the firmware?
 
Wayne said:
OK - Seems we are ready for the next level of testing. We are looking for a few folks that can put some hours of flight time in on this new firmware.

If you are interested in helping us test this new firmware, and are in a position where you have decent enough weather going into winter where you can still fly, we would love to hear from you. At this point the firmware has been very refined and tested, but we would like to accrue more hours of flight time before we release. While I do think this is a release candidate, care should be used, and I would not suggest putting it in a highly valued plane just yet.

If you are interested and would be able to fly during these cooler months, please reply here.

Thanks!
Click to expand...
If you still need someone for testing I can do it already have several X8R and X6R and all the FrSky programming software/hardware needed for them. I'm in Florida and it's just getting to comfortable flying weather now.
 
MikeB said:
What do you want f.port for? As I understand it, there are no sensors available from FrSky (yet), so it may only be used with flight controllers.

Mike
Click to expand...
sorry for not getting back sooner.

f.port for use with helicopters flying with Brain fbl. or to use with other flight controllers(betaflight/inav).
 

Distribution and Pricing.​

This is something we have discussed from the very start. Our goals are pretty simple, we want to offer you the best firmware possible and not hurt any of our manufacturers in the process.

Due to the threat of clone manufacturers we can not make this firmware available for download. We wish we could, but since FrSky does not own this firmware we have to be careful. (Cloners have already copied FrSky receivers and firmwares and sold them and been forced to stop via the legal system in China. In this case, we have made something that would be very attractive to clone manufacturers as it would get them around the FrSky ownership.)

We can is supply you with brand new receivers with the firmware installed.

You can send us your existing compatible receivers and we can burn the new firmware onto them for a small fee. We still need to calculate what the fee will be, but let's just say it will be as low as we can make it and still cover our expenses.

The firmware will be available from the 4 FrSky service dealers around the globe. Germany, UK and CZ are the other options. These are the other dealers that have helped us create and bring this firmware to life.

New ACCST receivers?​

Yes, as FrSky discontinues the ACCST receivers in favor of the new Archer receivers that run the ACCESS protocol the 4 service dealers have been bringing those discontinued units back to life under a special deal with FrSky. We know there are many thousands of older transmitters out there there that can not support the newer ACCESS protocol. We do not want to leave our existing customers hanging, or force them into buying new gear when their existing radios are fine.
 
You must log in or register to reply here.

Similar threads

R
FrSky Access and Accst Issues
Replies
2
Views
322
alm_nl
A
E
X10S ACCESS Upgrade module installation process question
Replies
5
Views
859
alm_nl
A
V
Best firmware and method to repurpose FRSKY TH9X with ACCST module and D4R-II rcvr for BOT???
Replies
2
Views
365
MikeB
MikeB
John in Boston
Firmware Upgrade(s) for (now-early) FrSky X-Lite transmitters?
Replies
4
Views
1K
alm_nl
A
B
Need Internal RF module firmware file for X12S
Replies
3
Views
2K
Bill Sanford
B
Back
Top