More flight modes

[GoogleCodeExporter]

Any chance of 5 flight modes like my Multiplex Evo ?

Original issue reported on code.google.com by th9...@gmail.com on 24 Jul 2011 at 11:56

[GoogleCodeExporter]

Do you mean adding one extra flight mode or 2 extra flight modes (we now have 1 
default and 3 extras)? I do agree if it's needed!
It will use some extra EEPROM (for each flight mode we need to store a switch, 
and 4 trim positions = 5 bytes)

Also, is there any possibility to give a name to each flight mode on your 
Multiplex? If yes how many chars?

Original comment by bson...@gmail.com on 25 Jul 2011 at 3:13

[GoogleCodeExporter]

My apologies the Evo only has four flight modes, I am remembering 5 because I 
always wished it had 5. I was meaning 1 default plus 4 extras.

You can name the flight modes on the Evo up to 8 chars are allowed. I think it 
would be nice to be able to name the flight modes including the default mode on 
our firmware to.

This maybe a comment for another issue but had you thought about implementing 
transition delays between the flight modes ? So the servos don't snap to new 
positions when changing flight modes.

Cam.

Original comment by th9...@gmail.com on 25 Jul 2011 at 3:50

[GoogleCodeExporter]

It makes sense, no need for a new issue, I prefer having only one EEPROM format 
change.
So:
- one more flight mode
- flight mode names, including the default one
- transition delays, do you mean a "slow" function rather than a delay? or both?

Original comment by bson...@gmail.com on 25 Jul 2011 at 6:00

[GoogleCodeExporter]

Yes a slow function, bad English from and Englishman, sorry ! The idea is so 
the servos have a smooth transition between the flight modes, preferably with 
an adjustable transition period.

The Evo allows a transition period of 1-2-3-4 secs, same for all flight modes. 
Although some sets allow different periods for different flight modes, this 
might be an idea if it's not too much hassle. 

Original comment by th9...@gmail.com on 25 Jul 2011 at 6:16

[GoogleCodeExporter]

In MIXERS screen we have a configurable 0-15s delay UP(4bits) + DOWN(4bits). 
Then it would take 1 extra byte to have the same capacity in flight modes.

Original comment by bson...@gmail.com on 25 Jul 2011 at 7:25

[GoogleCodeExporter]

Of course I meant SLOW UP + SLOW DOWN!

Original comment by bson...@gmail.com on 25 Jul 2011 at 9:09

[GoogleCodeExporter]

Technical problem... there is no space left on the screen for 8 chars! 6 seems 
to me the maximum, unless we also want to change the stock lcd!

Here is the struct I have in mind right now:

typedef struct t_FlightPhaseData {
  int8_t trim[4];  // ...
  int8_t swtch;    // swtch of phase[0] is the trimSw
  char name[6];
  uint8_t speedUp:4;
  uint8_t speedDown:4;
} __attribute__((packed)) FlightPhaseData;

Original comment by bson...@gmail.com on 25 Jul 2011 at 9:52

[GoogleCodeExporter]

Yes, perfect. Just what I had in mind. 6 chars it will have to be then !

Speed, Land, Therm, Launch, Std, Hover, 3D, Auto, all 6 chars or under.

Original comment by th9...@gmail.com on 25 Jul 2011 at 10:07

[GoogleCodeExporter]

Yes -- let's change the stock LCD to full colour TFT at 360dpi (Apple retna), 
yummie! We can sell an optional magnifying lens to mount over it! OK, maybe not 
just yet. :P [We now return you to your regular programme ...]

So, total five flights modes, yes? Default plus 4 more. Wow. I can see I'm 
going to have to build a new model plane or too so that I can show all this 
stuff off at the club! :D

Original comment by gru...@gmail.com on 26 Jul 2011 at 2:31

• Changed state: Accepted

[GoogleCodeExporter]

Original comment by gru...@gmail.com on 26 Jul 2011 at 2:32

• Changed state: Started

[GoogleCodeExporter]

Original comment by gru...@gmail.com on 26 Jul 2011 at 2:41

[GoogleCodeExporter]

Maybe should have asked at the start, but am I correct in saying Bertrand that 
you are planning to make D/R and EXPO flight mode switchable ?

Original comment by th9...@gmail.com on 26 Jul 2011 at 6:48

[GoogleCodeExporter]

I am not sure to understand the requirement ;)

If you mean that each flight mode SHOULD have its own DR/EXPOS settings, then 
answer is yes (it's also possible to have an EXPO/DR setting for all phases 
except one).

And same answer for MIXERS

Original comment by bson...@gmail.com on 26 Jul 2011 at 9:42

[GoogleCodeExporter]

I was confused by the DR/Expo vs. flight mode thing too Cam. Very confused. But 
I finally sat down and played with what Bertrand has done last night. I'm used 
to DR/Expo being tied to flight modes. I expected to have separate settings for 
each flight mode, as standard.

But Bertrand has done it more in keeping with the way things work in the mixer. 
It's considerably more complex to what I'm used to (just like the mixer system) 
but very much more flexible as well.

basically, you can add multiple lines if DR/Expo settings. Each line can be 
assigned a flight mode under which is is operative. Each line also has the 
"switch" setting, just as before. The switch appears to override the flight 
mode.

The only down side of this approach, far as I can see, is that when you want to 
separate your dual rates out onto one switch and your flight-mode expos onto 
another -- then you have to create two DX/Expo lines for each flight mode 
(phase).

There are presently 14 rows available. I used 9 (well 6, if you exclude std. 
ELE/RUD/THR lines) just to get three aileron expo settings (one per flight 
phase) and with DR set separately on the AIL switch.

Really, it's too hard to explain like this. You have to actually play with it. 
:D

Original comment by gru...@gmail.com on 26 Jul 2011 at 11:30

[GoogleCodeExporter]

Holy crap it's already in there, (embarrassed face on), when did that sneak in 
? Didn't spot that in the commit log. Right off for a play, (happy face on).

Original comment by th9...@gmail.com on 26 Jul 2011 at 11:37

[GoogleCodeExporter]

"The switch appears to override the flight mode.": not exactly, it's an AND, 
both are important!

Original comment by bson...@gmail.com on 26 Jul 2011 at 11:41

[GoogleCodeExporter]

Oh, OK. "AND". I might be confused with the standard mixer lines. Pretty sure 
the switch overrides flight phase in there??

Original comment by gru...@gmail.com on 26 Jul 2011 at 11:43

[GoogleCodeExporter]

I understand the comment now, move left (+) while selecting a flight phase and 
you get !FP1 not flight phase. Genius !

As you were Bertrand.

Original comment by th9...@gmail.com on 26 Jul 2011 at 11:45

[GoogleCodeExporter]

It should not also in MIXER screen, or it's a bug!

Original comment by bson...@gmail.com on 26 Jul 2011 at 11:47

[GoogleCodeExporter]

Do you mean !FP1 should be unavailable in the MIXER screen ? Because it is 
available on my firmware r777. Seems like a good idea to leave in.

Original comment by th9...@gmail.com on 26 Jul 2011 at 11:56

[GoogleCodeExporter]

Thanks :)
The idea is not from me, but from thus with the -SWTCH concept
Should work in both EXPO/DR and MIXER screen of course (my previous comment was 
an answer to comment 17)
New commit for flight modes coming to-morrow! Snapshots attached (hope they 
will)

Original comment by bson...@gmail.com on 27 Jul 2011 at 12:01

Attachments:

• snapshot_01.png
• snapshot_02.png
• snapshot_03.png

[GoogleCodeExporter]

Awesome, looks superbe ! Cannot wait.

Original comment by th9...@gmail.com on 27 Jul 2011 at 12:13

[GoogleCodeExporter]

Yes yes. All very good. But can we get on to the built-in hand warmer and 
coffee machine soon please? :P :P

Original comment by gru...@gmail.com on 27 Jul 2011 at 7:22

[GoogleCodeExporter]

You have to provide 220V from the hardware first :)

Original comment by bson...@gmail.com on 27 Jul 2011 at 7:39

[GoogleCodeExporter]

Cam! You're the hardware expert. We need 10 Amps at 220V out of V5. Make it so! 
:P (Perhaps a slot on the side to put the ampairs into, at the start of the 
day? Don't bother with liquid ones. They're too dangerous!)

Original comment by gru...@gmail.com on 27 Jul 2011 at 8:20

[GoogleCodeExporter]

OK => one more flight mode
OK => flight mode names, including the default one: done
IN PROGRESS => transition speed configurable

Original comment by bson...@gmail.com on 27 Jul 2011 at 6:55

[GoogleCodeExporter]

Off to have a play with it now, simply brilliant !

Not sure about the 220VAC, might have to steel some plutonium from Libyans, ask 
Doc. Brown ;)

Original comment by th9...@gmail.com on 27 Jul 2011 at 7:17

[GoogleCodeExporter]

Maybe we should just kidnap Doc. Brown and make him build us a quantum flux 
capacitor and stick it in a Ford Escort. Then we can simply travel to the 
future, to when we've already finished this project. Guess we'd have to knock 
off our other future selves, for safety. *shrug* (Hmmm... but if we leave for 
the future, before we get started on the V4 board... wouldn't that mean that we 
never finish it? Arrg!! Why is life so hard? :P)

Original comment by gru...@gmail.com on 27 Jul 2011 at 11:15

[GoogleCodeExporter]

Commited, with the smooth transition between phases. Which I have called "fade 
in" and "fade out".

In the same time is commited the extended trim feature which allows (if 
enabled) to have a trim range of [-500:500] instead of [-125:125] with a cost 
of 5 extra bytes in eeprom per model.

More tests needed.

Original comment by bson...@gmail.com on 16 Sep 2011 at 7:07

• Changed state: Fixed

[GoogleCodeExporter]

:D

Original comment by gru...@gmail.com on 17 Sep 2011 at 12:54

[GoogleCodeExporter]

Original comment by gru...@gmail.com on 23 Sep 2011 at 1:52

• Changed state: Verified