![]() |
Re: CAMERA
We are having trouble getting our camera to follow the target. It gets the target but doesn't follow it, can you help? Also can we have your code for easy c
|
Re: CAMERA
I know it's repetitive, but we got the same thing. Using LabView, it picks up the color, but doesn't track it. Also, we've tried to get our light to show up green, but it just comes up as white. We used different lighting conditions, but because it's always white it usually tries to track the ceiling lights.
|
Re: CAMERA
kevin, thankyou i will try this monday morning unfortnately I dont have access to the school over the weekend.
|
Re: CAMERA
We have the same problem as mentioned twice in this thread that with labview the camera thinks that the green light is white. Also when we use the default code provided by kevin.org the camera will not lock onto the light. It continues scanning and when the defualt values are changed to what labview says they should be closer to the camera will recognize the light(the red light comes on) but it wont stay on it because it keeps going back and forth between the lights on the ceiling.
any ideas or suggestions would be greatly appreciated Thanks |
Re: CAMERA
All,
Kevin's code works fine "right out of the box" with no modifications. Please read this FAQ (particularly Q9). Mike |
Re: CAMERA
Quote:
Kevin, We recompiled with the increase to 10 of the SEARCH_DELAY_DEFAULT. The camera panned slower, but still didn't respond with anything other than "searching..." We had some students play with the configuration (I know, they shouldn't have...). Now we want to revert to the default calibration, how do we go about doing that? Thanks! Team 2051 |
Re: CAMERA
Quote:
|
Re: CAMERA
Quote:
|
Re: CAMERA
thanks. this helped. we are now tracking the light with one minor problem. if we use the diffuser(the white board in front of the lights) the camera keeps searching, if we turn the light tubes directly to the camera the camera tracks the lights. has anybody else had this problem? and any suggestions on what might need modified?
|
Re: CAMERA
Quote:
-Kevin |
Re: CAMERA
Quote:
If using the "bells and whistles" version, go into the camera menu by typing the letter c into the little "to port" box and hit return. From there you can restore the default settings. Do the same for the tracking menu but use the letter t. Make sure you save the changes once you've recalled the default values. -Kevin |
Re: CAMERA
Quote:
When powering the light from a battery, you should disconnect when not actually trying to acquire the light. The debugging dimension has a different temporal scale than the physical world, and the battery is living in the latter. It appears that one charge is good for testing one - or at maximum, two - ideas or one configuration error. When packing 10 lbs in a 5 lb box, like we've done with all the wire, ballasts, and bulbs in the light enclosure, you might expect that the light performance may not be optimal. Especially when the light gets put together in a big rush because you have something more important to do - like debugging camera code. Shadows of a wiring rats nest projected onto the diffuser are probably not the best thing to calibrate to. When all else fails, plug the camera into the LabView CMUcam GUI and take a peek at what it is seeing, rather than tweaking settings blindly while the battery discharges. |
Re: CAMERA
Quote:
|
Re: CAMERA
Hey, Kevin, just a personal question, but do you think that finding the RBG or YcrBrcg(sorry, I forogt how it's called)parameters(color level, max-min etc.) on LABView and then entering them to the color parameters in your code will work even better than setting them on LABView?
|
Re: CAMERA
Quote:
-Kevin |
| All times are GMT -5. The time now is 03:38. |
Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi