Phidget USB Setup
Rostoc has experimental read-only support for Phidget USB temperature channels.
Use this path for catalog machines that list Phidget USB as the connection
type, or for imported Artisan .aset presets that review as Phidget USB with
channel mappings.
Experimental support means the machine is addable, the Phidget runtime path is implemented, and Rostoc can build channel-specific connection settings from the catalog or import review. It does not mean Rostoc controls the roaster, and it does not remove the need to validate probe order on the exact USB hardware.
What you need
Section titled “What you need”- Connect the Phidget interface or temperature module with a data-capable USB cable.
- Install the Phidgets driver for your operating system from the Phidgets website before the first connection. Rostoc ships the Phidget software library, but the operating-system driver has to be installed separately — without it, no Phidget will attach, and the failure looks like a missing device. This is the most common reason a Phidget setup never connects.
- Attach probes to the channels expected by the catalog entry or
.asetpreset. - Close other roasting software that may already be using the same Phidget device.
- Keep the Phidgets Control Panel available if you need to confirm the attached module, serial number, hub port, or channel order.
Add the machine
Section titled “Add the machine”- Open Settings -> Machines.
- Click Add Machine and browse the catalog.
- Choose your machine or Phidget module entry.
- Confirm the support status is Experimental.
- Save the machine. Rostoc uses the USB device directly, so there is no COM port to choose.
Import an .aset preset
Section titled “Import an .aset preset”If you already have an .aset settings file from your existing roasting
software, import it from Settings ->
Machines. When the preset contains Phidget mappings, the review form should
show Phidget USB and channel mappings such as Bean Temp, Env Temp, or
additional Phidget inputs. Review the channels before saving.
Catalog families
Section titled “Catalog families”Current catalog Phidget USB entries include roasters and sensor-module presets for these families:
- Diedrich
- Hive Roaster
- Mill City Roasters / MCR
- Phidget module presets
- Titanium
- Tostabar
- VNT
Check the machine catalog for the exact model and current status before relying on the setup for production logging.
Exact experimental entries
Section titled “Exact experimental entries”| Brand | Catalog entries | Notes |
|---|---|---|
| Diedrich | Diedrich 4-Sensor, Diedrich 6-Sensor, Diedrich 6-Sensor (Pre-2018) | Use the Phidget entries only for USB sensor logging. Diedrich CR and DR entries use a separate Modbus TCP path where listed. |
| Hive Roaster | Data Dome | Validate probe/channel order for the Data Dome setup before saving production records. |
| Mill City Roasters | MCR Phidget, MCR Phidget & Delta controls (port on the back), MCR Phidget & Shihlin controls (port on the back) | Check the panel and port location; Mill City Modbus RTU variants are a different setup path. |
| Phidget | Phidget 2xRTD, Phidget 2xTC, Phidget Databridge | Treat these as sensor-module entries, not as a roaster brand claim. |
| Titanium | Titanium TGX | Validate the TGX probe channels and optional wiring before production use. |
| Tostabar | Tostabar Genius | Covers the Genius catalog entry, not every Tostabar model. |
| VNT | VNT Phidget | Separate from VNT PID, which follows a Modbus RTU path where listed. |
What Rostoc reads
Section titled “What Rostoc reads”Phidget entries read the temperature channels wired to the module — typically
bean temperature and environmental temperature, plus any additional probe
inputs the catalog entry or .aset preset maps. Probe order is defined by the
channel mapping, which is why validating it on the real hardware matters.
Rostoc does not send control commands over this path.
Validate the first roast
Section titled “Validate the first roast”Use the first roast as a short validation run:
- Add the exact Phidget catalog entry or import and review the
.asetpreset. - Confirm the support badge says Experimental.
- Connect with the real Phidget USB device attached.
- Compare Bean Temp, Env Temp, and any extra channels against the roaster display, probe labels, or the Phidgets Control Panel.
- Save a short test batch, reopen it, and confirm stream labels and chart routing before daily production use.
The final connection test requires physical Phidget hardware. Catalog and import review can confirm the expected setup, but live readings should be checked with the actual USB device attached.
Troubleshooting
Section titled “Troubleshooting”- No COM port appears - this is expected for Phidget USB. Rostoc talks to the USB device directly.
- USB device not recognized - try another data-capable cable and USB port, then confirm the Phidgets control panel or driver can see the device.
- Rostoc cannot read the device - close other roasting software, reconnect the Phidget device, and try again. If it still fails, install or reinstall the Phidgets operating-system driver — a missing driver shows up as a missing device.
- The error says “Looked for serial number …” - the machine settings name a specific Phidget serial number and no attached device matched it. A Phidget serial number has 5-6 digits and is printed on the device label — the four-digit number on the board is the model, not the serial. Leave the serial number blank to use whichever Phidget is attached.
- Readings are on the wrong curve - check that probes are connected to the
channels expected by the catalog entry or
.asetimport review.