Binho Pulsar: Troubleshooting
Find the symptom, then open the page. The steps are the same for the Pulsar and the Supernova.
| Symptom | Page |
|---|---|
| The adapter stops answering, times out, or resets itself | Adapter Stops Responding |
| The adapter shows up as a USB drive or as “bootloader”, or a firmware file is rejected | Firmware and Bootloader |
| The adapter is not found on Windows or macOS | Windows and macOS |
| The adapter is not found on Linux, or its serial number is empty | Solving USB Connection Issues on Linux |
| mc3.binho.io does not see or keep the adapter | Mission Control 3 in the Browser |
Specific to the Pulsar
Section titled “Specific to the Pulsar”- In bootloader mode the adapter mounts a USB drive named PULSAR. See Firmware and Bootloader.
- Firmware for the Pulsar is named
pulsar-app-<version>.afx. See Firmware. - Mission Control 2.16.1 and earlier do not work with Pulsar firmware 4.x. Use Mission Control 3.
- The Pulsar appears as both a USB HID device and a USB serial port. If the serial port is missing, or behaves as RS-485 or CAN-FD when UART is expected, check the mode: Virtual COM Port Modes.
- On Linux the Pulsar needs a
udevrule, installed once. See Solving USB Connection Issues on Linux.
Known Limitations
Section titled “Known Limitations”- One role at a time. I2C and SPI each run as a controller or as a target, but not both at the same time.
- Self-powered targets: call
use_external_voltage()instead ofset_voltage(). See Target Voltage. - CAN-FD mode: 16 KB bulk transfers are unavailable while the serial port is in CAN-FD mode. Switch back to UART pass-through for bulk work.
Still stuck? Collect the details listed in Collect Information for Support and email [email protected].

