Greg,
Im guessing Drink -> dlink.
And yeah, I kind of figured that that was the better way to do it. I just kept it that way to make a nice challenge for my programming team. In the end, though, like you said, we'll probably end up with the camera connected to the dlink.
As a side note, we only measured ~3-5% drop in CPU usage on the cRIO when we turned off the camera acquisition stuff, and with a short delay to stop the teleop loop from eating all of the free CPU time our CPU hangs around 80-90% which leaves plenty of time for other stuff to happen (except onboard video processing which we discovered the hard way via a psychotic runaway robot. Yeah..... safety....)