Technical support and project documentation
A clear product revision and reproducible conditions make a technical discussion more useful. Prepare the following information before debugging or requesting documentation.
Product and environment
Provide the model or sample identifier, hardware revision, host and carrier board, connection diagram, cable and power conditions. Include the operating system, kernel or BSP release and capture application.
Reproducing the issue
Describe the expected result, observed behavior, when the issue first appeared and how to reproduce it. Note whether it is limited to a mode, cable, motion or lighting condition.
Useful attachments
Include original logs, capture settings, image files or short clips without additional compression, and connection and installation photographs. If using screenshots, retain the full error message and timestamp.
Documentation and software requests
List the documents needed and their purpose, such as pinouts, dimensions, capture instructions or software for a specific version. Confirm source code, drivers, calibration files and adaptation scope within the project.
Can the module be adapted to the equipment space?
Share the dimensional envelope, mounting points, lens clearance and connector orientation to discuss hardware customization. The available changes, design scope and prototypes are confirmed per project.
Are GMSL, MIPI, stereo and low-light mutually exclusive categories?
GMSL and MIPI describe interface choices; stereo and low-light describe imaging requirements. Specify both the interface and imaging configuration when selecting a module.
Can a camera connect to our existing NVIDIA platform?
Provide the compute module, carrier board, JetPack / Jetson Linux versions, interface and capture mode. Support is reviewed for the specific camera and platform combination.
Can I download a driver directly?
Drivers must match the module and software release. Provide the product or sample identifier, host platform and software versions to confirm the relevant package. The resource page currently provides selection and development checklists.
Does a stereo module output depth directly?
Specify whether you need two original image streams, rectified images or depth output. Agree processing, calibration and output format separately.
What minimum illumination can a low-light module operate at?
This requires testing the selected module, optics, exposure, gain, frame rate and image-quality criteria. Provide the scene and task so illumination figures can be evaluated with their test conditions.
Are automotive certifications or ingress-protection ratings available?
State the requirement in the project brief and check valid documents for the exact model and scope. A product category does not establish certification or testing of a particular model.
What are the sample quantities, minimum order and lead time?
These depend on the model, customization scope, materials and project schedule. Include expected prototype quantities and target dates in the inquiry.
Does the project include source code or calibration files?
Agree documentation, binaries, source code, calibration files and their terms of use as individual deliverables.
Can we discuss a project before all parameters are fixed?
Start with the equipment, subject, existing platform and main constraints. Mark open items and develop the selection and validation checklist from there.
What criteria apply to production and testing?
Agree the reference sample and revision, inspection items, test conditions and pass criteria for the project. Define the scope and documentation for any environmental or certification requirements.
Can I order directly on the website?
The website currently supports product information, technical resources and project briefs. Pricing, ordering and delivery terms are confirmed per project.