Open CamDavidsonPilon opened 1 year ago
[PWM]
2=relay2
3=relay3
(we need to have unique names here)
Ideally it's something like:
Actually even better would be to give them alias.
The problem is this data lives in the plugins yaml file, and that data is fixed: server -> client -> /pioreactors card. Nothing edits it. So even if a user only has two relays, the UI will show 4 relays "available", but only two are ever on.
Similar problem in the Manage modal.
We could dynamically populate the settings, by showing them only when the job starts and intersecting with the $properties
message in MQTT. This way the job, at runtime, can define its settings: overpromise in the yaml, and deliver from the runtime. This has some latency problems though.
Screw it, users can make a custom set up instead of my trying to fin-angle the 4 possible cases:
And how does one control the multiple relays from the UI?