Practical engineering guides to Modbus, serial connectivity and industrial IoT gateway validation.
If the board passes but its result upload fails, preserve the test result locally and keep release eligibility separate from the physical test outcome. Reconcile the same immutable attempt with the result service; do not rerun the hardware merely to obtain a new upload. Where traceable acceptance is required, a missing or mismatched receipt remains…
Near an analog acceptance threshold, keep the measured value, applicable uncertainty and approved decision rule together. A rounded display value inside the product limits is not enough to classify the unit. If the required inputs are missing or the rule leaves an overlap region, report an invalid or indeterminate decision instead of forcing a pass….
A fixture self-test should challenge the exact paths that will support the next DUT result. Use known stimuli or reference loads, require the corresponding observations and record which cables, switching routes and measurement functions were exercised. One successful loopback cannot validate every relay position or the final contact with the product. This is an original…
Align firmware and logic-analyzer records through identifiable common events, then state the uncertainty of that alignment before subtracting timestamps. One marker can establish an offset under a clock-rate assumption. Two separated markers can estimate a rate difference, but they do not prove that the mapping remained valid between them or across a reset. This article…
Accept a serial PASS only when a complete result record belongs to the expected unit, qualified boot instance, current test request and test identity. Clearing a buffer or reopening a port does not create that relationship. Stale output can arrive after either action, and a plain success string carries no evidence about which run produced…
When a hardware-test worker disappears, move its board into recovery quarantine before assigning it again. Establish that the old owner can no longer issue commands, reconcile any operation already in flight and verify the required hardware state. Process death, reservation expiry and safe physical cleanup are separate facts. This design uses upstream labgrid 24.0.2 as…
If a hardware test fails only when another device starts, treat the shared supply and wiring as test resources that can couple otherwise independent jobs. Compare each device alone with controlled concurrent and staggered activity, while observing voltage at the affected load. A supply’s front-panel reading or nominal current rating does not establish that both…
A second-run pass is a new observation, not a replacement for the first failure. Keep both attempts, identify what changed between them and require an explicit disposition of the conflicting evidence. Repeatedly pressing “run” until a green result appears creates an undocumented selection rule rather than a qualified acceptance process. This article defines an original…
After a programmer disconnects, revoke the previous connection’s permission to write. Re-establish the physical unit, selected adapter, approved artifact and programming recipe, then reconcile the interrupted operation before considering a retry. USB reconnection or a familiar filename is not enough evidence to repeat a flash command. The concrete interface reference is upstream OpenOCD 0.12.0. An…
A completed, error-free verification with reconciled section and byte coverage establishes a specific image-to-memory comparison through the selected access path. A success return or banner alone is insufficient, including in the pinned OpenOCD version below. It does not establish that the board selects that image at reset, executes it correctly or meets a product requirement….