problem with rudder trim implementation.

[mslim]

UPDATE: It seems like this problem only manifests on Ant's T-28's I was using for testing. The rudder trims seem to work on most, if not all, of my other aircraft. Also the rudder trims work but are reversed on the MilViz DHC-2.

 

I recently upgraded to the latest FSUIPC for P3D4.5 and was trying to implement the rocker switch on the TM Hotas X as a rudder trim axis.

I have tried 10 ways from Sunday but I still am doing something wrong. Some of you forum members may immediately spot my problem.

Any suggestions or corrections would be immensely appreciated.

Best,

Slim

[Axes]
PollInterval=10
RangeRepeatRate=10
0=AX,256,D,1,0,0,0    -{ DIRECT: Aileron }-
1=AY,256,D,2,0,0,0    -{ DIRECT: Elevator }-
2=AZ,256,D,4,0,0,0    -{ DIRECT: Throttle }-
3=AR,1
4=AR,BR,-6966,-387,x32000C04,x3FFF0040    -{ Entering=offset sword increment, offset 0C04 (Incr=64, Limit=16383) }-
5=AR,BR,-16384,-6966,x32000C04,x3FFF0080    -{ Entering=offset sword increment, offset 0C04 (Incr=128, Limit=16383) }-
6=AR,BR,387,6966,x42000C04,xC0010040    -{ Entering=offset sword decrement, offset 0C04 (Decr=64, Limit=-16383) }-
7=AR,BR,6966,16383,x42000C04,xC0010080    -{ Entering=offset sword decrement, offset 0C04 (Decr=128, Limit=-16383) }-
8=BX,256,D,7,0,0,0    -{ DIRECT: LeftBrake }-
9=BY,256,D,8,0,0,0    -{ DIRECT: RightBrake }-
10=BR,256,D,3,0,0,0    -{ DIRECT: Rudder }-

 

FSUIPC6.zip

[John Dowson]

10 hours ago, mslim said:

I recently upgraded to the latest FSUIPC for P3D4.5 and was trying to implement the rocker switch on the TM Hotas X as a rudder trim axis.

Is the rocker switch an axis then? I am not sure how that works - I would expect a rocker to trigger buttons...

Your ini file is quite strange as you only have the letter assignments under [JoyNames] and no lines with the joystick ids - did you remove those?

10 hours ago, mslim said:

UPDATE: It seems like this problem only manifests on Ant's T-28's I was using for testing. The rudder trims seem to work on most, if not all, of my other aircraft. Also the rudder trims work but are reversed on the MilViz DHC-2.

For the MilViz DHC-2, as you are using inc/dec controls on offset 0C04 for the rudder trim, create a specific profile for this aircraft and switch around the controls, so perform the decrements in the range you are currently performing the increments and vice versa.

For Ant's T-28's, check what the rudder trim in the aircraft is using by logging events and also set logging for offset 0C04 as S16. Then load the aircraft and adjust the rudder trim in the virtual cockpit and see what event (if any) is logged, and if the offset value changes (which I expect not). If the rudder controls Rudder Trim Left/Right are logged, you could try using those. Otherwise, if the Axis control Rudder Trim Set is logged, you could try assigning to that as an axis.
You can also attach your FSUIPC6.log and latest FSUIPC6.ini files here and I can take a look.

John

[mslim]

 

12 hours ago, John Dowson said:

Is the rocker switch an axis then? I am not sure how that works - I would expect a rocker to trigger buttons...

Yes. Jetblst showed me how to set that up in 2013.

Your ini file is quite strange as you only have the letter assignments under [JoyNames] and no lines with the joystick ids - did you remove those?

Yes I thought that since the joystick ids had been changed to letters rather than numbers in FSUIPC6, the numbered ids were a legacy from my FSUIPC4.ini that was no longer needed. I have since reinstated them.

For the MilViz DHC-2, as you are using inc/dec controls on offset 0C04 for the rudder trim, create a specific profile for this aircraft and switch around the controls, so perform the decrements in the range you are currently performing the increments and vice versa.

Understood.

For Ant's T-28's, check what the rudder trim in the aircraft is using by logging events and also set logging for offset 0C04 as S16. Then load the aircraft and adjust the rudder trim in the virtual cockpit and see what event (if any) is logged, and if the offset value changes (which I expect not). If the rudder controls Rudder Trim Left/Right are logged, you could try using those. Otherwise, if the Axis control Rudder Trim Set is logged, you could try assigning to that as an axis.
You can also attach your FSUIPC6.log and latest FSUIPC6.ini files here and I can take a look.

Log file uploaded

John

 

 

 

 

FSUIPC6.zip FSUIPC6log.zip

[John Dowson]

11 hours ago, mslim said:

Is the rocker switch an axis then? I am not sure how that works - I would expect a rocker to trigger buttons...

Yes. Jetblst showed me how to set that up in 2013.

Do you have a reference? Noy sure how you can get an axis value from a rocker switch,,,

11 hours ago, mslim said:

Your ini file is quite strange as you only have the letter assignments under [JoyNames] and no lines with the joystick ids - did you remove those?

Yes I thought that since the joystick ids had been changed to letters rather than numbers in FSUIPC6, the numbered ids were a legacy from my FSUIPC4.ini that was no longer needed. I have since reinstated them.

Both are needed, and you shouldn't add them manually - if you remove them, FSUIPC will automatically add the joystick id lines back. It cannot work without them.

11 hours ago, mslim said:

Log file uploaded

It is difficult to tell what is happening from such a large log file...its far easier for you to see what is logged in real-time (with the logging console window open) when you perform the action.  When you adjust the ridder trim in the VC, what do you see logged? Any controls? Does offset 0C04 change value, and if so through what range? When you move the rocker switch, do you also see offset 0C04 changing value?

[John Dowson]

I can see the rudder trim working in the Trojan T28D:

Quote

   612429 Aircraft="Trojan T28D 138232 Attack"
   662459 *** Exiting Axes option page ***
   711739 Monitor IPC:0C04 (S16) = 448
   712675 **** Restarting traffic scanning due to non-reception ****
   715281 IPC Offsets Control: Ctrl=x3200, Length=2, Offset=0C04, Param=x3FFF0040
   715296 Monitor IPC:0C04 (S16) = 512
   715296 SimRead: 0C04="RUDDER TRIM PCT"
            FLT64: 3.12500047893
   715359 IPC Offsets Control: Ctrl=x3200, Length=2, Offset=0C04, Param=x3FFF0080
   715374 Monitor IPC:0C04 (S16) = 640
   715374 SimRead: 0C04="RUDDER TRIM PCT"
            FLT64: 3.90625048039
   715468 IPC Offsets Control: Ctrl=x3200, Length=2, Offset=0C04, Param=x3FFF0080
   715483 Monitor IPC:0C04 (S16) = 768
   715483 SimRead: 0C04="RUDDER TRIM PCT"
            FLT64: 4.68750096241
   715561 IPC Offsets Control: Ctrl=x3200, Length=2, Offset=0C04, Param=x3FFF0080
   715577 Monitor IPC:0C04 (S16) = 896
   715577 SimRead: 0C04="RUDDER TRIM PCT"
            FLT64: 5.46875096386
   715671 IPC Offsets Control: Ctrl=x3200, Length=2, Offset=0C04, Param=x3FFF0080
   715686 Monitor IPC:0C04 (S16) = 1024
   715686 SimRead: 0C04="RUDDER TRIM PCT"
            FLT64: 6.25000096532
   715780 IPC Offsets Control: Ctrl=x3200, Length=2, Offset=0C04, Param=x3FFF0080
   715795 Monitor IPC:0C04 (S16) = 1152
   715795 SimRead: 0C04="RUDDER TRIM PCT"
            FLT64: 7.03125096677
   715936 IPC Offsets Control: Ctrl=x4200, Length=2, Offset=0C04, Param=xC0010040
   715951 Monitor IPC:0C04 (S16) = 1088
   715951 SimRead: 0C04="RUDDER TRIM PCT"
            FLT64: 6.64062596604
   715998 IPC Offsets Control: Ctrl=x4200, Length=2, Offset=0C04, Param=xC0010080
   716014 Monitor IPC:0C04 (S16) = 960
   716014 SimRead: 0C04="RUDDER TRIM PCT"
            FLT64: 5.85937596459
   716092 IPC Offsets Control: Ctrl=x4200, Length=2, Offset=0C04, Param=xC0010080
   716107 Monitor IPC:0C04 (S16) = 832
 

But when the offset is changed with the MilViz DHC2 Beaver loaded there was no monitoring of the offset, and only the offset control is logged:

Quote

   285280 IPC Offsets Control: Ctrl=x4200, Length=2, Offset=0C04, Param=x3FFF0040
   285342 IPC Offsets Control: Ctrl=x4200, Length=2, Offset=0C04, Param=x3FFF0080
   285436 IPC Offsets Control: Ctrl=x4200, Length=2, Offset=0C04, Param=x3FFF0080
   285545 IPC Offsets Control: Ctrl=x4200, Length=2, Offset=0C04, Param=x3FFF0080
   285638 IPC Offsets Control: Ctrl=x4200, Length=2, Offset=0C04, Param=x3FFF0080
   285748 IPC Offsets Control: Ctrl=x4200, Length=2, Offset=0C04, Param=x3FFF0080
   285872 IPC Offsets Control: Ctrl=x4200, Length=2, Offset=0C04, Param=x3FFF0080
   286465 IPC Offsets Control: Ctrl=x3200, Length=2, Offset=0C04, Param=xC0010040
   286512 IPC Offsets Control: Ctrl=x3200, Length=2, Offset=0C04, Param=xC0010080
   286637 IPC Offsets Control: Ctrl=x3200, Length=2, Offset=0C04, Param=xC0010080
   286746 IPC Offsets Control: Ctrl=x3200, Length=2, Offset=0C04, Param=xC0010080
   286855 IPC Offsets Control: Ctrl=x3200, Length=2, Offset=0C04, Param=xC0010080
   286855 IPC Offsets Control: Ctrl=x3200, Length=2, Offset=0C04, Param=xC0010040
   287214 IPC Offsets Control: Ctrl=x4200, Length=2, Offset=0C04, Param=x3FFF0040
   287261 IPC Offsets Control: Ctrl=x4200, Length=2, Offset=0C04, Param=x3FFF0080
   287370 IPC Offsets Control: Ctrl=x4200, Length=2, Offset=0C04, Param=x3FFF0080
   287464 IPC Offsets Control: Ctrl=x4200, Length=2, Offset=0C04, Param=x3FFF0080

It would be useful to see the offset monitoring with the MilViz DHC2 loaded, but I suspect that the simvar RUDDER TRIM PCT is not being used by that aircraft. You could try the axis control Rudder Trim Set, or the standard controls (i,.e, not axis controls) Rudder Trim Left and Rudder Trim Right in a specific profile for that aircraft. Still  not sure how the rocker is controlling an axis, but you could just change the offset control you are sending in the ranges to use those left/right trim controls instead. Otherwise, remove the axis range controls completely and try assigning the rocker directly to the Rudder Trim Set axis control.

John

[mslim]

Here is the discussion where jetblst showed me how to set up the rocker switch as a rudder trim axis. The reversed rudder settings are working as I wanted them to be in the DHC2. However it is actuating the trim, it is effective.  I may backup the .ini and try to to set the axis control to Rudder Trim Set and see what happens just for grins.

Here are the latest ini and log

FSUIPC6_log.zip FSUIPC6_ini.zip

[John Dowson]

1 hour ago, mslim said:

Here is the discussion where jetblst showed me how to set up the rocker switch as a rudder trim axis.

Ok, so the rocker is an actual axis - interesting.

1 hour ago, mslim said:

The reversed rudder settings are working as I wanted them to be in the DHC2. However it is actuating the trim, it is effective.

Ok, good.

1 hour ago, mslim said:

I may backup the .ini and try to to set the axis control to Rudder Trim Set and see what happens just for grins.

For the T-28? Did you try with the Rudder Trim Left and Rudder Trim Right controls?

1 hour ago, mslim said:

Here are the latest ini and log

Ok - will take a look at them tomorrow - finishing now...cheers,

John

[John Dowson]

Log file looks ok and just shows its working in the DHC2. I thought your issue was with the T-28, but you dom'y seem to be providing any of the requested logs for this, or reporting on the other controls I have asked you to try.

Btw. you should consider using aircraft substrings for your profile sections rather than the full aircraft name, with livery. Then you won't have to continually have to add your aircraft to a profile if not previously used. For example, you could change:

Quote

[Profile.MilViz DHC2]
1=MilViz DHC2 Beaver N1117F
2=DHC2 Beaver N1117F Straight Floats
3=MilViz DHC2 Beaver N1117F Floats
4=MilViz DHC2 Beaver CUXPA Floats
5=MilViz DHC2 Beaver CUXPA Skis
6=MilViz DHC2 Beaver N963DH Tundra
7=DHC2 Beaver N904AK Tundra STOL
 

to

Quote

[Profile.MilViz DHC2]
1=MilViz DHC2 Beaver

You also have "DHC2 Beaver N1117F Straight Floats" in your "Single Engine Amphib" profile (as well as your "MilViz DHC2" profile) which you probably want to remove.

However, if you do use different profiles for different variants (which seems strange to me!), then you may need to use the full aircraft name, but using substrings is far easier. See the documentation for details in profile substring matching.

John

[mslim]

6 hours ago, John Dowson said:

I thought your issue was with the T-28, but you dom'y seem to be providing any of the requested logs for this, or reporting on the other controls I have asked you to try.

I have instituted the Rudder Trim Left and Rudder Trim Right settings as per your recommendations, and it seems to be working as I desire. See attached pix for my implementation in FSUIPC axes.

I know the values aren't equal in the ranges but I edited them in the .ini.

Kindly provide further suggestions if needed.

6 hours ago, John Dowson said:

Btw. you should consider using aircraft substrings for your profile sections rather than the full aircraft name, with livery.

Yes I take your point and hope I have implemented that properly.

Thanks for bearing with me. I am not very code savvy. I'm more comfortable with a wrench in my hands fixing a vintage motorbike, than typing on a keyboard.

 

 

FSUIPC6_ini.zip FSUIPC6_log.zip

[John Dowson]

12 hours ago, mslim said:

I have instituted the Rudder Trim Left and Rudder Trim Right settings as per your recommendations, and it seems to be working as I desire. See attached pix for my implementation in FSUIPC axes.

I know the values aren't equal in the ranges but I edited them in the .ini.

Kindly provide further suggestions if needed.

If it is working to your liking, no other suggestions needed - apart from what I have said (i.e. try assigning directly to the rudder trim set axis). But if it is working ok, why not just stick to that,

John