<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>LIDARMAGIC DOCUMENTATION</title><link>https://docs.lidarmagic.com/</link><description>Recent content on LIDARMAGIC DOCUMENTATION</description><generator>Hugo</generator><language>en</language><atom:link href="https://docs.lidarmagic.com/index.xml" rel="self" type="application/rss+xml"/><item><title>Data Format</title><link>https://docs.lidarmagic.com/docs/software/sdk/data-format/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.lidarmagic.com/docs/software/sdk/data-format/</guid><description>&lt;h2 id="packet-layout">Packet layout &lt;a href="#packet-layout" class="anchor" aria-hidden="true">&lt;i class="material-icons align-middle">link&lt;/i>&lt;/a>&lt;/h2>&lt;p>Each measurement packet contains a batch of range readings for a contiguous
angular span, plus a sensor timestamp taken at the start of the batch.&lt;/p>
&lt;table>
 &lt;thead>
 &lt;tr>
 &lt;th>Field&lt;/th>
 &lt;th>Type&lt;/th>
 &lt;th>Description&lt;/th>
 &lt;/tr>
 &lt;/thead>
 &lt;tbody>
 &lt;tr>
 &lt;td>Header&lt;/td>
 &lt;td>uint8&lt;/td>
 &lt;td>Fixed sync pattern&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>Timestamp&lt;/td>
 &lt;td>uint32&lt;/td>
 &lt;td>Sensor clock, microseconds&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>Start angle&lt;/td>
 &lt;td>uint16&lt;/td>
 &lt;td>Hundredths of a degree&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>Points&lt;/td>
 &lt;td>array&lt;/td>
 &lt;td>Range and intensity pairs&lt;/td>
 &lt;/tr>
 &lt;/tbody>
&lt;/table>
&lt;h2 id="coordinate-frame">Coordinate frame &lt;a href="#coordinate-frame" class="anchor" aria-hidden="true">&lt;i class="material-icons align-middle">link&lt;/i>&lt;/a>&lt;/h2>&lt;p>Angles increase clockwise when viewed from above, with zero along the connector
face. Confirm the orientation against a known target before trusting it in a
mapping pipeline — mounting rotation is a common source of mirrored output.&lt;/p></description></item><item><title>Power, Network and Cabling</title><link>https://docs.lidarmagic.com/docs/hardware/interfaces/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.lidarmagic.com/docs/hardware/interfaces/</guid><description>&lt;h2 id="power-requirements">Power requirements &lt;a href="#power-requirements" class="anchor" aria-hidden="true">&lt;i class="material-icons align-middle">link&lt;/i>&lt;/a>&lt;/h2>&lt;table>
 &lt;thead>
 &lt;tr>
 &lt;th>Parameter&lt;/th>
 &lt;th>Value&lt;/th>
 &lt;th>Notes&lt;/th>
 &lt;/tr>
 &lt;/thead>
 &lt;tbody>
 &lt;tr>
 &lt;td>Input voltage&lt;/td>
 &lt;td>12 V DC nominal&lt;/td>
 &lt;td>Confirm the range for your specific model&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>Peak current&lt;/td>
 &lt;td>See datasheet&lt;/td>
 &lt;td>Occurs during spin-up, not at steady state&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>Connector&lt;/td>
 &lt;td>Per model&lt;/td>
 &lt;td>M12 industrial or flying leads depending on variant&lt;/td>
 &lt;/tr>
 &lt;/tbody>
&lt;/table>
&lt;p>The sensor contains a spinning optical assembly. Supply impedance matters: a
long, thin cable that works at idle can cause brown-out during spin-up. Size the
conductor for peak current, not average.&lt;/p></description></item><item><title>Topology &amp; Power</title><link>https://docs.lidarmagic.com/docs/hardware/topology/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.lidarmagic.com/docs/hardware/topology/</guid><description>&lt;p>Every LIDARMAGIC sensor is designed to run from a &lt;strong>single cable&lt;/strong> that carries
both power and data. Which components sit on that cable depends on your series.&lt;/p>
&lt;h2 id="option-a--native-poe-e--m-series">Option A — native PoE (E / M series) &lt;a href="#option-a--native-poe-e--m-series" class="anchor" aria-hidden="true">&lt;i class="material-icons align-middle">link&lt;/i>&lt;/a>&lt;/h2>&lt;p>The sensor takes PoE directly. Nothing else on the cable.&lt;/p>
&lt;pre class="mermaid">flowchart LR
 SW[&amp;#34;PoE switch&amp;lt;br/&amp;gt;802.3af / at&amp;#34;] --&amp;gt;|&amp;#34;Cat5e/6, ≤100 m&amp;#34;| S[&amp;#34;E / M sensor&amp;#34;]
&lt;/pre>
&lt;h2 id="option-b--poe-with-a-splitter-a--c-series">Option B — PoE with a splitter (A / C series) &lt;a href="#option-b--poe-with-a-splitter-a--c-series" class="anchor" aria-hidden="true">&lt;i class="material-icons align-middle">link&lt;/i>&lt;/a>&lt;/h2>&lt;p>These sensors take 12 V. A PoE splitter sits inline and converts the PoE feed
back to 12 V for the sensor.&lt;/p></description></item><item><title>Wiring &amp; Power-Up</title><link>https://docs.lidarmagic.com/docs/getting-started/hardware-connection/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.lidarmagic.com/docs/getting-started/hardware-connection/</guid><description>&lt;h2 id="before-you-start">Before you start &lt;a href="#before-you-start" class="anchor" aria-hidden="true">&lt;i class="material-icons align-middle">link&lt;/i>&lt;/a>&lt;/h2>&lt;table>
 &lt;thead>
 &lt;tr>
 &lt;th>Need&lt;/th>
 &lt;th>Note&lt;/th>
 &lt;/tr>
 &lt;/thead>
 &lt;tbody>
 &lt;tr>
 &lt;td>PoE switch or 12 V supply&lt;/td>
 &lt;td>Matched to your series — see &lt;a data-bs-delay="{&amp;#34;hide&amp;#34;:300,&amp;#34;show&amp;#34;:550}" data-bs-html="true" data-bs-title="&lt;a href='https://docs.lidarmagic.com/docs/hardware/topology/'>&lt;p>HARDWARE&lt;/p>&lt;strong>Topology &amp; Power&lt;/strong>&lt;br>Three wiring options, cable limits and the power budget for each series.&lt;/a>" data-bs-toggle="tooltip" href="https://docs.lidarmagic.com/docs/hardware/topology/">Topology&lt;/a>&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>Cat5e or better cable&lt;/td>
 &lt;td>≤ 100 m including the patch panel&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>PoE splitter&lt;/td>
 &lt;td>Only for A / C series&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>Host computer with a free Ethernet port&lt;/td>
 &lt;td>Wi-Fi cannot discover the sensor&lt;/td>
 &lt;/tr>
 &lt;/tbody>
&lt;/table>
&lt;h2 id="wiring-order">Wiring order &lt;a href="#wiring-order" class="anchor" aria-hidden="true">&lt;i class="material-icons align-middle">link&lt;/i>&lt;/a>&lt;/h2>&lt;ol>
&lt;li>&lt;strong>Connect the cable to the sensor first&lt;/strong>, then to the switch.&lt;/li>
&lt;li>Check the link LED on the sensor&amp;rsquo;s RJ45 socket — it should light as soon as
the cable is in, even before power negotiation completes.&lt;/li>
&lt;li>Apply power.&lt;/li>
&lt;/ol>

&lt;div class="alert alert-danger d-flex" role="alert">
 &lt;div class="flex-shrink-1 alert-icon">
 
 &lt;span class="material-icons size-20 me-2">
 error
 &lt;/span>&lt;/div>
 
 
 &lt;div class="w-100">
 
Never hot-plug the sensor's power connector. Standard variants have no soft start
on the inrush path, and repeated hot-plugging degrades the contacts.

 &lt;/div>
 &lt;/div>
&lt;h2 id="status-indicators">Status indicators &lt;a href="#status-indicators" class="anchor" aria-hidden="true">&lt;i class="material-icons align-middle">link&lt;/i>&lt;/a>&lt;/h2>&lt;table>
 &lt;thead>
 &lt;tr>
 &lt;th>LED&lt;/th>
 &lt;th>Meaning&lt;/th>
 &lt;th>Action&lt;/th>
 &lt;/tr>
 &lt;/thead>
 &lt;tbody>
 &lt;tr>
 &lt;td>Off&lt;/td>
 &lt;td>No power, or supply below minimum&lt;/td>
 &lt;td>Check PoE budget, try option C&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>Slow blink&lt;/td>
 &lt;td>Booted, waiting for a network link&lt;/td>
 &lt;td>Check the cable and the switch port&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>Solid&lt;/td>
 &lt;td>Streaming&lt;/td>
 &lt;td>Proceed to find the sensor&lt;/td>
 &lt;/tr>
 &lt;/tbody>
&lt;/table>
&lt;h2 id="power-up-symptoms">Power-up symptoms &lt;a href="#power-up-symptoms" class="anchor" aria-hidden="true">&lt;i class="material-icons align-middle">link&lt;/i>&lt;/a>&lt;/h2>&lt;table>
 &lt;thead>
 &lt;tr>
 &lt;th>Symptom&lt;/th>
 &lt;th>Most likely cause&lt;/th>
 &lt;/tr>
 &lt;/thead>
 &lt;tbody>
 &lt;tr>
 &lt;td>Runs a few seconds then stops&lt;/td>
 &lt;td>Peak current exceeds what the port can deliver&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>Never lights up&lt;/td>
 &lt;td>Wrong option for your series (12 V sensor on a PoE port with no splitter)&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>Link LED on, no data&lt;/td>
 &lt;td>Cable fault on the data pair&lt;/td>
 &lt;/tr>
 &lt;/tbody>
&lt;/table>
&lt;h2 id="next">Next &lt;a href="#next" class="anchor" aria-hidden="true">&lt;i class="material-icons align-middle">link&lt;/i>&lt;/a>&lt;/h2>&lt;p>With the sensor powered and the link up, set the host network:
&lt;a data-bs-delay="{&amp;#34;hide&amp;#34;:300,&amp;#34;show&amp;#34;:550}" data-bs-html="true" data-bs-title="&lt;a href='https://docs.lidarmagic.com/docs/hardware/network/'>&lt;p>HARDWARE&lt;/p></description></item><item><title>供电、网络与线缆</title><link>https://docs.lidarmagic.com/zh/docs/hardware/interfaces/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.lidarmagic.com/zh/docs/hardware/interfaces/</guid><description>&lt;h2 id="供电要求">供电要求&lt;/h2>
&lt;table>
 &lt;thead>
 &lt;tr>
 &lt;th>参数&lt;/th>
 &lt;th>数值&lt;/th>
 &lt;th>说明&lt;/th>
 &lt;/tr>
 &lt;/thead>
 &lt;tbody>
 &lt;tr>
 &lt;td>输入电压&lt;/td>
 &lt;td>12 V DC 标称&lt;/td>
 &lt;td>具体容差以对应型号规格书为准&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>峰值电流&lt;/td>
 &lt;td>见规格书&lt;/td>
 &lt;td>出现在启动瞬间，不是稳态值&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>连接器&lt;/td>
 &lt;td>按型号&lt;/td>
 &lt;td>视版本为 M12 工业连接器或飞线&lt;/td>
 &lt;/tr>
 &lt;/tbody>
&lt;/table>
&lt;p>设备内部有高速旋转的光学组件，&lt;strong>电源内阻很关键&lt;/strong>：一根空载正常的长细线，可能在
启动瞬间造成欠压复位。线径按峰值电流选，不要按平均值选。&lt;/p>
&lt;h2 id="网络">网络&lt;/h2>
&lt;p>设备通过 UDP 输出数据。建议接在独立网段或专用 VLAN 上——办公网里的广播流量会
造成丢包，而现象看起来像是设备故障。&lt;/p>
&lt;h2 id="线缆规范">线缆规范&lt;/h2>
&lt;p>长期安装时：&lt;/p>
&lt;ul>
&lt;li>屏蔽层&lt;strong>单端&lt;/strong>接地，接在主机侧&lt;/li>
&lt;li>电源对绞，并与数据对保持间距&lt;/li>
&lt;li>应力消除夹住外皮，不要夹导体&lt;/li>
&lt;/ul>

&lt;div class="alert alert-danger d-flex" role="alert">
 &lt;div class="flex-shrink-1 alert-icon">
 
 &lt;span class="material-icons size-20 me-2">
 error
 &lt;/span>&lt;/div>
 
 
 &lt;div class="w-100">
 
不要带电插拔电源连接器。标准版本的上电回路没有软启动，反复热插拔会加速连接器老化。

 &lt;/div>
 &lt;/div></description></item><item><title>拓扑与供电</title><link>https://docs.lidarmagic.com/zh/docs/hardware/topology/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.lidarmagic.com/zh/docs/hardware/topology/</guid><description>&lt;p>所有型号都设计成&lt;strong>一根线同时供电和传数据&lt;/strong>。区别只在于这根线上挂不挂分离器。&lt;/p>
&lt;h2 id="方案-a--原生-poee--m-系列">方案 A —— 原生 PoE（E / M 系列）&lt;/h2>
&lt;p>雷达直接吃 PoE，线上不需要任何额外设备。&lt;/p>
&lt;pre tabindex="0">&lt;code class="language-mermaid" data-lang="mermaid">flowchart LR
 SW[&amp;#34;PoE 交换机&amp;lt;br/&amp;gt;802.3af / at&amp;#34;] --&amp;gt;|&amp;#34;Cat5e/6，≤100 m&amp;#34;| S[&amp;#34;E / M 雷达&amp;#34;]
&lt;/code>&lt;/pre>&lt;h2 id="方案-b--poe--分离器a--c-系列">方案 B —— PoE + 分离器（A / C 系列）&lt;/h2>
&lt;p>这两个系列吃 12 V，用一个 PoE 分离器把 PoE 转回 12 V。&lt;/p>
&lt;pre tabindex="0">&lt;code class="language-mermaid" data-lang="mermaid">flowchart LR
 SW[&amp;#34;PoE 交换机&amp;lt;br/&amp;gt;802.3af / at&amp;#34;] --&amp;gt;|&amp;#34;Cat5e/6，≤100 m&amp;#34;| SP[&amp;#34;PoE 分离器&amp;lt;br/&amp;gt;48 V → 12 V&amp;#34;]
 SP --&amp;gt;|&amp;#34;12 V + 数据&amp;#34;| S[&amp;#34;A / C 雷达&amp;#34;]
&lt;/code>&lt;/pre>&lt;p>分离器装&lt;strong>雷达这一端&lt;/strong>，不要装在交换机那端。装在远端可以让长距离线缆跑在 PoE 电压上，电流减半，压降也跟着减半。&lt;/p>
&lt;h2 id="方案-c--没有-poe-交换机时">方案 C —— 没有 PoE 交换机时&lt;/h2>
&lt;p>用本地 12 V 电源供电，数据走同一根线回到主机。台架测试，或客户交换机没有 PoE 预算时使用。&lt;/p></description></item><item><title>接线与上电</title><link>https://docs.lidarmagic.com/zh/docs/getting-started/hardware-connection/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.lidarmagic.com/zh/docs/getting-started/hardware-connection/</guid><description>&lt;h2 id="开始之前">开始之前&lt;/h2>
&lt;table>
 &lt;thead>
 &lt;tr>
 &lt;th>需要&lt;/th>
 &lt;th>说明&lt;/th>
 &lt;/tr>
 &lt;/thead>
 &lt;tbody>
 &lt;tr>
 &lt;td>PoE 交换机或 12 V 电源&lt;/td>
 &lt;td>按你的系列选，见 &lt;a href="https://docs.lidarmagic.com/zh/docs/hardware/topology/">拓扑与供电&lt;/a>&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>Cat5e 或更好规格的网线&lt;/td>
 &lt;td>含跳线在内不超过 100 m&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>PoE 分离器&lt;/td>
 &lt;td>仅 A / C 系列需要&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>带空闲网口的主机&lt;/td>
 &lt;td>无线网络无法发现雷达&lt;/td>
 &lt;/tr>
 &lt;/tbody>
&lt;/table>
&lt;h2 id="接线顺序">接线顺序&lt;/h2>
&lt;ol>
&lt;li>&lt;strong>先把线接到雷达上&lt;/strong>，再接到交换机。&lt;/li>
&lt;li>看雷达网口上的链路指示灯——线一插上就该亮，不必等供电协商完成。&lt;/li>
&lt;li>通电。&lt;/li>
&lt;/ol>

&lt;div class="alert alert-danger d-flex" role="alert">
 &lt;div class="flex-shrink-1 alert-icon">
 
 &lt;span class="material-icons size-20 me-2">
 error
 &lt;/span>&lt;/div>
 
 
 &lt;div class="w-100">
 
不要带电插拔雷达的电源连接器。标准版本的上电回路没有软启动，反复热插拔会加速触点老化。

 &lt;/div>
 &lt;/div>
&lt;h2 id="状态指示">状态指示&lt;/h2>
&lt;table>
 &lt;thead>
 &lt;tr>
 &lt;th>指示灯&lt;/th>
 &lt;th>含义&lt;/th>
 &lt;th>处理&lt;/th>
 &lt;/tr>
 &lt;/thead>
 &lt;tbody>
 &lt;tr>
 &lt;td>熄灭&lt;/td>
 &lt;td>未上电，或电压不足&lt;/td>
 &lt;td>检查 PoE 预算，或改走 12 V 直供&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>慢闪&lt;/td>
 &lt;td>已启动，等待网络链路&lt;/td>
 &lt;td>检查网线与交换机端口&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>常亮&lt;/td>
 &lt;td>正在出数&lt;/td>
 &lt;td>进入&amp;quot;找到雷达&amp;quot;&lt;/td>
 &lt;/tr>
 &lt;/tbody>
&lt;/table>
&lt;h2 id="上电异常">上电异常&lt;/h2>
&lt;table>
 &lt;thead>
 &lt;tr>
 &lt;th>现象&lt;/th>
 &lt;th>最可能的原因&lt;/th>
 &lt;/tr>
 &lt;/thead>
 &lt;tbody>
 &lt;tr>
 &lt;td>出数几秒后停止&lt;/td>
 &lt;td>峰值电流超过端口可提供的功率&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>指示灯完全不亮&lt;/td>
 &lt;td>型号与供电方式不匹配（12 V 设备直接接 PoE 口且无分离器）&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>链路灯亮但无数据&lt;/td>
 &lt;td>网线的数据对存在故障&lt;/td>
 &lt;/tr>
 &lt;/tbody>
&lt;/table>
&lt;h2 id="下一步">下一步&lt;/h2>
&lt;p>设备已上电、链路正常，接下来设置本机网络：&lt;a href="https://docs.lidarmagic.com/zh/docs/hardware/network/">网络设置&lt;/a>。&lt;/p></description></item><item><title>数据格式</title><link>https://docs.lidarmagic.com/zh/docs/software/sdk/data-format/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.lidarmagic.com/zh/docs/software/sdk/data-format/</guid><description>&lt;h2 id="数据包结构">数据包结构&lt;/h2>
&lt;p>每个测量包包含一段连续角度区间内的距离读数，以及一个在数据段开始时刻采集的
传感器时间戳。&lt;/p>
&lt;table>
 &lt;thead>
 &lt;tr>
 &lt;th>字段&lt;/th>
 &lt;th>类型&lt;/th>
 &lt;th>说明&lt;/th>
 &lt;/tr>
 &lt;/thead>
 &lt;tbody>
 &lt;tr>
 &lt;td>帧头&lt;/td>
 &lt;td>uint8&lt;/td>
 &lt;td>固定同步字&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>时间戳&lt;/td>
 &lt;td>uint32&lt;/td>
 &lt;td>传感器时钟，微秒&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>起始角&lt;/td>
 &lt;td>uint16&lt;/td>
 &lt;td>百分之一度&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>点集&lt;/td>
 &lt;td>array&lt;/td>
 &lt;td>距离与强度对&lt;/td>
 &lt;/tr>
 &lt;/tbody>
&lt;/table>
&lt;h2 id="坐标系">坐标系&lt;/h2>
&lt;p>俯视时角度顺时针递增，零点位于连接器所在面。在把数据送入建图流程之前，请先用
已知目标确认朝向——安装旋转是最常见的镜像来源。&lt;/p>
&lt;h2 id="时序">时序&lt;/h2>
&lt;p>时间戳标记的是&lt;strong>扫描开始&lt;/strong>时刻，不是数据包到达时刻。用到达时间会造成随网络缓冲
增长的滞后，在高速运动时表现为形变。&lt;/p></description></item><item><title>Cannot Find the Sensor</title><link>https://docs.lidarmagic.com/docs/troubleshooting/cannot-find-sensor/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.lidarmagic.com/docs/troubleshooting/cannot-find-sensor/</guid><description>&lt;h2 id="first-check">First check &lt;a href="#first-check" class="anchor" aria-hidden="true">&lt;i class="material-icons align-middle">link&lt;/i>&lt;/a>&lt;/h2>


 
 
 

 
 
 
 

 

 &lt;div class="prism-codeblock ">
 &lt;pre id="5c780a6" class="language-bash ">
 &lt;code># 1. What is your adapter&amp;#39;s address?
ifconfig en0 # macOS
ipconfig # Windows

# 2. Can you reach the sensor at its known address?
ping &amp;lt;sensor-ip&amp;gt;&lt;/code>
 &lt;/pre>
 &lt;/div>
&lt;p>If ping fails, the rest of the software configuration does not matter — fix the
network first.&lt;/p>
&lt;h2 id="cause-ranking">Cause ranking &lt;a href="#cause-ranking" class="anchor" aria-hidden="true">&lt;i class="material-icons align-middle">link&lt;/i>&lt;/a>&lt;/h2>&lt;table>
 &lt;thead>
 &lt;tr>
 &lt;th>#&lt;/th>
 &lt;th>Cause&lt;/th>
 &lt;th>Check&lt;/th>
 &lt;/tr>
 &lt;/thead>
 &lt;tbody>
 &lt;tr>
 &lt;td>1&lt;/td>
 &lt;td>Host adapter on a different subnet&lt;/td>
 &lt;td>Compare the first three octets with the sensor&amp;rsquo;s address&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>2&lt;/td>
 &lt;td>Adapter set to DHCP and pulled an address from a router&lt;/td>
 &lt;td>Look for a 192.168.x or 10.x address that is not the sensor&amp;rsquo;s subnet&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>3&lt;/td>
 &lt;td>Wrong sensor default address for the model&lt;/td>
 &lt;td>Confirm on the series page&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>4&lt;/td>
 &lt;td>Sensor not powered&lt;/td>
 &lt;td>Link LED off — see &lt;a data-bs-delay="{&amp;#34;hide&amp;#34;:300,&amp;#34;show&amp;#34;:550}" data-bs-html="true" data-bs-title="&lt;a href='https://docs.lidarmagic.com/docs/hardware/topology/'>&lt;p>HARDWARE&lt;/p></description></item><item><title>Confirm the Point Cloud</title><link>https://docs.lidarmagic.com/docs/getting-started/first-point-cloud/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.lidarmagic.com/docs/getting-started/first-point-cloud/</guid><description>&lt;p>&lt;strong>Verify first, configure later.&lt;/strong> A sensor that streams correctly on its factory
address is known-good hardware. If you change the IP first and the connection
then fails, you cannot tell whether the network or the sensor is at fault.&lt;/p>
&lt;h2 id="what-to-look-at">What to look at &lt;a href="#what-to-look-at" class="anchor" aria-hidden="true">&lt;i class="material-icons align-middle">link&lt;/i>&lt;/a>&lt;/h2>&lt;p>Open the point cloud view in your software and check three things:&lt;/p>
&lt;table>
 &lt;thead>
 &lt;tr>
 &lt;th>Check&lt;/th>
 &lt;th>Healthy&lt;/th>
 &lt;th>Not healthy&lt;/th>
 &lt;/tr>
 &lt;/thead>
 &lt;tbody>
 &lt;tr>
 &lt;td>Shape&lt;/td>
 &lt;td>Walls and objects appear at the right distance and orientation&lt;/td>
 &lt;td>Everything at 0, or a single ring&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>Stability&lt;/td>
 &lt;td>Points stay put; noise is a thin band&lt;/td>
 &lt;td>Cloud flickers or collapses&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>Coverage&lt;/td>
 &lt;td>Full configured angular span&lt;/td>
 &lt;td>Wedge missing at one end&lt;/td>
 &lt;/tr>
 &lt;/tbody>
&lt;/table>
&lt;h2 id="orientation">Orientation &lt;a href="#orientation" class="anchor" aria-hidden="true">&lt;i class="material-icons align-middle">link&lt;/i>&lt;/a>&lt;/h2>&lt;p>Angles increase clockwise seen from above, with zero at the connector face.
Confirm this against a known target — a wall straight ahead should show up where
you expect it. Mounting rotation is the usual source of a mirrored scene, and it
will make every later calibration step wrong.&lt;/p></description></item><item><title>Find the Sensor</title><link>https://docs.lidarmagic.com/docs/software/find-sensor/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.lidarmagic.com/docs/software/find-sensor/</guid><description>&lt;h2 id="before-you-scan">Before you scan &lt;a href="#before-you-scan" class="anchor" aria-hidden="true">&lt;i class="material-icons align-middle">link&lt;/i>&lt;/a>&lt;/h2>&lt;p>The sensor will not appear unless your host adapter is on the same subnet as the
sensor. If the device list is empty, fix that first —
see &lt;a data-bs-delay="{&amp;#34;hide&amp;#34;:300,&amp;#34;show&amp;#34;:550}" data-bs-html="true" data-bs-title="&lt;a href='https://docs.lidarmagic.com/docs/hardware/network/'>&lt;p>HARDWARE&lt;/p>&lt;strong>Network &amp; Host Setup&lt;/strong>&lt;br>Why the host adapter must share the sensor's subnet, and how to change it on Windows and macOS.&lt;/a>" data-bs-toggle="tooltip" href="https://docs.lidarmagic.com/docs/hardware/network/">Network &amp;amp; host setup&lt;/a>.&lt;/p>
&lt;h2 id="scan-for-devices">Scan for devices &lt;a href="#scan-for-devices" class="anchor" aria-hidden="true">&lt;i class="material-icons align-middle">link&lt;/i>&lt;/a>&lt;/h2>&lt;p>Pick your series&amp;rsquo; application. You only need the tab that matches your software.&lt;/p></description></item><item><title>Network &amp; Host Setup</title><link>https://docs.lidarmagic.com/docs/hardware/network/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.lidarmagic.com/docs/hardware/network/</guid><description>&lt;h2 id="the-one-rule">The one rule &lt;a href="#the-one-rule" class="anchor" aria-hidden="true">&lt;i class="material-icons align-middle">link&lt;/i>&lt;/a>&lt;/h2>&lt;blockquote>
&lt;p>Your computer&amp;rsquo;s Ethernet adapter and the sensor must always be on the &lt;strong>same
subnet&lt;/strong>.&lt;/p>&lt;/blockquote>
&lt;p>This is the single most common cause of &amp;ldquo;the sensor is dead&amp;rdquo; reports. The sensor
is fine; the computer simply cannot reach it.&lt;/p>
&lt;p>The rule applies twice:&lt;/p>
&lt;table>
 &lt;thead>
 &lt;tr>
 &lt;th>When&lt;/th>
 &lt;th>What goes wrong if you skip it&lt;/th>
 &lt;/tr>
 &lt;/thead>
 &lt;tbody>
 &lt;tr>
 &lt;td>Before you first discover the sensor&lt;/td>
 &lt;td>The software shows an empty device list&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>After you change the sensor&amp;rsquo;s IP&lt;/td>
 &lt;td>The sensor is now on the new subnet, your adapter is still on the old one, and the device disappears&lt;/td>
 &lt;/tr>
 &lt;/tbody>
&lt;/table>
&lt;h2 id="factory-default">Factory default &lt;a href="#factory-default" class="anchor" aria-hidden="true">&lt;i class="material-icons align-middle">link&lt;/i>&lt;/a>&lt;/h2>&lt;p>Sensors ship with a static address on a fixed subnet. Confirm the exact value for
your model on its series page, then set your adapter to a free address in the
same range.&lt;/p></description></item><item><title>The Short Path</title><link>https://docs.lidarmagic.com/docs/start/quick-path/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.lidarmagic.com/docs/start/quick-path/</guid><description>&lt;p>This is the whole setup on a single page. If anything is unfamiliar, follow the
linked page instead — each one explains the reasoning behind the step.&lt;/p>
&lt;h2 id="1-wire-it-up">1. Wire it up &lt;a href="#1-wire-it-up" class="anchor" aria-hidden="true">&lt;i class="material-icons align-middle">link&lt;/i>&lt;/a>&lt;/h2>&lt;table>
 &lt;thead>
 &lt;tr>
 &lt;th>Your sensor&lt;/th>
 &lt;th>Connection&lt;/th>
 &lt;/tr>
 &lt;/thead>
 &lt;tbody>
 &lt;tr>
 &lt;td>E / M series&lt;/td>
 &lt;td>PoE switch → cable → sensor&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>A / C series&lt;/td>
 &lt;td>PoE switch → cable → PoE splitter → sensor&lt;/td>
 &lt;/tr>
 &lt;/tbody>
&lt;/table>
&lt;p>One cable carries both power and data. Details in
&lt;a data-bs-delay="{&amp;#34;hide&amp;#34;:300,&amp;#34;show&amp;#34;:550}" data-bs-html="true" data-bs-title="&lt;a href='https://docs.lidarmagic.com/docs/hardware/topology/'>&lt;p>HARDWARE&lt;/p></description></item><item><title>找不到雷达</title><link>https://docs.lidarmagic.com/zh/docs/troubleshooting/cannot-find-sensor/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.lidarmagic.com/zh/docs/troubleshooting/cannot-find-sensor/</guid><description>&lt;h2 id="先做两个检查">先做两个检查&lt;/h2>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># 1. 本机网卡当前是什么地址？&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>ifconfig en0 &lt;span style="color:#75715e"># macOS&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>ipconfig &lt;span style="color:#75715e"># Windows&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># 2. 能 ping 到雷达的已知地址吗？&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>ping &amp;lt;雷达IP&amp;gt;
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>ping 不通的话，后面的软件配置都不用看，先把网络修好。&lt;/p>
&lt;h2 id="原因排序">原因排序&lt;/h2>
&lt;table>
 &lt;thead>
 &lt;tr>
 &lt;th>#&lt;/th>
 &lt;th>原因&lt;/th>
 &lt;th>怎么查&lt;/th>
 &lt;/tr>
 &lt;/thead>
 &lt;tbody>
 &lt;tr>
 &lt;td>1&lt;/td>
 &lt;td>本机网卡不在雷达网段&lt;/td>
 &lt;td>对比两者前三段地址&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>2&lt;/td>
 &lt;td>网卡是 DHCP，从路由器拿到了别的网段&lt;/td>
 &lt;td>看地址是否 192.168.x 或 10.x，但不是雷达那段&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>3&lt;/td>
 &lt;td>该型号的出厂地址记错了&lt;/td>
 &lt;td>到系列页确认&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>4&lt;/td>
 &lt;td>雷达没有上电&lt;/td>
 &lt;td>链路灯熄灭，见 &lt;a href="https://docs.lidarmagic.com/zh/docs/hardware/topology/">拓扑与供电&lt;/a>&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>5&lt;/td>
 &lt;td>软件扫错了网卡&lt;/td>
 &lt;td>无线网卡和 VPN 虚拟网卡可能抢占优先级&lt;/td>
 &lt;/tr>
 &lt;/tbody>
&lt;/table>
&lt;h2 id="处理">处理&lt;/h2>
&lt;p>把本机网卡手动设成雷达网段内的空闲地址，掩码一致，网关留空。两个平台的具体步骤见
&lt;a href="https://docs.lidarmagic.com/zh/docs/hardware/network/">网络与本机设置&lt;/a>。&lt;/p>
&lt;p>然后重新扫描，设备应该在几秒内出现。&lt;/p>

&lt;div class="alert alert-warning d-flex" role="alert">
 &lt;div class="flex-shrink-1 alert-icon">
 
 &lt;span class="material-icons size-20 me-2">
 warning
 &lt;/span>&lt;/div>
 
 
 &lt;div class="w-100">
 
VPN 客户端是常见的隐形原因：它会装一个虚拟网卡，软件可能优先扫它而不是以太网。
下结论说雷达坏了之前，先断开 VPN。

 &lt;/div>
 &lt;/div>
&lt;h2 id="还是不出现">还是不出现&lt;/h2>
&lt;table>
 &lt;thead>
 &lt;tr>
 &lt;th>测试&lt;/th>
 &lt;th>说明&lt;/th>
 &lt;/tr>
 &lt;/thead>
 &lt;tbody>
 &lt;tr>
 &lt;td>换一台机器 ping 雷达&lt;/td>
 &lt;td>如果通，雷达没问题，问题在这台主机&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>改走 12 V 直供&lt;/td>
 &lt;td>排除 PoE 协商问题&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>查交换机端口的 PoE 预算&lt;/td>
 &lt;td>预算超支的端口可能根本不给电&lt;/td>
 &lt;/tr>
 &lt;/tbody>
&lt;/table>
&lt;h2 id="下一步">下一步&lt;/h2>
&lt;p>找到了？进入 &lt;a href="https://docs.lidarmagic.com/zh/docs/getting-started/first-point-cloud/">第一帧点云&lt;/a>。&lt;/p></description></item><item><title>最短路径</title><link>https://docs.lidarmagic.com/zh/docs/start/quick-path/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.lidarmagic.com/zh/docs/start/quick-path/</guid><description>&lt;p>整条安装流程浓缩在一页。有不熟悉的地方就点进对应页面，那里会解释为什么。&lt;/p>
&lt;h2 id="1-接线">1. 接线&lt;/h2>
&lt;table>
 &lt;thead>
 &lt;tr>
 &lt;th>你的雷达&lt;/th>
 &lt;th>接法&lt;/th>
 &lt;/tr>
 &lt;/thead>
 &lt;tbody>
 &lt;tr>
 &lt;td>E / M 系列&lt;/td>
 &lt;td>PoE 交换机 → 网线 → 雷达&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>A / C 系列&lt;/td>
 &lt;td>PoE 交换机 → 网线 → 分离器 → 雷达&lt;/td>
 &lt;/tr>
 &lt;/tbody>
&lt;/table>
&lt;p>一根线同时供电和传数据。细节见 &lt;a href="https://docs.lidarmagic.com/zh/docs/hardware/topology/">拓扑与供电&lt;/a>。&lt;/p>
&lt;h2 id="2-本机网段对齐">2. 本机网段对齐&lt;/h2>
&lt;p>在尝试发现雷达之前，先把本机有线网卡设到雷达所在的网段。网段不对，软件里根本不会
出现设备。见 &lt;a href="https://docs.lidarmagic.com/zh/docs/hardware/network/">网络与本机设置&lt;/a>。&lt;/p>
&lt;h2 id="3-找到雷达">3. 找到雷达&lt;/h2>
&lt;p>打开点云软件，扫描网络。&lt;/p>
&lt;table>
 &lt;thead>
 &lt;tr>
 &lt;th>系列&lt;/th>
 &lt;th>软件&lt;/th>
 &lt;/tr>
 &lt;/thead>
 &lt;tbody>
 &lt;tr>
 &lt;td>E 系列&lt;/td>
 &lt;td>MagicViewer&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>A 系列&lt;/td>
 &lt;td>MagicViewer&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>C 系列&lt;/td>
 &lt;td>MagicViewer Classic&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>M 系列&lt;/td>
 &lt;td>Configuration Tool&lt;/td>
 &lt;/tr>
 &lt;/tbody>
&lt;/table>
&lt;p>见 &lt;a href="https://docs.lidarmagic.com/zh/docs/software/find-sensor/">雷达查找&lt;/a>。&lt;/p>
&lt;h2 id="4-确认点云">4. 确认点云&lt;/h2>
&lt;p>点云稳定、朝向正确，说明光路通畅、扫描在跑。先确认硬件，再动配置。&lt;/p>
&lt;h2 id="5-修改-ip">5. 修改 IP&lt;/h2>
&lt;p>把雷达改到客户网段的地址，然后把自己的网卡切到同一网段并用 &lt;code>ping&lt;/code> 验证。见
&lt;a href="https://docs.lidarmagic.com/zh/docs/software/set-ip/">修改 IP&lt;/a>。&lt;/p>
&lt;h2 id="6-标定">6. 标定&lt;/h2>
&lt;p>运行 LiDARMagic Calibration，全系列同一个软件。见 &lt;a href="https://docs.lidarmagic.com/zh/docs/software/calibration/">标定&lt;/a>。&lt;/p>
&lt;h2 id="7-互动测试">7. 互动测试&lt;/h2>
&lt;p>走一遍检测区，检查边缘，确认响应延迟。见 &lt;a href="https://docs.lidarmagic.com/zh/docs/interaction-test/">互动测试&lt;/a>。&lt;/p></description></item><item><title>确认点云</title><link>https://docs.lidarmagic.com/zh/docs/getting-started/first-point-cloud/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.lidarmagic.com/zh/docs/getting-started/first-point-cloud/</guid><description>&lt;p>&lt;strong>先验证，再改配置。&lt;/strong> 在出厂地址上能正常出数的雷达，就是已知良好的硬件。如果先
改 IP 再测，一旦不通就有两种可能，排查成本翻倍。&lt;/p>
&lt;h2 id="看三件事">看三件事&lt;/h2>
&lt;p>打开软件的点云视图，检查：&lt;/p>
&lt;table>
 &lt;thead>
 &lt;tr>
 &lt;th>检查项&lt;/th>
 &lt;th>正常&lt;/th>
 &lt;th>不正常&lt;/th>
 &lt;/tr>
 &lt;/thead>
 &lt;tbody>
 &lt;tr>
 &lt;td>形状&lt;/td>
 &lt;td>墙面和物体出现在正确的距离与朝向&lt;/td>
 &lt;td>全部为 0，或只剩一个圆环&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>稳定性&lt;/td>
 &lt;td>点基本不动，噪声是一条细带&lt;/td>
 &lt;td>点云闪烁或塌陷&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>覆盖&lt;/td>
 &lt;td>完整覆盖配置的角度范围&lt;/td>
 &lt;td>一端缺一块扇形&lt;/td>
 &lt;/tr>
 &lt;/tbody>
&lt;/table>
&lt;h2 id="朝向">朝向&lt;/h2>
&lt;p>俯视时角度顺时针递增，零点在连接器所在面。用已知目标核对——正前方的墙应该出现在
你预期的位置。安装时转了个角度，是最常见的场景镜像来源，而且会让后面所有标定都错。&lt;/p>
&lt;h2 id="这一步常见的异常">这一步常见的异常&lt;/h2>
&lt;table>
 &lt;thead>
 &lt;tr>
 &lt;th>现象&lt;/th>
 &lt;th>原因&lt;/th>
 &lt;/tr>
 &lt;/thead>
 &lt;tbody>
 &lt;tr>
 &lt;td>出数后画面卡住&lt;/td>
 &lt;td>供电撑不住启动电流&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>某一侧点稀疏或噪声大&lt;/td>
 &lt;td>光路上有窗片或遮挡&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>只有一段弧&lt;/td>
 &lt;td>有遮挡，或雷达离墙面太近&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>完全没有&lt;/td>
 &lt;td>雷达已被找到但没在出数，检查软件里的设备状态&lt;/td>
 &lt;/tr>
 &lt;/tbody>
&lt;/table>

&lt;div class="alert alert-info d-flex" role="alert">
 &lt;div class="flex-shrink-1 alert-icon">
 
 &lt;span class="material-icons size-20 me-2">
 info
 &lt;/span>&lt;/div>
 
 
 &lt;div class="w-100">
 
如果雷达在软件里根本不出现，这一页不适用。回到 [雷达查找](/zh/docs/software/find-sensor/)
——几乎总是本机网络设置的问题，不是雷达。

 &lt;/div>
 &lt;/div>
&lt;h2 id="下一步">下一步&lt;/h2>
&lt;p>点云稳定、朝向正确之后，进入 &lt;a href="https://docs.lidarmagic.com/zh/docs/software/set-ip/">修改 IP&lt;/a>。&lt;/p></description></item><item><title>网络与本机设置</title><link>https://docs.lidarmagic.com/zh/docs/hardware/network/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.lidarmagic.com/zh/docs/hardware/network/</guid><description>&lt;h2 id="唯一的原则">唯一的原则&lt;/h2>
&lt;blockquote>
&lt;p>主机的有线网卡与雷达必须&lt;strong>始终在同一网段&lt;/strong>。&lt;/p>&lt;/blockquote>
&lt;p>这是&amp;quot;雷达坏了&amp;quot;这类报修里最常见的原因。雷达没坏，只是主机根本到不了它。&lt;/p>
&lt;p>这条规则会出现两次：&lt;/p>
&lt;table>
 &lt;thead>
 &lt;tr>
 &lt;th>时点&lt;/th>
 &lt;th>漏做会怎样&lt;/th>
 &lt;/tr>
 &lt;/thead>
 &lt;tbody>
 &lt;tr>
 &lt;td>第一次发现雷达之前&lt;/td>
 &lt;td>软件里设备列表是空的&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>改完雷达 IP 之后&lt;/td>
 &lt;td>雷达在新网段，本机还在旧网段，设备&amp;quot;消失&amp;quot;了&lt;/td>
 &lt;/tr>
 &lt;/tbody>
&lt;/table>
&lt;h2 id="出厂默认">出厂默认&lt;/h2>
&lt;p>雷达出厂时是固定网段的静态地址。具体值请看对应系列页，然后把本机网卡设成同网段
的一个空闲地址。&lt;/p>
&lt;h2 id="windows">Windows&lt;/h2>
&lt;ol>
&lt;li>打开 &lt;strong>设置 → 网络和 Internet → 以太网 → 编辑 IP 分配&lt;/strong>&lt;/li>
&lt;li>从 &lt;strong>自动（DHCP）&lt;/strong> 改为 &lt;strong>手动&lt;/strong>&lt;/li>
&lt;li>启用 &lt;strong>IPv4&lt;/strong>，填写：
&lt;ul>
&lt;li>IP 地址：雷达网段内任一空闲地址&lt;/li>
&lt;li>子网掩码：与雷达一致&lt;/li>
&lt;li>网关：留空&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>保存后用 &lt;code>ping&lt;/code> 验证&lt;/li>
&lt;/ol>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-powershell" data-lang="powershell">&lt;span style="display:flex;">&lt;span>ipconfig
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>ping &amp;lt;雷达IP&amp;gt;
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;h2 id="macos">macOS&lt;/h2>
&lt;ol>
&lt;li>打开 &lt;strong>系统设置 → 网络 → 以太网 → 详细信息&lt;/strong>&lt;/li>
&lt;li>把 &lt;strong>配置 IPv4&lt;/strong> 改为 &lt;strong>手动&lt;/strong>&lt;/li>
&lt;li>填入雷达网段内的地址，掩码一致，路由器留空&lt;/li>
&lt;li>应用后验证&lt;/li>
&lt;/ol>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>ifconfig en0
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>ping -c &lt;span style="color:#ae81ff">3&lt;/span> &amp;lt;雷达IP&amp;gt;
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;h2 id="多台雷达的现场">多台雷达的现场&lt;/h2>
&lt;p>每台雷达给一个 DHCP 池之外的固定地址，并把分配记录下来。两台雷达撞地址会产生
间歇性异常——一台应答、另一台不应答，事后极难排查。&lt;/p></description></item><item><title>雷达查找</title><link>https://docs.lidarmagic.com/zh/docs/software/find-sensor/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.lidarmagic.com/zh/docs/software/find-sensor/</guid><description>&lt;h2 id="扫描之前">扫描之前&lt;/h2>
&lt;p>本机网卡必须与雷达同网段，否则设备列表一定是空的。先解决这个：
&lt;a href="https://docs.lidarmagic.com/zh/docs/hardware/network/">网络与本机设置&lt;/a>。&lt;/p>
&lt;h2 id="扫描设备">扫描设备&lt;/h2>
&lt;p>按你的系列选对应标签页，只需要读自己那一份。&lt;/p>

&lt;nav>
	&lt;div class="nav nav-tabs" id="nav-tab" role="tablist">

		
		
		
		

		

		&lt;a class="nav-link active"
		 id="bfedacTab" data-bs-toggle="tab" data-bs-target="#bfedac"
		 type="button" role="tab" aria-controls="bfedac" aria-selected="true">MagicViewer · A / E&lt;/a>

		

		&lt;a class="nav-link "
		 id="cdfeabTab" data-bs-toggle="tab" data-bs-target="#cdfeab"
		 type="button" role="tab" aria-controls="cdfeab" aria-selected="true">MagicViewer Classic · C&lt;/a>

		

		&lt;a class="nav-link "
		 id="baecfdTab" data-bs-toggle="tab" data-bs-target="#baecfd"
		 type="button" role="tab" aria-controls="baecfd" aria-selected="true">Configuration Tool · M&lt;/a>

		

	&lt;/div>
&lt;/nav>

&lt;div class="tab-content" id="nav-tab-content">

	






&lt;div class="tab-pane fade show active" id="bfedac" role="tabpanel" aria-labelledby="nav-1">

	&lt;ol>
&lt;li>打开 MagicViewer。&lt;/li>
&lt;li>进入设备发现面板，开始扫描网络。&lt;/li>
&lt;li>扫描范围是本机网卡所在网段，其他网段的雷达不会出现在列表里。&lt;/li>
&lt;li>选中设备，可以看到当前地址与固件版本。&lt;/li>
&lt;/ol>
&lt;p>列表为空时：先核对本机网段，再看雷达的链路指示灯。&lt;/p>


&lt;/div>






&lt;div class="tab-pane fade" id="cdfeab" role="tabpanel" aria-labelledby="nav-1">

	&lt;ol>
&lt;li>打开 MagicViewer Classic。&lt;/li>
&lt;li>打开设备列表并刷新。&lt;/li>
&lt;li>设备按网段分组，默认扫描本机所在网段。&lt;/li>
&lt;li>选中设备即可查看地址与型号。&lt;/li>
&lt;/ol>
&lt;p>如果什么都没列出来，先确认本机地址，再怀疑硬件。&lt;/p>


&lt;/div>






&lt;div class="tab-pane fade" id="baecfd" role="tabpanel" aria-labelledby="nav-1">

	&lt;ol>
&lt;li>打开 Configuration Tool。&lt;/li>
&lt;li>在设备面板中执行扫描。&lt;/li>
&lt;li>匹配到的设备会显示地址、型号与状态。&lt;/li>
&lt;li>选中一台打开它的配置面板。&lt;/li>
&lt;/ol>
&lt;p>扫描基于网卡的广播域，网段不匹配就什么也扫不到。&lt;/p>


&lt;/div>


&lt;/div>
&lt;h2 id="应该看到什么">应该看到什么&lt;/h2>
&lt;table>
 &lt;thead>
 &lt;tr>
 &lt;th>字段&lt;/th>
 &lt;th>含义&lt;/th>
 &lt;/tr>
 &lt;/thead>
 &lt;tbody>
 &lt;tr>
 &lt;td>地址&lt;/td>
 &lt;td>当前 IP，下一步要改的就是它&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>型号&lt;/td>
 &lt;td>确认你操作的是正确的那台&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>状态&lt;/td>
 &lt;td>出数中 / 空闲。扫描成功但状态为空闲，通常意味着供电有问题&lt;/td>
 &lt;/tr>
 &lt;/tbody>
&lt;/table>
&lt;h2 id="一个网络里有多台雷达">一个网络里有多台雷达&lt;/h2>
&lt;p>先按 MAC 地址或序列号核对清楚再动手。两台同地址的设备会出现间歇性异常，事后
极难拆解——参见 &lt;a href="https://docs.lidarmagic.com/zh/docs/hardware/network/">网络与本机设置&lt;/a>。&lt;/p></description></item><item><title>Host IP Mismatch After Changing the Sensor</title><link>https://docs.lidarmagic.com/docs/troubleshooting/host-ip-mismatch/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.lidarmagic.com/docs/troubleshooting/host-ip-mismatch/</guid><description>&lt;h2 id="what-happened">What happened &lt;a href="#what-happened" class="anchor" aria-hidden="true">&lt;i class="material-icons align-middle">link&lt;/i>&lt;/a>&lt;/h2>&lt;p>You set the sensor to a new address. The sensor rebooted onto the new subnet.
Your adapter is still on the old subnet, so the two can no longer see each other.&lt;/p>



 
 
 

 
 
 
 

 

 &lt;div class="prism-codeblock ">
 &lt;pre id="898d5f1" class="language-text ">
 &lt;code>before: adapter 192.168.0.50 ←→ sensor 192.168.0.10
after: adapter 192.168.0.50 ✗ sensor 10.0.0.10&lt;/code>
 &lt;/pre>
 &lt;/div>
&lt;p>This is not a fault. It is the expected consequence of step ②.&lt;/p>
&lt;h2 id="fix">Fix &lt;a href="#fix" class="anchor" aria-hidden="true">&lt;i class="material-icons align-middle">link&lt;/i>&lt;/a>&lt;/h2>&lt;p>Move the adapter to the &lt;strong>new&lt;/strong> subnet and confirm:&lt;/p></description></item><item><title>Set the IP Address</title><link>https://docs.lidarmagic.com/docs/software/set-ip/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.lidarmagic.com/docs/software/set-ip/</guid><description>&lt;p>Changing a sensor&amp;rsquo;s address is three operations, not one. Skipping the third is
the most common reason a sensor &amp;ldquo;disappears&amp;rdquo; right after being configured.&lt;/p>



 
 
 

 
 
 
 

 

 &lt;div class="prism-codeblock ">
 &lt;pre id="eb37f6c" class="language-text ">
 &lt;code>① host → sensor&amp;#39;s current subnet
② change the sensor&amp;#39;s IP ← the only software-specific part
③ host → sensor&amp;#39;s new subnet, then verify with ping&lt;/code>
 &lt;/pre>
 &lt;/div>
&lt;h2 id="-align-the-host-first">① Align the host first &lt;a href="#-align-the-host-first" class="anchor" aria-hidden="true">&lt;i class="material-icons align-middle">link&lt;/i>&lt;/a>&lt;/h2>&lt;p>If you cannot reach the sensor, you cannot configure it. Set your adapter to a
free address on the sensor&amp;rsquo;s &lt;strong>current&lt;/strong> subnet — usually the factory one. The
procedure is in &lt;a data-bs-delay="{&amp;#34;hide&amp;#34;:300,&amp;#34;show&amp;#34;:550}" data-bs-html="true" data-bs-title="&lt;a href='https://docs.lidarmagic.com/docs/hardware/network/'>&lt;p>HARDWARE&lt;/p></description></item><item><title>修改 IP</title><link>https://docs.lidarmagic.com/zh/docs/software/set-ip/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.lidarmagic.com/zh/docs/software/set-ip/</guid><description>&lt;p>改雷达地址是三个动作，不是一个。漏掉第三个，就是&amp;quot;改完 IP 雷达不见了&amp;quot;的头号原因。&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-text" data-lang="text">&lt;span style="display:flex;">&lt;span>① 本机 → 雷达当前网段
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>② 改雷达 IP ← 唯一与软件相关的部分
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>③ 本机 → 雷达新网段，然后 ping 验证
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;h2 id="-先把本机对齐">① 先把本机对齐&lt;/h2>
&lt;p>到不了雷达，就改不了雷达。把本机网卡设成雷达&lt;strong>当前&lt;/strong>（通常是出厂）网段的空闲地址。
具体做法见 &lt;a href="https://docs.lidarmagic.com/zh/docs/hardware/network/">网络与本机设置&lt;/a>。&lt;/p>
&lt;p>继续之前先确认：&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>ping -c &lt;span style="color:#ae81ff">3&lt;/span> &amp;lt;雷达当前IP&amp;gt;
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;h2 id="-修改雷达地址">② 修改雷达地址&lt;/h2>

&lt;nav>
	&lt;div class="nav nav-tabs" id="nav-tab" role="tablist">

		
		
		
		

		

		&lt;a class="nav-link active"
		 id="cabfdeTab" data-bs-toggle="tab" data-bs-target="#cabfde"
		 type="button" role="tab" aria-controls="cabfde" aria-selected="true">MagicViewer · A / E&lt;/a>

		

		&lt;a class="nav-link "
		 id="acbdefTab" data-bs-toggle="tab" data-bs-target="#acbdef"
		 type="button" role="tab" aria-controls="acbdef" aria-selected="true">MagicViewer Classic · C&lt;/a>

		

		&lt;a class="nav-link "
		 id="abdcefTab" data-bs-toggle="tab" data-bs-target="#abdcef"
		 type="button" role="tab" aria-controls="abdcef" aria-selected="true">Configuration Tool · M&lt;/a>

		

	&lt;/div>
&lt;/nav>

&lt;div class="tab-content" id="nav-tab-content">

	






&lt;div class="tab-pane fade show active" id="cabfde" role="tabpanel" aria-labelledby="nav-1">

	&lt;ol>
&lt;li>在列表中选中设备。&lt;/li>
&lt;li>打开网络设置。&lt;/li>
&lt;li>填入新地址与子网掩码，端口保持不变。&lt;/li>
&lt;li>应用，等待设备重启——重启期间它不会应答。&lt;/li>
&lt;/ol>


&lt;/div>






&lt;div class="tab-pane fade" id="acbdef" role="tabpanel" aria-labelledby="nav-1">

	&lt;ol>
&lt;li>选中设备。&lt;/li>
&lt;li>打开 IP 配置对话框。&lt;/li>
&lt;li>设置新地址与掩码，确认。&lt;/li>
&lt;li>设备重启网络栈，旧地址立即失效。&lt;/li>
&lt;/ol>


&lt;/div>






&lt;div class="tab-pane fade" id="abdcef" role="tabpanel" aria-labelledby="nav-1">

	&lt;ol>
&lt;li>在设备列表中右键，打开配置。&lt;/li>
&lt;li>进入网络选项卡。&lt;/li>
&lt;li>填入新地址与掩码，写入设置。&lt;/li>
&lt;li>等待状态指示恢复到出数。&lt;/li>
&lt;/ol>


&lt;/div>


&lt;/div>

&lt;div class="alert alert-warning d-flex" role="alert">
 &lt;div class="flex-shrink-1 alert-icon">
 
 &lt;span class="material-icons size-20 me-2">
 warning
 &lt;/span>&lt;/div>
 
 
 &lt;div class="w-100">
 
应用之前先把新地址记下来。重启之后雷达就从旧网段消失了，在本机网段切换过去之前，
软件再也找不到它。

 &lt;/div>
 &lt;/div>
&lt;h2 id="-对齐本机并验证">③ 对齐本机并验证&lt;/h2>
&lt;p>把本机网卡切到&lt;strong>新&lt;/strong>网段，然后确认：&lt;/p></description></item><item><title>改完 IP 就连不上了</title><link>https://docs.lidarmagic.com/zh/docs/troubleshooting/host-ip-mismatch/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.lidarmagic.com/zh/docs/troubleshooting/host-ip-mismatch/</guid><description>&lt;h2 id="发生了什么">发生了什么&lt;/h2>
&lt;p>你把雷达改到了新地址，雷达重启后在新网段上。而本机网卡还在旧网段，两边互相看不见。&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-text" data-lang="text">&lt;span style="display:flex;">&lt;span>改之前：本机 192.168.0.50 ←→ 雷达 192.168.0.10
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>改之后：本机 192.168.0.50 ✗ 雷达 10.0.0.10
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>这不是故障，是第 ② 步的必然结果。&lt;/p>
&lt;h2 id="处理">处理&lt;/h2>
&lt;p>把本机网卡切到&lt;strong>新&lt;/strong>网段并确认：&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>ping -c &lt;span style="color:#ae81ff">3&lt;/span> &amp;lt;雷达新IP&amp;gt;
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>如果没记下新地址，看下面的找回办法。&lt;/p>
&lt;h2 id="找回未知地址">找回未知地址&lt;/h2>
&lt;table>
 &lt;thead>
 &lt;tr>
 &lt;th>办法&lt;/th>
 &lt;th>说明&lt;/th>
 &lt;/tr>
 &lt;/thead>
 &lt;tbody>
 &lt;tr>
 &lt;td>用软件的扫描功能扫目标网段&lt;/td>
 &lt;td>大致知道改到哪时就最快&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>查 DHCP 服务器的租约表&lt;/td>
 &lt;td>如果你是通过 DHCP 分配的&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>恢复出厂设置&lt;/td>
 &lt;td>最后手段——会丢掉标定配置&lt;/td>
 &lt;/tr>
 &lt;/tbody>
&lt;/table>

&lt;div class="alert alert-danger d-flex" role="alert">
 &lt;div class="flex-shrink-1 alert-icon">
 
 &lt;span class="material-icons size-20 me-2">
 error
 &lt;/span>&lt;/div>
 
 
 &lt;div class="w-100">
 
应用前记下新地址只要五秒。找回一个没记下的地址可能花一小时，而恢复出厂还会连带
丢掉标定。

 &lt;/div>
 &lt;/div>
&lt;h2 id="怎么避免">怎么避免&lt;/h2>
&lt;p>把&amp;quot;改 IP&amp;quot;当成三个动作而不是一个，这个故障就不会发生。见
&lt;a href="https://docs.lidarmagic.com/zh/docs/software/set-ip/">修改 IP&lt;/a>——第三步就是为它存在的。&lt;/p></description></item><item><title>No Point Cloud</title><link>https://docs.lidarmagic.com/docs/troubleshooting/no-point-cloud/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.lidarmagic.com/docs/troubleshooting/no-point-cloud/</guid><description>&lt;h2 id="separate-the-two-cases">Separate the two cases &lt;a href="#separate-the-two-cases" class="anchor" aria-hidden="true">&lt;i class="material-icons align-middle">link&lt;/i>&lt;/a>&lt;/h2>&lt;table>
 &lt;thead>
 &lt;tr>
 &lt;th>Case&lt;/th>
 &lt;th>Meaning&lt;/th>
 &lt;th>Where to look&lt;/th>
 &lt;/tr>
 &lt;/thead>
 &lt;tbody>
 &lt;tr>
 &lt;td>&lt;strong>Never appeared&lt;/strong>&lt;/td>
 &lt;td>Device listed but no data at all&lt;/td>
 &lt;td>Software configuration, protocol&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>&lt;strong>Appeared then stopped&lt;/strong>&lt;/td>
 &lt;td>It ran, so power and data were fine once&lt;/td>
 &lt;td>Power budget, thermal, cable&lt;/td>
 &lt;/tr>
 &lt;/tbody>
&lt;/table>
&lt;p>The second case is far more common in the field and is almost always power.&lt;/p>
&lt;h2 id="runs-a-few-seconds-then-stops">Runs a few seconds, then stops &lt;a href="#runs-a-few-seconds-then-stops" class="anchor" aria-hidden="true">&lt;i class="material-icons align-middle">link&lt;/i>&lt;/a>&lt;/h2>&lt;p>The spin-up peak draws two to three times the steady-state current. A supply that
is adequate at idle can still brown out during acceleration.&lt;/p></description></item><item><title>无点云</title><link>https://docs.lidarmagic.com/zh/docs/troubleshooting/no-point-cloud/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.lidarmagic.com/zh/docs/troubleshooting/no-point-cloud/</guid><description>&lt;h2 id="先分清两种情况">先分清两种情况&lt;/h2>
&lt;table>
 &lt;thead>
 &lt;tr>
 &lt;th>情况&lt;/th>
 &lt;th>含义&lt;/th>
 &lt;th>查哪里&lt;/th>
 &lt;/tr>
 &lt;/thead>
 &lt;tbody>
 &lt;tr>
 &lt;td>&lt;strong>从来没出现&lt;/strong>&lt;/td>
 &lt;td>设备在列表里，但完全没有数据&lt;/td>
 &lt;td>软件配置、协议&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>&lt;strong>出现后停止&lt;/strong>&lt;/td>
 &lt;td>曾经跑通过，说明供电和链路当时是好的&lt;/td>
 &lt;td>功率预算、散热、线缆&lt;/td>
 &lt;/tr>
 &lt;/tbody>
&lt;/table>
&lt;p>现场更多见的是第二种，而且几乎都是供电问题。&lt;/p>
&lt;h2 id="出几秒就停">出几秒就停&lt;/h2>
&lt;p>启动瞬间的峰值电流是稳态的 2–3 倍。空载时够用的电源，在加速阶段仍可能掉压。&lt;/p>
&lt;table>
 &lt;thead>
 &lt;tr>
 &lt;th>检查&lt;/th>
 &lt;th>通过标准&lt;/th>
 &lt;/tr>
 &lt;/thead>
 &lt;tbody>
 &lt;tr>
 &lt;td>电源额定与规格书峰值对比&lt;/td>
 &lt;td>至少留 30% 余量&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>PoE 端口预算&lt;/td>
 &lt;td>未被其他设备占满&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>全程线径&lt;/td>
 &lt;td>按峰值选，不按平均值&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>分离器额定（A / C）&lt;/td>
 &lt;td>12 V 侧不低于峰值电流&lt;/td>
 &lt;/tr>
 &lt;/tbody>
&lt;/table>
&lt;h2 id="从来没出现">从来没出现&lt;/h2>
&lt;table>
 &lt;thead>
 &lt;tr>
 &lt;th>检查&lt;/th>
 &lt;th>原因&lt;/th>
 &lt;/tr>
 &lt;/thead>
 &lt;tbody>
 &lt;tr>
 &lt;td>软件里的设备状态&lt;/td>
 &lt;td>&amp;ldquo;已找到但空闲&amp;quot;与&amp;quot;在出数但画面空&amp;quot;是两种不同故障&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>主机防火墙拦截 UDP&lt;/td>
 &lt;td>本地防火墙会静默丢包&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>软件选错网卡&lt;/td>
 &lt;td>VPN 与无线网卡&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>软件版本&lt;/td>
 &lt;td>旧版本可能不支持新固件&lt;/td>
 &lt;/tr>
 &lt;/tbody>
&lt;/table>
&lt;h2 id="有点云但几乎是空的">有点云但几乎是空的&lt;/h2>
&lt;p>距离全为零，通常是窗口被遮挡，或雷达贴在了某个面上。先查光路，再查电路。&lt;/p>
&lt;h2 id="下一步">下一步&lt;/h2>
&lt;p>设备在列表里都找不到的话：&lt;a href="https://docs.lidarmagic.com/zh/docs/troubleshooting/cannot-find-sensor/">找不到雷达&lt;/a>。&lt;/p></description></item><item><title>IP Conflict</title><link>https://docs.lidarmagic.com/docs/troubleshooting/ip-conflict/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.lidarmagic.com/docs/troubleshooting/ip-conflict/</guid><description>&lt;h2 id="how-it-presents">How it presents &lt;a href="#how-it-presents" class="anchor" aria-hidden="true">&lt;i class="material-icons align-middle">link&lt;/i>&lt;/a>&lt;/h2>&lt;p>An address conflict never looks like a clean failure. Typical symptoms:&lt;/p>
&lt;ul>
&lt;li>The device answers, then goes silent, then answers again&lt;/li>
&lt;li>Two sensors appear as one in the software, or the model reported is wrong&lt;/li>
&lt;li>Ping succeeds roughly half the time&lt;/li>
&lt;li>Calibration fails intermittently with no code change&lt;/li>
&lt;/ul>
&lt;h2 id="diagnose">Diagnose &lt;a href="#diagnose" class="anchor" aria-hidden="true">&lt;i class="material-icons align-middle">link&lt;/i>&lt;/a>&lt;/h2>


 
 
 

 
 
 
 

 

 &lt;div class="prism-codeblock ">
 &lt;pre id="5b96fc2" class="language-bash ">
 &lt;code># Look at the ARP table: two MACs, one IP
arp -a | grep &amp;lt;sensor-ip&amp;gt;&lt;/code>
 &lt;/pre>
 &lt;/div>
&lt;p>Two different MAC addresses against the same IP confirms the conflict.&lt;/p></description></item><item><title>IP 冲突</title><link>https://docs.lidarmagic.com/zh/docs/troubleshooting/ip-conflict/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.lidarmagic.com/zh/docs/troubleshooting/ip-conflict/</guid><description>&lt;h2 id="典型表现">典型表现&lt;/h2>
&lt;p>地址冲突从来不会干净地失败，常见症状：&lt;/p>
&lt;ul>
&lt;li>设备时有时无，应答一下又沉默&lt;/li>
&lt;li>软件里两台雷达显示成一台，或者型号显示错乱&lt;/li>
&lt;li>ping 大约一半成功&lt;/li>
&lt;li>标定间歇性失败，而代码一行没改&lt;/li>
&lt;/ul>
&lt;h2 id="确认">确认&lt;/h2>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># 看 ARP 表：一个 IP 对应两个 MAC&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>arp -a | grep &amp;lt;雷达IP&amp;gt;
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>同一个 IP 出现两个不同 MAC，就确认了冲突。&lt;/p>
&lt;h2 id="处理">处理&lt;/h2>
&lt;table>
 &lt;thead>
 &lt;tr>
 &lt;th>情况&lt;/th>
 &lt;th>做法&lt;/th>
 &lt;/tr>
 &lt;/thead>
 &lt;tbody>
 &lt;tr>
 &lt;td>两台都是 LIDARMAGIC 雷达&lt;/td>
 &lt;td>一次改一台，改到空闲地址&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>与笔记本撞车&lt;/td>
 &lt;td>把雷达移出 DHCP 池&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>与其他厂商设备撞车&lt;/td>
 &lt;td>给雷达预留独立地址段&lt;/td>
 &lt;/tr>
 &lt;/tbody>
&lt;/table>
&lt;p>&lt;strong>一次只改一台&lt;/strong>：只留一台通电拔掉其余的，剩下的设备就不会有歧义。&lt;/p>
&lt;h2 id="预防">预防&lt;/h2>
&lt;table>
 &lt;thead>
 &lt;tr>
 &lt;th>做法&lt;/th>
 &lt;th>原因&lt;/th>
 &lt;/tr>
 &lt;/thead>
 &lt;tbody>
 &lt;tr>
 &lt;td>固定地址放在 DHCP 池外&lt;/td>
 &lt;td>路由器不会把这些地址分出去&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>每个现场一张地址表&lt;/td>
 &lt;td>冲突在纸上就能发现，不用到现场&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>每台雷达贴标签写地址&lt;/td>
 &lt;td>下一位工程师不用靠猜&lt;/td>
 &lt;/tr>
 &lt;/tbody>
&lt;/table>
&lt;h2 id="下一步">下一步&lt;/h2>
&lt;p>地址规划的一般规则：&lt;a href="https://docs.lidarmagic.com/zh/docs/hardware/network/">网络与本机设置&lt;/a>。&lt;/p></description></item><item><title>Calibration Issues</title><link>https://docs.lidarmagic.com/docs/troubleshooting/calibration-issues/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.lidarmagic.com/docs/troubleshooting/calibration-issues/</guid><description>&lt;h2 id="residual-grows-instead-of-settling">Residual grows instead of settling &lt;a href="#residual-grows-instead-of-settling" class="anchor" aria-hidden="true">&lt;i class="material-icons align-middle">link&lt;/i>&lt;/a>&lt;/h2>&lt;p>The fit is fighting bad input. In order of likelihood:&lt;/p>
&lt;table>
 &lt;thead>
 &lt;tr>
 &lt;th>Cause&lt;/th>
 &lt;th>Check&lt;/th>
 &lt;/tr>
 &lt;/thead>
 &lt;tbody>
 &lt;tr>
 &lt;td>A reference point was placed in the wrong position&lt;/td>
 &lt;td>Re-place the targets exactly where prompted&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>A target moved between capture and fit&lt;/td>
 &lt;td>Nothing should touch the scene during the run&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>Geometry selection wrong for the surface&lt;/td>
 &lt;td>A curve modelled as flat fits the centre and fails the edges&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>Point cloud itself is unstable&lt;/td>
 &lt;td>Go back to &lt;a data-bs-delay="{&amp;#34;hide&amp;#34;:300,&amp;#34;show&amp;#34;:550}" data-bs-html="true" data-bs-title="&lt;a href='https://docs.lidarmagic.com/docs/getting-started/first-point-cloud/'>&lt;p>GETTING STARTED&lt;/p></description></item><item><title>标定异常</title><link>https://docs.lidarmagic.com/zh/docs/troubleshooting/calibration-issues/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.lidarmagic.com/zh/docs/troubleshooting/calibration-issues/</guid><description>&lt;h2 id="残差越迭代越大">残差越迭代越大&lt;/h2>
&lt;p>拟合在和错误输入较劲。按可能性排序：&lt;/p>
&lt;table>
 &lt;thead>
 &lt;tr>
 &lt;th>原因&lt;/th>
 &lt;th>检查&lt;/th>
 &lt;/tr>
 &lt;/thead>
 &lt;tbody>
 &lt;tr>
 &lt;td>参照点放错位置&lt;/td>
 &lt;td>严格按软件提示的位置重放靶标&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>采集与拟合之间靶标被碰动&lt;/td>
 &lt;td>整个过程中场景不能有任何变动&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>几何选错&lt;/td>
 &lt;td>把曲面当平面拟合，中心对、边缘必错&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>点云本身不稳&lt;/td>
 &lt;td>回到 &lt;a href="https://docs.lidarmagic.com/zh/docs/getting-started/first-point-cloud/">第一帧点云&lt;/a>&lt;/td>
 &lt;/tr>
 &lt;/tbody>
&lt;/table>
&lt;h2 id="残差正常但边缘不准">残差正常但边缘不准&lt;/h2>
&lt;p>中心拟合上了，四个角不行。这是几何或覆盖问题，不是数值问题。&lt;/p>
&lt;table>
 &lt;thead>
 &lt;tr>
 &lt;th>检查&lt;/th>
 &lt;th>处理&lt;/th>
 &lt;/tr>
 &lt;/thead>
 &lt;tbody>
 &lt;tr>
 &lt;td>有效区大于雷达覆盖范围&lt;/td>
 &lt;td>增加一台雷达，或缩小有效区&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>雷达以很小掠射角打向表面&lt;/td>
 &lt;td>调整安装位置，让扫描更接近垂直&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>参照点都堆在中间&lt;/td>
 &lt;td>把点布到有效区边缘&lt;/td>
 &lt;/tr>
 &lt;/tbody>
&lt;/table>
&lt;h2 id="断电重启后标定失效">断电重启后标定失效&lt;/h2>
&lt;p>配置没有写进设备。显式保存一次，然后断电重启验证一遍再收工。&lt;/p>
&lt;h2 id="重复性一开始好几天后漂移">重复性一开始好，几天后漂移&lt;/h2>
&lt;p>有东西在动。支架蠕变、投影机被碰、三脚架沉降。重新标定并对比残差——缓慢漂移指向
机械问题，不是软件问题。&lt;/p>
&lt;h2 id="下一步">下一步&lt;/h2>
&lt;p>修好了？重新跑验收测试：&lt;a href="https://docs.lidarmagic.com/zh/docs/interaction-test/">互动测试&lt;/a>。&lt;/p></description></item><item><title>Interaction Lag</title><link>https://docs.lidarmagic.com/docs/troubleshooting/interaction-lag/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.lidarmagic.com/docs/troubleshooting/interaction-lag/</guid><description>&lt;h2 id="measure-before-changing-anything">Measure before changing anything &lt;a href="#measure-before-changing-anything" class="anchor" aria-hidden="true">&lt;i class="material-icons align-middle">link&lt;/i>&lt;/a>&lt;/h2>&lt;p>Touch a known point and record the interval between the physical event and the
visual response. Eyeballing &amp;ldquo;feels slow&amp;rdquo; leads to tuning the wrong stage.&lt;/p>
&lt;table>
 &lt;thead>
 &lt;tr>
 &lt;th>Stage&lt;/th>
 &lt;th>Typical contribution&lt;/th>
 &lt;/tr>
 &lt;/thead>
 &lt;tbody>
 &lt;tr>
 &lt;td>Sensor scan and packet emission&lt;/td>
 &lt;td>Tens of milliseconds at 100 Hz+&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>Network transport&lt;/td>
 &lt;td>1–5 ms on a quiet segment&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>Host application processing&lt;/td>
 &lt;td>Varies wildly — usually the culprit&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>Rendering / display pipeline&lt;/td>
 &lt;td>1–3 frames, i.e. 16–50 ms&lt;/td>
 &lt;/tr>
 &lt;/tbody>
&lt;/table>
&lt;h2 id="where-the-time-actually-goes">Where the time actually goes &lt;a href="#where-the-time-actually-goes" class="anchor" aria-hidden="true">&lt;i class="material-icons align-middle">link&lt;/i>&lt;/a>&lt;/h2>&lt;table>
 &lt;thead>
 &lt;tr>
 &lt;th>Symptom&lt;/th>
 &lt;th>Likely stage&lt;/th>
 &lt;/tr>
 &lt;/thead>
 &lt;tbody>
 &lt;tr>
 &lt;td>Delay grows over hours&lt;/td>
 &lt;td>Host application leaking frames or buffering&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>Delay constant but high&lt;/td>
 &lt;td>Display pipeline, or vsync on a slow refresh&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>Delay only with many targets&lt;/td>
 &lt;td>Host-side tracking complexity, not the sensor&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>Delay only on one machine&lt;/td>
 &lt;td>Network adapter offload, or an antivirus inspecting UDP&lt;/td>
 &lt;/tr>
 &lt;/tbody>
&lt;/table>
&lt;h2 id="cheap-wins">Cheap wins &lt;a href="#cheap-wins" class="anchor" aria-hidden="true">&lt;i class="material-icons align-middle">link&lt;/i>&lt;/a>&lt;/h2>&lt;table>
 &lt;thead>
 &lt;tr>
 &lt;th>Change&lt;/th>
 &lt;th>Effect&lt;/th>
 &lt;/tr>
 &lt;/thead>
 &lt;tbody>
 &lt;tr>
 &lt;td>Disable frame buffering in the renderer&lt;/td>
 &lt;td>Removes 1–3 frames&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>Process packets on arrival, not on a timer&lt;/td>
 &lt;td>Removes up to one polling interval&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>Isolate the sensor VLAN&lt;/td>
 &lt;td>Removes retransmission delays from congestion&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>Lower the sensor frame rate&lt;/td>
 &lt;td>Sometimes &lt;em>reduces&lt;/em> perceived lag if the host was dropping packets&lt;/td>
 &lt;/tr>
 &lt;/tbody>
&lt;/table>
&lt;h2 id="when-it-really-is-the-sensor">When it really is the sensor &lt;a href="#when-it-really-is-the-sensor" class="anchor" aria-hidden="true">&lt;i class="material-icons align-middle">link&lt;/i>&lt;/a>&lt;/h2>&lt;p>Only if the emitted packet rate is below the configured frame rate. Check that on
the wire before blaming the hardware:&lt;/p></description></item><item><title>互动延迟</title><link>https://docs.lidarmagic.com/zh/docs/troubleshooting/interaction-lag/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.lidarmagic.com/zh/docs/troubleshooting/interaction-lag/</guid><description>&lt;h2 id="先测不要凭感觉">先测，不要凭感觉&lt;/h2>
&lt;p>触碰一个已知点，记录物理事件到画面响应之间的时间。凭&amp;quot;感觉慢&amp;quot;去调，多半调错环节。&lt;/p>
&lt;table>
 &lt;thead>
 &lt;tr>
 &lt;th>环节&lt;/th>
 &lt;th>典型耗时&lt;/th>
 &lt;/tr>
 &lt;/thead>
 &lt;tbody>
 &lt;tr>
 &lt;td>雷达扫描与发包&lt;/td>
 &lt;td>100 Hz 以上时几十毫秒&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>网络传输&lt;/td>
 &lt;td>干净网段上 1–5 ms&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>上位机处理&lt;/td>
 &lt;td>差异极大——通常是元凶&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>渲染 / 显示链路&lt;/td>
 &lt;td>1–3 帧，即 16–50 ms&lt;/td>
 &lt;/tr>
 &lt;/tbody>
&lt;/table>
&lt;h2 id="时间花在哪">时间花在哪&lt;/h2>
&lt;table>
 &lt;thead>
 &lt;tr>
 &lt;th>现象&lt;/th>
 &lt;th>可能的环节&lt;/th>
 &lt;/tr>
 &lt;/thead>
 &lt;tbody>
 &lt;tr>
 &lt;td>延迟随时间增长&lt;/td>
 &lt;td>上位机堆帧或缓冲泄漏&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>延迟稳定但偏大&lt;/td>
 &lt;td>显示链路，或垂直同步锁在低刷新率&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>目标多时才延迟&lt;/td>
 &lt;td>上位机追踪复杂度，不是雷达&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>只在某台机器上出现&lt;/td>
 &lt;td>网卡卸载设置，或杀毒软件在检查 UDP&lt;/td>
 &lt;/tr>
 &lt;/tbody>
&lt;/table>
&lt;h2 id="成本最低的几招">成本最低的几招&lt;/h2>
&lt;table>
 &lt;thead>
 &lt;tr>
 &lt;th>改动&lt;/th>
 &lt;th>效果&lt;/th>
 &lt;/tr>
 &lt;/thead>
 &lt;tbody>
 &lt;tr>
 &lt;td>关闭渲染端帧缓冲&lt;/td>
 &lt;td>省掉 1–3 帧&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>收到即处理，不要定时轮询&lt;/td>
 &lt;td>省掉最多一个轮询周期&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>雷达单独划 VLAN&lt;/td>
 &lt;td>去掉拥塞带来的重传延迟&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>降低雷达帧率&lt;/td>
 &lt;td>如果主机在丢包，有时反而&lt;strong>降低&lt;/strong>感知延迟&lt;/td>
 &lt;/tr>
 &lt;/tbody>
&lt;/table>
&lt;h2 id="什么情况才是雷达的问题">什么情况才是雷达的问题&lt;/h2>
&lt;p>只有实际发出的包速率低于配置帧率时。抓包确认了再怀疑硬件：&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>tcpdump -i en0 -n udp port &lt;span style="color:#ae81ff">10940&lt;/span> -c &lt;span style="color:#ae81ff">200&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;h2 id="下一步">下一步&lt;/h2>
&lt;p>延迟的验收标准：&lt;a href="https://docs.lidarmagic.com/zh/docs/interaction-test/">互动测试&lt;/a>。&lt;/p></description></item></channel></rss>