Insect GateTechnology
Purpose-built sensing for low-power insect monitoring.
Unlike a conventional digital break-beam detector, Insect Gate samples two analogue optical channels at each entrance. Crossing order gives direction. The waveforms give transit time, attenuation and signal shape. Those features are processed locally to filter and classify activity without transmitting images.
Optical architecture
Each of the four corner entrances contains Beam A and Beam B. Both are sampled as analogue measurements rather than treated only as digital beam-break states. From a single passage the firmware can extract the A and B crossing order, transit interval, pulse width, minimum signal level, attenuation area, slope, asymmetry, multi-peak structure and passage duration.
These features provide the basis for event filtering and classification. They do not guarantee species identification, and the system is designed to say unknown rather than invent a class.
Classification, stated carefully
Insect Gate combines lure selectivity with dual-beam optical sensing. Analogue signal characteristics can be used to distinguish different types of movement and improve rejection or classification of non-target events.
Where confidence is reported, it is reported as high, moderate or unknown rather than as a percentage that implies more certainty than the data supports. Every event is stored with the firmware and classifier version that produced it, so history remains traceable as the models improve.
| Events | Qualifying optical passages |
|---|---|
| Entries and exits | Events with a direction from the A and B crossing order |
| Classification | Target, non-target or unknown, with a confidence level |
| Features | Direction, transit speed, signal attenuation, waveform morphology |
| Traceability | Firmware and classifier version stored with every event |
System architecture
A low-power STM32WL handles control, LoRaWAN communications, event processing and system supervision. A separate radio module provides Bluetooth Low Energy for commissioning and servicing on site. Sensing, processing and reporting all happen inside the unit, so nothing leaves it but event data and device health.
We do not publish schematics or internal interfaces. A customer needs the measurements, not the circuit.
| Control and LoRaWAN | STM32WL, low-power operation with an integrated sub-GHz radio |
|---|---|
| Commissioning | Bluetooth Low Energy, on site |
| Uplink | Events, direction, classification, battery, health |
| Buffer | Events retained locally if the gateway is unavailable |
| Images | None captured, none transmitted |
Connectivity
Monitors communicate over LoRaWAN, which lets large numbers of low-power devices report through a small number of gateways. One gateway can connect a property; actual coverage depends on building construction and the radio environment, and a first-site walk confirms it.
Nothing connects to the property's Wi-Fi and no unit carries a SIM. Bluetooth covers the last metre when a technician is standing over the device.
Security by design
LoRaWAN traffic is encrypted end to end under the standard, and every device joins the network with its own credentials. Console access is role-based, with separate technician, manager and read-only client roles. No images are ever captured, so there is nothing sensitive to secure at the sensor.
Enterprise deployments can add single sign-on, an API and integration with facilities systems.
Servicing
The product is designed around long unattended service intervals, with lure and battery replacement incorporated into the planned service cycle. The console tracks lure health as a percentage and flags a device before it needs attention.