MAVProxyUser

@saching13 can you explain the workaround in context of the referenced problems, aka simply starting the ROS nodes to publish *any* topic related to the cameras.

lol I now see there was a more complete example at: https://github.com/luxonis/depthai-python/blob/main/examples/calibration/calibration_reader.py It returned this error: ``` ubuntu@ubuntu:~$ python3 calibration_reader.py Stored.json Traceback (most recent call last): File "calibration_reader.py", line 17,...

For posterity, here is my OAK-1-MAX ``` ubuntu@ubuntu:~$ python3 calibration_reader.py Stored.json RGB Camera Default intrinsics... [[2986.73291015625, 0.0, 2004.2607421875], [0.0, 2986.73291015625, 1510.3992919921875], [0.0, 0.0, 1.0]] 4000 3000 RGB Camera Default intrinsics......

@saching13 yeah, my goal would be to simply make it work transparently for anyone that happens to own said camera variant, and chooses to use the existing ROS nodes. In...

sounds completely reasonable! This is my first week with you all's code base so, forgive some of my uninformed questions. I appreciate the help.

@Serafadam I'm sadly stuck on Noetic on a few of my instances, will this be backported to the other branches as well?