Problem Details
A PCAN-USB FD interface reporting firmware 2.3.1 cannot be updated with the PCAN-Flash utility. The symptom is specific and repeatable:
- The adapter is placed into bootloader mode from PCAN-View.
- PCAN-Flash is started, the hardware profile is selected, and Detect is pressed.
- The module list returns empty — no error dialog, no timeout message, simply nothing.
Because PCAN-Flash gives no diagnostic text, engineers typically assume a driver fault, a USB enumeration problem, or a bricked bootloader. In this case none of those are the cause. The tool is being applied to a device generation that no longer supports it.
2.2.1 do not use PCAN-Flash at all. Running PCAN-Flash against such a unit will always return an empty module list, because the device does not present the proprietary flash protocol the tool scans for.Root Cause
PEAK-System changed the update mechanism for the PCAN-USB FD family. Two distinct update paths exist, and the boundary is the firmware version already resident in the device:
| Installed firmware | Update mechanism | Tool required | Bootloader entry |
|---|---|---|---|
| ≤ 2.2.1 (legacy) | Proprietary flash protocol over the CAN/USB channel | PCAN-Flash (Windows utility) | Hardware/utility-triggered bootloader; module appears in PCAN-Flash list |
| > 2.2.1 (including 2.3.1) | USB Mass Storage Device (MSD) bootloader — file copy | Windows File Explorer only | Bootloader mode set from PCAN-View; device re-enumerates as a removable drive |
With firmware 2.3.1 installed, the device is on the MSD path. Setting bootloader mode causes the adapter to drop its CAN interface personality and re-enumerate on the USB bus as a small removable volume. PCAN-Flash scans for the legacy protocol endpoint, finds no responding device, and returns an empty list. This is expected behaviour, not a failure.
The secondary cause, when the removable drive never appears, is that the host never completed the re-enumeration — typically a USB port, hub, driver, or host-OS handling issue rather than a device fault.
Correct Update Procedure for Firmware > 2.2.1
-
Record the current firmware. Open PCAN-View, connect to the PCAN-USB FD channel, and read the device information. Confirm the firmware string (for example
2.3.1). This determines which path applies. Do not skip this step — applying the wrong path wastes hours. - Close all applications using the device. Any PCAN-Basic application, CANoe/CANalyzer style tool, or second PCAN-View instance holding the channel will block the mode change. Disconnect the CAN bus channel in PCAN-View before proceeding.
-
Set bootloader mode from PCAN-View. Use the device/bootloader function in PCAN-View to command the adapter into bootloader mode. Two things should happen immediately:
- Windows enumerates a new removable volume (a small USB flash drive).
- A help/instruction screen or readme is presented from that volume.
- Read the on-device instructions. The volume exposed by the bootloader contains the vendor's own instruction file. Read it before copying anything; it names the exact file the bootloader expects and the completion behaviour.
- Copy the firmware file to the volume root. Drag the firmware image supplied by the vendor to the root of the removable drive. Do not place it in a subfolder, do not rename it, and do not copy multiple firmware images at once.
- Wait for the device to complete and re-enumerate. The bootloader writes the image and returns to normal operation. The removable volume disappears and the CAN interface reappears. Do not unplug the adapter while the volume is still mounted.
- Verify. Reopen PCAN-View, connect the channel, and read the firmware version. It must show the new version.
Diagnostics When No Removable Drive Appears
If bootloader mode is commanded but no USB volume and no help screen appear, the failure is on the host side of the enumeration. Work the list in order — each step removes one variable.
| Check | Action | What it proves |
|---|---|---|
| Volume enumeration | Open Disk Management and Device Manager (View > Devices by connection) while the adapter is in bootloader mode | Distinguishes "drive mounted but no letter assigned" from "device never enumerated" |
| USB path | Plug directly into a rear-panel root-hub port on the PC. Remove all hubs, docking stations, KVMs, and USB-C dongles | Hubs and docks are the most common cause of failed re-enumeration after a mode change |
| Cable | Substitute a known-good data-rated USB cable | Charge-only or marginal cables enumerate the CAN interface but fail the mass-storage transfer |
| Host OS | Repeat the procedure on a different Windows machine. Windows 7 or Windows 10 are the recommended hosts for this operation | Isolates OS-level mass-storage policy, group policy blocks, or a corrupted driver stack |
| Removable-storage policy | Confirm no endpoint security agent or group policy blocks removable mass-storage devices | Corporate images routinely block MSD, which silently hides the bootloader volume |
| Driver stack | Uninstall and reinstall the current PEAK device driver package, then reboot | Stale driver bindings can hold the device on the old interface after the mode command |
| Power | Verify the port supplies full bus power; avoid unpowered hubs | Brown-out during re-enumeration aborts the mode change |
Endpoint-protection software blocking removable storage is the single most under-diagnosed item on this list. It produces exactly the reported symptom — the device switches modes, but nothing ever appears in Explorer. Testing on a clean, non-domain Windows machine settles it in minutes.
Verification
- Unplug and replug the adapter after the update completes.
- Open PCAN-View and confirm the channel enumerates normally as a CAN FD interface.
- Read the device information page and confirm the firmware version string has changed to the target version.
- Connect to a live CAN FD bus at the intended nominal and data bit rates and confirm frames are received without error frames or bus-off events.
- Confirm the removable bootloader volume is no longer present in Explorer — if it persists, the image was not accepted and the copy step must be repeated with the correct file.
If the firmware version is unchanged after a successful copy, the file was almost certainly the wrong image type for the device variant. Re-download the image for the exact product (PCAN-USB FD, not PCAN-USB or PCAN-USB Pro FD) and repeat.
Practical Notes for Field Work
- Version-gate your procedure. Any internal work instruction for updating PCAN hardware must branch on the installed firmware version at step one. A single procedure written around PCAN-Flash will fail on every modern unit.
- Do not interrupt the write. Removing power or the cable while the bootloader volume is mounted and writing risks leaving the device in bootloader mode. Recovery then depends on re-entering the mass-storage path, which requires a working USB enumeration.
- Keep a known-good update host. A non-domain laptop with Windows 10 and no endpoint-security removable-storage policy removes the majority of update failures before they start.
- Only flash when there is a reason. If the resident firmware supports the CAN FD bit rates and API features your application uses, an update introduces risk without benefit. Flash to fix a documented defect or to gain a required feature.
- Document the as-found and as-left versions in the maintenance record. Interface firmware differences are a frequent cause of "it works on my bench" timing discrepancies during bus captures.
Frequently Asked Questions
Why does PCAN-Flash detect no modules on my PCAN-USB FD?
Because the device firmware is newer than 2.2.1 and no longer uses the PCAN-Flash protocol. Devices above that version update through a USB mass-storage bootloader — you copy the firmware file onto a removable drive the adapter presents. PCAN-Flash returns an empty list by design.
How do I check the firmware version of a PCAN-USB FD?
Connect the channel in PCAN-View and read the device information for that hardware. The version string (for example 2.3.1) determines whether you use PCAN-Flash or the mass-storage file-copy method.
I set bootloader mode but no USB drive appeared. What now?
The device re-enumeration did not complete on the host. Move to a direct rear-panel USB port with no hub or dock, swap the data cable, check Disk Management for an unmounted volume, and confirm no security policy blocks removable storage. If it still fails, repeat on a different Windows 7 or Windows 10 machine.
Can I still use PCAN-Flash on newer devices if I force it?
No. Use the mass-storage path exclusively on firmware above 2.2.1. Mismatching the update protocol to the resident bootloader offers no path to a successful write and only adds risk.
How do I confirm the update actually took?
Replug the adapter, reopen PCAN-View, and read the firmware version — it must show the new value. The bootloader volume must no longer be present in Explorer, and the interface must pass live traffic on a CAN FD bus without error frames.