Board-level ranging module, or a cased industrial sensor?
Both measure distance with a laser. They are not substitutes, and the comparison that matters is not “which is better” but “which one belongs in your product”. This page lays out the split with the questions that actually decide it, using the industrial instrument class that buyers usually compare us against — Keyence LR-T / LK class, SICK DT35 / Dx35 class, Dimetix DLS-C class — as the reference point. Their specifications are on their own datasheets; check them there, not here.
The difference in one table
| Cased industrial sensor (instrument class) | Board-level module (what we build) | |
|---|---|---|
| What you receive | A finished instrument: housing, window, connector, display or LEDs, mounting features | A populated board with the optical bench, receiver, timing electronics and a serial interface; no housing |
| How it connects | Terminal block, M12 connector, analog output or IO-Link; an electrician can wire it | UART-TTL header or cable; a firmware engineer integrates it |
| Environment | IP65–IP67 claimed by the vendor, with the certification to match | Your enclosure, your gasket, your IP claim — the module is a component inside it |
| Quantity | Buy one, buy ten; per-unit list price | Per-unit price that falls with volume; designed to be built into a product line |
| Where the cost sits | Front-loaded: you pay for housing, display, certification and support per unit | Back-loaded: you pay engineering once, then a component price per unit |
| Who it suits | Machine builders, integrators, maintenance — one sensor on one machine | OEMs building the sensor into their own product: UAV payload, AGV, gimbal, level instrument |
Five questions that decide it
- Does the distance number leave your product, or stay inside it? If the sensor feeds your own firmware and your own display, a module is the cheap path. If the number goes to a PLC over an analog card, an instrument is the short path.
- How many units a year? One to twenty: an instrument almost always wins once you count engineering hours. A few hundred plus: the module’s unit price and the freedom to put the optical head where the geometry needs it start to matter more.
- Who owns the enclosure, the window and the IP rating? A module puts that on you. That is not a drawback if you already build a housing; it is a hard blocker if you do not.
- Do you need the measurement head separated from the electronics? Board-level wins outright here: the optics can sit millimetres from the target plane while the host board sits where the heat and the harness are. An instrument fixes both in one box.
- Which support model do you want? Instrument vendors give you a regional application engineer and a replacement unit. We give you a datasheet, a protocol document, driver examples and an engineer by email — and we expect you to be the one integrating.
Where the board-level path wins in practice
- Payload weight and volume. A module measured in grams changes what airframe or gimbal you need; a cased instrument adds a bracket and a cable.
- Power budget. Our modules run on a 3.3–5 V rail; the H series takes 9–36 V DC directly. You integrate into the rail you already have instead of adding a supply for an instrument.
- Interface control. You get the distance as a frame with a checksum, at the update rate your control loop needs — not one value per second on an analog wire.
- One optical design across a product family. The same module line ranges from a 9 m guard to 18 km long range, so a product family can share integration work. See the 1 km comparison and the 300–3,000 m range guide.
Where the instrument path wins, honestly
- You need one sensor on one machine and an electrician to mount it on Friday.
- You need an IP67 rating you can point at in a tender document.
- You need analog output or IO-Link as a first-class feature, not an add-on.
- You need a local service contract with a replacement unit inside 24 hours.
We do not compete on any of those four. If they are your requirements, buy the instrument — and come back to us when the volumes justify a custom board.
If you are in the middle
The usual compromise is a module inside a small enclosure of your own, with a cable gland and a serial connector, built once and reused across the product line. That is what most of our OEM customers do, and it is the configuration where the OEM/ODM process page is worth reading before you design the housing.
Start from the specification, not the shape: tell us the range, the target and the conditions, the interface, and the annual volume — we will say whether a module or an instrument is the right answer for that case, including when the answer is “not us”. tommy@erdimail.com, one working day (Chengdu, UTC+8).
Brand and model names above identify the industrial instrument class for comparison. Their specifications, prices and certifications are set by those vendors; verify them on the vendors’ own documentation before relying on them.
Related reading: HS code and import declaration elements · Getting 4–20 mA out of a UART module