Mike Purvis
Mike Purvis
Another potential mitigation here would be comparing with the local workspace and just using that message if the MD5 is a match, rather than generating fresh ones indiscriminately.
Hey, is there still interest here?
I'd be delighted for a PR to patch in roslint fails for this. :)
Absolutely, please go ahead and create a pull request.
Would love to see this handled correctly as well, but I'm also not sure how it should work. Please feel free to send a PR if you figure it out!
Ah, this is excellent, thanks very much for the heads-up. Been meaning to implement markers for rviz (See #25), though perhaps this is a better approach.
This is true, but that function is not actually called from anywhere, I don't think. How are you triggering the problem?
Would you consider submitting a PR which more comprehensively enables camera calibration, and includes as part of it a bugfix for this issue?
@cedricpradalier When I was trying to spruce this driver up in July, I added a launchfile which uses gscam instead of the built-in driver: https://github.com/clearpathrobotics/axis_camera/blob/master/launch/axis_gscam.launch Unfortunately, I had enough problems...
Is it typical to have more than one camera on a single IP? We haven't come across any Axis cams like this.