Neil,
I think you may be misunderstanding the starting premise of this
"exercise". The idea was not to create a feedback or computer controlled
situation where the computer controls the tx.
The idea was to take the numerical and small screen interface of the
Tx's programming screen and "enhance" that to make it easier to understand.
That is a huge advantage. I use an example from aviation between 2 Garmin
GPS units. The 430 and 530. The functionality of the units is identical,
the difference is screen size. Now, yes the map is bigger, but the main
reason people swap to the larger 530 is to have more information displayed
on one screen.
I can also give an example from a MPX 4000 that I would love to see. I
use the 4000 because I am familiar with it, but any higher end tx would
probably benefit as well. Anyway, on the 4000 you have 2 distinct sets of
parameters. The servos and the controls. The servos are set up to be
"limits". You set the maximum limit that the servo can physically move.
The controls then are linked/mixed into each servo to control it (up to the
limits). This can be VERY confusing as the setups are on totally different
screens. Also, since everything is really a mixer, it is also difficult to
see all the relationships between the controls and servos.
It would be great to have a graphical display of the control and what
servo(s) it controls. Also displaying the max/min values. This gets REALLY
confusing when you set up special functions such as the reverse differential
or switch functions. Seeing it is much easier than trying to imagine it and
flip through the menus.
I don't think this is for field progrmaming though! I would use it at
home for basic setup and then go from there. Field tuning would be done
with the normal functions.
Now...if it could "expand" on some of the programming...that would be
nice. I keep hearing of ways to "unlock" certain functionality that
different tx's has (like heli CCPM on older radios) and the like. I suspect
that they are much more "adaptable" than we are allowed to play with. That
would be nice....
Jason Werner
----- Original Message -----
From: "Neil Gillies" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, January 10, 2003 4:45 AM
Subject: [RCSE] RE: GUI programming for TX's - More
> Hi All
>
> This is really a question to Arne, and to simplify what he is attempting
to
> attain.
>
> Q: Please explain EXACTLY how the following information is returned to the
> Tx to enable the PC/Mac program to make any SENSIBLE (for sensible, read
> usable) mechanical adjustments/mixing arrangements to the flying surfaces
> (or throttle/cyclic pitch etc even :-)
>
> 1 The linkage position on the servo arm
> 2 The linkage position on the surface horn
> 3 The linkage position on any intervening bellcranks (if any)
> 4 The amount of physical throw at the trailing edge of the surface
> 5 The direction the surface moves for a given signal
> 6 The above assumes that all the throws are linear - what happens when
there
> is a mechanical offset on the centreline of the horn/output arms giving a
> non-linear bias - how would this be achieved?
>
> In my stupidity, I just can't see what use ANY interaction on the computer
> would offer without all of the above information being available - or at
> least the final relationship between servo and surface for each channel.
>
> Not having any positional feedback from a surface (from say some form of
> encoder attached to the surface) negates any possibility of making it
> automatic - not to mention that there would still be the problem of
getting
> the positional feedback to the transmitter - perhaps a telemetry downlink?
>
> This is all completely achievable using fairly simple technology of
course.
>
> Please don't take this post the wrong way, I AM genuinely interested - I
too
> hate the dreaded Tx interfaces ! I am a systems engineer who still finds
it
> difficult to program my JVC VHS !!
>
> There is of course a possibility that I have completely missed the point
of
> the exercise and that all you want to do is have the PC/Mac as an
extension
> to the Tx (ie control the Tx in real time via the serial interface). This
is
> of course easily possible I assume - just emulate another 3030 in buddy
box
> mode. Not sure that you wouldn't forget how to program the tx at the field
> 'though when you needed to give the crow a little tweak :-))
>
> I think I might just repeat that it would be better to grab a copy of Mike
> Shellim's excellent online 3030 manual and spend the time reading :-)))
>
> Best regards
>
> Neil
>
>
>
___________________________________________________________________________
>
> Neil D. Gillies Tel: +44
(0)1383-823489
> iGull Technologies Fax: +44
(0)8707-059481
> 11 River View Mobile: +44
(0)771-4330793
> Dalgety Bay, Fife
[EMAIL PROTECTED]
> Scotland KY11 9YE
http://www.igull.co.uk
>
http://www.sea-gull.demon.co.uk
>
> RCSE-List facilities provided by Model Airplane News. Send "subscribe"
and "unsubscribe" requests to [EMAIL PROTECTED] Please note that
subscribe and unsubscribe messages must be sent in text only format with
MIME turned off.
RCSE-List facilities provided by Model Airplane News. Send "subscribe" and
"unsubscribe" requests to [EMAIL PROTECTED] Please note that subscribe and
unsubscribe messages must be sent in text only format with MIME turned off.
