|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
|||
|
|||
|
Re: Using Target Distance to Move Robot
Provided the camera is connected to the dlink, you don't need the cRIO to do anything with the image.
The dashboard reads the image directly from the camera. The dashboard processes it. The dashboard sends any target info to the robot via UDP string. The robot reads the TDP string and updates setpoints which ultimately move the robot. You don't have to do it this way, but if you want to use the laptop to do the processing, to allow the cRIO CPU to do other things, this is the way I'd approach it. Greg McKaskle |
|
#2
|
||||
|
||||
|
Re: Using Target Distance to Move Robot
Quote:
also it'd be nice if you could direct your attention here, if it's not too much trouble? |
|
#3
|
|||
|
|||
|
Re: Using Target Distance to Move Robot
Yes, the dashboard is quite capable of doing vision processing. The classmate and typical laptops are quite a bit more powerful than the cRIO. Less capable to do I/O, but more powerful CPU.
I'll look at the other thread as well. Thanks for bringing it to my attention. Greg McKaskle |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|