deploy.

App/wwwroot/HiAPI-docsite/release-note/upgrading-to-3.2/new-diagnostics.html

@@ -126,10 +126,18 @@ they are the fastest way to find out what a run actually did.</p>
 <td>a Siemens (T, D) pair had no <code>$TC_DP</code> row; the generic tool height was used</td>
 </tr>
 <tr>
+<td><code>SiemensToolOffset--TcdpRowMissingGenericHeightNaN</code></td>
+<td>a Siemens (T, D) pair had no <code>$TC_DP</code> row and the generic tool height was NaN too; the D activation resolved to offset 0</td>
+</tr>
+<tr>
 <td><code>Comp-ToolHeight--001</code></td>
 <td>a G43.4 H word could not be resolved</td>
 </tr>
 <tr>
+<td><code>RadiusComp--Interference</code></td>
+<td>a G41/G42 block whose compensated path runs against the programmed direction (an inner arc or groove smaller than the offset radius); a real control stops there with an interference alarm (Fanuc PS0041) while the simulation continues on the swapped-side path — on a tool-centre CAM path the radius offset row (D row) must hold the wear only, not the tool radius</td>
+</tr>
+<tr>
 <td><code>Coord-WorkOffset--AdditionalZero</code></td>
 <td>a Fanuc-family additional work coordinate system (<code>G54.1 Pn</code>, also written <code>G54 Pn</code>) was selected but no offset has been entered for it; the program runs on the machine origin</td>
 </tr>
@@ -174,6 +182,10 @@ they are the fastest way to find out what a run actually did.</p>
 <td>a CL motion resolved no tool offset</td>
 </tr>
 <tr>
+<td><code>CsvStepDurationClamped</code></td>
+<td>a replayed CSV row's recorded step gap exceeded the single-step duration limit and was capped at it; such a gap is normally the seam where two recordings were concatenated</td>
+</tr>
+<tr>
 <td><code>Map-ShotGap--StepsSkipped</code></td>
 <td>steps were skipped because their shot pairing window held no measured row</td>
 </tr>