openrcforums

The multiprotocol module isn't much, if any better than a XJT. Without any heartbeat synchronisation the latency can get quite long. Also, the multiprotocol module sends channels 1-8 in one frame, then channels 9-16 in the next, 9mS later. I understand that the XJT actually may send some or all of channels 1-8 in the next frame if they have larger changes than channels 9-16. I have seen this happen when I captured the whole operation on a logic analyser.

I use a Taranis plus as my main transmitter, with the internal XJT module and a mixture of X and D receivers. I have no reliability problems either.

Mike

I use mainly the D protocol.
I believe there were some X receivers going bad some time ago. Maybe that is why I feel that the D system is more reliable..

João

I've been thinking about the request for having logical switches have a delay when switching off as well as when switching on. While investigating this I noticed the eepskye simulator doesn't do the delay, so I've been fixing that!
I've concluded this is likely to be something that is rarely needed. If you just want the delay when switching off, then create a logical switch that is the inverted logic, with the delay when turning on, and use the inverted switch where you need it.
If you want a delay for both on and off, create a logical switch with the on delay, then another logical switch that is simply the inverted output of the first, with it's own delay, and use the inverted version of this switch and you get both delays.
e.g.
L1 v>val Thr 50 delay(2)
L2 AND !L1 !L1 delay(1)
and use !L2

Mike

I didn't try it yet, but that will most likely work. Although this solution works, it is much less intuitive to newcomers to ersky9x than an OFF option that they / we can see..
One of the many great positive aspects of Ersky9x and Er9x is that it did become much more intuitive and user friendly on nearly every new released "test" version. And this is something that has been commented all over the different forums.

João

On the STAT2 display, there is a "Total On Time" timer. The value is reset by a LONG MENU press. It was added to keep track of how long the radio has been running since the battery was last charged. You, currently, need to reset it when you charge the battery for it to be useful.
I'm adding a new check at power on. The battery voltage is going to be saved at power off, then at power on, if the battery voltage is now more than 0.7 volts higher than the saved value you are prompted to reset the timer, which is done by the checking code so you don't need to go to the STAT2 display to do it.

I may look to add the ability to set a time limit so if this timer exceeds the limit you may have a warning it is time to charge the battery.

Mike

Thanks Mike..

João

I'm just testing the added feature of being able to edit the notes for a model on the radio.
You edit them one line at a time, but it all seems to be working.

I hope to post a test version in the next day or so.

Mike

That's cool. Thanks Mike

João

Mike, a little idea that could be useful for some of us.

What about an option to select what we want to see on (some?) main screens?
As a start point, for example, Timers main screen, select whether "Timer 2" or "Total Model Time" is displayed

João

Test version posted. I've included eepskye (Win and Linux) that support the "RunT" telemetry value. I've also included an updated "Helptel.txt" file.

Idea noted.

Mike

As a start to what might be possible for that idea, I'll make the "Total Model time" available as a "Telemetry value". With that, you should be able to use the value (hours:minutes) on a custom telemetry display, and also use it in a telemetry script.

Mike

Thanks Mike.. It is a very good start indeed. All the other Timers are already available anyway
The custom screens are indeed more or less what I described above. In that case would it be possible to have 1 or two more?
Do we have a Custom screen value for the active flight mode??

João

Flight mode is "Fmd" as a 'telemetry' value.
Within a script on a custom screen, you can probably have more than one screen.

Mike

Most of the users (me included) can't do scripts I probably have more fingers and toes than the number of people using scripts with Erky9x..
This is why I suggested at least another custom screen..

João

Worth you trying to do a script then!
I'll see about producing a simple script you may use as a starting point.

Mike

Thanks Mike.. I could probably learn it, it would take a long time, but I think I would manage it. But how many of us could? Many of us are only interested in flying our models
I believe some essential stuff should be implemented on the radio's firmware.
Scripts as far as I see and understand them, are good for configuring other equipment, like RF modules, receivers, flight controllers, etc.
With scripts, we could also make some screens for displaying data related to some protocols that the radio do not support, or to show data from flight controllers, like having an artificial horizon for example.

But critical data related to the radio itself and model being controlled, in my opinion, should be displayed on normal menus.
And also, absolutely nothing related to critical control should be controlled by a script.
Of course, this is just my opinion..

João

Probably not the best place to ask, but does ErSky9X on the Horus support serial mode for the irangex multi module?
Need to figure out which one to get.
Just getting myself sorted again after a long real life hiatus... some great stuff has been done here and I have a LOT to catch up on!!

TiA,
Rob.

It should work, but I can't test it as the external bay connector on my prototype isn't working, the power switch doesn't operate.

I need to investigate what the problem is.

Mike

Thanks Mike.
Have ordered the non-usb version from BG and will post results when it arrives.
Updating Horus to the latest test version this evening.

OK, I've fixed the problem with my prototype Horus. The module connector was wired with the pins in the opposite order to that required. Some track cutting and add 4 wires and it is all working. A Multi module plugged in shows the correct LEDs and reports back with the firmware revision so looks to be working.

Mike

Mike, what about a full reset option in the "Hardware" menu (Just because it is hidden). This would reset the eeprom. It would be great because we wouldn't need eepskye. Ok, we could always carry a default eeprom on the SD Card but not everyone will have it when really needed

Thanks

João

Mike,
Have installed the latest test version onto my Horus - nice bits of colour! Not had chance to see if/how I can get a picture into the currently 'No Image' box.
One thing I did notice is that the vario 'chirp' was chirping away happily by default with 'vspd' and '!LI' setup, and had to be disabled as the Mrs. was not happy with it hahah!!
But all else seems to be good so far after having a quick refresh on button presses!!! Great work as always Mike!

Time to get the cinemascope sized screen full now matey! hahahaha!!!

The odd control on the left, in the middle of the buttons labelled PgUp and PgDn, should be working as though it is 4 buttons, left, up, down and right.
For a picture, you need a .bmp file, 128 pixels wide, 64 pixels high and 24-bit colour. Then put the file in an Images directory on the root of the SD card.
I'm looking into getting a bootloader working, to enable access to the SD card from the USB.
The custom telemetry screens support 9 items, and use the full width of the display. There is also a custom display called 'X'. This has 3 items, and these appear to the right of the other telemetry screens.
What other things could be displayed on the currently unused areas of the display?

Mike

I've just posted "A8" test version. This adds the model timer value as a "telemetry value" (ModT).
For the Horus (X12), it implements the "double rate" driver code and the XJT heartbeat synchronisation to improve latency.
There was a minor bug on "Wide Screen" radios (wider than 128 pixels) when editing custom telemetry entries. When you did a LONG MENU press to get the list of possible values, it always started at "----" instead of the current value, this bug is now fixed.

Mike

Thank you
João

I now have ersky9x running on the FrSky X-Lite transmitter, I'll be posting a test version in the next day or so, complete with a couple of "apps".

Mike

Are the apps also for the other tx, or are they related to the X-Lite only?
Thanks for all Mike..
João

My understanding is he ported some of the existing apps to the x-lite (every app needs to be ported to every new radio).

Yeah, reading Mike's post again I realize that I misunderstood it the first time. Probably too tired

João

I've now posted a first version of ersky9x for the X-Lite, together with apps for "Change-Id" and "Flash-Multi".

Mike