jennik

Confirmed: forgotten CH gameport drivers. After uninstall and win restart everything works well. Thanks so much for the tip!

Thanks so much, this might be the problem, i have been using gameport CH Pro Pedals and now flying with USB pedals. I didnt uninstall all GP drivers. I will take a look on it.

This never happened to me before but now. I reinstalled everything and have almost clear MFS 9.1 installation. There is only few addons like UT-E and several airplane addons there (PIC, PSS) + latest IVAO install. FSUIPC is latest version 3.75 and registered. When i run FSUIPC to set up buttons it freezes. It works well until I choose the buttons tab - then the whole FS with FSUIPC on the top freeze and does not respond for long time until i shut it off by task manager. I have a lot of HW connected: Saitek X-52, CH products MFD, TQ, Yoke and PRO pedals (all USB), Track IR 4 Pro, so mayby the reason is somewhere there, i have no idea... Anybody here met already this issue? Thanks for reply.

This is perfectly clear for me already and there is no need to explain it more simple then it actualy is :) Oh, i though there is only "Kohlsman set" option to choose in the list, i missed those "inc" and "dec" options so i though something more complicated has to be set to do this. Exactly nothing.. you are right. That wos only my mistake, sorry and thanks for answer.

Hi Pete, hi all, this is my idea: I have the Mjoy16 USB device with apx. 30 pushbuttons and switches to control various options in FS via FSUIPC. Its working pretty good. There are also 4 rotary switches (encoders), still used for HDG, ALT and CRS setting. I would like to use one rotary encoder for QNH setting (barometric pressure setting on altitude gauge). Now i know that FSUIPC can be used to set it as one exact volue. But i would like to set alt press by increments up and down by apx. 0.01 InHg or 1 hPa. Could you help me how to solve this? Unfortunately, i am not able to understand any advanced informations in FSUIPC manual. So if there is some simple solution, please, write me some "step by step" manual.... Thanks so much Jennik

Dear Pete, I have to apologize... I have upgraded to newest FSUIPC version and everything works fine now... Sorry for wasting your time :) Jennik

Sorry - the buttons are: No. 16 - turning slowly to the left - Heading Bug Dec assigned No. 24 - turning fast to the left - Heading Bug Dec Fast assigned No. 17 - turning slowly to the right - Heading Bug Inc assigned No. 25 - turning fast to the right - Heading Bug Inc Fast assigned

Sorry, see now the words wrapping: Another part of log file: 5657203 *** EVENT: Cntrl= 65879 (0x00010157), Param= 0 (0x00000000) HEADING_BUG_INC 5657250 Button changed: bRef=0, Joy=1, Btn=17, Released 5657609 Button changed: bRef=0, Joy=1, Btn=17, Pressed 5657609 [Buttons] 26=P1,17,C65879,0 5657609 FS Control Sent: Ctrl=65879, Param=0 5657609 Button changed: bRef=0, Joy=1, Btn=25, Pressed 5657609 [Buttons] 28=P1,25,C1025,0 5657609 FSUIPC Control Action: Ctrl=1025, Param=0 5657609 *** EVENT: Cntrl= 65879 (0x00010157), Param= 0 (0x00000000) HEADING_BUG_INC 5657656 Button changed: bRef=0, Joy=1, Btn=17, Released 5657656 Button changed: bRef=0, Joy=1, Btn=25, Released 5657687 Button changed: bRef=0, Joy=1, Btn=25, Pressed 5657687 [Buttons] 28=P1,25,C1025,0 5657687 FSUIPC Control Action: Ctrl=1025, Param=0 5657734 Button changed: bRef=0, Joy=1, Btn=25, Released 5657781 Button changed: bRef=0, Joy=1, Btn=17, Pressed 5657781 [Buttons] 26=P1,17,C65879,0 5657781 FS Control Sent: Ctrl=65879, Param=0 5657781 *** EVENT: Cntrl= 65879 (0x00010157), Param= 0 (0x00000000) HEADING_BUG_INC 5657812 Button changed: bRef=0, Joy=1, Btn=17, Released 5658218 Button changed: bRef=0, Joy=1, Btn=17, Pressed 5658218 [Buttons] 26=P1,17,C65879,0 5658218 FS Control Sent: Ctrl=65879, Param=0 5658218 *** EVENT: Cntrl= 65879 (0x00010157), Param= 0 (0x00000000) HEADING_BUG_INC 5658265 Button changed: bRef=0, Joy=1, Btn=17, Released 5658296 Button changed: bRef=0, Joy=1, Btn=25, Pressed 5658296 [Buttons] 28=P1,25,C1025,0 5658296 FSUIPC Control Action: Ctrl=1025, Param=0 5658343 Button changed: bRef=0, Joy=1, Btn=25, Released 5658390 Button changed: bRef=0, Joy=1, Btn=25, Pressed 5658390 [Buttons] 28=P1,25,C1025,0 5658390 FSUIPC Control Action: Ctrl=1025, Param=0 5658437 Button changed: bRef=0, Joy=1, Btn=25, Released 5658468 Button changed: bRef=0, Joy=1, Btn=17, Pressed 5658468 [Buttons] 26=P1,17,C65879,0 5658468 FS Control Sent: Ctrl=65879, Param=0 5658468 *** EVENT: Cntrl= 65879 (0x00010157), Param= 0 (0x00000000) HEADING_BUG_INC 5658515 Button changed: bRef=0, Joy=1, Btn=17, Released 5659046 Button changed: bRef=0, Joy=1, Btn=16, Pressed 5659046 [Buttons] 10=P1,16,C65880,0 5659046 FS Control Sent: Ctrl=65880, Param=0 5659046 *** EVENT: Cntrl= 65880 (0x00010158), Param= 0 (0x00000000) HEADING_BUG_DEC 5659078 Button changed: bRef=0, Joy=1, Btn=16, Released 5659125 Button changed: bRef=0, Joy=1, Btn=16, Pressed 5659125 [Buttons] 10=P1,16,C65880,0 5659125 FS Control Sent: Ctrl=65880, Param=0 This is the part of log, when the "jumping back to ZERO" is happened. I have to say another thing - sometimes the movement of the rotary coder is not translated correctly and reports "fast" button press instead of "slow". Rarely the oposite direction button press is generated too. So i should to expect the HDG bug can step sometimes back a little bit. But why directly back to zero?... How. It is late today, i have to go sleep now, tired after the hard week. I would like to read your documentation more precise and then I could post soem more usefull information. Thanks jennik

Ok, no problem, i will prepare detailed documentation for precise analyze ;) Thanks for your time :)

now its correct

Oh, I wonder about whats in that log file :) See: I have performed several slow turns when the HDG bug turned by 1° steps from 0 to 90. Then I turn the knob faster and the bug jumped back to 0. Here is the expample of one of these slow steps: HEADING_BUG_INC 3331234 Button changed: bRef=0, Joy=1, Btn=17, Released 3331312 Button changed: bRef=0, Joy=1, Btn=17, Pressed 3331312 [Buttons] 26=P1,17,C65879,0 3331312 FS Control Sent: Ctrl=65879, Param=0 3331312 *** EVENT: Cntrl= 65879 (0x00010157), Param= 0 (0x00000000) But when the fast function was activated, it seems there were a lot of DEC commands was send... here is the last "slow" step and see whats happened then. I never turned the knob to the left... HEADING_BUG_INC 3051062 Button changed: bRef=0, Joy=1, Btn=17, Released 3051296 Button changed: bRef=0, Joy=1, Btn=16, Pressed 3051296 [Buttons] 10=P1,16,C65880,0 3051296 FS Control Sent: Ctrl=65880, Param=0 3051296 *** EVENT: Cntrl= 65880 (0x00010158), Param= 0 (0x00000000) HEADING_BUG_DEC 3051343 Button changed: bRef=0, Joy=1, Btn=16, Released 3051343 Button changed: bRef=0, Joy=1, Btn=24, Pressed 3051343 [Buttons] 27=P1,24,C65880,0 3051343 FS Control Sent: Ctrl=65880, Param=0 3051343 *** EVENT: Cntrl= 65880 (0x00010158), Param= 0 (0x00000000) HEADING_BUG_DEC 3051375 Button changed: bRef=0, Joy=1, Btn=24, Released 3051437 Button changed: bRef=0, Joy=1, Btn=24, Pressed 3051437 [Buttons] 27=P1,24,C65880,0 3051437 FS Control Sent: Ctrl=65880, Param=0 3051437 *** EVENT: Cntrl= 65880 (0x00010158), Param= 0 (0x00000000) HEADING_BUG_DEC 3051484 Button changed: bRef=0, Joy=1, Btn=24, Released 3051687 Button changed: bRef=0, Joy=1, Btn=16, Pressed 3051687 [Buttons] 10=P1,16,C65880,0 3051687 FS Control Sent: Ctrl=65880, Param=0 3051687 *** EVENT: Cntrl= 65880 (0x00010158), Param= 0 (0x00000000) HEADING_BUG_DEC 3051718 Button changed: bRef=0, Joy=1, Btn=16, Released 3051718 Button changed: bRef=0, Joy=1, Btn=24, Pressed 3051718 [Buttons] 27=P1,24,C65880,0 3051718 FS Control Sent: Ctrl=65880, Param=0 3051718 *** EVENT: Cntrl= 65880 (0x00010158), Param= 0 (0x00000000) And, here is the example how the VOR1 Obi Fast Dec/Inc works fine: VOR1_OBI_INC 3899734 Button changed: bRef=0, Joy=1, Btn=19, Released 3900515 Button changed: bRef=0, Joy=1, Btn=19, Pressed 3900515 [Buttons] 16=P1,19,C65663,0 3900515 FS Control Sent: Ctrl=65663, Param=0 3900515 *** EVENT: Cntrl= 65663 (0x0001007f), Param= 0 (0x00000000) VOR1_OBI_INC 3900546 Button changed: bRef=0, Joy=1, Btn=19, Released 3900546 Button changed: bRef=0, Joy=1, Btn=27, Pressed 3900546 [Buttons] 18=P1,27,C66368,0 3900546 FS Control Sent: Ctrl=66368, Param=0 3900546 *** EVENT: Cntrl= 66368 (0x00010340), Param= 0 (0x00000000) VOR1_OBI_FAST_INC 3900640 Button changed: bRef=0, Joy=1, Btn=27, Released 3900671 Button changed: bRef=0, Joy=1, Btn=27, Pressed 3900671 [Buttons] 18=P1,27,C66368,0 3900671 FS Control Sent: Ctrl=66368, Param=0 3900671 *** EVENT: Cntrl= 66368 (0x00010340), Param= 0 (0x00000000) VOR1_OBI_FAST_INC 3900718 Button changed: bRef=0, Joy=1, Btn=19, Pressed 3900718 [Buttons] 16=P1,19,C65663,0 3900718 FS Control Sent: Ctrl=65663, Param=0 3900718 Button changed: bRef=0, Joy=1, Btn=27, Released 3900718 *** EVENT: Cntrl= 65663 (0x0001007f), Param= 0 (0x00000000)

I have also trying to use that Slow/Fast feature of Mjoy for NAV Radio control. The slow steps controles -.xx part of the frequency and the fast controles whole frq. 1XX.- It works nice :)

Like I said i am using MJoy16 USB device. Each rotary coder connected via that device produces 4 button presses depends on rotation speed and direction. Normal "slow" speed generates "button presses" appx 0-10 times per second. Any faster rotation generates different button presses, but it looks its no faster then appx 20times per sec. In fact, it doesnt work as precise as it sounds. When you rotate the coder fast, mainly the "fast" and sometimes the "slow" button press ocures. I have tryed it ones more with default Boeing 737 and CRS control: 1) when VOR1 Obi Fast Inc/Dec is assigned for the "Fast pushbuttons" it works perfectly. 2) when VOR1 Obi Inc/Dec Fast is used for "Fast" presses - its useless - the bearing needle stays controlable by slow steps by 1° but anytime some "fast" buttonpress appears - it activates VOR1 Obi Inc/Dec Fast function and then the needle jumps back to ZERO. It seems what i only need is the Heading Bug Fast Inc/Dec function instead of the only available Heading Bug Inc/Dec Fast which works the same way as desribed with VOR1 Obi... Next time i will try to log the events and send you the report whats happened within FSUIPC and FS. Thanks Jennik

Ok, i have to review all when at home, now i cant check it. Thanks

Thanks for so fast reply :) Oh, my poore english... I am sure, i have assigned the "Fast" functions correctly - It works with CRS bug right. the effect of HDG Fast function looks like that: When the coder is rotating slowly, bug moves by 1°steps to the right direction. When rotating quick, and the "Fast" command is performed, bug only jump over 10° to the side, then back. When you started with HDG 15°, then rotated HDG bug by 1°steps to the right to 90° and THEN tried to use Fast function, the bug jump back to the origin location between 10-20°. Thats what i remeber when I tried it last time. Ofcourse i turned it off, because of some reasons i dont remeber :) I will try that possibility. Thanks very much. Thats nothnig I would like to hear :) Iam absolutely unworthy with anything which souns like scripting or programming :) but i promiss - i try it.

Sorry, if that issue was already discussed here, there are many similar keywords to search and i didnt found it. I am using great USB controller MJoy by Mindaugas and there are four rotary encoders for use. But when I tried to asign them via FSUIPC, I found strange thing with HDG bug control: There are several commands for HDG bug - the most important is HDG bug Dec/Inc and HDG bug Dec/Inc Fast, just because i am using 20-step encoders and MJoy controller is able to send diferent pushbutton outputs depending on how fast are you turning by encoder. The first FSUIPC command HDG bug Dec/Inc works perfect, but something strange occures when HDG bug Dec/Inc Fast is used. The bug should go by 10° each step, but instead of that its only switching within two places on gauge... The important thing is the solution, how it works with CRS bug: There are more commands in FSUIPC for it and some of them looks like the same: VOR1 bearing Dec/Inc Fast or VOR1 bearing Fast Dec/Inc. The thrue is, that one of that two commands work perfect, and other by the same way as HDG works. My questions: 1) I thoungh that problem is somewhere in FS or FSUIPC, not with my encoders and MJoy controller - tell me please, how to control HDG bug by this way, please. i have perfectly working CRS bug control and absolutely useless HDG (try to turn DHG by 180° by 1° step on 20steps encoder :) ) 2) Another thing - is there any possibility to assign separately Batery ON/OFF of Toggle Master battery? There is only toggle function, not ON or OFF separately. The same occures with Alternator, Taxi lights etc. Thanks for reply Jennik