Home/Devices/iTop Skywalker V2 setup

iTop Skywalker V2 setup

Get your iTop Skywalker V2 talking to the Roastline desktop app in a few minutes — over USB (recommended) or Bluetooth.

Protocol
TC4 serialArtisan-style · 115200 8N1
Best connection
USB serialCH340 chip · plug & go
Also supports
Bluetooth (SPP)AKROASTER pairing
Profile
skywalker-v2bundled with the app
DEVICE GUIDE · iTop Skywalker V2 · ~5 min

USB cable plugged in? Always choose USB serial in device settings — not Bluetooth (AKROASTER). If both are connected, picking the wrong type sends commands to the wrong port.

Before you start

Four quick checks before you plug anything in:

  1. Install the Roastline desktop app (the Electron build) — not the browser-only simulator.
  2. Use a data-capable USB cable. Charge-only cables will not work.
  3. Install the correct USB-serial driver so your computer shows a port (step 2 below).
  4. Close Artisan or any other app that might already be using the serial port.

1 · Identify your USB chip

iTop Skywalker V2 uses a USB-to-serial chip inside the cable/board. Most Skywalker units use the CH340, which Roastline auto-detects. Find yours, then install its driver below.

ChipVID:PIDDriver
CH340 (WCH / QinHeng)1a86:7523Windows: WCH CH341SER · macOS: CH341SER for Mac — verified on Skywalker
FTDI FT232 / FT231X0403:6001FTDI VCP drivers
Silicon Labs CP210x10c4:ea60CP210x drivers
Arduino / 16U22341:0043Often built into the OS

Windows — open Device Manager → Ports (COM & LPT) (or Other devices if the driver is missing), then Properties → Details → Device instance path and read the VID_XXXX&PID_YYYY. A CH340 shows USB\VID_1A86&PID_7523\….

macOS — list connected serial devices in Terminal:

$ system_profiler SPUSBDataType | grep -A5 -i serial
$ ls /dev/cu.usbserial* /dev/cu.wchusbserial* /dev/cu.usb* 2>/dev/null

2 · Install the driver

macOS (CH340 / WCH)

  1. Install WCH CH341SER for Mac.
  2. Replug USB. If prompted, allow the driver in System Settings → Privacy & Security.
  3. Confirm a call-out port exists — use /dev/cu.*, not /dev/tty.*, e.g. /dev/cu.wchusbserial2120 or /dev/cu.usbserial-2120.

Roastline accepts small naming differences (with or without a hyphen before the number).

Windows (CH340 / WCH)

  1. Install WCH CH341SER. Reboot if prompted, then replug USB.
  2. In Device Manager you should see USB-SERIAL CH340 (COM4) with VID_1A86&PID_7523.
  3. Do not install FTDI drivers if Device Manager shows VID_1A86 — that is a CH340.

Check available ports in PowerShell:

> [System.IO.Ports.SerialPort]::GetPortNames()

Linux

  1. Most modern kernels already include the ch341 / ftdi_sio modules. If yours doesn't, install the WCH CH341SER for Linux driver.
  2. Add your user to the dialout group, then log out and back in:
$ sudo usermod -aG dialout "$USER"

Then check for /dev/ttyUSB* or /dev/ttyACM*.

3 · Connect over USB

This is the usual path when the roaster is plugged in with USB.

  1. Open the device pickeriTop Skywalker V2.
  2. Expand Connection & settings (advanced).
  3. Under Connection, select USB serialnot Bluetooth (AKROASTER).
  4. Serial port → Refresh, then pick your WCH port — e.g. /dev/cu.wchusbserial2120 (macOS) or COM4 (Windows). Your choice is saved automatically.
  5. (Optional) Turn on Allow machine control to send burner / air / drum commands. It's off by default — the session stays read-only until you enable and save it.
  6. Click Save, then press Start.

After Start, USB waits about 2 seconds for the board to boot. Temperatures should appear within a few seconds.

4 · Verify the connection

Open View → Console Log (Cmd+Shift+L on macOS, Ctrl+Shift+L on Windows). A good USB connect looks like:

CONNECT device=skywalker-v2 preferred=usb port=/dev/cu.wchusbserial2120
explicit serial port /dev/cu.wchusbserial2120 → connection usb
endpoint usb on /dev/cu.wchusbserial2120

Turn on Tools → Serial Debug Logging to see the raw traffic. Readings should come back as a comma-separated temperature line on the USB path (not /dev/cu.AKROASTER):

/dev/cu.wchusbserial2120,115200,8,N,1 || Tx = READ
/dev/cu.wchusbserial2120,115200,8,N,1 || Rx = 25.0,114.4,128.4

Adjusting burner to 10%, air to 25%, and drum to 80% should send:

Tx = OT1,10
Tx = OT2,25
Tx = OT3,80

If you see OT1;10 or DRUM;100 (semicolons) instead, you connected with the V1 profile by mistake — switch to iTop Skywalker V2 in the device picker.

5 · Connect over Bluetooth

Use Bluetooth only when you're not using USB for this session.

macOS

  1. Pair the roaster in System Settings → Bluetooth.
  2. In Roastline, choose Bluetooth (AKROASTER)Start. The port /dev/cu.AKROASTER is auto-detected.

Windows

  1. Pair in Settings → Bluetooth & devices.
  2. Note the outgoing COM port (its name contains "Bluetooth").
  3. In Roastline, choose Bluetooth (AKROASTER)Serial port → Refresh → pick the Bluetooth COM → Start.

Troubleshooting

SymptomLikely causeWhat to do
Serial log shows /dev/cu.AKROASTER but USB is plugged inBluetooth selected, or stale settingsDevice settings → USB serial → pick WCH port → Save → reconnect and Start
Empty COM / port listDriver missing or wrong chipInstall WCH CH341 for VID_1A86; replug USB
macOS: no /dev/cu.*WCH driver not installed / blockedInstall CH341SER for Mac; check Privacy & Security
Windows: ? in Device ManagerCH340 driver not installedInstall CH341SER
Skywalker "not found"No port matchesSerial port → Refresh, pick the port manually; check Console Log
Connected but BT/ET emptyWrong port, board booting, or parse issueEnable serial debug; confirm Rx = CSV on the USB path; wait ~2s after plug-in
Controls greyed outRead-only session (default)Enable Allow machine controlSave → reconnect
TC4 read failed / timeoutPort in use or wrong linkClose Artisan; make sure only one app uses the port
Settings stuck on BluetoothOld saved prefsReset to defaults in device settings, then reconfigure USB
Bluetooth silent after reconnectStale RFCOMM / COM linkRe-pair; pick the COM port again (Windows)

Skywalker V1 vs V2 reference

Both share the same TC4 telemetry (READ, CHAN, UNITS, FILT). The difference is in machine control: V1 uses semicolons and named commands; V2 uses commas and OT output channels.

Skywalker V1Skywalker V2
Profile idskywalker-v1skywalker-v2
ProbesBean temp (BT) onlyBT + environmental (ET)
TC4 channel mapCHAN;0100CHAN;2100
TransportUSB serial onlyUSB or Bluetooth
SeparatorSemicolon ;Comma ,
ControlExampleV1V2
Burner10%OT1;10OT1,10
Air25%OT2;25OT2,25
Drum> 0%DRUM;100 (on/off)OT3,80
Drum0%DRUM;0OT3,0
CoolingonCOOL;100CLDN,ON
CoolingoffCOOL;0CLDN,OF

Takeaway: V1 drum is on/off only — any slider value above 0% sends DRUM;100. V2 controls the drum speed directly with OT3,{value}.

Milestone events are the same on both (standard TC4 EVT numbers): Charge EVT,1, Turning point EVT,2, Dry end EVT,3, First crack start EVT,4, First crack end EVT,5, Second crack start EVT,6, Drop EVT,8.

Still stuck connecting?

Send us your Console Log and we'll help you get roasting.