openrcforums

Posted: **Tue Sep 02, 2014 5:11 pm**

The problem is that unlike all other panels SFs can have a different number of parameters, so the same logic can't be applied without becoming a mess.

Posted: **Tue Sep 02, 2014 5:31 pm**

I was afraid of that

I by myself already tried to modify that menu but to no success.

Only to show how the menu is setup in the moment and what I would like to get

Code: Select all

Switch  Override        CH1-16                    -100..100       activate
Switch  Trainer         Rud-Ail                                   activate
Switch  InstTrim                                                  activate
Switch  Reset           Tim1/Tim2/TimAll                          activate
Switch  Adjust          GVar1-5                   -100..100       activate
Switch  PlaySound                                  Bp1...Alarm    Repet.Time
Switch  PlayTrack                                 0-250/GV1-GV5   Repet.Time
Switch  PlayBoth                                  0/1-255/256     Repet.Time
Switch  PlayValue                                     AnyInput    Repet.Time
Switch  Vario
Switch  Haptic                                    0-3             Repet.Time
Switch  Backlight

I recognized, that it would be complicated, to, for all functions,
have the target in the first column as sometimes the 'target' is e.g. a track number

But something like this would be my proposal for a, to my opinion, more user friendly
menue. I have put the repetition time, where available, into the last column,
as it is kind of the final switch to activate the function.

Code: Select all

Trainer          Rud-Ail                                 Switch   activate
Reset            Tim1/Tim2/TimAll                        Switch   activate
Override        CH1-16                  -100..100        Switch   activate
Adjust           GVar1-5                 -100..100       Switch   activate
PlaySound      Bp1...Alarm 		                        Switch   Repet.Time
PlayTrack       0-250/GV1-GV5  		                    Switch   Repet.Time
PlayBoth        0/1-255/256    		                    Switch   Repet.Time
PlayValue       AnyInput       			                 Switch   Repet.Time
Haptic           0-3            			                Switch   Repet.Time
InstTrim                                                 Switch   activate
Vario                                                    Switch
Backlight                                                Switch

'Switch' is any available physical or logial switch

btw,
with PlayBoth, the last combination that is selectable is 255/256 but in reality 255/0 is played
This may be intentionally to be able to play Track0 with a switchDown condition, but then it should be named correctly as 255/0

Reinhard

Posted: **Tue Sep 02, 2014 5:57 pm**

I must say I really don't see the point of changing this, especially as it's been so since OpenTX exists. Maybe you prefer it like that, but thousands of people who like or are used to the current layout will be confused. Myself included.

And it would be tedious to implement as column positions will have to change for each function, while with the current order they can be fixed. And it won't be possible to keep it same for 9X and Taranis, etc...

Posted: **Tue Sep 02, 2014 8:38 pm**

ReSt wrote:Is this only my problem?

Probably yes

Thats ok, there obviously is no great interest for such a change.
And that was worth to find.

Thanks Kilrah

Reinhard

Posted: **Thu Sep 04, 2014 4:48 pm**

I found the .csv datas files logged with my PRO can't be displayed with Companion 2.0.8; I don't know the reason: my Win XP-PC, Companion, files badly recorded...
Anyone has succeed to play that files ?

MP

Posted: **Thu Sep 04, 2014 4:56 pm**

Hi,

michel49 wrote:I found the .csv datas files logged with my PRO can't be displayed with Companion 2.0.8

Put your file here so that we can test it.

Bye.

Posted: **Mon Sep 08, 2014 3:45 pm**

EASY_GLIDE-2014-08-27.csv: (189.72 KiB) Downloaded 546 times

Posted: **Mon Sep 08, 2014 4:54 pm**

Hi,

I've only logged data with a Taranis and your file headers do not match mine:

Your file:

Code: Select all

Time,Elapsed,Valid,RxRSSI,TxRSSI,A1,A2,AltB,AltG,Temp1,Temp2,RPM,Amps,Volts,mAH,TxBat,Vspd,RxV,Lat,Long,Fuel,SC1

Taranis working log:

Code: Select all

Date,Time,SWR,RSSI,A1,A2,A3,A4,GPS Date,GPS Time,Long,Lat,Course,GPS Speed(kts),GPS Alt,Baro Alt(m),Vertical Speed,Air Speed(kts),Temp1,Temp2,RPM,Fuel,Cell volts,Cell 1,Cell 2,Cell 3,Cell 4,Cell 5,Cell 6,Cell 7,Cell 8,Cell 9,Cell 10,Cell 11,Cell 12,Current,Consumption,Vfas,AccelX,AccelY,AccelZ,Rud,Ele,Thr,Ail,S1,S2,S3,LS,RS,SA,SB,SC,SD,SE,SF,SG,SH

I think it's the reason why Companion can't display it.

Bye.

Posted: **Mon Sep 08, 2014 5:53 pm**

That does not look like an OpenTX log. Companion won't support it.

Posted: **Tue Sep 16, 2014 9:49 am**

I discovered Companion play only the csv files logged with OpenTx, not the files logged with stockFW.

Thanks.

Posted: **Mon Oct 06, 2014 3:54 pm**

Why stutter in the Beep setting ?
[BBvideo 425,350]https://www.youtube.com/watch?v=cdTQY-z ... e=youtu.be[/BBvideo]
I not understand...

Posted: **Mon Oct 06, 2014 5:03 pm**

Delete sound file system\timer10.wav.

Posted: **Tue Oct 07, 2014 5:10 am**

Kilrah wrote:Delete sound file system\timer10.wav.

It's not going to miss the voice setting?

Posted: **Tue Oct 07, 2014 5:33 am**

No. That file is what's playing every second during the last 10 if present. It's not part of the new >2.0 voice packs.

Posted: **Tue Oct 07, 2014 5:36 am**

Kilrah wrote:No. That file is what's playing every second during the last 10 if present. It's not part of the new >2.0 voice packs.

Thank you, I'll try.

Posted: **Tue Oct 07, 2014 1:41 pm**

Thank you! Work fine!

Posted: **Mon Oct 20, 2014 4:17 pm**

OpenTX (Tanaris) Hungarian online description:
http://rc-miskolc.emiter.hu/rc-miskolc/ ... Itemid=220

Posted: **Tue Jan 06, 2015 6:48 pm**

I just downloaded the master branch as a .zip file and tried to compile it.
It failed looking for "nano.specs".

Mike.

Posted: **Wed Jan 07, 2015 1:05 am**

I recently have downloaded the master src via git and successfully compiled companion using Linux
Today I was able to compile the radio firmware using linux . I just did a regular make, so I compiled for a 9x binary. I do not have the tools installed to compile the taranis version.
Also searched the source for 'nano.specs' but did not find any file called *nano*. googling on that filename has me thinking it is related to the ARM toolchain, so that is probably why the 9x binary compiled for me

Posted: **Wed Jan 07, 2015 1:11 am**

Taken from:
https://github.com/opentx/opentx/wiki/O ... structions

A word of warning 2014-06-26

Things have recently changed in the build files that have broken the environment described below. These instructions no longer work to set up a working environment for several variants of the firmware.

Use Linux instead.

Posted: **Wed Jan 07, 2015 6:00 am**

MikeB wrote:I just downloaded the master branch as a .zip file and tried to compile it.
It failed looking for "nano.specs".

Mike.

I made that change, it is now a default to link with newlib nano library. You can disable this by using NANO=NO make commandline option. Which os does this? Which toolchain?

Posted: **Wed Jan 07, 2015 9:23 am**

I had the same problem with my "usual" compiler on Win (Yagarto toolchain, gcc 4.7.2), and even NANO=NO isn't good, as the bootloader still tries to build with nano and fails.

You probably have an outdated compiler. The latest release of the 4.7 branch (4.7.4, which we're using for OpenTX) works fine.
https://launchpad.net/gcc-arm-embedded/ ... -q2-update

Posted: **Wed Jan 07, 2015 10:03 am**

Compiling for Taranis/Taranis Plus on Windows 7 64-bit using Yagarto GCC ARM, probably 4.7.2.

Mike.

Posted: **Wed Jan 07, 2015 10:05 am**

I still maintain the bootloader should NOT be part of the build. It should be a completely separate build and not require changing except to add new features.

Mike.

Posted: **Wed Jan 07, 2015 2:12 pm**

Building for the PLUS using the MASTER branch and NANO=NO, I now have a built and running version, however, the splash screen and some other bitmaps are not correct. *.lbm files were built as part of the build process, including splash_taranis.lbm.
The build command I used was:
make PCB=TARANIS PCBREV=REVPLUS NANO=NO

I checked the build used the img2lbm.py file from the util directory downloaded as part of the master.zip file.

Mike.

Edit: Just built for a standard Taranis, same image problem.
Edit2: I just used Companion 1.52, read the splash screen from the FrSky PLUS official firmware (it displayed on the PC badly) and put that into openTx.bin I built. This then displayed correctly on the radio. It seems the img2lbm.py in the master/src/util directory doesn't produce the correct .lbm file.

Posted: **Wed Jan 07, 2015 10:46 pm**

Did you do a 'make clean' before?

Posted: **Wed Jan 07, 2015 10:55 pm**

Not specifically, but it did make all the .lbm files as they were not in the bitmaps directory.
I'll try with a make clean.

Mike.

Posted: **Wed Jan 07, 2015 11:08 pm**

That breaks the build completely, it goes off to build the bootloader and fails badly:

arm-none-eabi-gcc: error: ./startup_stm32f2xx.o: No such file or directory
arm-none-eabi-gcc: error: ./system_stm32f2xx.o: No such file or directory
arm-none-eabi-gcc: error: ./stm32f2xx_rcc.o: No such file or directory
arm-none-eabi-gcc: error: ./stm32f2xx_gpio.o: No such file or directory
arm-none-eabi-gcc: error: ./stm32f2xx_spi.o: No such file or directory
arm-none-eabi-gcc: error: ./misc.o: No such file or directory
arm-none-eabi-gcc: error: ./usb_core.o: No such file or directory
arm-none-eabi-gcc: error: ./usb_dcd.o: No such file or directory
arm-none-eabi-gcc: error: ./usb_dcd_int.o: No such file or directory
arm-none-eabi-gcc: error: ./usbd_core.o: No such file or directory
arm-none-eabi-gcc: error: ./usbd_ioreq.o: No such file or directory
arm-none-eabi-gcc: error: ./usbd_req.o: No such file or directory
arm-none-eabi-gcc: error: ./usbd_desc.o: No such file or directory
arm-none-eabi-gcc: error: ./usb_bsp.o: No such file or directory
arm-none-eabi-gcc: error: ./usb_driver.o: No such file or directory
arm-none-eabi-gcc: error: ./pwr_driver.o: No such file or directory
arm-none-eabi-gcc: error: nano.specs: No such file or directory
make[1]: *** [bootloader_ramBoot.elf] Error 1
make[1]: Leaving directory `C:/Data/C/opentx/Master/src/bootloader'
make: *** [bootloader/bootloader_ramBoot.bin] Error 2

Mike.

Posted: **Wed Jan 07, 2015 11:20 pm**

Those object files appear to be in their source file directories!

Mike.

Posted: **Thu Jan 08, 2015 7:09 am**

Mike, which Python do you have installed, there is an issue with Python 3 that was fixed in next branch, but not on the master https://github.com/opentx/opentx/issues/1907 This might affect your splash screen generation.

Anyway I just did a test, downloaded zip of master branch from github, issued your command

Code: Select all

make PCB=TARANIS REV=REVPLUS NANO=NO

and had no problems. But I am no Linux.

Code: Select all

$ md5sum bitmaps/splash_taranis.*
110b39e72d27ed8df8ae64311af101c6  bitmaps/splash_taranis.lbm
e446ddeb0c64326efccefd0db33585d5  bitmaps/splash_taranis.png

openrcforums

OpenTX 2.0.0

Re: OpenTX 2.0.0

Re: OpenTX 2.0.0

Re: OpenTX 2.0.0

Re: OpenTX 2.0.0

Re: OpenTX 2.0.0

Re: OpenTX 2.0.0

Re: OpenTX 2.0.0

Re: OpenTX 2.0.0

Re: OpenTX 2.0.0

Re: OpenTX 2.0.0

Re: OpenTX 2.0.0

Re: OpenTX 2.0.0

Re: OpenTX 2.0.0

Re: OpenTX 2.0.0

Re: OpenTX 2.0.0

Re: OpenTX 2.0.0

Re: OpenTX 2.0.0

Re: OpenTX 2.0.0

Re: OpenTX 2.0.0

Re: OpenTX 2.0.0

Re: OpenTX 2.0.0

Re: OpenTX 2.0.0

Re: OpenTX 2.0.0

Re: OpenTX 2.0.0

Re: OpenTX 2.0.0

Re: OpenTX 2.0.0

Re: OpenTX 2.0.0

Re: OpenTX 2.0.0

Re: OpenTX 2.0.0

Re: OpenTX 2.0.0