NIT SWIR Camera Integration: Engineering & Setup 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.

For USB 3.0 and GigE models covered by the NIT Quick Start Guide, use NITVision. For Camera Link M-SE/M-STE models, use NITLink for camera control and frame-grabber software for image acquisition. For Camera Link M-S/M-ST models, the guide specifies WiDyCAM, except SenS 1280 M-ST which uses NITVision. SDI/analog models use NITLink for control and a compatible display or video acquisition system for images. Newer models may have different software: verify the supplied documentation.

No. The NIT Quick Start Guide identifies its GigE camera range as GigE Vision compliant, enabling compatible third-party acquisition software. USB, Camera Link, and SDI/analog cameras use other transport and control arrangements. Do not assume a universal GenICam interface; confirm the exact camera model.

The supplied Quick Start Guide describes Windows setup and NITLibrary SDK examples for USB and GigE cameras in C++, C#, and Python (specific Python versions listed in that guide are historical). Current OS, architecture, driver, and language support must be verified with the SDK release supplied for your camera. Camera Link integration options depend on the model and frame grabber.

Use the supplied camera power adapter and cable unless the model-specific documentation explicitly approves an alternative. Some GigE configurations offer optional Power over Ethernet; some Camera Link configurations offer optional Power over Camera Link. USB models with a Hirose power connector may require separate power for the thermoelectric cooler. Never transfer voltage, current, or connector specifications from another model.

Refer to the specific camera datasheet or interface-control document and confirm connector orientation before wiring. NIT models use different connectors and pin assignments, including Hirose, SMA, and other interfaces. The general Quick Start Guide is not a substitute for a model-specific pinout.

Many NIT cameras support external triggering, but allowable voltage levels, pulse widths, polarity, timing, and connector pins are model-dependent. Never connect a 24 V PLC output directly without confirming input ratings. Where necessary, use an appropriately designed isolated or level-shifting interface.

Obtain the model-specific mechanical drawing, mount specification, lens flange requirements, connector locations, and heatsink envelope. Avoid excessive mechanical force on the C-mount, housing, or electrical connectors. Account for cable bend radius and airflow in the final enclosure.

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.

Operating temperature, storage temperature, thermal dissipation, vibration, and enclosure requirements vary by camera. Consult the model datasheet. NIT warns against extreme environments, strong electromagnetic fields, hazardous chemical atmospheres, moisture, and mishandling.

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.

Start with internal or free-running acquisition to verify the image stream. Then select external triggering if required by the application and validate the input timing with the model reference guide. A camera left in external-trigger mode may display no image if no trigger pulses are supplied.

A smaller ROI reduces image dimensions and may permit higher acquisition rates, depending on the sensor and interface. Confirm supported ROI dimensions, offsets, pixel format, and frame-rate limits for the selected camera; these are not uniform across NIT models.

Estimate raw payload as image width × image height × transmitted bits per pixel × frames per second ÷ 8. Add margin for packing, protocol overhead, host processing, and storage. Validate sustained throughput on the actual USB, GigE, or Camera Link acquisition chain.

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 the supplied version of NITVision and the correct Windows driver, then attach the camera to a genuine USB 3.0 port using a suitable cable. Prefer a direct motherboard port rather than a hub. Connect the separate power supply if required by the model. In NITVision select USB 3.0, choose the detected camera, and start acquisition. Check Device Manager and USB 3.0 negotiation if discovery fails.

Connect a Cat 5e or better Ethernet cable, supply external power unless the ordered camera supports PoE, and use a suitable network adapter. Permit NITVision through applicable firewalls and ensure a reachable IP configuration. In NITVision select GigE, select the camera, and start acquisition. For sustained high throughput, the guide recommends tuning jumbo frames, interrupt moderation, and receive buffers where supported.

Connect the Camera Link cable securely to a compatible frame grabber and provide camera power unless Power over Camera Link is supported and ordered. Configure the frame grabber first. M-SE/M-STE models use NITLink via a Windows COM port for control while the grabber acquires images. M-S/M-ST models generally use WiDyCAM; the guide treats SenS 1280 M-ST separately with NITVision. Check frame-grabber compatibility for each configuration.

For supported USB and GigE cameras, use the NITLibrary SDK and supplied C++, C#, or Python examples. The guide identifies GigE Vision interoperability for GigE models. For embedded Camera Link M-SE/M-STE and SDI/analog models, consult the NITLink serial-control protocol and use a separate image-acquisition path. Other Camera Link SDK options require model-specific confirmation.

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.

Correction methods depend on interface and software. USB NITVision and WiDyCAM configurations may require calibration files in a folder named for the camera serial number. For GigE NITVision, check NUCActivate and NUCMode where available. For NITLink-controlled models, refresh the NUC parameters and confirm correction is activated. Keep calibration files matched to the exact camera.

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.

First check non-uniformity correction. In USB NITVision or WiDyCAM, confirm the camera serial-number calibration folder is present. In GigE NITVision, check NUCActivate and NUCMode if available. In NITLink, open the NUC tab, refresh parameters, and check Activate NUC. If the problem persists, contact support with sample images and camera serial number.

Verify the Windows COM port and the configured serial baud rate. The guide identifies 57600 as a default for the covered NITLink configurations; an earlier saved setting may differ. Try only supported baud rates and consult the relevant NITLink reference manual before saving new settings.

Check power, Ethernet link, firewall permissions, network-adapter settings, and whether the camera IP address is reachable on the host subnet. The Quick Start Guide describes a temporary Force IP recovery method for certain models, followed by persistent configuration in NITVision. Use a current manufacturer-approved recovery utility and coordinate address 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.

USB 3.0: camera, suitable USB 3.0 cable, host computer, and separate power supply if specified. GigE: camera, Cat 5e or better Ethernet cable, network adapter, and external supply unless optional PoE is supported. Camera Link: camera, Camera Link cable, compatible frame grabber, and supply unless optional Power over Camera Link is supported. SDI/analog: camera, compatible video display or converter, and RS-232 interface for control. Check the supplied accessory list for your model.

Attach the specified camera control connector and RS-232 interface, connect the video output to a compatible display or capture system, and use NITLink to select the camera and connect through the correct COM port. NITLink controls settings; video is viewed or captured through the separate video path.

Identify the exact camera model and interface; verify supplied cables and power; install the matching driver, control software, and frame-grabber software where applicable; connect the camera; confirm discovery; select internal/free-running triggering; start acquisition; adjust exposure and gain; verify NUC and TEC stabilization if fitted; and save the working configuration. Introduce external triggering and production software only after a stable image stream is established.

Do not open the camera or touch or clean the sensor window yourself. Use only an approved supply, protect connectors and lens mount from excessive force, and keep the camera away from moisture, extreme conditions, strong electromagnetic fields, and hazardous atmospheres. Consult the model-specific operating limits.