Headset sensor check

[HeellcaT42]

Everyone hello! 🙂

the error is this.

for more additional information, check this LOG in link:

before reinstall

https://drive.google.com/file/d/1U5A0Hei91q2YQO7sLQRlBBC0O_8Ltspy/view?usp=sharing

and after

https://drive.google.com/file/d/1VBl66DlXfCFX9GUzB8AdjS3zarWp2vqr/view?usp=sharing

And every time I touch the helmet, it shows it

06/06 16:50:21.688 {WARNING} [KMCore] [VISION][CALIBRATION] Imu ID does not exist or could not be parsed

06/06 16:50:21.688 {WARNING} [KMCore] [VISION][SensorRegistration] Unable to convert sensor ID '' to int: Empty input string

06/06 16:50:21.688 {WARNING} [KMCore] [VISION][SensorRegistration] Unable to find IMU calibration for device ID 0! As only a single calibration was available we are continuing with that one.

06/06 16:50:21.688 {WARNING} [KMCore] [VISION][VIPER] Loading noise parameters from config. [SensorModel: ]

06/06 16:50:21.688 {!ERROR!} [KMCore] [VISION][viper::viper::imu_types] Both the IMU calibration and the config file specify an accel time offset (calibration: 0, config: -0.0012). The calibration file will be ignored!

06/06 16:50:21.688 {!ERROR!} [KMCore] [VISION][viper::viper::imu_types] Both the IMU calibration and the config file specify a gyro time offset (calibration: 0, config: -0.002). The calibration file will be ignored!

06/06 16:50:21.689 {WARNING} [KMCore] [VISION][VIPER:VIO] Treating initial calibration as nominal. Ocal not allowed to change the camera extrinsics by more than 2 mm

06/06 16:50:21.689 {WARNING} [KMCore] [VISION][SQRFilter] Adjusting extraTimestampPaddingMicroSec from 0.002000000 [sec] to 0.000000000 [sec]

06/06 16:50:21.689 {WARNING} [KMCore] [VISION][SQRFilter] Adjusting filterMaxActiveObservations from -1 to 36000

06/06 16:50:21.689 {WARNING} [KMCore] [VISION][SQRFilter] Adjusting covInflationSettings.epsilon from 2.9999999242136255e-05 to 0

06/06 16:50:21.690 {WARNING} [KMCore] [VISION][VIPER:VIO] Treating initial calibration as nominal. Ocal not allowed to change the camera extrinsics by more than 2 mm

06/06 16:50:21.690 {WARNING} [KMCore] [VISION][SQRFilter] Adjusting extraTimestampPaddingMicroSec from 0.002000000 [sec] to 0.000000000 [sec]

06/06 16:50:21.690 {WARNING} [KMCore] [VISION][SQRFilter] Adjusting filterMaxActiveObservations from -1 to 36000

06/06 16:50:21.690 {WARNING} [KMCore] [VISION][SQRFilter] Adjusting covInflationSettings.epsilon from 2.9999999242136255e-05 to 0

06/06 16:50:21.692 {INFO}    [KMHal] [TrackingHal] Starting camera streaming for device handle 1000

06/06 16:50:21.694 {!ERROR!} [KMHal] (HAL): ERROR: (hal_impl_camera_wmf_win.cpp:84): Failed to find mode (36 modes)

06/06 16:50:21.694 {!ERROR!} [KMHal] (HAL): ERROR: (hal_camera.cpp:358): Could not run camera capture.

06/06 16:50:21.702 {!ERROR!} [KMHal] (HAL): ERROR: (hal_impl_camera_wmf_win.cpp:84): Failed to find mode (36 modes)

06/06 16:50:21.702 {!ERROR!} [KMHal] (HAL): ERROR: (hal_camera.cpp:358): Could not run camera capture.

06/06 16:50:21.710 {!ERROR!} [KMHal] (HAL): ERROR: (hal_impl_camera_wmf_win.cpp:84): Failed to find mode (36 modes)

06/06 16:50:21.710 {!ERROR!} [KMHal] (HAL): ERROR: (hal_camera.cpp:358): Could not run camera capture.

06/06 16:50:21.718 {!ERROR!} [KMHal] [TrackingHal] [PCHAL] Call 'pc_hal_camera_start_streaming':1166 returned a system error, Camera query failed (PC HAL result 13)

06/06 16:50:21.718 {!ERROR!} [KMHal] [TrackingHal] Failed to start camera streaming: CAMERA_QUERY_FAIL

06/06 16:50:21.718 {INFO}    [KMHal] [TrackingHal] Tracking Started

06/06 16:50:21.718 {WARNING} [KMCore] [VISION][VIPER] dropping gyro data, because accelerometer cannot be interpolated.

06/06 16:50:21.718 {WARNING} [KMCore] [VISION][VIPER] dropping gyro data, because accelerometer cannot be interpolated.

06/06 16:50:21.872 {INFO}    [KMHeadsetPlugin] [MapManagement] Current Maps: {97a43b28-b7af-0e66-8f0e-63078d527bc9}{0e8adde8-e5e4-1c4e-3fba-c7f44f1f484c}{9084a183-293f-6ec6-aa46-58d0c2b85c09}

06/06 16:50:21.872 {!ERROR!} [KMHealth] Camera query failed via pc_hal_camera_start_streaming

06/06 16:50:21.872 {INFO}    [HardwareSDKRelay] HMD 1GNGH850QW0374 got health event with error code -4003: Camera query failed via pc_hal_camera_start_streaming

06/06 16:50:21.873 {WARNING} [OAFInterface] GetHMDInfo: USB Host Info was not available

06/06 16:50:21.877 {INFO}    [LifeCycle] ActiveHardwareChanged::get(session).subscribe() Start

06/06 16:50:21.877 {INFO}    [LifeCycle] ActiveHardwareChanged::get(session).subscribe() End

06/06 16:50:22.874 {!ERROR!} [KMCore] [VISION][TIMESTAMPCHECKER] Camera-IOHM sample not received since 1 seconds.

which I've already tried. reinstall the application, rearrange the USB connector, check all usb devices in the device manager and uncheck the boxes, tried to reinstall the USB driver and I think that the problem is of a software nature and not technical, so I hope for your help. In advance, everyone who helped, THANK YOU VERY MUCH.

[HeellcaT42]

in addition, I will add a zip file created by oculus itself

https://drive.google.com/file/d/1bayX_2rnAcPxGx54BMa50NB1zR-n7EHN/view?usp=sharing

[MetaQuestSupport]

Hello there, @HeellcaT42! Thank you for bringing this to our attention. We understand how getting this message can really cause many questions, so we would love to take a closer look into this to get to the root of it. Can you please try the following and see if it does the trick for you? 

• Reseat USB cable from the PC
• Reseat cable from the headset
• Reboot the PC
• Lighting
   - Is the play location well lit? (Turn on more light)
   - Is the play location too bright? (Adjust the intensity, or amount of light
   - Texture is also a factor with tracking. If there is not enough contrast between objects in the room, this could lead to tracking issues.
• Check your Windows camera settings:
  1. Open your Windows settings.
  2. Click Privacy.
  3. Click Camera.
  4. Change the Allow apps to access your camera setting to On.
  5. Once you've updated your settings, unplug the headset cables from your computer and plug them back in
• Open device manager
  1. Go to Universal serial bus controllers
  2. Uninstall/remove the Rift S sensor items listed.
  3. Once removed; click scan for hardware changes at the top of device manager and wait a few minutes for the items removed to come back.

If the issue persists after trying this, please don't hesitate to reach out to us again so we can continue to look further into this for you. We look forward to hearing from you soon! 

[HeellcaT42]

Unfortunately, your advice did not help, there is still an error when setting up, but every other time, I can turn my head and see my hands (gamepads) under me

[MetaQuestSupport]

Thanks for your response! At this point, we would like to get these logs over to our specialists for further review and action. Due to the nature of this request and the information we will need to ask, we request that you message us privately. Please select our name to get to our profile page, or click here: https://metaque.st/CommunitySupport. Next, click "Send a Message" to privately message us! Please remember, you must be signed into the community first to send us a private message. 

[MetaQuestSupport]

Thank you so much for reaching out to us privately! We will be addressing the issues there now, so please keep an eye on your messages! Have a good day!

[ssemaster]

So,bro.I have the same question.Did you solved it? Ican't manage to deal with it!!!

[HeellcaT42]

No, I'm sorry for now, I suffer from repairs from time to time, but so far there has been no progress