Docs
Prepare the hardware, sample set and machine-interface decisions for your first SCMVS session. Use this checklist to identify missing inputs, define the first test and collect useful evidence if setup fails.
A first setup session can stall because a cable is missing, the camera address conflicts with the plant network, or nobody has defined what the inspection should reject. This checklist prepares the equipment and decisions needed for the SC1000/SC2000 quick start. The quick start contains the commissioning sequence; use this article to arrive at that sequence with the right inputs.
Record the exact camera model and serial number. Obtain its connector diagram, power requirements and supported SCMVS release. Confirm whether a separate lens, external light and light controller are needed. An Ethernet connector alone does not establish support for Power over Ethernet.
| Preparation | What to record | Ready when |
|---|---|---|
| Camera and software | Model, firmware and supported SCMVS version | The software supports the exact device. |
| Power and cabling | Supply specification, connector pinout and cable part numbers | Connections can be checked against the model documentation. |
| Optics and mounting | Lens, working distance, inspection area and mounting position | The feature and position variation fit the intended image. |
| Network | Camera and PC addresses, subnet and responsible IT contact | The addresses are available on the agreed network. |
| Machine interface | PLC type, supported protocol or digital signals, result deadline | The PLC engineer can define the trigger/result sequence. |
For a bench trial, use an isolated test network where practical. For a machine-network connection, agree address changes with the person responsible for that network. Keep the model documentation available during wiring and commissioning.
Write a sentence that describes the required decision. For example: “Reject a product if the cap is absent.” This is an illustrative task, not a reported customer result. Decide separately whether a tilted cap or a wrong-colour cap must also be rejected; those are additional conditions to test.
Prepare good products, known defects and borderline examples. Identify each sample and record its expected outcome. Include changes in position, surface finish and ambient light that production permits. Keep a separate validation set rather than using every sample to tune the first configuration.
These checks do not establish production performance by themselves. Set acceptable missed-defect and false-reject limits, the required sample coverage and the timing test conditions before deciding whether a production trial can proceed.
If the camera is not found, record the power indication, network link, addresses and software version. If the image is unusable, retain an example image with exposure, lighting and working distance. If a tool gives the wrong decision, provide the original image, tool settings and expected result. If SCMVS shows a result but the PLC does not, capture the signal or message sequence and timeout behaviour.
This evidence separates connection, imaging, inspection and communication problems. It also makes a support session easier to prepare than a general report that the camera “does not work”.
Allow for mounting and lighting trials, inspection configuration, PLC work, validation, operator instructions and backup restoration. Estimate each activity as hours multiplied by the applicable rate, and include any planned production interruption. Use the first session to replace uncertain assumptions with observations; do not infer payback from the hardware price.
Once the preparation is complete, follow the quick start. Use the SCMVS manual for further configuration detail. If the task exceeds the selected camera’s tools or timing, review the vision architecture before adding more hardware.

Send the exact model, SCMVS version, sample images and the step that fails. We can then discuss the connection, image settings or inspection configuration with the relevant evidence.