Apologies in advance for being long-winded, but I figure I'm not the only one who will experience these same issues as the Vectrix software programs keep getting older...
The other night, I tried to update the firmware on my 2007 Vectrix. I had already used the 64-bit Vectrix Diagnostics GUI software (circa 2013) via Windows 10 to install The Laird's NiMH firmware a couple of months ago. I have since installed 19 gen2 Nissan Leaf lithium modules into my bike, confirmed that the motor operates (though the temperature and battery warning lights flash as would be expected with the NiMH firmware and no temp sensors installed), and am trying to update the motor controller (and then will update the ESD charger) firmware.
Using the exact same computer, software setup, and Peak IPEH-002021 166440 USB cable, I got a "DownLoad to VX1Li Motor Controller Failed..." message when trying to install The Laird's 38s lithium MC firmware. The box containing the MC firmware version number was empty and turned from green to red, to me seemingly indicating that it had been cleared but not reprogrammed. With the kill switch in the run position, I had the Ready display on the dash but could not get GO to appear. Fearing the worst, I kept the ignition switch on, tried restarting my laptop and rerunning the firmware install to no avail.
I already had ScooterDiag v2.1 and v1.1 on my computer but they were not functional, so after copying some dll files around, I was able to get each to connect to the CANBUS on my scooter. I may have actually had to uninstall Vectrix Diagnostics GUI before they started working correctly, or maybe I had re-run the PEAK driver setup utility. On the firmware update tab of both v2.1 and v1.1 programs, the text on the lower half of the window was a bit distorted (I assumed some sort of Windows compatibility issue). If I browsed for the motor controller hex file on my computer and clicked the Program button, the program would crash suddenly, the window disappearing.
Many thanks to antiscab who told me I could save a copy of the firmware directly to my C: directory and manually type/ paste in the file location. Doing that, clicking the Program button in either ScooterDiag v2.1 or v1.1 would then prompt me for CLR24_X1.hex, ERA24_X1.hex, and PRG24_X1.hex, which I found in a ScooterDiag v1.1 sub-folder. Unfortunately, I got the same "No response to Clear... Please try again" message with both versions of the program. By that point, my laptop battery was getting ready to die. Antiscab also verified that I could recharge my computer while connected to the scooter (so long as the scooter charger was not plugged in at the same time).
It got to a point in the night where I had to sleep and needed to shut the scooter off, so I was somewhat relieved when I stumbled upon this post: https://visforvoltage.org/comment/63084#comment-63084. I turned off my key, waited the longest 10 or 20 seconds of my life, then turned it back on. The motor was operable again, and ScooterDiag v2.1 and v1.1 showed the current (NiMH) firmware again. That was a major relief, but I still cannot successfully install the motor controller firmware no matter how many times I try.
Has anyone else had similar issues with the motor controller firmware not clearing/ installing correctly using Windows 10? The fact that it never clears the current firmware in the first place makes me believe it could be a CANBUS communication issue, but nothing with my computer setup had changed since the last time I updated the firmware successfully and all three programs showed an active/ green CANBUS connection with the scooter. I don't want to update the charger firmware to The Laird's 38s ESD file until I successfully update the motor controller, but uninstalling and reinstalling the software on my Windows 10 machine repeatedly doesn't seem to do the trick. Next I might try using the 32-bit version instead of 64-bit, or seeing if any friends have an old Windows XP laptop in their closet...