Spektrum AR6610T SRXL2 with Brain2

First the receiver must be powered (MIN 4,7V, MAX 8,4V) from the servo bus of the Brain2 and in the picture we can't see any power cable connected to the servo bus of the Brain2.
Note: the USB cable will power the inside of the Flight Control Unit, but will not power the servo bus (servos, receivers, etc.). This is done because the USB ports of the PCs do not provide enough current to power the servos connected to the Brain2 Servo Bus.

Second, using the apps (Window, Android, iOS) in the Receiver Selection panel of the Wizard, select the correct receiver type (SRXL2) which is the first icon on the left of the second row and not the last icon on the right of the third row (SRXL not "2").

Obviously the receiver must be linked to the transmitter and the transmitter must be powered on. This is indicated by the led on the receiver that must be on, indicating that the receiver is binded and powered and the transmitter is on.

Last: Have you updated the receiver firmware to the latest Spektrum firmware version available?

Thanks for the fast respond,

On the Ar6610T the firmware is 2.35.
Yesterday I updated the current firmware on the Brain.

If I use the Ar6610T without the SPM9746, I also get no connection to the brain. The Status LED remains dark

If I only use the SPM9747 receiver, the connection works and the status LED lights up green.

The same problem is also with a 7.8V BEC

Morning,
The SRXL2 protocol is only one, so it must work with all products that support this protocol.
In fact we have (obviously) tested it and it works without any problem both with receivers (SPM4650 and SPM4651T) and with satellites (SPM9746) and it works correctly also connecting on the same bus the ESCs SRXL2 Avian and FIRMA without any conflict in the data flow of the SRXL2 bus.

We don't have the AR6610T receiver available to do the necessary checks.

With our FCUs transmitting all the telemetry data received from the ESCs connected to our FCUs, the data received from the thermal sensors and the internal data also sent by our own FCUs there is no real need for a receiver like the AR6610T.

Moreover the solution of a satellite connected to the receiver and where the signals of the receiver and the satellite arrive together through the same single cable and contacts to the control unit is surely less reliable than three separate physical connections (receiver with its own connection plus satellite1 with its independent connection, satellite2 with its independent connection).
Also, as you can see, the SPM9746 satellites do not have antennas that can be protruded outside the edges of the carbon roof of our models that screen the radio signal.

For now we have written to Spektrum developers asking if and what could be the problem with their AR6610T receivers that compared to the others do not work.
To get an answer we will have to wait a few working days (today is Saturday, tomorrow Sunday).

If we don't receive an answer we will buy an AR6610T receiver to verify with our instruments.

Hello,

Thanks for your efforts.
My first plan here was that I would use an SPM4651T receiver and an SPM9745, but unfortunately the 4651T is currently out of stock. So I thought it had to work the same way with the AR6610T.
Then I hope that Spektrum gives us some information here.
thank you again

Hello,

Today I tested the receiver on an F7 flight controller with Betaflight. Here is the same problem. I think that either the receiver has a defect, or the firmware of the receiver is faulty.

Posted by: @wusa

Hello,

Today I tested the receiver on an F7 flight controller with Betaflight. Here is the same problem. I think that either the receiver has a defect, or the firmware of the receiver is faulty.

Thank you so much for the test and the information.
Having gotten to this point though and more out of curiosity than anything else, we will be ordering an AR6610T receiver today and when it arrives we will maybe start to understand a little more.

Hello I am building a new 700 and I have telemetry through my AR6610t and want to use SRXL2 protocol and it is not working for me. I was Just wondering if there has been a solution yet for this integration.

I have the same trouble with an Spektrum AR8020t, it dosent work with the brain (SRXL2). What is the solution ?

We have received clarification for the unexplained operation of these receivers.
Unfortunately, these receivers have only two UARTs.
Although not very clearly it is also written in the instructions ("This receiver features 2 integrated telemetry ports that are compatible with Spektrum telemetry capable transmitters.").
One UART is used for the sensors connected to the XBUS port and the other UART is connected either to the "BIND/PROG/SRXL2" port but only for the first 250 milliseconds and then to the "REMOTE Rx" port.
At power on the SRXL2 connector waits only for the first 250ms for an acknowledge from the firmware update software and then if there is no firmware update dongle connected the UART will take care of the remote satellite management.
If our control unit sends an acknowledge, then our control unit could connect but the remote satellite connected to "REMOTE Rx" port could never communicate and start working not being connected to any UART.
Given the above,
Since with our control unit it is already possible to connect through separate hardware connections up to two other DSMX satellite receivers in order to have a triple redundancy also hardware and to have a higher security than only one other remote receiver connected through the same and only one hardware cable of the primary receiver to our control unit,
Since our controllers have more output ports (3 x swashplate, 1 per tail, one per throttle, two auxiliary outputs for accessories and two for serial communication: SYS+USB, for a total of 9 ports) and therefore the PWM outputs of the receiver are not needed,
Since our Flight Control Units already transmit all telemetry data from the FCU, the ESC connected to the FCU and any thermal sensors connected to the FCU,
It is completely unnecessary to use these receivers instead of much smaller and lighter receivers like the SPM4650 and SPM4651T.
In short: the auxiliary receiver is not needed and would not work, the PWM outputs are not needed, the sensor input is not needed, the bigger footprint is not needed, the bigger weight is not needed.
For all these reasons, we do not consider it necessary or useful to implement operation with these particular receivers that could only be counterproductive by giving the erroneous belief that you have a second remote receiver that is actually not working.

Thanks for your research, but these receivers would still be useful, as additional sensors can be used here through the XBus connection (current sensor, capacitance sensor, GPS,...)
of course not absolutely necessary, but unfortunately some motor controllers have no telemetry.

The PWM outputs on the receiver would certainly be useful in some applications, but I think that Spektrum should do its job better here, so that the receiver can be easily programmed in the Spektrum software (e.g. as with Futaba - Ch1-9 SBus, Ch10-15 receiver)

Posted by: @wusa

Thanks for your research, but these receivers would still be useful, as additional sensors can be used here through the XBus connection (current sensor, capacitance sensor, GPS,...)
of course not absolutely necessary, but unfortunately some motor controllers have no telemetry.

The PWM outputs on the receiver would certainly be useful in some applications, but I think that Spektrum should do its job better here, so that the receiver can be easily programmed in the Spektrum software (e.g. as with Futaba - Ch1-9 SBus, Ch10-15 receiver)

The spm4651t needs the firmware updated to the most recent for it to work with the ar6610t. I've heard this problem with them not working together. Have you got a usb firmware update cable for the spektrum rx's? 

This should solve your problem.

Good luck,

Pete

@Uzzlaff 

Sorry, i completely mixed up my receivers there!!

The ar6610t and the spm4651t are both full range receivers in there own right. The spm4651t cannot be connected to the ar6610t as it is not a

satellite receiver. You will need to use the spm9747 srxl2 remote receiver if you want a satellite to cover the grey areas of your build.

Sorry for the mix up!! 

Hope this helps 🙂 

Has the issues with the 8020T been resolved? I have one on my TREX 550X connected to a BeastX via SRXL2 and was hoping to connect it to my Brain2. I have some 4649T's I can use if not but not sure if the 4649T receiver is as good as the 8020T?

Posted by: @andythilo

Has the issues with the 8020T been resolved? I have one on my TREX 550X connected to a BeastX via SRXL2 and was hoping to connect it to my Brain2. I have some 4649T's I can use if not but not sure if the 4649T receiver is as good as the 8020T?

There have never been any "issues" of our Flight Control Units with 8020T receivers!

Much more simply, the operation of this type of receivers had not been implemented for the reasons we have already explained several times:

"When using the SRXL2 protocol at the output of the "Bind/Prog/SRXL2" port of these receivers, the "remote receivers" connected to these receivers stop working and become just heavy, bulky and useless pieces of wood mounted on the model.
The use of these receivers has only disadvantages and no advantages compared to the use of a receiver like the SPM4651T since these receivers are bulkier, heavier, consume more power and are more expensive and the most important telemetry parameters are already managed by our control units without the need to connect sensors to the receivers.".

However, as we had also said, we have "anyway" already implemented in the firmware (currently in beta phase) also the operation of these "base" receivers.
By doing so we were also able to activate and use the SRXL2 signal on the CH1 (throttle) connector that would normally be activated and used by Spektrum Smart ESCs (Avian/Firma). Using the "base" receivers in this way we have also seen that the "remote receivers" connected to this type of "base" receivers work!

So in the Release Notes of the next firmware there will be, among others, the following notes:

   • Now also the SRXL2 signal coming from the "Bind/Prog/SRXL2" port of Spektrum "base" receivers (EG: AR6610T, AR8020T) is recognized and used
   • Now also the SRXL2 signal coming from the Smart Throttle output (CH1) of Spektrum "base" receivers (EG: AR6610T, AR8020T) and Spektrum "normal" receivers (EG: AR410, AR620) is recognized and used. This is the preferred way to use also "base" receivers if you want to avoid the internal RX UART for remote receiver connected to the base receivers is disabled and used for "Bind/Prog/SRXL2" communications!!!