DaveSimBuildGuy Posted December 6, 2014 Report Share Posted December 6, 2014 Hello, I'm trying to assign the "OBS" function of a VOR display and am having some problems. What I am getting is incremental jumps, a degree at a time, and then monster leaps of many degrees at a time. I understand this to be a function of FSX, but is there a way to reign it in through FSUIPC? I'm not yet at the Lua programming or Offset use phase. At the moment, all I know how to do is assign FSX or FSUIPC commands from the drop downs. I need this for a rotary encoder. I need it to increase or decrease only one degree at a time. As always, all help very much appreciated. Cheers Dave Link to comment Share on other sites More sharing options...
DaveSimBuildGuy Posted December 6, 2014 Author Report Share Posted December 6, 2014 Ohhhhhhh, thank you, Google :) You too, Mr. Dowson. Found it under Miscellaneous "fix control acceleration." Cheers Dave Link to comment Share on other sites More sharing options...
DaveSimBuildGuy Posted December 6, 2014 Author Report Share Posted December 6, 2014 Ok, no... That was short lived. Still the same problem :( Link to comment Share on other sites More sharing options...
Pete Dowson Posted December 6, 2014 Report Share Posted December 6, 2014 I'm trying to assign the "OBS" function of a VOR display and am having some problems. What I am getting is incremental jumps, a degree at a time, and then monster leaps of many degrees at a time. I understand this to be a function of FSX, but is there a way to reign it in through FSUIPC? I'm not yet at the Lua programming or Offset use phase. At the moment, all I know how to do is assign FSX or FSUIPC commands from the drop downs. I need this for a rotary encoder. I need it to increase or decrease only one degree at a time. As always, all help very much appreciated. You will need to be more specific. Exactly how are you assigning it? Pete Link to comment Share on other sites More sharing options...
DaveSimBuildGuy Posted December 7, 2014 Author Report Share Posted December 7, 2014 Exact process for choosing the OBS decrement function of VOR1. 1. Bring up FSUIPC 2. Choose "Buttons + Switches tab 3. Check "Profile Specific" 4. Twist the encoder left 5. Check "Select for FS Control." and click drop down. 6. Select "Vor1 Obi Dec." I also have an interesting situation occurring with 3 of my encoders. They're all connected to the same board as the other encoders, but FSUIPC cannot see them to assign a function, also, FSX won't see them. Strangely enough, the FSUIPC log DOES see them, and they have functions assigned that work in FSX. I haven't seen anything like this before. They also can't be seen in Windows USB game controller settings. Cheers Dave Link to comment Share on other sites More sharing options...
Pete Dowson Posted December 7, 2014 Report Share Posted December 7, 2014 Exact process for choosing the OBS decrement function of VOR1. 1. Bring up FSUIPC 2. Choose "Buttons + Switches tab 3. Check "Profile Specific" 4. Twist the encoder left 5. Check "Select for FS Control." and click drop down. 6. Select "Vor1 Obi Dec." Okay -- without "repeat whilst held" and nbo assignment to button release? In that case it will send one such control on each "on" pulse from the encoder. If you turn it slowly it should decrease one step per click. I have encoders set up like this and they work fine. If you turn them fast then of course you will get multiple clicks and FS will respond to the fast arriving controls appropriately. I also have an interesting situation occurring with 3 of my encoders. They're all connected to the same board as the other encoders, but FSUIPC cannot see them to assign a function, also, FSX won't see them. Strangely enough, the FSUIPC log DOES see them, and they have functions assigned that work in FSX. I haven't seen anything like this before. They also can't be seen in Windows USB game controller settings. FSUIPC and FSX both use the same set of functions in Windows to read joystick type devices. If Windows doesn't see them then neither will FS nor FSUIPC. So how did you get them assigned in FSX, and what identification does FSX give them in its assignments? And for that matter, how are they logged by FSUIPC? What joystick number and button number? Or are you only talking about FSUIPC's logging of the event being caused, not the buttons themselves? Pete Link to comment Share on other sites More sharing options...
DaveSimBuildGuy Posted December 7, 2014 Author Report Share Posted December 7, 2014 Thanks Pete, I'll check hothouse two conditions you mentioned. Certainly, I'm turning them slowly, one click at a time. The things just weren't built for anything more. As to the 3 rogue encoders, they were never given an assignment by a human being. The machine is freshly set up, new software, all new installations and nothing carried over. I was concerned the encoders were no good, as I could register a pulse with any of the others in the Windows USB game controllers configuration. Similarly, I checked FSUIPC to assign, and same. They didn't registers. That's when it got interesting. I was playing around with all the encoders and quite accidentally, twisted the nob the should be the Pilot side Heading Bug. And there it went, just as it was supposed to. I went back to Windows and FSUIPC and same result, nothing. Next, I started up the log and started watching the text roll. When I twisted the heading but encoder, sure enough, FSUIPC saw and reported it correctly as Heading Bug Inc/Dec. It reported the other errant encoders as "vor1 set," which will,one day be assigned course bug, and the other, for Baro, as "Kohlsman." Back to buttons assignment I went, and nothing. Zip. Back to Windows and nothing. I checked FSX controls for any assignments that may have magically appeared, nothing. Full-on flummoxed. One thing I did notice... The Course (OBS) bug, when set to "Vor1 set" behaved as I would like "vor1 obi inc/dec" to behave, only it only goes in one direction, regardless of the direction of the twist. One degree increments. Is there any way to make that one goes both ways, or forget it and keep, working on "vor1 obi inc/dec?" By the way, I very much appreciate your personal responses to these assistance requests. It is rare. Cheers Dave Link to comment Share on other sites More sharing options...
Pete Dowson Posted December 8, 2014 Report Share Posted December 8, 2014 As to the 3 rogue encoders, they were never given an assignment by a human being. The machine is freshly set up, new software, all new installations and nothing carried over. I was concerned the encoders were no good, as I could register a pulse with any of the others in the Windows USB game controllers configuration. Similarly, I checked FSUIPC to assign, and same. They didn't registers. That's when it got interesting. I was playing around with all the encoders and quite accidentally, twisted the nob the should be the Pilot side Heading Bug. And there it went, just as it was supposed to. I went back to Windows and FSUIPC and same result, nothing. Well, in the assignments list in FSX it will tell you which joystick device and which button numbers they are. If it doesn't then they are not being assigned in FSX, but being sent directly by another piece of software -- perhaps some driver you don't realise you have running. From what you are saying that sounds the most likely. Either that, or they are actually producing keystrokes -- try FSUIPC's button and keypress logging. Next, I started up the log and started watching the text roll. When I twisted the heading but encoder, sure enough, FSUIPC saw and reported it correctly as Heading Bug Inc/Dec. It reported the other errant encoders as "vor1 set," which will,one day be assigned course bug, and the other, for Baro, as "Kohlsman." Yes, all that means is that FSUIPC is detecting the controls arriving in FSX. It isn't logging button detection, just the controls. As you say, it isn't seeing the buttons.. Pete Link to comment Share on other sites More sharing options...
DaveSimBuildGuy Posted December 8, 2014 Author Report Share Posted December 8, 2014 The only thing I could think of would be the Elite drivers package for the avionics. It doesn't allow for much customisation, and I'm thinking it might some how have gotten hold of the two based on how they were wired to their respective boards. The unit has too many boards. I'll start troubleshooting. Thanks for the input. Cheers Dave. Link to comment Share on other sites More sharing options...
DaveSimBuildGuy Posted December 9, 2014 Author Report Share Posted December 9, 2014 G'day Pete, Still no luck. I brought a generic, known good encoder out to troubleshoot and have the same problems. Set to VOR1 Obi Inc/Dec. I've also set the heading bug up the same way, and it is behaving the same way. Not jumping an increment, but up to 10° at a time, randomly. This has nothing to do with the speed at which the encoder is being twisted. I'm doing so very slowly. I am experiencing the same problem when manipulation the course or heading bug with a keyboard shortcut. Strangely, those rogue encoders are working just fine for heading bug and Kohlsman, though FSUIPC see that as Heading Bug Set and Kohlsman set, yet it works the way it should. Here is a portion of the log showing those encoders. I guess I'm hoping you might recognize the behaviour so I can hunt down whatever is controlling their function. Again... Not FSX, not FSUIPC, and not seen in windows USB Game controllers. 832796 *** EVENT: Cntrl= 65716 (0x000100b4), Param= 339 (0x00000153) VOR1_SET 833155 *** EVENT: Cntrl= 65716 (0x000100b4), Param= 338 (0x00000152) VOR1_SET 833295 *** EVENT: Cntrl= 65716 (0x000100b4), Param= 337 (0x00000151) VOR1_SET 834559 *** EVENT: Cntrl= 65716 (0x000100b4), Param= 336 (0x00000150) VOR1_SET 834996 *** EVENT: Cntrl= 65716 (0x000100b4), Param= 335 (0x0000014f) VOR1_SET 835635 *** EVENT: Cntrl= 65716 (0x000100b4), Param= 334 (0x0000014e) VOR1_SET 838584 *** EVENT: Cntrl= 65716 (0x000100b4), Param= 333 (0x0000014d) VOR1_SET 839052 *** EVENT: Cntrl= 65716 (0x000100b4), Param= 332 (0x0000014c) VOR1_SET 844387 *** EVENT: Cntrl= 66040 (0x000101f8), Param= 16207 (0x00003f4f) KOHLSMAN_SET 844481 *** EVENT: Cntrl= 66040 (0x000101f8), Param= 16204 (0x00003f4c) KOHLSMAN_SET 844590 *** EVENT: Cntrl= 66040 (0x000101f8), Param= 16201 (0x00003f49) KOHLSMAN_SET 844621 *** EVENT: Cntrl= 66040 (0x000101f8), Param= 16198 (0x00003f46) KOHLSMAN_SET 844715 *** EVENT: Cntrl= 66040 (0x000101f8), Param= 16195 (0x00003f43) KOHLSMAN_SET 845417 *** EVENT: Cntrl= 66040 (0x000101f8), Param= 16198 (0x00003f46) KOHLSMAN_SET 845495 *** EVENT: Cntrl= 66040 (0x000101f8), Param= 16201 (0x00003f49) KOHLSMAN_SET 845588 *** EVENT: Cntrl= 66040 (0x000101f8), Param= 16204 (0x00003f4c) KOHLSMAN_SET 845760 *** EVENT: Cntrl= 66040 (0x000101f8), Param= 16207 (0x00003f4f) KOHLSMAN_SET 848505 *** EVENT: Cntrl= 66042 (0x000101fa), Param= 94 (0x0000005e) HEADING_BUG_SET 848599 *** EVENT: Cntrl= 66042 (0x000101fa), Param= 93 (0x0000005d) HEADING_BUG_SET 848677 *** EVENT: Cntrl= 66042 (0x000101fa), Param= 92 (0x0000005c) HEADING_BUG_SET 849613 *** EVENT: Cntrl= 66042 (0x000101fa), Param= 93 (0x0000005d) HEADING_BUG_SET 849675 *** EVENT: Cntrl= 66042 (0x000101fa), Param= 94 (0x0000005e) HEADING_BUG_SET 849785 *** EVENT: Cntrl= 66042 (0x000101fa), Param= 95 (0x0000005f) HEADING_BUG_SET 849816 *** EVENT: Cntrl= 66042 (0x000101fa), Param= 96 (0x00000060) HEADING_BUG_SET 849909 *** EVENT: Cntrl= 66042 (0x000101fa), Param= 97 (0x00000061) HEADING_BUG_SET And the following will be for first heading bug and vor1 obi on the known, good encoders: 77984 [buttons] now profile-specific: 77984 47=P0,21,K67,10 77984 102=P2,15,K66,10 88093 Button changed: bRef=0, Joy=5, Btn=1, Pressed 88093 [buttons.Eurocopter BK-117 Final Edition ADAC Auxtank] 103=P5,1,C65880,0 88093 FS Control Sent: Ctrl=65880, Param=0 88156 Button changed: bRef=0, Joy=5, Btn=1, Released 88359 Button changed: bRef=0, Joy=5, Btn=1, Pressed 88359 [buttons.Eurocopter BK-117 Final Edition ADAC Auxtank] 103=P5,1,C65880,0 88359 FS Control Sent: Ctrl=65880, Param=0 88390 Button changed: bRef=0, Joy=5, Btn=1, Released 89731 Button changed: bRef=0, Joy=5, Btn=1, Pressed 89731 [buttons.Eurocopter BK-117 Final Edition ADAC Auxtank] 103=P5,1,C65880,0 89731 FS Control Sent: Ctrl=65880, Param=0 89794 Button changed: bRef=0, Joy=5, Btn=1, Released 90137 Button changed: bRef=0, Joy=5, Btn=1, Pressed 90137 [buttons.Eurocopter BK-117 Final Edition ADAC Auxtank] 103=P5,1,C65880,0 90137 FS Control Sent: Ctrl=65880, Param=0 90168 Button changed: bRef=0, Joy=5, Btn=1, Released 91245 Button changed: bRef=0, Joy=5, Btn=1, Pressed 91245 [buttons.Eurocopter BK-117 Final Edition ADAC Auxtank] 103=P5,1,C65880,0 91245 FS Control Sent: Ctrl=65880, Param=0 91307 Button changed: bRef=0, Joy=5, Btn=1, Released 92103 Button changed: bRef=0, Joy=5, Btn=1, Pressed 92103 [buttons.Eurocopter BK-117 Final Edition ADAC Auxtank] 103=P5,1,C65880,0 92103 FS Control Sent: Ctrl=65880, Param=0 92149 Button changed: bRef=0, Joy=5, Btn=1, Released 94723 Button changed: bRef=0, Joy=5, Btn=2, Pressed 94723 [buttons.Eurocopter BK-117 Final Edition ADAC Auxtank] 106=P5,2,C65663,0 94723 FS Control Sent: Ctrl=65663, Param=0 94786 Button changed: bRef=0, Joy=5, Btn=2, Released 94895 Button changed: bRef=0, Joy=5, Btn=2, Pressed 94895 [buttons.Eurocopter BK-117 Final Edition ADAC Auxtank] 106=P5,2,C65663,0 94895 FS Control Sent: Ctrl=65663, Param=0 94926 Button changed: bRef=0, Joy=5, Btn=2, Released 95862 Button changed: bRef=0, Joy=5, Btn=2, Pressed 95862 [buttons.Eurocopter BK-117 Final Edition ADAC Auxtank] 106=P5,2,C65663,0 95862 FS Control Sent: Ctrl=65663, Param=0 95893 Button changed: bRef=0, Joy=5, Btn=2, Released 96003 Button changed: bRef=0, Joy=5, Btn=2, Pressed 96003 [buttons.Eurocopter BK-117 Final Edition ADAC Auxtank] 106=P5,2,C65663,0 96003 FS Control Sent: Ctrl=65663, Param=0 96034 Button changed: bRef=0, Joy=5, Btn=2, Released 96970 Button changed: bRef=0, Joy=5, Btn=2, Pressed 96970 [buttons.Eurocopter BK-117 Final Edition ADAC Auxtank] 106=P5,2,C65663,0 96970 FS Control Sent: Ctrl=65663, Param=0 97017 Button changed: bRef=0, Joy=5, Btn=2, Released 97079 Button changed: bRef=0, Joy=5, Btn=2, Pressed 97079 [buttons.Eurocopter BK-117 Final Edition ADAC Auxtank] 106=P5,2,C65663,0 97079 FS Control Sent: Ctrl=65663, Param=0 97110 Button changed: bRef=0, Joy=5, Btn=2, Released 98452 Button changed: bRef=0, Joy=5, Btn=2, Pressed 98452 [buttons.Eurocopter BK-117 Final Edition ADAC Auxtank] 106=P5,2,C65663,0 98452 FS Control Sent: Ctrl=65663, Param=0 98483 Button changed: bRef=0, Joy=5, Btn=2, Released 98561 Button changed: bRef=0, Joy=5, Btn=2, Pressed 98561 [buttons.Eurocopter BK-117 Final Edition ADAC Auxtank] 106=P5,2,C65663,0 98561 FS Control Sent: Ctrl=65663, Param=0 98623 Button changed: bRef=0, Joy=5, Btn=2, Released 99996 Button changed: bRef=0, Joy=5, Btn=2, Pressed 99996 [buttons.Eurocopter BK-117 Final Edition ADAC Auxtank] 106=P5,2,C65663,0 99996 FS Control Sent: Ctrl=65663, Param=0 100027 Button changed: bRef=0, Joy=5, Btn=2, Released 100105 Button changed: bRef=0, Joy=5, Btn=2, Pressed 100105 [buttons.Eurocopter BK-117 Final Edition ADAC Auxtank] 106=P5,2,C65663,0 100105 FS Control Sent: Ctrl=65663, Param=0 100137 Button changed: bRef=0, Joy=5, Btn=2, Released 101572 Button changed: bRef=0, Joy=5, Btn=2, Pressed 101572 [buttons.Eurocopter BK-117 Final Edition ADAC Auxtank] 106=P5,2,C65663,0 101572 FS Control Sent: Ctrl=65663, Param=0 101650 Button changed: bRef=0, Joy=5, Btn=2, Released 101775 Button changed: bRef=0, Joy=5, Btn=2, Pressed 101775 [buttons.Eurocopter BK-117 Final Edition ADAC Auxtank] 106=P5,2,C65663,0 101775 FS Control Sent: Ctrl=65663, Param=0 101806 Button changed: bRef=0, Joy=5, Btn=2, Released 104224 Button changed: bRef=0, Joy=5, Btn=2, Pressed 104224 [buttons.Eurocopter BK-117 Final Edition ADAC Auxtank] 106=P5,2,C65663,0 104224 FS Control Sent: Ctrl=65663, Param=0 104255 Button changed: bRef=0, Joy=5, Btn=2, Released 104364 Button changed: bRef=0, Joy=5, Btn=2, Pressed 104364 [buttons.Eurocopter BK-117 Final Edition ADAC Auxtank] 106=P5,2,C65663,0 104364 FS Control Sent: Ctrl=65663, Param=0 104395 Button changed: bRef=0, Joy=5, Btn=2, Released 107110 Button changed: bRef=0, Joy=5, Btn=2, Pressed 107110 [buttons.Eurocopter BK-117 Final Edition ADAC Auxtank] 106=P5,2,C65663,0 107110 FS Control Sent: Ctrl=65663, Param=0 107141 Button changed: bRef=0, Joy=5, Btn=2, Released 107313 Button changed: bRef=0, Joy=5, Btn=2, Pressed 107313 [buttons.Eurocopter BK-117 Final Edition ADAC Auxtank] 106=P5,2,C65663,0 107313 FS Control Sent: Ctrl=65663, Param=0 107375 Button changed: bRef=0, Joy=5, Btn=2, Released 110635 Button changed: bRef=0, Joy=5, Btn=2, Pressed 110635 [buttons.Eurocopter BK-117 Final Edition ADAC Auxtank] 106=P5,2,C65663,0 110635 FS Control Sent: Ctrl=65663, Param=0 110698 Button changed: bRef=0, Joy=5, Btn=2, Released 110838 Button changed: bRef=0, Joy=5, Btn=2, Pressed 110838 [buttons.Eurocopter BK-117 Final Edition ADAC Auxtank] 106=P5,2,C65663,0 110838 FS Control Sent: Ctrl=65663, Param=0 110869 Button changed: bRef=0, Joy=5, Btn=2, Released 112008 Button changed: bRef=0, Joy=5, Btn=2, Pressed 112008 [buttons.Eurocopter BK-117 Final Edition ADAC Auxtank] 106=P5,2,C65663,0 112008 FS Control Sent: Ctrl=65663, Param=0 112071 Button changed: bRef=0, Joy=5, Btn=2, Released 112804 Button changed: bRef=0, Joy=5, Btn=2, Pressed 112804 [buttons.Eurocopter BK-117 Final Edition ADAC Auxtank] 106=P5,2,C65663,0 112819 FS Control Sent: Ctrl=65663, Param=0 112851 Button changed: bRef=0, Joy=5, Btn=2, Released 113911 Button changed: bRef=0, Joy=5, Btn=2, Pressed 113927 [buttons.Eurocopter BK-117 Final Edition ADAC Auxtank] 106=P5,2,C65663,0 113927 FS Control Sent: Ctrl=65663, Param=0 113989 Button changed: bRef=0, Joy=5, Btn=2, Released 114021 Button changed: bRef=0, Joy=5, Btn=2, Pressed 114021 [buttons.Eurocopter BK-117 Final Edition ADAC Auxtank] 106=P5,2,C65663,0 114021 FS Control Sent: Ctrl=65663, Param=0 114083 Button changed: bRef=0, Joy=5, Btn=2, Released 128014 Sim stopped: average frame rate for last 50 secs = 29.8 fps 135908 System time = 09/12/2014 23:49:43, Simulator time = 12:06:44 (02:06Z) 135908 *** FSUIPC log file being closed I've got a video coming if I can ever get the bloody thing upload to YouTube Cheers Dave Link to comment Share on other sites More sharing options...
Pete Dowson Posted December 9, 2014 Report Share Posted December 9, 2014 Still no luck. I brought a generic, known good encoder out to troubleshoot and have the same problems. Set to VOR1 Obi Inc/Dec. I've also set the heading bug up the same way, and it is behaving the same way. Not jumping an increment, but up to 10° at a time, randomly. This has nothing to do with the speed at which the encoder is being twisted. I'm doing so very slowly. I am experiencing the same problem when manipulation the course or heading bug with a keyboard shortcut. Is this with specific aircraft or all? Normally the acceleration, to 10's for instance, is part of FS's inbuilt control acceleration facility, to get to very different values quickly. It is instigated by seing two of the same controls successively -- like double taps on the keyboard instead of definitely separate taps. Strangely, those rogue encoders are working just fine for heading bug and Kohlsman, though FSUIPC see that as Heading Bug Set and Kohlsman set, yet it works the way it should. Here is a portion of the log showing those encoders. I guess I'm hoping you might recognize the behaviour so I can hunt down whatever is controlling their function. Again... Not FSX, not FSUIPC, and not seen in windows USB Game controllers. Your Elite driver, or whatever you have operating those controls, is doing the value increments/decrements internally and writing the resulting values. That is a much more reliable and smooth way of dealing with such instrumentation, and most of my controls are like that -- using my own drivers. And the following will be for first heading bug and vor1 obi on the known, good encoders: Okay. So look: 88093 Button changed: bRef=0, Joy=5, Btn=1, Pressed 88093 [buttons.Eurocopter BK-117 Final Edition ADAC Auxtank] 103=P5,1,C65880,0 88093 FS Control Sent: Ctrl=65880, Param=0 88156 Button changed: bRef=0, Joy=5, Btn=1, Released 200 mSec gap before next "click" 88359 Button changed: bRef=0, Joy=5, Btn=1, Pressed 88359 [buttons.Eurocopter BK-117 Final Edition ADAC Auxtank] 103=P5,1,C65880,0 88359 FS Control Sent: Ctrl=65880, Param=0 88390 Button changed: bRef=0, Joy=5, Btn=1, Released Over 1 second gap before next "click" 89731 Button changed: bRef=0, Joy=5, Btn=1, Pressed 89731 [buttons.Eurocopter BK-117 Final Edition ADAC Auxtank] 103=P5,1,C65880,0 89731 FS Control Sent: Ctrl=65880, Param=0 89794 Button changed: bRef=0, Joy=5, Btn=1, Released About 240 mSec gap before next "click". etc etc You appear to be turning it too fast. One click = one increment or decrement. You might also want to make sure you have "Fix control acceleration" enabled in FSUIPC (on the Miscellaneous Tab). This fixes a bug in FS where it does sometimes accelerate changes when it shouldn't I've got a video coming if I can ever get the bloody thing upload to YouTube I don't want to watch videos, sorry. Pete Link to comment Share on other sites More sharing options...
DaveSimBuildGuy Posted December 9, 2014 Author Report Share Posted December 9, 2014 All aircraft, across two PC's. No, Pete, I'm not turning them too fast. I thought I was quite clear about that. Oh, and yes, the "fix control acceleration" option was selected. I found an alternate fix and am good to go. Thanks for your time. Link to comment Share on other sites More sharing options...
Pete Dowson Posted December 10, 2014 Report Share Posted December 10, 2014 All aircraft, across two PC's. No, Pete, I'm not turning them too fast. I thought I was quite clear about that. Oh, and yes, the "fix control acceleration" option was selected. I found an alternate fix and am good to go. Thanks for your time. As the log shows, there is only 200 milliseconds or so between the "clicks". What do you think is slow about that? Pete Link to comment Share on other sites More sharing options...
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now