A robot simulation runs at conveyor speeds of 200 mm/s but reports a script error after the conveyor is reduced to 6 mm/s. The evidence does not establish the exact error text or root cause. It does support testing whether slower transport exposes a process-flow or synchronization problem before treating the speed setting itself as defective.
Correct the conveyor speed calculation
Use distance equals speed multiplied by time, not s = v - t. At 6 mm/s, the corresponding conveyor length is 1,680 mm.
Separate speed behavior from process-flow behavior
| Observation | Engineering interpretation | Next decision |
|---|---|---|
| The layout runs at 200 mm/s. | The robot process can complete under the faster timing condition. | Retest at 100 mm/s and 50 mm/s. |
| The error appears at 6 mm/s. | The slower speed changes event timing and may expose a process-model synchronization issue. | Check part-presence signaling and waits in the robot sequence. |
| Intermediate speeds work but 6 mm/s fails. | This comparison supports a speed-dependent software defect or timing boundary, but does not prove one. | Capture the exact error and escalate the reproducible case to Visual Components support. |
The reported failure time is inconsistent: one observation says the error begins around minute 4, while another says the process works for 6 minutes before failing. Record the precise elapsed time during repeat tests instead of using either value as a confirmed threshold.
Test the robot synchronization
- Run the unchanged layout at 200 mm/s, then at 100 mm/s and 50 mm/s. Record whether it completes and the elapsed time at failure.
- At 6 mm/s, verify that a part-presence sensor or equivalent process signal tells the robot when the part reaches the required position.
- Temporarily test a 0.1-second delay at the suspected synchronization point and observe whether the failure behavior changes. Treat a change as diagnostic evidence, not as proof that the delay is the final correction.
- Capture the exact script error, process state, conveyor speed, and robot step when the fault occurs.
Decide between model correction and support escalation
If the sensor or delay test changes the result, inspect the process-model flow for a missing event, premature transition, or wait condition. If 200, 100, and 50 mm/s work while 6 mm/s consistently fails with the same process logic, preserve the reproducible test case and contact Visual Components support. Without the attachment's error text, the affected software version and specific defect remain unknown.
FAQ
Calculate using the measured conveyor path. A speed of 6 mm/s produces that travel time only when the path is 1,680 mm.
Why does the robot script fail at 6 mm/s but run at 200 mm/s?
The evidence suggests that slower motion may expose a process-flow or synchronization problem. Test part-presence signaling and compare operation at 200, 100, 50, and 6 mm/s before classifying it as a software defect.
When should I contact Visual Components support?
Escalate when the same layout works at 200, 100, and 50 mm/s but repeatedly fails at 6 mm/s. Include the exact script error, elapsed failure time, process state, and robot step.
