@ataiwo473 You will most likely need some form of separate processor to connect the USB webcams to. We are using an hp mini 1000 netbook but another programmer has suggested using FitPC, a small pc that runs linux (i think). You most likely will not be getting the processing power you need on an arduino. Image processing burns many CPU cycles
We need a USB host device unless anybody here wants to re-implement the USB protocol from scratch. And I'm wondering if any rule savvy people here know what kinda of things we can put on the robot. I was thinking it would be best to put something like an arduino or such on the robot that would handle all image manipulation or point detection and would send the rest of the results back to the DriverStation either by the Network or a Digital Input. Does anybody know if thats legal?
that rule only says that you can't have another device DIRECTLY controlling motors. It's totally fine to have a co-processor that sends information to the cRIO. Other teams we know have been using co-processors for years.
you cannot connect the kinect to cRIO, we are going to have a netbook on our robot that will do all the image processing so we will connect the kinect to that through USB. We actually just bought 2 hd webcams that we will be using instead
@ataiwo473 You will most likely need some form of separate processor to connect the USB webcams to. We are using an hp mini 1000 netbook but another programmer has suggested using FitPC, a small pc that runs linux (i think). You most likely will not be getting the processing power you need on an arduino. Image processing burns many CPU cycles
coolnerdguy1353 1 month ago
We need a USB host device unless anybody here wants to re-implement the USB protocol from scratch. And I'm wondering if any rule savvy people here know what kinda of things we can put on the robot. I was thinking it would be best to put something like an arduino or such on the robot that would handle all image manipulation or point detection and would send the rest of the results back to the DriverStation either by the Network or a Digital Input. Does anybody know if thats legal?
ataiwo473 1 month ago
@madscienti11 He probably means kinect connects to netbook, netbook connected to DLINK, Crio connected to Dlink.
WildcatRobotics3540 1 month ago
that rule only says that you can't have another device DIRECTLY controlling motors. It's totally fine to have a co-processor that sends information to the cRIO. Other teams we know have been using co-processors for years.
coolnerdguy1353 1 month ago
Yo, coolnerdguy, your netbook idea is a no-go, R52.
madscienti11 1 month ago
you cannot connect the kinect to cRIO, we are going to have a netbook on our robot that will do all the image processing so we will connect the kinect to that through USB. We actually just bought 2 hd webcams that we will be using instead
coolnerdguy1353 1 month ago
sadly, I don't think you can use the Kinect to the cRIO.
wilsonmw04 1 month ago
Are we actually allowed to use the kinect on-board the robot? If so, how do you connect the USB into the cRio?
Hellocommenters 1 month ago
Super helpful. Thanks guys!
rexcorsetto 1 month ago