We did have an issue where it kept complaining that no Coral was plugged in when we tried to switch a pipeline to “detector”, we had to power cycle a few times in a row to get it to work. Tried a few variations of plugging it in before and after powering up.
I have been having issues working with one of my team’s new Limelight 3s. We have two on our robot, one is working well, detecting april tags normally the other is extremely blurry with no april tags being made out by the algorithm. I have tried all of the settings and tried cleaning the lens to no avail. This unit may have been dropped or hit something, I am unsure. I was wondering if there was a way to refocus the camera or if this symptom is indicative of another, deeper issue. Below are images attached of both the bad and good cameras. Any help would be appreciated.
My apologies if this post needs to be moved to a new thread, I am inexperienced here.
We are running the newest OS on our limelight 3 (limelight 2 had the same issue) and when we see ID 5,the megapose suddenly moves into the driver station. As you can see from the image, the pose derived from 5 (the right green cylinder) and the simply derived botpose are both accurate, whereas the megapose is nowhere near them and it flickers around.
Also interested in an ETA? We are seeing okay results with just the grid tags but a lot of wild results when we don’t disable the loading station tags. It seemed like 973 had things working at CVR at the loading station, but maybe that was just really good driving.