Skip to the content
2 layers91.6 × 128.3 mmVANDIMMER-8CH, the printed circuit board in 3D

a central camper van control system for ModBus in c#

Size
91.6 × 128.3 mm
Copper layers
2
Thickness
1.6 mm
Parts
42
Nets
46
Pads
130
Tracks, vias
310, 0
Routed
Yes
KiCad
KiCad 9.0 (file 20241229)
Created
8 Oct 2024
Updated
4 Oct 2026

Overview

VANDIMMER-8CH is an open-source printed circuit board by StuartF303, from the StuartF303/vandaemon repository on GitHub, published under the Apache-2.0 licence. It is a 2-layer board of 91.6 × 128.3 mm with 42 parts on 46 nets, routed with 310 tracks and 0 vias.

It is built around the LM1117T-3.3 and IRLZ44N. Its parts include 18 resistors, 11 connectors, 8 transistors, 3 capacitors and 2 ICs. It belongs with the ESP32 boards of this library.

Main components

2

README

README.md

VanDaemon - Camper Van Control System

A comprehensive IoT control system for camper vans built with .NET 10 and Blazor WebAssembly. Monitor and control your van's systems including water tanks, LPG, lighting, heating, and more - all from your phone, tablet, or computer.

License .NET Docker

Features

  • Real-time Monitoring: Track water tanks, waste water, LPG, fuel, and battery levels in real-time
  • Interactive Controls: Control lights, water pump, heater, and other systems with a touch-friendly interface
  • Configurable Alerts: Get notified when tanks are running low or waste tanks are full
  • Multiple Van Types: Support for different van models with customizable diagrams (default: Mercedes Sprinter LWB)
  • Modular Plugin System: Easy integration with various hardware systems (Modbus, I2C, Victron Cerbo, etc.)
  • Web-Based Interface: Access from any device with a web browser
  • Containerized Deployment: Easy deployment with Docker on Raspberry Pi or other Linux systems
  • Offline-First: Works without internet connectivity

Quick Start

Prerequisites

  • .NET 10.0 SDK (for development)
  • Docker (for containerized deployment)
  • Raspberry Pi 4 (2GB+ RAM recommended) or similar Linux system

Running with Docker (Recommended)

  1. Clone the repository:
bash
git clone https://github.com/yourusername/vandaemon.git
cd vandaemon
  1. Start the services:
bash
docker compose up -d

For detailed Docker usage, configuration, and troubleshooting, see DOCKER.md.

  1. Access the web interface:

Running for Development

  1. Build the solution:
bash
./build.sh          # Linux/Mac
build.bat           # Windows
  1. Run the API:
bash
cd src/Backend/VanDaemon.Api
dotnet run
  1. Run the Web UI (in a separate terminal):
bash
cd src/Frontend/VanDaemon.Web
dotnet run

Project Structure

text
VanDaemon/
├── src/
│   ├── Backend/
│   │   ├── VanDaemon.Api/              # REST API and SignalR hubs
│   │   ├── VanDaemon.Core/             # Domain models and interfaces
│   │   ├── VanDaemon.Application/      # Business logic services
│   │   ├── VanDaemon.Infrastructure/   # Data access and external services
│   │   └── VanDaemon.Plugins/          # Hardware integration plugins
│   │       ├── Abstractions/           # Plugin interfaces
│   │       ├── Simulated/              # Simulated hardware (for testing)
│   │       ├── Modbus/                 # Modbus integration
│   │       ├── I2C/                    # I2C sensor integration
│   │       └── Victron/                # Victron Cerbo integration
│   └── Frontend/
│       └── VanDaemon.Web/              # Blazor WebAssembly application
├── tests/                              # Unit and integration tests
├── docs/                               # Documentation
├── docker/                             # Docker configuration
└── .github/workflows/                  # CI/CD pipelines

Architecture

VanDaemon follows a clean architecture pattern with clear separation of concerns:

  • Frontend: Blazor WebAssembly with MudBlazor UI components
  • Backend API: ASP.NET Core Web API with SignalR for real-time updates
  • Plugin System: Modular hardware integration layer supporting multiple protocols
  • Data Storage: JSON file storage for configuration, in-memory cache for real-time data

See PROJECT_PLAN.md for detailed architecture documentation.

Hardware Integration

VanDaemon supports multiple hardware integration methods through its plugin system:

Supported Plugins

  1. Simulated Plugin (Default) - For testing and development
  2. Modbus Plugin - For Modbus TCP/RTU devices
  3. I2C Plugin - For direct I2C sensor integration
  4. Victron Plugin - For Victron Cerbo GX integration via MQTT

Adding a New Plugin

See docs/deployment/plugin-development.md for instructions on creating custom hardware plugins.

Configuration

System Settings

Configure the system through the web interface Settings page or by editing the configuration files:

  • appsettings.json - API configuration
  • Environment variables - Runtime configuration

Van Diagram Configuration

Customize the van diagram to match your vehicle:

  1. Create an SVG diagram of your van (facing left)
  2. Add the diagram to src/Frontend/VanDaemon.Web/wwwroot/diagrams/
  3. Configure overlay positions in the Settings page

Deployment

VanDaemon supports multiple deployment options:

Cloud Deployment (Fly.io)

Deploy VanDaemon to the cloud for remote access as a single combined container:

bash
# Install Fly.io CLI
curl -L https://fly.io/install.sh | sh

# Login and deploy
flyctl auth login
flyctl apps create vandaemon
flyctl deploy

Access your application at:

Architecture

The Fly.io deployment uses a single container with:

  • Nginx (Port 8080) - Serves Blazor WASM static files and proxies API/WebSocket requests
  • .NET API (Port 5000 internal) - Handles REST API and SignalR connections
  • Supervisor - Manages both nginx and API processes
Key Features
  • Single Endpoint: All services accessible from one URL
  • WebSocket Support: Nginx configured for long-lived SignalR connections
  • Health Checks: Automatic monitoring via /health endpoint
  • Auto-Scaling: Machines stop when idle to save costs
  • GitHub Actions: Automatic deployment on push to main branch

For detailed instructions including GitHub Actions auto-deployment, see DEPLOYMENT.md

Local/Raspberry Pi Deployment

Step 1: Prepare the Raspberry Pi

bash
# Update system
sudo apt update && sudo apt upgrade -y

# Install Docker (includes Docker Compose V2)
curl -fsSL https://get.docker.com -o get-docker.sh
sudo sh get-docker.sh

# Add user to docker group
sudo usermod -aG docker $USER

Step 2: Clone and Deploy

bash
git clone https://github.com/yourusername/vandaemon.git
cd vandaemon
docker compose up -d

Step 3: Configure Hardware Access

For GPIO/I2C access, you may need to:

bash
# Enable I2C
sudo raspi-config
# Select: Interface Options -> I2C -> Enable

# Add user to i2c group
sudo usermod -aG i2c $USER

Step 4: Set Up Auto-Start

bash
# Create systemd service
sudo nano /etc/systemd/system/vandaemon.service

Add the following content:

ini
[Unit]
Description=VanDaemon Control System
Requires=docker.service
After=docker.service

[Service]
Type=oneshot
RemainAfterExit=yes
WorkingDirectory=/home/pi/vandaemon
ExecStart=/usr/bin/docker compose up -d
ExecStop=/usr/bin/docker compose down

[Install]
WantedBy=multi-user.target

Enable and start:

bash
sudo systemctl enable vandaemon
sudo systemctl start vandaemon

API Documentation

The API is documented with OpenAPI/Swagger. Access the interactive documentation at:

Key Endpoints

  • GET /api/tanks - Get all tanks
  • GET /api/tanks/{id}/level - Get current tank level
  • POST /api/tanks/refresh - Refresh all tank levels
  • PUT /api/tanks/{id} - Update tank configuration
  • GET /health - Health check endpoint (returns status and timestamp)

Real-Time Updates

SignalR hub for real-time telemetry updates:

  • Local: ws://localhost:5000/hubs/telemetry
  • Cloud: wss://vandaemon.fly.dev/hubs/telemetry

The hub broadcasts tank levels, control states, and alerts to all connected clients.

Development

Building from Source

bash
# Build solution
dotnet build VanDaemon.sln

# Run tests
dotnet test VanDaemon.sln

# Run specific project
cd src/Backend/VanDaemon.Api
dotnet run

Running Tests

bash
# Run all tests
dotnet test

# Run with coverage
dotnet test --collect:"XPlat Code Coverage"

Roadmap

See PROJECT_PLAN.md for the detailed development roadmap.

Troubleshooting

Common Issues

Issue: Cannot connect to API from web interface

  • Check that API is running on http://localhost:5000
  • Verify CORS settings in appsettings.json
  • Check browser console for errors
  • The frontend automatically uses the current host URL (no configuration needed)

Issue: Docker containers won't start

  • Run docker compose logs to check logs
  • Ensure ports 5000 and 8080 are not in use
  • Verify Docker daemon is running

Issue: Sensors not reading values

  • Check plugin configuration in Settings
  • Verify hardware connections
  • Check API logs for errors

Issue: SignalR WebSocket connections failing

  • Verify health endpoint is accessible: curl https://your-app.fly.dev/health
  • Check nginx logs for WebSocket upgrade errors
  • Ensure nginx is configured with proper WebSocket headers
  • Check for firewall blocking WebSocket connections (port 443 for wss://)

Issue: Fly.io deployment health checks failing

  • Verify the /health endpoint returns 200 OK
  • Check logs: flyctl logs --app vandaemon
  • Ensure nginx and API are both running: flyctl ssh console -C "supervisorctl status"

Issue: Frontend making requests to localhost in production

License

This project is licensed under the MIT License - see the LICENSE file for details.

Acknowledgments

  • MudBlazor - Material Design components for Blazor
  • NModbus - Modbus communication library
  • Victron Energy - For their excellent products and documentation

Built with ❤️ for the camper van community

Parts

42
QtyValueFootprintReferences
1010KResistor_THT:R_Axial_DIN0207_L6.3mm_D2.5mm_P7.62mm_HorizontalR2, R4, R6, R8, R10, R12, R14, R16, R17, R18
8100RResistor_THT:R_Axial_DIN0207_L6.3mm_D2.5mm_P7.62mm_HorizontalR1, R3, R5, R7, R9, R11, R13, R15
8IRLZ44NPackage_TO_SOT_THT:TO-220-3_Horizontal_TabDownQ1, Q2, Q3, Q4, Q5, Q6, Q7, Q8
1100nFCapacitor_THT:C_Disc_D4.3mm_W1.9mm_P5.00mmC2
1100uFCapacitor_THT:CP_Radial_D8.0mm_P3.50mmC4
110uFCapacitor_THT:C_Disc_D4.3mm_W1.9mm_P5.00mmC1
1BTN1Connector_PinHeader_2.54mm:PinHeader_1x02_P2.54mm_VerticalJ10
1BTN2Connector_PinHeader_2.54mm:PinHeader_1x02_P2.54mm_VerticalJ11
1CH1TerminalBlock:TerminalBlock_Xinya_XY308-2.54-2P_1x02_P2.54mm_HorizontalJ2
1CH2TerminalBlock:TerminalBlock_Xinya_XY308-2.54-2P_1x02_P2.54mm_HorizontalJ3
1CH3TerminalBlock:TerminalBlock_Xinya_XY308-2.54-2P_1x02_P2.54mm_HorizontalJ4
1CH4TerminalBlock:TerminalBlock_Xinya_XY308-2.54-2P_1x02_P2.54mm_HorizontalJ5
1CH5TerminalBlock:TerminalBlock_Xinya_XY308-2.54-2P_1x02_P2.54mm_HorizontalJ6
1CH6TerminalBlock:TerminalBlock_Xinya_XY308-2.54-2P_1x02_P2.54mm_HorizontalJ7
1CH7TerminalBlock:TerminalBlock_Xinya_XY308-2.54-2P_1x02_P2.54mm_HorizontalJ8
1CH8TerminalBlock:TerminalBlock_Xinya_XY308-2.54-2P_1x02_P2.54mm_HorizontalJ9
1ESP32-DevkitC-1SF_Library:ESP32-DevKitC-1U2
1LM1117T-3.3Package_TO_SOT_THT:TO-220-3_Horizontal_TabDownU1
1PWR_INTerminalBlock:TerminalBlock_bornier-2_P5.08mmJ1

More from StuartF303/vandaemon

1
  • 2 layers106.7 × 132.1 mmVANDIMMER-8CH-2big, the printed circuit board in 3D

    VANDIMMER-8CH-2big

    StuartF303/vandaemon

    a central camper van control system for ModBus in c#

    42 parts3Apache-2.0

Similar boards

  • 2 layers115 × 88 mmReactor, the printed circuit board in 3D

    Reactor

    Jorgeherrera-hub/Proyecto-Electr-nica-Biom-dica-

    Mini-bioreactor

    42 parts
  • 2 layers68.6 × 53.3 mmDw probe tht, the printed circuit board in 3D

    Dw probe tht

    felias-fogg/dw-link

    An Arduino-UNO-based debugWIRE hardware-debugger

    28 parts90GPL-3.0
  • 2 layersT41-Main+RF board V012, the printed circuit board in 3D

    T41-Main+RF board V012

    DRWJSCHMIDT/T41

    This is the repository for the officially released V10, V11, and V12 versions of the T41 Software Defined Transceiver hardware and kits.

    255 parts66
  • 2 layers99.9 × 99.9 mmIsa debug card, the printed circuit board in 3D

    Isa debug card

    maniekx86/isa_debug_post_card

    8-bit ISA debug and POST card

    85 parts13GPL-3.0
  • 4 layers100 × 100 mmT41, the printed circuit board in 3D

    T41

    ai6ym/t41

    T41-EP SDT Files

    234 parts10
  • 4 layers98.5 × 82 mmPico2lvds, the printed circuit board in 3D

    Pico2lvds

    ceteras/PicoLVDS

    Tested with B089AW01-V.0 and HSD089IFW1-A00-V1.0 on a breadboard. I'm sure it will work with other displays from old netbooks.

    43 parts7GPL-3.0
  • 2 layers54.5 × 77.5 mmEmbedded pcb, the printed circuit board in 3D

    Embedded pcb

    mvx-dev/morphing-airfoil

    UNSW DESN1000 morphing airfoil project

    32 parts6

Questions

How big is the VANDIMMER-8CH PCB?

It measures 91.6 × 128.3 mm and has 2 copper layers, 1.6 mm thick.

What parts does the VANDIMMER-8CH use?

42 parts, built around the LM1117T-3.3 and IRLZ44N. The full list of its parts is on this page, with links to each part's symbol and footprint where PCBKit's library has them.

Where can I download the VANDIMMER-8CH KiCad files?

From the StuartF303/vandaemon repository on GitHub, at the commit this page was made from: the board is hw/LEDDimmer/pcb/VANDIMMER-8CH.kicad_pcb and its schematic hw/LEDDimmer/LEDDimmer.kicad_sch. PCBKit opens the board in the browser, with nothing to install.

Can I use the VANDIMMER-8CH design in my own project?

Its repository publishes it under the Apache-2.0 licence: you may reuse it on that licence's terms (keep the author's notice, and for a copyleft licence share your changes alike).