Your devices do not talk to each other.
You have good hardware, but the test still depends on manual switching, copy-paste data, and separate screens.
AUTOMATED TEST SYSTEMS FOR ADVANCED ENERGY
I make complex test setups work as one system.
I help advanced nuclear and energy teams find what is fragile, connect the hardware, collect reliable data, and turn experiments into usable automated systems.
Remote engineering support + on-site commissioning
Test bench automation.
Data acquisition and logging.
Instrumentation, embedded systems, and GUIs.
Advanced nuclear and energy R&D.
THE PROBLEM
What is broken in your setup?
Most engineering teams already have smart people and good hardware. The problem is the space between the devices: manual steps, messy data, missing GUIs, weak logging, and systems that only one person understands.
Your tests are too manual.
People spend time starting devices, watching values, saving files, and repeating steps that software should handle.
Your data is messy or incomplete.
The team cannot easily reconstruct the test, match readings to events, or compare runs with confidence.
Your setup depends on one expert.
If the one person who knows the scripts is unavailable, the test slows down or stops.
You need a real operator interface.
The test needs live status, controls, alarms, trends, logs, and clear actions, not a folder of scripts.
You need planning before hardware gets expensive.
Before building, we map the control, data, safety, and handover needs so the system can grow cleanly.
LOW-RISK FIRST STEP
Initial Test Setup Bottleneck Review
Find the 3 biggest reasons your test setup is wasting time, losing data, or creating unreliable results.
Send a short description of your setup: what you are testing, which devices are involved, how data is collected, and what feels fragile. I review it and tell you the first practical improvement before any larger project starts.
No meeting is needed first. Send the setup, and I will write back with the first useful diagnosis.
Devices
Data acquisition
GUI
Logs
Decision
What you get
- The 3 biggest bottlenecks in the current test or data flow.
- Where time, data quality, or operator confidence is being lost.
- The first practical fix I would make before a larger build.
- A simple path toward automation, logging, GUI, or control work.
Find what is fragile in your test setup.
Based on real engineering, data acquisition, GUIs, testing, and nuclear/energy context.
I review the setup and point to the first useful fix.
Send a short description. No meeting needed at first.
WHAT I BUILD
The practical pieces that make a test setup usable.
No mystery language. These are the parts teams usually need when hardware has to become a working test system.
Automated Test Benches
Turn a physical test setup into a repeatable system with clear steps, controls, state, and data capture.
Run tests faster with fewer manual mistakes.
Data Acquisition Systems
Collect readings from sensors, instruments, DAQs, and embedded devices into structured, analysis-ready records.
Know what happened, when it happened, and why it matters.
Control Dashboards and GUIs
Build screens that let engineers run tests, monitor live state, change setpoints, and review system behavior.
Operators see the system instead of guessing from raw devices.
Instrumentation Integration
Connect power supplies, sensors, motion systems, controllers, detectors, and lab instruments behind one workflow.
Separate devices start behaving like one test platform.
Feedback and Control Logic
Add automatic responses, setpoint tracking, safety states, and control logic where the experiment needs closed-loop behavior.
The setup can react instead of waiting for a person.
Experimental System Consulting
Plan the system architecture, test flow, electrical/control concept, safety logic, data path, and handover approach.
You get clarity before the build becomes expensive.
WHY BELIEVE ME
Credibility comes from systems, not slogans.
My work sits where hardware, software, data, and operators meet. That is where experimental teams lose time, and where the right system creates leverage.
- Built GUI concepts for neutron diffusion, reactor test control, and sample analysis workflows.
- Experience around reactor physics, neutron measurements, irradiation tests, and high-temperature test environments.
- Comfortable connecting hardware, embedded systems, instrumentation, software, data, and operator workflows.
- Focused on practical systems: clear controls, clean logs, visible state, and documentation your team can use.
PROJECT PROOF + GUI DEMOS
Existing work shown as client value and interface proof.
Each project is shown once: first as the problem it solves, then as the kind of interface that makes the system usable.
High-temperature nuclear materials research
Helios / STARSHIP Reactor Test Control
- ProblemMaterial tests in a reactor environment need stable temperature control, clear telemetry, and operator confidence under unusual constraints.
- BuildBuilt the concept for a command center with zones, target setpoints, power usage, telemetry charts, and system logs.
- ValueA complex thermal experiment becomes visible, controllable, and easier to defend technically.
GUI demo
Helios Reactor Test Command Center
Multi-panel command center for high-temperature reactor material testing with zones, telemetry, power, logs, and target setpoints.
Reactor physics measurement workflow
Neutron Diffusion in Water
- ProblemA neutron measurement setup combines detector signals, motion control, temperature state, noise rejection, and safety limits.
- BuildModeled the control architecture from detector and FPGA-style pulse discrimination through probe positioning and live GUI feedback.
- ValueInvisible physics becomes an operator workflow with measurable state and clean data flow.
GUI demo
Neutron Diffusion Control GUI
Motion-control and telemetry interface for a neutron diffusion experiment, including temperature control, CPS trends, and manual jog.
HOW WE WORK
Clear path from messy setup to usable system.
-
01
Audit
We identify the devices, signals, manual steps, data outputs, operator actions, and current bottlenecks.
-
02
Plan
I define how the instruments, control logic, GUI, data logging, and safety states should work together.
-
03
Build
The software is built around real hardware behavior, practical failure cases, and the way the team runs tests.
-
04
Test
We check the system against real test behavior: data quality, state changes, edge cases, and operator workflow.
-
05
Handover
You get the system, documentation, run logic, and a clear path for future changes.
NEXT STEP
Request an Initial Test Setup Bottleneck Review.
Send what you are testing, which devices are involved, how data is currently collected, and what feels slow, risky, or unclear. I will write back with the first useful diagnosis.
- Best fit: advanced nuclear, energy R&D, laboratories, prototype teams, and technical companies.
- Main outcome: find what is fragile before spending money on the wrong build.
- First step: a short written setup review before a larger project.
What happens after you submit?
- You send a short setup description.
- I review the system flow.
- I reply with the first bottleneck and practical fix.
- If it makes sense, we discuss a build.