Signaling is in the trunk...

News, Setup, Compiling, Flashing, Development

Signaling is in the trunk...

Postby Max » Thu Apr 11, 2013 9:21 pm

... and there was much rejoicing! :mrgreen:

A revamped version of Menno's signaling functionality has finally been incorporated into the main code base. Many thanks to Menno for putting this together and making it more customizable for us! We'll upload a compiled hex file ASAP.

There are no docs and no GUI for setting this up yet, so here it goes. 3 new parameters have been created:

SIG_LED_1_PRT
SIG_LED_2_PRT
SIG_BEEP_PRT

You can see/set these in the Onboard Parameters window in QGC. As you might expect, these control which ports your signaling devices are attached to. Set them to zero to disable (default), or 1 though 14 to correspond to the "M" ports on AQ board.

If you have a piezo speaker (w/out internal freq. generator) then you can put a minus sign in front of the SIG_BEEP_PRT value (eg. -13). This will generate the necessary wave for driving the speaker (@ 2KHz by default).

Please see Menno's original instructions for information about hooking up LEDs. A buzzer/speaker is hooked up by connecting its positive lead to the AQ signal pin, and ground to ground pin of the same port. Piezo devices generate strong magnetic fields when active and should be placed well away from the FC.

The signaling light and beeper patterns (described below) can be altered by modifying the code. In the future we want to make this easier to configure, perhaps by using a file on the SD card to load custom patterns. But for now you'll have to re-compile to change those. Check at the top of signaling.c for the current pattern setup and comments about how it works.

Here are the current signaling patterns:
Code: Select all
Startup:
    1 short beep per detected battery cell;
    Followed by one longer "ready" beep;

Arming: one beep;
Disarming: two beeps;

Flight modes/status:

1 (Disarmed - no GPS fix)    Led 1: fast flashing, Led 2: off
2 (Disarmed - GPS fix)       Led 1: slow flashing (1Hz), Led 2: off
3 (Armed)                    Led 1: On, Led 2: Off
4 (Flying)                   Led 1: long on, Led 2: off
5 (Alt hold)                 Led 1: On, Led 2: slow flashing (2Hz)
6 (Pos hold)                 Led 1: On, Led 2: On
7 (Mission)                  Led 1: On, Led 2: slow flashing (1Hz)
8 (DVH)                      Led 1: On, Led 2: fast flashing (5Hz)
9 (Low Batt 1)               Led 1 & Led 2 alternating slow flashing (1Hz);
                             Beep: 2 short + long pause;
10 (Radio Loss 1/Low Batt 2) Led 1 & Led 2 alternating fast flashing (5Hz);
                             Beep: 1 long, pause, 1 long, shorter pause;
11 (Radio Loss 2)            Led 1 & Led 2 alternating fast flashing (5Hz);
                             Beep: 1 long + 1 short, 2x per second;

The low battery signals are activated in both armed and disarmed modes.


Enjoy! And please let us know how it's working out for you.

Cheers,
-Max
Max
 
Posts: 2814
Joined: Mon Aug 13, 2012 9:45 pm
Location: Near Ithaca, NY, USA

Re: Signaling is in the trunk...

Postby fred_fr » Thu Apr 11, 2013 9:54 pm

It's a very good news

thanks

fred
fred
fred_fr
 
Posts: 75
Joined: Tue Aug 28, 2012 10:13 am
Location: france, Caluire et Cuire

Re: Signaling is in the trunk...

Postby kinderkram » Fri Apr 12, 2013 10:04 am

Thx Menno & Max!
Very nice to see it in the code - finally...

One thing I don't get: what's the difference between "on" (armed) and "long on" (flying) for LED1? :?
kinderkram
 
Posts: 2911
Joined: Fri Jun 22, 2012 7:47 am

Re: Signaling is in the trunk...

Postby leopold1 » Fri Apr 12, 2013 10:26 am

Nice,

When will it be in the compiled section for download?
leopold1
 
Posts: 311
Joined: Tue Jul 31, 2012 11:43 pm
Location: Belgium

Re: Signaling is in the trunk...

Postby Max » Fri Apr 12, 2013 3:12 pm

kinderkram wrote:One thing I don't get: what's the difference between "on" (armed) and "long on" (flying) for LED1? :?


What, that's not clear enough? :P A "long on" in this case means on for 800ms and then off for 200ms, then repeat. Yea so maybe that can be described better... :)


Compiled AQ firmware v6.7 r100 has been posted to our downloads area.

Emphasis on experimental and BETA :!:

-Max
Max
 
Posts: 2814
Joined: Mon Aug 13, 2012 9:45 pm
Location: Near Ithaca, NY, USA

Re: Signaling is in the trunk...

Postby skew » Sun Apr 14, 2013 12:33 pm

Got to try out new signaling nice improvement. I love the GPS lock signal it was always a pain to see the blue led in direct sun now its a non issue. Its mission day 70f 5-10mph wind sunny! Time to burn some electrons while sitting in a chair sipping a beverage watching my AQ fly :)
skew
 
Posts: 181
Joined: Sun Oct 14, 2012 1:30 am
Location: Morehead, Ky

Re: Signaling is in the trunk...

Postby Ecky » Sun Apr 14, 2013 7:25 pm

Works fine! Included the optional beeping for arming an disarming too,
works also fine.

Great job, thanks for implementing. Have now to consider whether solution
i will use -> included signaling or MavToHott :(

Greatings
Christian
Ecky
 
Posts: 70
Joined: Wed Nov 21, 2012 11:11 am
Location: Germany, Bonn

Re: Signaling is in the trunk...

Postby Ecky » Mon Apr 15, 2013 6:45 pm

Is there a possibility to do some RGB 5050 works :?:

Is it possible that the "Radio Loss 1/2" dosent work with Graupner Hott?
Perhaps something to configure before it works?
-> OK watched the code, Radio Loss is only detected during flight?


Greatings
Christian
Ecky
 
Posts: 70
Joined: Wed Nov 21, 2012 11:11 am
Location: Germany, Bonn

Re: Signaling is in the trunk...

Postby Ruffio » Thu Apr 18, 2013 10:52 pm

It is realy grate improvement but I have some suggestions.
Most of important befor fly in my opinion is:
- do we have GPS fix
- is FC armed
I tested this FW with only one Led 1 - it is all what is necessary and only one port is used.
My suggestion is to change default flashing for 1st led:
Code: Select all
1 (Disarmed - no GPS fix)    Led 1: fast flashing (not rady to fly)
2 (Disarmed - GPS fix)       Led 1: off (ready to fly)
3 (Armed)                    Led 1: On

Rest of status it little useful, a specially for Led2.
May be important is to use beeper in connection with battery state but who flyes close enough to hear beeper.
Ruffio
 
Posts: 73
Joined: Sun Nov 18, 2012 9:43 pm
Location: Poland

Re: Signaling is in the trunk...

Postby joebar.rc » Fri Apr 19, 2013 6:07 am

You can change or create any pattern you like in the signaling.c file. Every position is 0.1s and 1 is on, 0 is off :)

And couldn't live without the led2 status, but its up to you if you will use it..

Menno
joebar.rc
 
Posts: 1084
Joined: Fri Jun 22, 2012 8:59 am
Location: The netherlands

Next

Return to AQ Firmware

Who is online

Users browsing this forum: No registered users and 2 guests

cron