openrcforums

MikeB wrote: ↑Mon Oct 30, 2017 11:24 pm I clearly didn't change the setting to make the revision appear as r821.
As long as you have the date line as: DATE: 30.11.2016 then you have r821.
Mike.

Thank you Mike for clarifying !
Blessings,
Bob B.

jhsa wrote: ↑Fri Oct 20, 2017 6:41 pm Mike, Er9x, in my case m2561. This was reported by some other user by PM.

Set timer countdown. Radio says " 1 Minutes" instead of "1 minute". Could you please check that when you have time?

Thanks

João

Hi Mike,

In V2 too.

This "bug" is already two years old and nobody ever noticed?

Yes, I remember reporting it a while ago, but it is a minor bug and Mike might have had more important things to do

João

I have changed the source code in both er9x and ersky9x to fix this. I thought this fix was in er9xV2 (mbtx) that I posted on the 6th Nov 2017.

Mike.

MikeB wrote: ↑Thu Nov 09, 2017 2:43 pm I have changed the source code in both er9x and ersky9x to fix this. I thought this fix was in er9xV2 (mbtx) that I posted on the 6th Nov 2017.

Mike.

Sorry, in V2 is OK, I had loaded the old firmware.

I don't know if this is thread for feature suggestion. If not, please direct me accordingly.

On my Turnigy X9R pro, I need to hold the trims to get it into bootloader mode. But every time I do this, the trims become off-centered. Few times, my trims are so off-centered because I forget to recenter them and go fly. I have had quad flap on take off before I remember the trim. Is there anyway to not have the trim change when trying to get into bootloader mode?

If the radio starts in bootloader mode, then the trim settings should not change, mine don't. I can only guess you have occasions when the trims don't cause the bootloader to start, so are then taken as real trim changes.
However, on the 'PRO (running ersky9x with the ersky9x bootloader), if you plug the USB cable in first, then power on, it should start in the bootloader anyway, without needing the trims held.

Mike.

I found a small bug in the ER9x code that I downloaded from Github on 20180101

In the telemetry screens the (single) custom screen is displayed twice and the gps data screen is missing.

This is probably because the selection statements in menu.cpp have changed
in the older versions:
"if ( tview == 0x10 ") up to "if ( tview == 0x40 )"

changed in the latest version to

"if ( tview == 0x20 )" up to "if ( tview == 0x50 )"

changing it back to the old values shows the expected screens again

Reinhard

Thanks!
That is related to changes for "V2", which does have two custom telemetry pages.

Have you tried V2?

Mike.

No,I didn't try.
could try the original code as v2.
I have so many modifications in that rely on v1, so I assume, v2 wil not compile with my code.

Reinhard

I compiled the original code as V2 with EXT=FRSKY TEMPLATES=YES HELI=YES BEEPER=SPEAKER BOOT=YES V2=YES
without problems.
Now there are two custom pages available and all the other telemetry screens are displayed as well.

One small bug when configuring the custom pages:
when you step through the setup and enter the first custom screen, you have to push down once to get to the first parameter field and on the second screen you leave with the fifth parameter. The sixth parameter is skipped so you can never enter something there.

Reinhard

I've done a couple of changes to fix that bug and fix the telemetry screen selection.
I've attached a patch file with the changes in.

Mike.

I installed your patches (by the way, I assume there is a program that can apply the changes automatically ?? ) manually

(As I don't have FRSky telemetry, I can not verify the content of the telemetry screens)

Now version1 has 4 telemetry screens, one of then the custom screen.
Version2 has 6 telemetry screens, two of them are custom screens.

One problem with version 2
On the first setup screen where you set the voltages for A1 and A2, the voltages are stepping 0.01, 0.02 .... 0.99 10.0 10.1...
The stepwidth is 0.01 Volt up to 0.99 V and then jumps to 10.0 V continuing with steps of 0.1 V . No values from 1.00 to 9.90 V

Reinhard

In er9x.cpp, function "scale_telem_value" there is: change this to: Mike.

Thanks, Mike.
Now it steps in 0.10 Volt steps from 0.00 up to 100.00 V

Reinhard

The next test/release version of er9x for the '2561 will include a serial bootloader. I've just been testing it and it seems to be OK (can only handle 128K of flash), but the Tx battery just went flat so I need to charge it before I can complete the testing.

Mike

Wonderful.. Thanks Mike..

João

I'v just posted a new test version of er9x (V1) for the '128 and '2561. I realised I had customs names for flight modes available on V2, for these processors, and had allocated space in the model structure in V1 for them. So, I've now enabled the use of custom names for flight modes in the "normal" (V1) version. No change for the M64 as it doesn't have spare flash space.

It might be possible to add some features to the M64 version, but only by having the editing for such features only in eepe (as is currently done for most of the hardware menu). Or perhaps some, currently rarely used, features could have their editing only in eepe. Not ideal, but it is now very difficult to free up any more flash space on the M64, so most new additions to er9x can only be done for '128 and '2561 processors.

Mike

Thanks Mike.. will flash it to my m2561 as soon as I have a little time..

Sent from my BLN-L21 using Tapatalk

Mike, suddenly eepe started displaying this error message when flashing the firmware to my er9x 2561 radio.

avrdude.exe: verifying ...
avrdude.exe: verification error, first mismatch at byte 0x10000
0xcb != 0xff
avrdude.exe: verification error; content mismatch

avrdude.exe done. Thank you.

Any idea of what it could be happening?
Apart from that, the firmware seems to be working as it should..

Thanks

João

The firmware should include the bootloader, which is located right at the top of flash space. This needs AvrDude and the programmer to properly handle the extra paging to access this. It looks like one is not doing this correctly when verifying.
It works fine for me using AvrDude 5.1 and an AVRISP-II programmer.

Mike

The m2561 has bootloader? I thought it was only the m128 version.
anyway, I get the same error when flashing older ersky9x822a as well.

João

I posted above on 24-Feb that the next '2561 test version would have the bootloader, so now it does!
Flashing which older version, not ersky9x of course?

I've posted two test version (on 11-Mar and 13-Mar), both include the bootloader in the '2561 version.

Mike

I have flashed now the latest from 13th Mar.
But I did also flash the older version "er9xProv822a.hex" from 15-02-2017, and I had the same error..
We are of course talking about er9x, not ersky9x

Thanks

João

0x10000 is at the first byte beyond 64K. There have been problems in the past with flashing the '128 with more than 64K of code, this seems to be the same problem. As I recall it was a problem with AvrDude.

Mike

Well, I am using the avrdude that comes with eepe. I wonder if something changed in the radio.. it has been sitting on my table and it has been a while since last time I flashed it. As long as i remember, all was good..
tried with previous eepe I had installed, and also just downloaded the new one from er9x.com. Same error..

João

hello all, good day.. I have er9x it is great fw, but I just want to ask developers, if it is possible to correct or amend one voice file..
it is not the issue but, thing is, you have ,,throttle" and ,,switch" warnings active for startup notification that your throttle is not idle and switches are not in default possition, radio plays you the same alarm voice message with voice file played number 0023. a
Both warnings have related the same voice file number 0023
question is : it is possible to separate them to have each warning own voice file ? ?
for example:
0023 will keep for throttle warning
and 0027, which is not used according to sound files, will be used for switch warning ?

thank you and sorry for my english
Greetings from Slovakia, EU.... Mino

Voice file 0023 is a general purpose "ALERT" message.
I do have the throttle warning as voice 0074 and switch warning as 0075, but these are not currently played.

What processor do you have M64 or M128?
I used the same file (0023) for both warnings to keep the firmware small so it fits in the M64.
I will look to see if I can use 0074 and 0075 for the M128 processor.

Mike

m128 and 2561??

João

If Mike is not able to and you do not have the 128 chip,
here is where there is an option to upgrade your board with the ATMEGA2561-16AU CPU Chip:
(https://openrcforums.com/forum/viewtopi ... 105#p74105).

This was a long time ago, but Mike and João will help you through the process.
CHIP QUIK works very well.