Omron 3Z4S-LE VS-MCL50-FNO56/M42-10 — 50 mm F5.6 Vibration-Resistant M42 Lens

Applications this camera is commonly selected for. Open one to see the full recommended hardware and approach.

• datasheetOmron / Sentech 3Z4S-LE VS-MCL50-FNO56 — manufacturer page →
• datasheetOmron / Sentech 3Z4S-LE VS-MCL50-FNO56 — manufacturer page →
• softwareSentech SDK (StViewer + StApi) →
• downloadsOmron / Sentech software & SDK downloads →

These steps take an Omron Sentech (STC) camera from the box to a stable first image and on to your own application. They apply across the GigE Vision, USB3 Vision and CoaXPress STC families; the interface only changes how you cable and power the camera.

Software: Sentech SDK (StViewer + StApi)

1. 1. Install the Sentech SDK (StViewer and StApi)

   Download and install the Sentech SDK on the host PC. The package provides StViewer, the viewing and configuration software you use to bring the camera up, and StApi, the programming SDK you integrate later. Because the cameras are GenICam/GenTL-compliant, StApi also registers a GenTL producer, so any GenICam-compliant third-party vision software can discover and drive the camera as an alternative front end.

2. 2. Cable, power and connect the camera

   Connect according to the interface. GigE Vision: link to a Gigabit NIC (use PoE or the separate power input) and put the camera and host on the same subnet; for USB3 Vision use a USB 3.x port and a certified cable; for CoaXPress (STC) connect to a CoaXPress frame grabber, which also supplies Power-over-Coax. Then open StViewer and let it enumerate the camera. If a GigE camera does not appear, check the IP configuration and firewall, and on USB3 confirm the host bandwidth and driver.

3. 3. Configure exposure, gain and white balance

   Open the device in StViewer and start a live stream. Set exposure and gain for a well-exposed, low-noise image: raise exposure first and only add gain when more light or a faster shutter is not an option, keeping exposure short enough to freeze motion on global-shutter models. On colour cameras, run white balance under your actual production lighting. Adjust the lens aperture and focus on a representative target before tuning anything else.

4. 4. Set the trigger and grab a first image

   Start in free-run (continuous) acquisition to confirm a clean, stable image. For inline inspection switch to hardware or software triggering: select the trigger source, set the active edge and any delay, and wire the strobe or illumination to the camera's I/O so lighting fires with each exposure. Acquire and save a frame in StViewer; this saved image is your reference for the SDK stage and for downstream inspection.

5. 5. Move to the StApi SDK (or any GenICam software)

   Once the image is stable, reproduce the same settings in code. Use StApi to open the device, apply the GenICam features you validated in StViewer (exposure, gain, trigger, pixel format) and grab frames into your application via the bundled C++, C, C#/.NET or Python interfaces; the included samples are the fastest starting point. Prefer a different stack? The same GenICam/GenTL camera works with third-party vision libraries. With a reliable feed, you can route it into a deep-learning inspection such as Rosepetal for AI-based defect detection.