AXE027/AXE027D Programming Tool
The AXE027 cable contains an FTDI USB<>serial convertor chip. This enables communication with the PICAXE chip during the programming process.
The FTDI chip is a generic chip used by many companies. Therefore companies using the chip often customise the settings inside the chip to give each product a unique product ID (PID). This is so the computer can identify exactly which product is connected.
The unique PID of the AXE027 cable is bd90 (listed as 'AXE027 PICAXE USB')
The AXE027D is compatible with the PICAXE system but uses the generic PID 6001 instead (listed as 'USB Serial Port'). The Programming Tool below can convert AXE027 to AXE027D and vice versa.
Windows: the AXE027 unique PID and AXE02D default PID have WHQL certified drivers available on Windows Update.
Windows 11 on ARM64: (or in Parallels on ARM Mac) the AXE027 unique PID is not supported so reprogram the AXE027 cable to use the default AXE027D 6001 PID instead. Then use the manual installation (section 3.3) instructions with the FTDI ARM driver. Note in Parallels this zip file must be extracted to the C:\ Windows partition drive e.g. C:\CDM-v2.12.36.4-for-ARM64-Signed-Distributable
More information on using Windows 11 on ARM64 available here
Linux: For kernel 6.19+ the AXE027 PID (bd90) and default PID are directly supported. On older kernels the default (preinstalled) ftdi_sio driver only recognises the default FTDI PID, which is 6001. However the user can use 'modprobe' to set the driver to recognise the AXE027 PID (bd90). Therefore Linux users on older kernels may choose either to simply use a 'modprobe' command or to reprogram the cable to set the PID to 6001.
Older versions of Linux (kernel 3.13 to 6.18): 64-bit Linux instructions
Older obsolete versions of Linux (pre 3.13):
sudo modprobe ftdi_sio vendor=0x0403 product=0xbd90
sudo adduser your_name dialout
Mac: the AXE027 unique PID is supported via the custom AXE027 drivers.
Chromebook: Newer versions (April 2026 onwards) support both PIDs. For older versions it is recommended that Chromebook users reprogram the AXE027 cable to use the default 6001 PID instead. The cable will then instantly work correctly on the Chromebook (and will also continue to work correctly on all other operating systems using the default FTDI drivers).
Summary
| Windows | PID bd90 | Install AXE027 driver |
| PID 6001 | Install default FTDI driver | |
| Windows 11 on ARM64 | PID bd90 | Not available |
| PID 6001 | Manually install FTDI ARM64 driver | |
| Mac | PID bd90 | Install AXE027 driver |
| PID 6001 | Use default system driver | |
| Linux | PID bd90 | Use default system driver (6.19+). Older versions use modprobe command as above |
| PID 6001 | Use default system driver | |
| Chromebook | PID bd90 | Use default system driver |
| PID 6001 | Use default system driver | |
| Android | PID bd90 | Use default system driver |
| PID 6001 | Use default system driver | |
| iOS | PID bd90 | Apple does not allow USB<>serial adapters on iPhone/iPad |
| PID 6001 | Apple does not allow USB<>serial adapters on iPhone/iPad |
Using the AXE027 Reprogramming Tool (tool runs on Windows only)
- Plug the AXE027 or AXE027D cable into the Windows computer. Note that when reprogramming a cable for ARM64 use this tool must be used on a different, Intel, computer.
- Let the Windows driver install the cable as normal.
- Download the reprogramming tool and unzip the two files, e.g. to your desktop
- Run the ProgAXE027.exe file (note this file needs the .Net 3.5 runtimes, which are probably installed on your computer anyway).
- Click the desired 'Program to Default FTDI' (AXE027D) or 'Program to PICAXE AXE027' button and wait for reprogramming to end.
Note that after reprogramming is complete the cable will automatically reset.
As the cable now has a different PID it is normal for the Windows 'New Hardware Wizard' to run again.