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 microcontrollers
• loxdb_pro_docs — public API documentation for the commercial loxdb_pro modules
• loxdust — verified persistent object storage with recovery operations
• loxbudget — heap-free admission control based on resource budgets
• loxboot — zero-heap bootloader core with A/B slots and rollback-oriented flow
• loxguard — supervised execution boundaries and failure evidence
• loxalarm — deterministic alarm-state core
• loxseq — power-loss-aware step sequencer
• loxperm — permissive and interlock evaluator
• loxsort — constraint-aware deterministic sorting
• loxc — trainable codec for domain-specific text payloads

• axiom-one — focused deterministic primitives for common embedded problems
• GrayGyre — allocation-free Gray-code data-placement primitive for spreading adjacent indices across logical cells
• skipspace — heap-free traversal and subtree skipping for large implicit constrained search spaces
• micro-toolkit — collection of small, composable embedded C99 libraries
• micronet — LAN-first messaging for embedded nodes and desktop diagnostics
• uMesh — lightweight ESP32 mesh networking over raw 802.11
• iotspool — persistent store-and-forward MQTT queue

• microsh — debug shell with history and tab completion
• microlog — multi-backend structured logging
• microfsm — table-driven finite-state machine engine
• microres — retry, backoff, circuit breaker, and rate limiter
• microconf — schema-driven configuration with CRC and flash storage
• microcbor — minimal CBOR encoder and decoder
• micoring — lock-free SPSC ring buffer
• microtimer — one-shot and periodic software timers
• microbus — topic-based event and publish/subscribe bus

• microhealth — runtime health monitoring
• microwdt — per-task software watchdog
• microboot — boot and crash-loop recovery manager
• microassert — unified panic system
• microota — OTA update flow with commit and rollback
• microflash — unified flash abstraction
• panicdump — persistent Cortex-M3/M4 crash dumps
• MCU-Malloc-Tracker — deterministic heap diagnostics for bare-metal MCUs
• nvlog — power-loss-safe append log
• microtest — single-header C test framework

• defer — automatic resource cleanup through DEFER()
• cguard — scope guards and result types for C
• safemath — checked arithmetic and buffer sizing
• microcrypt — SHA-256, HMAC-SHA256, and AES-128 ECB/CBC/GCM
• microdh — minimal X25519 key exchange

• IOBusMonitor — desktop tool for Modbus TCP/RTU and Siemens S7 PLCs
• RTULogSuite — ESP32 and Windows Modbus RTU logging toolchain
• Pragotron-Controller — minute-impulse controller for a Pragotron stepper clock

• num8 — O(1) membership engine for eight-digit numbers
• num8-lup — low-bandwidth update propagation protocol
• IronFamily.FileEngine — binary IoT file engines and tooling

• MultiGpuHelper — scheduling compute workloads across multiple GPUs
• CrudFramework — 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