Jump to content

Controllers Losing Tracking due to "IMU went off scale"


Archalais
 Share

Recommended Posts

Hello,

 

Both of my controllers are having issues tracking when I do quick movement. Mainly playing Beat Saber. 

Below are the corresponding logs from the VR Server log at time of tracking loss. I used video recording software that was watching gameplay with a clock to determine what time in the logs this would be at. 

 

Also included is VR monitor log and Controller info from log files.

Is there a way to prevent issues with the internal measument unit?

 

VR server log around time of disconnect:
Tue Oct 02 2018 17:18:05.126 - lighthouse: LHR-F7EFBFC3 C: IMU went off scale.
Tue Oct 02 2018 17:18:05.945 - lighthouse: LHR-F7FCFBC3 C: IMU went off scale.
Tue Oct 02 2018 17:18:06.292 - lighthouse: LHR-F7EFBFC3 C: IMU went off scale.
Tue Oct 02 2018 17:18:11.371 - lighthouse: LHR-F7EFBFC3 C: IMU went off scale.
Tue Oct 02 2018 17:18:11.383 - lighthouse: LHR-F7FCFBC3 C: IMU went off scale.
Tue Oct 02 2018 17:18:15.156 - lighthouse: LHR-F7FCFBC3 C: IMU went off scale.
Tue Oct 02 2018 17:18:16.170 - lighthouse: LHR-F7EFBFC3 C: IMU went off scale.
Tue Oct 02 2018 17:18:20.227 - lighthouse: LHR-F7FCFBC3 C: IMU went off scale.
Tue Oct 02 2018 17:18:21.287 - lighthouse: LHR-F7EFBFC3 C: IMU went off scale.
Tue Oct 02 2018 17:18:23.422 - lighthouse: LHR-F7FCFBC3 C: Resetting tracking: unlikely gravity 9.32 m/s/s
Tue Oct 02 2018 17:18:23.422 - lighthouse: LHR-F7FCFBC3 C: Dropped 1983 back-facing hits during the previous tracking session
Tue Oct 02 2018 17:18:23.561 - lighthouse: LHR-F7FCFBC3 C: ----- BOOTSTRAPPED base 5BABA129 (immediate) distance 2.52m velocity 1.02m/s recorded pitch ~30.1 deg roll ~0.9 deg -----
Tue Oct 02 2018 17:18:26.129 - lighthouse: LHR-F7FCFBC3 C: ----- CALIBRATED base 5BABA129 at pitch 30.66 deg roll 2.70 deg -----
Tue Oct 02 2018 17:18:27.213 - lighthouse: LHR-F7FCFBC3 C: ----- SECONDARY base 02EAF560 distance 1.92m -----
Tue Oct 02 2018 17:18:27.613 - lighthouse: LHR-F7FCFBC3 C: ----- RELATIONSHIP bases 5BABA129 <-> 02eaf560 distance 4.24m, angle 165.78 deg -----
Tue Oct 02 2018 17:18:27.744 - lighthouse: LHR-F7FCFBC3 C: Resetting tracking: IMU misalignment unreasonably large (3.5, 6, 13) deg sigma 0.47
Tue Oct 02 2018 17:18:27.744 - lighthouse: LHR-F7FCFBC3 C: Dropped 6 rejected updates, 13 back-facing hits during the previous tracking session
Tue Oct 02 2018 17:18:28.178 - lighthouse: LHR-F7FCFBC3 C: ----- BOOTSTRAPPED base 02EAF560 (delayed) distance 1.95m velocity 1.73m/s recorded pitch ~42.5 deg roll ~0.0 deg -----
Tue Oct 02 2018 17:18:29.854 - lighthouse: LHR-F7FCFBC3 C: ----- CALIBRATED base 02EAF560 at pitch 42.79 deg roll 1.02 deg -----

 

VR monitor log at time of disconnect:
Tue Oct 02 2018 17:18:25.766 - [bluetooth] CHTCBasestationBluetoothController:: PipeInit: CreateFile( \\.\pipe\VIVE_PIPE_BS_PM_MESSAGE ) success.
Tue Oct 02 2018 17:18:25.766 - [bluetooth] CHTCBasestationBluetoothController:: PipeInit: ( 1 ) completed.
Tue Oct 02 2018 17:18:25.766 - [bluetooth] CHTCBasestationBluetoothController:: ProcessCommand: Send MSG_EXTEND_TIMEOUT to BS 5BABA129
Tue Oct 02 2018 17:18:26.115 - [bluetooth] CHTCBasestationBluetoothController:: ProcessCommand: Receive MSG_EXTEND_TIMEOUT : 0 (RSP_SUCCESS)
Tue Oct 02 2018 17:18:26.115 - [bluetooth Controller] Send 'Extend timeout' to LHB-5BABA129 (Success) (0.35 seconds)
Tue Oct 02 2018 17:18:26.115 - [bluetooth] CHTCBasestationBluetoothController:: PipeInit: CreateFile( \\.\pipe\VIVE_PIPE_BS_PM_MESSAGE ) success.
Tue Oct 02 2018 17:18:26.115 - [bluetooth] CHTCBasestationBluetoothController:: PipeInit: ( 1 ) completed.
Tue Oct 02 2018 17:18:26.115 - [bluetooth] CHTCBasestationBluetoothController:: ProcessCommand: Send MSG_EXTEND_TIMEOUT to BS 02EAF560
Tue Oct 02 2018 17:18:26.475 - [bluetooth] CHTCBasestationBluetoothController:: ProcessCommand: Receive MSG_EXTEND_TIMEOUT : 0 (RSP_SUCCESS)
Tue Oct 02 2018 17:18:26.475 - [bluetooth Controller] Send 'Extend timeout' to LHB-02EAF560 (Success) (0.36 seconds)

 

Contoller Info:
Device 5 - Controller Vive. Controller MV HTC LHR-F7FCFBC3
Firmware: 1465809478 htcvrsoftware@firmware-win32 2016-06-13 FPGA 262(1.6/0/0) BL 0 VRC 1465809477 Radio 1466630404
Hardware Revision: product 129 rev 1.5.0 lot 2000/0/0 0
Hardware Id: 0x81010500
Watchman Firmware: 1465809478 / 0 (2016-06-13)
Watchman FPGA: 262 / 262 (1.6)
VRC Version: 1465809477 / 1465809477 (2016-06-13)
Radio Version: 1466630404 / 1466630404 (2016-06-22)
Dongle Version: 1461100729 / 1461100729 (2016-04-19)
Supported Buttons: 12884901894
Connected Dongle: A20242B38A Version: Unknown Version
Device Path: /devices/htc/vive_controllerLHR-F7FCFBC3
Best Alias: /user/hand/left

 

Link to comment
Share on other sites

Steps I have now tried to resolve this (in this order):

1. Re-paired the controllers

2. Updated viveport

3.

o Access to the address: C:\Program files\SteamLibrary\steamapps\common\SteamVR\tools\lighthouse\firmware\vr_controller\archive\
o Verify that "htc_vrc_dongle_1461100729_2016_04_19.bin" and "htc_vrc_dongle_1461100729_2016_04_19.bin" are on the folder.
o Delete File: htc_vrc_dongle_1461100729_2016_04_19.bin
o Uninstall all custom VIVE content, find installed game list and unsubscribe from them all.
o Quit SteamVR.
o Unplug USB HUB From the PC.
o Turn off all apps (some like flux or Razer Synapse conflict with SteamVR).
o Restart PC.
o Plug in the HMD and turn SteamVR on.

3.

o Hold down the trigger, menu button, trackpad button, AND grip buttons on the controller (everything except the system button)
o While holding the buttons, plug your controller into your computer with a micro USB cable (you may need an extra hand to do this)
o Wait for five seconds, then release the buttons
o Ignore the new storage device that appears and unplug the micro USB cord to reset

4.
o Close SteamVR.
o Go to Steam\steamapps\common\SteamVR\tools\lighthouse\bin\win32
o Run lighthouse_console.exe
o Type "Unpair all" on the console then hit enter.
o Close the console and restart SteamVR changing USB ports from 3.0 to 2.0 or vice versa.
5. Connected the two lighthouses using the cable.

Note: this had an interesting effect as it appears the controllers now lose tracking at the same time and with the same incorrect offset. 

 

VR Server log from when the lighthouses were connected. You can see that both controllers went off scale at the "same time" (off by about 1 second)

 

Tue Oct 02 2018 21:25:29.414 - lighthouse: LHR-F7EFBFC3 C: Resetting tracking: unlikely gravity 9.32 m/s/s
Tue Oct 02 2018 21:25:29.414 - lighthouse: LHR-F7EFBFC3 C: Dropped 9 rejected updates, 50 back-facing hits during the previous tracking session
Tue Oct 02 2018 21:25:29.530 - lighthouse: LHR-F7EFBFC3 C: ----- BOOTSTRAPPED base 5BABA129 (immediate) distance 2.11m velocity 3.91m/s recorded pitch ~30.5 deg roll ~0.6 deg -----
Tue Oct 02 2018 21:25:31.223 - lighthouse: LHR-F7EFBFC3 C: ----- CALIBRATED base 5BABA129 at pitch 26.78 deg roll 1.14 deg -----
Tue Oct 02 2018 21:25:31.235 - lighthouse: LHR-F7EFBFC3 C: Resetting tracking: IMU misalignment unreasonably large (13, -11, 1.1) deg sigma 1.1
Tue Oct 02 2018 21:25:31.297 - lighthouse: LHR-F7EFBFC3 C: ----- BOOTSTRAPPED base 5BABA129 (immediate) distance 2.07m velocity 2.96m/s recorded pitch ~30.5 deg roll ~0.6 deg -----
Tue Oct 02 2018 21:25:31.570 - lighthouse: LHR-F7EFBFC3 C: IMU went off scale.
Tue Oct 02 2018 21:25:33.589 - lighthouse: LHR-F7EFBFC3 C: ----- CALIBRATED base 5BABA129 at pitch 28.27 deg roll 0.07 deg -----
Tue Oct 02 2018 21:25:34.613 - lighthouse: LHR-F7EFBFC3 C: ----- SECONDARY base 02EAF560 distance 2.53m -----
Tue Oct 02 2018 21:25:34.837 - lighthouse: LHR-F7EFBFC3 C: ----- RELATIONSHIP bases 5BABA129 <-> 02eaf560 distance 4.12m, angle 168.29 deg -----
Tue Oct 02 2018 21:25:35.447 - lighthouse: LHR-F7FCFBC3 C: LighthouseDirect: Optical data at time 160.643894 < filter at 160.689392
Tue Oct 02 2018 21:25:36.847 - lighthouse: LHR-F7EFBFC3 C: IMU went off scale.
Tue Oct 02 2018 21:25:37.647 - lighthouse: LHR-F7FCFBC3 C: IMU went off scale.
Tue Oct 02 2018 21:25:42.538 - lighthouse: LHR-F7EFBFC3 C: IMU went off scale.
Tue Oct 02 2018 21:25:43.964 - lighthouse: LHR-F7FCFBC3 C: IMU went off scale.
Tue Oct 02 2018 21:25:46.254 - lighthouse: LHR-F7EFBFC3 C: IMU went off scale.
Tue Oct 02 2018 21:25:51.249 - lighthouse: LHR-F7EFBFC3 C: IMU went off scale.
Tue Oct 02 2018 21:25:51.989 - lighthouse: LHR-F7FCFBC3 C: IMU went off scale.
Tue Oct 02 2018 21:25:53.440 - lighthouse: LHR-F7FCFBC3 C: IMU went off scale.
Tue Oct 02 2018 21:25:55.512 - AppTransition: Aborting external launch because of timeout after 0.00996399 seconds
Tue Oct 02 2018 21:25:55.512 - Aborting launch of 'steam.app.620980'
Tue Oct 02 2018 21:25:56.246 - lighthouse: LHR-F7EFBFC3 C: IMU went off scale.
Tue Oct 02 2018 21:25:58.545 - lighthouse: LHR-F7FCFBC3 C: IMU went off scale.
Tue Oct 02 2018 21:26:02.287 - lighthouse: LHR-F7EFBFC3 C: IMU went off scale.
Tue Oct 02 2018 21:26:04.283 - lighthouse: LHR-F7FCFBC3 C: IMU went off scale.
Tue Oct 02 2018 21:26:05.488 - lighthouse: LHR-F7FCFBC3 C: Resetting tracking: unlikely gravity 9.32 m/s/s
Tue Oct 02 2018 21:26:05.488 - lighthouse: LHR-F7FCFBC3 C: Dropped 71 back-facing hits during the previous tracking session
Tue Oct 02 2018 21:26:05.899 - lighthouse: LHR-F7FCFBC3 C: ----- BOOTSTRAPPED base 5BABA129 (immediate) distance 2.34m velocity 1.53m/s recorded pitch ~30.5 deg roll ~0.6 deg -----
Tue Oct 02 2018 21:26:06.406 - lighthouse: LHR-F7EFBFC3 C: Resetting tracking: unlikely gravity 9.32 m/s/s
Tue Oct 02 2018 21:26:06.406 - lighthouse: LHR-F7EFBFC3 C: Dropped 5 rejected updates, 50 back-facing hits during the previous tracking session
Tue Oct 02 2018 21:26:06.466 - lighthouse: LHR-F7EFBFC3 C: ----- BOOTSTRAPPED base 5BABA129 (immediate) distance 1.73m velocity 3.93m/s recorded pitch ~30.5 deg roll ~0.6 deg -----
Tue Oct 02 2018 21:26:06.773 - lighthouse: LHR-F7EFBFC3 C: IMU went off scale.
Tue Oct 02 2018 21:26:08.532 - lighthouse: LHR-F7EFBFC3 C: ----- CALIBRATED base 5BABA129 at pitch 27.34 deg roll 0.13 deg -----
Tue Oct 02 2018 21:26:08.598 - lighthouse: LHR-F7EFBFC3 C: Resetting tracking: IMU misalignment unreasonably large (19, -1.4, 3.3) deg sigma 1.6
Tue Oct 02 2018 21:26:08.598 - lighthouse: LHR-F7EFBFC3 C: Dropped 33 back-facing hits during the previous tracking session
Tue Oct 02 2018 21:26:08.664 - lighthouse: LHR-F7EFBFC3 C: ----- BOOTSTRAPPED base 5BABA129 (immediate) distance 2.05m velocity 1.96m/s recorded pitch ~30.5 deg roll ~0.6 deg -----
Tue Oct 02 2018 21:26:09.165 - lighthouse: LHR-F7EFBFC3 C: IMU went off scale.
Tue Oct 02 2018 21:26:09.241 - lighthouse: LHR-F7FCFBC3 C: IMU went off scale.
Tue Oct 02 2018 21:26:10.456 - lighthouse: LHR-F7FCFBC3 C: ----- CALIBRATED base 5BABA129 at pitch 30.84 deg roll 0.32 deg -----
Tue Oct 02 2018 21:26:10.464 - lighthouse: LHR-F7EFBFC3 C: ----- CALIBRATED base 5BABA129 at pitch 27.54 deg roll 3.00 deg -----
Tue Oct 02 2018 21:26:11.583 - lighthouse: LHR-F7EFBFC3 C: ----- SECONDARY base 02EAF560 distance 2.55m -----
Tue Oct 02 2018 21:26:11.814 - lighthouse: LHR-F7EFBFC3 C: ----- RELATIONSHIP bases 5BABA129 <-> 02eaf560 distance 4.28m, angle 169.00 deg -----
Tue Oct 02 2018 21:26:12.281 - lighthouse: LHR-F7FCFBC3 C: ----- SECONDARY base 02EAF560 distance 2.42m -----
Tue Oct 02 2018 21:26:12.887 - lighthouse: LHR-F7FCFBC3 C: ----- RELATIONSHIP bases 5BABA129 <-> 02eaf560 distance 4.32m, angle 169.52 deg -----

Link to comment
Share on other sites

After speaking with support for a few hours, here are all the things that we tried: 

  1. Checked that all firmware was up to date by:
    1. Quit SteamVR and any other Vive/VR apps running on your PC.
    2. Unplug the power cable from the side of the link box that's feeding into the headset.
    3. Hold down the button on the left side of the Vive headset, and continue to hold it down as you plug the cable back into the link box – keep holding the button for up to 15 seconds after plugging that cable back in.
    4. After releasing the button, the Vive should get snapped out of its semi-bricked state.
    5. After that, install any available firmware updates. (Before you update the firmware disconnect any other unneeded USB device from the PC.
      1. Side Note: After doing this, my computer stopped recognizing the Vive. To fix this:
        1. Unplug all Link Box cables from your PC.
        2. Navigate to SteamVR > Settings > Developer.
        3.  Click on Remove all SteamVR USB Devices. Verify the USB cable or any other cable is not plugged in to the Link Box and click Yes.
        4.  Once this is complete, quit SteamVR.
        5.  Restart your PC.
        6.  Plug them in the following order: AC Adapter > HDMI/DP > USB. This will reinstall all Vive USB drivers.
  2. I use two moniters so we unplugged one to test.
  3. Verified no reflective surfaces in/near play area.
  4. Adjusted base stations to look directly at each other. Verifying with Steamvr settings> developer> room overview (They were slightly off). Ran room setup after adjustment.
  5. Tried using channels A and B with the sync cable plugged in
  6. Turned on base station off and set it to A and tested while facing directly at it. Repeated for other base station
  7. Reinstalled Steam, SteamVR, and VR games to C: drive. (They were on seperate drives)
  8. Bypassed the link box by plugging HDMI and USB direcly from headset to the computer
  9. I tried step 1. again just to make sure that having that side issue did not prevent anything

After each step I was able to replicate the issue.

 

A couple of things I noticed were consistent:

  • It started or was just the right hand controller 90% of the time (I would swap which hand each controller was in by shutting them off, swapping hands, then turning them on again)
  • The controller "wandered off" to the left of where it was actually at if it didn't just stop moving
  • It occurs when moving at higher speed and never when I was moving regularly.
  • Hard to tell but it seems to be more prominent when I am changing direction quickly rather than just moving fast. So higher amounts of jerk (change in acceleration) exasperates it.
Link to comment
Share on other sites

With some more troubleshooting to determine the root of the problem, it turned out to be the right side of the headset that connects to the controllers is having issues. Repairs to the hardware need to be done to solve the problem. Vive support was very helpful throughout this to find what was the exact cause of the issue. Thank you!

Link to comment
Share on other sites

  • 1 month later...
  • 7 months later...

i have exactly the same annoying issue with my new Htc Vive headset on  Beatsaber expert + ! i have like 130 hours + ingame and hit every note but sometimes the controller dont recognize my hits and "imu went off scale" its very frustrating. in my case its like 95% left controller and 5% right controller. i rly dont know how to solve this problem did everything. maybe my vive is faulty ?
by the way could htc repaired ur vive ? was there any warranty left on the device? 
thx

Link to comment
Share on other sites

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...