Jump to content
The simFlight Network Forums
Sign in to follow this  
English Rebel

Problem with Rudder Trim

Recommended Posts

I'm using these settings to trim my rudder from the User Guide (yes I do read it :razz: ):

Offest: 0C04

Type: Word

Decrement (for left trim) and Increment (for right trim)

Value: 1000

Minimum value: -16383 (for left trim)

Maximum value: 16383 (for right trim)

The problem is that the trim only works for trimming to the left (a decrement), I can only get it to work in one direction -- not both.

I thought I had the settings okay and it works fine for pitch trim using offset 0BC0

Thanks

Alan

Share this post


Link to post
Share on other sites

I'm using these settings to trim my rudder from the User Guide (yes I do read it :razz: ):

Offest: 0C04

Type: Word

Decrement (for left trim) and Increment (for right trim)

Value: 1000

Minimum value: -16383 (for left trim)

Maximum value: 16383 (for right trim)

The problem is that the trim only works for trimming to the left (a decrement), I can only get it to work in one direction -- not both.

I thought I had the settings okay and it works fine for pitch trim using offset 0BC0

0C04 maps onto the SimConnect variable "RUDDER TRIM PCT". That's all I know about it really.

Are you writing a program to do this? Or what? I really need to understand what you are doing if I'm to help.

Try using the FSUIPC logging facilities. If you go into the Logging tab, and on the right-hand side add "0C04" as an offset to be monitored, of type "S16" (signed 16-bit), then check "Normal log" below and enable the console log on the left, then on OKing out, change FSX to Windowed mode so you can see the log in real time. Then run your program or whatever it is and see what happens. If you think it is wrong, show me the log itself.

Regards

Pete

Share this post


Link to post
Share on other sites

Pete

Sorry I should have been more specific. I'm trying to program my yoke top hatch switch that trims the elevator (nose up/nose down) and rudder (left/right). I used the example from page 31 of the User Guide (the box with Offset Increment/Decrement Controls examples for elevator, rudder, and ailerons). I'm programming my switches in Flight Deck Systems InterfaceIT software. I should add, that my elevator controls are now only acting in one direction -- same as the rudder.

Thanks

Alan

Share this post


Link to post
Share on other sites

Sorry I should have been more specific. I'm trying to program my yoke top hatch switch that trims the elevator (nose up/nose down) and rudder (left/right). I used the example from page 31 of the User Guide (the box with Offset Increment/Decrement Controls examples for elevator, rudder, and ailerons). I'm programming my switches in Flight Deck Systems InterfaceIT software. I should add, that my elevator controls are now only acting in one direction -- same as the rudder.

The elevator control, or the elevator trim, which you said in your previous message was working? If the latter, what have you changed?

I still don't have enough information. Perhaps you should show me the actual assignments in your INI file, else we'll go in circles for a while!

You also haven't shown me any of the logging reults. Are you shy? ;-)

Regards

Pete

Share this post


Link to post
Share on other sites

Pete

Here is the relevant entries from the log file for monitoring offset 0BC0 (and no,at my age Im beyond being shy :cool:). The switch actions are erratic - I haven't changed anything. For instance some times it will work fine then the next time it will only work for Nose Down. On other occassions I got readings both ways. I think you will see that last two entries are when I couldnt get the Nose Up function to work but had to move the switch twice to get the Nose Down to register.

Thanks

Alan

1150289 WideFS: write to 0BC0 from skt=7764 ("AVIONICS"), program Id=1456

1150289 Monitor IPC:0BC0 (S16) = -2055

1150305 Monitor IPC:0BC0 (S16) = -2054

1150305 SimRead: 0BC0="ELEVATOR TRIM PCT"

FLT64: -12.5434933091

1156810 Sim stopped: average frame rate for last 22 secs = 71.7 fps

1163877 WideFS: write to 0BC0 from skt=7764 ("AVIONICS"), program Id=1456

1164002 Monitor IPC:0BC0 (S16) = -3082

1259381 Sim stopped: average frame rate for last 23 secs = 71.8 fps

1265964 WideFS: write to 0BC0 from skt=7764 ("AVIONICS"), program Id=1456

1266104 Monitor IPC:0BC0 (S16) = -4110

1275511 WideFS: write to 0BC0 from skt=7764 ("AVIONICS"), program Id=1456

1275589 Monitor IPC:0BC0 (S16) = -5138

1285995 WideFS: write to 0BC0 from skt=7764 ("AVIONICS"), program Id=1456

1286073 Monitor IPC:0BC0 (S16) = -6166

[Log closed by user request, and continued in new file]

1615126 System time = 09/05/2013 13:08:05, Simulator time = 12:58:55 (16:58Z)

1615126 *** FSUIPC log file being closed

Average frame rate for running time of 1063 secs = 77.0 fps

G3D fix: Passes 14377, Null pointers 0, Bad pointers 0, Separate instances 0

Memory managed: 636 Allocs, 523 Freed

********* FSUIPC Log file closed ***********

This is my INI file

[General]

UpdatedByVersion=4900

History=XK5BX83I0BOODP80SSL6E

InitDelayDevicesToo=No

UseMidMouseBtn=Yes

MouseWheelMove=No

MouseWheelTrim=No

MouseWheelTrimSpeed=1

JoystickTimeout=20

PollGFTQ6=Yes

BlankDisplays=No

FixControlAccel=No

FixMachSpeedBug=No

DeleteVehiclesForAES=Yes

AutoScanDevices=Yes

VisibilityOptions=No

OneCloudLayer=No

CloudTurbulence=No

CloudIcing=No

GenerateCirrus=No

SuppressCloudTurbulence=No

MaxIce=-4

MinIce=-4

UpperWindGusts=No

SuppressWindTurbulence=No

SuppressWindVariance=No

WindTurbulence=No

TurbulenceRate=1.0,5.0

TurbulenceDivisor=20,20,40,40

SuppressAllGusts=No

MaxSurfaceWind=0

WindLimitLevel=200

WindDiscardLevel=400

WindAjustAltitude=No

WindAjustAltitudeBy=2000

SmoothBySimTime=No

WindSmoothing=No

WindSmoothness=2

WindSmoothAirborneOnly=Yes

PressureSmoothness=0

TemperatureSmoothness=0

DisconnTrimForAP=No

ZeroElevForAPAlt=No

ThrottleSyncAll=No

WhiteMessages=No

ShowPMcontrols=No

SpoilerIncrement=512

MagicBattery=No

RudderSpikeRemoval=No

ElevatorSpikeRemoval=No

AileronSpikeRemoval=No

ReversedElevatorTrim=No

ClockSync=No

ClockSyncMins=5

ClearWeatherDynamics=No

OwnWeatherChanges=No

TimeForSelect=4

LoadFlightMenu=No

LoadPlanMenu=No

PauseAfterCrash=No

BrakeReleaseThreshold=75

SaveDataWithFlights=No

ZapSound=firework

ShortAircraftNameOk=Substring

UseProfiles=Yes

EnableMouseLook=No

AxesWrongRange=No

TCASid=Flight

TCASrange=40

AxisCalibration=No

DirectAxesToCalibs=No

ShowMultilineWindow=Yes

SuppressSingleline=No

SuppressMultilineFS=No

AxisIntercepts=No

DontResetAxes=No

InitDelay=0

GetNearestAirports=Yes

OOMcheck=Yes

WeatherReadFactor=2

WeatherRewriteSeconds=1

CustomWeatherModify=No

SimConnectStallTime=1

LuaRerunDelay=66

Console=No

FSVersionUsed="Microsoft Flight Simulator X",10.0.61472.0

SimConnectUsed=10.0.61259.0

ConsoleWindow=150,150,827,509

LogEvents=Yes

LogButtonsKeys=Yes

[window.LUA display]

Docked=7356, 2856, 3534, 2446

[JoyNames]

AutoAssignLetters=Yes

A=BU0836 Interface

B=Virtual Joystick

A.GUID={486EF670-8BD6-11E2-8001-444553540000}

B.GUID={7BA4DE70-8BDA-11E2-8002-444553540000}

0=Virtual Joystick

0.GUID={7BA4DE70-8BDA-11E2-8002-444553540000}

[WideServer]

WideFSenabled=Yes

AdvertiseService=1

Port=8002

Port2=9002

[sounds]

Path=E:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Sound\

Device1=Primary Sound Driver

Device2=SAMSUNG-1 (NVIDIA High Definition Audio)

Device3=Digital Audio (S/PDIF) (High Definition Audio Device)

Device4=Digital Audio (S/PDIF) (High Definition Audio Device)

[AutoSave]

AutoSaveEnabled=No

Next=1

Interval=60

Files=10

SaveOnGround=No

[GPSout]

GPSoutEnabled=No

Port=COM0

Speed=4800

Interval=2000

PosTo6Decimal=No

Sentences=

[GPSout2]

GPSoutEnabled=No

Port=<none set>

Speed=4800

Interval=2000

PosTo6Decimal=No

Sentences=

[Programs]

[ClientNames]

1=AVIONICS

[Monitor]

Display=1

Monitor0=0,0BC0,2,0

[JoystickCalibration]

AllowSuppressForPFCquad=Yes

ExcludeThrottleSet=Yes

ExcludeMixtureSet=Yes

ExcludePropPitchSet=Yes

SepRevsJetsOnly=No

ApplyHeloTrim=No

UseAxisControlsForNRZ=No

FlapsSetControl=0

FlapDetents=Yes

ReverserControl=66292

Reverser1Control=66422

Reverser2Control=66425

Reverser3Control=66428

Reverser4Control=66431

MaxThrottleForReverser=256

AileronTrimControl=66731

RudderTrimControl=66732

CowlFlaps1Control=66162

CowlFlaps2Control=66163

CowlFlaps3Control=66164

CowlFlaps4Control=66165

SteeringTillerControl=0

MaxSteerSpeed=60

Aileron=-16068,-512,512,16096

SlopeAileron=-7

Elevator=-16209,-512,512,16131

SlopeElevator=-6

Rudder=-13926,-492,512,16274

LeftBrake=-16384,16383

RightBrake=-16384,15798

!1=T

PropPitch=-16380,16380

Throttle1=22,22,512,16384/48

Throttle2=36,36,512,16380/48

FlapStarts=-16384,0,11346,16072

FlapEnds=-15344,5084,12917,16384

Flaps=0,16380

Spoilers=13240,15944

Reverser=-16380,16380

[Axes]

0=BX,256,D,9,0,0,0

1=BY,287,D,10,0,0,0

2=BZ,256,D,22,0,0,0

3=BU,256,D,22,0,0,0

4=BV,256,D,23,0,0,0

5=BS,824,D,22,0,0,0

6=AX,256,D,3,0,0,0

7=AU,256,D,7,0,0,0

8=AV,256,D,8,0,0,0

[buttons]

0=P1001,0,Cx0D0073F8,x01

2=P1001,5,Cx050073F8,x20

4=P1001,1,Cx050073F8,x02

5=P1001,14,C66040,16211

6=U1001,1,Cx090073F8,x02

7=U1001,0,Cx090073F8,x01

8=P1001,2,Cx050073F8,x04

9=U1001,2,Cx090073F8,x04

10=P1001,3,Cx050073F8,x08

11=U1001,3,Cx090073F8,x08

12=P1001,4,Cx050073F8,x10

13=U1001,4,Cx090073F8,x10

14=U1001,5,Cx090073F8,x20

15=P1001,13,Cx050073D5,x40

18=U1001,13,Cx090073D5,x40

19=P1001,7,Cx050073F9,x01

20=U1001,7,Cx090073F9,x01

21=P1001,8,Cx050073F9,x02

22=U1001,8,Cx090073F9,x02

23=P1001,9,Cx050073F9,x04

24=U1001,9,Cx090073F9,x04

25=P1001,10,Cx050073F9,x08

26=U1001,10,Cx090073F9,x08

27=P1001,11,Cx050073F9,x10

28=U1001,11,Cx090073F9,x10

29=P1001,12,Cx050073F9,x20

30=U1001,12,Cx090073F9,x20

31=R1001,19,Cx110073FD,x00FF0001

32=R1001,18,Cx210073FD,x00FF0001

33=R1001,23,Cx110073FC,x00FF0001

34=R1001,22,Cx210073FC,x00FF0001

35=R1001,21,Cx210073D2,x00FF0001

36=R1001,20,Cx110073D2,x00FF0001

37=R1001,25,Cx110073D7,x00FF0001

38=R1001,24,Cx210073D7,x00FF0001

39=R1001,27,Cx210073D8,x00FF0001

40=R1001,26,Cx11000049,x00FF0001

41=R1001,29,C65883,1

42=R1001,28,C65884,1

50=PB,0,C3,0

51=PB,1,C65552,0

54=PB,2,C65983,1

55=PB,3,C65988,1

56=PB,5,C65820,0

60=PB,4,C65588,0

66=UB,4,C65752,0

67=UB,5,C65820,-4096

Buttonrepeat=20,10

68=UB,2,C65987,1

69=UB,3,C65992,1

70=PB,6,C65821,0

71=UB,6,C65821,-4096

72=P72,0,C1126,0

73=P72,1,Cx05000B51,x01

[MacroFiles]

1=iFly737

2=leveld767

[buttons]

Buttonrepeat=20,10

[LuaFiles]

1=ipcReady

2=linda

Share this post


Link to post
Share on other sites

1150289 WideFS: write to 0BC0 from skt=7764 ("AVIONICS"), program Id=1456

Okay, so you aren't doing all this by assignments as I assumed from what you said:

"I used the example from page 31 of the User Guide (the box with Offset Increment/Decrement Controls examples for elevator, rudder, and ailerons)."

but instead a program running on a PC called "AVIONICS".

This is my INI file

But anything you do there is surely being overridden by the program running on "AVIONICS"? And in any case thee is certainly no assignment there to any offset control handling either of the offsets you were asking about.

What is going on? Nothing here is in anyway reelated to anything you were saying you were doing or what you were asking about!!!

Pete

Share this post


Link to post
Share on other sites

Pete

I think the issue is that I'm using Flight Deck Solutions InterfaceIT program that writes the offsets direct to FSX which is why they are not in the INI file. I had this issue before when I wanted to add a button condiiton. I had to make InterfaceIT emulate a joystick button (joystick 72) so I could program it in FSUIPC. Let me do the same for these elevator and rudder switches and see where we go from here.

The AVIONICS is the name of my client PC by the way.

Thanks

Alan

Share this post


Link to post
Share on other sites

I think the issue is that I'm using Flight Deck Solutions InterfaceIT program that writes the offsets direct to FSX which is why they are not in the INI file.

So what was all that about using the offset and programming inc and dec?

Why can't this FDS program handle the correct offsets in the corerect way in any case? As far as i know they are a competent company and should know what they are doing. Don't they have any support?

The AVIONICS is the name of my client PC by the way.

Yes, I understood that. But nothing of what you supplied in the last message really had any relation to your original questions. It is totally baffling when you do that to someone who is trying to help. How can you say so much that is plainly not true?

:-(

Aren't you trying to do something in the most complicated way possible? What are you using the FDS software for if it isn't suitable and has to be perverted so much?

Pete

Share this post


Link to post
Share on other sites

Pete

I cant comment on the functionality of the FDS program. All I can do is to enter the offsets and values. I will take this up with FDS to see why its not writing them properly. (I have attached a screen shot of the InterfaceIT window).

In the meantime I set the switches for nose up and nose down on my center console and also on my yoke as buttons on offset 3360 in InterfaceIT and they are recognized in FSUIPC as buttons 2, 3, 4, & 5 on joystick 72. In the Buttons + Switches section I programmed the Nose Up switches on Offset 0BC0 SWord Increment with a value of 500/16383. Same for Nose Down but with Decrement 500/-16383. Now what happens is that the pitch goes from 0.0 to 0.3 with one push of the spring loaded nose down switch (and from 0.3 to 0.0 with a push of the nose up switch and that's it. If I check the box Control to repeat if held, the pitch goes from either full nose down to full nose up with a single press of the switch.

Heres the additional entries in the INI file (let me know if you need the whole file again).

Thanks

Alan

75=P72,2,Cx42000BC0,xC00101F4

76=P72,3,Cx32000BC0,x3FFF01F4

77=P72,4,Cx42000BC0,xC00101F4

78=P72,5,Cx32000BC0,x3FFF01F4

FDS InterfaceIT switch programming window.

post-21337-0-68970000-1368124626.jpg

Share this post


Link to post
Share on other sites

I cant comment on the functionality of the FDS program. All I can do is to enter the offsets and values. I will take this up with FDS to see why its not writing them properly.

Why aren't you using an axis (potentiometer) for trim adjustments, and calibrating them as such? It would be much nice that using two buttons.

Now what happens is that the pitch goes from 0.0 to 0.3 with one push of the spring loaded nose down switch (and from 0.3 to 0.0 with a push of the nose up switch and that's it.

0.3 of what? A radian? What is the limit in that measure? Where are you reading it? Are you saying on the next push it does nothing at all.

Where's the logging? PLEASE ENABLE BUTTON LOGGING too (one check mark on the left) so i can see exactly what you are pressing!

If I check the box Control to repeat if held, the pitch goes from either full nose down to full nose up with a single press of the switch.

That makes no sense whatsoever. At 500 per repeat and the default Buttonrepeat=20,10 setting you have, there will first be 1/2 second delay (in which time you should have released the button), and then 20 repeatets per second, so needing 3 seconds to get from 0 to 16k. Or maybe your "InterfaceIT" program is so slow it is not able to send the "release" for 3 seconds? That woud explain it. I'd need to see the log to believe that though!

I'm afraid I'm now off for a long weekend (steam train tour in Ireland). I'll be back on Wednesday next week.

I'm sure you'll work out what is going wrong using the logging. If you ask me, that software you are using seems to make things very complicated. A set of buttons connected via a Bodnar board, with some axis / pots too, would be soooo much easier! That's what i use.

Regards

Pete

Share this post


Link to post
Share on other sites

But nothing of what you supplied in the last message really had any relation to your original questions. It is totally baffling when you do that to someone who is trying to help. How can you say so much that is plainly not true?

Pete

Pete

I'm sorry if you think that but I was originally asking about rudder trim and now I'm referring to rudder and elevator trim because if we fix one we fix the other.

Alan

Where's the logging? PLEASE ENABLE BUTTON LOGGING too (one check mark on the left) so i can see exactly what you are pressing!

I'm afraid I'm now off for a long weekend (steam train tour in Ireland). I'll be back on Wednesday next week.

I'm sure you'll work out what is going wrong using the logging. If you ask me, that software you are using seems to make things very complicated. A set of buttons connected via a Bodnar board, with some axis / pots too, would be soooo much easier! That's what i use.

Regards

Pete

Pete

I hope you enjoy your time away from the forum (and questions like mine :mad: ) and I will enable button logging and let you have the results. BTW I love steam trains -- I miss that era when I used to catch a train from Redditch to Birmingham with a few ten shilling notes in my wallet. I would then change trains at New Street station to catch one to West Bromwich to see my auntie, uncle and cousins.

Alan

Share this post


Link to post
Share on other sites

Pete

I have monitored the nose up and nose down trim switches on my center console (switches 72,2 and 72,3) (switches 72,4 & 72,5 are on my yoke). The log file is attached as well as the entries for the switches in the ini file. Please let me know if you can see anything out of wack.

Thanks

Alan

Heres the additional entries in the INI file (let me know if you need the whole file again).

75=P72,2,Cx42000BC0,xC00101F4

76=P72,3,Cx32000BC0,x3FFF01F4

77=P72,4,Cx42000BC0,xC00101F4

78=P72,5,Cx32000BC0,x3FFF01F4

Here are the button log file with the Control to repeat if held box un-checked. When I push the spring loaded switch and release it the EICAS PITCH display moves from 0.0 to -0.3 and moves back to 0.0 with a press of the nose up switch (the value seems to be a function of the offset increment) but thats all -- repeated presses of the switch dont change anything.

If I check the Control to repeat while held box then press and release the spring loaded switch, the log file entries just keep repeaing until I cancel it.

********* FSUIPC4, Version 4.90 by Pete Dowson *********

User Name="ALAN NORRIS"

User Addr="REDACTED BY ME"

FSUIPC4 Key is provided

WideFS7 Key is provided

1696839 System time = 10/05/2013 11:05:16, Simulator time = 10:56:05 (14:56Z)

[Continuation log requested by user]

Running inside FSX on Windows 7

Module base=0C300000

1696854 LogOptions changed, now 40000080 00000001

1711924 Button changed: bRef=0, Joy=72, Btn=2, Released

1711924 Button changed: bRef=0, Joy=72, Btn=3, Pressed

1711924 [buttons] 77=P72,3,Cx42000BC0,x3FFF01F4

1711924 IPC Offsets Control: Ctrl=x4200, Length=2, Offset=0BC0, Param=x3FFF01F4

1713422 Button changed: bRef=0, Joy=72, Btn=2, Pressed

1713422 [buttons] 74=P72,2,Cx32000BC0,x3FFF01F4

1713422 IPC Offsets Control: Ctrl=x3200, Length=2, Offset=0BC0, Param=x3FFF01F4

1713422 Button changed: bRef=0, Joy=72, Btn=3, Released

Share this post


Link to post
Share on other sites

Whats wrong with using FS controls for trim ie Elev Trim Up and Elev Trim Dn rather than trying to feed it through the offsets. Works fine for my Learjet sim.

If you need to alter the effectiveness of the trim you can play with the settings in the aircraft cfg file under the flight tuning section.

I run mine at about 1.4 as I needed the trim to be more effective.

[flight_tuning]

elevator_trim_effectiveness = 1.4

aileron_trim_effectiveness = 1.0

rudder_trim_effectiveness = 1.0

post-11610-0-87224600-1368345882.jpg

Share this post


Link to post
Share on other sites

Here are the button log file with the Control to repeat if held box un-checked. When I push the spring loaded switch and release it the EICAS PITCH display moves from 0.0 to -0.3 and moves back to 0.0 with a press of the nose up switch (the value seems to be a function of the offset increment) but thats all -- repeated presses of the switch dont change anything.

But unfortunately the log extract you showed me only shows button 2 being pressed and released once, and button 3 pressed and released once, so naturally you'd get one increment and one decrement. There's also another strange thing. Look at this and then compare it wityh the setting you said you had in your message for button 2: (75=P72,2,Cx42000BC0,xC00101F4)

1713422 Button changed: bRef=0, Joy=72, Btn=2, Pressed

1713422 [buttons] 74=P72,2,Cx32000BC0,x3FFF01F4

1713422 IPC Offsets Control: Ctrl=x3200, Length=2, Offset=0BC0, Param=x3FFF01F4

1713422 Button changed: bRef=0, Joy=72, Btn=3, Released

Evidently the lines you are showing me from your INI file are NOT the lines being used, so either you are looking at the wrong INI file, or the wrong [buttons] section in it!

Perhaps next time you'd better show the whole INI and the whole LOG if you can't find the right places? Also, please, on the right-hand side of the Logging tab, enter 01F4 as an offset of type S16 and check the "norml Log" option below. That will give use the value off the offset for each change your assignments are making.

Regards

Pete

Share this post


Link to post
Share on other sites

Pete

Let me try what Alaxus suggested first and if that doesn't work (and there is no reason it shouldn't as he runs a Lear45 the same as me) I'll post the information you asked for.

By the way on your comment

"But unfortunately the log extract you showed me only shows button 2 being pressed and released once, and button 3 pressed and released once, so naturally you'd get one increment and one decrement"

Yes that is correct but if I press button 2 again and again (to trim up) I get no movement on the trim indicator on the EICAS -- just for the first press.

Thanks

Alan

Share this post


Link to post
Share on other sites

"But unfortunately the log extract you showed me only shows button 2 being pressed and released once, and button 3 pressed and released once, so naturally you'd get one increment and one decrement"

Yes that is correct but if I press button 2 again and again (to trim up) I get no movement on the trim indicator on the EICAS -- just for the first press.

That's what you said, but then you didn't show the logging which might tell me why!!! The point of logging things was to show what actually happened. There's no point otherwise, don't you see?

In any case there's obviously a discrepancy between your stated assignments and the actual ones in use. You'll need to make sure that confusion doesn't still exist when you try changing to the other suggestion.

Regards

Pete

Share this post


Link to post
Share on other sites

Pete

I tried the suggestion by Alaxus but when I presseed the trim button it goes from full nose up to full nose down. With the Control to repeat while held box unchecked it only increments once. As I said before if I press the trim switch once to pitch up I can see the Pitch Trim button on the Trim console in FSX move down but another press of the nose up switch does nothing. Same with the pitch down switch. Repeated presses of the switch in either direction has no effect the first press is the only one that has any effect. If I check the Control to repeat while held box and press the switch once (not holding it closed) the log entries:

678760 Button changed: bRef=0, Joy=72, Btn=3, Pressed

678760 [buttons] 77=P72,3,C65615,0.

Keep repeating until I stop the logging - Its as if I was holding the switch closed.

Thanks

Alan

I entered offset 01f4 and started a log file and this is what I got

********* FSUIPC4, Version 4.90 by Pete Dowson *********

User Name="ALAN NORRIS"

User Addr="REDACTED"

FSUIPC4 Key is provided

WideFS7 Key is provided

675219 System time = 15/05/2013 08:07:55, Simulator time = 08:03:17 (12:03Z)

[Continuation log requested by user]

Running inside FSX on Windows 7

Module base=65A90000

675219 LogOptions changed, now 40000080 00000001

678760 Button changed: bRef=0, Joy=72, Btn=2, Released

678760 Button changed: bRef=0, Joy=72, Btn=3, Pressed

678760 [buttons] 77=P72,3,C65615,0

678760 FS Control Sent: Ctrl=65615, Param=0

679977 Button changed: bRef=0, Joy=72, Btn=2, Pressed

679977 [buttons] 74=P72,2,C65607,0

679977 FS Control Sent: Ctrl=65607, Param=0

679977 Button changed: bRef=0, Joy=72, Btn=3, Released

681053 Button changed: bRef=0, Joy=72, Btn=2, Released

681053 Button changed: bRef=0, Joy=72, Btn=3, Pressed

681053 [buttons] 77=P72,3,C65615,0

681053 FS Control Sent: Ctrl=65615, Param=0

682785 Button changed: bRef=0, Joy=72, Btn=2, Pressed

682785 [buttons] 74=P72,2,C65607,0

682785 FS Control Sent: Ctrl=65607, Param=0

682785 Button changed: bRef=0, Joy=72, Btn=3, Released

684282 Button changed: bRef=0, Joy=72, Btn=2, Released

684282 Button changed: bRef=0, Joy=72, Btn=3, Pressed

684282 [buttons] 77=P72,3,C65615,0

684282 FS Control Sent: Ctrl=65615, Param=0

693299 LogOptions changed, now 00000080 00000001

757088 Sim stopped: average frame rate for last 64 secs = 70.9 fps

[Log closed by user request, and continued in new file]

767197 System time = 15/05/2013 08:09:27, Simulator time = 08:04:37 (12:04Z)

767197 *** FSUIPC log file being closed

Average frame rate for running time of 472 secs = 70.4 fps

G3D fix: Passes 14195, Null pointers 0, Bad pointers 0, Separate instances 0

Memory managed: 359 Allocs, 257 Freed

********* FSUIPC Log file closed ***********

Here is my whole INI file

[General]

UpdatedByVersion=4900

History=CUBT8IDOILQVJG95XXQBP

InitDelayDevicesToo=No

UseMidMouseBtn=Yes

MouseWheelMove=No

MouseWheelTrim=No

MouseWheelTrimSpeed=1

JoystickTimeout=20

PollGFTQ6=Yes

BlankDisplays=No

FixControlAccel=No

FixMachSpeedBug=No

DeleteVehiclesForAES=Yes

AutoScanDevices=Yes

VisibilityOptions=No

OneCloudLayer=No

CloudTurbulence=No

CloudIcing=No

GenerateCirrus=No

SuppressCloudTurbulence=No

MaxIce=-4

MinIce=-4

UpperWindGusts=No

SuppressWindTurbulence=No

SuppressWindVariance=No

WindTurbulence=No

TurbulenceRate=1.0,5.0

TurbulenceDivisor=20,20,40,40

SuppressAllGusts=No

MaxSurfaceWind=0

WindLimitLevel=200

WindDiscardLevel=400

WindAjustAltitude=No

WindAjustAltitudeBy=2000

SmoothBySimTime=No

WindSmoothing=No

WindSmoothness=2

WindSmoothAirborneOnly=Yes

PressureSmoothness=0

TemperatureSmoothness=0

DisconnTrimForAP=No

ZeroElevForAPAlt=No

ThrottleSyncAll=No

WhiteMessages=No

ShowPMcontrols=No

SpoilerIncrement=512

MagicBattery=No

RudderSpikeRemoval=No

ElevatorSpikeRemoval=No

AileronSpikeRemoval=No

ReversedElevatorTrim=No

ClockSync=No

ClockSyncMins=5

ClearWeatherDynamics=No

OwnWeatherChanges=No

TimeForSelect=4

LoadFlightMenu=No

LoadPlanMenu=No

PauseAfterCrash=No

BrakeReleaseThreshold=75

SaveDataWithFlights=No

ZapSound=firework

ShortAircraftNameOk=Substring

UseProfiles=Yes

EnableMouseLook=No

AxesWrongRange=No

TCASid=Flight

TCASrange=40

AxisCalibration=No

DirectAxesToCalibs=No

ShowMultilineWindow=No

SuppressSingleline=No

SuppressMultilineFS=Yes

AxisIntercepts=No

DontResetAxes=No

InitDelay=0

GetNearestAirports=Yes

OOMcheck=Yes

WeatherReadFactor=2

WeatherRewriteSeconds=1

CustomWeatherModify=No

SimConnectStallTime=1

LuaRerunDelay=66

Console=No

ConsoleWindow=150,150,827,545

FSVersionUsed="Microsoft Flight Simulator X",10.0.61472.0

SimConnectUsed=10.0.61259.0

[window.LUA display]

Docked=7350, 2856, 3532, 2446

[JoyNames]

AutoAssignLetters=Yes

A=BU0836 Interface

B=Virtual Joystick

A.GUID={486EF670-8BD6-11E2-8001-444553540000}

B.GUID={7BA4DE70-8BDA-11E2-8002-444553540000}

0=Virtual Joystick

0.GUID={7BA4DE70-8BDA-11E2-8002-444553540000}

1=BU0836 Interface

1.GUID={486EF670-8BD6-11E2-8001-444553540000}

2=Virtual Joystick

2.GUID={80C212B0-8BDA-11E2-8003-444553540000}

3=Virtual Joystick

3.GUID={A30E3C60-BBDA-11E2-8007-444553540000}

C=Virtual Joystick

C.GUID={80C212B0-8BDA-11E2-8003-444553540000}

D=Virtual Joystick

D.GUID={A30E3C60-BBDA-11E2-8007-444553540000}

[WideServer]

WideFSenabled=Yes

AdvertiseService=1

Port=8002

Port2=9002

[sounds]

Path=E:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Sound\

Device1=Primary Sound Driver

Device2=SAMSUNG-1 (NVIDIA High Definition Audio)

Device3=Digital Audio (S/PDIF) (High Definition Audio Device)

Device4=Digital Audio (S/PDIF) (High Definition Audio Device)

[AutoSave]

AutoSaveEnabled=No

Next=1

Interval=60

Files=10

SaveOnGround=No

[GPSout]

GPSoutEnabled=No

Port=COM0

Speed=4800

Interval=2000

PosTo6Decimal=No

Sentences=

[GPSout2]

GPSoutEnabled=No

Port=<none set>

Speed=4800

Interval=2000

PosTo6Decimal=No

Sentences=

[Programs]

[ClientNames]

1=AVIONICS

[Monitor]

Display=1

Monitor0=0,01F4,2,0

[JoystickCalibration]

AllowSuppressForPFCquad=Yes

ExcludeThrottleSet=Yes

ExcludeMixtureSet=Yes

ExcludePropPitchSet=Yes

SepRevsJetsOnly=No

ApplyHeloTrim=No

UseAxisControlsForNRZ=No

FlapsSetControl=0

FlapDetents=Yes

ReverserControl=66292

Reverser1Control=66422

Reverser2Control=66425

Reverser3Control=66428

Reverser4Control=66431

MaxThrottleForReverser=256

AileronTrimControl=66731

RudderTrimControl=66732

CowlFlaps1Control=66162

CowlFlaps2Control=66163

CowlFlaps3Control=66164

CowlFlaps4Control=66165

SteeringTillerControl=0

MaxSteerSpeed=60

Aileron=-16068,-512,512,16096

SlopeAileron=-7

Elevator=-16209,-512,512,16131

SlopeElevator=-6

Rudder=-13926,-492,512,16274

LeftBrake=-16384,16383

RightBrake=-16384,15798

!1=T

PropPitch=-16380,16380

Throttle1=-10768,22,512,14406/48

Throttle2=-9944,36,512,14830/48

FlapStarts=-16384,-8,7216,12768

FlapEnds=-11771,1328,8520,16384

Flaps=0,16380

Spoilers=13240,15944

Reverser=-16380,16380

[Axes]

0=BX,256,D,9,0,0,0

1=BY,287,D,10,0,0,0

2=BZ,256,D,22,0,0,0

3=BU,256,D,22,0,0,0

4=BV,256,D,23,0,0,0

5=BS,824,D,22,0,0,0

6=AX,256,D,3,0,0,0

7=AU,256,D,7,0,0,0

8=AV,256,D,8,0,0,0

9=CX,256,D,9,0,0,0

10=CU,256,D,10,0,0,0

11=CV,256,D,23,0,0,0

[buttons]

0=PB,0,Cx0D0073F8,x01

2=PB,5,Cx050073F8,x20

4=PB,1,Cx050073F8,x02

5=PB,14,C66040,16211

6=UB,1,Cx090073F8,x02

7=UB,0,Cx090073F8,x01

8=PB,2,Cx050073F8,x04

9=UB,2,Cx090073F8,x04

10=PB,3,Cx050073F8,x08

11=UB,3,Cx090073F8,x08

12=PB,4,Cx050073F8,x10

13=UB,4,Cx090073F8,x10

14=UB,5,Cx090073F8,x20

15=PB,13,Cx050073D5,x40

18=UB,13,Cx090073D5,x40

19=PB,7,Cx050073F9,x01

20=UB,7,Cx090073F9,x01

21=PB,8,Cx050073F9,x02

22=UB,8,Cx090073F9,x02

23=PB,9,Cx050073F9,x04

24=UB,9,Cx090073F9,x04

25=PB,10,Cx050073F9,x08

26=UB,10,Cx090073F9,x08

27=PB,11,Cx050073F9,x10

28=UB,11,Cx090073F9,x10

29=PB,12,Cx050073F9,x20

30=UB,12,Cx090073F9,x20

31=RB,19,Cx110073FD,x00FF0001

32=RB,18,Cx210073FD,x00FF0001

33=RB,23,Cx110073FC,x00FF0001

34=RB,22,Cx210073FC,x00FF0001

35=RB,21,Cx210073D2,x00FF0001

36=RB,20,Cx110073D2,x00FF0001

37=RB,25,Cx110073D7,x00FF0001

38=RB,24,Cx210073D7,x00FF0001

39=RB,27,Cx210073D8,x00FF0001

40=RB,26,Cx11000049,x00FF0001

41=RB,29,C65883,1

42=RB,28,C65884,1

50=PB,0,C3,0

51=PB,1,C65552,0

54=PB,2,C65983,1

55=PB,3,C65988,1

56=PB,5,C65820,0

60=PB,4,C65588,0

66=UB,4,C65752,0

67=UB,5,C65820,-4096

Buttonrepeat=20,10

68=UB,2,C65987,1

69=UB,3,C65992,1

70=PB,6,C65821,0

71=UB,6,C65821,-4096

72=P72,0,C1126,0

73=P72,1,Cx05000B51,x01

74=P72,2,C65607,255

75=P72,4,Cx42000BC0,xC00101F4

76=P72,5,Cx32000BC0,x3FFF01F4

77=P72,3,C65615,255

78=PC,4,Cx02000BC8,x0000

80=PC,5,C65820,0

81=UC,5,C65820,-4096

82=PC,6,C65821,0

83=UC,6,C65821,-4096

84=PC,2,C65983,0

85=UC,2,C65987,0

86=PC,3,C65988,0

87=UC,3,C65992,0

88=UC,4,Cx02000BC8,x7FFF

[MacroFiles]

1=iFly737

2=leveld767

[buttons]

Buttonrepeat=20,10

[LuaFiles]

1=ipcReady

2=linda

Share this post


Link to post
Share on other sites

I tried the suggestion by Alaxus but when I presseed the trim button it goes from full nose up to full nose down. With the Control to repeat while held box unchecked it only increments once. As I said before if I press the trim switch once to pitch up I can see the Pitch Trim button on the Trim console in FSX move down but another press of the nose up switch does nothing. Same with the pitch down switch. Repeated presses of the switch in either direction has no effect the first press is the only one that has any effect. If I check the Control to repeat while held box and press the switch once (not holding it closed) the log entries:

678760 Button changed: bRef=0, Joy=72, Btn=3, Pressed

678760 [buttons] 77=P72,3,C65615,0.

Keep repeating until I stop the logging - Its as if I was holding the switch closed.

Okay. So now we have the answer. The button you are using is acting exactly like a toggle switch -- one press and it is on, another press and it is off. Like those buttons on table lamps. You are not going to be able to use it as you had hoped. The best you could do is program both "press" and "release" to do the same thing, without "repeat whilst held" checked, and just keep pressing it over and over for repeated trim adjustments. There is not going to be any other way to get anywhere near a proper trim control with such buttons.

Reading back a little too, even that might not be possible. You said once pressed further presses had no effect -- until when? Something must allow you to press it again! Maybe these buttons remain pressed until another button is pressed, like a sort of reset? You should be able to see what is going on -- either in FSUIPC or in the Windows game controllers applet in Control Panel.

To be honest, I'm amazed you have a device which does such a thing. I know the VRInsight serial port devices are like that -- you can't tell if the button is pressed or released, each press/release gives one message only. Looking back you said " I'm trying to program my yoke top hatch switch". What is a "hatch" switch, and what sort of yoke has one?

Regards

Pete

Share this post


Link to post
Share on other sites
. Looking back you said " I'm trying to program my yoke top hatch switch". What is a "hatch" switch, and what sort of yoke has one?

Regards

Pete

Pete

I have a real yoke from a Lear35. The top hat switch is on the left horn and is the actual Lear switch. It has four functions Elevator trim for Nose Up and Nose Down, as well as rudder trim for left and right. All functions are spring loaded. The console mounted trim switch is a reproduction of the real Lear 45 panel with primary and secondary elevator trim and rudder trim.

Alan

post-21337-0-52302700-1368630969.jpg

Share this post


Link to post
Share on other sites

I have a real yoke from a Lear35. The top hat switch is on the left horn and is the actual Lear switch. It has four functions Elevator trim for Nose Up and Nose Down, as well as rudder trim for left and right. All functions are spring loaded. The console mounted trim switch is a reproduction of the real Lear 45 panel with primary and secondary elevator trim and rudder trim.

Well i don't know how they'd program it in a real Lear, but if it is doing what it appears to be doing, and you cannot tell when it is released, then holding it in one position is not going to be the way to trim. Maybe it needs to be wired up differently to the way you've done it, or connected to your PC differently. I'm guessing it isn't plugged directly into a USB port because a Lear35 seems unlikely to be controlled by a PC with USB ports.

Pete

Share this post


Link to post
Share on other sites

Pete

Its just a simple switch with 4 terminals and a common ground. A push in any direction just closes the circuit for that particular direction. I cannot understand why after pressing the switch in one direction and getting a response from the switch in FSX, I get no response when I press the switch again in the same direction. I only get a response when pressing the switch in the opposite direction and then only once - I cannot get it to do it again. Closing the switch only sends an offset nothing more.

Alan

Share this post


Link to post
Share on other sites

Its just a simple switch with 4 terminals and a common ground. A push in any direction just closes the circuit for that particular direction. I cannot understand why after pressing the switch in one direction and getting a response from the switch in FSX, I get no response when I press the switch again in the same direction. I only get a response when pressing the switch in the opposite direction and then only once - I cannot get it to do it again.

Yes, all that happens because when you release the switch there's nothing seen in FS. It must be something to do with whatever is BETWEEN those 4 terminals + ground and the USB port or whatever it is you've connected it to!

Closing the switch only sends an offset nothing more.

How does a switch send an offset? You must have some hardware and software in between!

Getting information from you in order to help is very very difficult! One little tidbit for every 5 or 6 exchanges. Why can't you explain everytihng in one go? There's so much you appear to want to keep secret!

Pete

Share this post


Link to post
Share on other sites

Pete

Okay let's get back to basics as it's obvious I'm frustrating you and not getting my issue across. The trim switch is just like any other momentary switch in my cockpit. I push the switch and it records in FSUIPC Buttons + Switches as Joy# 72 Btn 2 (for nose up) and Btn 3 (for nose down ). If I don't use offsets and take the suggestion of Alaxus and just use the Elev Trim Up and Elev Trim Down controls, then one would think that every time I push and release the switch to trim the nose up then I should see a movement of the trim switch in FSX. I do see a movement the first time I press it but none the next or the next or the next. It seems as if FSUIPC recognizes that first push of the switch but doesn't for every subsequent push. The only time I can get the switch in FSX to respond is if I then push it to trim the nose down. Then subsequent pushes of the switch to trim the nose down are not recognized.

I don't know where the issue is. It's not the switch because I have two switches to trim -- one on the console and one on the yoke and they are different switches but I get the same problem.

Isn't there something in the log file that tells you what the switch is doing -- I pressed the switch up and down several times. Does it record any action on the second push of the switches?

Thanks

Alan

Share this post


Link to post
Share on other sites

Okay let's get back to basics as it's obvious I'm frustrating you and not getting my issue across.

I am only frustrated because i don't have all the information. I've no idea how you are setting these offsets from your buttons/switches.

The trim switch is just like any other momentary switch in my cockpit. I push the switch and it records in FSUIPC Buttons + Switches as Joy# 72 Btn 2 (for nose up) and Btn 3 (for nose down ).

For it to register as joystick 72 you must have somehow assigned it to operate a virtual buttons offset. How and why? I think this is more the area where your mistakes must be.

If I don't use offsets and take the suggestion of Alaxus and just use the Elev Trim Up and Elev Trim Down controls, then one would think that every time I push and release the switch to trim the nose up then I should see a movement of the trim switch in FSX. I do see a movement the first time I press it but none the next or the next or the next. It seems as if FSUIPC recognizes that first push of the switch but doesn't for every subsequent push.

As I have said several times before and which you have apparently ignored or missed, this is because it doesn't see a button release when you release it. If it doesn't see a button release is will not be able to register another press! It makes no difference whether you use the offsets method we were discussing before or the controls method suggested afterwards. If the button/switch appears to stay on forever after you operate it, at least till you press another, then it will do EXACTLY what you have described.

I don't understand why you don't believe me when i explained this to you! :sad: Why ignore so much of my replies??? :-( :-( :-(

The only time I can get the switch in FSX to respond is if I then push it to trim the nose down. Then subsequent pushes of the switch to trim the nose down are not recognized.

You keep repeating tihs, the exact same thing, and I keep answering you with the reason. Why can't you actually read what I write? And then you are surprised that I am getting frustrated with you?

Isn't there something in the log file that tells you what the switch is doing -- I pressed the switch up and down several times. Does it record any action on the second push of the switches?

The log would recerd EVERY single change in the switch, but there is NO change -- once you've pressed it it remains looking pressed until you've pressed another, different switch.

How many more ways can I explain this simple fact to you?

The problem obviously lies in how you've programmed the switches in whatever program you are using which is writing to the virtual button offsets. That is where to look, and where I have no informatation whatsoever from you!!!

Pete

Share this post


Link to post
Share on other sites

The problem obviously lies in how you've programmed the switches in whatever program you are using which is writing to the virtual button offsets.

I thought about this overnight, and what I am hypothesising is wrong is that whatever software you are using to set the virtual buttons offsets is doing something like this:

When a button/switch is "pressed", is is WRITING a value to offset 3360 (which corresponds to virtual joystick 72). For button 2 it writes 4, for 3 it writes 8, and so on.

By writing a value rather than simply setting a bit, it effectively means only one button/switch can be seen as "pressed" at any one time. The correct way of using the virtual buttons offsets is by ORing the value into them to set "pressed" and ANDing the bit out to set "released". So each time a switch is pressed or switched on, the others are set off or released.

But, additionally, it looks like the value 0, to show the button released, is not being written when the button is released. Nothing is written when a button is released!

Now, this hypothesis explains all of your symptoms. (But it would be much more efficient for you to actualy tell me how it is all programmed).

If the software you are using has no facilities for handling bits instead of byte values, then you can only do what you want by using only one button/switch per byte. i.e. offsets 3340, 3341, 3342 ...3363 (36 of them) all with only values 1 (on) or 0 (off). They would be seen in FSUIPC as buttons 0, 8, 16, 24, on each of joysticks 64 to 72 inclusive.

Regards

Pete

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
Sign in to follow this  

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.