Jump to content
The simFlight Network Forums

Recommended Posts

Posted

hi

PMDG MD-11 has a 'define a keyboard command', 'Set Take Off Stab Trim',

and I've set this to CTRL-TAB-T

it sets the Trim to the calculation from the FMC

so is there any way (?) to make this to a FS control in the dropdown list?

I've added

LogEvents=Yes

LogButtonsKeys=Yes

LogWrites=Yes

LogReads=Yes

to my INI

loaded a routine test flight, pushed CTRL-TAB-T

and the end of the log grew to this:

123023 *** EVENT: Cntrl= 65709 (0x000100ad), Param= 71056 (0x00011590) NAV2_RADIO_SET

126049 *** EVENT: Cntrl= 65709 (0x000100ad), Param= 67648 (0x00010840) NAV2_RADIO_SET

129091 *** EVENT: Cntrl= 65709 (0x000100ad), Param= 71056 (0x00011590) NAV2_RADIO_SET

131400 KEYDOWN: VK=17, Waiting=0, Repeat=N, Shifts=2

131400 .. Key not programmed -- passed on to FS

131400 KEYDOWN: VK=9, Waiting=0, Repeat=N, Shifts=18

131400 .. Key not programmed -- passed on to FS

131400 *** EVENT: Cntrl= 65827 (0x00010123), Param= 0 (0x00000000) NEXT_VIEW

131634 KEYDOWN: VK=9, Waiting=0, Repeat=Y, Shifts=18

131634 .. Key not programmed -- passed on to FS

131634 *** EVENT: Cntrl= 65827 (0x00010123), Param= 0 (0x00000000) NEXT_VIEW

131681 KEYDOWN: VK=9, Waiting=0, Repeat=Y, Shifts=18

131681 .. Key not programmed -- passed on to FS

131681 *** EVENT: Cntrl= 65827 (0x00010123), Param= 0 (0x00000000) NEXT_VIEW

131728 KEYDOWN: VK=9, Waiting=0, Repeat=Y, Shifts=18

131728 .. Key not programmed -- passed on to FS

131728 *** EVENT: Cntrl= 65827 (0x00010123), Param= 0 (0x00000000) NEXT_VIEW

131728 KEYDOWN: VK=84, Waiting=0, Repeat=N, Shifts=18

131728 .. Key not programmed -- passed on to FS

131899 KEYUP: VK=84, Waiting=0

132133 KEYUP: VK=9, Waiting=0

132196 *** EVENT: Cntrl= 65709 (0x000100ad), Param= 67648 (0x00010840) NAV2_RADIO_SET

132196 KEYUP: VK=17, Waiting=0

135222 *** EVENT: Cntrl= 65709 (0x000100ad), Param= 71056 (0x00011590) NAV2_RADIO_SET

and I can somewhat see the keys pushed

but there's no event that shows the Trim set to FMC value

what am I missing?

thx, MT

FSUIPC v4.427

Posted

PMDG MD-11 has a 'define a keyboard command', 'Set Take Off Stab Trim',

and I've set this to CTRL-TAB-T

it sets the Trim to the calculation from the FMC

Interesting.

so is there any way (?) to make this to a FS control in the dropdown list?

Why would you want to? You can assign keystrokes to buttons and switches, asnd you just confirmed that you can operate it by a keypress combination.

I've added

LogEvents=Yes

LogButtonsKeys=Yes

LogWrites=Yes

LogReads=Yes

to my INI

Why? I don't think any of those would be relevant to setting an analogue value like the trim. If there is anything sent to FS via the normal systems by the MD-11 code it would be using an Axis control -- you logged everything except axes?

Only axis controls can set analogue axis values, unless the value is written direct to FS's internals, perhaps via FSUIPC or perhaps not.

Regards

Pete

Posted
so is there any way (?) to make this to a FS control in the dropdown list?

Why would you want to? You can assign keystrokes to buttons and switches, asnd you just confirmed that you can operate it by a keypress combination.

I have my Trim up and down with an axis, but it takes quite long,

and I figured I wanted to try a center position to set FMC Trim (and I'm running out of buttons :x )

added

LogAxes=Yes

unfortunately, log stated allmost the same, when CTRL-TAB-T is pushed:

594129 KEYDOWN: VK=17, Waiting=0, Repeat=N, Shifts=2

594129 .. Key not programmed -- passed on to FS

594129 KEYDOWN: VK=9, Waiting=0, Repeat=N, Shifts=18

594129 .. Key not programmed -- passed on to FS

594129 *** EVENT: Cntrl= 65827 (0x00010123), Param= 0 (0x00000000) NEXT_VIEW

594395 KEYDOWN: VK=17, Waiting=0, Repeat=Y, Shifts=18

594395 .. Key not programmed -- passed on to FS

594395 KEYDOWN: VK=9, Waiting=0, Repeat=Y, Shifts=18

594395 .. Key not programmed -- passed on to FS

594395 *** EVENT: Cntrl= 65827 (0x00010123), Param= 0 (0x00000000) NEXT_VIEW

594441 KEYDOWN: VK=17, Waiting=0, Repeat=Y, Shifts=18

594441 .. Key not programmed -- passed on to FS

594441 KEYDOWN: VK=9, Waiting=0, Repeat=Y, Shifts=18

594441 .. Key not programmed -- passed on to FS

594441 *** EVENT: Cntrl= 65827 (0x00010123), Param= 0 (0x00000000) NEXT_VIEW

594441 KEYDOWN: VK=17, Waiting=0, Repeat=Y, Shifts=18

594441 .. Key not programmed -- passed on to FS

594441 KEYDOWN: VK=9, Waiting=0, Repeat=Y, Shifts=18

594441 .. Key not programmed -- passed on to FS

594441 *** EVENT: Cntrl= 65827 (0x00010123), Param= 0 (0x00000000) NEXT_VIEW

594488 KEYDOWN: VK=17, Waiting=0, Repeat=Y, Shifts=18

594488 .. Key not programmed -- passed on to FS

594488 KEYDOWN: VK=9, Waiting=0, Repeat=Y, Shifts=18

594488 .. Key not programmed -- passed on to FS

594488 *** EVENT: Cntrl= 65827 (0x00010123), Param= 0 (0x00000000) NEXT_VIEW

594535 KEYDOWN: VK=17, Waiting=0, Repeat=Y, Shifts=18

594535 .. Key not programmed -- passed on to FS

594535 KEYDOWN: VK=9, Waiting=0, Repeat=Y, Shifts=18

594535 .. Key not programmed -- passed on to FS

594535 *** EVENT: Cntrl= 65827 (0x00010123), Param= 0 (0x00000000) NEXT_VIEW

594535 KEYDOWN: VK=84, Waiting=0, Repeat=N, Shifts=18

594535 .. Key not programmed -- passed on to FS

594800 KEYUP: VK=84, Waiting=0

595081 KEYUP: VK=9, Waiting=0

595175 KEYUP: VK=17, Waiting=0

596079 *** EVENT: Cntrl= 65709 (0x000100ad), Param= 67648 (0x00010840) NAV2_RADIO_SET

599153 *** EVENT: Cntrl= 65709 (0x000100ad), Param= 71056 (0x00011590) NAV2_RADIO_SET

"passed to FS" and no record of anything

my FMC trim does get set though

this end of story?

thx MT

Posted
so is there any way (?) to make this to a FS control in the dropdown list?

Why would you want to? You can assign keystrokes to buttons and switches, asnd you just confirmed that you can operate it by a keypress combination.

I have my Trim up and down with an axis, but it takes quite long,

and I figured I wanted to try a center position to set FMC Trim (and I'm running out of buttons :x )

Two points there:

1. You can calibrate your trim axis to give you a faster result -- just don't use so much of it. Calibrate it for less movement from full down to full up. You can also use the slope facility to give you the needed sensitivity near level trimming but with fast movements from further afield.

2. You can also assign the FSUIPC control to press and release a keystroke, if you are thinking of getting the Axis assignment tab to send it using the zone facilities on the right-hand side. The last example of axis assignments in the FSUIPC user guide features such controls.

I'm really puzzled by what it is extra to all these facilities you need, and by why you keep trying to find something by logging. If an add-on changes things directly in FS without using FSUIPC or any standard FS controls then there's no way FSUIPC logging wil do anything for you. Even if it did, what do you hope to gain?

Please tell me why you cannot use the facilities available to send the keystroke you already have.

Regards

Pete

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • 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.