USBServos Software not working?

[Boeing 747 Flyer]

Jack,

how will you get the IAS value from FSUIPC if you don't start FSX?

You can't, I'm wodnering if there was a way to test the servo without starting FSX.

Regardless, I'd much rather get it working through the testing software first, for the primary reason I could burn the servo.

Also, for me to get SIOC working is a nightmare, I'm just keeping it simple to start with.

[deering]

Jack, input via IOCP Console is simple enough.

An off topic question for you if I may. At the end of your last thread, Nico supplied a script to get you AP led working. Did you spend some time to work out why that version worked while the previous version didn't?

[Boeing 747 Flyer]

Yes, a reduction of 4 to 3 variables (removing v1 and replacing with the pre-existing var 9000) worked.

Anyway, back on topic. The USBServos Software should work, so there is no need to use SIOC yet. That is the whole intnded purpose of USBServos Software.

As I said, setting up sioc.ini, mkaing SIOC work and ensuring the Servo doesn't burn out is too much for me. I will use USBServos first, that is the purpose of this thread.

[fordgt40]

Jack

You are correct, it is much better to use the testing software IOCards_test.exe. On the basis that you have a separate 5 volt supply, the device is recognised, the connections are correct and the appropriate radio button is selected - then if the servo does not follow movement commands from the slider or numeric input. then perhaps the servo should be retested though would that involve changing the connections again? Incidentally, what servo are you using?

David

[Boeing 747 Flyer]

Not sure of the model number right now, but can confirm it is an "Electonix" one, apparently very similar to the Hitec HS-55, but the wiring is identical to a JR one.

I will-triple-check the wire connections. It is because I had to swap the colouring around, so now they're all different colours, very dangerous & confusing, I'll probably revise the connections on Friday.

[deering]

Yes, a reduction of 4 to 3 variables (removing v1 and replacing with the pre-existing var 9000) worked.
.
.

..but, you glossed over the question of why it worked and if you'd spent any time figuring it out.

[iwik]

Jack,
you can check your board without fitting a servo and with no external P/S.
Do the following,
Place a 1000 ohm resistor in series with a LED.
Connect the Anode end of the combo to the center pin of say SERVO 1 connector and connect the cathode of the LED to Ground.
Run only the IOCards_test.exe.
Select servo 1 and adjust the slider,the led should glow bright at 1023 and dims as you go towards 0
Ive tried it on my one and it works ok.
This way you lessen the chance of destroying anything.
Hope this helps
Les

[Boeing 747 Flyer]

Hiya Iwik,

I will definitely try that after I've connected a different Servo, ensuring it is in correct configurtion for the card.

[Boeing 747 Flyer]

Okay guys, fantastic news. I have managed to sucessfully get the card working with USBServos Software. I have also found the values I want from the ASI, take a look:

FAR LEFT (ASI: 103Knots) - 250

FAR RIGHT (ASI: 375Knots) - 700

CENTRE (ASI: 225Knots) - 475

Assuming there is nothing wrong with those values, I am working on implementing it into a SIOC script. However, there are a few problems...

- First of all, I only want the ASI to "pick up" when the FSX ASI reaches 103Knots.

- Secondly, don't want the ASI to exceed 375Knots (700 Value), whilst it is capable of doing up to 400 Knots, I do not want to overstress the Servo. I take it this is where I implement the limiting factors into my SIOC scripts, but what if I exceed 375Knots? Does the ASI just "die"?

Thanks alot,

Jack (getting there!)

[fordgt40]

Jack

What was the reason why the servo did not work?

"I take it this is where I implement the limiting factors into my SIOC scripts" - yes, 737NUT gave you a snippet of SIOC code to achieve this in the previous thread

David