Quote:
Originally Posted by ~Cory~
Ok thank you for the information. And isnt subsystems just like normal c++ classes and functions?
|
Essentially it just makes it much easier for rookies, but I am going to recommend staying away from that (along with the drive code that is provided). It gets even more higher level than it is already. I honestly think there are great benefits of writing the functions and classes by yourself.
Also, stay away from image processing on the laptop... There will be great delays. Assume each RGB pixel has 24 bits and the image is 640x480. That is essentially:
640 * 480 = 307200
307200 * 24 = 7372800 bits = 921600 bytes
That data has to travel from the camera to the cRio then to the laptop. Also, the big endian needs to be converted to little endian on the laptop end. Assume the cache of the cpu is 512KB. The cpu is already preoccupied by system processes and other processes. So assume only 24KB are available for the image processing. The image has to be retrieved from the RAM then stuffed into the cache. But look, the whole image can not be stuffed into the cache. There needs to be multiple times it has to go to RAM to retrieve data then send it to the cRio and then the cRio utilized that data. Keep in minds x86 cpus have 8 General purpose registers. It takes about 1-3 cycles to retrieve data from the cache. So only about 1 pixel can be handled at one time by the cpu. BUT powerpc architecture has 32 general purpose resisters. That can effectively quadruple the number of pixels that can be handled by cpu at any given time. Now, I am away my argument is flaws because I do not take account of the clock speed of the cRio into account. But I take my bet on the cRio any day over sending data over wifi and sending back.