> Look .. we don't need to necessarily rediscover a wheel ..
> There are some "remote control units" available on the market .. checked in
> gliders already ..
> check this one out
> ".....After spending a number of months gathering pilot input regarding
> shape and determining a method for accommodating the wide range of stick
> diameters, we are in the process of finalizing our design for a machine
> carved wooden handle mounting the Remote Control keypad (including an
> additional button for PTT) to the stick for convenient in-flight use. We
> expect to have the design finalized and to make this part available through
> our dealers by July 2009. Retrofitting for the Stick Handle Remote is
> possible at any time after installing the ClearNav, and having the backup
> handheld remote is recommended to enable use in other gliders or at home with
> the power adapter.
> OR Remote Control, Stick Mount Module Only
> $135.00....
> fromTim's Mara Wings&Wheels ......
> http://www.wingsandwheels.com/clearnav_nk_clearnav_nielsen_kel.htm
>
> I am sure we can spend eons debating how many button .. knobs etc ... while
> we already have something working.
> Just a matter of assigning proper function to it .. or BETTER YET ...
> providing an INTERFACE WHEN I CAN MAP MY DESIRED FUNCTION to these buttons
> ... and this is what I would call PERFECT ..;-)
>
> Kris Cichon - KiloCharlie
I have a stick mounted set of buttons. Mine is just 4 buttons, while John
Wharingtons has I think 8, 4 way hat (joystick), up/down etc. But as you said,
there is lots of things you can already buy.
There is three parts to buttons in a Glider
* Physical buttons - these are what you mention above. They are only buttons,
not useful by themselves
* Electronic interface - how you get the buttons into the glider. This can be
done with some electronics already (e.g. I use a Vega, but there are plenty of
other choices). Other choices are a IOIO- this is a good choice if you have it
already since you don't have to buy or run anything else at the same time.
* Software mappings - the button you pressed gets turned into some form of code
(either NMEA or a HID button) and you have in your software what it does.
There are people working on the middle bit using the IOIO boards, since they
are so versatile for buttons and serial ports and charging your android
devices. You would then in theory wire in any button.
The last bit, mapping to any function you like, already exists. Unfortunately
it is a text file to edit. Making an interface is possible, but could be time
consuming for limited use. Another way would be to write a web interface to
create the file for you. Or just ask on the list and someone (like me) can help
you write the config file.
Scott
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Xcsoar-user mailing list
Xcsoar-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xcsoar-user
