Question: Does it work with the subvan E11 device ?

[r10r]

Hi @heeen,

i recently bought a subvan E11 device (12mm-15mm label maker)
Do you know whether your driver will also work with this device ?

Greetings
Ruben

[heeen]

i only have a t50 but I invite you to clone it, check the usb id and try it out. maybe you need to change the ids the driver recognizes

[heeen]

I tasked my agent to support all devices the official apps/drivers support, here's a preliminary result:

  How the apps detect compatible devices

  USB (Windows Electron app / KatasymbolEditor)

  Detection is purely by VID/PID via WebHID. All devices share VID 0x1820 (6176 decimal) with 18 distinct PIDs:
  ┌───────────┬───────────┬───────────────┬───────────┬────────────────┐
  │ PID (hex) │ PID (dec) │     Name      │  Series   │    Category    │
  ├───────────┼───────────┼───────────────┼───────────┼────────────────┤
  │ 0x2072    │ 8306      │ T50M Plus     │ T50Plus   │ labelMachine   │
  ├───────────┼───────────┼───────────────┼───────────┼────────────────┤
  │ 0x2073    │ 8307      │ T50M Pro      │ T50Pro    │ labelMachine   │
  ├───────────┼───────────┼───────────────┼───────────┼────────────────┤
  │ 0x2074    │ 8308      │ T50s          │ T50Pro    │ labelMachine   │
  ├───────────┼───────────┼───────────────┼───────────┼────────────────┤
  │ 0x2076    │ 8310      │ T50M Pro (v2) │ T50Pro    │ labelMachine   │
  ├───────────┼───────────┼───────────────┼───────────┼────────────────┤
  │ 0x2077    │ 8311      │ T50M Pro (v3) │ T50Pro    │ labelMachine   │
  ├───────────┼───────────┼───────────────┼───────────┼────────────────┤
  │ 0x2075    │ 8309      │ T80M          │ T80Pro    │ labelMachine   │
  ├───────────┼───────────┼───────────────┼───────────┼────────────────┤
  │ 0x207A    │ 8314      │ T80MPro       │ T80Pro    │ labelMachine   │
  ├───────────┼───────────┼───────────────┼───────────┼────────────────┤
  │ 0x203E    │ 8254      │ SP650         │ SP        │ signageMachine │
  ├───────────┼───────────┼───────────────┼───────────┼────────────────┤
  │ 0x202F    │ 8239      │ TP86A         │ TP        │ tpMachine      │
  ├───────────┼───────────┼───────────────┼───────────┼────────────────┤
  │ 0x2081    │ 8321      │ TP86A (v2)    │ TP        │ tpMachine      │
  ├───────────┼───────────┼───────────────┼───────────┼────────────────┤
  │ 0x2080    │ 8320      │ TP80A         │ TP        │ tpMachine      │
  ├───────────┼───────────┼───────────────┼───────────┼────────────────┤
  │ 0x202E    │ 8238      │ TP80A (v2)    │ TP        │ tpMachine      │
  ├───────────┼───────────┼───────────────┼───────────┼────────────────┤
  │ 0x202C    │ 8236      │ TP76I         │ TP        │ tpMachine      │
  ├───────────┼───────────┼───────────────┼───────────┼────────────────┤
  │ 0x2087    │ 8327      │ TP76I (v2)    │ TP        │ tpMachine      │
  ├───────────┼───────────┼───────────────┼───────────┼────────────────┤
  │ 0x2090    │ 8336      │ G11 Pro       │ G_DPI_200 │ gMachines      │
  ├───────────┼───────────┼───────────────┼───────────┼────────────────┤
  │ 0x2092    │ 8338      │ G15 Pro       │ G_DPI_200 │ gMachines      │
  ├───────────┼───────────┼───────────────┼───────────┼────────────────┤
  │ 0x2093    │ 8339      │ G15 MPro      │ G_DPI_200 │ gMachines      │
  ├───────────┼───────────┼───────────────┼───────────┼────────────────┤
  │ 0x2091    │ 8337      │ G18 Pro       │ G_DPI_200 │ gMachines      │
  └───────────┴───────────┴───────────────┴───────────┴────────────────┘
  The Katasymbol-branded editor filters to only PIDs 8306, 8307, 8309, 8310, 8314 (T50/T80 label printers).

  Bluetooth (Android APK)

  Detection is by BT name prefix matching — the APK matches names starting with BT serial prefixes like T0096A, T0117A, G0028A, etc. (hundreds of them in DeviceConstants.java). Each prefix maps to a specific Device class. There's also a MAC prefix filter (A4:93:40).

  Does it implement multiple protocols?

  One protocol, different parameters. The wire protocol (command set 0x10-0xD9, LZMA compression, column-major bitmap) is the same across all models. The differences are:

  1. Transport framing — BT uses 0x7E 0x5A header with 512-byte frames + checksums; USB HID uses 0xC0 0x40 header with 64-byte reports, no checksums
  2. DPI — T50 series: 8 dots/mm (203 DPI), T80M Pro: 7.9 dots/mm, G series: 200 DPI (via G_DPI_200 flag)
  3. Print width — T50: 48mm max, T80: wider, SP650: 672px fixed height, TP: 144px fixed height
  4. Response handler — 5 different oninputreport handlers based on category (isT5080, isSP, isTP with sub-variants for TP86A/TP80A, and isG), but these just handle slightly different status response formats
  5. Printing process — a numeric ID (17=T50Plus, 18=T50, 19=T80, 24=TP2000, 28=MP50, 30=T80Pro, etc.) that selects minor behavioral variations in the print flow

  The core BasePrint.java / T50PlusPrint.java handles all models. The "printing process" enum selects small tweaks (raster orientation, padding logic), not fundamentally different protocols.

  What's relevant for our driver

  Since we already implement the T50Pro protocol, supporting the other label printers (T50M Plus, T80M, T80MPro) would mainly require:
  - Adding their PIDs to the VID/PID match list
  - Reporting the correct model name in the device ID string
  - Possibly adjusting DPI (T80MPro uses 7.9 dots/mm) and max print width

  The TP (tube), SP (signage), and G (portable industrial) machines use the same wire protocol but have fundamentally different raster geometry (rotated, different fixed dimensions), so they'd need more work.

[heeen]

I added support for all printers the official app supports but I have no way to test it

[r10r]

Thanks a lot for your detailed response. The E11 is officially supported by the iOS katasym App and the subvan app - so I suppose it must support one of the listed protocols. Is it also listed in the KatasymbolEditor on windows ?
Nevertheless, I'll test the E11 device in the next days.

[heeen]

can you test with the current version

[Todoori]

Hi,

I tried using the printer on Debian Trixie. I could not get it to connect.
Using bluetoothctl I was able to find the device, trust it, and connect to it, but not pair:

Device A4:93:40:AF:B0:B5 (public)
	Name: T0182A2507162197
	Alias: T0182A2507162197
	Paired: no
	Bonded: no
	Trusted: yes
	Blocked: no
	Connected: no
	LegacyPairing: no
	UUID: Generic Access Profile    (00001800-0000-1000-8000-00805f9b34fb)
	UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
	UUID: Tencent Holdings Limited. (0000fee7-0000-1000-8000-00805f9b34fb)
	RSSI: 0xffffffb9 (-71)
	AdvertisingFlags: 06      

Notably, a device starting with T018 is not in the models.toml file.

From my understanding, this suggests that the E11 uses BLE, which is currently not supported.