SorensenDK Posted December 22, 2019 Report Share Posted December 22, 2019 Hi Pete. I have a Bodnar BBI32 button box interface connected to my main PC and using an output for ATC keypress. Unfortunately FSUIPC sometimes looses contact with the board, even though it is still recognized by and working in windows (WIN7). If I close P3D, un- and replug the USB, start P3D up again everything works again in FSUIPC. And then maybe it works the nex 10 - 20 maybe 50 times, but suddently it doesnt work any more and for a while I need to un-replug and restart everytime.un- and replug is a bit of a hazzle as it is located rather deep inside a simulator-cockpit ;-) Any thoughts on this? I thank you in advance and wish you a merry christmas. Best Regards Bjarne Sorensen Link to comment Share on other sites More sharing options...
Pete Dowson Posted December 22, 2019 Report Share Posted December 22, 2019 2 hours ago, SorensenDK said: Unfortunately FSUIPC sometimes looses contact with the board, even though it is still recognized by and working in windows (WIN7). If I close P3D, un- and replug the USB, start P3D up again everything works again in FSUIPC. FSUIPC rescans devices if you go into the FSUIPC options. It also receives notifications from Windows if you unplug the device and plug it back in again. By either of these methods there's never a need to restart P3D. have you tried either? The only cause of such behaviour I know of is the action of Windows USB power management. Go into the Windows Device Manager, find the USB section, and go through all the devices (especially those described as hubs) and in the right-click Properties make sure power management is turned off if that option is available. Pete Link to comment Share on other sites More sharing options...
SorensenDK Posted December 26, 2019 Author Report Share Posted December 26, 2019 Hi Pete. Neither of your suggestions works. I have now disables all powermanagement of any USB device and hubs. I tried disconnect and reconnect, and the BBI32 is recognized by Windows but not by FSUIPC. I also tried going to FSUIPC options and out, but no luck here either. Only if I close P3D, disconnect/reconnect the BBI32, and restart P3D FSUIPC will fint it....only to loose it again next time I start the sim up. Best Regards Bjarne Link to comment Share on other sites More sharing options...
Thomas Richter Posted December 26, 2019 Report Share Posted December 26, 2019 Hi, you will need to send in any case the FSUIPC LOG and INI files and as well the FSUIPC5.JoyScan.csv file, after a short and fully closed FS session. All files not altered or shortened please. All of those files are located in Modules folder. Attach as zip or copy and paste their content to your message here. Thomas Link to comment Share on other sites More sharing options...
SorensenDK Posted January 2, 2020 Author Report Share Posted January 2, 2020 Hi Again. Finally back in the sim-room and having run two short sessions, the first one where the BBI32 was not recognized, and the second on witht he BBI recognized. I have attached two zipfiles. Thx for help :-) /Bjarne Logs with BBI32.zip LOGS without BBI32.zip Link to comment Share on other sites More sharing options...
John Dowson Posted January 6, 2020 Report Share Posted January 6, 2020 Hi Bjarne, your logs show that you have some dodgy registry entries that will need removing (which have a null GUID for your problematic device). To get further details, could you add the following to the [General] section of your FSUIPC5.ini file Debug=Please LogExtras=x200000 repeat your tests and re-attached the generated log files. This will add further information on your registry entries which will indicate to us what needs to be removed. You could alternatively try disconnecting the device, removing any drivers or software and then clean the registry yourself for all your Button Box Interface entries (take a backup of your registry first!) before rebooting and reconnecting/reinstalling. Cheers, John P.S. Please also attach your FSUIPC5.ini file when you next upload your log files, thanks. Link to comment Share on other sites More sharing options...
SorensenDK Posted January 7, 2020 Author Report Share Posted January 7, 2020 Hi John. I have now attached the logs with the extended logging. Thank you for all our help - appriciate! /BS logs with BBI32.zip Link to comment Share on other sites More sharing options...
SorensenDK Posted January 7, 2020 Author Report Share Posted January 7, 2020 Sorry - seems I cannot upload more files. Så I have copied the text below from the log without BBI32 Joyscan: Good?, flags, VID, PID, Name, INIid, REGid, RegEntry, INIguid, REGguid, HIDguid, ValsOK?, ReadsOk? ,,, HIDscanning completed N, x00, x16C0, x05BA, , -1, -1, 0, {NULL}, {NULL}, {53A56460-14F2-11E9-8002-444553540000}, Y, N N, x00, x1DD2, x1150, , -1, -1, 0, {NULL}, {NULL}, {2439F7C0-AFAA-11E8-800B-444553540000}, Y, N N, x00, x1FD1, x03ED, , -1, -1, 0, {NULL}, {NULL}, {E3F499F0-BF2A-11E8-8001-444553540000}, Y, N ,,, REGscanning completed N, x00, x16C0, x05BA, BU0836A Interface, -1, 1, 0, {NULL}, {53A56460-14F2-11E9-8002-444553540000}, {53A56460-14F2-11E9-8002-444553540000}, Y, Y N, x00, x1DD2, x1150, Button Box Interface, -1, 0, 0, {NULL}, {2439F7C0-AFAA-11E8-800B-444553540000}, {2439F7C0-AFAA-11E8-800B-444553540000}, Y, N N, x00, x1FD1, x03ED, FDS-FC1, -1, 2, 0, {NULL}, {E3F499F0-BF2A-11E8-8001-444553540000}, {E3F499F0-BF2A-11E8-8001-444553540000}, Y, Y ,,, User settings imported N, x00, x16C0, x05BA, BU0836A Interface, 1, 1, 0, {53A56460-14F2-11E9-8002-444553540000}, {53A56460-14F2-11E9-8002-444553540000}, {53A56460-14F2-11E9-8002-444553540000}, Y, Y N, x00, x1DD2, x1150, Button Box Interface, 0, 0, 0, {2439F7C0-AFAA-11E8-800B-444553540000}, {2439F7C0-AFAA-11E8-800B-444553540000}, {2439F7C0-AFAA-11E8-800B-444553540000}, Y, N N, x00, x1FD1, x03ED, FDS-FC1, 2, 2, 0, {E3F499F0-BF2A-11E8-8001-444553540000}, {E3F499F0-BF2A-11E8-8001-444553540000}, {E3F499F0-BF2A-11E8-8001-444553540000}, Y, Y ,,, Values matched and decided Y, x1E, x16C0, x05BA, BU0836A Interface, 1, 1, 0, {53A56460-14F2-11E9-8002-444553540000}, {53A56460-14F2-11E9-8002-444553540000}, {53A56460-14F2-11E9-8002-444553540000}, Y, Y (Y), x16, x1DD2, x1150, Button Box Interface, 0, 0, 0, {2439F7C0-AFAA-11E8-800B-444553540000}, {2439F7C0-AFAA-11E8-800B-444553540000}, {2439F7C0-AFAA-11E8-800B-444553540000}, Y, N Y, x1E, x1FD1, x03ED, FDS-FC1, 2, 2, 0, {E3F499F0-BF2A-11E8-8001-444553540000}, {E3F499F0-BF2A-11E8-8001-444553540000}, {E3F499F0-BF2A-11E8-8001-444553540000}, Y, Y and the fsuipc.log: ********* FSUIPC5, Version 5.152 (24th July 2019) by Pete Dowson ********* Running inside Prepar3D v4 Module base=7FEEB0E0000 Windows 7 Professional 64 Bit with SP 1.0 reported as Build 7601 (OS 6.1) Prepar3D.exe version = 4.5.12.30293 Reading options from "D:\P3D\Modules\FSUIPC5.ini" Checking the Registrations now ... User Name="Bjarne Sorensen" User Addr="sorensendk74@gmail.com" User WideFS Addr="bjs@nuserne.dk" FSUIPC5 Key is provided WideFS7 Key is provided 0 System time = 07/01/2020 13:12:58 0 FLT UNC path = "\\P3DMAIN\Users\SimEx1\Documents\Prepar3D v4 Files\" 0 Using DialogMode 0 FS UNC path = "\\P3DMAIN\P3D\" 78 #### Initialising Dlrectinput Axis Scanning ... 78 (Entry from GetRegisteredOptions) 78 ---------------------- Joystick Device Scan ----------------------- 78 Error 6 [00000006] returned on HidD_GetPreparsedData: () 78 Error 6 [00000006] returned on HidD_GetPreparsedData: () 78 Checking: \\?\hid#vid_16c0&pid_05ba#8&604fb3e&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} 78 Usage=4, UsagePage=1, =Game Controller 78 Product= BU0836A Interface 78 Manufacturer= Leo Bodnar 78 Serial Number= B76142 78 Vendor=16C0, Product=05BA (Version 1.37) 93 GUIDs returned for product: VID_16C0&PID_05BA: 93 GUID= {53A56460-14F2-11E9-8002-444553540000} 93 Details: Btns=32, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X3563,Y3188,Z0 93 Checking: \\?\hid#vid_1dd2&pid_1150#8&2ae653b3&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} 93 Usage=4, UsagePage=1, =Game Controller 93 Product= Button Box Interface 93 Manufacturer= Leo Bodnar 93 Serial Number= B71831 93 Vendor=1DD2, Product=1150 (Version 2.5) 93 GUIDs returned for product: VID_1DD2&PID_1150: 93 GUID= {2439F7C0-AFAA-11E8-800B-444553540000} 93 Details: Btns=128, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X0,Y0,Z0 93 Checking: \\?\hid#vid_1fd1&pid_03ed#8&10047d25&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} 93 Usage=4, UsagePage=1, =Game Controller 93 Product= FDS-FC1 93 Manufacturer= TEKWorx Limited 93 Serial Number= B51545 93 Vendor=1FD1, Product=03ED (Version 1.35) 93 GUIDs returned for product: VID_1FD1&PID_03ED: 93 GUID= {E3F499F0-BF2A-11E8-8001-444553540000} 93 Details: Btns=32, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R1023,U1023,V0,X1023,Y1023,Z1023 93 ------------------------------------------------------------------- 93 ****** Registry scanning: VID=16C0, PID=05BA ****** 93 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_16C0&PID_05BA\Calibration\0" 93 ... and a "GUID" value 93 GUID= {53A56460-14F2-11E9-8002-444553540000} 93 1st registry entry has Joystick ID=1 93 Attempting to acquire this device for checking ... 93 Acquired device, GetDeviceState to check values 93 ... Okay so far 93 Finding name in "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_16C0&PID_05BA" 93 Joy Name = "BU0836A Interface" 93 ****** Registry scanning: VID=1DD2, PID=1150 ****** 93 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_1DD2&PID_1150\Calibration\0" 93 ... and a "GUID" value 93 GUID= {2439F7C0-AFAA-11E8-800B-444553540000} 93 1st registry entry has Joystick ID=0 93 Attempting to acquire this device for checking ... 93 Acquired device, GetDeviceState to check values 93 ... Okay so far 93 Finding name in "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_1DD2&PID_1150" 93 Joy Name = "Button Box Interface" 93 ****** Registry scanning: VID=1FD1, PID=03ED ****** 93 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_1FD1&PID_03ED\Calibration\0" 93 ... and a "GUID" value 93 GUID= {E3F499F0-BF2A-11E8-8001-444553540000} 93 1st registry entry has Joystick ID=2 93 Attempting to acquire this device for checking ... 93 Acquired device, GetDeviceState to check values 93 ... Okay so far 93 Finding name in "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_1FD1&PID_03ED" 93 Joy Name = "FDS-FC1" 93 ------------------------------------------------------------------- 93 UserDevices: 0.GUID={2439F7C0-AFAA-11E8-800B-444553540000} 93 UserDevices: 1.GUID={53A56460-14F2-11E9-8002-444553540000} 93 UserDevices: 2.GUID={E3F499F0-BF2A-11E8-8001-444553540000} 93 Acquired device, GetDeviceState to check values 93 Device acquired for use: 93 Joystick ID = 1 (Registry okay) 93 1=BU0836A Interface 93 1.GUID={53A56460-14F2-11E9-8002-444553540000} 93 Acquired device, GetDeviceState to check values 93 Device acquired for use: 93 Joystick ID = 0 (Registry okay) 93 0=Button Box Interface 93 0.GUID={2439F7C0-AFAA-11E8-800B-444553540000} 93 Acquired device, GetDeviceState to check values 93 Device acquired for use: 93 Joystick ID = 2 (Registry okay) 93 2=FDS-FC1 93 2.GUID={E3F499F0-BF2A-11E8-8001-444553540000} 93 ------------------------------------------------------------------- 109 ---------- Making INI JoyNames Section ---------- 109 JoyID Used= INI 0007, REG 0007 109 Joy#0: Name = Button Box Interface 109 Joy#0: GUID = {2439F7C0-AFAA-11E8-800B-444553540000} 109 Joy#1: Name = BU0836A Interface 109 Joy#1: GUID = {53A56460-14F2-11E9-8002-444553540000} 109 Joy#2: Name = FDS-FC1 109 Joy#2: GUID = {E3F499F0-BF2A-11E8-8001-444553540000} 109 ------------------------------------------------- 109 Checking and assigning Joy Letters as needed 109 #### Completed Dlrectinput Axis Scanning 109 LogOptions=00000000 02000011 109 ------------------------------------------------------------------- 109 SimConnect_Open succeeded: waiting to check version okay 109 Opened separate AI Traffic client okay 6567 Ready Flags: Ready-To-Fly=N, In Menu=N, In Dlg=N 7519 Running in "Lockheed Martin® Prepar3D® v4", Version: 4.5.12.30293 (SimConnect: 4.5.0.0) 7519 Initialising SimConnect data requests now 7519 FSUIPC Menu entry added 7534 ... Using Prepar3D with Professional License 7534 Ready Flags: Ready-To-Fly=N, In Menu=Y, In Dlg=Y 7534 \\P3DMAIN\Users\SimEx1\Documents\Prepar3D v4 Files\PROSIM.fxml 7534 \\P3DMAIN\Users\SimEx1\Documents\Prepar3D v4 Add-ons\ProSim-AR\SimObjects\Airplanes\ProSim737-800-2019-PBR Professional\Prosim738_Pro.air 7550 ### The user object is 'Prosim AR 737-800 PBR 2019 - Jettime' 7550 ### Mode is NORMAL 9843 Deactivated for PID=2308, "chrome.exe" 9843 Lost focus to PID=2308, "chrome.exe" 9968 ### Mode: PAUSE on 33150 Loading Complete ... 33181 ### Mode is NORMAL 33571 Ready Flags: Ready-To-Fly=N, In Menu=N, In Dlg=N 33571 Aircraft loaded: running normally now ... 33587 User Aircraft ID 1 supplied, now being used 33977 System time = 07/01/2020 13:13:32, Simulator time = 12:13:01 (12:13Z) 33977 Aircraft="Prosim AR 737-800 PBR 2019 - Jettime" 39983 -------------------- Starting everything now ---------------------- 39983 Starting WideServer now ... 39983 Ready Flags: Ready-To-Fly=Y, In Menu=N, In Dlg=N 40045 ASN active function link set 40045 Ready for ActiveSky WX radar with additional data 40045 ... Creating WxRadar binary file as: 40045 C:\ProSim737\ProSim737-2.0\ProSim737-System/radar.bin 41184 Advanced Weather Interface Enabled 42104 Weather Mode now = Theme 50341 Ready Flags: Ready-To-Fly=Y, In Menu=Y, In Dlg=Y 52822 === Closing session: waiting for DLLStop to be called ... 65458 === DLLStop called ... 65458 === Closing external processes we started ... 66456 === About to kill any Lua plug-ins still running ... 66612 Lua threads being terminated: 66612 0 = "D:\P3D\Modules\Prosim-doors.lua" 66768 LUA: "D:\P3D\Modules\Prosim-doors.lua": killed 66768 === Closing global Lua thread 67782 === About to kill my timers ... 67985 === Restoring window procs ... 67985 === Unloading libraries ... 67985 === stopping other threads ... 67985 === ... Button scanning ... 68078 === ... Axis scanning ... 68188 === Releasing joystick devices ... 68188 === Freeing macro memory 68188 === Removing any offset overrides 68188 === Closing all WideFS threads 69560 === Clearing any displays left 69560 === NOTE: not calling SimConnect_Close ... 69560 === AI slots deleted! 69560 === Freeing button memory ... 69560 === Deleting wxstationlist.bin file ... 69560 === Closing my Windows ... 69560 === Freeing FS libraries ... 70559 === Closing devices ... 70559 === Closing the Log ... Bye Bye! ... 70559 System time = 07/01/2020 13:14:08, Simulator time = 12:13:17 (12:13Z) 70559 *** FSUIPC log file being closed Minimum frame rate was 29.5 fps, Maximum was 29.9 fps Average frame rate for running time of 17 secs = 29.1 fps Maximum AI traffic for session was 0 aircraft Memory managed: 32 Allocs, 31 Freed ********* FSUIPC Log file closed *********** Link to comment Share on other sites More sharing options...
John Dowson Posted January 7, 2020 Report Share Posted January 7, 2020 Are you sure those are the correct logs for 'without'? Both the log and the JoyScan.csv indicate that the device is acquired for use and working, although with some issues (as in your 'with' log). John Link to comment Share on other sites More sharing options...
John Dowson Posted January 11, 2020 Report Share Posted January 11, 2020 Hi Bjarne, although you have not responded to my previous post, I don't think it matters to much as the result is the same: you need to uninstall, remove registry entries and re-install. To do this 1. Find the device in the Control Panel – System – Device Manager, right click and uninstall, including driver if option presented. 2. Unplug the device. 3. Create and Execute a .reg file containing the text highlighted below, then run this “as administrator”: Windows Registry Editor Version 5.00 [-HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_1DD2&PID_1150] [-HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_1DD2&PID_1150] You may want to back-up your registry before running this file. To do this, start regedit and 'Export' your registry to a (backup) file. 4. Power off. 5. Re-connect the device 6. Re-boot and test again. We're not 100% sure this will fix your issue though, but maybe worth a try. Regards, John Link to comment Share on other sites More sharing options...
SorensenDK Posted January 12, 2020 Author Report Share Posted January 12, 2020 Hi John. Sorry, but you were right, the BBI is currently working fine for some reason. But I will try your suggestions. Thank you very much for your help. /Bjarne 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