Hikrobot Vision Sensors
Use this guide to connect a supported camera, obtain an image and configure an inspection in SCMVS. Record your full model code, firmware and SCMVS version first. SC2000 and SC2000E are different hardware generations: the SC2000E wiring examples below refer to Hikrobot guide UD27618B-B, V1.1.0 (2023). Use the exact device manual for electrical connections and the installed SCMVS help for version-specific controls.

Supported SC-series models are configured with SCMVS. Inspection processing runs on the device. The supported outputs, protocols and tools depend on the full model code, firmware and software release; confirm these before configuring the PLC interface.
Select the supply according to the exact model’s rated voltage and power consumption. Confirm the wiring and polarity with the power disconnected. Use 24 VDC only where specified for that device and cable assembly.


SCMVS provides device discovery, configuration and inspection monitoring. Install the supported release before configuring the camera network and logging in. The installer image below shows SCMVS V3.3.0. The download example lists both MVS and SCMVS; select the package that supports your exact smart camera. Menu names and available tools vary by release.
Both packages are available on the Hikrobot Download Center:
Hikrobot Download Center →Smart Camera software, projects, tools, I/O, output. This is the main software for projects and inspections.
Viewer + IP configurator. Fallback for network access, not intended for inspection projects.
Check the operating-system and device compatibility in the release notes of the selected SCMVS package. MVS and SCMVS are separate products; support listed for one package does not establish support for the other. Record software and camera-firmware versions in the machine documentation.


For the direct local connection described here, PC and camera must use the same subnet. For example, with subnet mask 255.255.255.0, addresses in 192.168.1.x can share the local subnet. Choose different, unused host addresses for PC and camera. Agree production-network changes with its administrator.
Use SCMVS to discover supported smart cameras, change the IP address, build inspection projects and set up I/O.
MVS provides a viewer for supported devices. It does not replace the SCMVS inspection workflow. Check compatibility first before using MVS to investigate a device that SCMVS cannot discover. MVS support must be documented for the exact camera.
192.168.1.64
If SCMVS cannot discover the camera, check power, link, subnet and software compatibility first. Use MVS only when its device-support information includes your model. Its discovery and IP functions do not establish that SCMVS inspections can run in MVS. Depending on device support, the following checks may be available:
MVS is on the same Hikrobot Download Center as SCMVS (Software → MVS Client).
192.168.1.64
User Name: admin
Password: Abc1234

A trigger is a signal that tells the camera when to take a new image. As soon as the trigger comes in, the camera captures an image and immediately performs the set inspection.
Without a trigger, the camera waits for the next signal. The camera will not take a new image and will not perform a new inspection.
A trigger does not always have to come from a PLC. A photocell, push button, encoder or the physical trigger button on the camera can also be used as a trigger source. Which source is available depends on the camera model and configuration.
Smart cameras can usually work in two ways.
In continuous mode, the camera is constantly taking new images. This is useful when developing an inspection, as changes are immediately visible.
Typical applications:
In trigger mode, the camera waits for an external signal. Only when a trigger is received, one image is created and the inspection is carried out.
Trigger mode links acquisition to an event in the machine. Verify trigger acceptance, exposure timing and the result deadline at the required product rate; selecting trigger mode alone does not establish correct timing.
The trigger can come from different devices.
| Trigger source | Scope |
|---|---|
| PLC | Product comes in the right position |
| Photoelectric sensor | Product passes the sensor |
| Encoder | Position on a conveyor belt |
| Push button | For manual testing. |
| Trigger button on camera | Testing during installation |
| Software Trigger | Testing from SCMVS or Hikrobot software |
Digital inputs and outputs connect the camera to machine control. The pictured settings show Line 0 as a trigger and Line 1 as a PNP output for that setup. This is not a universal SC-series configuration; for SC2000E, follow the model-specific NPN information below.
An input receives an electrical signal.
Examples:
An output sends a signal to another device.
Examples:
With industrial sensors, there are two commonly used ways to connect digital signals.
| Type | Function |
|---|---|
| PNP (Sourcing) | Sources current from the positive supply when active; the voltage follows the specified circuit. |
| NPN (Sinking) | Connects the output to 0 V when active |
Match each output circuit to a compatible receiving input. Check voltage thresholds, current limits, common reference and required pull-up or pull-down resistors using both manuals. A shared PNP/NPN label alone is not a wiring diagram.

For SC2000E in UD27618B-B, Line 0/1 are configurable I/O, Line 2 is input and Line 3 is output. Chapter 7 lists Line 0 as the default trigger and Line 1/2 for project switching. Start by testing one configured trigger source and verify its acceptance in SCMVS and the PLC. Check simultaneous-source restrictions in the installed version’s help.
Configure I/O via: Menu → IO Settings / IO Allocation

The workflow below covers image setup, inspection tools and result reporting. In the main-window image, the camera image is on the left, tools are on the right, detailed results are at the bottom and the menu is at the top. The Dutch annotations identify these areas. The displayed 94% is the pass ratio for that example session, not a measure of inspection accuracy.

The base image provides the image used to configure the inspection. Set focus, illumination, exposure and gain first. Retain separate good, defective and borderline images to test the configuration; a single reference image does not validate the decision.

Inspection tools evaluate a defined region of the image. Add the required tool, select its region of interest (ROI) and set the decision thresholds. Define how the tool results combine into the final decision and test that logic with representative good and defective products.

Configure a supported output method for the exact camera. Agree result-valid signalling, acknowledgement and a timeout with the PLC engineer. Test pass, fail, missing image and lost communication. Never treat a retained result from an earlier product as a fresh decision.

The categories below explain typical inspection functions. Available tools and licences vary by model and SCMVS release. Confirm the tool in your installed device environment before designing the inspection around it.
Is the item present? Edge, spot, contour, circle, pattern existence.
Count objects: spot count, edge count, contour count.
Distance, width, diameter, angle, contrast, grayscale.
Classification or character recognition where supported. Confirm the required training or character-set configuration and test independent samples.
Combine tool results: AND/OR, conditions, format output.
Locate a reference feature and move inspection regions with it. Define an invalid result when the reference cannot be located.

Check the power supply (indicator on?), network cable and whether you are on the same subnet. Click refresh in SCMVS. If the camera still does not appear, or the IP change does not work, use MVS only if it supports the device; otherwise provide the model, serial number and network settings to support.
Image is too darkCheck whether the light is enabled, aimed correctly and synchronized with exposure. Increase light output within its ratings before extending exposure beyond the motion-blur limit. Gain raises noise as well as brightness. Retest representative bright and dark surfaces after any adjustment.
No image in live viewCheck acquisition mode and whether a trigger is accepted. In a controlled setup test, use a supported software or physical trigger, or temporarily select continuous acquisition. Restore the intended production mode afterwards and verify the PLC-triggered result.