First Time Starting Vive Wireless Application and is stuck on "Initializing..."

[Krisfallion]

Hello,

I got my Vive Wireless Adapter yesterday and I am having trouble getting the software to work.

Here is what I have done so far:

1) I have installed the Intel card into a PCI 4x slot (only one I had available) and after booting back up I see a new unknown device in my Device Manager.  I attached the cable and mount the antennae so it has a good view of my play area.

2) I charge the battery over night so that it is full.

3) Following the instructions on the web page, I unplug the old cables and attached the wireless adapter and new cables to the HMD.

4) I attached the battery to the wireless adapter.

5) I download and install the software from the Vive website.  It downloads and configures but here is where my troubles begin:  A small window appears called "VIVE Wireless".  It has an animated icon and the text "Initializing..." in it.  The icon just spins and spins and nothing else happens.  It is stuck there and there is no cog or settings option that I can interact with.  All I can do is shut down the appllication.  I have tried it with the power turned on the battery pack and my light houses enabled.

Here are some observations:

1) The lights on the light houses are green.

2) There is a steady blue light on the back of the PCI card.

3) There are four steady green lights on the battery pack.

4) There is a flashing green light on the top of the wireless adapter.

5) There is a steady red light on the side of the HMD.

Am I missing something obvious here?  The instructions on the web page becomes a little vague at the installing software part and I assume it is supposed to come up with a wizard to walk me through pairing the adapter.

I have spent this evening doing a total re-install of my Windows OS from scratch, thinking it could be because my Steam VR and Steam was on the D: drive and the wireless adapter software always installs on C: but I am getting the same issue with fresh installs, no Anti virus installed, and all software on the C: drive.

Please help!

[Apneal]

When you first start pairing the devices, and your battery pack is switched on and the Vive Wireless client is searching to connect, you have to press the button on the center of the wireless adapter to pair it

[Krisfallion]

I do not even get to the point where I need to press the button to pair it.  The Vive Wireless Adapter is not getting past Initializing for the first time after installtion.

 

The screen shot below shows all that I am seeing after it installs and runs. I push the button on top of the wireless adapter and nothing changes.

[Apneal]

Then I'd try a different PCIe port, then try reinstalling the Vive Wireless software

[Krisfallion]

Ok, here is where I am at:

1) I uninstalled the Vive Wireless Adapter software and made sure its install directory was totally gone.

2) I powered down PC and moved the Intel card from the PCIe x4 slot to the other available PCIe x16 slot.  (I have a PCIe x1 slot but it is blocked by video card.  I will move that as a last resort before returning the adapter).

3) I powered on PC and saw that the unknown device for the Intel card showed up in Device Manager.

4) I reinstalled Vive Wireless software with Device Manager open and saw it installed the drivers and they showed up as:  Intel Wireless Gigabit Software Device and Intel Wireless W1100 VR device under Intel Wireless Gigabit VR Adapters.  All good.  No errors in device manager.

5) It then started the Vive Wireless application and I have the same issue where it is stuck on Initializing.

Some questions for the group:

1) Do I need to use the x1 slot?  I have read in several posts that the x4 and x16 will work just fine including HTC's install instructions.

2) Do I need software other than Steam and SteamVR installed before the Vive Wireless software such as the ViveSetup.exe which install ViveHome among other things? (I can use the Vive just fine in wired mode with just SteamVR installed).

Thanks,

Ed

 

[Krisfallion]

I have discovered the log files for the Vive Wirless Application and I see that there are a series of errors that repeat over and over again as I leave the Vive Wireless Application stuck on Initializing.

Here is an example of them:

[2018-10-06 16:45:02.615 -5 0x3358 INFO LOG] DisplayLink driver registered.
[2018-10-06 16:45:03.164 -5 0x3250 INFO LOG] (ControlCenter)GetDeviceStatus : SDK_WIGIGFSM_STATE_UNINITIALIZED(1), reason = SDK_CURRENT_STATE_REASON_COMMAND_IN_PROGRESS(12)
[2018-10-06 16:45:03.364 -5 0x3250 INFO LOG] (ControlCenter)GetDeviceStatus : SDK_WIGIGFSM_STATE_UNINITIALIZED(1), reason = SDK_CURRENT_STATE_REASON_COMMAND_IN_PROGRESS(12)
[2018-10-06 16:45:03.565 -5 0x3250 INFO LOG] (ControlCenter)GetDeviceStatus : SDK_WIGIGFSM_STATE_UNINITIALIZED(1), reason = SDK_CURRENT_STATE_REASON_COMMAND_IN_PROGRESS(12)
[2018-10-06 16:45:03.766 -5 0x3250 INFO LOG] (ControlCenter)GetDeviceStatus : SDK_WIGIGFSM_STATE_UNINITIALIZED(1), reason = SDK_CURRENT_STATE_REASON_COMMAND_IN_PROGRESS(12)
[2018-10-06 16:45:03.967 -5 0x3250 INFO LOG] (ControlCenter)GetDeviceStatus : SDK_WIGIGFSM_STATE_UNINITIALIZED(1), reason = SDK_CURRENT_STATE_REASON_COMMAND_IN_PROGRESS(12)
[2018-10-06 16:45:04.168 -5 0x3250 INFO LOG] (ControlCenter)GetDeviceStatus : SDK_WIGIGFSM_STATE_UNINITIALIZED(1), reason = SDK_CURRENT_STATE_REASON_COMMAND_IN_PROGRESS(12)
[2018-10-06 16:45:04.327 -5 0x30E8 INFO LOG] (ControlCenter)CallbackDeviceStatus : SDK_WIGIGFSM_STATE_UNINITIALIZED(1), reason = SDK_CURRENT_STATE_REASON_PLATFORM_ERROR(15)
[2018-10-06 16:45:04.327 -5 0xE70 INFO LOG] Show error code : 10001.15
[2018-10-06 16:45:04.335 -5 0xE70 INFO LOG] Connection Status set to 6(CONNECTION_STATUS_NOT_READY)
[2018-10-06 16:45:04.369 -5 0x3250 INFO LOG] (ControlCenter)GetDeviceStatus : SDK_WIGIGFSM_STATE_UNINITIALIZED(1), reason = SDK_CURRENT_STATE_REASON_PLATFORM_ERROR(15)
[2018-10-06 16:45:04.374 -5 0x30E8 INFO LOG] (ControlCenter)CallbackDeviceStatus : SDK_WIGIGFSM_STATE_UNINITIALIZED(1), reason = SDK_CURRENT_STATE_REASON_REQUESTED_BY_APPLICATION(9)
[2018-10-06 16:45:04.374 -5 0xE70 INFO LOG] Show error code : 10001.9
[2018-10-06 16:45:04.382 -5 0xE70 INFO LOG] Connection Status set to 6(CONNECTION_STATUS_NOT_READY)
[2018-10-06 16:45:04.570 -5 0x3250 INFO LOG] (ControlCenter)GetDeviceStatus : SDK_WIGIGFSM_STATE_UNINITIALIZED(1), reason = SDK_CURRENT_STATE_REASON_REQUESTED_BY_APPLICATION(9)
[2018-10-06 16:45:04.576 -5 0x30E8 INFO LOG] (ControlCenter)CallbackDeviceStatus : SDK_WIGIGFSM_STATE_UNINITIALIZED(1), reason = SDK_CURRENT_STATE_REASON_COMMAND_IN_PROGRESS(12)
[2018-10-06 16:45:04.576 -5 0xE70 INFO LOG] Show error code : 10001.12
[2018-10-06 16:45:04.579 -5 0xE70 INFO LOG] Connection Status set to 6(CONNECTION_STATUS_NOT_READY)
[2018-10-06 16:45:04.771 -5 0x3250 INFO LOG] (ControlCenter)GetDeviceStatus : SDK_WIGIGFSM_STATE_UNINITIALIZED(1), reason = SDK_CURRENT_STATE_REASON_COMMAND_IN_PROGRESS(12)
[2018-10-06 16:45:04.971 -5 0x3250 INFO LOG] (ControlCenter)GetDeviceStatus : SDK_WIGIGFSM_STATE_UNINITIALIZED(1), reason = SDK_CURRENT_STATE_REASON_COMMAND_IN_PROGRESS(12)
[2018-10-06 16:45:05.173 -5 0x3250 INFO LOG] (ControlCenter)GetDeviceStatus : SDK_WIGIGFSM_STATE_UNINITIALIZED(1), reason = SDK_CURRENT_STATE_REASON_COMMAND_IN_PROGRESS(12)
[2018-10-06 16:45:05.374 -5 0x3250 INFO LOG] (ControlCenter)GetDeviceStatus : SDK_WIGIGFSM_STATE_UNINITIALIZED(1), reason = SDK_CURRENT_STATE_REASON_COMMAND_IN_PROGRESS(12)
[2018-10-06 16:45:05.575 -5 0x3250 INFO LOG] (ControlCenter)GetDeviceStatus : SDK_WIGIGFSM_STATE_UNINITIALIZED(1), reason = SDK_CURRENT_STATE_REASON_COMMAND_IN_PROGRESS(12)
[2018-10-06 16:45:05.776 -5 0x3250 INFO LOG] (ControlCenter)GetDeviceStatus : SDK_WIGIGFSM_STATE_UNINITIALIZED(1), reason = SDK_CURRENT_STATE_REASON_COMMAND_IN_PROGRESS(12)
[2018-10-06 16:45:05.977 -5 0x3250 INFO LOG] (ControlCenter)GetDeviceStatus : SDK_WIGIGFSM_STATE_UNINITIALIZED(1), reason = SDK_CURRENT_STATE_REASON_COMMAND_IN_PROGRESS(12)
[2018-10-06 16:45:06.178 -5 0x3250 INFO LOG] (ControlCenter)GetDeviceStatus : SDK_WIGIGFSM_STATE_UNINITIALIZED(1), reason = SDK_CURRENT_STATE_REASON_COMMAND_IN_PROGRESS(12)
[2018-10-06 16:45:06.315 -5 0x30E8 INFO LOG] (ControlCenter)CallbackDeviceStatus : SDK_WIGIGFSM_STATE_UNINITIALIZED(1), reason = SDK_CURRENT_STATE_REASON_PLATFORM_ERROR(15)
[2018-10-06 16:45:06.322 -5 0xE70 INFO LOG] Show error code : 10001.15
[2018-10-06 16:45:06.330 -5 0xE70 INFO LOG] Connection Status set to 6(CONNECTION_STATUS_NOT_READY)
[2018-10-06 16:45:06.362 -5 0x30E8 INFO LOG] (ControlCenter)CallbackDeviceStatus : SDK_WIGIGFSM_STATE_UNINITIALIZED(1), reason = SDK_CURRENT_STATE_REASON_REQUESTED_BY_APPLICATION(9)
[2018-10-06 16:45:06.362 -5 0xE70 INFO LOG] Show error code : 10001.9
[2018-10-06 16:45:06.365 -5 0xE70 INFO LOG] Connection Status set to 6(CONNECTION_STATUS_NOT_READY)
[2018-10-06 16:45:06.378 -5 0x3250 INFO LOG] (ControlCenter)GetDeviceStatus : SDK_WIGIGFSM_STATE_UNINITIALIZED(1), reason = SDK_CURRENT_STATE_REASON_REQUESTED_BY_APPLICATION(9)
[2018-10-06 16:45:06.564 -5 0x30E8 INFO LOG] (ControlCenter)CallbackDeviceStatus : SDK_WIGIGFSM_STATE_UNINITIALIZED(1), reason = SDK_CURRENT_STATE_REASON_COMMAND_IN_PROGRESS(12)
[2018-10-06 16:45:06.564 -5 0xE70 INFO LOG] Show error code : 10001.12
[2018-10-06 16:45:06.568 -5 0xE70 INFO LOG] Connection Status set to 6(CONNECTION_STATUS_NOT_READY)
[2018-10-06 16:45:06.579 -5 0x3250 INFO LOG] (ControlCenter)GetDeviceStatus : SDK_WIGIGFSM_STATE_UNINITIALIZED(1), reason = SDK_CURRENT_STATE_REASON_COMMAND_IN_PROGRESS(12)
 
and this
 
[2018-10-06 16:45:10.227 -5 0xE70 INFO LOG] Show error code : 10001.4112
[2018-10-06 16:45:10.235 -5 0xE70 INFO LOG] Connection Status set to 6(CONNECTION_STATUS_NOT_READY)
[2018-10-06 16:45:10.396 -5 0x3250 INFO LOG] (ControlCenter)GetDeviceStatus : SDK_WIGIGFSM_STATE_UNINITIALIZED(1), reason = SDK_CURRENT_STATE_REASON_UNRECOVERABLE_MALFUNCTION(4112)
 
For the most part it starts with error 10001.12 and then repeats error 10001.4112 over and over again until I terminate the application.  It looks like it is having an issue with recognizing the wifi card and gets stuck in a loop?

[Krisfallion]

Ok, I resolved the issue.

It was a faulty antennae cable.

Someone on Reddit had the same exact issue when they attempted to use an extension cable.

I returned the hardware and got a replacement today and all works well.

If anyone else has this issue then check/replace the antennae cable.