Trigger/strobe time mismatch
jschmidt
✭
Been getting error messages quite a bit in pickmaster saying "Trigger/strobe time mismatch (0.3s). Strobe from RB pickzone was ignored." and also "Trigger/strobe time mismatch (0.3s). Pick positions lost." Currently running Insight Explorer v4.7.3 (26) and Pickmaster 3.551.0024. Cameras are Cognex Insight 5203. Any idea on what causes this and how to fix it?
0
Comments
-
Do you trigger your camera to often, or is your vision moden to complex ?Regards
Knud Erik Lindberg
Jorgensen Engineering0 -
cameras trigger based off the belt encoder, which i believe is set to around every 250mm. Model is just a 3oz Icee tube, nothing really complex about it.
0 -
1. Ensure the trigger switch is directly to the q-track board(s) pin 9.
2. The line work areas should only have the strobe signal defined (as below):
3. The time mismatch is probably due to the time synchronisation service:
a. The controller network should be isolated from any other network
b. Firewalls – turned off
c. Correct NIC address selected as shown below(in PickMaster->File->options)
d. To force a resync of the service:
i. Turn off all controllers and PickMaster PC
ii. Start PC only
iii. Once up and running (including PickMaster) start the controllers
iv. Wait some time before starting the PickMaster project.0 -
great thanks, ill give this a try. but I ended up deleting the program from insight and copied one of the working programs from another camera and that seemed to get rid of the problems. im not sure if something in the cameras got corrupted somehow or what happened.
0
Categories
- All Categories
- 5.5K RobotStudio
- 396 UpFeed
- 18 Tutorials
- 13 RobotApps
- 297 PowerPacs
- 405 RobotStudio S4
- 1.8K Developer Tools
- 250 ScreenMaker
- 2.8K Robot Controller
- 316 IRC5
- 61 OmniCore
- 7 RCS (Realistic Controller Simulation)
- 800 RAPID Programming
- AppStudio
- 3 RobotStudio AR Viewer
- 18 Wizard Easy Programming
- 105 Collaborative Robots
- 5 Job listings