DX100 Motosight 2D "Camera Response Timeout"

    Hi everybody.
    DX100 Handling DS3.62.00A(US)-14 with Motosight 2D
    Cognex is5605 Firmware 4.09, In-sight Explorer 4.9.0, fixed mount
    I have always had a problem where if power to the camera has been cycled I get the Motoman alarm 8113 "Camera Response Time Out" when the robot runs the macro INSPECT in full auto. This alarm will occur for the 1st 5-10 attempts, in auto, before working. Lately, this has been occurring randomly in full auto. It usually goes after 5-10 resets & starts in auto. The camera communicates via Ethernet with the robot, and this is the only Ethernet communication the robot handles.

    Does anyone else out there struggle with this alarm? Any solutions / workarounds?
    Thanks

    This may not be the same problem you are having, but I have seen this camera response timeout error. Here's my scenario:

    The application is inspecting pallets and locating boxes to be picked. I have a separate camera job for every layer of every pallet.

    1) Operators select a product to run.
    2) The robot loads the associated camera job, via the SET_JOB macro.
    3) The robot inspects the pallet, using the INSPECT macro.
    4) As soon as the inspection completes, the robot calls SET_JOB to load the camera job for the next layer of the pallet. I do this in a concurrent job.

    If the servo is turned off (HOLD is pressed, fence circuit opens, etc.) while the SET_JOB macro is active in step 4, I get the timeout alarm when the robot is restarted--but only if the job load has not yet completed. This happens because the SET_JOB macro starts from the beginning if it gets interrupted. So if it is executed while the camera is busy loading the next job, the camera doesn't respond.

    I solved this by copying and editing the SET_JOB code so it is not a macro, but a normal job.

    I have noticed that when the robot is powered on, the robot boot up finishes before the camera. So if you start the program before the camera is ready, you may get this error. Maybe try polling the camera to make sure it's ready before attempting to inspect? I forget the I/O and register numbers to check, but between the internals of the macro jobs and the MotoSight manual, it's not too hard to find them.

    Thanks,
    Scott

    It has been a long while but I wanted to set the record straight on this because it was VERY plaguing for a long time.
    With the help of my friendly neighborhood Yaskawa tech (thanks Guru!) we were able to determine the root cause......
    In the robot ladder which controls the vision light and incoming conveyors I had logic that would trigger the camera via the Cognex discrete trigger wire (green wire). When a part was sensed in the vision area and the conveyor motor stopped, I would pulse the trigger. (There were a bunch of other conditions but that is basically how it worked). The issue was when the robot job was also at the point when it runs the INSPECT macro the Motosight app would lock up because it was expecting signals it was requesting but because the camera was triggered in the middle of this protocol it would send back location and inspection data. This would lock up the otherwise solid Motosight app and require a robot reboot. This would directly cause the exact same issue due to discrete camera trigger and INSPECT macro simultaneously upon boot up and putting in auto. Eventually, the scan times and timing etc would eventually let this go as luck would allow.
    The reason for the double trigger was to save approx 1 sec cycle time. When it worked properly the robot already had a good inspection due to the discrete trigger so all it had to to was adjust and pick.
    To achieve the same results I was advised to P-start the INSPECT macro sometime during the routines where the robot was no where near the vision area making SURE not to double-trigger.

Advertising from our partners