OpenTX - Nightly builds for pre-2.0 testing

[Koffi]

The sticky function does not always work (version 16th march). Sometimes it does work, sometimes not.

[Kilrah]

Discovered one slight issue when in usb mode on bootloader.
Do not unplug then turn off TX before usb has unmounted properly.
TX will stay in an on state.
To get out of this state battery needs to be removed or usb cable needs to be plugged in and then removed properly before trying to turn off.

Can't reproduce.
Radio staying on while USB is connected is intended. But if you turn the radio off, then disconnect the cable it does power off.
Works correctly as it always has in the firmware for me.

[Kilrah]

The sticky function does not always work (version 16th march). Sometimes it does work, sometimes not.

Useless report...
What does it do when it doesn't work? What's wrong? Any info about the circumstances in which it happens?

[Koffi]

I'd like to give further Information but I rarely can.

When programming and selecting the active line, the command should become bold, shouldn't it?

I'll try to give more Information soon.

[Kilrah]

When the logical switch is ON it is bold. When it is OFF it isn't.

[RightRudder]

I can't burn the mar 22 build to sky9x. I just burned r2940 no problem so I know it is not a driver issue, and I can read the flash no problem but every time I try to burn the v1.99 bin I get a SAM-BA error.

Any ideas?
Joe

Edit: This is with companion 1.52 r2381

[RightRudder]

I am slowly writing a wiki page for Lua scripts on OpenTX. It's here:
https://github.com/opentx/opentx/wiki/L ... -in-OpenTX

You will be able to download and run the classical snake game at the very end of the page ... in case you broke all your planes

Will it be possible to use telemetry values as inputs to Lua scripts? And will it be possible to use outputs from Lua scripts as input values in the mixer?

[rdeanchurch]

I can't burn the mar 22 build to sky9x. I just burned r2940 no problem so I know it is not a driver issue, and I can read the flash no problem but every time I try to burn the v1.99 bin I get a SAM-BA error.

Any ideas?
Joe

Edit: This is with companion 1.52 r2381

V1.99 is companion, not the firmware for the transmitter.

Look at
http://jenkins.open-tx.org/firmware/nig ... _01-48-09/

[RightRudder]

Why am I running V1.99 on my Taranis then? I downloaded both the sky and tarainis versions yesterday from the Mar 22 nightly build.

[Kilrah]

Versions are the same for both the firmware and companion from now on.

I can't burn the mar 22 build to sky9x.

I see the filesize for the sky9x binary is about the same as for the Taranis - which is too much to fit in the sky9x's chip. We probably have something wrong in the build script.

We haven't really taken care of sky9x yet, one thing at a time. We'll work to fix it once the Taranis is stable enough.

[RightRudder]

Versions are the same for both the firmware and companion from now on.

Does that mean they have to be the same to work together though? I burned the latest unstable Taranis FW using companion 1.52 so I am guessing the answer is no. Bertrand directed me to this thread for the solution to issue #169 (I raised on the old google code site) which was supposed to have been fixed long ago so I assumed the nightly build should be the one I need. Can you advise me otherwise?

Joe

[Kilrah]

You can use anything for flahsing the firmware as this is always done the same way, but yes you need to have matching versions to edit settings. So if you want to edit settings on the PC you need to install and use companion 1.99 too.
Companion 1.52 will just tell you the eeprom is invalid if you try to read it from an 1.99 radio.

[DarKHawK]

Well I was waiting to test joystick mode and its working great.

Tested on Windows 7
CH1 Y Axis
CH2 X Axis
CH3 Z Axis
CH4 X Rotation
CH5 Y Rotation
CH6 Z Rotation
CH7 Slider 1
CH8 Slider 2
CH9 Button 1
CH10 Button 2
CH11 Button 3
CH12 Button 4
Ch13 Button 5
CH14 Button 6
CH15 Button 7
CH16 Button 8

All works great.

I did notice that S3 is somehow linked to elevator (type s3 under hardware is set to none)
This affected using S3 in joystick mode when moving elevator S3 moves too.
This also affects center beep on elevator when 3 is enabled. (elevator beeps when not enabled when s3 is enabled)

Thanks

[dinamich]

I don't understand exactly what is your problem with S3. The S3 source is not available currently on Taranis, it will be additional potentiometer or multi-position switch on Taranis+.

Please elaborate your S3 problem, maybe there is another issue with it, one was recently fixed, see https://github.com/opentx/opentx/issues/813

[Kilrah]

I guess he has selected S3 in companion, it's currently available for selecting there. Just don't use it.

[Helle]

Hy Kilrah,

latest opentx1.99 from 24.03.2014 *.bin at Taranis

Stcky (German SRFF) is a SR- Flip-Flop funktion with one condition for Set and one for Reset

Now have testetd sticky funktion intensiv,
at companionV1.999x simulator and at linux simu
All works well, can set and reset as expected

But not at the opentx1.99 at Taranis(Version A) itself!

Maybe a problem of key bonuce?

Examples:
I can Set and Reset with the same key same position (SAup SAup) then I have the Toggle-Flip-Flop
I can Set and Reset with the same key but diff position (SAup SAdown)
I can Set and Reset with diff keys and positions SAup SBup)
or all combinations of it


helle

[Helle]

Hy Kilrah,

latest opentx1.99 from 24.03.2014 *.bin at Taranis

Stcky (German SRFF) is a SR- Flip-Flop funktion with one condition for Set and one for Reset

Now have testetd sticky funktion intensiv,
at companionV1.999x simulator and at linux simu
All works well, can set and reset as expected

But not at the opentx1.99 at Taranis(Version A) itself!

Maybe a problem of key bounce?

Examples:
I can Set and Reset with the same key same position (SAup SAup) then I have the Toggle-Flip-Flop
I can Set and Reset with the same key but diff position (SAup SAdown)
I can Set and Reset with diff keys and positions SAup SBup)
or all combinations of it


helle

[bertrand35]

There was a problem in the nightly builds script, the bins for sky9x are just the binaries from the previous nightly builds for Taranis ... I just fixed the scripts and removed all sky9x bins

[Koffi]

Hello together,

after I was quite happy about the FAS Offset function, unfortunately the mAh consumption still is not correct at all, although the current is perfectly calibrated at least up to 10A (my Multimeters range).

Now there´s left the voltage, which of course also influences the mAh calculation.

Is it possible to add an Offset function for FVAS, too?

Or could I choose FLVSs`cells voltage to use in the consumption calculation?

Last option is, that I´ve simply bad luck with my sensor, as most other users don´t report such strange issues...


Anyway, thank you for all your work and endless programming-hours;)

Koffi

[mstrens]

Hello together,

after I was quite happy about the FAS Offset function, unfortunately the mAh consumption still is not correct at all, although the current is perfectly calibrated at least up to 10A (my Multimeters range).

Now there´s left the voltage, which of course also influences the mAh calculation.
Koffi

I don't understand why you say that voltage influences the mAh calculation.

mAh is normally just the amp (= current) multiplied by a time (hour). Voltage does not matter.

[rilot]

On the topic of the FAS, can the Taranis now read values above 5100mAh for consumption when using the FAS-100? The current stable release tops out at 5100mAh which is an issue for me flying with 12000mAh LiPos.

[Koffi]

@mstrens
You may be right, i was a bit confused with voltage, mAH, current and power.

[MikeB]

On the topic of the FAS, can the Taranis now read values above 5100mAh for consumption when using the FAS-100? The current stable release tops out at 5100mAh which is an issue for me flying with 12000mAh LiPos.

I don't know if this works. I assume you are using a custom switch like:
a>x cnsp 5100
Now you could also try
a>b cnsp GV1
I'm not sure what you get with this. In my opinion, GV1 should be scaled in the same way the 'x' is above, that is count in steps of 20. So setting GV1 to 100, the switch should come on at a cnsp of 2000.
Worth a try, because if it works, setting GV1 to 500 would trip the switch at a cnsp of 10000.

Mike.

[bertrand35]

snapshot_02.png (1.77 KiB) Viewed 20126 times

[bertrand35]

snapshot_04.png (1.82 KiB) Viewed 20126 times

[lichtl]

Hi,

maybe I missed it somewhere but I was unable to figure out how to get the Taranis into Storage mode. I've tried to press Exit button while connecting but this doesn't seem to work.

[Kilrah]

Hold the aileron and rudder trims inwards while powering up.
We might want to change that, not really intuitive.

Sent via mobile

[MikeB]

I'm not sure anything else would be intuitive either. I chose something you also wouldn't do by accident.

Mike.

[bertrand35]

I just uploaded a companion installer in nightly builds directory

[Daedalus66]

I'm not sure anything else would be intuitive either. I chose something you also wouldn't do by accident.

Mike.

Trims towards the middle is easy to do, easy to remember. Takes just a slight contortion to get your fingers into position. Seems perfect to me. Please don't change. I can't think of anything that would be "intuitive" for a fairly arcane command like launch boot loader.

(Besides, I've learned it for the 9XR Pro and don't want something different for my Taranis )