Skip to content
This repository has been archived by the owner on May 3, 2021. It is now read-only.

Windows Controller Setup

Jump to bottom
Chadwick Boulay edited this page Dec 31, 2015 · 9 revisions

#Overview Fair warning: This is probably the most frustrating phase of setup for psmove controller. Fortunately, once you get the controller paired and tracking settings correct, the tracking experience is usually pretty stable.

#Install Bluetooth Adapter

  1. Plug in the ASUS-BT400
  2. Let windows recognize it
  3. Install the bluetooth driver that comes on the CD
  4. There should be a bluetooth icon that shows up on your task tray

#Pairing Controller Getting the PSMove controller to pair and connect on Windows has traditionally been very difficult. There has been a lot of progress recently in improving this process, but it is not yet streamlined.

Plug the controller into the computer via the mini-USB cable. Run Binaries\Win64\psmovepair.exe. This will write the computer's Bluetooth address to the controller but will ultimately fail in establishing the connection. Follow the on-screen instructions but you will be pressing Ctrl+C before the LED is solidly lit.

Then run Binaries\Win64\psmove-pair-win.exe to complete the pairing process and to attempt connection. During this process you will have to press the PS button on the front of the controller (3-10 times) until the program reports pairing successful. You should now be able to unplug the controller from the USB port and remain connected by bluetooth. In the future, when you turn on your computer it should not be necessary to run either of these applications again. You should just have to press the PS button on the controller and it will be connected.

==== Looking for Bluetooth radios ====

  (0)  5c:f3:70:64:54:10  SACHSLAB-WIN8

Using the only available Bluetooth radio.
Making radio discoverable.


==== Connecting new controllers ====

Device: (0)  00:06:f7:97:32:e8  Motion Controller
                          CoD: 0x00002508, CON: 0, REM: 1, AUTH: 0

device #0: Move Motion Controller detected
Device removed - retry
Device: (0)  00:06:f7:18:cd:f3  Motion Controller
                          CoD: 0x00002508, CON: 0, REM: 0, AUTH: 0

device #0: Move Motion Controller detected
radioInfo.address: 5cf370645410
deviceInfo.address: 0006f718cdf3
sSubkey: SYSTEM\CurrentControlSet\Services\HidBth\Parameters\Devices\5cf37064541
00006f718cdf3
[ERROR 0x00000002] Failed to open registry key: The system cannot find the file
specified.
- checking HID service
- enabling HID service
radioInfo.address: 5cf370645410
deviceInfo.address: 0006f718cdf3
sSubkey: SYSTEM\CurrentControlSet\Services\HidBth\Parameters\Devices\5cf37064541
00006f718cdf3
[ERROR 0x000000ea] Failed to get registry value: More data is available.
Set VirtuallyCabled: 1
- verifying successful connection RE
radioInfo.address: 5cf370645410
deviceInfo.address: 0006f718cdf3
sSubkey: SYSTEM\CurrentControlSet\Services\HidBth\Parameters\Devices\5cf37064541
00006f718cdf3
Get VirtuallyCabled: 1
Set VirtuallyCabled: 1
- checking HID service
- verifying successful connection CRE.RE
radioInfo.address: 5cf370645410
deviceInfo.address: 0006f718cdf3
sSubkey: SYSTEM\CurrentControlSet\Services\HidBth\Parameters\Devices\5cf37064541
00006f718cdf3
Get VirtuallyCabled: 0
Set VirtuallyCabled: 1
- checking HID service
- enabling HID service
radioInfo.address: 5cf370645410
deviceInfo.address: 0006f718cdf3
sSubkey: SYSTEM\CurrentControlSet\Services\HidBth\Parameters\Devices\5cf37064541
00006f718cdf3
[ERROR 0x000000ea] Failed to get registry value: More data is available.
Set VirtuallyCabled: 1
- verifying successful connection RE
radioInfo.address: 5cf370645410
deviceInfo.address: 0006f718cdf3
sSubkey: SYSTEM\CurrentControlSet\Services\HidBth\Parameters\Devices\5cf37064541
00006f718cdf3
Get VirtuallyCabled: 1
Set VirtuallyCabled: 1
- checking HID service
- verifying successful connection CRE.CRE.CRE.CRE.CRE.
- !!!! Successfully connected device 00:06:f7:18:cd:f3 !!!!

Device: (1)  00:06:f7:97:32:e8  Motion Controller
                          CoD: 0x00002508, CON: 0, REM: 0, AUTH: 0

device #1: Move Motion Controller detected

#Magnetometer Calibration

  1. Launch Assets\Plugins\x86_64\magnetometer_calibration.exe. You should see the following console:

  1. Spin the controller around until the calibration number is 250+
  2. Press the move button to proceed to the next step. You should then see this:

  1. Set the controller down vertically on a flat surface facing the pseye. This will we the reference pose for the controller in your local magnetic field. Note that the pseye isn't actually used (only the blue light will be on).

  1. Once the controller is stable a timer will count down and then sample the magnetometer.
  2. Once the sampling is done the application should close automatically.
  3. The calibration file will be saved to C:\Users\<username>\AppData\Roaming\.psmoveapi\xx_xx_xx_xx_xx_xx.magnetometer.csv

#Testing PSMove Calibration

  1. Launch Binaries\Win64\test_calibration.exe
  2. You should see a spew of accelerometer and gyro data on the x, y, and z axis in units of 'g'
A: -0.07  1.05  0.01 G:   0.00   0.00   0.31
A: -0.07  1.05  0.01 G:   0.00   0.00   0.42
A: -0.07  1.05  0.01 G:   0.00  -0.00   0.08
...

#Testing Tracking Launching Binaries\Win64\test_opengl.exe will bring up a video feed with the exposure setting hopefully turned down such that all you see is a colored blob corresponding to the end of the controller.

If tracking isn't stable using this app, then you will get garbage tracking in Unreal. Poor tracking here is usually caused by one of two issues.

  1. Bad cached camera configuration values in C:\Users\<username>\AppData\Roaming\.psmoveapi
  2. Excessively bright spots in the camera frame, usually causes by sun reflecting off of your desk if you are near a window.

In either case, try deleting the following files from C:\Users\<username>\AppData\Roaming\.psmoveapi:

  • colormapping.dat
  • PSEye_backup.ini
  • PSEye_backup_win.ini

Then delete the the HKEY_CURRENT_USER\Software\PS3EyeCamera registry key and restart test_tracker.exe. This should reset the camera tracking settings to defaults. If bright spots persist, try reducing the lighting in the field of view of the camera.

#Attribution This wiki page is a collaboration between @cboulay and @PolyarcGames .

Clone this wiki locally