Files
brewpi/config.json.templ
T
jens 2c25b8be50 Sud: server always starts empty; sude/*.json is purely a client concern
Several sude/*.json schedules can exist on disk; only one runs at a
time, chosen by a client Load. Sud no longer takes a path at all - it
starts empty (EMPTY_SUD) and the server config no longer names a
specific schedule file, removing the implicit link to sud_0010.json
in particular. Reading/writing sude/*.json is now entirely the
client's job (e.g. the GUI's Load/Save file dialogs); the server's Sud
only ever holds whatever was last Load()ed, in memory, until replaced
or the server restarts.

Updates demo_sud.py/demo_sud_save_load.py to construct an empty Sud()
and load() a schedule explicitly, matching the new constructor.
2026-06-21 10:24:45 +02:00

43 lines
636 B
Templ

{
"ambient_temperature": 20,
"Controller" : {
"dt": 1,
"sim_warp_factor": 10.0,
"stirrer_name": "sim",
"heater_name": "sim",
"sensor_name": "sim",
"plant_name": "sim",
"pid_type": "Smith"
},
"TempCtrl": {
"Hold": {
"kp": 0.4,
"ki": 0.0,
"kd": 0.0,
"kt": 0.0
},
"Heat": {
"kp": 0.05,
"ki": 0.01,
"kd": 0.0,
"kt": 1.5
},
"Thresholds": {
"HoldIdle": 0.1,
"HoldHeat": 1.0,
"IdleHeat": 1.0,
"IdleHold": 0.1,
"HeatHold": 1.0,
"HeatIdle": 1.0
}
},
"Heater": {
"port": "/dev/ttyUSB0",
"speed": "115200"
},
"Stirrer": {
"port": "/dev/ttyACM0",
"speed": "115200"
}
}