Skip to content
binho.io (opens in a new tab)Contact Us

Binho Pulsar: Troubleshooting

Find the symptom, then open the page. The steps are the same for the Pulsar and the Supernova.

SymptomPage
The adapter stops answering, times out, or resets itselfAdapter Stops Responding
The adapter shows up as a USB drive or as “bootloader”, or a firmware file is rejectedFirmware and Bootloader
The adapter is not found on Windows or macOSWindows and macOS
The adapter is not found on Linux, or its serial number is emptySolving USB Connection Issues on Linux
mc3.binho.io does not see or keep the adapterMission Control 3 in the Browser
  • 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 udev rule, installed once. See Solving USB Connection Issues on Linux.
  • 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 of set_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].