OpenTX - Nightly builds for pre-2.0 testing

[rmsingh]

Hi guys,
I just upgraded Companion9X to 1.99.3 and downloaded firmware 1.99.3.
I keep getting this error:
dfu-util 0.7

Copyright 2005-2008 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2012 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to [email protected]

Filter on vendor = 0x0483 product = 0xdf11
No DFU capable USB device found

=================================================================================
DFU Util done - exit code 1
=================================================================================

Anyone can tell whats going on? I had no problem going from 1.52 to 1.99 to 1.99.1.

You need to specify what you are doing when you get this error.

I'm using Companion 1.99.3 to write openTX Taranis firmware 1.99.3 to the transmitter.

[cjklingman]

In Open TX Companion 1.99.4 General Settings/General Edit/Calibration Tab, what do these calibration numbers mean? And for that matter, what do the ppm blanks mean? The calibration numbers seem rather random.
My transmitter (on 1.99.4) is using the microsecond readout and my channels are set to 1000-1500-2000 roughly and this seems fine to me and all looks good on the monitor.
I have of course read the transmitter settings to Companion before seeing the problem above.
Thanks for you patience with my questions.

There really doesn't seem to be much of a Companion manual in spite of the transmitter itself having several good manuals.

C. J. Klingman
South Fork, CO

[Kilrah]

They're raw ADC readings, not of much use apart from copying/entering them manually from a backup or such if you want to do so. Running the calibration procedure on the radio is just much quicker though.

[MicheleVilla]

The Italian translation is very poor..................

You can help if you want!
The Italian contributor who was taking care of it hasn't been available for many months now, so the translations haven't been updated.

I have just try to modify the Italian translation (first step)
Plese let me know your comments

[Scott Page]

Hi guys,
I just upgraded Companion9X to 1.99.3 and downloaded firmware 1.99.3.
I keep getting this error:
dfu-util 0.7

Copyright 2005-2008 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2012 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to [email protected]

Filter on vendor = 0x0483 product = 0xdf11
No DFU capable USB device found

=================================================================================
DFU Util done - exit code 1
=================================================================================

Anyone can tell whats going on? I had no problem going from 1.52 to 1.99 to 1.99.1.

You need to specify what you are doing when you get this error.

I'm using Companion 1.99.3 to write openTX Taranis firmware 1.99.3 to the transmitter.

Given that you have 1.99.x you will find it fairly easy to follow this Protocol.
1. With transmitter turned off push the RUD and AIL trim switchs to the center while powering up the Tx.
2. Connect the tx with USB. - the microSD and the TARANIS volumes will mount.
3. Copy the new firmware file from it's location to the microSD card in a folder named "FIRMWARES"
4. Disconnect and power down the transmitter.
5. With transmitter turned off push the RUD and AIL trims to the center while powering up the Tx.
6. Choose update the firmware.
7. Choose the firmware you put on the microSD card. -- press ENT a couple times and you're good.

[rdeanchurch]

Scott
Isn't the above proceedure only valid after you have the bootloader in the TX....which requires that you can download Firmware with a bootloader, which means you have to have dfu ?

[Scott Page]

Scott
Isn't the above proceedure only valid after you have the bootloader in the TX....which requires that you can download Firmware with a bootloader, which means you have to have dfu ?

Correct but he says, " I had no problem going from 1.52 to 1.99 to 1.99.1." so he should have the bootloader when moving to 1.99.

[rdeanchurch]

I love the feature of having a file with Flight Modes and Switch assignments. It saves a ton of Functions.

Has anyone figured out how to handle !SXup-on.wav ?

Anyone?

[rdeanchurch]

Scott
Isn't the above proceedure only valid after you have the bootloader in the TX....which requires that you can download Firmware with a bootloader, which means you have to have dfu ?

Correct but he says, " I had no problem going from 1.52 to 1.99 to 1.99.1." so he should have the bootloader when moving to 1.99.

I thought he went from Comanion9x to Companion1.99.3/OpenTXCompanion and downloaded firmware to go with it....not than he had got the firmware OpenTX1.99.3 to Flash. I may be wrong.

[fe3]

At present you can with 1.99 down load firmware with Companion and update with DFU (TX off). Would it be possible to go into bootloader/USB mode and do the same thing getting rid of DFU problems. To have to copy the firmware file to the Firmwares folder is more problems for some people.

[bertrand35]

Yes, if you go into the Bootloader and place your bin in the FIRMWARES directory, you will be able to flash your Taranis from there!

[MikeB]

Have you not implemented the "Direct write to Firmware File" in Companion? This avoids needing to write the .bin to the SD card. It's all working in eepskye. Just power up the Tx in bootloader mode, run eepskye and click on the "Flash Firmware to Tx" button. Takes just a few seconds to do.
You should be able to use eepskye to update the firmware on the Taranis anyway.

Mike.

[fe3]

Have you not implemented the "Direct write to Firmware File" in Companion? This avoids needing to write the .bin to the SD card. It's all working in eepskye. Just power up the Tx in bootloader mode, run eepskye and click on the "Flash Firmware to Tx" button. Takes just a few seconds to do.
You should be able to use eepskye to update the firmware on the Taranis anyway.

Mike.

How do you implement "Direct write to Firmware File" in Companion TX latest

[Luc]

Hi!

1.99.1-1.99.4 The program has been updated.
The telemetry screen does not see the "Page" button and hold

1.99 The good telemetry screen

Luc

(google translator

[bertrand35]

Hi!

1.99.1-1.99.4 The program has been updated.
The telemetry screen does not see the "Page" button and hold

1.99 The good telemetry screen

Luc

(google translator

I don't understand what you mean!

[HC1969]

Does not appear on the radio telemetry screen (long press "page" button).

[rmsingh]

Scott
Isn't the above proceedure only valid after you have the bootloader in the TX....which requires that you can download Firmware with a bootloader, which means you have to have dfu ?

Correct but he says, " I had no problem going from 1.52 to 1.99 to 1.99.1." so he should have the bootloader when moving to 1.99.

I thought he went from Comanion9x to Companion1.99.3/OpenTXCompanion and downloaded firmware to go with it....not than he had got the firmware OpenTX1.99.3 to Flash. I may be wrong.

Thanks for the help guys. I did update the firmware by copying to the FIRMWARES folder. But I was hoping to update by using Companion to write the firmware directly. My concern was the "No DFU capable USB device found" error.

[MikeB]

How do you implement "Direct write to Firmware File" in Companion TX latest

If it is not already there, then by copying the code I wrote in eepskye to do this job.

Mike.

[bertrand35]

I will try to find time and add this code next week!

[adilsongoliveira]

Hello
I've been trying to compile companion on a 64bit Mint instalation (there's no 64 bit binary of 1.99 as far as I can see) and I'm getting a cmake error that I can't figure out how to fix (probably because I know nothing about cmake )
CMake Error: Attempt to add a custom rule to output "/home/adilson/opentx/companion/lbuild/moc_googleanalytics.cxx.rule" which already has a custom rule.
Any clues?
Thnaks in advance

[dvogonen]

Please report if you manage to compile. Both the OpenTX and Companion toolchains are needed to compile Companion and there is no known and documented method to install the ARM tools on 64 bit Linux.
But the problem you report does not seem to have anything to do with ARM. The cxx files are QT files.

[davx]

Hi,

No problem here to compile with Ubuntu 64bit.
I've followed these instructions to install the ARM toolchain : https://launchpad.net/~terry.guo/+archi ... m-embedded

@adilsongoliveira,
I'm doing exactly what is explained in the wiki to build Companion and it works.

Tchao

[dinamich]

Hello
I've been trying to compile companion on a 64bit Mint instalation (there's no 64 bit binary of 1.99 as far as I can see) and I'm getting a cmake error that I can't figure out how to fix (probably because I know nothing about cmake )
CMake Error: Attempt to add a custom rule to output "/home/adilson/opentx/companion/lbuild/moc_googleanalytics.cxx.rule" which already has a custom rule.
Any clues?
Thnaks in advance

Recent change in cmake config file in opentx requires to use cmake version 2.8.12.

More info at https://github.com/opentx/opentx/commit ... nt-6461403

[dvogonen]

Hi,

No problem here to compile with Ubuntu 64bit.
I've followed these instructions to install the ARM toolchain : https://launchpad.net/~terry.guo/+archi ... m-embedded

@adilsongoliveira,
I'm doing exactly what is explained in the wiki to build Companion and it works.

Tchao

I have added the information about the alternative toolchain distribution point. Should make life much easier for the next person trying to compile OpenTX on 64 bit Linux.

[seagovernor]

The latest firmware version 1.99.5 was loaded in my Taranis radio. I found some bugs, I am reporting.
In telemetry page,
(1) in the low alarm and critical alarm of RxBatt the receiver max number are 6.83V. For two cell Lipo receiver it is too low, it need higher number like 7.4V.
(2) Variometer source has VSpd as default, but it should be Vario, I believe. There are no Vario option.
(3) Beeping sound when linked to X8R receiver.

[adilsongoliveira]

Quick update.
I forgot to add that I was able to compile opentx itself without any problem, I hit the compilation issue on companion only.
The problem with cmake was indeed the version. I'm using Mint 16 Petra which has cmake 2.8.11.2
I've made a few changes on CMakeList.txt as indicated here https://github.com/opentx/opentx/commit ... 8ee6796a3a and works fine now.
Thanks for the help

[bertrand35]

The latest firmware version 1.99.5 was loaded in my Taranis radio. I found some bugs, I am reporting.
In telemetry page,
(1) in the low alarm and critical alarm of RxBatt the receiver max number are 6.83V. For two cell Lipo receiver it is too low, it need higher number like 7.4V.
(2) Variometer source has VSpd as default, but it should be Vario, I believe. There are no Vario option.
(3) Beeping sound when linked to X8R receiver.

(1) is now fixed:
https://github.com/opentx/opentx/commit ... 8457478933

(2) VSpd means vertical speed, where is the problem?

(3) prompts will be in next voice packs (english and french);
https://github.com/opentx/opentx/commit ... 3c24f4890e

[seagovernor]

Thank you bertrand
For vario source there are some difference between companion and radio :
In companion as option, Alti, Alt+, A1, A2
in radio, Vspd, A1, A2, dTE.

[seagovernor]

I just add a few more sound such as A3_org.wav, A3_red.wav, A4_orgt.wav, A4_red.wav, rx_org.wav, rx_org.wav in system sound fold in my Taranis. There are some missing sound too 0110.wav etc in theKM_opentx sound pack, I just found.
When linked to X8R receiver, now it says A4 critical instead of the beeping sound.
I looked the telemetry page. A4 values is different to other A1, A2, and A3.

[bertrand35]

Which are your parameters on A4? If you don't want any alarm on A4, you just have to put 0.00V on all its range/alarm values