Tom Mc Posted June 24, 2013 Report Share Posted June 24, 2013 Peter, I am using FSUIPC 4.90 as an interface for Eflite 430 GPS & Reality Xp S/w. I have been chasing a popup problem an annoying pop-up problem with the eflite 430 h/w interface buttons launch an additional fsx window. I turned on fusipc logging and capture a diagnostic . (paraphrase - function not implemented passing on to FS). question: Can I dump the ipc data in hex? Do I have any control on what to do with these diagnostice - eg do not pass them on? Basically, what capabilities do I have using fsuipc as an ipc debugger? Tom (USA, Pennsylvania) Link to comment Share on other sites More sharing options...
Pete Dowson Posted June 24, 2013 Report Share Posted June 24, 2013 question: Can I dump the ipc data in hex? Please look at the logging tab. See the options to log IP reads and writes. That data IS logged in Hex. If you want to simply take a snapshot of the whole 65k range of offsets, enable the option to save it with flights (Miscellaneous tab, "Reload FSUIPC Data", any choice except 'Never') , and simply save a flight to create a binary dump. The file is named for the flight with "ipcbin" filetype. Otherwise check out FSInterrogate2, as supplied in the FSUIPC SDK. Another option, where you can select whatever you like to dump and when would be to use the Lua plug-in facilities and dump the data using your own Lua code. Do I have any control on what to do with these diagnostice - eg do not pass them on? Sorry, you'll need to explain what you mean here. Basically, what capabilities do I have using fsuipc as an ipc debugger? If by "ipc" you mean the same as the IPC in "FSUIPC", and your IPC data is going through FSUIPC, then you have all the tools you could possibly need. Pete Link to comment Share on other sites More sharing options...
Tom Mc Posted June 28, 2013 Author Report Share Posted June 28, 2013 Peter, Here is a short log of the eFlite 430 interaction.. I believe the KEYDOWN: events are what are causing the FSX unwanted popup behavior. One of these appears to trigger [WINDOW 8] in the Panel.cfg for any aircraft I fly. Not sure exactly where to go to understand the VK=nn assignments? I was hoping to use FSUIPC to intercept the event and not pass it on. I was reading through the .pdf on VRInsight (I realize this is not what I want but the functionality is attractive). There is a FILTER capability defined in there. This is the functionality I was hoping to mimic somehow. (I do not want to passon the KEYDOWN VK=nn which are not Programmed!) The KEYUP: VK=nn all work as expected. ********* FSUIPC4, Version 4.90 by Pete Dowson *********User Name="Tom McCaa"User Addr="tmccaa@csc.com"FSUIPC4 Key is providedWideFS7 Key is provided 3367031 System time = 27/06/2013 20:50:59, Simulator time = 08:53:43 (12:53Z)[Continuation log requested by user]Running inside FSXModule base=06060000 3370890 KEYDOWN: VK=16, Waiting=0, Repeat=N, Shifts=1 3370890 .. Key not programmed -- passed on to FS 3370890 KEYDOWN: VK=57, Waiting=0, Repeat=N, Shifts=1 3370890 .. Key not programmed -- passed on to FS 3370890 KEYDOWN: VK=123, Waiting=0, Repeat=N, Shifts=1 3370890 .. Key not programmed -- passed on to FS 3371047 KEYUP: VK=123, Waiting=0 3371047 KEYUP: VK=57, Waiting=0 3371047 KEYUP: VK=16, Waiting=0 3371484 KEYDOWN: VK=16, Waiting=0, Repeat=N, Shifts=1 3371484 .. Key not programmed -- passed on to FS 3371484 KEYDOWN: VK=57, Waiting=0, Repeat=N, Shifts=1 3371484 .. Key not programmed -- passed on to FS 3371484 KEYDOWN: VK=123, Waiting=0, Repeat=N, Shifts=1 3371484 .. Key not programmed -- passed on to FS 3371719 KEYUP: VK=123, Waiting=0 3371719 KEYUP: VK=57, Waiting=0 3371719 KEYUP: VK=16, Waiting=0 3371937 KEYDOWN: VK=16, Waiting=0, Repeat=N, Shifts=1 3371937 .. Key not programmed -- passed on to FS 3371937 KEYDOWN: VK=57, Waiting=0, Repeat=N, Shifts=1 3371937 .. Key not programmed -- passed on to FS 3372172 KEYUP: VK=124, Waiting=0 3372172 KEYUP: VK=57, Waiting=0 3372172 KEYUP: VK=16, Waiting=0 3372312 KEYDOWN: VK=16, Waiting=0, Repeat=N, Shifts=1 3372312 .. Key not programmed -- passed on to FS 3372312 KEYDOWN: VK=57, Waiting=0, Repeat=N, Shifts=1 3372312 .. Key not programmed -- passed on to FS 3372469 KEYUP: VK=124, Waiting=0 3372469 KEYUP: VK=57, Waiting=0 3372469 KEYUP: VK=16, Waiting=0 3373609 KEYDOWN: VK=16, Waiting=0, Repeat=N, Shifts=1 3373609 .. Key not programmed -- passed on to FS 3373609 KEYDOWN: VK=57, Waiting=0, Repeat=N, Shifts=1 3373609 .. Key not programmed -- passed on to FS 3373781 KEYUP: VK=122, Waiting=0 3373781 KEYUP: VK=57, Waiting=0 3373781 KEYUP: VK=16, Waiting=0 3373844 KEYDOWN: VK=16, Waiting=0, Repeat=N, Shifts=1 3373844 .. Key not programmed -- passed on to FS 3373844 KEYDOWN: VK=57, Waiting=0, Repeat=N, Shifts=1 3373844 .. Key not programmed -- passed on to FS 3374015 KEYUP: VK=122, Waiting=0 3374015 KEYUP: VK=57, Waiting=0 3374015 KEYUP: VK=16, Waiting=0 3374359 KEYDOWN: VK=16, Waiting=0, Repeat=N, Shifts=1 3374359 .. Key not programmed -- passed on to FS 3374359 KEYDOWN: VK=57, Waiting=0, Repeat=N, Shifts=1 3374359 .. Key not programmed -- passed on to FS 3374437 KEYUP: VK=121, Waiting=0 3374437 KEYUP: VK=57, Waiting=0 3374437 KEYUP: VK=16, Waiting=0 3374578 KEYDOWN: VK=16, Waiting=0, Repeat=N, Shifts=1 3374578 .. Key not programmed -- passed on to FS 3374578 KEYDOWN: VK=57, Waiting=0, Repeat=N, Shifts=1 3374578 .. Key not programmed -- passed on to FS 3374672 KEYUP: VK=121, Waiting=0 3374672 KEYUP: VK=57, Waiting=0 3374672 KEYUP: VK=16, Waiting=0 3375140 KEYDOWN: VK=16, Waiting=0, Repeat=N, Shifts=1 3375140 .. Key not programmed -- passed on to FS 3375140 KEYDOWN: VK=57, Waiting=0, Repeat=N, Shifts=1 3375140 .. Key not programmed -- passed on to FS 3375359 KEYUP: VK=120, Waiting=0 3375359 KEYUP: VK=57, Waiting=0 3375359 KEYUP: VK=16, Waiting=0 3375359 KEYDOWN: VK=16, Waiting=0, Repeat=N, Shifts=1 3375359 .. Key not programmed -- passed on to FS 3375359 KEYDOWN: VK=57, Waiting=0, Repeat=N, Shifts=1 3375359 .. Key not programmed -- passed on to FS 3375515 KEYUP: VK=120, Waiting=0 3375515 KEYUP: VK=57, Waiting=0 3375515 KEYUP: VK=16, Waiting=0 5016265 KEYDOWN: VK=16, Waiting=0, Repeat=N, Shifts=1 5016265 .. Key not programmed -- passed on to FS 5016265 KEYDOWN: VK=57, Waiting=0, Repeat=N, Shifts=1 5016265 .. Key not programmed -- passed on to FS 5016265 KEYUP: VK=121, Waiting=0 5016265 KEYUP: VK=57, Waiting=0 5016265 KEYUP: VK=16, Waiting=0 5016265 KEYDOWN: VK=16, Waiting=0, Repeat=N, Shifts=1 5016265 .. Key not programmed -- passed on to FS 5016265 KEYDOWN: VK=57, Waiting=0, Repeat=N, Shifts=1 5016265 .. Key not programmed -- passed on to FS 5016265 KEYUP: VK=121, Waiting=0 5016265 KEYUP: VK=57, Waiting=0 5016265 KEYUP: VK=16, Waiting=0 Link to comment Share on other sites More sharing options...
Pete Dowson Posted June 28, 2013 Report Share Posted June 28, 2013 I believe the KEYDOWN: events are what are causing the FSX unwanted popup behavior. One of these appears to trigger [WINDOW 8] in the Panel.cfg for any aircraft I fly. Why not simply unassign that keypress in FS, then? Keypresses in FS don't needto do anything you don't want them to. Everything they do is a result of assignment, either deliberate or default. Not sure exactly where to go to understand the VK=nn assignments? VK means "Virtual Key" and the number is Windows' own code for the specific key. If you don't want to use Google to find these on-line, there are tables in the FSUIPC Advanced User's guide which list all the usual ones. I was hoping to use FSUIPC to intercept the event and not pass it on. If you don't want to unassign the keypress in FS you can assign it to something different, something innocuous, in FSUIPC, then it won't reach FS. But really it is easier to remove the original assignment. Regards Pete Link to comment Share on other sites More sharing options...
Tom Mc Posted July 1, 2013 Author Report Share Posted July 1, 2013 Peter, Not exactly sure how to reassign/clear the DOWNKEY VK=16 , VK=57 yet. I know how to address simple events like BREAKS... I'll search MS Learning Center first. Thank you for the direction. Gives me something to run down... Tom Link to comment Share on other sites More sharing options...
Pete Dowson Posted July 1, 2013 Report Share Posted July 1, 2013 Peter, Not exactly sure how to reassign/clear the DOWNKEY VK=16 , VK=57 yet. I know how to address simple events like BREAKS. Sorry, I don't know what you mean. To unassign a keypress in FS just go to the Assignments, find the one which is doing it, and clear it. What's a "simple event like BREAKS"? You've lost me there. Do you mean assigning BRAKES? If you can assign keys surely you can clear key assignments? Pete Link to comment Share on other sites More sharing options...
paulwayne Posted July 1, 2013 Report Share Posted July 1, 2013 Dear Peter, I purchased FS Flying School Pro for MS FSX Deluxe Acceleration. I read I need to install FSUIPC4 ver. 4.90 prior to installation. I have a HP envy h8-1520t gaming PC with Intel i7 processor @ 3.6GHZ, 8GB RAM, Radeon 2GB graphics card. I read your instructions to install FSUIPC4 and am confused regarding the LOADER file. Do I need to install that separately or just install FSUIPC4 4.90? Will FSUIPC4 change any of my FSX settings, saved flights, missions, or other functions? Do I need to run as Administrator, I never did that before? Also, do I need to register at the end of the installation? Thank you for your patients and support. Paul Link to comment Share on other sites More sharing options...
Pete Dowson Posted July 1, 2013 Report Share Posted July 1, 2013 I read your instructions to install FSUIPC4 and am confused regarding the LOADER file. Do I need to install that separately or just install FSUIPC4 4.90? The onstructions do actually tell you. It's only there just in case it is needed. Do you have a problem after installing FSUIPC? Will FSUIPC4 change any of my FSX settings, saved flights, missions, or other functions? No. certainly not! Why should it? Do I need to run as Administrator It depends on several things, but, please just do so as instructed. Please PLEASE follow the instructions. Also, do I need to register at the end of the installation? Yes, if you've paid for it, else you won't get value for money, will you? You can't register if you've not purchased it in any case becausde you won't have a key. Again, the instructions do tell you. Regards Pete Link to comment Share on other sites More sharing options...
Tom Mc Posted July 1, 2013 Author Report Share Posted July 1, 2013 Peter, "England and America are two countries separated by the same language " George Bernard Shaw From the FSUIPC Log: 3370890 KEYDOWN: VK=16, Waiting=0, Repeat=N, Shifts=1 3370890 .. Key not programmed -- passed on to FS 3370890 KEYDOWN: VK=57, Waiting=0, Repeat=N, Shifts=1 3370890 .. Key not programmed -- passed on to FS These are coming from the Reality XP Interface when I press a key (e.g. FLP) on the eLite h/w device. I have no idea what FS assignment to clear. ("To unassign a keypress in FS just go to the Assignments, find the one which is doing it, and clear it." Peter) Tom Link to comment Share on other sites More sharing options...
Pete Dowson Posted July 1, 2013 Report Share Posted July 1, 2013 I have no idea what FS assignment to clear. The one invoking the popup window you don't want. Or the one using key codes 16 and 57 (i.e. Shift+9). VK (Virtual Key) codes are listed in many places on the 'net, but probably more conveniently in the FSUIPC Advanced User's guide. Pete Link to comment Share on other sites More sharing options...
Tom Mc Posted July 2, 2013 Author Report Share Posted July 2, 2013 Pete, I don't want either the POPUP [window 8] or the KEYDOWN VK 16 & KEYDOWN VK 57. I am speculating that these two are causing the POPUP behavior and perhaps the bouncing COM1 active/standby frequencies. I see ascii 57 is a "9" & ascii 16 is a DLE.I'll look for through the FSUIPC Advanced User's Guide next. Tom Link to comment Share on other sites More sharing options...
Pete Dowson Posted July 2, 2013 Report Share Posted July 2, 2013 Pete, I don't want either the POPUP [window 8] or the KEYDOWN VK 16 & KEYDOWN VK 57. I am speculating that these two are causing the POPUP behavior and perhaps the bouncing COM1 active/standby frequencies. I see ascii 57 is a "9" & ascii 16 is a DLE.I'll look for through the FSUIPC Advanced User's Guide next. Tom I just told you that it is Shift+9. I don't understand why you then want to refer to the Advanced Users guide? Anyway, you don't have to "look for" it, it is right with all of the FSUIPC documentation, as noted in the Installation document, in FSUIPC Documents. Where else? If your device is spuriously sending Shift + 9 and you don't want it to then you should investigate that. I honestly don't know why you are here in this forum, because nothing so far is really anything to do with FSUIPC or any other program of mine. I am trying to help you but you seem to come back more confused each time! Either you need to stop your device sending keypresses you don't want, or de-assign those keypresses in FS. It is up to you. Regards Pete Link to comment Share on other sites More sharing options...
Tom Mc Posted July 3, 2013 Author Report Share Posted July 3, 2013 Pete, I am in this forum looking for some suggestions as to how I can utilize FSUIPC to correct my simulator problems. I have not infered there is anything wrong with FSUIPC. Is there another forum you can suggest? I tried assigning Shft+9 to No Action in FSUIPC and the [window 8] popup stopped as reflected in the log. tnx. 170593 KEYDOWN: VK=16, Waiting=0, Repeat=N, Shifts=1 170593 .. Key not programmed -- passed on to FS 170593 KEYDOWN: VK=57, Waiting=0, Repeat=N, Shifts=1 170593 FSUIPC Control Action: Ctrl=1126, Param=0 170593 .. This key is programmed in FSUIPC4 'Keys' options The confusion is my understanding the log. ----------------------------------------------------------------------------- The second problem I characterize is the bouncing COM1 Active/Standby Windows. Here is the log which shows repeating events even though I only pushed the key once. Any ideas? 898062 JoystickValues PCnum=0, dwCount=1, data[2]={0000008d 00000000} 898172 *** EVENT: Cntrl= 65707 (0x000100ab), Param= 6471 (0x00001947) COM_RADIO_SET 898172 *** EVENT: Cntrl= 66371 (0x00010343), Param= 9349 (0x00002485) COM_STBY_RADIO_SET 898172 *** EVENT: Cntrl= 65708 (0x000100ac), Param= 5968 (0x00001750) NAV1_RADIO_SET 898172 *** EVENT: Cntrl= 66447 (0x0001038f), Param= 2048 (0x00000800) NAV1_STBY_SET 898172 *** EVENT: Cntrl= 65707 (0x000100ab), Param= 6471 (0x00001947) COM_RADIO_SET 898172 *** EVENT: Cntrl= 66371 (0x00010343), Param= 9349 (0x00002485) COM_STBY_RADIO_SET 898172 *** EVENT: Cntrl= 65708 (0x000100ac), Param= 5968 (0x00001750) NAV1_RADIO_SET 898172 *** EVENT: Cntrl= 66447 (0x0001038f), Param= 2048 (0x00000800) NAV1_STBY_SET 898297 *** EVENT: Cntrl= 65707 (0x000100ab), Param= 9349 (0x00002485) COM_RADIO_SET 898297 *** EVENT: Cntrl= 66371 (0x00010343), Param= 6471 (0x00001947) COM_STBY_RADIO_SET 898297 *** EVENT: Cntrl= 65708 (0x000100ac), Param= 5968 (0x00001750) NAV1_RADIO_SET 898297 *** EVENT: Cntrl= 66447 (0x0001038f), Param= 2048 (0x00000800) NAV1_STBY_SET 898390 *** EVENT: Cntrl= 65707 (0x000100ab), Param= 6471 (0x00001947) COM_RADIO_SET 898390 *** EVENT: Cntrl= 66371 (0x00010343), Param= 9349 (0x00002485) COM_STBY_RADIO_SET 898390 *** EVENT: Cntrl= 65708 (0x000100ac), Param= 5968 (0x00001750) NAV1_RADIO_SET 898390 *** EVENT: Cntrl= 66447 (0x0001038f), Param= 2048 (0x00000800) NAV1_STBY_SET 898593 *** EVENT: Cntrl= 65707 (0x000100ab), Param= 9349 (0x00002485) COM_RADIO_SET 898593 *** EVENT: Cntrl= 66371 (0x00010343), Param= 6471 (0x00001947) COM_STBY_RADIO_SET 898593 *** EVENT: Cntrl= 65708 (0x000100ac), Param= 5968 (0x00001750) NAV1_RADIO_SET 898593 *** EVENT: Cntrl= 66447 (0x0001038f), Param= 2048 (0x00000800) NAV1_STBY_SET 898703 *** EVENT: Cntrl= 65707 (0x000100ab), Param= 6471 (0x00001947) COM_RADIO_SET 898703 *** EVENT: Cntrl= 66371 (0x00010343), Param= 9349 (0x00002485) COM_STBY_RADIO_SET 898703 *** EVENT: Cntrl= 65708 (0x000100ac), Param= 5968 (0x00001750) NAV1_RADIO_SET 898703 *** EVENT: Cntrl= 66447 (0x0001038f), Param= 2048 (0x00000800) NAV1_STBY_SET Thank you for your patients. Tom. Link to comment Share on other sites More sharing options...
Pete Dowson Posted July 3, 2013 Report Share Posted July 3, 2013 The second problem I characterize is the bouncing COM1 Active/Standby Windows. Here is the log which shows repeating events even though I only pushed the key once. Any ideas? 898062 JoystickValues PCnum=0, dwCount=1, data[2]={0000008d 00000000} 898172 *** EVENT: Cntrl= 65707 (0x000100ab), Param= 6471 (0x00001947) COM_RADIO_SET 898172 *** EVENT: Cntrl= 66371 (0x00010343), Param= 9349 (0x00002485) COM_STBY_RADIO_SET 898172 *** EVENT: Cntrl= 65708 (0x000100ac), Param= 5968 (0x00001750) NAV1_RADIO_SET 898172 *** EVENT: Cntrl= 66447 (0x0001038f), Param= 2048 (0x00000800) NAV1_STBY_SET 898172 *** EVENT: Cntrl= 65707 (0x000100ab), Param= 6471 (0x00001947) COM_RADIO_SET 898172 *** EVENT: Cntrl= 66371 (0x00010343), Param= 9349 (0x00002485) COM_STBY_RADIO_SET 898172 *** EVENT: Cntrl= 65708 (0x000100ac), Param= 5968 (0x00001750) NAV1_RADIO_SET 898172 *** EVENT: Cntrl= 66447 (0x0001038f), Param= 2048 (0x00000800) NAV1_STBY_SET 898297 *** EVENT: Cntrl= 65707 (0x000100ab), Param= 9349 (0x00002485) COM_RADIO_SET 898297 *** EVENT: Cntrl= 66371 (0x00010343), Param= 6471 (0x00001947) COM_STBY_RADIO_SET 898297 *** EVENT: Cntrl= 65708 (0x000100ac), Param= 5968 (0x00001750) NAV1_RADIO_SET 898297 *** EVENT: Cntrl= 66447 (0x0001038f), Param= 2048 (0x00000800) NAV1_STBY_SET 898390 *** EVENT: Cntrl= 65707 (0x000100ab), Param= 6471 (0x00001947) COM_RADIO_SET 898390 *** EVENT: Cntrl= 66371 (0x00010343), Param= 9349 (0x00002485) COM_STBY_RADIO_SET 898390 *** EVENT: Cntrl= 65708 (0x000100ac), Param= 5968 (0x00001750) NAV1_RADIO_SET 898390 *** EVENT: Cntrl= 66447 (0x0001038f), Param= 2048 (0x00000800) NAV1_STBY_SET 898593 *** EVENT: Cntrl= 65707 (0x000100ab), Param= 9349 (0x00002485) COM_RADIO_SET 898593 *** EVENT: Cntrl= 66371 (0x00010343), Param= 6471 (0x00001947) COM_STBY_RADIO_SET 898593 *** EVENT: Cntrl= 65708 (0x000100ac), Param= 5968 (0x00001750) NAV1_RADIO_SET 898593 *** EVENT: Cntrl= 66447 (0x0001038f), Param= 2048 (0x00000800) NAV1_STBY_SET 898703 *** EVENT: Cntrl= 65707 (0x000100ab), Param= 6471 (0x00001947) COM_RADIO_SET 898703 *** EVENT: Cntrl= 66371 (0x00010343), Param= 9349 (0x00002485) COM_STBY_RADIO_SET 898703 *** EVENT: Cntrl= 65708 (0x000100ac), Param= 5968 (0x00001750) NAV1_RADIO_SET 898703 *** EVENT: Cntrl= 66447 (0x0001038f), Param= 2048 (0x00000800) NAV1_STBY_SET Where is this button programmed, and to what? Pete Link to comment Share on other sites More sharing options...
Tom Mc Posted July 3, 2013 Author Report Share Posted July 3, 2013 I believe the button (rocker) programming is imbeded in the Reality XP s/w since that software is required to handle the external h/w device. I have been unsuccessful at getting Reality XP (John Luke.-Canadian I believe) to engage in any discussion. I was looking for some way to work around the problem. Acts like a "repeat count" is embeded somewhere but just a guess! Without these logs, I would have been no idea... Tom Link to comment Share on other sites More sharing options...
Pete Dowson Posted July 3, 2013 Report Share Posted July 3, 2013 I believe the button (rocker) programming is imbeded in the Reality XP s/w since that software is required to handle the external h/w device. I have been unsuccessful at getting Reality XP (John Luke.-Canadian I believe) to engage in any discussion. I was looking for some way to work around the problem. Acts like a "repeat count" is embeded somewhere but just a guess! Without these logs, I would have been no idea... Tom But programmed not only to repeat but to affect both COM1 and NAV1 standby and active, continually? Makes no sense. I'm afraid programming a button in FSUIPC cannot override a button programmed in FSX, and certainly cannot override direct control by a separate driver not using button inputs at all as this appears to do. Pete Link to comment Share on other sites More sharing options...
Tom Mc Posted July 4, 2013 Author Report Share Posted July 4, 2013 Pete, But programmed not only to repeat but to affect both COM1 and NAV1 standby and active, continually? Makes no sense. It appears that they refresh the 4 values for the Com1/Nav1 even though some may not have changed. Guess it wont hurt but the repeat must be a bug in their driver. I'll start working the forum at Reality and perhaps with the logs I have captured, open a ticket with them. Thanks for your support. Tom 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