Quote:
Originally Posted by Greg McKaskle
Good news and bad.
The vision team now has a reproducible case of this. It only occurs on the ARM linux target with certain cameras.
Unfortunately, the camera that shows it most easily is the MS 3000. I had four camera types and didn't do all combos of two, but did enough to see that some worked and some resulted in the internal error in Start. I saw it fail with two MS 3000 and one MS3000 and one high end Logitech. I saw it succeed with one MS3000 and a lower end logitech. And saw it succeed with two Logitech cams.
My only suggestion at this point is a workaround of trying there models or makes of camera. Sorry. Thanks for reporting the bug. They should have it fixed for an upcoming release. But that will probably be after the season ends.
Greg McKaskle
|
Which model Logitech cams seem to work with this? We have been having a couple flakey results with the Lifecams:
1. Exposure setting VI. Zero sets image pretty dark (but seems workable), 1-100 appears to all be the same.
2. Sometimes exposure settings "take" on boot-up, sometimes not. No rhyme or reason. With low sample size, restarting robot code from DS seems to fix this. I suspect a boot-up sequence issue with camera settings being set before camera is up and running. We tried implementing a button to set the exposure again to Zero during teleop...does nothing.
We saw this behavior with both 1 and 2 camera scenarios.
-Steve