Guides
Roasters from Artisan's catalogue
Pick a machine from Artisan's catalogue and get its connection, register map and channels set up: Modbus, Fuji PIDs, TC4, WebSocket and MQTT machines.
If Artisan knows your roaster, Roastwarden can set it up the way Artisan has it, with no
manual to read and no register numbers to type in. Artisan ships a setup file (.aset) for
each machine it supports, 264 machines from 94 brands. Each names the device Artisan reads the
machine through and, for Modbus machines, every input (register, controller, scale, °C or
°F), the sliders that drive the burner, air, drum and damper, and the extra curves (inlet,
exhaust, gas pressure). Roastwarden carries that catalogue and turns a machine into a roaster:
its connection, its register map or field mapping, outputs from the sliders and declared
channels from the extra curves. 189 of the 264 machines plan a roaster.
A roaster from the catalogue is added at control off, like any other: check what it reads first, then switch control on (roaster kind and control level).
Using it
Dashboard: Roasters → Add roaster → A known machine? Type a brand or model (show all lists the machines it cannot read too, with why), or open an .aset file saved from Artisan. Picking one fills in the wizard and lists notes: what was read, guessed or left out. When the file cannot know something, it says "Next step: give the …": the serial port on the server, the roaster's address, or an MQTT topic. Then Connection, Check and Control, as for any roaster (add a roaster).
Command line:
roast roaster machines coffed # search the catalogue
roast roaster machines --all # every machine, with why not
roast roaster add sr5 --artisan Coffed/SR5_manual --port /dev/ttyUSB1 --dry-run
roast roaster add sr5 --artisan Coffed/SR5_manual --port /dev/ttyUSB1
roast roaster add r1 --aset my-roaster.aset --host 192.168.1.70--dry-run prints the plan and makes nothing. Without the port, address or topic the file
cannot know, add stops and names it. Then roast roaster check <id>.
What it can read
| Artisan reads it through | Roastwarden sets up |
|---|---|
| Modbus RTU, ASCII or TCP (most machines) | the register map with roles; each register on its own controller when BT and ET sit on different ones on one RS-485 line; BCD values (the Loring Smart Roast) |
| Fuji PIDs: PXG, PXR, PXF (Sedona Elite, Phoenix ORO, Santoker 2xPXF/2xPXR, Wintop, Bideli) | Modbus RTU registers for each controller's temperature and its setpoint (an ET target) |
| Arduino TC4 (Hottop TC4, Kaleido Legacy) | a TC4 connection as stock aArtisan answers, the sliders as command templates |
| Artisan's WebSocket (Probat P Series III, G/UG and Sample Roaster, Prisma PLC) | the WebSocket client with Artisan's request, the field mapping and the sliders' commands |
| MQTT (ROEST 100, 200, P3000) | a field mapping; ROEST's broker is its own cloud, so bridge the roaster's data to your server's broker and give that topic (--telemetry-topic) |
| Phidgets boards (1048, TMP1101, TMP1200, 1051; Diedrich, Mill City and others) | a Phidgets connection: give the computer running Phidgets' network server (Phidgets boards) |
The kind comes from Artisan's heating type (gas or electric). Without one it is a guess, and noted: a gas drum when the machine has sliders, else a logger.
What it cannot read, and what is left out
- Not supported: machines Artisan reads through Siemens S7 (Giesen and others), and those
on Santoker's, Kaleido's, IKAWA's, Aillio's or Hottop's own protocols, HB, ARC and a few
more; Modbus binary or UDP.
roast roaster machines --alllists each with the reason. - Left out, and noted: Artisan's custom buttons (Roastwarden has none), a slider in °C (an inlet setpoint), formulas other than a plain scale, a slider's second command, Artisan's CHARGE and DROP messages to a WebSocket roaster, and a Phidgets 1018's voltages.