Releases ·
Roastwarden 0.20.0
Phidgets, the thermocouple boards most gas roasters log with in Artisan, now work in rustRoast: through Phidgets' own network server, with no Phidgets software in rustRoast itself. Artisan's 13 Phidgets machines (Diedrich, Mill City and others) set up the way Artisan has them, so 189 of its 264 machines now come across.
Added
- Phidgets temperature boards (Next 67, Phidgets boards): a 1048, a TMP1101 on a VINT
hub, a TMP1100, a 1051 or a TMP1200 RTD, read through Phidgets' network server on the computer
the board is plugged into. rustRoast speaks the network protocol itself (no Phidgets library in
the image): it logs in with the server's password, picks the board (serial number, hub port),
opens the inputs the mapping names (
ch0–ch7; BT ch0 and ET ch1 by default, as Artisan), sets each input's data interval and thermocouple type (or RTD element and wiring), and makes each sample the mean of the readings since the last. Roasters → Add roaster → "Phidgets temperature board", orroast roaster add ID --transport phidget22 --host … [--password …]; the connection test lists the server's boards and reads them; a network server on the LAN is found by mDNS. A Phidget connection only reads. - The 13 Phidgets machines of Artisan's catalogue (Diedrich's 4 and 6 sensor logging, Mill City,
VNT, Titanium, Tostabar, Hive's Data Dome, Phidget's own databridges) are set up the way Artisan
has them: 189 of its 264 machines now (
roast roaster add ID --artisan … --host …). tools/mock-device/mock_phidget22.py, a Phidget22 network server for the local stack, andscripts/dev/phidget22-check.sh: Phidgets' own client against the mock and the real network server (Docker) against rustRoast's.- Hermes eval task 46: a Diedrich's 1048 on a Raspberry Pi's network server, from Artisan's catalogue.
Security
- A password in a connection's config (a Phidget network server's) is shown as
********in every answer, to the dashboard and the CLI alike; sending the mask back keeps the saved one.