er9x development

[MikeB]

I've just committed r811. The main changes are:

Telemetry - accept OXsensor voltage
Add Scalers for '128/'2561 - uses too much flash to get into the '64 version
Add telemetry items for A3 and A4 (SPort)
Add custom LCD support - only used when custom compiling
Fix EXPO/DR bugs on upgrading - another bug from the stick mode changes!
FMx displayed on main screen for active flight mode - so you can see if you are in FM1 to FM4.

Mike.

[jhsa]

Thanks Mike.
Joao

Sent from my GT-I9195 using Tapatalk

[LTMNO]

Thanks Mike for the FMx and continued support.

[Malapell]

Thanks Mike;
I have seen some posts at er9sky concerning to a custom sw functios.
My vote is for adding lacht memory and flip-flop instead of duplicated comparisons v1/v2.

Nice to have for next compilation.

Jordi

[MikeB]

It's in the code and tested, but not in this revision as I need to get eepe sorted to match. This includes the MAC version that I have to get someone else to build.

Mike.

[Malapell]

Nice to heard this; wait is not a problem.

Jordi

[MikeB]

I'd like to add Scalers to the M64 FrSky version (they are in the '128/2561 version). The problem is if I do, there will be very little flash left. Partly because of this, I'm thinking of removing some other things.

Altitude Alarm - saves 164 bytes flash.
mAh alarm - saves 212 bytes flash.
Volt threshold - saves 128 bytes flash.
Flight Mode Trim - saves 166 bytes flash.

Total saving 670 bytes flash.

The first three can all be replaced by custom switches and Audio/Voice switches.
The last is replaced by proper flight modes.

Any comments or reasons to keep any of these?

Mike.

[Wimh]

I am quite happy with the present flight mode trim, but then I do not know what proper flight modes would be like
How do I custom compile a real noht frsky 811 version to keep just in case I do not like future versions?

[MikeB]

'Proper' flight modes are available in r811, they were added in r789.
You are, I assume, using a switch to enable a mix with the flight-mode-trim selected. Just use the same switch to select, say, Flight Mode 1 (FM1), and set the trim for the control to be "OWN TRIM" and the other trims to be "FM0". You should then have the same effect.

Mike.

[Wimh]

then I do not understand what this means :

Flight Mode Trim - saves 166 bytes flash.


The last is replaced by proper flight modes.

my flight modes work perfectly in 810

[MikeB]

Flight Mode Trim is where you select FlModeTrim in a mix, and then the offset field is used as the trim for that mix instead of the original main trim.

I put this in many revisions ago, long before I added the 'proper' flight modes. It is this option in the mixer I wish to remove.
Since I added proper flight modes, I don't think this option in the mix is needed.

Mike.

[jhsa]

I agree. you didn't remove the feature. You just moved it to another place.

João

[LTMNO]

Not that i am using a m64 anymore but i would agree with Joao, not removed.. just alt-configuration.

[MikeB]

I've just released r812:

Flash saving
Fix curve editing bug - couldn't edit the last point, confused with PRESET.
Fix ANA display bug - decimal numbers moved position with stick mode.
Add trim centre telltales - highlight when a trim is in the centre.

Mike.

[argo]

Hi Guys stepped away from er9x developments for a minute or two (ok a year!) and great to see things have moved on (in a big way).

Last time I was here the voice mod was the project of the day and I still get a kick out of this feature even though its old hat now. I still want to keep 'Betsy' going for a season or two so a quick question: with all the changes does the latest (downloaded via EEPE) firmware updates work with the original chip (m64)? Appreciate memory space is limited but other than that is all ok to use the latest firmware? I see there has been a fork for m64 & m128, how is that handled?

One of the reasons I ask is that I updated my TX a few months ago and all my Models looked ok but the settings were crazy. Going back to an old firmware sorted that out.

O' and is EEPE still 'backwards' compatible?

Many thanks!

[MikeB]

Yes to all your questions, I think. Download er9x.hex or er9x-frsky.hex for telemetry, for the M64. The M128 version has some extras.

As always, back up your EEPROM and firmware so you can go back if necessary, then try the latest version. There have been some EEPROM changes, but the loaded firmware 'should' update your settings automatically. If you are updating from a very old version there may be some problems, although I have tried to prevent these.

EEPE should still be backwards compatible.

Mike.

[jhsa]

Mike, what about a bootloader for the m128 and m2561 versions? any benefits?

João

[MikeB]

I don't think so. I gave it some thought, but they don't have any built in interface for programming using a bootloader.

Mike.

[jhsa]

FTDI? something like the arduino bootloader? Uses the TX and RX lines.. and probably the reset..

[MikeB]

Yes, but if you have telemetry as well they could be fighting each other for the serial port. And you would still need to use an 'proper' programmer to get the bootloader loaded in the first place.
If you have RS232 buffers on the telemetry lines, we might be able to connect using the 5-pin header in the module bay, but this wouldn't work if you have the TEZ board, or if you use the logic level method.
It's not impossible, but I'm not sure what the gains are.

Mike.

[jhsa]

well, it's just an idea. If there are no benefits then better leave as it is
What about the sound module and it's connection to the m128? could the sound module be a pass through to programming the atmega, connection to eepe, etc?

João

[MikeB]

Posible. The main question I have is: Is it worth me putting in the effort to do this, rather than new features and enhancements? 9X users are familiar with the existing methods, I'm not sure the effort is worth it.

Mike.

[jhsa]

As I said before, if there are no real benefits maybe better leaving it like that.. saving models to the sound module's SD card would be a nice feature though

I think/guess that some people don't like the 9x still being developed but I really appreciate that it is still being developed to make the most of the now obsolete hardware.. I think there is still room for some cool stuff, at least on the m128 and m2561.

I just had the chance of selling one of my 9x's and I declined because they are very personal.. and I still need them to test er9x and opentx if both keep being developed Saddly it seems that the 9x has been a bit forgotten by the openTX team. No more fun for them probably.. Oh well...

João

[MikeB]

The original 9X with the M64 is becoming limited. I think I'm going to add SCALERS into the M64 er9x. This takes the flash usage to 64890 (out of 65536) so there won't be much left for additions after that, but the SCALERS are useful.

I think saving models to the sound SD card is possible, but probably only for the '128/'2561, just too much code for the '64. I think it would best be done using "maintenance mode" to avoid any conflicts from the trim switches and the voice output.

Mike.

[mmilan]

1+ for the continued development of the 9x. With the 128 or 2561 they are far from obsolete. Thank you for the continued efforts!

[jhsa]

Mike, you mean the sound module in maintenance mode? Or a bootloader for the tx atmega? Or you mean starting the tx with an alarm active like we do for uploading new files to the SD Card? I can't se how we could save the models without clearing the alarms though.
Sorry. A bit confused here

Joao

Sent from my GT-I9195 using Tapatalk

[MikeB]

As on the 9XR-PRO, power on with the horizontal trims held apart, and the code then runs a mini application that only lets you backup and restore models to the SD card on the sound module. The serial port to the sound module connects to pins that are normally trim inputs. By running in "maintenance mode", you won't be using the trims or the voice output so there will be no conflicts to deal with.

Mike.

[jhsa]

yes, that sounds good. in other words we won't be using the radio while using this feature. So, that means a bootloader on the m128, right? because it will need to access the eeprom, where the models are stored?

Thanks.

João

[andrewju]

Guys, guys,

Does this mean there will be no way (even in theory) to save telemetry logs to SD card on the sound module? I was hoping if SD-card interface will ever get further development, it will not only allow storage of models to SD (which is a less of an issue on m128/2561 anyway because they already have twice as much EEPROM), but also to store telemetry logs (which I believe is more important)...

Perhaps, I'm asking for too much, but let's try to evaluate all options...

[MikeB]

I'm not sure the Mega328 on the voice board could handle both voice output and logging at the same time. Also, the only way to send the log data to the voice board would be to use the second serial port. This is shared with the left vertical trim switches. Using either of these switches will interrupt the data transfer. Not impossible, but the method used to send the data has to be able to handle this.

I don't want to stop development of the 9X based firmware, but with the 9XR-PRO coming out, which has all these features already, my time has to be allocated carefully or I won't get anything completed!

Mike.