SWIR Camera Engineering & System Integration FAQ

Freeze target wavelength, smallest feature, object FOV, working distance, motion speed, illumination, frame rate, exposure, host OS, interface, mechanical envelope, thermal environment and synchronization. Obtain exact model, revision, firmware and electrical/mechanical ICD.

USB 3.0 suits direct PC connections; GigE Vision supports networked machine vision; Camera Link requires a frame grabber. SDI/analog variants suit video systems. Evaluate bandwidth, cable length, driver support and acquisition software.

NIT Quick Start rev. 2.0 maps many USB/GigE models to NITVision; certain non-embedded Camera Link models to NITVision or WiDyCAM; and embedded Camera Link/SDI models to NITLink or NITGenicamControlTool. Confirm the exact model against section 4.2.1.

No. G-STE2 is GigE Vision/GenICam compliant, while certain embedded models use GenICam/GenCP through a COM port. Other models use NITLink or NITCAM protocols.

The G-STE2 datasheet lists Windows/Linux x64/aarch64 NITVision and NITLibrary with C++/Python. The general NIT guide lists C++ for NITVision-compatible models and C#/Python for supported USB/GigE models. Verify SDK versions and platform for the specific camera.

The G-STE2 datasheet specifies 6–24 V input, supplied 12 V adapter, camera power below 5.5 W, plus selectable TEC power. PoE is an optional ordered configuration. Do not use these limits for other models.

On its 12-position Hirose connector: 1 and 9 = 6–24 V; 2 and 8 = power ground; 3 = Trigger OUT2; 4 = Trigger OUT1; 10 = LVTTL Trigger IN/OUT; 12 = trigger ground; 5/6/11 = NC; 7 = reserved. Verify connector orientation against datasheet page 5 before wiring.

No, not to a documented LVTTL input. Use an appropriate isolated or level-shifting interface and verify logic levels, polarity, ground reference and protection against the full model-specific ICD.

Without heatsinks: 640 model 46 × 46 × 65.4 mm; 320 model 46 × 46 × 59.7 mm, both C-mount. Datasheet pages 6–9 contain mounting and heatsink drawings; check cable clearance and mounting depth.

TEC cooling transfers heat to the housing; provide heatsinking and airflow. Monitor actual versus target sensor temperature at worst-case ambient conditions. NIT links unstable TEC temperature to image artifacts.

Only for G-STE2, the datasheet lists −40 to +71 °C operating and −40 to +80 °C storage. Validate condensation, vibration, EMC, ingress and enclosure heating separately.

Compute active sensor size = pixels × pitch. Choose image circle, focal length, working distance and wavelength transmission to meet FOV. Object-space sampling = FOV/pixels; verify MTF, focus shift, distortion and lens mount clearance.

Blur ≈ object velocity × exposure time. Keep blur below the permitted object-space feature/pixel scale. Use brighter illumination, a strobe or shorter exposure where feasible.

Define a master PLC, encoder or motion-controller signal; validate trigger polarity, pulse width, exposure latency, strobe timing and jitter with a scope. For line scan, use encoder-linked line timing to preserve aspect ratio.

The datasheet lists internal/external LVTTL/software triggers, selectable delay, global shutter, ITR/IWR and exposure by register or trigger width. Obtain the full camera reference guide for exact electrical and timing constraints.

ROI reduces image dimensions and may increase frame rate. G-STE2 specifies eight-pixel ROI increments. Confirm allowable offsets, output geometry and maximum achievable rate.

Raw payload ≈ width × height × bits per pixel × frames/s ÷ 8. For 640 × 512 at 12 bits and 260 fps, raw payload is about 128 MB/s before transport overhead; actual packing and throughput vary.

NIT directs customers to https://new-imaging-technologies.com/software-log-in/. Archive the supplied installer, SDK examples, reference guide, calibration files and firmware by model and serial number.

Install model-matched NITVision and driver, connect directly to a genuine USB 3.0 port, and attach separate power if required. Avoid hubs and troubleshoot USB selective suspend and driver architecture if detection or acquisition fails.

Use Cat 5e or better, connect required power or ordered PoE, configure NIC and IP subnet, and allow camera software through the firewall. NIT recommends tuning jumbo frames/receive buffers and avoiding congested switches.

Install and validate the frame grabber, cable and camera power. Configure pixel format, geometry and acquisition in frame-grabber software. For NITLink/GenICam embedded models, expose the grabber serial channel as a Windows COM port; the control utility does not itself acquire the image.

Use NITLibrary and supplied samples for supported NITVision cameras. Use NITLink serial protocol documentation for appropriate embedded models, or GenICam libraries for compliant models. Confirm feature names and supported SDK versions rather than assuming universal APIs.

The supplied documents do not establish universal native MATLAB or LabVIEW support. Validate the exact transport, drivers and SDK wrappers; GenICam compliance may enable third-party machine-vision applications but should be tested.

Preserve camera-specific calibration files. NITVision may require the serial-number-named SN folder; G-STE2 documents onboard factory 2-point NUC and bad-pixel maps. Verify correct correction enablement, operating temperature and firmware.

Log camera serial/firmware, exposure, gain, ROI, correction mode, sensor temperature, frame count, dropped frames and part ID. Implement clear discovery, thermal stabilization, acquisition, recovery and shutdown states.

Check external-trigger selection first: free-run requires internal trigger. Then check link bandwidth, driver, power, frame grabber geometry, ROI, host CPU and buffer/storage throughput.

Check serial-matched NUC files or onboard correction activation and verify TEC stabilization. The NIT guide provides different NUC checks for USB, GigE, NITLink and GenICam cameras.

Check COM-port selection and baud rate. The guide identifies 57600 as the default for certain NITLink cameras; use the model’s supported alternatives and save settings carefully.

Check camera power, Ethernet link, firewall and IP subnet. NIT documents temporary force-IP recovery followed by persistent configuration; coordinate changes with IT.

Test power cycles, startup time, maximum sustained frame rate, dropped frames, trigger jitter, strobe timing, thermal stabilization, worst-case ambient temperature, NUC behavior, optical sharpness and host restart. Record results for each hardware/software revision.

Provide camera serial and model, firmware/SDK versions, host OS, interface and wiring, exact error, sample images, relevant logs, temperature readings and troubleshooting already attempted.