Application’s JSON files

Application’s directory tree

  • An application must have a subdirectory “config” to use ready scripts to process JSON configuration.

  • Subdirectories “signals”, “network” and “pins” contain the actual configuration JSON files.

  • “include” and “intermediate” directories are generated by the script.

  • “include” directory contains C code and headers generated from JSON configuration.

  • “intermediate” contains intermediate merged JSON files and compressed binary JSONs.

Typical directory tree of most example applications (/coderoot/iocom/examples/gina, etc) is something like:

├── code
├── config
│   ├── include
│   │   ├── esphw
│   │   └── megahw
│   ├── intermediate
│   │   ├── esphw
│   │   └── megahw
│   ├── network
│   │   ├── esphw
│   │   └── megahw
│   ├── pins
│   │   ├── esphw
│   │   └── megahw
│   └── signals
├── doc
├── osbuild
│   └── vs
└── scripts

Shared signal configuration JSONs

Shared JSONS are located in:

/coderoot/iocom/config
├── parameters
│   └── wifi_dhcp_device_network_parameters.json (will change ?)
└── signals
    ├── camera_buf8k_signals.json
    └── device_conf_signals.json

Network configuration

Pins configuration

User account configuration

Using shared common signal JSONs

  • Configuration signals

  • Camera signals

200519, updated 21.5.2019/pekka