Gear sequencer in 12S

Hi folks
First of all, greetings from good old Germany and many many THX´s for the brilliant work of the guys behind the DEVIATION project.
For my purpose it´s been the best decision I ´ve ever made. I run the 12S( V5.0.0) for Heli´s ; 4flap gliders and 2 EDF jets.


Now I have started a new project and for this plane I need a kind of sequencer for the gear and the doors.

I have tried it myself by using delay functions n´stuff but no success.

It should work like this:

Assigned is Switch GEAR1/0 and Ch6 ; Ch7; Ch8
-Switch GEAR1
-Landing beacon ON /Ch6
-Delay 3sec.
-Gear doors open /Ch7
-Delay 2 sec.
-Gear out /Ch8
-Delay 2 sec.
-Gear doors close again /Ch7

Switch GEAR0 should reverse the sequence.

Has anybody a clue how to bring this in my DEVO12S.

Regards
Achim

Good evening from good old Germany

I can't seem to get delay to work in the emulator and I do not have my devo at hand, but from theory could work like this:

Channel 6: Complex mixer (2 pages)
Page 1: switch=none; mux=replace; src=Gear1; curve type=min/max with value=-99; scale=100; offset=0
Page 2: switch=none; mux=delay; src=none; curve=fixed; scale=125
-> immediately switch on lights, when turning back to gear0 delay switching lights off by roughly 7 seconds

Virt1: Complex mixer (2 pages)
Page 1: switch=none; mux=replace; src=Gear1; curve type=13 point (-100;-100;100;100;100;100;100;100;100;100;100;-100;-100)
Page 2: switch=none; mux=delay; src=none; curve=fixed; scale=125
-> Virtual Channel for Landing Gear transition

Channel 7: Simple mixer
src=Virt1; curve=min/max (value= -95) scale=100; offset=0;
-> actual steering of landing gear doors from virt1 - I don’t know about soft servo transition or anything else needed on this channel, but in separating the transition flag to virt1 you can do anything with the channel itself. Right now it would be basically on/off.

Channel 8: Complex mixer (2 pages)
Page 1: switch=none; mux=replace; src = gear1; curve type=min/max (value=0); scale=100; offset=0
Page 2: switch=none; mux=delay; src=none; curve=fixed; scale=125
-> extend/retract landing in the middle of the sequence.

Es gilt wie immer keine Gewähr.

Hi Moeder
THX for your quick response.

I´ll try it this afternoon and I let you know the result.

Right now I tried it with the EMU but the behave is the same as you mentioned.
No visible delay.
Might be the EMU is not “real” enough for such functions?

Talk to you later.

By the way. A short story around this project.
A pal of mine came to me two days ago and I told him about my struggle.
He is owner of a (holy) GRAUPNER MC26/HoTT.
Now his words.
“Of course! GRAUPNER has such a function. That’s normal!
If you would have decided for a high quality system in the past you wouldn’t have this problem now “

Now I’m in a kind of competition with him.

I NEED HIS FACE IN THE MUD. OK?

So all help would be appreciated.

Cheers
Achim

Time for OpenTX and Lua script...
opentx.gitbooks.io/opentx-2-2-lua-refere...unction_scripts.html

Hi aMax

TARANIS is awesome!

One of my flying buddy´s has a X9.

Do they use LINUX ?

I have visited an exhibition weeks ago here in Germany and I have seen the new HORUS X12D there.
It´s a freaky high end “flying computer „but nothing for old dudes like me.
Did you know it contains a redundant backup system for transmission?

Would be surely nice to have such scripts in DEVIATION .

Cheers
Achim

Sorry, I don´t know much about the Horus, this is not my target.
What do you mean by redundant backup? Double receivers are possible or just a main receiver and a second as satellit (RX8R & RX8 /or XM+)

I am an old dude as well and have been a long time a Futaba guy..( Futaba/Graupner/Multiplex was the only choice not to be exotic).
After several long breaks in the hobby, I startet new with Devo/Deviation & 2.4ghz world in 2014.
I like the free programming a lot, but sometimes something is missing as an input for a function
( e.g rssi a source and redirecting to a free channel for an OSD).
So I went the complete route with the new QX7 and compared to the Devo,I think programming is easy as well, but with more options.

For your stimulation read this, an (old) solution for your task.
rcsettings.com/index.php/viewdownload/3-...uencing-using-opentx
openrcforums.com/forum/viewtopic.php?f=38&t=487

Happy flying.

Hi aMax

Pretty nice solution. (As far as I can understand the CODE).
I know OpenTX is a foxy firmware but I have to use different protocols like WLTOY and MJxQ (E010).
Am I right? OpenTx can only support DSM2/X ? (Except for Frsky)

If yes, I can´t go this way.
I have installed the 4in1 module and need a suitable firmware for it.


Cheers
Achim

We've looked into doing scripts for DeviationTx, but there just isn't enough interest to justify doing it.

OpenTx can do pretty much any protocol that deviation can do. The TH9X it started on as well as the Taranis both have an external module bay. The DIY Tx module project uses hardware based on the deviation multimodule board, except with a beefier MCU that can run protocols directly instead of just switching between them. Protocols get ported both ways between the two projects. The "other" 4-in-1 module you find on banggood is the hardware for this project.

When you talk about "redundant backup transmitters", are you talking about the transmitter having two rf modules? The internal one that's FrSky only, and the one in the external module bay? I haven't heard about that being used for backup, just extra channels. So with FrSky hardware, you get 32 channels (16 from each transmitter). It also allows for the interesting possibility of taking an aircraft with an all-in-one flight/controller/receiver board, and then adding a second Rx using a different protocol to control payload hardware like a gimbal or camera, even if the original design doesn't provide channels for them. Again, something we've discussed doing for deviation, but there's not enough interest to justify the work.

AN1610 wrote: Hi aMax

Pretty nice solution. (As far as I can understand the CODE).
I know OpenTX is a foxy firmware but I have to use different protocols like WLTOY and MJxQ (E010).
Am I right? OpenTx can only support DSM2/X ? (Except for Frsky)

If yes, I can´t go this way.
I have installed the 4in1 module and need a suitable firmware for it.


Cheers
Achim

This is my second Devo7e ......with FrskyD/X,full telemetry, DSMX; Devo, both Flysky protocoles and a NRF. for the JXD.

static.rcgroups.net/forums/attachments/5...163-170-module_F.jpg
static.rcgroups.net/forums/attachments/5...2164-37-module_B.jpg

The multi-purpose gang...
static.rcgroups.net/forums/attachments/5...247-126-DSCI2428.jpg

But having a small size devo7e with one antenna doing all this fancy stuff is always impressing people

Good evening friends

!!!!!!!VICTORY!!!!!!!!

I´ve Got´m !!!!

Yes it´s true. I have found a solution to pie on the GRAUPNER carpet.
I go to win the competition with my fellow. I´m pretty sure.

The initial idea is based on Moeders hints but as I tried it with the TX this evening it didn´t worked.
But the point is, now I´ve had a sample how to use virtual channels without source assignment.
I always thought this is illegal or useless.
It works like a timer and generates an analog ramp. Right?
What I have found now is much better than the GRAUPNER system.
I have modified the INI file to make it fit for my purpose.
Additionally I can now modify the speed of each assigned channel. Each channel of the sequencer chain can move with his own speed. This is brilliant for scale models.
The number of assigned channels can be increased up to the limits of your TX channels.

I have attached the INI as a sample.
Pls. try it and let me know your thoughts.

I´m sure OpenTX is a high performance base but I cannot pop over.
I have spend a sh** lot of coins to erect a teacher/ student system with two DEVO 12S.
Important is my problem is solved and might be a template for other DEVO user.

Many THX for your assistance

Cheers
Achim



[channel6]
template=simple
[mixer]
src=Virt1
dest=Ch6
curvetype=min/max
points=-98

[channel7]
template=simple
[mixer]
src=Virt1
dest=Ch7
curvetype=7point
points=-100,-100,100,100,100,-100,-100

[channel8]
template=simple
[mixer]
src=Virt1
dest=Ch8
curvetype=13point
points=-100,-100,-100,-100,-100,-50,0,50,100,100,100,100,100

[virtchan1]
name=Virt1
template=complex
[mixer]
src=GEAR1
dest=Virt1
usetrim=0
[mixer]
src=AIL
dest=Virt1
scalar=125
usetrim=0
muxtype=delay
curvetype=fixed

Might be bit off topic, but I find this thread also pretty interesting on advanced use of deviation;

It describes basically, generate a servo tester.
www.deviationtx.com/forum/7-development/...rs-to-channels#29092


I think we should put more generic templates by default, with a description in our standard builds......

Hi dear Fernandez

Definitely yes. I’m sure such special tutorials or templates are very helpful.
And I can tell from my own history with deviation.
Is there a place where we can store such things?
Just with a headline and a small description and attachment.
Search function is sometimes hard going.

I´m a little bit proud that I could offer a small piece of work to make DEVIATION more popular and convenient.
I´m far away from being so brilliant like our developers here but I try to do what I can.


Best regards
Achim

Well, how about we add a category to the Wiki (or a chapter to the manual) containing popular configuration examples?

edit: Glad I could point you in the right direction with my theoretical solution

You definitely did.
That’s what I like here in the Forum.
Combined knowledge without trash statements.

Very nice.

I think the WIKI is the right palce .


@Admin: What do you think?

Regards
Achim

The wiki seems right for me as well. It's open for everyone IIRC, so go ahead and add a category. We already have www.deviationtx.com/wiki/model_config for model specific configs, but I guess it would be useful to also have some general examples like sticky throttle hold, delaying actions etc.

Where in NRW will I be able to see the sequencer in action, BTW?

The forums also have disadvantages compared to the wiki. Most notable is that only the original author can edit the post, so if they lose interest for some reason, it will get obsolete and nobody can fix it. The amount of time I spent helping people who had gone wrong following outdated forum or blog posts is why I pushed for the Wiki around the 5.0 release time. Seems to be working really well.

A link to a forum thread for discussion would be a good idea. Similarly, a link from the forum thread to the wiki entry to help people find it is a good idea.

Hi friends

I´m not keen on do things complicate as much as possible.
A simple way is the best solution.
So I would quote for MWM´s solution.
Linkage from FORUM to WIKI.

Thanks to all.

Cheers
Achim