I’m using the trim wheel on the logitech multipanel through spad.next and it works perfectly.
The trim wheel itself is just a rotary encoder and I think that this is much better than an analog pot mapped to to trim axis since in this way, when the AP change the aircraft trim, you have a discrepancy between the trim settings in the sim and the phisical axis position that, if the pot is a little noisy, leads to a fight between the AP and the pot itself causing some of the AP malfunctions we have seen since release.
regarding the slowliness reportet when using a rotary encoder this is my setting in spad.next
<Event BoundTo="MULTIPANEL_PITCHTRIM">
<EventDefinitions>
<EventDefinition Trigger="NOSEUP">
<EventActions>
<EventActionChangeValue TargetDataDefinition="SIMCONNECT:ELEVATOR TRIM POSITION" Value="0.01" ValueOperation="Increment" />
</EventActions>
<Options>
<Option Key="ACCEL_MAX" Value="20" />
<Option Key="ACCEL_THRESHOLD" Value="3" />
<Option Key="ACCEL_MULTIPLIER" Value="3" />
<Option Key="ACCEL_TIMEOUT" Value="500" />
</Options>
</EventDefinition>
<EventDefinition Trigger="NOSEDOWN">
<EventActions>
<EventActionChangeValue TargetDataDefinition="SIMCONNECT:ELEVATOR TRIM POSITION" Value="0.01" ValueOperation="Decrement" />
</EventActions>
</EventDefinition>
</EventDefinitions>
<Options>
<Option Key="SENSITIVITY" Value="50" ValueType="System.Double" />
<Option Key="LINEFACTOR" Value="1638" ValueType="System.Double" />
</Options>
</Event>
where the 0.01 in the “SIMCONNECT:ELEVATOR TRIM POSITION” Value=“0.01” ValueOperation=“Increment” is expressed in angle radiants thanks to @RoboGreg 