Quote:
Originally Posted by Lil' Lavery
1712 used the given calibration time during Lunch on Thursday to work with the NI representative at DC to calibrate our camera. I don't know the specifics on the settings (was working on other items at the time), but we managed to get our tracking code working succesfully.
We would sometimes lose targets at a longer range, but that may have been due to their movement and the presence of multiple targets (when we lost a target, we would almost always lock onto another almost immediately) in the camera's vision.
We did notice some difference between when the camera was aimed at the black curtain background and when it was aimed anywhere else. It wasn't a massive difference, but it may be enough at some venues to impact your results.
|
Yep, one of our software engineers, Paul Gehman, worked with Greg from NI at lunch to get the 1712 settings right. I'll see if I can get Paul to post our values here - maybe I can get some screen shots from the programming laptop to post., but I'd suggest on field calibration on Thursday if/when it might be allowed. Bob Bellini, our other engineer helped to refine our target code on Sat, but since the lighting on the field was so bright and different, we really couldn't test a lot in the pits and never went to the practice field because of the difference. We just tried to learn through Thursday and things really worked out well for our autonomous routine using the camera and target size only with no other sensors.