Goblin 570 eepe

[ArchmageAU]

Had a query from a user, so I thought I would share the information.

The setup is a Goblin 570 with a vbar pro. The issue was with tuning the tail gain.

To tune the tail gain you must set the gain to be controlled by the Aux channel in vstabi. Once the values are established, then they can be programmed into the banks.

I think the ESC is a Castle with governor mode (but I cannot be sure).

A Castle ESC Governor works at:
- 30% - Speed 1 - Throttle level -40 (= (30 * 2) - 100)
- 70% - Speed 2 - Throttle level +40 (= (70 * 2) - 100)
- 100% - Speed 3 - Throttle level +100 (= (100 * 2) - 100)

A Castle ESC also has auto-bailout. This means throttle hold can be greater than -100 (so hold needs it's own value), but cut should be -100 (this will disable auto-bailout and required to arm the ESC).

Attached is an eepe to allow control of the heli and tuning.

Features of the .eepe model.

- 3 Flight modes + Hold + Cut
- 3 DR/expo rates
- Timer once throttle above hold
- Voice alerts
- Auto max volume when hold released
- S2 level volume when hold engaged

The channel order is TERAGC, but this can be easily changed.

The travel adjusts are set for the requestors RX, but are easily changed.

Hold I moved from the original location to Switch F. If you like your hold on the right side (like me who started with Spektrum TX's), you can swap Switch H and Switch F like I have using the following process:

Originally Posted by btheli

Here's what I did:

http://www.rcgroups.com/forums/showt...0#post26467096

No soldering or lengthening wires. Worked perfect. ...

All switches are done in the Logical Switches section. This way the switch selections are done in only one place. If you change them, all functions change appropriately.

Switch F does throttle hold (set in LS1)

Switch E does the 3 flight modes (set in LS 2, 3 and 4)

Switch C down engages throttle cut, but only when hold is on. (set in LS 6)

Switch G does DR/expo rates (set in LS 10, 11 and 12)

Switch B down engages gyro override (set in LS 14). Gyro override makes gyro take the value of S1

Flight modes dependent on L1 (hold), L2 (normal), L3 (cruise), L4 (acro).

Timer dependent on Throttle channel output value over 25% (set in L7)

All model programming done in the Inputs panel. Inputs take the value of first qualifying value. Inputs created for Thr, Ail, Ele, Rud, Col and Gyr. Throttle and Collective based on throttle stick with notrim.

Mixes panel is reserved for use when channels need cross programming (none required in this model). Therefore all mixes are passthrough.

All Channels, Inputs, Flight Modes and Curves labeled.

In this model, Hold and Cut are the same value. The hold output level can be altered in Inputs if wanting to enable CC ESC auto-bailout.

Hope people find this useful. Please comment if you find any errors.

[Bladecpnitro]

I don't have a Goblin or Vbar but I'm going to download it and study it a bit to see how you have it all set up. Thanks for sharing and Happy landings!

[Bladecpnitro]

Hi Arch! I noticed after flipping through some of your settings that I can't play the sounds. Are those sounds available for download?

[ArchmageAU]

Originally Posted by Bladecpnitro

Hi Arch! I noticed after flipping through some of your settings that I can't play the sounds. Are those sounds available for download?

There are a number of default sounds for the Taranis for download (I use the Amber pack). https://www.rcgroups.com/forums/show...59&postcount=1

2.2 has a new SD to download which has more sounds again. http://downloads.open-tx.org/2.2/nightly/sdcard/

[Bladecpnitro]

Thanks Arch! I'll check out those sounds.

It took me a bit to figure out how you have everything mapped out and I'm starting to get the hang of it.

In the logical switches it seems when you place !L1 at the end of L2, L3 and L4, it makes L1 which is the Hold SF switch dominant over those FM's, Low L2, Med L3 and High L4 positions on SE switch. Is that right?

Also I noticed that L7 on SD which is the 2nd throttle hold doesn't work at all unless the 1st SF throttle hold is applied.

I couldn't figure out how the FM's were tied to the throttle and then I found where you have the FM selected in each corresponding throttle Input mix. Awesome!

Is there a reason why you do most of the real setup in the Input page?
Most I've seen is done in the mixer page, in fact thus far I've practically ignored the input page.

[ArchmageAU]

Originally Posted by Bladecpnitro

Thanks Arch! I'll check out those sounds.

It took me a bit to figure out how you have everything mapped out and I'm starting to get the hang of it.

In the logical switches it seems when you place !L1 at the end of L2, L3 and L4, it makes L1 which is the Hold SF switch dominant over those FM's, Low L2, Med L3 and High L4 positions on SE switch. Is that right?

Also I noticed that L7 on SD which is the 2nd throttle hold doesn't work at all unless the 1st SF throttle hold is applied.

I couldn't figure out how the FM's were tied to the throttle and then I found where you have the FM selected in each corresponding throttle Input mix. Awesome!

Is there a reason why you do most of the real setup in the Input page?
Most I've seen is done in the mixer page, in fact thus far I've practically ignored the input page.

Input page is the "pure" model. If you needed to do any complex mixing (like CCPM - or revo mixing (collective/rudder) or in aircraft with elevons) then this occurs in the mix page.

I use the mix page for things like rescue switch mixing out cyclics (very useful for a BD3SX FBL) or auto-bailout for non-auto bailout ESC's.

Output from he inputs are Throttle, Elevator, Aileron, Rudder, Gyro, Collective and any other pure input you want (like rescue, landing gear, lights, etc...). The mix page combines these pure inputs into channels. Channels adjusts the signals to match the RX and on-model systems.

L7 is "cut". This is used if L1 "hold" is not -100 to enable auto-bailout (on a castle ESC). Auto bailout allows motor to stop, but not go back to slow start (as you may need the motor to re-spool quickly if the auto is off track). "cut" is also needed if "hold" is not -100 to allow an esc to "arm" (allow to start). You will only ever want "cut" if "hold" is engaged. You will never want "cut" in flight.

Hope that all makes sense.

[Bladecpnitro]

Yes it all makes perfect sense!
Its really amazing what all can be done with OpenTX.
I don't know if I could ever go back to a TX with very limited programming.

[ArchmageAU]

Originally Posted by Bladecpnitro

Yes it all makes perfect sense!
Its really amazing what all can be done with OpenTX.
I don't know if I could ever go back to a TX with very limited programming.

I could never go back either.

I like doing the things with my Taranis that TX's 3x the price cannot do.

[JWeber]

I have a Horus, but I'm thinking of replacing it with the SE. The Taranis is so easy to make things happen on and fits in my hands so well. I could never go to anything else.

[ArchmageAU]

Originally Posted by JWeber

I have a Horus, but I'm thinking of replacing it with the SE. The Taranis is so easy to make things happen on and fits in my hands so well. I could never go to anything else.

I like the m9 gimbals for the SE, but I'm not a big fan of artwork cases.

I may look at getting some m9 gimbals for my Taranis (still using the stock ones).

[JWeber]

I agree about the graphics. Although the SE also get's you Horus quality switches and upgraded speaker and other common Taranis mods.

[Bladecpnitro]

Hey Archmage! I can't seem to download the Amber sound files for the Taranis at RCGroups. Maybe they don't have them up any longer.

And for some reason I don't seem to be able to open files that were created and saved on Windows with Companion in Ubuntu.

I just upgraded my Companion to 2.2 on my Ubuntu 17.04 installation.
Any idea why those files aren't usable?

[ArchmageAU]

Originally Posted by Bladecpnitro

Hey Archmage! I can't seem to download the Amber sound files for the Taranis at RCGroups. Maybe they don't have them up any longer.

And for some reason I don't seem to be able to open files that were created and saved on Windows with Companion in Ubuntu.

I just upgraded my Companion to 2.2 on my Ubuntu 17.04 installation.
Any idea why those files aren't usable?

Looks like the full amber pack is no longer at the download address.

Send me a PM with an email address and I can email it to you. It's 16.2Mb zip, so too big to put in an attachment to a post.

There are cut down amber packs (4.4mb) on the OpenTX download site:
http://www.open-tx.org/downloads

• Sound packs for OpenTX 2.0
• Sound packs for OpenTX 2.1
  

[Bladecpnitro]

Looks like in Companion9x 2.2 that inputs are now called sticks.
Does that mean that the TX also needs updating to work with 2.2?

[ArchmageAU]

Originally Posted by Bladecpnitro

Looks like in Companion9x 2.2 that inputs are now called sticks.
Does that mean that the TX also needs updating to work with 2.2?

Will work on your existing TX but you will need to update firmware.

There is also an update to the SD card.

Once you change to 2.2, changing back requires a restore of 2.1 firmware and a re-load of your pre-2.2 models (if you ever want to go back). 2.1 models can translate to 2.2, but 2.2 models cannot translate back to 2.1

If you switch to 2.2, test ALL your models work as expected. I have had parameters drop in translating from 2.1 to 2.2.

[Bladecpnitro]

Ok I might just stick with 2.1 a little while longer. At least past the weekend. Thats probably why my Ubuntu's 2.2 won't read any of the previously created eepm files

[Bladecpnitro]

Hey Arch! I'm having a hard time understanding how your G switch is working for DR and Expo.

I see that you've added some trim in the outputs page but I don't see how its affecting the channels.

I see you have it assigned to work in all flight modes but I don't see how it affects the channels.

I'm used to using curves for expo and have not used DR since the Blade SR days.

[ArchmageAU]

Originally Posted by Bladecpnitro

Hey Arch! I'm having a hard time understanding how your G switch is working for DR and Expo.

I see that you've added some trim in the outputs page but I don't see how its affecting the channels.

I see you have it assigned to work in all flight modes but I don't see how it affects the channels.

I'm used to using curves for expo and have not used DR since the Blade SR days.

Logical switches 10, 11 and 12 are used for DR switching (low, medium and high).



Dependent on the mode the "weight" and expo can be changed. In the model posted all 3 modes for Ail, Ele and Rud were DR 100/Expo 0.



The outputs (servos) were for the member that asked originally. The outputs for each channel should match the wiring and the sensitivity of the FBL controller (so 100% input result should equal 100% on channel input on the FBL system).

The mixes just make sure the inputs (logical model) map to the right outputs.

Hope that helps explain it a bit.

[Bladecpnitro]

So if you adjust the weight it will adjust DR for each switch position.

If you want expo do you use curves?

[ArchmageAU]

Originally Posted by Bladecpnitro

So if you adjust the weight it will adjust DR for each switch position.

If you want expo do you use curves?

As you said. DR is done by adjusting weight.

Expo has a value already (it's 0), you can adjust that. No need to use a curve. (You could use a curve if you really wanted, but I find expo is enough.)