-
Notifications
You must be signed in to change notification settings - Fork 120
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
Close-In Depth Model - OAK-D-SR (OAK D405) #241
Comments
What's the model of the TOF sensors and their specification (mainly range, FOV, accuracy, and FPS)? |
Great question. Will circle back with answers. |
@nicholas-presien here are some specs for the VGA ToF that might help:
|
no PoE model for this? I'm thinking USB and mounting on a moving robotic arm don't mix. |
Great question @shpigi - we're going to do a PoE as well. I'll write that up now and cross-post it. |
For at least the initial USB version we're dropping ToF: This will allow the device to be smaller and also exist sooner. And then the PoE version, #244, which will have to be bigger anyway, will have the ToF additionally. |
More of the enclosures have arrived, painting and assembly to be done and we will have some units available for sale on our early access store. In fact you can reserve one with preordering here. |
what screws fit in the three holes on the back side of the Oak D SR ? |
and what is the center-to-center distance between the two outer screw holes ? |
please consider adding an expansion-port on the on the back of these (and OAK-1) form factor
use-case would be to allow building fairly basic LED-light fixtures that sync with captures
where the led-pcb could simply contain a good i2c controlled led-driver, not needing a cpu of its own |
Hi @raveslave , The OAK-D-SR-PoE actually does have an M8 connector which allows you to access the strobe output. |
true that, but I really like the USB-C form factor as we run from raspberry's (wired eth -> internet), |
@raveslave one option would be to use M8 to USB adapter board, which also exposes strobe output. The downside is that it's only USB2, so 480mbps. |
isn't that breakout board for control only? |
@raveslave intention was for control (due to bandwidth limitation), but you can also get images/other outputs through it as well. |
Start with the
why
:A short-range-depth version of OAK is missing in the line up. The closest solution is the OAK-D-IoT-40, which does come close, but is intended for IoT applications (embedded; e.g. has built-in ESP32) rather than USB applications.
So while the OAK-D-IoT-40 is now often used for close-in depth, it's a bit of a mis-fit as in this case there's an unused ESP32 onboard, and it lacks an enclosure. And in such applications, having a single, small, enclosed product is clutch for mounting to picking arms/etc.
Meanwhile, there are a bunch of robotic bin pick/pack applications which would benefit from high-res, high-frame-rate and very-good-quality depth sensing + AI + CV + onboard compute in a USB-formfactor camera.
Supplementarily, there are cases where stereo excels in such applications and other scenarios where ToF (time of flight) excels. So to provide a
swiss army knife
of excellent close-in depth for such applications. The DepthAI ecosystem is uniquely suited to allow this as the onboard CV/depth computation can produce a single depth output that is the result of intelligent combination of ToF + stereo results to give the highest-accuracy depth-map output.Finally, RGB-depth alignment in such applications ends up being paramount, as often the items being manipulated are challenging to grasp, so even tiny errors can result in underperformance of the robotic assembly. So the built-in support for OV9782 (global shutter color) in the DepthAI library is very useful, as it allows perfect RGBD alignment from the stereo pair. And this result, in combination with ToF, allows even-more-refined alignment of ToF to RGB and thereby a single, RGB-aligned depth result that is the fusion of stereo and ToF.
Given our modular arch
Move to the
how
:Leverage our OAK-SoM-Pro to make a compact overall design that supports both wide FOV Stereo (color, 150° DFOV) and standard FOV (color, ~80° DFOV) - production-time selectable - and ToF. The SoM approach allows the design to be smaller and easier to mount/fit in robotic process automation/etc. It also allows the design to be open-sourced, allowing modifications as needed/desired by anyone.
The internal PCBA concept is shown below:
Move to the
what
:Want it in PoE instead? See #244
The text was updated successfully, but these errors were encountered: