The concern is that this 'garbage data' COULD cause engine damage if one is using a 'fake' FTDI chip on the ALDL interface.Just over a year ago, FTDI, manufacturers of the most popular USB to serial conversion chip on the market, released an update to their drivers that bricked FTDI clones.
After a year, we have the latest update to FTDI gate. Instead of bricking fake chips, the latest FTDI drivers will inject garbage data into a circuit.
Can't say I blame FTDI for playing hard ball on fake chips but the implications are that most people don't know they even have the fakes (ie. end user).
http://hackaday.com/2016/02/01/ftdi-dri ... ips-again/
EDIT: Here's a fix..
If you manually select an older driver, like 2.08.30, you have to change the driver not only on the obvious "USB Serial Port (COMx)" (ftdiport.inf) but also the corresponding "USB Serial Converter" (ftdibus.inf) listed under "USB-Controller" in the device manager. After changing BOTH to 2.08.30, the chip works fine again. It is easy to see if you list the devices by connection. (screenshot)