er9x V2 = mbtx

Post by **MikeB** » Tue Oct 30, 2018 6:54 pm

I've done that change to my modeledit.ui file, and a newly compiled eepeV2 works OK (Compiled under windows).

What is your build environment? (OS, QTCreater version and compiler setup?).

Mike

Edit: You may need to change the "Default EEPROM version" in Preferences to 4. I actually need to allow 5 as this is the correct value for V2.

domind · Post by **domind** » Wed Oct 31, 2018 8:09 pm

After changing eprom to 4 it works OK.

Post by **MikeB** » Fri Nov 02, 2018 6:41 pm

I've made a change that should fix the templates problem "properly" and committed it on Github.

Mike

domind · Post by **domind** » Fri Nov 02, 2018 8:08 pm

thx. Now works even with epprom v1.
BTW what are the differences between eeprom versions?

german71 · Post by **german71** » Fri Nov 16, 2018 4:22 am

Suggest, do you might change the icone battery? It is V2 then make a change, like icon battery in opentx

Post by **MikeB** » Fri Nov 16, 2018 9:29 am

What battery icon? There is an audio volume bar, but the radio battery voltage is only displayed as a number.

Mike

german71 · Post by **german71** » Fri Nov 16, 2018 9:03 pm

Hi Mike,
I mean this battery icon

german71 · Post by **german71** » Fri Nov 16, 2018 9:04 pm

https://ibb.co/kG8YKf

Post by **MikeB** » Sun Nov 18, 2018 11:25 pm

Are you asking for a battery icon to be added? I doubt I could get it added for the M64 version. It not only needs the code to display the icon but also menu items so you may set the high and low voltage values. I'm also not sure just how good the icon is at showing "battery capacity" remaining using just he battery voltage, particularly for NiMh batteries.

Mike

Post by **jhsa** » Mon Nov 19, 2018 1:37 am

I think do it just by inserting the highest and lowest battery voltages, so the radio knows when is empty or full.
I still think that displaying the battery as a voltage is the best and most accurate way to do it. A graphic is obviously more "visual" and let's you get an idea much quicker than processing a numeric value..

João

tomatos666 · Post by **tomatos666** » Wed Jul 17, 2019 7:52 pm

Hello i have a Th9X with the Atmega64 Processor.
I use the R9M module with a R9Mini. I have a problem with the setting for the Pitch(E).
It´s allways a low value. I have just setting up in the Mixer a other stick for the Pitch bud allways the same problem.
What are the recomend setting in the Mixer for a drone with FC?

kmargos · Post by **kmargos** » Thu Aug 22, 2019 9:37 pm

Hi Mike,

I use firmware mbtx5a for telemetry correction. But it seems that telemetry is not working for the M2561 microcontroller.

Do I have to change anything?

Tks,

Marco.

Post by **MikeB** » Thu Aug 22, 2019 10:09 pm

Check this post (applies to the '2561 as well) https://www.openrcforums.com/forum/view ... 53#p119538

Mike

kmargos · Post by **kmargos** » Thu Aug 22, 2019 11:32 pm

Hi Mike,

Sorry Mike, a wire had a bad solder, but it seemed to be soldered.

mgouvea · Post by **mgouvea** » Sun Aug 02, 2020 4:47 pm

Hello Mike, I have a th9x 64 without a frsky mod and installed the mtbx-sv firmware, the r9m module I have is with the access protocol. When I press BIND the red LED on the RX does not flash. What to do?

Post by **MikeB** » Sun Aug 02, 2020 8:16 pm

I haven't considered implementing the ACCESS protocol in er9x, only in erskyTx for ARM processor based radios.
Unfortunately, I don't think it would fit in a '64 even if I try to add it in as there is quite a lot of code needed to support ACCESS.

Mike

Post by **Kilrah** » Sun Aug 02, 2020 10:11 pm

You can flash your module to ACCST.

antowa · Post by **antowa** » Thu Aug 13, 2020 3:06 am

Hi there!
I ordered a R9M 2019 and a R9 SX recently. Back then I didn't know that er9x doesn't support ACCESS protocol. MikeB, I wish one day you can make it possible. Thanks for all your work!
For now I ordered a FrSky STK and a R9 Slim+ which is supposed to be compatible with ACCST. Really don't want to get rid of my 9x.

Post by **MikeB** » Thu Aug 13, 2020 9:19 am

I don't think it will be possible, at least not directly. For external modules, ACCESS uses asynchronous serial communication at 400 000 baud.
The 9X (AVR) processor uses a "bit-banged" output and I don't think it would be possible to generate the required signal rate. The received data from the module (assuming the telemetry mod is done) goes to a USART, and the processor cannot generate this baud rate.

In addition, the ATMEGA64 processor doesn't have the flash memory spare to add the protocol, and I'm not sure the '128 processor has enough spare RAM either.

Mike

antowa · Post by **antowa** » Sat Sep 19, 2020 1:38 am

Hey again!
I've received the R9 Slim+ and was able to bind it to my R9M 2019. Extra thanks for FLEX firmware support, that's insane how you've managed to pack that into 64 kb.
I've ran into another weird issue though. After turning off my 9X I can't turn it back on for some time. The switch is 100% working since the radio module is getting power, but the screen remains blank. Replugging the battery doesn't help. After about 5 minutes of sitting turned off the radio turns on again. I don't have any mods except for a 12V wire for external display soldered onto the radio module pins.
Any ideas?

openrcforums

er9x V2 = mbtx

Re: er9x V2 = mbtx

Re: er9x V2 = mbtx

Re: er9x V2 = mbtx

Re: er9x V2 = mbtx

Re: er9x V2 = mbtx

Re: er9x V2 = mbtx

Re: er9x V2 = mbtx

Re: er9x V2 = mbtx

Re: er9x V2 = mbtx

Re: er9x V2 = mbtx

Re: er9x V2 = mbtx

Re: er9x V2 = mbtx

Re: er9x V2 = mbtx

Re: er9x V2 = mbtx

Re: er9x V2 = mbtx

Re: er9x V2 = mbtx

Re: er9x V2 = mbtx

Re: er9x V2 = mbtx

Re: er9x V2 = mbtx

Re: er9x V2 = mbtx