ERSKY9X Coding

[MikeB]

We only have 10 characters for the name in the index menu, "Audio&Haptic" is too long.
I'll see what the 'numbers' could change to.
Usual problem with adding the Delay option, find somewhere in the EEPROM to store the value.

Mike.

[Daedalus66]

New test version posted for the QX7. This now includes the bootloader for the QX7, and also fixes a number os cosmetic problems where switches SE and SG were still displayed and sliders SL and/or SR were displayed.

Mike.

Hi Mike

I wonder if you could offer some guidance on loading ERSky9x onto the QX7.

As you will have seen from my earlier post, on my first try I ran into problems and was unable either to install ERSky9x or to go back to OpenTX. Eventually, by using Maintenance Mode I was able to get OpenTX working again (not sure why).

Anyway, I'd like to get ERSky9x installed, but want to make sure I do it right this time.

I really like the QX7.

Nigel

[MikeB]

You need to use the version of eepskye included in the X7 test versions. The openTx bootloader uses a lower case drive name so isn't found by previous versions of eepskye.
It should then be a case of using the "Write firmware to Tx" button to flash ersky9x, then if you copy the x7_rom.bin file to the Firmware directory and start in maintenance mode, you can update the bootloader, if required. Make sure you use the files from "x7_romC.zip", or later, to get a valid bootloader.

Mike.

[MikeB]

Also in "File Type" I think the "Numbers" type doesn't make sense anymore. I explain why. Numbered files can only be selected in the voice menu (forget the model names for a minute as the files are in a different folder).
A numbered file is also a named file. If you put it in the "User" folder, you can select any numbered file from the normal "Name" selection.
Currently, to select a GVAR or Scaler to trigger a voice (Numbered Files?), you have to scroll to the end of the numbered files. Over 500 I even forgot this existed, so difficult it is to find.
Scalers and GVARS could also look for numbered files inside the normal "user" folder.
So, based on this I suggest, replacing the "Numbers" Type with "GV&Scalers", or whatever name it fits. These would look for numbered files inside the "User" folder.

Numbered files are expected to be in the user directory, whether by constant or GVAR/Scaler. I think it drops out to look in the voice directory if the file is not found in the voice/user directory.
Numbered files are still used by "Voice Switches" found at the end of the Safety switches. These also should be in the user sub-directory.

Mike.
Edit: I have a change in where the GVARs and Scalers now appear before the numbers. Easier to skip these 15 items than skip 500 numbers.

[jhsa]

Numbered files are expected to be in the user directory, whether by constant or GVAR/Scaler. I think it drops out to look in the voice directory if the file is not found in the voice/user directory.
Numbered files are still used by "Voice Switches" found at the end of the Safety switches. These also should be in the user sub-directory.

Mike,that is exactly what I have been trying to say.. The numbered files are all expected to be in the "user" folder
Numbered files can also be loaded as "Names" in the voice menu.
Numbered files are NOT needed in the voice menu. If you need a numbered file because you had an old pack, just use the "Names" option
So, no need to have the option "Numbers"

I think the numbers should disappear from the option, and only the GVARs and Scalers should stay.

João

EDIT: I doubt there are many still using numbered voice files, but even if there are people using them, they can just load them using "Names". There is absolutely no difference. "Numbers are absolutely redundant there..

[Daedalus66]

You need to use the version of eepskye included in the X7 test versions. The openTx bootloader uses a lower case drive name so isn't found by previous versions of eepskye.
It should then be a case of using the "Write firmware to Tx" button to flash ersky9x, then if you copy the x7_rom.bin file to the Firmware directory and start in maintenance mode, you can update the bootloader, if required. Make sure you use the files from "x7_romC.zip", or later, to get a valid bootloader.

Mike.

Thanks Mike. Will try it later today.

[Daedalus66]

Success!

ERSky9x on the Taranis Q X7.

It works very well. I just had a bit of difficulty with the name editor, which worked but was awkward compared to using it in any of the other versions of ERSky9x. Perhaps needs Mike's skilled tweaking.

Also setting up triple rates was a problem for me. Never could find the right settings for Sw1 and Sw2 to give High, Mid, Low.
EDIT: Figured it out.

The rotary encoder seems to be a good way to interact with the Tx. Couldn't quite figure out the functional difference between Menu and the encoder button (on the left and right respectively in the accompanying picture), as they do many but not all of the same things.

Also noted that you need to press and hold the ON button, whereas in OpenTX just press and it completes the start-up.

Anyway, thank you Mike for this alternative firmware.

Nigel

[jhsa]

I believe, press and hold the button is the right procedure to avoid turning the radio On by mistake.

Also, I wonder what a reboot would do to a radio that doesn't have a physical switch keeping it ON. Any chance it would turn the radio OFF?

João

[MikeB]

No, we already dealt with that possibility on the X9E. The bootloader turns the soft power switch on immediately it runs if the boot was due to software or watchdog.

I did notice a bit of trouble using the name editor myself. On the bottom line I've added '<' and '>'. These move the "current position" in the text being edited left and right to allow easier editing of specific characters.

Mike.

[jhsa]

Mike, the trouble is not only on the QX7
For example, deleting the characters doesn't work very well. For example, instead of deleting the selected character, it deletes the one before.. I always have a fight with it when I make a mistake.

Also if you forgot a letter, you place the cursor where the new missing letter should be inserted, and it replaces the selected one with the new one, causing you to write the rest of the word(s) again. I think it should insert the new character BEFORE the selected character, and not replacing it.
Jusr my 2c..

João

[MikeB]

If you forget a letter you use the INS (INSert) option on the bottom line. This puts a SPACE where the cursor is and moves the rest of the text to the right.

I've wondered about DEL. It is written as it is so that if you enter an incorrect character, you just select DEL to remove it and go back to the same place to put the correct one in. Maybe, with the new '<' and '>' options it doesn't need to do that as you can just move back over the incorrect character and overtype it.

Mike.

[bob195558]

More info about the FrSky Taranis Q X7 Radio here: (viewtopic.php?f=98&t=9677&p=124995#p123297)
and new firmware here (http://www.er9x.com/).

Bob B.

[jhsa]

If you forget a letter you use the INS (INSert) option on the bottom line. This puts a SPACE where the cursor is and moves the rest of the text to the right.

I've wondered about DEL. It is written as it is so that if you enter an incorrect character, you just select DEL to remove it and go back to the same place to put the correct one in. Maybe, with the new '<' and '>' options it doesn't need to do that as you can just move back over the incorrect character and overtype it.

Mike.

Ok, but it would still be easier if we could just delete the highlighted character and not the one before. That's the way any other text editor works as far as I know
And if we could insert a character before the one highlighted, you wouldn't even need the INS option in there. Just select a letter and it would be inserted before the highlighted one. Much easier, and less clicks
The arrows to move to next and previous characters are a good idea.

João

[MikeB]

I've now posted a new test version. This suppoerts 32 channels and 64 mixes (up from 24 and 48). Make sure you backup your existing EEPROM before flashing this, and any later, test versions.
DEL in text editing now deletes the current character.
On the X9E and QX7, the 'Page' button steps the cursor right and left when text editing, a short press for right and a long press for left.

Mike.

[jhsa]

Thanks Mike.. Will flash it in a while and report. Thanks for changing the text editing Delete thing..

When I was to trying some examples on eepskye a couple days ago, I really felt the need for having somewhere in the model setup where I could write what that example does, what switches do what. Some general descripton/information about that model. Just like we have on the radio, but allowing many more characters. Would that be possible?
It would also be nice if this could also be seen on the radio. With more lines and characters allowed.
I know the screen is very small on the radio. But we could experiment?

João

[jhsa]

Mike, delete Character now works as it should, but if you type a character it will delete the next one. Confusing I think it should insert the new one BEFORE the next character instead of replacing it. This would make typing much more simple, without the need to go to the lower line again to insert a character, and then moving to the keyboard again.
Please check your Mobile phone to see how it handles new characters when texting Joking!!

Thanks

João

[jhsa]

Mike, new test version, 9XT, but I think it applies to all versions.

Still have the low cell voltage alarm reporting 0.00V when I turn the oXs on by plugging the Battery balance plug to it.

Now the really bad one, If the serial communication between the oXs and the receiver is broken, there is NO ALARM whatsoever, you are left without any of the sensor alarms. You will easily damage your LiPo, or any other critical equipment that depends on the telemetry information.
The connection between the oXs and receiver is just one wire, and a plug, and wires can break easily because of vibration, moving around when installing, etc.. Plugs can have a bad connection..
Maybe the radio should detect and alert automatically when TmOK is different from 2??

Thanks

João

[MikeB]

I think it should insert the new one BEFORE the next character instead of replacing it.

This is surely choosing between "insert mode" and "overtype mode". So this works in "overtype mode", and you use the INS option on the bottom line to insert enough spaces when you want to insert something.

Mike.

[MikeB]

Still have the low cell voltage alarm reporting 0.00V when I turn the oXs on by plugging the Battery balance plug to it.

Maybe the radio should detect and alert automatically when TmOK is different from 2??

Need to check if the oXs is actually sending a cell voltage of 0 when first powered on. I can check what a "real" FrSky lipo sensor does.

A bit tricky on TmOK. If you run a 'D' receiver, you may be only using A1 and A2 and no extra sensors, or a 'X' receiver without external sensors, in which case TmOK is only ever 0 or 1.

Mike.

[jhsa]

This is surely choosing between "insert mode" and "overtype mode". So this works in "overtype mode", and you use the INS option on the bottom line to insert enough spaces when you want to insert something.

Mike.

Ok, but that means unnecessary clicks It just doesn't make sense..

João

[jhsa]

Need to check if the oXs is actually sending a cell voltage of 0 when first powered on. I can check what a "real" FrSky lipo sensor does.

If it helps, If I plug the balance plug (Powering the oXs) before I power the receiver, I get no alarm..

A bit tricky on TmOK. If you run a 'D' receiver, you may be only using A1 and A2 and no extra sensors, or a 'X' receiver without external sensors, in which case TmOK is only ever 0 or 1.

Is there any other way of detecting that the serial communication has been lost?

Thanks

João

[RCHH]

Hi All,
Just flashed my now very ancient Sky9X rev.b with ersky9xProvR221b1 of 22-Feb-2017 23:56. Working lovely! Many thanks Mike!

Unfortunately due to a self inflicted hand injury 7 weeks ago, I am unable to fly anything. Or even work come to that, for at least another 2 months ... Grrrrrr! What an idiot!

[jhsa]

Sorry to read that. I hope you get better quickly.

João

[RCHH]

Thanks João. It is certainly something I will never, ever do again. First and last time event for certain.

[jhsa]

Mike, there is a way of having an alarm if the serial communication with the oXs is lost. Force the voltage to zero if the signal is lost.. At least we will know that we aren't receiving any voltage..

Thanks

João

[MikeB]

Please try setting a voice alarm to have a source of TmOK, a function of v<val, and set the val to 2 with a trigger of ON.
This should, I think, play a voice file when TmOk drops from 2 to 1 or 0.

Mike.

[jhsa]

Yes it does. as well as when I turn the oXs ON along with the Low cell voltage, and sometimes the low FasV voltage alarm.. I have a concert of voices at startup now

Mike, is there any reason you can't set the telemetry fields to zero if telemetry is lost? Just like with the RSSI, TSSI, etc?
Also, I don't think people will bother to set the TmOK alarm for every model, which is bad, as sooner or later someone will destroy his battery, and hopefully not his model.. It already happened to me a couple times when I was using one of the analog Ports that a wire to the voltage sensor broke. Last time was just before I installed the oXs. That was when I started having that problem that it was recently fixed. Fortunately it wasn't with the oXs or with a frsky sensor because I would have damaged my battery.
This kind of alarm should really be automatic as it has nothing to do with normal model programming. Most of us don't even know what TmOK is.

As far as I'm concerned this is a safety issue and I think I might have to go back to using the analog ports. it is safer as at least I will have an alarm if something goes wrong with the connections. I start regretting having wasted my time building the oXs sensors as they are useless if i can't have peace of mind when flying a model with them

Thanks

João

[MikeB]

For the oXs cell voltage, please set the Tx to be raw logging, then turn the oXs on. If you get the low cell warning, then pm me the log file.

Mike.

[jhsa]

Thanks. Will do..

João

[MikeB]

The problem with the oXs cell and voltage alarms is in the oXs itself. When you power it on, it sends some telemetry data reporting the cells as 0.00 volts and also the pack voltage as 0.0.
I think this should be fixed in the oXs itself. If ersky9x receives a telemetry value of 0, it should process it as 0.

Mike.