So I’ve built my own trim wheel based on an arduino leonardo with rotary potmeter and gear so it needs 9 revolutions to fully turn the potmeter. All is working, however I don’t see the trim wheel in the cockpit moving. I needed to set for up as a slider. When it was setup as axis it would only register it as a key press when the potmeter hit the end of it’s reach. I’ve tried it in the da40ng and cessna 152. When I use the mouse to trim the virtual wheel it’s obviously moving. This matters a lot to me cause I’m flying in VR so I have no idea of the position of the trim wheel.
Any advice here? Thanks
It’s a normal behaviour.
An encoder act like two buttons so they should not be used on an axis. (except if you use external apps like FSUIPC or others transforming buttons presses on axis movements).
For axes you should use a potentiometer, not an encoder.
But if using a potentiometer for trimming sounds to be the solution, it induce problems when deactivating the A/P, you instantanely change from the trim position the A/P used to the one the potentiometer was set before.
Look at this vid, a little bit long but explains all clearly.
Ah I am using a potmeter not an encoder, my bad. But with the potmeter on an analog input on the arduino it registers only the end of the rotation of the potmeter when it is setup on a rotary axis in arduino. But as mentioned I solved it by setting it up to a slider axis.
My main issue is that the virtual trimwheel 8n the cockpit is not moving when I move my physical trim wheel so I don’t have a clue what the position is, because I’m in VR. Any thoughts there?
I have no knowledge with Arduino, but I guess the problem is in the fact your pot is not recognized as a reguler axis in MSFS ans you had to find a workaround.
If your elevator axis is bounded as it in your controllers settings the trimwheel in the cockpit should move.
Or a VR problem ?
Anyway, if you solved the display problem, the issue of using a pot for trimming will still occurs.
My reading of the original post is that it is set up as a regular axis in MSFS. I don’t know whether using any other device as an axis for trim causes this problem (no visible feedback on the trim wheel in cockpit) or not, but I do know that as mentioned earlier in this thread using an axis for trim is problematic when using a plane with an autopilot, for the separate reason that your input device does not move in response to the autopilot’s control of the trim and can cause a massive “jump” when deactivating the autopilot, so it’s recommended to not use an axis for trim.
(My dream trim wheel device would be motor-driven by feedback via reading the trim position via SimConnect. In theory setting the input position via SimConnect should cause the wheel in-cockpit to move, as it seems to work with my trim up/down control buttons on the Honeycomb Bravo as I’ve configured them with spad.next)
I have a Flight Velocity Trim Wheel, and the cockpit view does show the virtual trim wheel responding to my inputs. I use it regularly but never really checked to see if it does show graphically until this thread. I tested it on a stock C152 Aerobat.