0
$\begingroup$

Rosanswers logo

So I understand that this was an issue with some Kinects but I didn't think the 1473 models had this problem. When I first started using them I remember each had a distinct serial ID. But now when I launch one and it gives me the readout of devices connected this is what happens:

[ INFO] [1389133766.386762473]: Number devices connected: 3
[ INFO] [1389133766.386864325]: 1. device on bus 003:10 is a SensorV2 (2ae) from PrimeSense (45e) with serial id 'A00367A05655114A'
[ INFO] [1389133766.386900866]: 2. device on bus 001:08 is a SensorV2 (2ae) from PrimeSense (45e) with serial id '0000000000000000'
[ INFO] [1389133766.386928332]: 3. device on bus 002:11 is a SensorV2 (2ae) from PrimeSense (45e) with serial id '0000000000000000'
[ INFO] [1389133766.388238717]: Searching for device with bus@address = 2@0

Currently I'm trying to calibrate them so that I can use camera_pose_calibration but the problem is that as stated in the intrinsic calibration tutorial the calibrations are stored based on serial number.

depth_B00362708888047B.yaml  rgb_B00362708888047B.yaml

I'm assuming this might not cause problems making everything run but it WILL override the calibration for my 2nd or 3rd Kinect based on whichever was saved last to that filename.

Anyone have any ideas on how to fix this? Running Hydro.

Edit: So I just noticed right below the 0000 serial number it says this-

[ INFO] [1389137117.588627159]: Opened 'SensorV2' on bus 2:11 with serial number 'A00367A05655114A'

Now I'm truly confused as to whether it is recognizing it or not.


Originally posted by Athoesen on ROS Answers with karma: 429 on 2014-01-07

Post score: 0

$\endgroup$

1 Answer 1

0
$\begingroup$

Rosanswers logo

Nevermind. It appears I missed a memo about the new 1473 models having no serial number whereas my 3rd Kinect was (a surprise to me) a 1414 model.

Issues between the two models discussed here: http://answers.ros.org/question/61542/kinect-xbox360-new-model-1473-has-problems-example-serial-number-soundcard/


Originally posted by Athoesen with karma: 429 on 2014-01-08

This answer was ACCEPTED on the original site

Post score: 0


Original comments

Comment by TFinleyosu on 2014-03-19:
Athoesen, were you able to get a new driver installed to recognize the serial number? I'm in your exact same boat with calibration and I really dont want to try a bunch different drivers to get this working. Can you suggest a solution? freenect_stack or Openni2?

Comment by Athoesen on 2014-03-20:
No. My advisor ended up trading me her family's 1414 for one of the 1473's. That serial number issue seems to be a sticking point. I tried to see if you could manually assign one or choose the name for saving but no one answered.

$\endgroup$

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.