About
Pavel Banić
Principal engineer and owner. MB Lab Technology is me.
I build the tools I needed and could not buy.
The name is not an abbreviation of anything corporate. MB Lab is My Basement Laboratory, which is both a YouTube channel and an accurate description of where all of this started.
Over twenty years in electronics, mechanical and manufacturing engineering — fourteen of them in research and development, nine in test and nine in manufacturing — mostly in automotive and agricultural equipment. Twelve of those years were spent designing components, fixtures and assemblies and drawing them properly, with GD&T, from first release to design freeze.
The documentation side is not an afterthought either: DVP&R, gap analysis, performance and component specifications, test specifications and plans, coverage analysis, test reports for DV, PV and CV, and the change management around them. That is why every application here writes documents rather than just printing results — it is the part of the job I spent a decade doing by hand.
I am fluent in English, Slovak, Serbian and Croatian, and get by in Czech, Polish and Russian. That has been more useful than it sounds whenever a supplier or a test house turns out to be in central Europe.
Every application on this site started as something I needed on a particular afternoon and could not find at a price a one-person shop could justify. Test coverage analysis, EMC pre-compliance, validation planning, a scope that would read whatever the bench already spoke — each one exists because the commercial answer cost more than the job was worth.
That is the gap I want to close for other people too. Not a cheaper copy of the expensive tools, but a set that assumes you are one engineer or a small team, that writes documents you can hand to a customer, and that does not price you out of your own work.
Where this is going
A low-cost ecosystem for people without a department.
There is a whole category of engineer the industry does not serve: the one working alone, or in a team of three, who still has to answer the same questions about coverage, emissions and qualification that a department does. That is who these are for, and it is why they are priced and built the way they are.
The thread between the applications is the valuable part, and a thread nobody else can join is worth less than one they can — so the interfaces are open and documented. SCPI, Modbus, OPC UA, MQTT, and a manifest each application writes about itself. You can drive any of them from your own code today.
Elsewhere
The other half of what I do.
Engineering is not the only thing I write up. I publish independent research on the Open Science Framework, and I record what happens in the basement on YouTube — which is where the name came from.
The Electrodynamic Universe
A treatise on the unified field theory of redefined mass — inertia and gravitation as field-energy states rather than intrinsic properties of matter. Written with Pavel Vrbovsky and published openly, with the components registered separately.
The Engineering of Neuro-Recovery
A systems-engineering framework for recovery after neurological injury — the Unified Saturation Theory — written from an engineer's side of the problem rather than a clinician's.
On the record
Everything above is under one OSF profile, and one ORCID, so a reader can check who wrote what without taking my word for it.
My Basement Laboratory
The channel the company is named after — bench work, boards, and test rigs driven from Excel.
An invitation
If you build things for engineers, there is room here.
This is one person's work so far, which is its limit rather than its point. If you have an instrument driver, a test method for an industry I do not know, a board worth adding, or a manual that would make one of these tools usable by someone who has never seen it — I would like to hear from you. Tell me what you would want to build, and what you would need from me to make it worth your time.