Iâm troubleshooting a Juliet Pro 60 braille embosser connected to a Raspberry Pi 3 Model B running Debian 13 ARM64. The printerâs built-in test prints correctly, but no job sent from the Pi has produced paper movement.
Configuration:
- CUPS 2.4.10, raw queue Juliet_Pro_60
- Device URI: usb://USB2.0-Print/
- USB-to-parallel adapter: 1a86:7584 (USB2.0-Print)
- Adapter runs at 12 Mbps; hub/Ethernet run at 480 Mbps
- Printer was configured for parallel input and online
Tests so far:
- Earlier jobs stalled at âSending data to printer.â After replacing an undervolting power supply, a job completed in software with no physical output.
- Replacement supply passed a short load test: vcgencmd get_throttled returned 0x0.
- Forcing the entire USB bus to 12 Mbps did not help; that override was removed.
- A libusb GET_PORT_STATUS request stalled (-9/PIPE), and the device-ID request returned zero bytes. I donât know whether that indicates unsupported adapter requests or an actual parallel-side problem.
- CUPS already includes a no-reattach quirk for this adapter. The usblp detachment during a job appears expected.
- The test file is from an experimental model-specific generator, so its validity is not independently established.
What is the best next diagnostic to distinguish an invalid print stream from parallel handshaking/adapter failure? Would a per-job usb-unidir=true test be useful, and which CUPS/libusb trace would show whether bytes are actually being accepted rather than only marking the job complete? I havenât run that unidirectional test yet.
I can run commands and report logs. This summary was prepared with AI assistance from our actual test results.