erik
Yes one camera will be blocked and won't recover. The tricky part is the issue not appear for all the pipelines with IMX477. But as comparison, with IMX214, NO issue for all the pipelines.
In the latest C++ MRE, I have 3 different nodes
image_publisher_node
: color camera nodes and detection nodes for CAM_B and CAM_C, no ROS.
image_publisher_ros_node
: color camera nodes and detection nodes for CAM_B and CAM_C, also ROS bridges to publish image and detection to ROS.
image_publisher_ros_single_detection_node
: color camera nodes for both cameras, only one camera has detection node. ROS publishing image from two cameras and detection from one camera.
In term of severity of the issue
For image_publisher_node
, the blocking issue can be seen directly from the screen, it happens around 1 out of 10
For image_publisher_ros_node
, we need pipeline_graph to see the FPS. It happens around 2 out of 5
For image_publisher_ros_single_detection_node
, we need pipeline_graph to see the FPS, I have NOT see the blocking happen yet
Also, like I mentioned a while ago, the issue rarely happens with the python MRE even with IMX477 (1 out of 30?). But I did see it happen before.
So in summary
- The inconsistency of the issue with IMX477 modules in different pipelines, make it looks like it is more on the firmware side.
- But absolutely no issue with IMX214 in all pipelines make it looks like IMX477 hardware is the one to blame.
Sorry for the mess. Let me know what do you think.
Thanks
Lincoln