I use either Hitec or futaba digitals. I tried the cheap servo's and they would burn out in little use. Spend a little extra now and save money and heartache in the long run! :)
Printable View
I use either Hitec or futaba digitals. I tried the cheap servo's and they would burn out in little use. Spend a little extra now and save money and heartache in the long run! :)
Jack
Post deleted, as earlier enquiry was to 737NUT and not general
David
Hmmm... My Etronix Servo isn't *perfectly* accurate (just did 10 Tests in a row going from min to max deflection, biggest error margin was 9 servo values, avarage was only 1 or two away from the correct value), however, it is wonderful at not burning. I have constantly thrashed it past the limits and it never fails to work!
Furthermore, I've had my SIOC script slightly (after avaraging the results out from that 10-test run), here's the final result:
EDIT: And, as usual, it doesn't work. SIOC is completely messed up, after starting it turns the Servo to position "55", despite 197 being defined in the script. It also doesn't move in time with the Sim.Code:// *****************************************************************************
// * Config_SIOC ver 3.7B1 - By Manolo Vélez - www.opencockpits.com
// *****************************************************************************
// * FileName : ASIgauge.txt
// * Date : 7/3/2010
Var 0000, Value 0, name Intialization // Set servo positions
{
&Servo3 = 197
}
Var 9003, name IAS, Link FSUIPC_IN, Offset $02BC, Length 4 // IAS from Sim
{
L0 = DIV &IAS 128
L1 = L0 * 1.653 // Calculate Servo Slope
L2 = L1 + 114.35 // Calculate Servo Intercept
V9000 = L2
}
Var 9000, name Servo3, Link USB_SERVOS, Output 3, PosL 197, PosC 445, PosR 693, Type 2 // ASI gauge
I managed to achieve *limited* sucess with the script. At low speeds, my real life ASI is showing way too fast. At high speeds, it is the opposite, showing speeds way to slow. Pretty much the same problem as last time, and I can't figure out why, because that script looks okay?
Heya 737NUT,
Could you tell me which is your favourite Servo out of all of your Digital Dutabas and Hitecs?
I just want one that is reliable and powerful, and that will work well with USBServos Software & Card.
Thanks in advance,
Jack
Like I told you before: You may delete Var 0000 completely... It has no use. The init value of 197 will immediately be overwritten by the value of the IAS FSUIPC offset.
Tip (just syntax): write
or even better:Code:&Servo3 = L2
NicoCode:&Servo3 = L1 + 114.35
Hi Nico,
I have deleted Var0000.
Still, what is the use of defining the Left, Mid and Right points of the Servo? SIOC doesn't seem to use them. For example, it thinks 0 IAS means position 0 on the servo, despite me defining 197 in this following line:
Code:Var 9000, name Servo3, Link USB_SERVOS, Output 3, PosL 210, PosC 473, PosR 735, Type 2 // ASI gauge
I know nothing about Servo's.
Note that yesterday I have add a SIOC presentation (from Opencockpits) to the SIOC page of my website. I recommend to print this colourful file, take a break (or even a holiday) and study this document over and over again (from over to cover) ;-)
Have a good Summer!
Nico
Thanks Nico, I will have a peek at that presentation!
Strangely, my Servo is consistently off by 15Knots. I may try offsetting the SIOC script by 15Knots to compensate for this.
Here is what i will be using from now on, it's their new design and pot life is increased tremendously!
http://www.servocity.com/html/hs-5045hb_servo.html
Until you get a good servo in there it will be impossible to code correctly! The servo must go to the same spot every time.
Hello everyone,
I have some good news.
I have managed to find the fault behind the mysterious Servo problem. It was actually one of the gears that was to blame! It had come loose of the Servo arm and was waivering about trying to obey the SIOC rules. A quick re-application of the gear seems to have fixed the problem.
After further testing with FSX, the biggest error margin was about 7Knots, usually only about 3-5Knots, and other times SPOT ON. I can live with these small errors, especially because in real life ASIs do vibrate about and aren't always 100% accurate.
So, after long, long last, I can declare this project a sucess and move on to the next gauge... The VSI!
Thanks for everyone who contributed, I wish you a happy summer,
Until the VSI...
Bye! (thread can be closed!)