The boot.config file

boot.config controls what the station does at startup — static IP, alias files, Wi-Fi, auto-loaded modules, services and USB ports.

View as Markdown (for AI/KB)

This document describes the boot.config file.

Introduction

Sometimes a default boot-up configuration is necessary — for example to set a static IP address, or to load an alias file automatically. The boot.config file tells the system what to do when booting up.

File structure

{
  "Enabled": true,
  "Author": "system",
  "Created": "2025-11-03T04:23:29.7742193Z",
  "Modified": "2025-11-03T04:23:29.774345Z",
  "Description": "My favorite boot configuration file.",
  "IpConfigurations": [
    { "Enabled": true, "StaticIP": "169.254.36.222/16", "Interface": "eth0" }
  ],
  "AliasFiles": [
    { "Enabled": false, "Order": 0, "Path": "myaliasfile.csv" }
  ],
  "Wifi": { "Enabled": false, "Ssid": "your_ssid", "Password": "your_password" },
  "Modules": [
    { "Name": "MyModule", "Enabled": false, "ClassName": "MyNamespace.MyModuleClass",
      "AssemblyPath": "modules/mymodule.dll", "Namespace": "MyNamespace",
      "ImageName": "", "InitialData": {}, "SerializableVersion": 1 }
  ],
  "services": [
    { "enabled": true, "name": "Swagger", "serviceFile": "accordionq2-webapi" }
  ],
  "disableUsbPorts": true
}

General fields: Enabled (master switch — if false, nothing is configured), Author, Created, Modified, Description.

IpConfigurations

Configure static IP addresses. DHCP is always enabled (turning it off could render the system unreachable); you can always reach the system by host name (the serial number in axxxxxx format) if a DNS controller is on the network.

Field Example Description
Enabled true Whether this IP configuration is applied
StaticIP 169.254.36.222/16 CIDR static IP. The /16 sets netmask 255.255.0.0 and MUST match the host PC’s network. If the CIDR suffix is missing, /24 is inferred.
Interface eth0 The network interface, typically eth0

Multiple IP configurations are allowed, even on the same interface. Before applying, the configured IP is pinged; if there is a response, the configuration is skipped to prevent address conflicts.

AliasFiles

Field Example Description
Enabled true Whether this alias file is applied
Order 0 Order of application, lowest first
Path myaliasfile.csv File name of the alias file to load

The alias file must already be installed on the system (via the file browser or the Upload Alias button).

Wifi

Field Example Description
Enabled true Whether Wi-Fi is enabled
Ssid “your_ssid” The network SSID
Password “your_password” The network password

Wi-Fi also requires the target hardware to be configured to allow it (agreed at purchase).

The password is visible to anyone who attaches to the system via Accordion Pilot. Do not store sensitive passwords in this file. Contact E# support if you need a Wi-Fi configuration where users cannot see the password.

Modules

Auto-load software modules at boot.

Field Example Description
Name MyModule Name of the installed module to load
Enabled true Whether loading this module is enabled
ClassName MyNamespace.MyModuleClass The module’s class name
AssemblyPath modules/mymodule.dll Path to the module DLL
Namespace MyNamespace The module’s namespace
InitialData {} Key/value pairs to configure the module
SerializableVersion 1 Internal version — do not change

Test-load a module manually first; a faulty module configuration will prevent the Accordion process from booting.

Services

"services": [ { "enabled": true, "name": "Swagger", "serviceFile": "accordionq2-webapi" } ]

Enables/disables the WebAPI engine. Do not turn this off unless you use your Accordion from Pilot only.

USB ports

"disableUsbPorts": true

Sets whether the USB ports are disabled.

Configuration order

The configuration runs in this order: Wi-Fi → USB enable/disable → IP configurations → load software modules → enable/disable services → apply alias files (ascending order). Loading software modules and applying alias files happens at each reset, not only during boot.

How to edit boot.config

Open Accordion Pilot, go to the configuration tab, attach the file browser, go to hw/config/boot.config and download the file. Edit it (e.g. set a static IP with CIDR, which is optional — defaults to /24 — but required if the netmask differs), then upload it to the same location, overwriting the existing file, and reboot the AGENT.

If a faulty configuration is entered, the Accordion process will not boot correctly — judge from the heartbeat LED on the back: pulsing blue/green means the process started normally; stale or black means it did not. You can still attach via the configuration tab, delete the file and reboot; an empty (disabled) file is then recreated for you.

Book a demo of Probe

Show us your board — we review it and go through the findings together.

Prefer to email? info@esharp.se