[NSRCA-discussion] How many transmitters let you add your own features?
Peter Vogel
vogel.peter at gmail.com
Fri Dec 30 14:57:06 AKST 2016
Mixes, etc. are still done the traditional way (though you can see all of
the mix data in a JSON file, I wouldn't trust myself editing that
directly!) this scripting capability enables you to add whole new features
the brilliant guys at Jeti hadn't gotten around to yet. Especially since
when you are coding just for your needs you don't need to handle all the
different ways other people might want to use it (you can make the code
available to others for them to modify as they see fit). I made the
discharged flightpack warning system nice and all-purpose because it was
easy to do. I just wrote another one to give me a gentle haptic "bump" on
the throttle stick when I hit my preferred cruise setting (since that's not
right at half stick) and that one I made much less generic because I
couldn't figure out quickly how to correlate a proportional control the
user selects to the gimbal on which that control lives, so I stuck with
causing the bump on the left stick.
Next step is something more complex, defining a new control that can be
mixed into an existing control to enable an asymmetric servo delay, to slow
the movement of a surface only when that surface was deflected fully and is
returning to center. I haven't fully thought that one through yet.
Peter+
On Fri, Dec 30, 2016 at 3:35 PM, Keith Black via NSRCA-discussion <
nsrca-discussion at lists.nsrca.org> wrote:
> Wow, love the ability to view the code and logic in a text editor like
> that. Being able to see expos, mixes, etc. at a glance and easily edit
> would be awesome.
>
> Keith
>
> On Fri, Dec 30, 2016 at 5:26 PM, Vogel, Peter via NSRCA-discussion <
> nsrca-discussion at lists.nsrca.org> wrote:
>
>> Jeti's DC-24 added Lua scripting capability so you can add your own
>> "native" features to the radio easily. They just released a SW update so
>> you can do the same with the DC and DS-16s too.
>>
>> I played with it a bit today. This is AMAZING. I've written a Lua script
>> here: https://github.com/pvogel1967/Lua-Apps/tree/master/Discharge
>> d%20Flightpack for warning if you arm your plane with a discharged
>> flight pack (happens more often than I would like in competition). While it
>> *is* possible to get the same functionality from the native features of the
>> radio, it burns a sequencer and several logical switches. It's even more
>> complicated to do if you have an ESC with a BEC and you use a separate RX
>> backup pack as many of us flying competition do! As an added bonus I added
>> the ability to have it announce the model name when the TX is powered up or
>> a model is selected. While this is ostensibly a distinct function it seemed
>> silly to burn another one of 10 script slots just for announcing the name
>> of the model. See the readme in the above directory for details of the app.
>>
>> Everything you see on the screen below is a result of this script being
>> enabled for this model.
>>
>> [image: Image]
>>
>> Get Outlook for iOS
>>
>>
>> Get Outlook for iOS <https://aka.ms/o0ukef>
>>
>>
>> _______________________________________________
>> NSRCA-discussion mailing list
>> NSRCA-discussion at lists.nsrca.org
>> http://lists.nsrca.org/mailman/listinfo/nsrca-discussion
>>
>
>
> _______________________________________________
> NSRCA-discussion mailing list
> NSRCA-discussion at lists.nsrca.org
> http://lists.nsrca.org/mailman/listinfo/nsrca-discussion
>
--
Director, Fixed Wing Flight Training
Santa Clara County Model Aircraft Skypark
Associate Vice President, Academy of Model Aeronautics District X
Treasurer, National Society of Radio Control Aerobatics (NSRCA)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.nsrca.org/pipermail/nsrca-discussion/attachments/20161230/6f740b99/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Image.png
Type: image/jpeg
Size: 63851 bytes
Desc: not available
URL: <http://lists.nsrca.org/pipermail/nsrca-discussion/attachments/20161230/6f740b99/attachment.jpe>
More information about the NSRCA-discussion
mailing list