I have another question.
After i have updated my AR6610T i have more than 6 channels.
How many channels do i have now?
[SOLVED] srxl2 AR6610T
Hello MichealHeliMLM wrote:@10x... as you are 'playing around' a lot with srxl2 too... did you test failsafe? how is your experience? as i my parallel thread... i am in trouble with it not working
I have now had a chance to test. With the 6610t and 4651t connected as a sat to the spirit the fail safe does not work, the motor still keeps turning. Also regarding the RSSI signal i also get the 100% all the time walking down the garden. I also have another 4651t not connected to any thing so just bind that to the tx to a new model with a battery and the RSSI is working correct dropping as i walk down the garden...All Spektrum rx's on latest FW... Did you test your 4651t on its own not connected to the spirit?
Rgs Adrian
thx a lot for your test, Adrian... as far as it's about RSSI: my problem is also for 4651T only (connected to Spirit as well as battery-powered / not connected to anything) the RSSI problem seems to be clearly a Spektrum problem. fail safe on the other side really seems to be a Spirit topic with srxl2... so maybe Tomas could comment on it? maybe he has another idea for a solution...10x wrote:...
I have now had a chance to test. ...
as for myself i will not use it in the moment (switched back to 4649T which is 'failsafeing' as expected)... no failsafe with any heli bigger than a micro is a nogo for me
[edit]nb: recent news, Matt from Spektrum srxl2 dev.team just told they have been able to reproduce the rssi topic and found the problen: firmware update for 4651T will come after some testing...
cheers
Michael
Michael
Hello Michael
Sorry for missplelling your name....Yes i see the good news on RC groups...Just to add that i used a DX9 on the singal 4651t and a DX18 on the heli with 6610t and 4651t connected to the spirit if it makes any difference...
Rgd
Adrian
Sorry for missplelling your name....Yes i see the good news on RC groups...Just to add that i used a DX9 on the singal 4651t and a DX18 on the heli with 6610t and 4651t connected to the spirit if it makes any difference...
Rgd
Adrian
-
chris_0815
- Posts: 20
- Joined: Wed 18. Mar 2020 8:08:25
Is your 6610t on the latest firmware? According to Matt in rcgroups, only the 4651t should suffer the RSSI problem, so this might be a valuable information to him ...10x wrote:With the 6610t and 4651t connected ...
Regarding RSSI testing: I found it far easier to go to the range test menu and watch the dBm and RSSI values drop there in case of "reduced power" instead of "walking away"
chris
-
chris_0815
- Posts: 20
- Joined: Wed 18. Mar 2020 8:08:25
As written in the other thread:
However, they mark it as "failsafe channel data" (0x01) and send the throttle value that was set during binding.
I am not so familiar with the Spirit throttle settings: do you setup your throttle values in the banks or are they taken from "the transmitter/receiver"?
In the first case, there is nothing you can do about it until Spirit recognizes the failsafe condition correctly.
In the second case, the "smart failsafe" should kick in. Maybe you can configure Spirit in that way?
@Tomas: there is another thing to mention: if an SRXL2 receiver is powered and does not yet hear a transmitter, it sends "empty channel data" (i.e. channel mask = 0x00000000), not "failsafe channel data".
chris
If this is the case, it should be an easy fix on the Spirit side ...chris_0815 wrote:SRXL2 receivers send channel data even when the link to the transmitter is lost - but it is marked as "failsafe channel data" (0x01).
Presumably, spirit doesn't recognize that?
So actually there are two failsafe settings: one in Spirit and one in the receiver. The SRXL2 receivers don't stop sending data in the failsafe condition.chris_0815 wrote: When failsafe channel data is sent, all channels hold their last value except the throttle channel. Failsafe throttle value is the one set during binding,
i.e. you have to bind with throttle at the desired failsafe "position". Spektrum calls that "smart failsafe".
However, they mark it as "failsafe channel data" (0x01) and send the throttle value that was set during binding.
I am not so familiar with the Spirit throttle settings: do you setup your throttle values in the banks or are they taken from "the transmitter/receiver"?
In the first case, there is nothing you can do about it until Spirit recognizes the failsafe condition correctly.
In the second case, the "smart failsafe" should kick in. Maybe you can configure Spirit in that way?
@Tomas: there is another thing to mention: if an SRXL2 receiver is powered and does not yet hear a transmitter, it sends "empty channel data" (i.e. channel mask = 0x00000000), not "failsafe channel data".
chris
this should be fixed as in 4651T change log:chris_0815 wrote:...@Tomas: there is another thing to mention: if an SRXL2 receiver is powered and does not yet hear a transmitter, it sends "empty channel data" (i.e. channel mask = 0x00000000), not "failsafe channel data".
Version 2.39.0 (April 17, 2020)
-------------------------------
- Fix bug in RF reception in EU mode that caused invalid RSSI reporting and increased fades in some radios (thanks chris_0815)
Version 2.38.2 (March 9, 2020)
------------------------------
- Fix SRXL2 telemetry behavior when used with AR6610T or AR637T as a remote receiver
(NOTE: AR637T/AR6610T must be v2.34.1 or higher to realize the full benefits of this improvement).
- Set default SRXL2 channel data to failsafe values during init instead of at RF connect.
- Improve bind reliability.
Version 2.37 (December 17, 2019)
--------------------------------
- Initial release
cheers
Michael
Michael
-
chris_0815
- Posts: 20
- Joined: Wed 18. Mar 2020 8:08:25
Interesting, since not all SRXL2 devices seem to behave that way. I've therefore asked for clarification.HeliMLM wrote: - Set default SRXL2 channel data to failsafe values during init instead of at RF connect.
chris