Industrial computing & control / Reference hardware
ARK-1123H typical input of 5.64 W provides the published hardware reference.
Reference hardware
Evidence: Manufacturer specifications and worked calculation examples.
The saved controller summary reports 45 matching sequences. This is an attributed summary; recovery of the original run evidence is pending.
CUMULATIVE APPLICATION BUDGET / 17 OCTOBER 2026
In the main modeled cases, the magnetic-bearing control task uses 0.01029% less energy and brushless-motor control uses 0.00354% less. The other listed industrial comparisons use the same energy as their conventional controls.
Related model results: D019: 43.01% longer completion; 0.2022% more energy at its worst tested condition; D015: 37.37% longer completion; 0.0679% more energy at its worst tested condition. No winner saved energy across the required robustness cases.
Related model jobs: D015, D019, D061, D062, D063, D064, D065. Integration into a product remains open.
Complete bundles, comparisons and lossesRECORDER STORAGE · RECOVERY · COMPUTING / 8 OCTOBER 2026
The proposed layout keeps all 2,592,000 records from 30 days of one reading per second, with two durable copies and timing evidence for every record. It reserves less storage and reduces reads and writes during normal recording.
The design calculations leave more storage available around the same history and reduce the data read during routine restart. Restart time and installed energy remain unmeasured.
| Metric | Earlier design | Revised design | Practical change |
|---|---|---|---|
| Reserved recorder storage | 1,153,112,064 B | 862,808,256 B | 25.18% less reserved recorder storage |
| Recorder + complete input-history storage | 1,453,784,064 B | 1,163,480,256 B | 19.97% less for recorder and input-history storage |
| Normal capture writes | 580,608,000 B | 518,400,000 B | 10.71% fewer written bytes |
| Normal capture reads | 1,410,048,000 B | 1,161,216,000 B | 17.65% fewer read bytes |
| Data read on routine restart | 656,580,608 B | 8,391,072 B | 98.72% fewer read bytes; restart time unmeasured |
| Checksum work for timing records | 1,658,880,000 bit-level checksum steps | 663,552,000 bit-level checksum steps | 60% fewer bit-level checksum steps for timing records |
| Requests to save writes durably | 15,552,000 | 15,552,000 | Unchanged; six calls per record |
| Complete exported recording | 228,096,016 B | 228,096,016 B | Complete history and final state retained |
Storing shared identification once reduces each record’s timing data from 48 to 24 bytes. The layout also reserves less extra storage on the recorder. The complete 30-day history remains available for export and review.
Conventional software can implement these same layout changes.
Routine restart finds where recording stopped without rereading the entire history. It assumes previously checked data stays unchanged and postpones the full corruption scan.
The complete diagnostic scan remains available. It reads 594,374,304 bytes before saving the restart and final-state records. The number of requests to save writes durably stays unchanged.
WHAT THE NUMBERS MEAN
The computer’s typical reference input is 5.64 W. A net reduction of 100 mW would be 1.77% of that input and 0.876 kWh over 8,760 hours. These figures scale the reference input.
Less electricity and cooling for factory or corporate computing, with the same control deadlines and useful output.
THE APPLICATION
Industrial-computer manufacturers, automation integrators and control teams
The aim is less electricity and cooling for factory controls, inspection systems and corporate computing, by reducing repeated work at the same useful output.
Controller-code verification · Energy and heat accounting · Offline engineering workbench
The study looks for avoidable work within a defined job, with control timing and correct output checked together.
REFERENCES & CHECKED RESULTS
| Measure | Reference or conventional method | FI result or stated assumption | What it means |
|---|---|---|---|
| Published computer input | Advantech ARK-1123H A4: 5.64 W typical, 14.04 W maximum | FI operating input remains unmeasured | Published hardware reference |
| Generated control code | Original reference logic | The corrected controller matched 45 specified input sequences | Behavior matched on those 45 sequences |
Executed software comparisons and calculated bounds · 12 October 2026
FI compared ways to store calculation records while keeping the same required output, checks and record behavior. The smaller formats saved memory, but timing depended on the comparison. A separate signal-recording calculation exceeded its frame budget.
A packed, ordered snapshot used less traced Python memory in all 16 matched groups. The detailed record was faster in six groups; two comparisons were uncertain. Against a second read-only format, eight timing comparisons were uncertain.
The snapshot preserves the complete ordered record for reading. It gives up persistent edits, object identity, live changes, custom traces and the full list interface.
One specified validation job needs at least 16,896 recording units per frame to retain the unchanged record. Its budget is 8,192 units.
These are recording-work units from a fixed, uncalibrated model, rather than processor clock cycles.
SOURCES / REVIEWED 6 OCTOBER 2026
19 April 2023: the computer’s typical and maximum input power.
The controller-code comparison and current development status.
Saved sensing-energy ranges, independently checked thermal calculations and recorded software comparisons. The device calculations show energy shares, heat paths and component budgets.
