openrcforums

I have received several requests for "maintenance mode" to be available in openTx revision 2.0.15, to allow easy updating of SPort device firmware.
As a result of these requests, I have built standard and plus versions with this in.

I have done no special build options, just included lua, I can't really do all the many custom combinations users may require.

It only took me around 10 minutes to get the 2.0.15 sources and add this in.

I've tested the PLUS version and updated the internal XJT firmware on a PLUS, so I believe it is all working. As usual with something like this, please backup your EEPROM before flashing this version.

NOTE: Put your SPort .bin files in a "firmware" sub-directory on the SD card (not "FIRMWARES"). Instructions: Mike.

Thanks Mike.

Awesome Mike. Thank you so much for your contribution.

Rob

Hi Mike,

Thanks for doing this, but the plus version is missing the GVAR-page.
I can't fly my models without that.
I reverted to the standard 2.015

I thought they were included by default, clearly not. This concept of choosing what you want in a build isn't easy to deal with.
I feel, for the Taranis, there should basically be a single version. I'll see if I can build a version with the GVARs in.

Mike.

Version(s) with GVARS added to the first post.

Mike.

Hy Mike,

Danke!

I've built openTx 2.0.16 with maintenance mode added, doesn't take long to do the changes.
It should all work, although I haven't given it too much of a test!

I've built a version with GVARS and LUA in it, the same as the last version I did for 2.0.15.

Mike.

Hello mike

opentx V2.0.17 is out and fixes a few bugs in 2.016

Could you please edit a "maintenance" version of it ?

Such a wonderful tool - Can't do without it !!!

Regards

As I understand it, 2.0.17 only fixes bugs in companion. I can't see any changes to the radio firmware in the Github "Master" branch between 2.0.16 and 2.0.17.
I will, however, see if I can find time to put "maintenance mode" into 2.0.17.

Mike.

hello mike
Maybe I am wrong but I think 2.017 firmware has the mixer monitor and 2.016 has not because of a compilation script error (which is fixed now) Anyhow it would be nice to have the mixer monitor option in which case I could use only your bin file. Otherwise I keep a copy of your maintenance 2.015 file in case I need to update firmware from Taranis.
So no problem
Franck

I have the problem that openTx has all these different options. When you download openTx, a compile is done to match the specific options you select in companion. I can't really do builds for all the possible options, so I just picked LUA and GVARS as commonly expected options.
I think the change for 2.0.17 was to companion so it requested "mixer monitor" correctly, rather than any change to the 2.0.16 sources.

Mike.

Mike, my version of Companion (ver 2.0.16) fell over when I tried to use the transmitter simulator. The earlier version didn't and neither does ver 2.0.17 which I have now. I assumed that was the reason for the update which appeared very shortly after 2.0.16.

Geoff

That was also fixed in 2.0.17.

Mike.

Mike for the Taranis:
make PCB=TARANIS PCBREV=REVPLUS HELI=YES GVARS=YES LUA=NO_MODEL_SCRIPTS
is the standard build

thanks for including the maintenance mode

I've posted the changed and additional source files to add "maintenance mode" to 2.0.17.
Add maintenance.cpp and maintenance.h.
Change the Makefile to include maintenance.cpp
Change openTx.cpp to detect and action maintenance mode.
Change telemetry\frsky_sport.cpp to pass SPort data to maintenance mode.
Change targets\taranis\telemetry_driver.cpp to handle SPort transmit data.

Mike.

Hy Mike

thanks for the files for maintenance mode openTxV2.017 for Taranis and TaranisPlus

I can compile it with make all
and get a opentx.bin no errors, think thats ok

but with make simu I got errors

---------------------
maintenance.cpp:22:29: fatal error: stm32f2xx_flash.h: Datei oder Verzeichnis nicht gefunden
#include "stm32f2xx_flash.h"
^
compilation terminated.
telemetry/frsky_sport.cpp: In function ‘void frskySportProcessPacket(uint8_t*)’:
telemetry/frsky_sport.cpp:194:7: error: ‘MaintenanceRunning’ was not declared in this scope
if ( MaintenanceRunning )
^
telemetry/frsky_sport.cpp:196:38: error: ‘maintenance_receive_packet’ was not declared in this scope
maintenance_receive_packet( packet ) ; // Uses different chksum
^

file stm32f2xx_flash.h is at correct subdirectorie since all others too

----------------------------------

With Normal Makefile compiling is ok, make clean, make simu, make all, no errors, all ok

_______________________

How to use and compile it for V2.99 ?

Maybe maintenance.cpp needs to be in the EXTRABOARDSRC list, and the two items using MaintenanceRunning and maintenance_receive_packet() should be bounded by #ifndef SIMU.

I've not tried to build the simu myself.

Mike.

There is no reason to build a simu with that...

And there is no need for it in next either as the functionality is already built in.

ok, thanks Kilrah

I put it in because there is a need for the functionality now!
I've been helping out on the R.C.M&E. forum with people needing to update Tx modules and receivers and this is an easy way to do it.
I appreciate it will be in 2.1. I did suggest to Bertrand that what I have is put into 2.0.17 (2.1.18?) so it is available now should a 2.0.18 be needed, and it would also then be in any built download. It does only take a few minutes to add it in as I have it.

If 2.1 was definitely going to be released within about a week, I wouldn't suggest this, but as we go on through 2015, more and more people are finding the need to use this functionality.

Mike.

I know, all I said is it wasn't useful in a simulator (you can't even call it...) and the functionality is already in next.

Your 2.0 releases with it are welcome as an option for anybody who'd need it, and it precisely allows us not to include it in ours and thus avoid confusing everybody by releasing something that works in a certain way only to change it completely in 2.1. We already have enough confused users as it is...

Hy,

Thank you Mike for the Bootloader extension at openTx V2.0.17

SPort-update works at both Taranis and TaranisPlus

Kilrah wrote: Your 2.0 releases with it are welcome as an option for anybody who'd need it, and it precisely allows us not to include it in ours and thus avoid confusing everybody by releasing something that works in a certain way only to change it completely in 2.1. We already have enough confused users as it is...

Now you have me confused
Are you planning to do it in a different way in 2.1?

IMHO Mike's way (trims outward) is logical and it doesn't clutter the normal OpenTX behaviour. It forces you to turn off your radio, which is also a good thing if you start connecting stuff.
If you have it in the normal screens it gets more likely to just try that upgrade without carefully reading the procedure. Some users may not use a cable with reversed polarity.

In 2.1 it is done the way we always said we'd do it - from the SD card browser.

Just wanted to say thank you to Mike for this.
Since the new EU firmware for receivers and XJT, people have been looking for ways to flash without all the cables and the computer.

can anyone give me a link to the wiring diagram needed to upgrade the RX's via maintenance mode please - have looked all morning, I guess I am not using the right words to search....

I have to ask this question, because this is the closest thread regarding Xjt and Sport.
Does the T9x support OpenTx Firmware and XJT module now? Full support for Sport, etc.
Before, only er9x did so... Thanks to Mike...
I have another radio and was wondering if I can load up Opentx again and get it going with X8R, XJT and my T9X?

Thanks for a simple and quick response.

heliphil wrote:can anyone give me a link to the wiring diagram needed to upgrade the RX's via maintenance mode please - have looked all morning, I guess I am not using the right words to search....

You need to make a dual female servo cable and cross the red and black wire

I'm not planning to move to OpenTX 2.1x branch for now.
Is it possible to only updated the bootloader with your customized version?
So I should be able to have the maintenance mode (for S.Port update), but keep my non-modified French OpenTX 2.0.17 firmware.
This will it work?