What NeoEyes NE302 Actually Is
NeoEyes NE302 is a compact camera and compute subsystem for teams adding a specific visual function to indoor equipment or terminals. The 38 × 38 mm Main Board combines a 4 MP image sensor, an STM32N6 vision MCU, an STM32U0 control MCU, runtime memory, Flash, and wireless hardware. The Interface Board adds USB Type-C power, MicroSD storage, and the connections used for programming and service.
That combination changes the starting point for a project. A team can work with camera preview, image capture, a packaged AI model, trigger logic, local records, and an external result path before designing its own carrier or camera electronics.
The standard NE302 device packages the Main Board and Interface Board in a 42 × 42 × 20 mm indoor enclosure.
The Two-Board Hardware Architecture
The Main Board is the product’s vision core. The OS04C10 4 MP sensor connects to the STM32N6 through the camera data and control paths. The STM32N6 connects to 32 MB PSRAM, 64 MB OSPI Flash, and the fitted wireless module. A separate STM32U0 handles power-control and wake-related signals.
The Interface Board makes the first evaluation easier. It provides USB Type-C power, MicroSD, separate programming paths for the N6 and U0 MCUs, and serial access. Teams evaluating the complete device can use both boards in the 42 × 42 × 20 mm enclosure. A custom product can instead evaluate Main-Board-only integration with DC power and carry those results into its electrical and mechanical design.
| Hardware | Primary Role | What It Changes for Evaluation |
|---|
| Main Board | Camera, STM32N6, STM32U0, PSRAM, Flash, and wireless circuits | Provides the image, AI, control, and connectivity core in a 38 × 38 mm footprint. |
| Interface Board | USB Type-C, MicroSD, programming, serial, and service access | Lets a team power, inspect, flash, and store records without first designing a carrier. |
| Standard Enclosure | Indoor installation with rear magnetic or adhesive mounting | Provides a complete device for camera, model, and system-path evaluation. |
| Source: CamThink NE302 Product Information and Components Overview. |
The Main Board concentrates the image, compute, memory, wireless, and wake-control paths.
How a 4 MP Image Becomes an AI Result
The data path starts with the camera, but it does not end with a frame. NE302 can encode media, run an INT8 model locally, apply device logic, keep a record, and deliver an output to another application.
- The 4 MP CMOS sensor supplies the image stream to the STM32N6.
- The device prepares the image for capture, hardware JPEG encoding, H.264 video, or the model input path.
- A compatible NE302 model package runs through the Neural-ART accelerator. The published compute ceiling is 0.6 TOPS INT8, while actual application performance depends on the model, input, memory use, firmware, and scene.
- The application handles the inference result together with trigger, storage, retention, and upload rules.
- The result can remain as a local record or leave the device through MQTT/MQTTS or Webhook. RTSP and RTMP support video paths exposed by the current firmware.
The Web console includes fixed-image validation so a team can check that the current model accepts an image and returns JSON before connecting an external receiver. This is an early compatibility check, not a substitute for camera-pipeline and field testing.
Fixed-image validation checks the loaded model and result format before the team moves to the live camera pipeline.
Continuous and Triggered Operating Paths
With continuous USB Type-C power, NE302 can provide preview, video, inference, device processing, and network services according to the current firmware configuration. This path suits a terminal or workstation that already has stable power and needs an active camera function.
The STM32U0 control domain also supports sleep and wake behavior. Current firmware can initiate capture from IO/PIR input, a remote MQTT command, or a schedule. Capture rules decide whether the device uploads immediately, keeps a local record, retries after a failed delivery, or retains an image for later review.
These paths share the same hardware but solve different data problems. Continuous operation keeps a live visual path available. Triggered operation concentrates capture, storage, and reporting around a defined event. The project still needs to choose one primary operating model before measuring power, latency, network use, and record behavior.
The Web Console and Open Project
The Web console brings the main evaluation tasks into one browser interface. A developer can confirm the camera preview, adjust supported image settings, upload an NE302 model package, validate a fixed image, configure wake sources, and inspect capture records. Data transmission pages expose the MQTT/MQTTS, Webhook, RTSP, and RTMP settings provided by the installed firmware.
The source project separates the first-stage bootloader, main application, Web interface, model package, wireless firmware, and WakeCore components. This structure lets engineering teams rebuild or update a specific part instead of treating the camera as a closed appliance. The App runtime and model package must use compatible ST Edge AI variants when a team rebuilds them.
The fastest way to see these parts working together is to follow the NE302 Quick Guide and complete one preview, one model validation, and one triggered record on the same device.
Where NE302 Fits
NE302 fits projects with a defined indoor camera position and a focused visual task. Typical starting points include a terminal that needs presence or state recognition, a workstation that reports a known equipment condition, a panel-reading prototype, or a compact node that sends structured detection results to an existing application.
It can also be a practical retrofit option for legacy equipment that still works well but was never connected to a digital system. Instead of replacing a functioning controller or modifying its internal wiring, a team can position NE302 in front of an analog gauge, LED panel, or legacy control display. A compatible model can recognize a reading or operating state locally, while the application sends the structured result through MQTT or MQTTS to an existing monitoring platform. The camera does not remove the need for engineering work: placement, lighting, model validation, and the interpretation of each display still determine whether the retrofit is reliable.
The complete two-board device is useful when a team wants a working camera for evaluation; the NE302 store listing is the direct route to the scheduled product release. Main-Board-only integration is the more relevant path when enclosure space, power input, or service access must become part of another product. The standard product can serve as evaluation hardware, while an application-specific configuration can be assessed after the camera, model, and output path have been proven.
Where NE302 Does Not Fit
NE302 is an indoor platform and does not provide the IP67 enclosure, LTE option, or standard PoE deployment path used by other CamThink cameras. Projects that need weather exposure, remote cellular service, or an outdoor battery design should start with a different hardware path.
The STM32N6 also sets a clear compute boundary. NE302 is designed for compatible INT8 models and focused embedded vision tasks. Heavy multi-model processing, many camera streams, containerized third-party applications, or large vision-language workloads belong on a Linux or higher-compute edge platform.
When choosing an integration path, confirm the selected NE302 SKU’s radio, antenna, lens, debug interfaces, power input, and exposed board functions.
What to Validate First
A useful NE302 evaluation answers five questions in order:
- Does the selected lens and mounting position produce an image with enough target detail under the real lighting?
- Can a compatible INT8 model package return the required result on fixed images and through the live camera path?
- Should the device run continuously, or capture around an IO/PIR, remote, or scheduled event?
- Does the application need a structured result, image evidence, a video stream, or a combination of them?
- Will the complete device or Main Board fit the product’s power, space, antenna, storage, and service constraints?
When those answers are based on the same camera, model, firmware, and receiver, the team has enough evidence to define the next PoC. The Wiki and source repository provide the versioned implementation details; this product view connects them into one system.
