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)

@MikeB I've changed line 109 into a comment (put -- in front) and upped the version number to 4a (so I know it was changed). Locked the receiver with three times a wrong code, then rebound as it became unbound, then activated it again (all with the updated script).

In other words, your recommended change works! I'll update the issue on github as well.
 
I've noticed, with an X8R receiver and UNI firmware V83, that CH5 servo moves to one side and back just after powering on the receiver.
I don't remember having this with V53 or V57, which I used earlier.
CH2 and CH5 are used for ailerons and it's only CH5 that does this.

Is it normal?

PS. After that it works just fine.
 
Last edited:
Further to my difficulties with dual binding discussed on P39 here, I think I have come across an insurmountable problem.

I have a Blackhawk Chipmunk in which I have to run more than 8 channels so it is arranged with an X8R and an X4R receiver. I bind these separately to my X9D+ Tx, the X8R as channels 1 - 8 in Telemetry mode and then the X4R as channels 9 - 16 Telem OFF.

I can then bind each in the same manner to my X18 Tx but to change back to the X9D+ I would have to set the Tx to bind (in which mode?) and switch on the receivers together.

Am I right in assuming the X4R MUST be in Telemetry OFF mode? In which case I cannot see that I can simply switch transmitters with the usual dual binding method. Correct?

On second thoughts, this may not be insurmountable if I used the the SBus output of the X8R to an Sbus to PWM converter to access 4 additional channels from the X8R. The only downside of this may be the effect on the servos controlled via the Sbus-PWM converter as I understand it only outputs PWM at 9ms pulse rate which could be bad for a non-digital servo. I would need to check the servos (I did not build this Chipmunk), but as they are all HV servos, does this mean they are digital??
 
I've noticed, with an X8R receiver and UNI firmware V83, that CH5 servo moves to one side and back just after powering on the receiver.
I don't remember having this with V53 or V57, which I used earlier.
CH2 and CH5 are used for ailerons and it's only CH5 that does this.

Is it normal?

PS. After that it works just fine.
I've tried to reset the receiver, but that did not change it's behavior.

@MikeB Is it normal that CH5 does some movement after powerup while all other channels don't do that?
 
Is it the receiver or the servo?
I just tested a servo by itself (no receiver). When I apply power the servo moves a bit, about 25% of total movement.

Mike
 
@MikeB Thank you for your response. I didn't test that, but I now have and it doesn't move with another servo connected to CH5, so guess it's the servo itself. The servo's used for the ailerons are both same brand & type and CH2 didn't do it so I thought it was coming from the receiver.
 
Do you have to power both receivers on at the same time when re-binding to the X9D+?

Mike
The short answer is Yes, but I think this is a rather academic problem now, which I could cure by using the SBus output from the X8R and an Sbus to PWM converter to run the channels 9 - 12 which is all I'd need.

However my problem escalated because I could not get the X8R to bind to both Tx's. So I decided to do some trials on my work table with an X8R, an RX8R pro and Rx6R receivers. I got myself thoroughly confused with the binding setups till I decided for each Rx, both Tx's should be set up with the same channel selection (exactly the same), Telem setting and failsafe modes. Maybe not all necessary.

Anyway, I could not get the X8R or RX8R pro receivers to bind at all. The Rx6R bound OK to both and I could switch between Tx's OK. So what was wrong? When trying to bind I was releasing the F/S button immediately and then getting just the red LED flashing slowly - indicating: no signal received but, I knew the Tx's were transmitting. Why was this? I had the Tx'c at various distances from the Rx's lying on my table, 3ft, 10ft, 20ft. All failed to bind. The Rx antennas were just lying on the table, parallel, ½" apart. I figured this was no good so I arranged 1 antenna to be vertical and I moved my Tx to within 1 foot, and bingo - bind was successful :D I repeated this on both the X8R and RX8R pro with both Tx's and achieved bind in all cases and the ability to swap transmitters.

This success was not just due to the antenna arrangement but also the closeness of the Tx, as I think (IIRC) bind did not occur with the Tx further away.
 
I don't know why I thought UNI was only available if you shipped your RX in or bought one new from Aloft. Have been flying around with several SXR receivers on the stock 2.1 firmware. I guess I'm going to be pulling them and updating this weekend. Would be easier for non-stabilized so I didn't have to recalibrate but ah well.
 
Has anyone tested the lua scripts on a X20RS? I am using ethos 1.6.2. I cannot get them to appear on my radio at all. I tried using the lua libray, with the files in a *.zip. It sees them, says it installs. But, I don't see the option anywhere after. I just got this radio. I bound the receiver ok. It is a X8R. It is flashed with v83.
 
Last edited:
Nope - not dead at all. We have been a little behind on emails this last week following our big annual event and then 2 of my guys being out of the office. We are coming back fighting tooth and nail now. :)
 
I do not see a request that has not been filled... I try to keep on top of them...
In some cases the response from Aloft with the code goes into the spam folder...
 
Firstly the UNI software development looks really great. Well done for all your hard work.

On the downside, I've flown a model on UNI f/w today for the first time, unfortunately it ended badly, with the model going in and destroyed. I'm now worried about flying the other models / receivers I've moved over

TX X20 Ethos 3.2, TD-ISRM 3.0.2
RX X8R
Uni firmware rev 84
Low VFR set to 60%
Low RSSI default
Bound ACCST D16 Telemetry on, 1-16 channels, LBT. With custom Failsafe, holding all, except applying zero power.

I've had this model for a few years, and no issues on reception etc. I was flying a few easy circuits to test. VFR was at it's lowest 96%. RSSI did drop to 50ish. While flying the model did a left roll, I was without any control, and crashed at good speed.

I've attached the log file, looks like the incident happened at 15:29. Anything I can get from this what might have happened?

Likewise any advice to check setup, logs, installation for my other models so I have confidence before flying?

Thank you in advance.
 

Attachments

Firstly the UNI software development looks really great. Well done for all your hard work.

On the downside, I've flown a model on UNI f/w today for the first time, unfortunately it ended badly, with the model going in and destroyed. I'm now worried about flying the other models / receivers I've moved over

TX X20 Ethos 3.2, TD-ISRM 3.0.2
RX X8R
Uni firmware rev 84
Low VFR set to 60%
Low RSSI default
Bound ACCST D16 Telemetry on, 1-16 channels, LBT. With custom Failsafe, holding all, except applying zero power.

I've had this model for a few years, and no issues on reception etc. I was flying a few easy circuits to test. VFR was at it's lowest 96%. RSSI did drop to 50ish. While flying the model did a left roll, I was without any control, and crashed at good speed.

I've attached the log file, looks like the incident happened at 15:29. Anything I can get from this what might have happened?

Likewise any advice to check setup, logs, installation for my other models so I have confidence before flying?

Thank you in advance.
Attached the stats output while looking at the RX on my bench.
 

Attachments

  • 1000062027.webp
    1000062027.webp
    172.3 KB · Views: 115
Back
Top