Illusion Walk Posted August 14 Posted August 14 Hi, we re trying to calibrate the cameras of our focus 3 headsets, as they seem to be not calibrated. we re following this guide. https://business.vive.com/us/support/vive-lbss/category_howto/calibrating-the-cameras-on-the-primary-headset.html we re getting the message: HD : "HMD calibration file: /mnt/vendor/mfg/Final_calib_data.json, size:" so the cameras are not calibrated, but we can not get any further. Sometimes we get an unsuspected EOF end of file, sometimes not. however no calibration process will start. Any help would be appreciated thanks!
VIVE_Sally Posted August 28 Posted August 28 Hi, The process will start once the headset starts tracking, no matter the message shows up in the terminal or not. To have a better understanding of the progress of calibration, make sure the headset is nicely connected to the PC, and try the following command to show the progress: adb logcat | find “LIVEK” instead of using adb logcat -s “LIVEK adsprpc” | findstr “LIVEK doLiveK” since some PC might not be able to show the correct result from this command. By replacing the command, you’ll see more information shown on the terminal, which should include the following, indicating the calibration process: [doLiveK] LIVEK prepare to collect data. Please use HMD look around. Once the line appears, you can start to move the headset around to scan the environment. [doLiveK] LIVEK good pose 100 [doLiveK] LIVEK good pose 200 [doLiveK] LIVEK good pose 300 [doLiveK] LIVEK good pose 400 [doLiveK] LIVEK good pose 500 [doLiveK] LIVEK good pose 600 [doLiveK] LIVEK pose enough. Once you saw this line, please put the headset into standby mode by pressing the headset’s power button [LIVEK] We use new extrinsic instead of original extrinsic. This line should show up after a few minutes in standby mode. Notes: Make sure the headset only contains the /mnt/vendor/mfg/Final_calib_data.json file The headset should be charged to at least 50% before calibrating. The calibration process will start right after the headset turns on, so make sure to connect the headset to the PC before powering on the headset.
Illusion Walk Posted August 28 Author Posted August 28 hi Sally, thanks for your response. Even with the adb logcat | find “LIVEK” command no data of the calibration progress will show up. - waiting for device - 08-28 16:52:31.806 2529 2529 D LIVEK : BOOT_COMPLETED listened 08-28 16:52:31.827 2529 2529 D LIVEK : batteryPct 88.0 level 88 scale 100 08-28 16:52:34.949 2529 2529 D LIVEK : batteryPct 87.0 level 87 scale 100 08-28 15:54:34.272 2529 2529 D LIVEK : batteryPct 86.0 level 86 scale 100 here is the output of adb logcat | find "_calib_data.json" 08-28 16:56:43.316 1948 2251 D HDtools : read_from_file: file name = /mnt/vendor/mfg/Final_calib_data.json 08-28 16:56:43.318 1948 2251 D HD : HMD calibration file: /mnt/vendor/mfg/Final_calib_data.json, size: 42581 08-28 16:56:43.318 1948 2251 D HDtools : read_from_file: file name = /mnt/vendor/mfg/Final_calib_data.json 08-28 16:56:43.333 1948 2251 D HDplay : [player_init] json: /mnt/vendor/mfg/Final_calib_data.json 08-28 16:56:45.912 3068 3068 I FeedbackConfig: hmd_json = /mnt/vendor/mfg/Final_calib_data.json 08-28 16:56:46.720 3217 3217 D HDtools : read_from_file: file name = /mnt/vendor/mfg/Final_calib_data.json 08-28 16:56:46.721 3217 3217 D EYEjniso: HMD calibration file: /mnt/vendor/mfg/Final_calib_data.json, size: 42581 08-28 16:56:46.738 3231 3297 I LIPD : HMD calibration file: /mnt/vendor/mfg/Final_calib_data.json, size: 42581 not sure if the calibration is really needed, or just a thing nice to have.
VIVE_Sally Posted August 29 Posted August 29 From the result of adb logcat | find "_calib_data.json", the headset is not calibrated yet. the possible cause of adb logcat | find "LIVEK" not having any calibration progress result might be the environment, you may try to put the headset facing a wild and well decorated environment (same requirement as LBE mode environment), so the headset could start tracking and thus do the calibration. If the calibration process is still not working, you might have to factory reset the headset to make sure the calibration data is clean. Camera calibration is strongly suggested when the headset is used to build the LBE tracking map, since the condition of the cameras could largely effect the quality of tracking, other headsets will still do the calibration in the background in a fixed frequency, to ensure the tracking performance.
Illusion Walk Posted September 11 Author Posted September 11 so we got the cameras calibrated now. we had to factory reset because otherwise it wouldnt work. we used the command adb logcat | find “LIVEK” thanks for the help
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now