Quote:
Originally Posted by apalrd
I would use a small single-core PC and connect it only to the camera (usb) and Ethernet to the cRio. Nothing else.
Here are its primary tasks:
Get image and find shapes
Relate shapes to objects
Determine angle of shapes and position in space
Filter objects that are invalid (e.g. too far away or whatnot)
Send remaining array of objects to cRio
Many platforms can do that. The cRio can too, but that takes too much power away from everything else.
|
I guess, but I was going to do the logic on the co processor too. So use several cores to get images from several cameras and use the remaining to regulate and do logic. I think its best to prepare for the future, the every day computer now days are dual core, or even quad, they get bigger and stronger every year, so thinking into the future and get multi threading under your belt because it will be a norm by the time I am in college and in the work force. So always invest in more knowledge. Im not arguing, I just think you should shoot a little further than you need so you gain that much more experience
edit: lets do some math:
R = 8 bit
B = 8 bit
G = 8 bit
Therefore
RGB pixel = 24 bit
Lets use 800 * 600 resolution
480,000 pixels in 1 image
Thats 11,520,000 bits per image
Or 1.37329102 megabytes per image
And lets say we are taking 60 pics per second: 82.3974612 MBs per second
Now image 4 cameras 329.589845 MBs per second usage in the ram. Thats is alot of memory just for imaging. Yes you can argue you should compress it better or have better memory management, I am merely trying to prove a point. You need a lot of juice