Controller Won't Stay Connected  

   RSS

0

Hey! First of all I want to say thank you for all of your work you do. It's really awesome. I'm having troubles keeping my usb connected controller active in Input Mapper. My log is here                           

Spoiler
[code]

4/15/2019 6:09:25 PM> TRACE: Active application changed to C:\Program Files (x86)\DSDCS\InputMapper\InputMapper.exe (InputMapper)

4/15/2019 6:09:25 PM> TRACE: Running exclusive mode tool...

4/15/2019 6:09:29 PM> TRACE: Starting VBus...

4/15/2019 6:09:29 PM> TRACE: Starting...

4/15/2019 6:09:29 PM> TRACE: Searching for controllers....

4/15/2019 6:09:29 PM> TRACE: Using Exclusive Mode

4/15/2019 6:09:29 PM> TRACE: VBus: VBus started

4/15/2019 6:09:45 PM> TRACE: Device connected 6358802|32768|277073290656

4/15/2019 6:09:46 PM> TRACE: AC:FD:93:A1:1C:35 device start

4/15/2019 6:09:47 PM> TRACE: Found Controller: AC:FD:93:A1:1C:35 (USB)

4/15/2019 6:09:47 PM> TRACE: AC:FD:93:A1:1C:35 power subsystem octet: 0x1b

4/15/2019 6:09:47 PM> TRACE: Device connected 6358802|32768|277073290640

4/15/2019 6:09:47 PM> ERROR: The remote server returned an error: (403) Forbidden. (System.Net.WebResponse EndGetResponse(System.IAsyncResult) in System) []

   at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)

   at MS.Internal.WpfWebRequestHelper.EndGetResponse(WebRequest request, IAsyncResult ar)

   at System.Windows.Navigation.NavigationService.HandleWebResponse(IAsyncResult ar)

   at System.Windows.Navigation.NavigationService.<>c__DisplayClass106_0.<HandleWebResponseOnRightDispatcher>b__0(Object unused)

   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)

   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)

4/15/2019 6:09:51 PM> TRACE: Active application changed to C:\Program Files (x86)\DSDCS\InputMapper\XInputTest.exe (XInputTest)

4/15/2019 6:10:31 PM> TRACE: AC:FD:93:A1:1C:35 power subsystem octet: 0x08

4/15/2019 6:10:31 PM> TRACE: AC:FD:93:A1:1C:35 power subsystem octet: 0x1b

4/15/2019 6:10:32 PM> TRACE: AC:FD:93:A1:1C:35 power subsystem octet: 0x08

4/15/2019 6:10:32 PM> TRACE: AC:FD:93:A1:1C:35 power subsystem octet: 0x1b

4/15/2019 6:10:33 PM> TRACE: Active application changed to C:\Program Files (x86)\DSDCS\InputMapper\InputMapper.exe (InputMapper)

4/15/2019 6:10:37 PM> TRACE: Active application changed to C:\Program Files (x86)\DSDCS\InputMapper\InputMapper.exe (InputMapper)

4/15/2019 6:10:40 PM> TRACE: Active application changed to C:\Program Files (x86)\DSDCS\InputMapper\InputMapper.exe (InputMapper)

4/15/2019 6:10:44 PM> TRACE: Active application changed to C:\WINDOWS\Explorer.EXE (explorer)

4/15/2019 6:10:44 PM> TRACE: Active application changed to C:\Windows\SystemApps\ShellExperienceHost_cw5n1h2txyewy\ShellExperienceHost.exe (ShellExperienceHost)

4/15/2019 6:10:48 PM> TRACE: Active application changed to C:\WINDOWS\Explorer.EXE (explorer)

4/15/2019 6:10:50 PM> TRACE: Active application changed to C:\Program Files (x86)\DSDCS\InputMapper\InputMapper.exe (InputMapper)

4/15/2019 6:10:56 PM> TRACE: Active application changed to C:\Program Files\Malwarebytes\Anti-Malware\mbamtray.exe (mbamtray)

4/15/2019 6:11:11 PM> TRACE: Active application changed to C:\WINDOWS\Explorer.EXE (explorer)

4/15/2019 6:11:23 PM> TRACE: Active application changed to C:\WINDOWS\Explorer.EXE (explorer)

4/15/2019 6:11:23 PM> TRACE: AC:FD:93:A1:1C:35 encountered read failure attempt (1/5): 995

4/15/2019 6:11:24 PM> WARNING: Controller 01 (AC:FD:93:A1:1C:35) is experiencing latency issues. Currently at 20.7ms of recomended maximum 14ms

4/15/2019 6:11:25 PM> TRACE: AC:FD:93:A1:1C:35 power subsystem octet: 0x08

4/15/2019 6:11:25 PM> TRACE: AC:FD:93:A1:1C:35 power subsystem octet: 0x1b

4/15/2019 6:11:26 PM> TRACE: Active application changed to C:\Games\Borderlands - GotY Enhanced\Binaries\Win64\BorderlandsGOTY.exe (BorderlandsGOTY)

4/15/2019 6:11:26 PM> TRACE: Active application changed to C:\Games\Borderlands - GotY Enhanced\Binaries\Win64\BorderlandsGOTY.exe (BorderlandsGOTY)

4/15/2019 6:11:30 PM> TRACE: AC:FD:93:A1:1C:35 encountered read failure attempt (1/5): 1167

4/15/2019 6:11:30 PM> TRACE: Device removed 6358802|32772|277073290704

4/15/2019 6:11:31 PM> TRACE: Device connected 6358802|32768|277073290704

4/15/2019 6:11:31 PM> TRACE: AC:FD:93:A1:1C:35 encountered read failure attempt (2/5): 1167

4/15/2019 6:11:32 PM> TRACE: AC:FD:93:A1:1C:35 encountered read failure attempt (3/5): 1167

4/15/2019 6:11:33 PM> TRACE: AC:FD:93:A1:1C:35 encountered read failure attempt (4/5): 1167

4/15/2019 6:11:34 PM> TRACE: AC:FD:93:A1:1C:35 encountered read failure attempt (5/5): 1167

4/15/2019 6:11:35 PM> ERROR: AC:FD:93:A1:1C:35 disconnect due to read failure: 1167

4/15/2019 6:11:35 PM> TRACE: StopOutputUpdate called, requesting gracefull disconnect.

4/15/2019 6:11:35 PM> TRACE: Close device filestream

4/15/2019 6:11:35 PM> TRACE: Close device handle

4/15/2019 6:11:35 PM> TRACE: IO closed

4/15/2019 6:11:35 PM> TRACE: Controller AC:FD:93:A1:1C:35 was removed or lost connection

4/15/2019 6:11:35 PM> TRACE: Device removed 6358802|32772|277073290688

4/15/2019 6:11:45 PM> TRACE: Active application changed to C:\Games\Borderlands - GotY Enhanced\Binaries\Win64\BorderlandsGOTY.exe (BorderlandsGOTY)

4/15/2019 6:11:45 PM> TRACE: Active application changed to C:\Games\Borderlands - GotY Enhanced\Binaries\Win64\BorderlandsGOTY.exe (BorderlandsGOTY)

4/15/2019 6:16:13 PM> TRACE: Device removed 6358802|32772|277073290704

4/15/2019 6:16:14 PM> TRACE: Device connected 6358802|32768|277073290704

4/15/2019 6:16:14 PM> TRACE: AC:FD:93:A1:1C:35 device start

4/15/2019 6:16:15 PM> TRACE: AC:FD:93:A1:1C:35 encountered synchronous write failure attempt (1/5): 31

4/15/2019 6:16:16 PM> TRACE: Found Controller: AC:FD:93:A1:1C:35 (USB)

4/15/2019 6:16:16 PM> TRACE: AC:FD:93:A1:1C:35 power subsystem octet: 0x1b

4/15/2019 6:16:16 PM> TRACE: Device connected 6358802|32768|277073290688

4/15/2019 6:16:17 PM> ERROR: AC:FD:93:A1:1C:35 encountered write failure: 31

4/15/2019 6:16:17 PM> ERROR: AC:FD:93:A1:1C:35 encountered write failure: 2

4/15/2019 6:16:17 PM> ERROR: AC:FD:93:A1:1C:35 encountered write failure: 87

4/15/2019 6:16:18 PM> TRACE: AC:FD:93:A1:1C:35 power subsystem octet: 0x08

4/15/2019 6:16:18 PM> TRACE: AC:FD:93:A1:1C:35 power subsystem octet: 0x1b

4/15/2019 6:16:35 PM> TRACE: AC:FD:93:A1:1C:35 power subsystem octet: 0x08

4/15/2019 6:16:35 PM> TRACE: AC:FD:93:A1:1C:35 power subsystem octet: 0x1b

4/15/2019 6:17:05 PM> TRACE: AC:FD:93:A1:1C:35 encountered read failure attempt (1/5): 995

4/15/2019 6:17:06 PM> TRACE: Device removed 6358802|32772|277073290704

4/15/2019 6:17:06 PM> TRACE: AC:FD:93:A1:1C:35 encountered read failure attempt (2/5): 1167

4/15/2019 6:17:06 PM> TRACE: Device connected 6358802|32768|277073290704

4/15/2019 6:17:07 PM> TRACE: AC:FD:93:A1:1C:35 encountered read failure attempt (3/5): 1167

4/15/2019 6:17:08 PM> TRACE: AC:FD:93:A1:1C:35 encountered read failure attempt (4/5): 1167

4/15/2019 6:17:09 PM> TRACE: AC:FD:93:A1:1C:35 encountered read failure attempt (5/5): 1167

4/15/2019 6:17:10 PM> ERROR: AC:FD:93:A1:1C:35 disconnect due to read failure: 1167

4/15/2019 6:17:10 PM> TRACE: StopOutputUpdate called, requesting gracefull disconnect.

4/15/2019 6:17:10 PM> TRACE: Close device filestream

4/15/2019 6:17:10 PM> TRACE: Close device handle

4/15/2019 6:17:10 PM> TRACE: IO closed

4/15/2019 6:17:10 PM> TRACE: Controller AC:FD:93:A1:1C:35 was removed or lost connection

4/15/2019 6:17:10 PM> TRACE: Device removed 6358802|32772|277073290688

4/15/2019 6:17:32 PM> TRACE: Device removed 6358802|32772|277073290704

4/15/2019 6:26:25 PM> TRACE: Device connected 6358802|32768|277073290704

4/15/2019 6:26:26 PM> TRACE: 00:00:00:00:00:00 device start

4/15/2019 6:26:27 PM> TRACE: 00:00:00:00:00:00 encountered synchronous write failure attempt (1/5): 2

4/15/2019 6:26:28 PM> TRACE: 00:00:00:00:00:00 encountered synchronous write failure attempt (2/5): 2

4/15/2019 6:26:29 PM> TRACE: 00:00:00:00:00:00 encountered synchronous write failure attempt (3/5): 1167

4/15/2019 6:26:30 PM> TRACE: 00:00:00:00:00:00 encountered synchronous write failure attempt (4/5): 1167

4/15/2019 6:26:31 PM> TRACE: 00:00:00:00:00:00 encountered synchronous write failure attempt (5/5): 1167

4/15/2019 6:26:32 PM> TRACE: 00:00:00:00:00:00 encountered synchronous write failure attempt (6/5): 1167

4/15/2019 6:26:33 PM> TRACE: StopOutputUpdate called, requesting gracefull disconnect.

4/15/2019 6:26:33 PM> TRACE: Close device filestream

4/15/2019 6:26:33 PM> TRACE: Close device handle

4/15/2019 6:26:33 PM> TRACE: IO closed

4/15/2019 6:26:33 PM> TRACE: Active application changed to C:\Windows\SystemApps\Microsoft.Windows.Cortana_cw5n1h2txyewy\SearchUI.exe (SearchUI)

4/15/2019 6:26:33 PM> TRACE: Active application changed to C:\Games\Borderlands - GotY Enhanced\Binaries\Win64\BorderlandsGOTY.exe (BorderlandsGOTY)

4/15/2019 6:26:33 PM> TRACE: Device removed 6358802|32772|277073290704

4/15/2019 6:26:33 PM> TRACE: Active application changed to C:\WINDOWS\Explorer.EXE (explorer)

4/15/2019 6:26:34 PM> TRACE: Active application changed to C:\Windows\SystemApps\ShellExperienceHost_cw5n1h2txyewy\ShellExperienceHost.exe (ShellExperienceHost)

4/15/2019 6:26:37 PM> TRACE: Active application changed to C:\WINDOWS\Explorer.EXE (explorer)

4/15/2019 6:26:37 PM> TRACE: Active application changed to C:\Windows\SystemApps\Microsoft.Windows.Cortana_cw5n1h2txyewy\SearchUI.exe (SearchUI)

4/15/2019 6:26:40 PM> TRACE: Active application changed to C:\WINDOWS\Explorer.EXE (explorer)

4/15/2019 6:26:40 PM> TRACE: Active application changed to C:\Windows\SystemApps\Microsoft.Windows.Cortana_cw5n1h2txyewy\SearchUI.exe (SearchUI)

4/15/2019 6:26:40 PM> TRACE: Active application changed to C:\Program Files (x86)\DSDCS\InputMapper\InputMapper.exe (InputMapper)

4/15/2019 6:27:17 PM> TRACE: Active application changed to C:\Program Files (x86)\DSDCS\InputMapper\InputMapper.exe (InputMapper)

4/15/2019 6:27:26 PM> INFO: Log coppied to clipboard

4/15/2019 6:27:26 PM> TRACE: Active application changed to C:\Program Files (x86)\DSDCS\InputMapper\InputMapper.exe (InputMapper)

[/code]

3 Answers
0

Possible causes for USB disconnections:

USB controllers can use a high amount of bandwith and power. Because of this considerations must be taken when choosing what type of wire to use and where to plug it into the PC.

Some USB cables do not provide enough power to charge devices and are meant for data only. Be sure to use only high quality USB cables.

Likewise some USB cables have only the pins for charging and have no data capabilities.

USB ports are not isolated and individual on PCs. Some ports share power and bandwidth. Because of this you must make sure that any ports that do share power and or bandwidth have enough of both to support simultaneous operation of all devices connected.

Grounding and shielding are extremely important when it comes to USB. A cable or port that is lacking in either will see substantially reduced performance.

Try to make sure to use USB 2.0 devices only on USB 2.0 ports and hubs. Though the spec is backwards compatible, sometimes it still has issues.

0

Possible causes:

Bluetooth connection requires a BT 4.0 EDR capible adapter and even then is extremely susceptible by outside factors.

Only Broadcomm compatible chipsets are supported by IM due to compatibility issues with other chipsets.

No other BT devices should be in use when trying to use a BT controller, BT cannot handle much bandwith and the more devices in use or connected the less likely they are to operate properly.

BT and WiFi do not play nice with eachother, keep them as far apart as possible and if using an all-in-one card or wireless device, disable one of the radios to minimize inteference.

BT only works over short distances, regardless what your device may say it is capible of, BT is a short range protocol. Make sure there is a clear line of sight between the BT dongle and the controller.

If the above have already been taken into consideration, attempt to try different drivers with your BT dongle; try generic Windows, Manufacturer, or Broadcom drivers each to see if this resolves.

I’m afraid I’m not connecting the controller via Bluetooth, It is wired

0

Use your rear ports instead of front ports.

Answer
Share:

Theme by Anders Norén

  
Working

Please Login or Register