openrcforums

Sorry, not really understood that. Please tell me again, part by part... Thanks..

More newbie problems. I have a 9XR Pro with OpenTx 2.2.0 (218) loaded. Seems to run OK. I have Companion loaded and have used it to set up a couple of models with fairly lengthy mixes. On the simulator these worked well. I was pleased with it. But, it seems that I have connection problems with my Tx...

Thank you João, Now I feel guilty.... within my club there are several that run OpenTx who can help me with those simple "how do you set that up" questions... there are no other Ersky9x users.

Thanks to all, especially MikeB for spending the time to help me.. I will go and play with OpenTx trying to configure mixes and modes for my F5J gliders. I recall enough of the old version of Ersky9x to know that it is fully able to host my mixes and more... so can be comfortable that I will have a ...

Yes, I had flashed the latest version onto the Tx...this does not give access to the SD card menu, the OpenTx f/w doesn't see a bootloader option. It has the opentx f/w now.

Attempted to install the OpenTx bootloader, from the Tx SD card browser. By selecting any of the f/w versions on there gave only options to copy, rename or delete, no install.

Running OpenTx, the menu SD-HC card list shows EEPROM (contents: readme.txt), FIRMWARE (cont: ersky9xr_rom.bin, opentx-9xrpro-autswit...... , readme.txt), FIRMWARES I added this dir earlier (cont: <empty>). ..and other directories.. nothing that looks like a bootloader.

I can try the bootloader, it would be nice if it would work with my Ubuntu system..... but how would I load the new boot loader? ... now that i have the new f/w the method I used last time will not work.

It's almost an non-issue now. It now works, apparently well, on Windows (I popped a copy of sam-ba into the right place) but not on Ubuntu Linux. MikeB tells me that the fact that sam-ba must be used is itself an indication of a (comms) problem, however the comms will only be used to transfer a coup...

Thanks for the info.. things have moved along a little.. I loaded a recent issue of Ersky9x then from that F/w installed bootloader V2.1. Then back to load OpenTx where the "sam-ba" issue remains the same...

I found a later issue Ersky9xr firmware and loaded it. I used to option to load the bootloader from this f/w issue. The Tx now reports having bootloader v2.1. I reloaded my OpenTx f/w. Seems fine, opentx runs. Within companion, it still pops up with the error message about sam-ba being missing and f...

Thanks for your patience.. I much prefer to use these things rather than config them to the latest version or "flash" exotic f/w for the thrill of it. As a consequence, I am not necessarily sure about how to go about many of these routines, so have to read up and ask. The user guides that ...

Although the screen reports "USB" when connected whilst not in bootmode, the Tx/SD card cannot be seen via the PC.

I agree, it would be desirable to sort it. If I connect the USB without entering boot mode, then the display shows "USB". In boot mode it shows "Connecting"... Not sure which is used for transfers... How would I get and load a later bootloader?

Thanks... I am a noob, so wouldn't know what may have changed. The model setups failed to transfer until I found a copy of sam-ba and dropped it into the appropriate directory. That stopped the error message and appeared to allow the transfer to complete. My Companion installation on Ubuntu (which a...

Thanks for you help with my noob problem so far..... A bit of a change. Having generated a f/w with Companion, I copied it manually to the FIRMWARE directory of the SD card and booted it from the on-screen menu. It appears to run the new F/W. Used Companion to set up a new model. Downloaded to the T...

I tried again to download a different f/w to the Tx. It failed, I had to copy it into the SD card directory and boot it from the menu. Stangely, it appeared to take a model setup with it.. but when I look at the SD card "models" directory, it has not been updated, an older model it there, ...

Oddly, I don't recall specifying the location of the SD card and model/firmware directories within companion...... not found an option for this

After starting again, I formatted the Sd card and copied back the directory structure. Regenerated the firmware on Companion and successfully downloaded it to the Tx. Rebooted the Tx and selected the new f/w. Ran the new f/w, seems ok. Entered into boot mode and connected to companion. Will not down...

I notice that the naming of the directories is the same as for the original Esky. could this be an issue?
I will start again after formatting the SD card.

It shows:
Boot Loader V1.1Ready

Connecting..

F1
E0


Now it runs OpenTx, from a f/w bin file as configured and named using Companion.

The screen does not change from the above.... ie always "connecting", never connected.

Although I now see the drives and can configure companion, it frequently reports that "sam-ba" cannot be found. I'm now trying it on Linux, but the same message appears. I have Companion 2.2.0N371 installed. I have configured my SD card copy and backup locations, I can read the F/w off the...

Thank you.... this made a difference, now I see them.. when connected via USB, powering on the radio shows "USB" on the Tx screen, suggesting that a connection is available but cannot be seen... with the Tx in boot mode, it's there with no missing file message.

Hi, I'd like to load #openTx onto my 9XR Pro, but have failed very miserably at each attempt. Please help.. This will have to be a step by step report.. Aside from other problems, one noticeable feature is that when any attempt to communicate with the radio is made, It reports "C:/Program Files...