Hi,
I've been trying to set-up a Spektrum AR6610T receiver in SRXL2 mode, and have waited until tested firmware is released for this configuration.
Yesterday's post by "Support" (Tomas?) in another thread said:
<Spektrum SRXL2 was impelmented in ver 2.8.1.4
Hello,
we have solved the problems with firmware update.
All SRXL2 receivers should work now.
Please flash this firmware:
http://spirit-system.com/dl/fw//spirit-fw-2.8.1.4df
Wiring diagram for AR6610T will be available tomorrow. For this receiver normal JETI Integration cable is needed (or you can make the cable at home)>
I have installed firmware 2.8.1, have correctly connected using the Jeti integration cable and set the unit to SRXL2 in the settings. All seems to function except throttle which does appear to work correctly in the 'diagnostic' page (throttle allocated to Ch1). Heli is a Trex 300X using an Align RCE-BL25A ESC. The ESC just beeps once per second after initialisation and doesn't allow ESC re-calibration. Spirit settings have a range of 1100-1940 uS. All was working using v2.80 and Spektrum DSMX satellite.
Is there a wiring (port) change for the AR6610T with v2.8.1, please?
Cheers, Andy
_________________
Spirit System developer
SRXL2 / AR6610T with updated FW version 2.8.1
I have my 6610t connected to a 4651t also so must use port 1 on the 6610t not the SRXL2 / data port....As Tomas recons that the new ver3 will be out in a few days i am going to wait untill then....All my controls work fine but no SAFE working....
Last edited by 10x on Sun 10. May 2020 15:22:21, edited 1 time in total.
10X,10x wrote:I have my 6610t connected to a 4651t also so must use pot 1 on the 6610t not the SRXL2 / data port....As Tomas recons that the new ver3 will be out in a few days i am going to wait untill then....All my controls work fine but no SAFE working....
Many thanks for this - very helpful. I will continue with the setup using the receiver port 1 (I need to do something with my time!) to see if it works but will also carefully check other functions including failsafe before hover-testing. If there's any issue, I'll wait for v3.0....
Cheers, Andy