-
Notifications
You must be signed in to change notification settings - Fork 118
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PoE Close-In Depth Model - OAK-D-SR-PoE (D405 PoE) #244
Comments
@Luxonis-Brandon |
CC: @Luxonis-David Hi @alexivins - I'll let David describe more of LR HW - but I think LR might be an appropriate choice, due to capability of swapping out lenses for custom ones, which should allow you to basically cover a wide range of different FOVs |
Sorry about the delay @alexivins Yes with OAK-D-LR you can get 3-different baselines where shortest one would be 5cm and with the WFOV lenses you should cover the area pretty well although fisheye cold be used as well. |
@Luxonis-David, thank you for the info. from my understanding the fisheye impacts the accuracy of the depth and item detection. Would you happen to have a visual footprint of these? When would be the soonest I could get one (or both) of these cameras? I would like to begin testing real soon if possible. I appreciate your time and info. |
Yes that is right, with fisheye you get worse depth due to artifacts that are brought in. |
Hello @Luxonis-David @Luxonis-Brandon |
@alexivins we will be looking into this and let you know once we can have it. |
Hi, very interesting product! I have a question: when using with OV9782 WFOV module, what would be the estimated min and max distances that the cam could cover? |
Hi @bochen87 , If you mean the recommended min/max stereo depth perception, I'd estimate it would be from 20cm to about 80cm-100cm for the stereo, and about 3m for tof (max depth perception for tof is 5m though). Thoughts? |
Hi, very interesting product for eye-in-hand applications! Can you share the dimensions of the current design? How will the TOF and stereo data be combined, or do you get 2 depth streams? And what is the minimum distance for the TOF sensor? |
Hi @ToonTielen, Dimensions of the enclosure(x,y,z): 7.9 x 5.2 x 4.5 cm Minimum working distance for the ToF sensors is 29cm. |
Hi @ToonTielen , we do plan to add fusing of ToF + Stereo, but aligning ToF to camera is the priority. We haven't yet added either of these 2 features. |
Updates available in comments below
Start with the
why
:PoE and IP67 sealed is a necessity in many robotic applications because of dirty, dusty, etc. environments and also because USB is often too fragile, finicky, or too short-distance for robotic-arm application. And M12 X-coded Ethernet is either a necessity or quite a nice to have.
So an IP67, M12 X-Coded version of the OAK D405 (#241) would be enable use of such close-in depth in robotic applications in such environments.
Move to the
how
:Leverage the OAK D405 USB version and the PoE circuitry, IP67 design, and M12 X-Coded + M8 IO connector design from OAK-D-Pro-PoE (shop, docs)
And implement this onto a smaller-form-factor commensurate with the narrower baseline like OAK-D-IoT-40 Series 2 (#91; shown below)
Move to the
what
:The text was updated successfully, but these errors were encountered: