Guide
Connection troubleshooting
Steps when roaster connect fails or temperatures look wrong
Fresh install on a new PC
Section titled “Fresh install on a new PC”Machine settings are stored on that PC. On a new computer:
- Sign in with the same account
- Reinstall USB drivers / Phidget Network Server
- Re-add machine: serial port, IP, slave ID
- Re-enter capacity and other machine metadata
USB serial roasters
Section titled “USB serial roasters”- Settings → Roasting machines → select machine → Connect
- Confirm serial port (COM can change after replug)
- Baud, slave ID, register addresses match the manual
- Empty port list → Serial drivers
- Still failing → test on another PC
- Fails everywhere → cable, hub, roaster hardware → maker support
LAN (Modbus TCP)
Section titled “LAN (Modbus TCP)”- Same network for roaster and PC
- Did the roaster IP change? Update the app
ping <roaster IP>if allowed by policy- Port 502 blocked by firewall/router?
- Giesen/Probat need maker network setup first
- Fails on other PCs → roaster, switch, cables
Phidget
Section titled “Phidget”- Phidget Control Panel → Network Server Running
- Devices tab shows live temperature
- App channel map matches Control Panel
- Re-read Phidget setup
Live temps look wrong
Section titled “Live temps look wrong”| Symptom | Check |
|---|---|
| Always 0 | Wrong register / slave ID |
| 10× or 0.1× | Scale factor (÷10, ÷100) |
| BT/ET swapped | Swap channel mapping |
| Dropouts / spikes | USB cable, RS485 termination, power noise |
If Artisan is fine, compare values 1:1 with Artisan settings.
App & sync
Section titled “App & sync”- Login fails: Confirm the same account works on the web
- Profiles missing: Wait for sync on a good network, or restart the app
- Subscription not recognized: Check Pro on the account page
Still stuck
Section titled “Still stuck”Email Contact with:
- OS and app version
- Roaster make & model
- Path (USB / LAN / Phidget)
- Error screenshots
- Artisan settings capture if any