|
Post by terrydew on Apr 1, 2016 14:38:22 GMT
Hi Mark
I watched your video number 11 where you discussed the changes to the trim wheel. I also purchased your book on building. I am interested in doing this mod as it might help with using Fsforce with my Iris yoke. I understand the part about soldering to the two points to pickup the optical pluse signal. What I am unclear about is what you did with the two wires on the other end. It sounded like you plugged them into a switch input board as a regular switch? How did you detect the direction of the wheel? Is one wire clockwise and the other counterclockwise with a third ground wire? Do you think any switch input board would work or does it have to be a rotary encoder board input?
Thanks terry
|
|
|
Post by MarkH on Apr 1, 2016 17:25:09 GMT
Hi Terry. You are not the first to point out that I missed a bit of info there! In fact I didn't realise at the time and it just worked so I never thought any more about it... The two wires you solder on here are the signal wires, so they go into two adjacent inputs of a Leo Bodnar board, which you can set to interpret the pulses the encoder sends. Connected this way it acts just like two separate switches, one for each direction of the wheel. Now in principle I should also have taken a ground wire from somewhere on the circuit board and connected it to one of the Bodnar board's GND inputs but I didn't do this. But as the wheel is still plugged into a USB socket, and likewise the Bodnar board, I am assuming that they share a common ground this way. By the way, before you go hacking the hardware you might want to try it in software using FSUIPC. I didn't discover this until after I had done the hardware hack, so I haven't tried it. I would be interested to hear how you get on if you try it.
|
|
|
Post by terrydew on Apr 2, 2016 14:45:22 GMT
Hi Mark
Interesting I will give that a try. I think your hardware solution might be better but we will see. Focusing on Fsforce I am not sure that Fsforce will "intercept an offset/event" like it will key presses? My guess is it will not. I am not a programmer but I will try to see if that lula script could be modified to send key press rather than event.
I am using go-flight gear and I have one of there dio boards for switch contacts. Not sure it will pick up the pulses. Does the board you use have software that allows you to tell it that a input is pulsed?
Thanks for the input. I am glad I found your forum. Terry
|
|
|
Post by MarkH on Apr 2, 2016 16:27:18 GMT
Oh yes, FS Force. I don't know, you 'd need to try it. You can certainly send keypresses if you need to - use ipc.keypress() to do it. The interface boards I use are designed to recognise encoders - look here for details. I'm not familiar with the GoFlight boards, sorry.
|
|
|
Post by terrydew on Apr 2, 2016 16:27:25 GMT
Hi Mark The software method did not work. I had the same small range issues as per this thread. forum.simflight.com/topic/76357-trim-wheel-saitek-fsuipc/Back to hardware. I found more info on the Bodnar board and it looks like he does indeed have a rotary encoder software to be used with his board. If you can confirm that you had to use that software then I will need another type of board. Thanks Terry
|
|
|
Post by terrydew on Apr 2, 2016 16:31:29 GMT
Sorry cross post. I didn't see your reply until I posted last. I will try the key press method but not hopeful it will change range problem. I think I am spending 1 or 2 hours of tinkering for every 10 minutes I fly. Not sure which I enjoy more. Thanks again Terry
|
|
|
Post by terrydew on Apr 5, 2016 21:22:24 GMT
Hi Mark
After trying the software approach with a couple of different software, I gave up because the range kept shifting. I bought a bodnar board and did what you did. Works great.
Thanks for the idea. Terry
|
|
|
Post by MarkH on Apr 6, 2016 6:34:47 GMT
I bought a bodnar board and did what you did. Works great. Phew, glad it worked out!
|
|
MattS
Almost Aviator
Posts: 27
|
Post by MattS on Mar 6, 2017 23:37:08 GMT
So are you saying that there is not a fix in FSUIPC for the issue, and the only option is the hardware bypass? I have a few extra inputs on my Bodnar board and I'm seriously thinking of doing this. Those 2 inputs on the Bodnar board are setup as rotary encoders? Also, just to confirm do you need a ground from the trim wheel board or will plugging in the USB effectively bypass this? Thanks!
|
|
|
Post by MarkH on Mar 7, 2017 7:35:37 GMT
So are you saying that there is not a fix in FSUIPC for the issue, and the only option is the hardware bypass? I have a few extra inputs on my Bodnar board and I'm seriously thinking of doing this. Those 2 inputs on the Bodnar board are setup as rotary encoders? Also, just to confirm do you need a ground from the trim wheel board or will plugging in the USB effectively bypass this? Thanks! My setup just has the two wires from the encoder and is plugged into the USB, so I am assuming the USB provides the ground. Anyway, it works fine whatever the explanation! And yes, the input are set up as rotary encoders (so they have to be adjacent inputs - B1/B2, B3/B4, etc.) I have not tried the FSUIPC method so can't comment.
|
|