ERSKYTx (was ersky9x) Questions

[kaos]

丫es，I read that。I am using Sky board, just don’t know it is the same situation or it is my mod has a problem.

[MikeB]

OK. We may get into some problems as the control protocol for the MULTI module is changing and I haven't updated ersky9x to the new version yet. As soon as I do, the MULTI module will need to be updated to match.

I have something of a problem with setting the telemetry parameters (port, baudrate, protocol). I have tried to make it automatic, but with the 9Xtreme having two modules, each with several different possible protocols, and a choice of places where the telemetry my be connected, it is getting more difficult to do this automatically.
I've just posted a test version to see if it will receive telemetry data. There are .bin files for the SKY board and the 9Xtreme.
For the 9XT, it expects the telemetry data is on COM2 (3.3V logic-level, non-inverted). The SKY board should accept the telemetry data on either COM1 or COM2, but both expect inverted data.

Mike.

[jhsa]

Mike,if using the multi as external module,is there a way of receiving it on COM1, the module bay pin 5? Would it need a level converter?

Thanks

João

[kaos]

Thx mike for clarify that, i thought i was doing something wrong.

Jhsa , multi telemetry does not need rs232 converter, go to com port straight. I have to byass my rs232

[jhsa]

I know, But as far as I know COM1 on skyboard and Ar9x is RS232 level.. That is why I asked. Not sure about COM2 though.
You had to bypass the level converter on stock 9x right? this thread is about erxky9x not er9x, so the levels used might be different..

João

[bob195558]

Mike, are the Sky9x and Taranis radios much the same ?

Bob B.

[MikeB]

The SKY/9XR-PRO/AR9X boards (SKY boards) use an Atmel ARM processor while the Taranis and the 9Xtreme use a STM ARM processor.
These do have some significant differencies, and the circuitry around them has some differencies as well. However, since they are all ARM processors, the compiled code is much the same.

Mike.

[MikeB]

Mike,if using the multi as external module,is there a way of receiving it on COM1, the module bay pin 5? Would it need a level converter?

Actually, I have a software driven UART that can operate receiving serial data, both inverted and non-inverted, on COM1.
What I also have is a big mess of code trying to work out how the telemetry data is arriving, on what port, what protocol, at what baudrate, based on various settings.
I've tried to make it all automatic, but I'm beginning to think I need a set of manual settings, possibly as an override to the automatic ones, to force how things should be set up.

Mike.

[jhsa]

I can't see a problem having to manually enter the settings for the multi protocol. We just have to enter it once per model, right? not every time we change the protocol or sub-protocol?

Thanks

João

[bob195558]

but I'm beginning to think I need a set of manual settings, possibly as an override to the automatic ones, to force how things should be set up.
Mike.

This sounds very good to me !

Bob B.

[willhac]

+1 for manual settings

I've just run the test version for telemetry on COM2 with MULTI on 9Xtreme : I still have the reboot problem if the telemetry signal is connected at startup, BUT if I connect it after startup the values appear and seem correct, I get A1, A2, RSSI, TSSI with a D6FR receiver.

[jhsa]

Please do something as a test.. Go to Radio Setup/General and turn "Splash Screen" to OFF.. See if you still have the same problem.. Please report back..

João

[MikeB]

Just posted another test version that might (!) fix the reboot problem.

Mike.

[kaos]

I know, But as far as I know COM1 on skyboard and Ar9x is RS232 level.. That is why I asked. Not sure about COM2 though.
You had to bypass the level converter on stock 9x right? this thread is about erxky9x not er9x, so the levels used might be different..

João

on my sky board, both com port do not use rs232 converter with Frsky modules. May be that is why I don't get telemetry data on either port with the Multi module.

[willhac]

Please do something as a test.. Go to Radio Setup/General and turn "Splash Screen" to OFF.. See if you still have the same problem.. Please report back..

João

Sorry I was out for a while, I usually have the splash screen OFF so I tried with ON but it's the same.
But it's all good because it's fixed with Mike's test version he's just posted !

[jhsa]

Great,

João

[willhac]

Yes I really begin to appreciate the 9Xtreme.
It has a big potential.
Thanks Mike !

[kaos]

I would vote for manual setting for protocol as well. You will never know what new things will come out 2 months from now, but if we can just set protocol, polarity, baudrate then there is no need to redo the codes.

[MikeB]

I actually now know why the serial interrupt routine could cause a reboot, and have fixed it so it now works.

I think a manual telemetry setting is useful, but I think having an "AUTO" option in it is also good for most people.

Mike.

[kaos]

You are just making us become brainless!

edit: besides, what the 'NOTE' is for.

[jhsa]

As far as I'm concerned I can't become brainless... well, not anymore.. and since a long time..

João

[kaos]

Does the latest test version for Multi 16 ch telemetry work with AR9X board? I could not get it to bind last night.

[jhsa]

I think Mike still didn't implement it on the sky type boards. Only 9XT as far as I know.

João

[MikeB]

I don't think I've posted a version for the SKY/AR9X boards, unless the A8/A10 version on the 21st has it in. I think it should have as I has a version working on the 'PRO on the 18th.
I have a note to make sure I post this.

Mike.

[kaos]

Ok, on the 'ersky9x test version' thread I saw this Dec 15 'ersky9x_sky_9xt_multi' says for SKY and 9exteme board for testing multiprotocol only. i thought it might work on ar9x too. So it does not even work on sky board? or it is not for 16ch version Multi?

edit: so many different version changing at multi side and er9x side at the same time, I think I got lost some where

[MikeB]

I think the file ersky9x_rom_A8_10.zip does have the updated MULTI protocol in it that should work on SKY and AR9X boards. Telemetry however needs an inverted signal sent to the SKY board.

Mike.

[jhsa]

Can we use just a transistor to invert the signal?

Thanks

João

[kaos]

I am really going crazy. Need to take a break from this RC thing.
I decide to replug everything back for my AR9X to stock switches and stick.. to fly over the wkend for a while. BUT something went wrong/crazy. Can't even get a simple 4 ch quad to work.
Here is the eeprom, the THR turn on/off light normally, but the throttle cut does not work, it is like backward, on is off, off is on, that even shows on analog data. When THR is on (light is on), the ana data is from 75.6 to -100 (stick bottom to up, while should not move), when THR is off (and light off) the ana data is -75.6to 100.
I check and rechecked calibration, mixes, switches... nothing there. and I reverted to r218, 06.11.2015 still the same. and when I bind my Flysky module to v959 the quad just went nuts after binding.
something I can't figure out. I was flying with this transmitter no problem till today. (using both my Joystick or the stock stick). or something happened to the hardware? which I did not change anything but removed the 1nF cap from AD8/AD10 to gnd. and even uplugged the ext1-3.
here is the eeprom, look at model 34, the simulator shows the same thing. the eeprom is downloaded with version r218 06.11.2015

crazy.txt

(512 KiB) Downloaded 142 times

[MikeB]

1. You have "Throttle trim" turned ON, you need it off for electric.
2. The first mix on CH3 doesn't need to be a Replace mix, just add.
3. Your throttle safety mix line should use the source as FULL (or HALF), not Thr.
4. You may not know but for throttle safety, you may use a "Safety" switch. Make it type 'X' and it is "sticky safety". So, set safety switch for CH3 to:
'X' THR -100.
With THR towards you, then CH3 output is -100%. When you switch THR away, CH3 stays at -100 until the throttle stick is fully down, and then will follow the throttle stick. A useful safety feature as switching THR away won't let the throttle output immediatly jump to the throttle stick position.

Throttle trim is really for IC engines. It lets you use the trim to set the idle position without affecting the full throttle output.

Mike.

[kaos]

hmm, how did I turn on that throttle trim, never did that and did not catch it either.
The cut using HALF also, did not catch that.
I really need a break Eyes or brain is going nut!

Have a Merry X'mas! I will.