openrcforums

Hi Mike, thanks, Yes I do see rx Voltage on A1 as well. er9x is really great. I used scaler just to name A1, where I redirect A1 to SC1 with name as RxV. and put SC1 to custom telemetry screen. so obviusly, no divider is needed, when we have A1 or rxV+Scaler.. thats great . thanks

Hi,
I use M2561 /Testing this firmware er9xProv822j
I need a bootloader ?


avrdude.exe: verification error, first mismatch at byte 0x1fd00
0xff != 0x90
avrdude.exe: verification error; content mismatch


Even with this error, it seems to work.

Marco.

Works OK for me, but I'm using an AVRISP-II programmer. It may be your programmer is not handling the flash space on the '2561 properly, or AvrDude is not doing it.
What version of AvrDude are you using?

Mike

This is a known issue with some programmers.

MikeB wrote: ↑Sat Sep 29, 2018 3:12 pm Works OK for me, but I'm using an AVRISP-II programmer. It may be your programmer is not handling the flash space on the '2561 properly, or AvrDude is not doing it.
What version of AvrDude are you using?

Mike

Hi,
I reviewed everything except the version of avdude, it was version 5.1, I changed to 6.3 and it worked. Sorry for the inattention.
Tks!!!
Marco.

Hello!

I haven't used my tx for a long time. I'm using a Turnigy 9XR (not Pro). It has the Version V1.438-Mike, 09.05.2015 21:23:35, SVN: er9x-r818, MOD: FRSKY NT.

My question: is there a newer that it's worth to update to? And if yes: where do i find it?

Thank you!

Regards
Skyscraper90

Yes there is, and yes it is worth it to update Many features added including support for the multiprotocol module. You can get the latest release version at www.er9x.com

Thank

jhsa wrote: ↑Fri Nov 16, 2018 2:50 pm You can get the latest release version at www.er9x.com

And whats the correct file? er9x for M64-FrSky, German?

Regards
Skyscraper

Depends on what processor your radio has. Some 9XR were sold with an m64 processor, and others were sold with an m128 processor.., so, you need to find out which of them your radio has..

João

good afternoon friends! Happy Holidays !!! I would like to ask a question about the versions of er9x. I found and flashed er9x v2. which one is developing on now? which changes and updates are made more quickly? what is the difference between v1 and v2? I also noticed that there is no possibility in the logical switches to create a condition of the form v <val Gvr1 -50. can not be compared with the negative. only> = 0. but equating Gvr1 with a negative value is possible. Is this a bug or a normal behavior? thank!!!

I am updating both V1 and V2, so both are being developed. I created V2 so I could do a major change to the EEPROM structure, resulting in a significant saving in flash memory use, and rationalising several things, e.g. the AND switch in logical switches is restricted in V1.
The flash saving is needed for those radios using the M64 processor.
Not being able to test a GVAR for negative values is a bug, it will be fixed in the next test version (both V1 and V2).

Mike

MikeB wrote:Not being able to test a GVAR for negative values is a bug, it will be fixed in the next test version (both V1 and V2).

Mike

So I use V2. I print gvar on telemetry screen and see negative values. I can output this values in channel and it ok. But! When I try make a log.switch I can’t set negative value on it. Only 0 and more...
Thank you!

MikeB wrote: ↑Mon Dec 24, 2018 6:29 pm Mike

Dear Mike, and all dear devolopers,

I am using the ye goode olde turnigy 9x transmitters again.

please be so kind:

-to link me an actual changelog where I can read the HISTORY:

I have now V1.438-MIKE
09.05.2015
21.23.35
er9x-r818
MOD frsky NT

and wonder, what HISTORICAL changes would I face if I install the latest er9x FRSKY.

(so that some mixes or inputs winn or will NOT be inverted etc.. )

see I am teaching my young kid and dont want any trouble

keep up the good work, let me know your paypal so that I can buy you a large pizza!! PM me!

cheers.

The changelog is here: https://github.com/MikeBland/mbtx/blob/ ... ngelog.txt.

I would expect you to be able to update to the latest release without any problems. As always, when doing this, if you backup your EEPROM and the firmware currently on the radio, if there are any unexpected problems, you may simply replace these and so restore the Tx to the current state.

Mike

Newest er9x firmware release and newest eepe, found here: (http://www.er9x.com/).

er9x manual, found here: (viewtopic.php?f=5&t=6473#p90349).

Hi!
Is there any chance that i can compile this code: https://github.com/MikeBland/mbtx/tree/ ... o/er9x/src
in Atmel Studio 7 ? I included all files but still gives an error that there is no opentx.h , and when i copy it from an opentx github project it gives more errors and warnings . I'd like to use is to buid an altitude logger for my turnigy 9x and DJT module combo.(I only need that part code which communicate with the module via usart, but when i copy the usart rx interrupt, other files also needed, and it gives errors again )

There is a makefile and you need to normally need to run a make from the command line with the correct options for the make you want.
I've never tried to build from the Atmel Studio, partly because I use a specific version of the compiler that creates the smallest code for the M64. Newer versions create more code that doesn't fit in the M64 processor.

Mike

I just followed up a couple of ideas I had and this has resulted in saving 264 bytes of flash and 9 bytes of RAM on the M64 (V1) version.

Mike

When we thought you cannot shrink that code anymore, you surprise us again.. If you keep doing it, we will start taking bets

Thank you Mike..

João

Just saved over 100 bytes more! The '64 version doesn't have Templates, but does need to use the basic, 4-channel template when creating a new model. I was using the templates code, cut down, but I just wrote a "only 4-channel template" routine that therefore saved all these extra bytes.

Mike

Also the templates can still be used in eepe's (computer) ?
So maybe there could be more stuff remove that would then be available only in eepe for setup purposes ?

A dream I would like to see come true is a totally open source radio system. I mean radio hardware and software, and also RF module and receivers. All DIY.
The multiprotocol module is already a good start, but I would like the open source community to create our own killer protocol. I bet that with time, we would come up with something way better that any commercial equipment.
I know, this is just a dream..
But if I look at what I use, I actually fly my models with DIY radio (upgrade boards), DIY RF module, and DIY receivers.. So, we are quite close.
Ahhhh, forgot the DIY openXsensor project as well
João

jhsa wrote: ↑Tue Jul 23, 2019 6:10 pm The multiprotocol module is already a good start, but I would like the open source community to create our own killer protocol.

Kiiller for what? Once you go custom and give up the convenience of off-the-shelf hardware people tend to want something that fully caters to their own little niche and can't be bothered with a compromise, so that'll mean more like 10 different protocols.

Someone actually recently developed a custom protocol but I doubt you'll like it since it has short range and only has 4 proportional channels, 12 on/off channels and no telemetry.

Killer for what?? Hmm, better than the protocols we have now?
And I am not talking about short range. I am also not talking about long range as most of that equipment does not transmit using legal frequencies anyway, and if they do, the power is way over the maximum allowed.
I am talking about gear for normal model flying.
At the moment I am using frsky protocol even if all hardware is DIY.
As I said my "Dream" is to have some gear which would be created by the model flying community, for the model flying community. And that would also include an "open source" protocol that could also be improved and updated if needed.
Model flying radio gear really improved since Erazz, Mike, and a few others started developing the systems we all know and love. Yes, frsky for example is what it is due to the efforts and ideas of the open source community. And not only frsky
And much more can still be done.

The open source community can for example start by developing an even more powerful hardware...

I remember many people saying that the 9x radio would never speak because the code would never fit in the processor, and that the processor wasn't powerful enough.. Well, Mike proved everybody wrong, and not only the 9x radio spoke, as it is still being developed today and getting new features.. yes, I am talking about the stock 9x radio.. This is the real DIY and open source.. This is taking knowledge to the limit and beyond. THANKS MIKE.

So, in my opinion, let the spirit of DIY and open source live

It was great in the beginning, and it stopped being fun when commercial stuff got in the way..

Just my 2 cents of course..

João

Well, I've just hit a total of 500 bytes of flash saved on the M64! I'm slightly surprised I've managed to save this many. I've also saved 13 bytes of RAM.
Bob: I think I've already removed all the items worth removing from the hardware menu, I'm not sure it is a good idea to remove anything else.

I now have the question of what to add in. Some candidates are (all are present in the '128/'2561 firmware):
Extras to scalers (MOD and destination)
XYcurve
FrSky and DSM bind options
Volume display on main screen
Failsafe setting from Tx
FrSky R9M support
6 extra logical switches

At this point I have no idea whether these will fit, and/or what combinations will fit.

At present I don't have the time or inclination to work on an open source RF protocol, it sounds like work not (hobby) fun.

Mike

As I said, it is just an idea.. It would be nice if a radio system was 100% open source and DIY

Thanks for all Mike

João

Sent from my BLN-L21 using Tapatalk

I've just posted test versions of er9x (V1). The total flash space saving on the M64 is 604 bytes now (12 bytes of RAM saved)!
Support for converting the RUD, AIL and GEA switches to 3-position switches is included. The .zip file also includes an updated eepe.exe (needs to be copied to your eepe directory) that supports setting these switches to 3-position. This is needed for the M64 version as the hardware menu doesn't include the settings.

Technical details of space saving.
When adding the 3-pos switch support I re-wrote the code to display the current switch positions allowing several areas to be merged to subroutines.
Each menu had a C++ object that stored the current vertical position in the menu. I've removed this object and put the data on a stack. Now we only need 5 bytes of RAM instead of nearly 20. This change than allows the simplification of detecting whether any particular menu line needs highlighting, removing a test from many lines.

Mike

I can´t believe that you're still saving space on that code

Thank You

João

Hi pilots and developers! I started work on porting the wonderful ER9X firmware to the FlySky -I6 transmitter. There is already some result. You can watch the video.https://youtu.be/nmXNQ-JMpLk

Nice..

João