The issue raised is that Enterprises created a proprietary cable with wiring specific to the Gen3 ECU (PE3) connection to your download computer. The connection between the ECU and firewall terminates in a USB-B female connector. The computer connection uses proprietary cable consisting of USB-B-Type male connector that's wired to an Ethernet RJ45 plug
The inadvertent connection of a standard USB cable (B-Type to A-Type) into the ECU port that's also attached to your computer can fry the ECU, rendering it inoperable and not fixable (explanation is in the note mentioned earlier in this thread.)
You may think this is not plausible, but I have a perfect example in my car. Anyone using an AIM Dash with the dash mounted USB extension also uses USB B-Type female connector. Since that's a standard cable (USB-B male to USB-A male typically used to connect to printers) that terminates in a standard USB-A male connector connector, if I accentually plugged that into the PE3 while it's plugged into my laptop I may fry to the laptop.
I'm not sure why there was a need to go the proprietary cable route since the connection is standard Ethernet RJ45 to the PE3. Ideally, if the Ethernet wiring is standard (I suspect it is since the software uses a network protocol), A PE3 to Ethernet female connector would alleviate that issue, allowing a standard RJ45 cable to be used between this connector and your laptop.
Since I'm not familiar with the actual wiring or signals, perhaps Enterprises can explain why their proprietary approach, requiring two proprietary cables (PE3 to USB-B and USBB to RJ45) was necessary.
I hope that there will be some consideration for resolving this design issue since it has the potential for catastrophic results for the PE3.
Something along these lines:
http://www.wolfautomation.com/products/ ... fgod4HIAQQ