Using FrSky S6R with ersky9x

[MikeB]

You only need to update the bootloader if I announce it has changed.

Mike.

[MikeB]

A new test version on the first post. This seems more reliable at fetching the parameters.
I've added a delay (350 uS) between seeing the SPort poll and sending the data out. This gives more time for the XJT to "turn the line round".

Mike.

[andrewju]

Looks like something is wrong. I can't fetch any values with the version you just posted.

For the next build, can you please also post a version for Taranis? There is some interest from Taranis users, too!

[MikeB]

I'll need to get a diode on my AR9X, I can only test on the 9XR-PRO at present.
There are some debug values available.
On the S6R menu, the three values at the bottom are:
Valid Index Value
When a request is made, Valid is set to 0, and is set to 1 on receipt of a response, when the other two items are also filled in.
Make sure you use a short press of MENU, a long press doesn't get the value. I'm looking to fix that!
Also, if you go to the Trainer Debug menu there are 4 (hex) numbers there, After several attempts at reading values from the S6R, it would be useful to know what those 4 values are. I'll move them to the S6R menu for the next test.

Mike.

[andrewju]

Ok, maybe I held Menu for too long... I see the values are being fetched.

Still, sometimes there is no reaction. In this case, the "Trainer diag" values are: 0017 0017 0017 0033

Update: after another unsuccessful attempt to fetch a value, the "Trainer diag" showed 001C 001C 001C 003D.

[MikeB]

OK, try this one, Taranis/plus included.
I've moved the values from the Trainer diag to the S6R menu (last but one line).
A MENU LONG should also read a value if needed.
The first of those 4 debug values should increment when you press menu. It counts the number of SPort requests sent.

I now have a diode on my AR9X, and that seems to be working OK.

Mike.

[andrewju]

Hmm... It still works in less than 100% of attempts for me.

I get to the S6R menu. Then I press "Down" to select the first parameter, then "Menu" to fetch the value. Then again "Down", then 'Menu", and so on.
Sometimes when I press "Menu", the upper line of digits increments by 1, but lower line stays the same and no value is fetched. Usually, a second press of "Menu" fetches the value. But in a few cases I have to click 5-6 times in a row in order to finally get the value. This seem to happen randomly and doesn't seem to be related to a specific parameter. It happens quite often though - once per 5-6 fetches, sometimes even more often.

[Kilrah]

Make sure not to have the receiver too close to the radio, remember how packets/telemetry gets lost if it is.

[andrewju]

Well, this doesn't seem to depend on the distance. I just tried it with the receiver in another room, about 10 meters far from the radio. Still the same.

I'm in a noisy area though - many large buildings with lots of apartments. Lots of wifi, bluetooth and other devices at 2.4GHz here. Still, connection with receiver (both telemetry and servo control) is never lost while I'm doing tests.

[MikeB]

OK, here's another one. I don't think I was getting the delay between receiving the poll (7E 1B) and sending the SPort packet out. I've increased the delay to 1mS, and I can see the gap on my 'scope. I don't think the status bit was being cleared so the timeout interrupt occured immediately.
It is possible on the Taranis, that the STM processor sends an "Idle" character when you first send data. This is a time of duration the start bit, 8 data bits and a stop bit of all 1s. This would provide a gap of around 170uS.

Mike.

[andrewju]

Confirmed!

The latest version fetches the data in all cases I tried so far. Works just GREAT!!!

[MikeB]

Another version posted! 2 more parameters included, and I fixed a bug where I used the wrong index so the wrong parameter was fetched/changed.

Mike.

[andrewju]

I can confirm data fetching works great. I could also store some values and read them back.

Everything works fine so far!!!

[MikeB]

I've only a few more parameters to add, and the calibration to sort.

Mike.

[andrewju]

Great, thank you VERY MUCH!

Another off-topic, if I may: I noticed the protocol name has changed from PXX to XJT. Is there a technical reason behind it, or is it only to improve user-friendliness?

[MikeB]

Just to improve user friendliness. New users won't know that PXX is needed for a XJT!

Mike.

[MikeB]

New version posted. This should handle all the settable parameters. I've also removed some of the debug.
Working towards the gyro calibration, I've added some images of the S6R to show which way up it should be during the 6 calibration stages (calibratio n is not yet implemented, just the images).
Are these images good enough to show the way the Rx should be placed? As you step through the possible parameters the 6 possible images are displayed at some point.

Mike.

[MikeB]

Warning: You can't set the failsafe on the S6R using the bind/failsafe button, the button puts the S6R into self-check mode. It may only be set from the Tx, and I haven't got that in ersky9x (yet!).

Mike.

[andrewju]

The images look Ok. Just the first one (with "S6R" placed horizontally) looks a bit thin, not like other versions.

It's an interesting note regarding the failsafe, somehow I missed that point. It will be great if you will implement Failsafe config in ersky9x. This could be useful for many (beyond just the S6R users)! Does it require bi-directional S.Port, too? I mean, will the Failsafe setup alone need a diode to be installed on AR9x ?

[MikeB]

No, the failsafe is set using the PXX protocol. I have it working. The menu may need some improvement, but I felt I needed to get it functioning quickly. Currently, you will just get a list of 16 channels, and be able to set the failsafe position from -125% to +125%, with a default of 0%.

As I've noted on another thread, I've found it seems to be possible to set the ELE2 output to NOT respond to corrections from the S6R, so it could be used for flaps/retracts. I assume the same applies to AIL2, but I haven't tested that (yet).

I'll post another test version on the first post in the next few minutes that includes failsafe and this new 'Off' setting for ELE2 etc.

Mike.

[MikeB]

Posted!
Failsafe setting is on the model|General menu, bottom of the first page.
You choose the type there, and edit the custom settings by pressing MENU LONG. You have to press MENU on any setting to be able to edit it.
The settings are sent every 10 seconds, so you may need to wait 10 seconds to be sure they have been set in the Rx.

Mike.

[jhsa]

Mike, that failsafe setting only works with the XJT, right? Then maybe it should be placed in the protocol menu, and ONLY if the XJT is selected? Or any other protocol that supports it?
Otherwise it will confuse people and they will think they can use it with any protocol..
Or can it be used with any protocol??

João

Edit: or perhaps a menu that would only be visible when a supported protocol is selected?

[MikeB]

I'll get to that. Adding another, protocol specific, option to the protocol menu is not straightforward, too many thing like that already.
I needed to get the failsafe menu in somewhere quickly.
Yes, it only works with the XJT (with a X series Rx).

Mike.

[MikeB]

This post of mine is also interesting: viewtopic.php?f=96&t=9192&start=60#p120522.
If this does work generally, it means you can have a standard, 4-channel model, and 2 other channels for extras like flaps and retracts.
I'd like to use this Rx in my Spitfire, but I need 7 channels (2 ailerons with differential, ele, rud, thr, flaps and retracts). A pity it doesn't have SBUS. I wonder if they ran out of processor pins?

Since I can send SPort data to this Rx, maybe I could program an Arduino to receive some SPort data and output a couple of channels of PPM! It would certainly work OK for the retracts.

Mike.

[andrewju]

Any chance to try and find an SBUS in S6R - perhaps, with some mods? This would have been amazing!

[jhsa]

I'll get to that. Adding another, protocol specific, option to the protocol menu is not straightforward, too many thing like that already.
I needed to get the failsafe menu in somewhere quickly.
Yes, it only works with the XJT (with a X series Rx).

Mike.

But I think it should be PXX specific.
I'm not sure (need to look), but doesn't multi have already something like that?

[MikeB]

New version posted. This handles the calibration.
I've also moved the failsafe setting to the protocol menu.
I've also included a version for the 9Xtreme.

Mike.

[jhsa]

I think it is the best place for it
Mike, a little off topic question, on these test versions is the Trainer over SBus still in the debug menu? my CC2500 modules still didn't arrive I hope they aren't lost
Thank you
João

[MikeB]

I know, but I needed to get it in somewhere quickly!
Yes, Trainer using SBUS is still in the debug menu.

Mike.

[jhsa]

Thank you.. I hope those modules arrive soon

João