I build industrial software, embedded firmware tools, and small deterministic engines for systems that have to keep working when conditions are not ideal.
My work focuses on practical C99, C#, and C++ tooling for:
- embedded firmware
- industrial software and communication
- diagnostics and reliability
- storage and power-loss recovery
- data acquisition
- constrained edge systems
Build tools that are small enough to understand, strict enough to trust, and useful outside of demos.
My usual design bias:
- deterministic behavior
- clear contracts and failure modes
- small integration surfaces
- zero or minimal dependencies
- caller-owned state where possible
- bounded memory and execution where practical
- tests before claims
🌐 Project documentation: vanderhell.github.io
LOX is the technical brand for my embedded and systems projects. The name represents concentrated engineering: compact code, high pressure, predictable behavior, and systems that can be tested instead of guessed.
The LOX family consists of focused libraries rather than one large framework:
loxdb— deterministic embedded database for constrained systems and microcontrollersloxdb_pro_docs— public API documentation for the commercialloxdb_promodulesloxdust— verified persistent object storage with recovery operationsloxbudget— heap-free admission control based on resource budgetsloxboot— zero-heap bootloader core with A/B slots and rollback-oriented flowloxguard— supervised execution boundaries and failure evidenceloxalarm— deterministic alarm-state coreloxseq— power-loss-aware step sequencerloxperm— permissive and interlock evaluatorloxsort— constraint-aware deterministic sortingloxc— trainable codec for domain-specific text payloads
axiom-one— focused deterministic primitives for common embedded problemsGrayGyre— allocation-free Gray-code data-placement primitive for spreading adjacent indices across logical cellsskipspace— heap-free traversal and subtree skipping for large implicit constrained search spacesmicro-toolkit— collection of small, composable embedded C99 librariesmicronet— LAN-first messaging for embedded nodes and desktop diagnosticsuMesh— lightweight ESP32 mesh networking over raw 802.11iotspool— persistent store-and-forward MQTT queue
microsh— debug shell with history and tab completionmicrolog— multi-backend structured loggingmicrofsm— table-driven finite-state machine enginemicrores— retry, backoff, circuit breaker, and rate limitermicroconf— schema-driven configuration with CRC and flash storagemicrocbor— minimal CBOR encoder and decodermicoring— lock-free SPSC ring buffermicrotimer— one-shot and periodic software timersmicrobus— topic-based event and publish/subscribe bus
microhealth— runtime health monitoringmicrowdt— per-task software watchdogmicroboot— boot and crash-loop recovery managermicroassert— unified panic systemmicroota— OTA update flow with commit and rollbackmicroflash— unified flash abstractionpanicdump— persistent Cortex-M3/M4 crash dumpsMCU-Malloc-Tracker— deterministic heap diagnostics for bare-metal MCUsnvlog— power-loss-safe append logmicrotest— single-header C test framework
defer— automatic resource cleanup throughDEFER()cguard— scope guards and result types for Csafemath— checked arithmetic and buffer sizingmicrocrypt— SHA-256, HMAC-SHA256, and AES-128 ECB/CBC/GCMmicrodh— minimal X25519 key exchange
IOBusMonitor— desktop tool for Modbus TCP/RTU and Siemens S7 PLCsRTULogSuite— ESP32 and Windows Modbus RTU logging toolchainPragotron-Controller— minute-impulse controller for a Pragotron stepper clock
num8— O(1) membership engine for eight-digit numbersnum8-lup— low-bandwidth update propagation protocolIronFamily.FileEngine— binary IoT file engines and tooling
MultiGpuHelper— scheduling compute workloads across multiple GPUsCrudFramework— lightweight CRUD framework for .NET applications
securebox-hw— secure hardware password manager concept
I welcome practical feedback from people working with embedded C, microcontrollers, RTOS or bare-metal firmware, industrial devices, and constrained edge systems.
Useful contributions include:
- integration on real hardware
- failure reports with logs and reproducible evidence
- storage and power-loss validation
- portability feedback
- code and API review
- documentation and example improvements