Topology & Power
Three wiring options, cable limits and the power budget for each series.
Every LIDARMAGIC sensor is designed to run from a single cable that carries both power and data. Which components sit on that cable depends on your series.
Option A — native PoE (E / M series)
The sensor takes PoE directly. Nothing else on the cable.
flowchart LR SW["PoE switch<br/>802.3af / at"] -->|"Cat5e/6, ≤100 m"| S["E / M sensor"]
Option B — PoE with a splitter (A / C series)
These sensors take 12 V. A PoE splitter sits inline and converts the PoE feed back to 12 V for the sensor.
flowchart LR SW["PoE switch<br/>802.3af / at"] -->|"Cat5e/6, ≤100 m"| SP["PoE splitter<br/>48 V → 12 V"] SP -->|"12 V + data"| S["A / C sensor"]
Mount the splitter at the sensor end, not at the switch end. A splitter at the far end keeps the long run at PoE voltage, which halves the current on the cable and the voltage drop with it.
Option C — no PoE switch available
Feed the sensor from a local 12 V supply and run data over the same cable to the host. This is what you use on a bench test or when the customer’s switch has no PoE budget left.
flowchart LR PSU["12 V DC supply"] --> S["A / C sensor"] S -->|"data"| H["Host PC"]
Power budget
| Item | Typical draw | Note |
|---|---|---|
| Sensor (steady state) | See datasheet | Always budget from the peak value below |
| Sensor (spin-up peak) | 2–3× steady state | Lasts a few hundred milliseconds |
| PoE splitter | ~1 W loss | Conversion is not free |
Cable rules
| Rule | Why |
|---|---|
| Cat5e or better, ≤ 100 m | Ethernet limit; PoE voltage drop adds up beyond it |
| Terminate the shield at one end only | Two grounds create a loop that shows up as packet loss |
| Keep power pairs away from data pairs | Long parallel runs of 48 V induce noise |
| Do not hot-plug the sensor connector | The inrush path has no soft start |