Nono15

Thank you Peter for your response. You are very responsive. Actually I have a little trouble with the concept of offset and control. But I'll get there! The tests I've done with the software encoder_keys writing in Notepad gives me the impression of being conclusive. Indeed the action keys on the CDU seem correct in Notepad. I used the parameters 1 and 0 because this is what is written in the PMDG SDK : This sample code sets the TAXI lights switch: // Send another command only if there is no active command request // and previous command has been processed by the NGX if (Control.Event == 0) { Control.Event = EVT_OH_LIGHTS_TAXI; // = 69749 if (New_TaxiLightSwitch) Control.Parameter = 1; else Control.Parameter = 0; SimConnect_SetClientData (hSimConnect, PMDG_NGX_CONTROL_ID, PMDG_NGX_CONTROL_DEFINITION, 0, 0, sizeof(PMDG_NGX_Control), &Control); } In this case, the transmitted event is EVT_OH_LIGHTS_TAXI. The available events are listed in the PMDG_NGX_SDK.h file. The control parameter in this case is either 0 or 1 and determines the position the switch should be placed into. Note how the code checks that the NGX has no pending events to process by checking that Control.Event == 0. In fact if I configure the following FSUIPC and if I press the keys A and B then A then it appears AABBAA for A : ctrl+F10 ; Control sent when keys pressed : 70205 ; Parameter : 1 ; Control sent when main key released : 70205 ; Parameter : 0 ; No repeats! for B : ctrl+F9 ; Control sent when keys pressed : 70206 ; Parameter : 1 ; Control sent when main key released : 70206 ; Parameter : 0 ; No repeats! and the log of this action : ********* FSUIPC4, Version 4.853 by Pete Dowson ********* User Name="Gérard N" User Addr="gerard.n@orange.fr" FSUIPC4 Key is provided WideFS7 Key is provided 2444769 System time = 07/11/2012 00:16:15, Simulator time = 17:05:48 (15:05Z) [Continuation log requested by user] Running inside Prepar3D on Windows 7 Module base=5AA20000 2450182 KEYDOWN: VK=17, Waiting=0, Repeat=N, Shifts=2 2450182 .. Key not programmed -- passed on to FS 2450182 KEYDOWN: VK=121, Waiting=0, Repeat=N, Shifts=2 2450182 *** EVENT: Cntrl= 70205 (0x0001123d), Param= 1 (0x00000001) <70205> 2450182 FS Control Sent: Ctrl=70205, Param=1 2450182 .. This key is programmed in FSUIPC4 'Keys' options 2450182 KEYUP: VK=121, Waiting=0 2450182 *** EVENT: Cntrl= 70205 (0x0001123d), Param= 0 (0x00000000) <70205> 2450182 FS Control Sent: Ctrl=70205, Param=0 2450182 .. This key is programmed in FSUIPC4 'Keys' options 2450182 KEYUP: VK=17, Waiting=0 2452117 KEYDOWN: VK=17, Waiting=0, Repeat=N, Shifts=2 2452117 .. Key not programmed -- passed on to FS 2452117 KEYDOWN: VK=120, Waiting=0, Repeat=N, Shifts=2 2452117 *** EVENT: Cntrl= 70206 (0x0001123e), Param= 1 (0x00000001) <70206> 2452117 FS Control Sent: Ctrl=70206, Param=1 2452117 .. This key is programmed in FSUIPC4 'Keys' options 2452117 KEYUP: VK=120, Waiting=0 2452117 *** EVENT: Cntrl= 70206 (0x0001123e), Param= 0 (0x00000000) <70206> 2452117 FS Control Sent: Ctrl=70206, Param=0 2452117 .. This key is programmed in FSUIPC4 'Keys' options 2452117 KEYUP: VK=17, Waiting=0 2453178 KEYDOWN: VK=17, Waiting=0, Repeat=N, Shifts=2 2453178 .. Key not programmed -- passed on to FS 2453178 KEYDOWN: VK=121, Waiting=0, Repeat=N, Shifts=2 2453178 *** EVENT: Cntrl= 70205 (0x0001123d), Param= 1 (0x00000001) <70205> 2453178 FS Control Sent: Ctrl=70205, Param=1 2453178 .. This key is programmed in FSUIPC4 'Keys' options 2453178 KEYUP: VK=121, Waiting=0 2453178 *** EVENT: Cntrl= 70205 (0x0001123d), Param= 0 (0x00000000) <70205> 2453178 FS Control Sent: Ctrl=70205, Param=0 2453178 .. This key is programmed in FSUIPC4 'Keys' options 2453178 KEYUP: VK=17, Waiting=0 Yet it seems to me that it should work. Otherwise by reprogramming the control KeyUp with unused, it does not work better. Regards Gerard

Hello Peter, First of all I allow myself to congratulate you for all the work which you provide for FSUIPC. I have used it for several years and really this program is fantastic and it gives me any satisfaction. Today, I have a problem in trying to use FSUIPC 4,853, P3D 1.4, PMDG 737 NGX SP1C and a CDU Opencockpits V2 equipped with an interface USBKey which emulates a keyboard. With this intention, I connect the CDU on an USB port of my computer, then I start a programme encoder_keys written by Opencockpits which allows mapper all the keys of CDU as one wishes it thanks to a file encoder_keys.ini. For example when I press on key A of my CDU, encoder_keys sends sequence CTRL+F10. I made all mapping while avoiding using the native orders P3d or then I removed them in P3d. I also paid attention not to use the sequence ALT which can pose problems. In FSUIPC, I select the tab Key Presses, then I click on the Set button then I press on key A of my CDU. FSUIPC detects pressing the A key as ctrl+F10. So far everything is OK. From there, I select custom Control and enter 70205 (69632+573) which is offset PMDG for letter A of left CDU. I put 1 in parameter. If I make the test in this way, I initialize FSUIPC with this configuration and when I press A on the CDU, letter A is display correctly on CDU but if I press for the second time or for the third time on A, it does not occur anything any more. It is identical which I notch No repeats or not. If I add offset 70205 in the section Control key hand feels When released with parameter 0, then with each striking on key A, the A is displayed 2 times on the screen of CDU. And it is similar which I notch or not No repeats. I have this same problem on all the keys of CDU (letters and functions). In the FSUIPC4.ini : [Keys] " " " " 111=N121,10,70205,1,70205,0 " " " I browsed many forums but I did not find any information regarding this problem. Maybe I missed. In addition, my English in not so good. It does not help me. Thank you in advance for your replay. Cordially