VNT Phidget roaster setup with Rostoc.

Direct Answer

Rostoc can be tested with the VNT Phidget catalog entry for experimental Phidget USB logging.

VNT PID is a different catalog path that uses Modbus RTU where listed. Choose the entry that matches the controller and connection in front of you.

• Use VNT Phidget for experimental USB-connected sensor logging.
• Use VNT PID only when the machine matches the Modbus RTU catalog entry.
• Do not swap these entries just because the brand is the same.
• Validate readings and saved labels before production use.

Covered VNT entries

The controller is the key detail for VNT setup. A Phidget sensor bridge and a PID controller with Modbus RTU should be treated as different support branches.

If the connection type is unclear, collect photos of the controller and cable path, plus screenshots or `.aset` files from any existing logger.

• VNT Phidget - experimental Phidget USB logging.
• VNT PID - separate Modbus RTU path where the catalog marks it available.
• Other VNT variants - request support unless an exact catalog entry says otherwise.

Validation checklist

Start by confirming whether the computer sees a Phidget USB device or the machine exposes a serial/RS-485 Modbus path. The wrong entry will produce confusing results.

Use Rostoc as the logging and records layer unless a specific future release states control support for the exact setup.

• Confirm whether the machine is VNT Phidget or VNT PID.
• Install the Phidgets driver for the Phidget path.
• Close other apps connected to the device.
• Compare Rostoc BT, ET, and optional channels against the roaster display.
• Save and reopen a short test batch to confirm stream labels and chart routing.

Support boundaries

Contact support if the controller identity, port type, or channel mapping is unclear. The brand name alone is not enough to choose the right VNT entry.

Start with the machine compatibility guide, the VNT catalog page, and the Phidget USB setup docs.

FAQ