ERSKYTx (was ersky9x) Questions

[NoahWL]

No luck with that test version unfortunately. It appears 250hz still works correctly, but at 500hz the radio and TX module appear to intermittently lose connection with each other. The screen on the module switches between its usual "Connected" status and "No handset." If I move the sticks or change switches the radio repeatedly says "no telemetry" and the module switches between "connected" and "no handset" more frequently (~2 times a second).

Not sure if it's any help but I tried to get some logs. The first is 250hz working normally on the test FW you provided. In the second, I enabled logging, waited a minute, turned on the quad, and moved the right stick around a bit. After I stopped logging and let the radio sit for a minute, telemetry data suddenly appeared. I started the log again (500hz log 2) and moved the right stick around some. The radio and quad were rebooted after switching from 250hz to 500hz packet rate.

The forum doesn't let me upload files with a ".raw" extension, so I changed the extensions to ".txt". Let me know if there's something else I can test.

[MikeB]

Please try this one, I found a reason why the last one would do something wrong at 500Hz.

Mike

[NoahWL]

This one behaves similarly, but a bit better. The link seems to hold stable until I move a stick. Then it disconnects ("telemetry lost" and "no handset"), but recovers after a second or two.

[MikeB]

I'm not sure why it behaves like that. I can see from the log file that it isn't getting into synchronisation, as the 250Hz timing does.
The attached file may do that correctly.

I'm working on something to do with LUA scripts, so the file has got bigger!

Mike

[NoahWL]

Looks like you got it! Weather is poor here so I can't test too extensively, but I haven't gotten a dropout and the RC commands in BlackBox appear to stable at 500hz. Nice work and thank you!! I'm curious what needed to be changed?

[MikeB]

Due to a lack of enough hardware timers on the Atmel processor, I'm using a PWM channel to provide the timing for sending the data.
I was using a default high time of 2.5mS and a period as required for the requested rate. For 500Hz, 2.5mS is clearly too long as the rate requires 2.0mS period. I changed the 2.5mS to 1.5mS, but this didn't allow enough time to synchronise to the RF transmission. The last change was to have a high time of 0.85mS and this did allow enough time to synchronise.

Mike

[Springer]

Just got a TX16s and while the EDGE firmware is less arcane than the original opentx, I still pine for my erskytx (on my TGY 9xrPro). I saw the "masterradio" thread, but it hasn't been active for 6 or so months. There has to be another place where it is discussed. I also saw the March23 latest version by Mike and downloaded it. I'm wondering where the implementation stands at this point, does everything work for LOS flying (not interested in elrs or FPV)?

[MikeB]

erskyTx is available for the TX16S, everything is fully functional. The FrSky X10 is also supported (the TX16S is basically a clone of the X10 for most things).
I've posted a new "test" version that includes a few more screen layout improvements, and some improvements to handling LUA scripts. There is a lot to do to get all the screens working well with touch, I did some quick changes that happened on most screens automatically (EXIT "button" at top right), but I have now also changed many menus to have a better layout for touch (EXIT arrow at top left) and a draggable scroll bar.

I've been busy with the UNI firmware for FrSky ACCST receivers, so I've spent less time on erskyTx.
I also got erskyTx running on the X20, and I've been making the touch screen changes for both the X20 and TX16S.

Mike

[Springer]

Sweet! Thanks, Mike for that, and for all the great things you do to keep ersky the best firmware!

I'll look back through the threads for the proper method of doing the update, unless you can point to a concise description.

[Springer]

This perhaps should be in the RMtx16s thread, but I'll ask here first. I downloaded the latest test version of erskytx for the TX16s, and loaded it to the micro SD card on TX. Tried turning it on in bootloader or maintenance mode (Horizontal trims apart and turn on). It just turned on and moved trims to max. I'm missing something or that's not the way for this radio. Also looked in eepesky and got the disk not loaded error when I tried to download the OEM firmware, so apparently I'm not doing that right either. Can You guys point me to a step be step process to flash erskytx on my tx16s?

[phil]

it's been 2 years since I installed erskytx. As far as I know, nothing worked with Bootsloader, but with eepskye.
after installation everything worked.

[MikeB]

You need the Tx in bootloader mode (power on with both horizontal trims towards the centre), then plugging in the USB should let you flash from eepskye.

Mike

[phil]

Hi Mike,
I had to replace my PC. My old PC, upgraded from W8 to W10, opens the eepskye program, but tx16 is not listed under version. I've tried many times to optimize eepskye but it doesn't work. Where am I wrong?
greeting

[MikeB]

I'm now building eepskye with version 5 of QT.
You need to download (from the erskyTx test versions thread) eepskye5.zip, and unzip this into a suitable directory, keeping the directory structure in the .zip file.
Then also download eepskye5exe.zip (which I've just posted) and unzip the .exe file into the same directory (overwrite the eepskye.exe file that is now there).

Mike

[phil]

It worked, thanks

[Springer]

Mike, last night, i did more browsing and discovered that my reading about the trims away from each other was wrong,. Like you said, i then tried them toward each other and maintenance mode came up. I backed up the sd, put the .bin file in sd and was able to flash first time. Also able to revert just as easy. I was disappointed in the text quality though, is that an aliasing issue with the color LCD? Perhaps i'm just finicky after all the bling of Edge. Which i still can't get to do what i want. I really dislike the inputs/mixes/outputs. Guess i need to read more before i give up and go erskytx permanently

[MikeB]

I find the display looks better with the background colour changed (not white). I use:
Red 9, Green 31 and Blue 19.
Set these in RadioSetup|Display|Background Colour.

Mike

[Springer]

Ok, I'll try those, thanks!

[phil]

I've been using erskyTx for years on different transmitters, Frysky and Rdiomaster. Since I'm not always busy with model building, it's much easier for me to get back into the software_ menu. With one click I know where I want to go. With OpenTx I had to spend a lot of time programming a model. open TX is certainly more colourful, but changing a setting again is not quite as quick. From one flight day to the next with different ones there can be weeks in between Models and the equality of the software helps there.