What's new
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)

On the Rx6R running ACCESS, what do you have for the Rx hardware version?
Also you report you can't flash that Rx with UNI, what problem do you get when trying to flash?

Mike
 
The error on the RX6R when flashing is (the same error I get on one of the G-XR6 receivers):
Firmware update error
Device not responding
I don't know the specific firmware on the RX6R, however, it works with the Taranis running ISRM 2.1.10. Since I can't flash it, I can't be sure what is on it. However, I'm assuming it was probably the last revision of the firmware.

Matt
 
1. Receivers running ACCESS report hardware and software versions to the Tx. It should be in the receiver menu of the module menu.

2. For registering when using V86, give the Rx some time and try with the Tx at different distances. UNI does a tuning operation first when registering, and also looks for ACCESS registering and the 4 possible ACCST binding protocols.
If you power on the Rx with the button pressed (Tx off) the LEDs should show red on solid with a brief green flash for a time (looking for register operation), then green off and red blinking off (looking for ACCST binding), then repeat. If the Tx is then turned on and put into register mode then the Rx should show the red on solid with the green led also lighting up, and should stop with both LEDs on when the Tx reports the Rx name to be registered.

3. I assume you are trying to flash using the SPort connection. Do you know if the SPort is working when using the Rx normally (i.e. are the hardware connections OK)?

4. I just put ISRM 2.1.10 on a X9Lite and it registers and binds to my G-RX6 running UNI V86.

5. What firmware are you using on the Tx? I use erskyTx (since I write and maintain it!) although I have openTx on my X9Lite for testing.

Mike
 
Last edited:
1. The RX6R is running 2.1.7
2. Success! The V86 on the G-XR6 worked with the Taranis on both ACCESS and ACCST! You're explanation of the lights worked.

Would you recommend the V86 on the RX6R as well?

Do you have any suggestions for the 2 receivers that don't want to flash?

Thanks, Mike!

Matt
 
You only need V86 if you are likely to want ACCESS.

Check item 3 in my previous post. When operating normally does an external, SPort sensor work? Or are you trying to flash OTA?

Mike
 
The RX6R receiver that won't flash, when bound to the Taranis using ACCESS, delivers telemetry. I do not have a separate sensor to attach to the S-port. Would using a XM+ receiver plugged in to the s-part as a secondary receiver be satisfactory?
 
No, you do need an external sensor to check the SPort is working.
Since you have updated some receivers OK I assume you have the STK connected correctly (DIP switch towards port 2 and the Rx connected to port 2).

When using the STK to update firmware, I would recommend connecting only ground and signal from the STK to the Rx and provide a separate (switchable) power supply to the Rx.
Keep the Rx powered off until you get to the "finding device" stage, then power it on.

Mike
 
Last edited:
Hi

For my gliders, I am using small receivers with 4 or 6 channels like X4R/X6R/RX4R/RX6R, sometime using the S-PORT to get an extra channel.

Since they are now discontinued (sometimes there are some as second hand), the only alternative seems to be the Archer R6. But it's only 6 channels.

Since UNI fw is now providing ACCESS protocol, I was wondering if it would be feasable to get UNI on Archer RX HW, thus having this extra channel on S-PORT feature ?

Thanks
 
The extra channel is on the SBUS signal not SPort.
Even the standard ARCHER receivers are discontinued, so while it should be possible to put UNI on them (I only have one Archer RX) it doesn't seem that usefult to do so.

Unfortunately, FrSky have changed their encryption method for the Archer Plus receivers and I don't know what it is, so I'm unable to create a file to flash these.

Mike
 
Hi
It looks like the UNI firmware could help me but I would need your feedback, I read a lot but not sure of my conclusions.

I am using X6R/X8R/X8R Pro and would like to add extra servos above the PWM physical outputs, respectively 6 and 8 channels, by using the SBUS port.

If I need ony one extra servo, the UNI firware allows to use the SBUS port as an extra PWM output, which is awesome.

Now if I need 2 extra servos, I do need to use an SBUS to PWM converter. Lets use X8R as an example.

First option is to use the Frsky SBUS to PWM convertor. While the FrSky SCC (Servo Channel Changer) is discontinued, I saw an Windows app using the Frsky STK to set the channel ID per PWM output, thus having the 4 extra PWM output on CH 9 to 12 (https://www.rcgroups.com/forums/showthread.php?4776841-SBUS-Channel-Changing-(FrSky)&perpage=20). Am I correct ?

Second option, take a 4 CH SBUS-PWM converter from AliExpress but it looks like they are "hard coded" to read the SBUS id 1 to 4 only. So the issue might be that the converter will take the id 1 to 4 on the SBUS, thus duplicating the physical PWM port 1 to 4 of the receiver, and therefore not adding 4 extras PWM output.
(on some 8 CH converter, you can choose 1-8 or 9-16 by solder a shunt, but theses converters are much bigger and also more expensive for just 2 extra channels).

Can UNI Firmware remap the physical PWM output of the receiver to channels 5 to 12 ? (PWM1 - CH5, PWM1 -CH6 etc) so that CH1 to 4 will go to SBUS and the converter and CH5 to 12 to PWM1 to 8 physical output of the receiver ?

Thanks for your advise.
So I finally got time and successfully use the SBUS to connect one additional servo on my X8R in may.
Bind is 1-16, Servo on SBUS is ON, TX sending output on Channel 9. Servo Map and S.BUS map are OFF. My servo on SBUS port move as expected.

I then tried the same setup on an RX6R mapped from 1-16 channels, activate Servo on SBUS to be used as channel 9 but the servo does not move. TX is sending signal on channel 9. No idea what's wrong.
The Servo output parameter is displaying 1-8 and 9-16: I would expect to have 1-6 and 7-16, no ?

I have one question : by default, will the SBUS port take the next physical channel of the receiver ? ie on RX6R, the SBUS port will take the 7th channel by default ? (on my X8R, it was obviously the channel 9.
And to have SBUS to output PWM, you just have to activate Servo on SBUS on Page 1 of the setup script ?

Thanks and sorry if this has been already been answered.
 
Last edited:
The firmware file is common to the Rx4R, RX6R, GRX6 and GRX8. The GRX8 is odd in that the channel 8 output is a shared pin with the SBUS output, so selecting the SBUS output to be a servo output on any of these receivers results with channel 8 in the SBUS signal, not 9 or 7!

Mike
 
The firmware file is common to the Rx4R, RX6R, GRX6 and GRX8. The GRX8 is odd in that the channel 8 output is a shared pin with the SBUS output, so selecting the SBUS output to be a servo output on any of these receivers results with channel 8 in the SBUS signal, not 9 or 7!

Mike
Ok.
So you confirm on alll receivers with 8 physical ports except GRX8, the extra servo on SBUS port is using channel 9 and channel 7 for receivers with 6 physical ports ?

How can I troubleshoot my RX6R ?

Thanks
 
When the SBUS out is used as a servo channel:
S6R - Ch 7 (9 and 10 control the stabilisation)
S8R - Ch 11 (9 and 10 control the stabilisation)
RX4R, RX6R, G-RX6, G-RX8 - Ch 8
All others - Ch 9

So your RX6R will use channel 8 on the SBUS signal.

Mike
 
The ACCESS version for the RXxR and G-RXx receivers is now at V87, the servo outputs were being sent twice when in ACCST mode.

Mike
 
When the SBUS out is used as a servo channel:
S6R - Ch 7 (9 and 10 control the stabilisation)
S8R - Ch 11 (9 and 10 control the stabilisation)
RX4R, RX6R, G-RX6, G-RX8 - Ch 8
All others - Ch 9

So your RX6R will use channel 8 on the SBUS signal.

Mike
Thanks, much clear.

For my RX6R servo on channel 8 works well : this was the only channel I did not tested !!!

Thanks for your support and your awesome firmware.

Might be a good addition to the "Universal ACCST Guide" ? I have added some descriptions of the fields used on the 3 pages of setup script. Are you interested by the file ?
 
Back
Top