Please tell me the behavior when a hardware trigger occurs after opening the camera with the following code and applying the trigger.(One sensor is connected in parallel to two cameras.)
As stated above, I received a response, but when I tested it on-site, the projector of the camera that was opened first lit up, and then 0.5 to 1 second later, the projector of the other camera lit up.
Looking at this profile, can you see that there is a delay in the illumination of the projectors from the two cameras? If so, could you please explain how to interpret the profile?
Unless you specified a trigger delay for one camera, they should trigger at the same time. Are the cameras properly wired together?
Just to make sure, you are not confusing the color sensor’s front light with the stereo projector?
I took a look at the log and I noticed that everything related to camera 245218 takes longer; triggering, retrieving, and computing the disparity map. That hits at a network configuration or camera settings issue.
I suggest two things:
Check the network configuration. If the two stereo cameras are transmitting simultaneously into a shared NIC, that might create a bottleneck. Please take a look at the network performance page in our manual.
Can you provide the camera tree for both cameras? Perhaps some individual camera’s settings are amiss.
I apologize for the delayed response. I was able to access the PC where the issue is occurring, so I’ve attached the Tree information. While capturing images with my custom software, I launched NxTreeEdit, selected “Copy value as JSON string” in the root directory, and saved it as a text file.