You received a stability report. Here is how to read it without a engineering background.
Section 1: Unit Identification
Model, serial number, firmware version, and test date. Verify these match the hardware you sent. Firmware version matters — two units with different firmware may not be directly comparable.
Section 2: Test Conditions
Ambient temperature, power supply model, pool endpoint, and test duration. If any condition differs from your operating environment, interpret results with that gap in mind.
Section 3: Hash Rate Timeline
The primary chart. The x-axis is hours; the y-axis is hash rate as a percentage of the run’s peak.
- Flat line (±2%) — Stable unit. Suitable for continuous operation.
- Gradual downward slope — Thermal or power issue developing over time.
- Sudden drops — Often firmware throttling, pool disconnect, or hardware fault.
- Oscillating pattern — Check fan curve settings and ambient temperature stability.
Section 4: Temperature Overlay
We plot chip temperature against hash rate. Correlated drops — temperature rising, hash falling — indicate cooling problems. Uncorrelated drops suggest power or firmware causes.
Section 5: Pass/Fail Recommendation
Our recommendation is based on the variance threshold you agreed at intake. A “pass” at ±3% may be a “fail” at ±2%. The threshold is stated explicitly in this section.
Section 6: Raw Data Export
The CSV contains per-minute readings: hash rate, temperature, fan RPM, and power draw. Import into Excel, Grafana, or your monitoring tool for deeper analysis.
Questions?
Every report includes a contact for a 15-minute phone walkthrough at no extra charge. Use it — the charts make more sense when someone explains what happened at hour 47.