I have scooter diagnostic version 2.0 on my laptop (windows seven). With the grid connect can/usb adapter connected and drivers installed, I have a continuous red light on the can/usb adapter. When I plug the adapter into the Vectrix, turn the bike on and initiate the scooter diagnostics program,
the general page comes up, but the red 'can inactive' indicator never goes green. Antiscab sent me an older version of dll file to install in windows 32 and to the scooter diag folder. I have installed these and still just a constant red light. If I use Pcan view, I can transmit and receive messages over the can/usb adapter, but not when I call up the scooter diagnostic. It's like the diagnostic program never attempts to comunicate with the bike. Does any one have a suggestion?
- All Forums
- EV Racing
- Electric Rides
- Electric Technology
- Community Marketplace
- V Forum
- Recent posts
- My ...
- Sign in
If your laptop is running 64 bit Windows 7, you may never get it to work. You may have to borrow someone's XP or possibly 32 bit Win7 to get results.
Thanks for the reply. I tried using a laptop with XP and it worked.
got all 18 LEAF cells balance charged to 8.3v (4.15 each pair) and hooked up. Started lap top (XP) and scooter diag, got Pcan lamp flashing, closed scooterdiag, connected to bike, turned on bike and restarted scooterdiag. Just battery and temp lights now flash on cluster and headlamp goes out.
Scooter diag Pcan bar stays red ... shut down computer, disconnected Pcan lead and turned off bike.
switched on bike and all systems seem fine, moved bike about 1 ft forward and back, lights horn indicators, brake light all functioning as they should. Battery indicator shows about 30-40% full bars.
At one stage I did notice "CAN bus" message displayed at the bottom of the left hand dial .It appears that the bike is seeing the PCAN but the computer not seeing the bike . Have not yet connected charger (ESD) to the bike.
Not sure what to do next and don't want to mess it up by doing something stupid/wrong. Any advice?
PS Fans and Batt Temp sensors removed and no BMS, 200 amp fuse fitted.
racking my brains to think of anything. The only thing that might offer an option is about 5 years ago I had a 3g wifi dongle that needed a 64bit driver, could that be causing a conflict on the comms side?
It does appear to be quite a fickle piece of software. I ended up doing a fresh XP install on an old laptop just to get it to work.
Not quite. I run it on Win 7 64 and, after I changed 2 DLLs, it works just fine.
Below is what I sent to the Laird to include if he wants with his instructions going forward. Hope it will help here too:
"To help the other guy in the US (if he's having the same issue), here are the two problems I encountered with the software and how I resolved them. Note that I use a Windows 7, Service Pack 1, 64 bit version, but I don't think that was related - would have had the same issues on XP I suspect.
(1) Following your installation instructions to the letter, all was good until and including installing the PEAK drivers so my laptop would see the CANbus adapter (solid red light on the adapter). Problem was that I could not get the ScooterDiag program to run. I got an error message that said that the "msvcp71.dll" was missing. After some google time, it turns out this is some Microsoft-provided library that could be coped from other locations on the computer. This I did - just searched my hard drive for it and found several versions of it. I used on that was in the folder for some camera software that I had on my computer - copied that and pasted it in the ScooterDiag folder where the scooterdiag.exe is. There is already a similarly named file there, "msvcr71.dll", which I did not touch. At this point, the ScooterDiag would start without errors.
(2) The ScooterDiag was not seeing the CANbus - red in the status window. On Visiforvoltage I had seen a thread about that issue and the solution there worked for me too:
(a) in the ScooterDiag folder there should be a PCAN_USB.dll. rename that to PCAN_USB_old.dll.
(b) Get a different version of it from the PEAK web site and save it in the ScooterDiag folder where the renamed DLL is. The address to get it from is this: http://www.peak-system.com/produktcd/Develop/PC%20interfaces/Windows/PCAN-Light%20API/Win32/PCAN_USB.dll That's it - now the software shows green in the status area and sees the CANBus.
I will try the second, my scooter diag is opening fine, just need to get the red to green!! will report back!
Tried new Pcanbus .dll file and now I have the opposite problem, red light flashes, scooter diag opens, green box, readings display on scooterdiag, However now the Bike now does not recognise Canbus mode( NO CANBUS display on Left instrument!)!! and so new firmware will not upload/transfer and scooterdiag shuts down!!
Gave up with old XP computer and went with Windows 7 Laptop as per Kocho advice above... all new Laird firmware loaded sweetly!! Just need to sort out rear lamp/brake light not working, everything else works perfectly. Range shows 93 Miles. Only 2 bars but this will fix with discharge and a fresh charge apparently!
Really pleased and thanks to all for help, advice and goodwill!
You can also just set the gauge to 'full' using ScooterDiag :)
I know this conversation is old, but it was very helpful to me. After a lot of issues, I was able to talk to my Vectrix CAN using the following procedure:
1. Windows 10 laptop
2. Either Peak (Grid Connect) PCAN-USB model IPEH-002022 or model IPEH 002021. Either one worked. (Shout out to my friend Tim for letting me borrow these CAN-USB adapters
3. Installed Peak PCAN- USB drivers from https://www.peak-system.com/PCAN-USB.199.0.html?&L=1
4. Installed scooterdiag.exe v2.1
5. Per @Kocho's suggestion above, changed PCAN_USB.dll to new file from http://www.peak-system.com/produktcd/Develop/PC%20interfaces/Windows/PCAN-Light%20API/Win32/PCAN_USB.dll
6. Connected PCAN to laptop
7. Got solid red light on PCAN
8. Connected straight through DB9 female to DB9 female to Vectrix CAN port and PCAN/USB converter
9. Success! CAN Active went green, and I was able to monitor the Vectrix variables!!!
Thanks everyone for the documentation. Now on to bigger/better things:
1. Why do different battery temperatures differ by like 3-4 °C even though the scooter has sat stationary for >2 days?
2. Why do Ambient Temp 4D and 4E both instantly, randomly jump +/- ~10-15 C?
3. What's the best (i.e. best bang for the bus, least hassle, best performance, etc.) procedure for Nissan Leaf and/or Chevy Volt swaps?
If you have original equipment (i.e. circa 2007) temperature sensors they are now over a decade old.
Without actually using a meter and physically measuring each of the small boards components (quantity 12 each)
it is almost certain those little sensors are bad. They can be had from (insert your favorite parts supplier here) any
good electronics supply company; however, do require soldering skills. The suggestion is to just replace all 12 - they
are fairly inexpensive (for avoiding the nuisance indicators/peace of mind).
I did mine a few years ago and used Mouser PN:594-NTCS0805E3103FMT
(these are 10Kohm, 1% Negative Temperature Coefficient NTC Thermistors, RoHS Compliant); however,
any equivalent will do.....