Roastwarden

Releases ·

Roastwarden 0.15.0

A roaster Artisan knows is now set up the way Artisan has it. rustRoast carries Artisan's own machine catalogue: name your machine (or give your .aset file) and its Modbus connection, BT and ET, burner, air and drum outputs and extra curves are filled in, starting at control off. A Modbus roaster may have several controllers on one RS-485 bus.

Added

  • A roaster from Artisan's machine catalogue (Next 65, Roasters from Artisan's catalogue). Artisan's own machine setups (264 .aset files, trimmed and embedded from a pinned Artisan commit by scripts/artisan-machines.py; AGPL like rustRoast, named in the notices) become rustRoast roasters: the Modbus RTU or TCP connection, BT and ET, the extra curves as channels, the burner, air, drum and damper sliders as outputs with Artisan's factor and offset, the PID's setpoint, at control off, with notes on what was guessed or left out. 145 machines plan a roaster; the rest (Siemens S7, Phidgets, …) say why not. GET /api/artisan/machines, POST /api/artisan/machines/plan (nothing saved), roast roaster machines, roast roaster add ID --artisan BRAND/MODEL | --aset FILE [--dry-run], and Add roaster's "Start from an Artisan machine". Hermes eval task 42.
  • A Modbus register on its own slave (migration 053): a register map entry's unit_id puts it on another controller of the RS-485 bus than the connection's, read and written at its own address; roast roaster map --register KIND:ADDRESS@SLAVE:TYPE:ROLE, a Slave column in the register map editor.