Choosing a Module
Before starting hardware integration, you need to select the right KLSTR. module for your fixture. Both modules provide network-to-DMX bridging, but they target different use cases and integration depths.
Feature comparison
| Feature | KLSTR.nano | KLSTR.one |
|---|---|---|
| Form factor | System-on-Module (SOM), 2× 20-pin 2.54 mm headers | System-on-Module (SOM), castellated vias |
| Chip | Microprocessor, RS485 drivers, memory, encryption | MT7621DAT, memory, encryption |
| Integration style | Soldered/socketed inside the fixture | Soldered onto host PCB via castellated vias |
| DMX interfaces | DMX_IN, DMX_OUT (isolated), DMX_LAN (non-isolated) | Via KLSTR.nano in dual mode |
| Ethernet | Via host fixture or KLSTR.one (dual mode) | 5× Gigabit Ethernet (MDI transceivers) |
| Power | 6.3–32 V DC or 5 V DC from host | 3.3 V DC from host power supply |
| Typical power | 3.5 W | 2 W |
| Target | OEM integration, high volume | OEM integration, dual mode with KLSTR.nano |
Decision matrix
- You are a fixture manufacturer embedding networking directly into your product
- Cost per unit matters — high-volume OEM pricing
- You have an existing host CPU in the fixture that handles DMX decoding
- The fixture already has an EIA-485 transceiver for DMX_LAN communication
- You want the smallest footprint (the module sits on the host PCB)
- You don’t need standalone Ethernet — the fixture connects via DMX daisy-chain or dual-mode with KLSTR.one
- You want Ethernet connectivity + compact internal integration
- KLSTR.one handles the network side (5× Gigabit Ethernet, automatic discovery, redundancy, synchronization, decentral merging)
- KLSTR.nano acts as a communication bridge between KLSTR.one and the host CPU
- This setup requires minimal software effort on the host fixture side because plain RDM+DMX is used as a communication protocol
- See Dual-Mode Operation for wiring and configuration
class r extends HTMLElementthis.tabs.forEach((i,c)=>),i.addEventListener("keydown",e=>)})}switchTab(t,i,c=!0)),this.panels.forEach(s=>);const n=this.panelsi;n&&(n.hidden=!1),t.removeAttribute("tabindex"),t.setAttribute("aria-selected","true"),c&&(t.focus(),r.#r(this,t),window.scrollTo())}#i(t)static#r(t,i)t.#i(e)}}static#s(t)}customElements.define("starlight-tabs",r);
Integration approaches
KLSTR.nano — Standalone
The KLSTR.nano is integrated directly onto your fixture’s PCB. It receives DMX from the external daisy-chain via DMX_IN, forwards it to your host CPU via DMX_LAN, and passes DMX downstream via DMX_OUT. When unpowered, a relay bypass maintains daisy-chain continuity.
You provide: Host PCB with EIA-485 transceiver, power supply (6.3–32 V or 5 V), DMX connectors.
KLSTR.nano provides: DMX reception/forwarding, network stack, encryption, fleet management connectivity.
KLSTR.nano + KLSTR.one — Dual Mode
KLSTR.nano acts as a communication bridge between KLSTR.one and the CPU of the host fixture. This setup requires minimal software effort on the host fixture side because plain RDM+DMX is used as a communication protocol.
The KLSTR.one can also be connected via USB 2.0 or Ethernet for advanced integrations — see the KLSTR.one Hardware Integration documentation for details.
You provide: Host PCB with EIA-485 transceiver, KLSTR.nano socket/solder pads, KLSTR.one solder pads (castellated vias), host power supply (3.3 V for KLSTR.one, 6.3–32 V or 5 V for KLSTR.nano).
Note
Not sure which approach to take? Contact your KLSTR. account manager for a recommendation based on your fixture design and production volume.
Next steps
Once you’ve selected your module, proceed to the hardware integration guide: