# Single-pair Ethernet bench plan: fields and instructions

Version: 2026-09-23. Companion files: spe-bench-plan.csv and spe-bench-demo-plan.csv.
Open the files as UTF-8, comma-delimited text using Excel’s “From Text/CSV” function or LibreOffice. English column names allow reuse across languages.

The plan already includes the trial purposes for B01 short-link baseline, B02 target cable, B03 power over the same pair, and B04 startup/load variation. This is a suggested sequence, not manufacturer wiring instructions or a completed test. Remove conditions that do not apply to the equipment’s capabilities. For repeated executions of one condition, duplicate the row and assign a unique test_id. Complete the documentation, actual boards, software and criteria before starting work.

| Field | Meaning and entry instructions |
| --- | --- |
| data_kind | unperformed_plan for the plan; illustrative_plan_not_measured for the example; use measured in a separate record after obtaining actual measurements |
| test_id | Unique ID for each execution, used to link logs |
| document_and_revision | Revisions of the actual board manuals, design files and software documents used |
| endpoint_a_hw_fw / endpoint_b_hw_fw | Hardware revisions and firmware/image/driver versions at both endpoints |
| cable_drawing_lot / planned_length_m | Cable drawing, connectors and lot / planned length in meters |
| power_route_and_class | Actual power path, PSE/PD configuration and power class; distinguish external power from power over the same pair |
| changed_factor / held_constant | Factor changed in this row / conditions kept constant |
| acceptance_criteria_ref | Reference to product criteria, component operating limits and stop conditions established before execution |
| planned_observation | Observations and logs planned for this condition |
| started_at_utc / ended_at_utc | Actual execution window, including date, time and UTC time zone |
| actual_tx_mode_vpp | Actual readback of transmit mode (Vpp); do not substitute a planned value |
| actual_tx_count / actual_rx_count | Transmitted/received counts at the same layer and within the same window; leave blank when counts are unavailable |
| counter_definition | Whether the counts represent Ethernet frames, application messages or another unit; how duplicates, filtering and resets are handled |
| link_down_count / reset_count | Link interruptions / endpoint resets actually observed in the window; leave blank if not observed |
| pd_input_min_v / pd_input_max_v | Minimum/maximum PD input voltage at the specified measurement point, in V; place instrument and measurement-point details in evidence_ref |
| power_setup_result / data_result | Separate conclusions for power establishment and application data, including the criteria used; do not enter a pass for an unperformed test |
| evidence_ref | Locations of logs, waveforms, measurement points, sampling settings and result files under the same ID |
| next_decision | Next action: continue, change a named item, stop this approach or perform a further test, with the basis for the decision |

## How to use the completed example plan

The demonstration file assumes compatible endpoints already exist, with a 1 m starting link and a 20 m target cable. These lengths are illustrative only. Separate rows change the cable, power arrangement, and startup or load. Replace REPLACE fields with actual information. Also verify power classes, negotiation and connector support at both ends; an assumption of compatibility is not a completed check.

Every example field from started_at_utc through next_decision is blank. There are no actual times, counts, voltages, resets, logs or test conclusions. After preparation, copy the plan into a separate execution file and retain the original plan. Distinguish the files in both their filenames and data_kind values.

## Summarizing and diagnosing results

First compare B01/B02 with the same window, load, endpoints and software. Note the change in power path when comparing B02/B03. An illuminated indicator alone is insufficient for data_result to be a pass; read the application data and apply the stated criteria. If count definitions differ or a counter resets, transmitted count minus received count cannot directly be treated as packet loss. Retain the logs and explain the difference first.

When faults appear only with power over the same pair, check the timing relationships among power establishment, PD state, resets and data events before choosing the next measurement. Do not infer cable voltage drop from that symptom alone. If the short link also fails, resolve the baseline configuration first. Leave unavailable records blank. Enter 0 only for an event that was actually absent during the observed window.

A bench conclusion is ready to hand over when each planned condition has configuration, criteria and result references, failures have an executable next diagnostic step, and untested scope is listed separately. The table does not automatically determine component compatibility or replace manufacturer wiring procedures, product qualification or EMC verification.


## Original CSV values and their meanings

The original files retain stable English values. The following table explains their meaning; demonstration identifiers do not identify actual parts or tests.

| Original value | Meaning |
| --- | --- |
| `unperformed_plan` | A plan that has not been executed. |
| `illustrative_plan_not_measured` | An illustrative plan with no measured results. |
| `measured` | A separate record of actual measurements after execution. |
| `B01` | Short-link baseline condition. |
| `B02` | Target-cable condition. |
| `B03` | Power-over-the-same-pair condition. |
| `B04` | Startup or load variation condition. |
| `REPLACE: exact board manuals and matched revisions` | Enter the actual board manuals and verify that their revisions match. |
| `REPLACE: compatible endpoint A / firmware` | Enter the actual endpoint A and firmware, and verify compatibility. |
| `REPLACE: compatible endpoint B / firmware` | Enter the actual endpoint B and firmware, and verify compatibility. |
| `REPLACE: actual drawing and lot` | Enter the actual cable drawing and lot. |
| `REPLACE: product-specific criteria agreed before test` | Enter the product-specific criteria established before execution. |
| `original supported supply` | Use the original supply arrangement supported by the manufacturer. |
| `same as B01` | Retain the power arrangement used for B01. |
| `compatible PoDL/SPoE only` | Use PoDL/SPoE only after verifying compatibility. |
| `validated route` | Use the power path already verified for the equipment. |
| `establish baseline` | Establish the initial comparison configuration. |
| `target cable and connector assembly` | Change to the target cable and connector assembly. |
| `power route` | Change the power arrangement. |
| `one declared startup or load condition` | Change one explicitly defined startup or load condition. |
| `endpoint firmware; application load` | Keep endpoint firmware and application load constant. |
| `endpoints; firmware; data load; supply` | Keep endpoints, firmware, data load and supply constant. |
| `B02 cable; endpoints; firmware; data load` | Keep the B02 cable, endpoints, firmware and data load constant. |
| `validated circuit and cable` | Keep the already verified circuit and cable constant. |
| `negotiation; application data; supply state` | Observe negotiation, application data and the supply state. |
| `same-window data counters; reconnect/reset; supply readings` | Observe data counters over the same window, reconnections/resets and supply readings. |
| `power classification/start; PD state; application data` | Observe power classification and startup, the powered-device state and application data. |
| `startup count; recovery duration; logs/waveform` | Record startup count, recovery duration and relevant logs or waveforms. |