Homepage › Forums › How-to and troubleshooting › Joy-con not responding & or "Unexpected error during communication."

Tagged: 

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • 2019-08-19 at 16:21 #11766
    Fredrik Asterhagsajon
    Participant

    The “Unexpected error during communicatio.” pop-up on start have been there for a week since I installed driver4vr and the program do work with a steam controller as xbox, but not very good.

    I Have tried a couple of time to reconnect the Joy-con controller. Paired and setup in driver4vr but nothing is happening on preview and the calibration always ends with n/a.

    2019-08-19 18:05:50: Initializing driver4vr application ver: 5.0.0.10
    2019-08-19 18:05:50: Initializing driver4vr: step 1
    2019-08-19 18:05:51: Initializing driver4vr: step 2
    2019-08-19 18:05:51: Initializing driver4vr: step 3
    2019-08-19 18:05:51: Initializing UI: step 1
    2019-08-19 18:05:51: Initializing UI: step 2
    2019-08-19 18:05:51: Initializing UI: step 2.1
    2019-08-19 18:05:51: Initializing UI: step 2.2
    2019-08-19 18:05:51: Initializing UI: step 2.3
    2019-08-19 18:05:51: Initializing UI: step 3
    2019-08-19 18:05:51: Initializing driver4vr: step 4
    2019-08-19 18:05:51: Attempting to login user: sajon
    2019-08-19 18:05:53: Login user completed with result: 0
    2019-08-19 18:05:53: Creating communication thread…
    2019-08-19 18:05:53: Creating communication done…
    2019-08-19 18:05:53: Initialize communication thread.
    2019-08-19 18:05:53: Exception in communication thread: All pipe instances are busy.

    2019-08-19 18:05:53: Connecting to SteamVR – start
    2019-08-19 18:05:54: VRPath reg output:

    2019-08-19 18:05:54: Runtime path = C:\Program Files (x86)\Steam\steamapps\common\SteamVR
    Config path = C:\Program Files (x86)\Steam\config
    Log path = C:\Program Files (x86)\Steam\logs
    External Drivers:
    C:\Program Files (x86)\Riftcat 2\lib\Driver\vridge
    C:\Users\micro\Downloads\ALVR-portable-v2.3.1\ALVR\driver\
    C:\Users\micro\Desktop\ALVR\driver\
    C:\Program Files (x86)\Steam\steamapps\common\Natural Locomotion\driver\00natural
    C:\Program Files\Pimax\SteamVRSupport\drivers\aapvr
    C:\Program Files (x86)\Driver4VR\lib\drivers\driver4vr

    2019-08-19 18:05:54: Connecting to SteamVR – complete
    2019-08-19 18:05:54: Creating VR Event thread…
    2019-08-19 18:05:54: Creating VR Event done…
    2019-08-19 18:05:54: Initialize VR Event thread.
    2019-08-19 18:05:54: Connection status chanced to: Press ‘Start Driver4VR’
    2019-08-19 18:05:54: Stopping devices…
    2019-08-19 18:05:54: Stopping devices… done.
    2019-08-19 18:05:55: Status trace: stopped
    2019-08-19 18:05:56: End communication thread.
    2019-08-19 18:05:58: Status trace: stopped
    2019-08-19 18:06:01: Status trace: stopped
    2019-08-19 18:06:04: Status trace: stopped
    2019-08-19 18:06:07: Status trace: stopped
    2019-08-19 18:06:10: Status trace: stopped
    2019-08-19 18:06:13: Status trace: stopped
    2019-08-19 18:06:16: Status trace: stopped
    2019-08-19 18:06:19: Status trace: stopped
    2019-08-19 18:06:22: Status trace: stopped
    2019-08-19 18:06:25: Enumeration of devices starting… with 0
    2019-08-19 18:06:25: PS Move Service not required… skipping.
    2019-08-19 18:06:25: Enumeration of JoyCon started with # devices: 0
    2019-08-19 18:06:25: Enumeration of JoyCon completed with # devices: 1
    2019-08-19 18:06:25: Enumeration of devices starting completed with 1 total.
    2019-08-19 18:06:59: Creating Wii Connection…
    2019-08-19 18:06:59: Creating Wii Connection… completed with success.
    2019-08-19 18:06:59: Shutdown of driver4vr application has been completed.
    2019-08-19 18:07:03: Initializing driver4vr application ver: 5.0.0.10
    2019-08-19 18:07:03: Initializing driver4vr: step 1
    2019-08-19 18:07:04: Initializing driver4vr: step 2
    2019-08-19 18:07:04: Initializing driver4vr: step 3
    2019-08-19 18:07:04: Initializing UI: step 1
    2019-08-19 18:07:04: Initializing UI: step 2
    2019-08-19 18:07:04: Initializing UI: step 2.1
    2019-08-19 18:07:04: Initializing UI: step 2.2
    2019-08-19 18:07:04: Initializing UI: step 2.3
    2019-08-19 18:07:04: Initializing UI: step 3
    2019-08-19 18:07:04: Initializing driver4vr: step 4
    2019-08-19 18:07:04: Attempting to login user: sajon
    2019-08-19 18:07:06: Login user completed with result: 0
    2019-08-19 18:07:06: Creating communication thread…
    2019-08-19 18:07:06: Creating communication done…
    2019-08-19 18:07:06: Initialize communication thread.
    2019-08-19 18:07:06: Exception in communication thread: All pipe instances are busy.

    2019-08-19 18:07:06: Connecting to SteamVR – start
    2019-08-19 18:07:06: VRPath reg output:

    2019-08-19 18:07:06: Runtime path = C:\Program Files (x86)\Steam\steamapps\common\SteamVR
    Config path = C:\Program Files (x86)\Steam\config
    Log path = C:\Program Files (x86)\Steam\logs
    External Drivers:
    C:\Program Files (x86)\Riftcat 2\lib\Driver\vridge
    C:\Users\micro\Downloads\ALVR-portable-v2.3.1\ALVR\driver\
    C:\Users\micro\Desktop\ALVR\driver\
    C:\Program Files (x86)\Steam\steamapps\common\Natural Locomotion\driver\00natural
    C:\Program Files\Pimax\SteamVRSupport\drivers\aapvr
    C:\Program Files (x86)\Driver4VR\lib\drivers\driver4vr

    2019-08-19 18:07:06: Connecting to SteamVR – complete
    2019-08-19 18:07:06: Creating VR Event thread…
    2019-08-19 18:07:06: Creating VR Event done…
    2019-08-19 18:07:06: Initialize VR Event thread.
    2019-08-19 18:07:06: Connection status chanced to: Press ‘Start Driver4VR’
    2019-08-19 18:07:06: Stopping devices…
    2019-08-19 18:07:06: Stopping devices… done.
    2019-08-19 18:07:08: Status trace: stopped
    2019-08-19 18:07:09: End communication thread.
    2019-08-19 18:07:11: Status trace: stopped
    2019-08-19 18:07:13: Start/Stop sequence starting.
    2019-08-19 18:07:13: Creating processing thread… start.
    2019-08-19 18:07:13: Creating processing thread… done.
    2019-08-19 18:07:13: Sending communication to start driver – start.
    2019-08-19 18:07:13: Sending communication to start driver – complete.
    2019-08-19 18:07:13: Initialize processing thread.
    2019-08-19 18:07:13: Start/Stop sequence done.
    2019-08-19 18:07:14: Status trace: running
    2019-08-19 18:07:14: Connection status chanced to: Driver4VR is running!
    2019-08-19 18:07:14: Starting all devices…
    2019-08-19 18:07:14: Enumeration of devices starting… with 0
    2019-08-19 18:07:14: PS Move Service not required… skipping.
    2019-08-19 18:07:14: Enumeration of JoyCon started with # devices: 0
    2019-08-19 18:07:14: Enumeration of JoyCon completed with # devices: 1
    2019-08-19 18:07:14: Enumeration of devices starting completed with 1 total.
    2019-08-19 18:07:14: Creating Wii Connection…
    2019-08-19 18:07:14: Creating Wii Connection… completed with success.
    2019-08-19 18:07:14: Starting devices…
    2019-08-19 18:07:14: JoyCon #0 Starting device…
    2019-08-19 18:07:14: JoyCon #0 No response.
    2019-08-19 18:07:14: JoyCon #0 No response.
    2019-08-19 18:07:14: JoyCon #0 No response.
    2019-08-19 18:07:14: JoyCon #0 No response.
    2019-08-19 18:07:14: JoyCon #0 Initialization done.
    2019-08-19 18:07:14: JoyCon #0 Starting device… done.
    2019-08-19 18:07:14: Starting devices complete
    2019-08-19 18:07:14: Starting all devices… done.
    2019-08-19 18:07:14: JoyCon #0 Pool thread started.
    2019-08-19 18:07:14: Tracker update test start – #1
    2019-08-19 18:07:14: Tracker update test end – #1
    2019-08-19 18:07:14: Tracker update test start – #2
    2019-08-19 18:07:14: Tracker update test end – #2
    2019-08-19 18:07:14: Tracker update test start – #3
    2019-08-19 18:07:14: Tracker update test end – #3
    2019-08-19 18:07:14: Tracker update test start – #4
    2019-08-19 18:07:14: Tracker update test end – #4
    2019-08-19 18:07:14: Tracker update test start – #5
    2019-08-19 18:07:14: Tracker update test end – #5
    2019-08-19 18:07:17: Status trace: running
    2019-08-19 18:07:20: Status trace: running
    2019-08-19 18:07:23: Status trace: running
    2019-08-19 18:07:26: Status trace: running
    2019-08-19 18:07:28: Enumeration of devices starting… with 1
    2019-08-19 18:07:28: PS Move Service not required… skipping.
    2019-08-19 18:07:28: Enumeration of JoyCon started with # devices: 1
    2019-08-19 18:07:28: Enumeration of JoyCon completed with # devices: 1
    2019-08-19 18:07:28: Enumeration of devices starting completed with 1 total.
    2019-08-19 18:07:29: Status trace: running
    2019-08-19 18:07:32: Status trace: running
    2019-08-19 18:07:35: Status trace: running

    2019-09-02 at 09:03 #11803
    Bla BlablaGreg Driver
    Keymaster

    can you confirm that you see joy-con as Connected in Bluetooth manager? Not just it is Paired or other status.

  • Author
    Posts
Viewing 2 posts - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.