ErskyTx Test Versions

Post by **MikeB** » Fri Dec 13, 2013 11:45 pm

This is NOT intended as a thread for discussions, just as somewhere I can put test versions of ersky9x for people to try out.
The idea is I'll put a specific test version on here, with a reason why it is here. Later, when I have something else to test I'll remove that one and replace it with another.
This should stop lots of test versions all over the forum, and help avoid the forum taking up more space on the server than it needs to.

Mike.

Reason for test version: Main popup and MODEl SETUP index menu.
I've also done a significant change to the Taranis versions. This relates to the internal coding for mix inputs.
The reason is the Taranis has an extra analog input (the Plus has 2). I did have this in order with the other pots/sliders but this has the side effect that the internal codes for everything after are one more that the same item on the SKY and 9XR-PRO versions of ersky9x.
This makes swapping model files between Taranis and SKY not really work. The change makes the files very closely compatible. but will mean any models on the Taranis that use a mix input after SL (P3 on SKY) will need to be checked. This includes inputs like HALF, FULL, PPMx and other channels. The firmware does, however, make SR appear after SL when editing a mix.
REVERSE the right POT operation on Taranis

NOTE: 19-Feb-2018, r221 is now released, also eepskye r422 is released.

The size of ersky9x_rom.bin may exceed 256K. On the AR9X board, make sure you have a bootloader rev 2.1 or later, or the flashing may not handle this size. On the SKY board (only 256K flash) use ersky9xs_rom.bin (s for small). This removes many languages to make it fit in the flash.
Versions that use new scripting language:

If you are testing these X10 versions, please report any problems. There seems to be a problem with the display operation at times, see this thread: https://openrcforums.com/forum/viewtopi ... =7&t=12604

x10_rom.zip: 28-May-2020 22:15
Improve handling of model images over 128x64.; (214.13 KiB) Downloaded 2 times

erskyTxR223A2.zip: 26-May-2020 22:29
Some improvements to multi-protocol module name and telemetry handling.; (3.37 MiB) Downloaded 12 times

ersky9x9XT_rom.zip: 25-May-2020 23:59
Test version for 9Xtreme, fix "SBUS input on trainer jack" bug.; (210.93 KiB) Downloaded 6 times

x10_rom.zip: 23-May-2020 21:24
Twelfth test version for X10/X10S (UNTESTED), fix graphic DMA interrupt bug.; (213.83 KiB) Downloaded 4 times

x10_rom.zip: 20-May-2020 22:28
Eleventh test version for X10/X10S (UNTESTED), add more interrupt debug and improve wddump file data.; (214.67 KiB) Downloaded 4 times

x10_rom.zip: 19-May-2020 23:30
Tenth test version for X10/X10S (UNTESTED), reduce display writing timeout.; (214.63 KiB) Downloaded 3 times

x10_rom.zip: 18-May-2020 23:50
Ninth test version for X10/X10S (UNTESTED), change watchdog file report.; (214.61 KiB) Downloaded 4 times

x10_rom.zip: 16-May-2020 16:36
Eighth test version for X10/X10S (UNTESTED), add extra to watchdog file report. Fix DMA2D interrupt flag clearing.
Add SDRAM and LCD reset on timeout.; (214.66 KiB) Downloaded 6 times

x10_rom.zip: 15-May-2020 20:32
Seventh test version for X10/X10S (UNTESTED), add extra to watchdog file report. Fix DMA2D interrupt flag clearing.; (214.61 KiB) Downloaded 8 times

x10_rom.zip: 14-May-2020 18:44
Sixth test version for X10/X10S (UNTESTED), add watchdog file report.; (214.58 KiB) Downloaded 7 times

x10_rom.zip: 10-May-2020 20:42
Fifth test version for X10/X10S (UNTESTED), add watchdog capture.; (214.21 KiB) Downloaded 14 times

x10_rom.zip: 09-May-2020 23:24
Fourth test version for X10/X10S (UNTESTED), change display code.; (426.79 KiB) Downloaded 9 times

x10_rom.zip: 09-May-2020 14:31
Third test version for X10/X10S (UNTESTED), change text editing.; (213.8 KiB) Downloaded 8 times

x10_rom.zip: 06-May-2020 20:27
Second test version for X10/X10S (UNTESTED); (213.77 KiB) Downloaded 15 times

ersky9x9XT_rom.zip: 05-May-2020 12:47
Attempt to fix "Bad EEPROM" on (Xtreme with serial encoder; (210.61 KiB) Downloaded 37 times

x10_rom.zip: 04-May-2020 21:56
Test version for X10/X10S (UNTESTED); (213.24 KiB) Downloaded 14 times

eepskye-i386.zip: 16-Apr-2020 10:29
eepskye for Linux .deb install
Fix Wizard and curve editing bugs; (2.18 MiB) Downloaded 37 times

x10E_rom.zip: 20-Mar-2020 11:56
Test version for FrSky X10Express.
Fix external Multi problem (may fix external XJT); (219.75 KiB) Downloaded 61 times

x10E_rom.zip: 19-Mar-2020 22:48
Test version for FrSky X10Express.
The external module now works with PPM, PXX(XJT), DSM and Multi.
Various screen layout changes; (219.77 KiB) Downloaded 35 times

x10E_rom.zip: 17-Mar-2020 22:10
First test version for FrSky X10Express.
The external module only works with PPM and PXX(XJT); (219.72 KiB) Downloaded 27 times

erskyTxR222D7.zip: 30-Jan-2020 15:23
Add SPI rotary encoder support for 9Xtreme.
Add "Min" function to Scalers.
T16 can flash internal module.; (2.87 MiB) Downloaded 257 times

eepskye.zip: 22-Feb-2019 23:12
A (third) definite test version with scroll bars and a resizeable window.
Some windows changed to improve the display.
This may help on displays with large fonts set.; (2.03 MiB) Downloaded 348 times

ersky9xr_romcells1.zip: 02-Jan-2019 00:02
Second test version for 9XR-PRO to handle 2 MLVSS sensors; (199.24 KiB) Downloaded 169 times

ersky9xr_romFlex.zip: 08-Nov-2018 17:08
9XR-PRO test version specifically for R9M Flex firmware; (198.95 KiB) Downloaded 155 times

xlite_rom.zip: 20-Jun-2018 23:45
First test version for the X-Lite.
Includes Apps:
Flash-Multi
Change-ID; (216.6 KiB) Downloaded 254 times

ersky9xr_rom.zip: 06-Apr-2018 22:21
9Xtreme only, includes crossfire telemetry script support.; (193.16 KiB) Downloaded 250 times

---------

opentx.zip: Test version of openTx r2940 for Taranis 14-Aug-2014 16:55
Minor change to "maintenance mode" to report "No Files" if directory is empty
This is r2940 with the addition of "maintenance mode" to allow SPort device update; (153.38 KiB) Downloaded 624 times

kaos · Post by **kaos** » Tue Jan 28, 2014 11:56 am

May be with a narration of what this test version is testing and changes are involved comparing to the latest version or whichever version it is trying to compare?
then no one else would post anything else here. You can lock the thread that only you can make/update post.

skylark · Post by **skylark** » Sat Feb 15, 2014 11:43 pm

Mike,
Just tried the latest test version (r202), Looks good so far. Still playing around with the model store feature, really impressive. I'm really chuffed to bits with it. Brilliant. Great job mike.
Stan.

Toxi81 · Post by **Toxi81** » Thu Jun 19, 2014 5:52 pm

Hello MikeB,

I tried your newest test firmware ersky9x_rom from 18.june.2014 on my ersky v3 board, but the transmiter module ASSAN X8J doesn't work in PPM mode. Older firmwares work correctly. Can you help me with this?

Post by **MikeB** » Fri Jun 20, 2014 3:36 pm

I'll need to check. For the 9XR-PRO, I had to make PPM drive out as open collector to let the transmitter power off properly when using PPM with a Turnigy module.
It is very likely this change is also in for the standard SKY board. I'll check, and remove the open collector drive for the SKY board. I may need to make it an option!

Mike.

Toxi81 · Post by **Toxi81** » Sun Jun 22, 2014 5:37 am

Thanks, I will wait for new version rom which will fix it.

Post by **MikeB** » Sun Jun 22, 2014 7:21 am

Try the one I posted on the 21-Jun, the open drain/collector driver should only be in for the 9XR-PRO. The ordinary SKY board now always drives low and high.

Mike.

Toxi81 · Post by **Toxi81** » Fri Jun 27, 2014 4:30 pm

Hello Mike,

I tried your last version ersky9x_rom from 27.june and it works correctly. Thanks for your support with the problem in PPM mode...

idar66 · Post by **idar66** » Thu Apr 02, 2015 6:13 am

hi mike great job with esky9xr ive got taranis and 9xr pro, ive been using open tx until pro arrived, i upgraded 9xr pro to lastest esky9xr and im loving it took mr awhile but i getting there, can you tell me does verson 204 have your updates for sport updates and sbus inprovements like on lastest test versions, also the esky9xr zip do you just paste it into eepee folder to replace the old one already installed, thanks for help idar

Post by **MikeB** » Thu Apr 02, 2015 10:18 am

r204 does NOT support PXX and SPort on the 'PRO, I think these were in from r211.
For eepskye, just copy the .exe from the .zip file into the eepe folder. You might rename or move the existing eepskye.exe first just in case you need to revert to it.

Mike.

GhostSharp · Post by **GhostSharp** » Wed Dec 30, 2015 3:01 pm

Hi Mike,

The ersky9xProvR218i.zip is valid for 9XR PRO too?

Post by **MikeB** » Wed Dec 30, 2015 3:41 pm

Yes, just use ersky9xr_rom.bin.

Mike.

Post by **jhsa** » Sat Feb 27, 2016 4:43 pm

Mike, the version "ersky9xProvR219h" from today has only mavlink updates? or also some other features/options that need testing? Just that I know what to look for after I've flashed it..

Thanks

João

Post by **MikeB** » Sat Feb 27, 2016 5:22 pm

The only thing other than Mavlink is when you are selecting the protocol within MULTI, if you go past the known, named options, it displays a number up to 31. This is a start to allow extra protocols in the MULTI module to be accessed without needing an immediate update to ersky9x.

Mike.

nuttybrewer · Post by **nuttybrewer** » Sun Mar 06, 2016 5:07 pm

Hi Mike,

I'm struggling with the telemetry from my APM to my 9XR-Pro. I'm using a combo of XJT/X8R from FrSky and I have them bound in D16 mode and my model is using the Pxx protocol. I also have the HobbyKing cable that connects the serial port on the XJT module to the Futaba Trainer port on the top of the 9xrPro. I zapped the latest r219h code from this site.

On the quad side, I installed an AirborneProjects module instead of the Teensy-based APM_Mavlink_to_FrSky. I'm assuming they do the same job. I also configured my APM2.7.2 board as per AirborneProject's quick start guide https://www.airborneprojects.com/wp-con ... -Guide.pdf

I configured the model's A1 variable to have a multiplier of 4.7 which pegs the reading at 12v on the telemetry screen. The only other reading that seems to indicate a value is RSSI which fluctuates. I'm also getting an inconsistency between selecting COM1 and COM2 for the telemetry. If I select COM1, I get a voice alert "Telemetry Signal Acquired" and the RSSI value appears (A1 gets pegged to 12v). If I set to COM2 I get a voice alert "Telemetry Signal Lost" and then all values stay at 0. In both cases, all other values don't seem to register. Telemetry from the Mission Planner seems to work as expected (battery, RSSI, GPS, Flight mode, etc.).

Is there any troubleshooting I can do from the radio to at least confirm I'm getting a signal from the telemetry port?

Could the AirborneProjects module be what's wrong here?

Thanks,
Pat

Post by **jhsa** » Sun Mar 06, 2016 5:38 pm

nuttybrewer wrote:Hi Mike,

I'm struggling with the telemetry from my APM to my 9XR-Pro. I'm using a combo of XJT/X8R from FrSky and I have them bound in D16 mode and my model is using the Pxx protocol. I also have the HobbyKing cable that connects the serial port on the XJT module to the Futaba Trainer port on the top of the 9xrPro. I zapped the latest r219h code from this site.

With the XJT module, you DO NOT use the telemetry cable between the module and the futaba trainer port.. That is only for the DJT module. The XJT is directly supported by the radio.
In the telemetry menu/frsky com port, select COM1.

João

Post by **MikeB** » Sun Mar 06, 2016 7:12 pm

I've had a quick look at the source code for that device, it looks as though a lot of it is compatible, I'll need to have a closer look to confirm. It does seem to map most of the expected values onto suitable FrSky values.

As João says, use COM1, the 'PRO has an internal connection to the XJT so doesn't need the external cable.
Have you selected "ArduC" as the "Usr. Proto" in the telemetry menu?

Mike.

nuttybrewer · Post by **nuttybrewer** » Thu Mar 17, 2016 8:30 pm

Ok, just got some Teensy 3.2 boards from PJRC. I loaded the APM_Mavlink_to_FrSky code into Arduino IDE (after installing the Teensyduino extra libraries).

At first it complained about clockspeed, so I dropped it to 16Mhz, now it says there's an error:
APM_Mavlink_to_FrSky:179: error: expected constructor, destructor, or type conversion before '(' token
ISR(USART_RX_vect)

I'm probably missing some libraries?

Mike, is there a github repository for this code? Your account only shows the ER9X code, just wondering (would make it easier for me than downloading ZIP files)

Also, is there a .hex file I could just upload to the teensy instead of compiling?

Razzor · Post by **Razzor** » Thu Mar 17, 2016 10:27 pm

Hello Mike,

First off, thank you for your awesome work with this firmware. I have a 9XR-PRO with a HC-05 BT module and have tested some of the latest test versions 219g,i,j. However, I have some problems with the telemetry.

My telemetry setup:
APM 2.6 <-> OrangeRX with ULRS frimware <--AIR--> OrangeRx with ULRS firmware <-> Dual channel inverter <-> 9XR-PRO

So as you see I use a inverter to invert the serial communication between the OrangeRX module and the 9XR-PRO due to that the interface is inverted. The 9XR-PRO is also modded so that COM2 is used. I have selected ArduC as protocol and the correct baudrates etc. The settings seems to be correct because when I choose the BTDirect function I can connect with my phone and send/receive data to the APM, no problems at all here.

But, to get the BTDirect function to start working I have to first set the option to FMSserial and then back to BTDirect. I have to do this at every restart of the 9XR-PRO. I also don´t get any telemetry in 9XR-PRO with COM2 Func. set to Telemetry. With this setting I also don´t get any connection over BT (BT Telemetry is ON).

Best Regards
// Lukas

Post by **MikeB** » Fri Mar 18, 2016 12:19 am

nuttybrewer wrote:At first it complained about clockspeed, so I dropped it to 16Mhz, now it says there's an error:
APM_Mavlink_to_FrSky:179: error: expected constructor, destructor, or type conversion before '(' token
ISR(USART_RX_vect)

I'm probably missing some libraries?

Mike, is there a github repository for this code? Your account only shows the ER9X code, just wondering (would make it easier for me than downloading ZIP files)

The code is written for the Atmel AVR processor (ATMEGA328 on an Arduino pro mini), so the ISR is specific for that processor. It will very likely need to be re-coded for a Teensy. I've not got a Teensy or done any coding for one.

I haven't put the code onto Github (yet).

Mike.

Post by **MikeB** » Fri Mar 18, 2016 12:28 am

Razzor wrote:My telemetry setup:
APM 2.6 <-> OrangeRX with ULRS frimware <--AIR--> OrangeRx with ULRS firmware <-> Dual channel inverter <-> 9XR-PRO

So as you see I use a inverter to invert the serial communication between the OrangeRX module and the 9XR-PRO due to that the interface is inverted. The 9XR-PRO is also modded so that COM2 is used. I have selected ArduC as protocol and the correct baudrates etc. The settings seems to be correct because when I choose the BTDirect function I can connect with my phone and send/receive data to the APM, no problems at all here.

But, to get the BTDirect function to start working I have to first set the option to FMSserial and then back to BTDirect. I have to do this at every restart of the 9XR-PRO. I also don´t get any telemetry in 9XR-PRO with COM2 Func. set to Telemetry. With this setting I also don´t get any connection over BT (BT Telemetry is ON).

The ArduC protocol selection is for when you use an Arduino pro mini to collect the MavLink data and convert it for transmission over the FrSky telemetry link. I haven't got as far as processing native MavLink, received on COM2, yet.

There is probably a baudrate problem on COM2. When you select telemetry, the baudrate is set for the expected telemetry according to the protocol to the Tx module. THis probably needs a few changes.

Mike.

Post by **MikeB** » Fri Mar 18, 2016 6:42 pm

The Aduino code is now on Github:
https://github.com/MikeBland/APM_Mavlink_to_FrSky.

I'm not sure when I'll have time to investigate the COM2 to BT function.

Mike.

nuttybrewer · Post by **nuttybrewer** » Fri Mar 18, 2016 10:22 pm

Ok thanks a lot Mike! I just configured the Teensy for the converter code linked from the copter.ardupilot.com telemetry site. I'm getting GPS values, A1, the flight mode, etc.

Just a quick question, on the main HUD screen, there's a little battery icon at the top and it keeps flashing at 0% (Even though the A1 reading right next to it is getting my battery voltage at a value that seems proper). Should I be mapping something else in the configs?

Thanks,
Pat

Post by **MikeB** » Fri Mar 18, 2016 10:49 pm

The battery icon shows the FUEL value, not the voltage. This relies on the current being measured and having a correct battery capacity entered in the APM.

Mike.

Post by **MikeB** » Sat Mar 19, 2016 12:35 pm

Razzor wrote:But, to get the BTDirect function to start working I have to first set the option to FMSserial and then back to BTDirect. I have to do this at every restart of the 9XR-PRO.

What setting do you have for "FrSky Com Port"?
There is a potential conflict between this setting and the "Com2 Function" setting. If you want to use Com2 for something other than telemetry, you (currently) need to make sure "FrSky Com Port" is set to 1.

Mike.

nuttybrewer · Post by **nuttybrewer** » Sat Mar 19, 2016 2:16 pm

Hi All,

One very frustrating thing about developing new features on these newsgroups is that threads and stuff get lost. Could I invite everybody to log issues on Github instead? https://github.com/MikeBland/APM_Mavlin ... Sky/issues

Post by **MikeB** » Sat Mar 19, 2016 10:06 pm

May we please move this discussion to this thread: viewtopic.php?f=7&t=8396.
This thread here is not meant for discussions, as mentioned in the first post.

Mike.

tomismrkolj1 · Post by **tomismrkolj1** » Sun Mar 20, 2016 6:23 am

Mike,

I tried newest verisons. Arudino did not want to compile so i removed "f" after airspeed * 10 (instead airspeed * 10f).
Now numbers fluctuate (40 to 50), but do not seem to be mutiple of 0,9 to 1,8, which is usual fluctuation when pitot tube is closed - not in flight).

tomi

CptanPanic · Post by **CptanPanic** » Tue Mar 22, 2016 3:07 pm

nuttybrewer wrote:Hi All,

One very frustrating thing about developing new features on these newsgroups is that threads and stuff get lost. Could I invite everybody to log issues on Github instead? https://github.com/MikeBland/APM_Mavlin ... Sky/issues

I see that you are starting to use the Releases feature on github also? It would def make it easier to see when new stable release is ready for ersky9xr

bob195558 · Post by **bob195558** » Tue Mar 22, 2016 3:27 pm

Sorry for jumping in here Mike.

Hi CptanPanic,
When you use eepSkye on your PC, it will auto check for new firmware updates.

Bob B.

openrcforums

ErskyTx Test Versions

ErskyTx Test Versions

Re: Ersky9x Test Versions

Re: Ersky9x Test Versions

Re: Ersky9x Test Versions

Re: Ersky9x Test Versions

Re: Ersky9x Test Versions

Re: Ersky9x Test Versions

Re: Ersky9x Test Versions

Re: Ersky9x Test Versions

Re: Ersky9x Test Versions

Re: Ersky9x Test Versions

Re: Ersky9x Test Versions

Re: Ersky9x Test Versions

Re: Ersky9x Test Versions

Re: Ersky9x Test Versions

Re: Ersky9x Test Versions

Re: Ersky9x Test Versions

Re: Ersky9x Test Versions

Re: Ersky9x Test Versions

Re: Ersky9x Test Versions

Re: Ersky9x Test Versions

Re: Ersky9x Test Versions

Re: Ersky9x Test Versions

Re: Ersky9x Test Versions

Re: Ersky9x Test Versions

Re: Ersky9x Test Versions

Re: Ersky9x Test Versions

Re: Ersky9x Test Versions

Re: Ersky9x Test Versions

Re: Ersky9x Test Versions