Problem with BUDS/BUDS won't connect - Any Ideas?

[brutusbikes]

Ok, BUDS is kicking my tail. I can't get it to connect to the bike (2009 GS). It always opens in demo mode. connected, not connected, engine on, engine off, running, not running. What am I doing wrong?

[PMK]

First guess is the cable is defective or incorrect.

[pauly1]

Not enough info. Could be cables, software configuration or comm port settings.

[Grandpot]

Is your license expired? Has the date on your computer been changed so that it is out of the license range? Is this a new BUDS system? Has it ever worked?

[Joel The Biker]

Try this sequence.
1. Connect cable to spyder
2 connect cable to computer
3 turn on spyder
4 open/start BUDS program on computer
5 sign in to BUDS
6 Both lights should be lit on MPI cable(if USB light is not lit, then you dont have your ports configured correctly. If CAN light is not lit, then you are not plugged into the spyder correctly or wrong plug on spyder.)
7 click on READ tab on BUDS

[Jetfixer]

After the latest Windows 10 update, I cannot seem to get BUDS to work. The program will load, but refuses to see the VCI module to communicate with the Spyder. BUDS2 works fine, so I think it's a legacy hardware-type issue with Windows. Any suggestions?

[bikerchris1270]

After the latest Windows 10 update, I cannot seem to get BUDS to work. The program will load, but refuses to see the VCI module to communicate with the Spyder. BUDS2 works fine, so I think it's a legacy hardware-type issue with Windows. Any suggestions?

I’ll try mine when I get home….. interesting.

[trong]

Interesting but not uncommon. For every update version of Windows in the last decade or so, some applications will work better whereas some other just stop working altogether or erratically. I'm not sure what kind of communication BUDS system uses, most likely some proprietary protocol(s) and newer Windows version just stops supporting it. You might have to wait for a fix from BRP or a work around. Just my humble opinion and personal experience as an IT Specialist.
Cheers!

[brutusbikes]

I figured it out. The Spyder owners manual had the correct sequence to get it to work. To me, the BUDS manual wasn't clear.

[Jetfixer]

I figured it out. The Spyder owners manual had the correct sequence to get it to work. To me, the BUDS manual wasn't clear.

What is the sequence? My 2020 RTL uses BUDS2 and it works perfectly. Trying to help a friend with a 2017 and BUDS will not see the VCI module.

[EdMat]

Jetfixer, have you tried opening up BUDS in compatibility mode? That might solve your problem.

[Jetfixer]

Yes. No help. The program runs perfectly, but only in demo mode. The icon at the bottom of the screen shows no vci module between the computer and Spyder. I think it's a Windows driver problem and hope there's a work-around.

[Jetfixer]

Ok. I've tried everything I can think of. I uninstalled both BUDS and BUDS2, all the IXXAT VCI files, deleted the leftover BRP and IXXAT folders, restarted, etc. Then re-downloaded all installation files. Reinstalled BUDS. It said there was no VCI driver present and would open in Demo mode. That would be correct. I then installed the driver files and rebooted. Started BUDS, and it no longer complained about missing driver files, the VCI has a solid green USB light, but BUDS still starts in demo mode and shows no VCI connected at the bottom of the screen. So in other words, no help at all. Will not connect to a 2016 RTL no matter what startup sequence I try. Then I downloaded and installed a fresh copy of BUDS2. Solid green USB light, solid green CAN light. BUDS2 will connect to the 2016 RTL (which it shouldn't) but identifies it as a Skidoo with an invalid VIN! BUDS2 will read the modules and show the occurred and current faults, and suggest fixes, but gives instructions for screen pages that are only used by BUDS1. However, it DID allow me to erase all fault codes. Again, this only happened with the current Windows 10 version. BUDS1 worked well before. I believe this has got to be a Windows driver issue. Not a program or program compatibility issue since both BUDS and BUDS2 will run. BUDS2 will show all the correct info for my VCI module such as the actual serial number. BUDS1 will not read it even though it has a solid green USB light on. Any help would be greatly appreciated.

[Jetfixer]

Solved it! The license code for BUDS somehow got erased from the installed files. Re-registering the license fixed everything!!

[hank573]

Anyone out there running Buds/Buds2 on MacBook Pro running Windows 10?? I have an older Macbook that I can install Windows10 on but am not sure the BRP Buds would work. Any info would be appreciated. Thanks in advance.

[sonsofanarchy]

Hi, do you solve your problem ? Same for me

[Peter Aawen]

Hi, do you solve your problem ? Same for me

If you're asking about Brutusbikes' original question sonsof.., we saw that'd been figured out in post #9...


I figured it out. The Spyder owners manual had the correct sequence to get it to work. To me, the BUDS manual wasn't clear.

But if you're asking about Jetfixer's failure to get it to start, we heard that was solved in post #14...


Solved it! The license code for BUDS somehow got erased from the installed files. Re-registering the license fixed everything!!

Or was it some other problem you were having? Hank's problem with a Mac that he raised in Oct '21 maybe?? :dontknow:

[Jetfixer]

Hi, do you solve your problem ? Same for me

You may want to ask your question through a PM. That last response was from last October. This BUDS forum was just created and these older posts were moved from various other forums. I wish I could help, but I use Windows.

[sonsofanarchy]

Anyone out there running Buds/Buds2 on MacBook Pro running Windows 10?? I have an older Macbook that I can install Windows10 on but am not sure the BRP Buds would work. Any info would be appreciated. Thanks in advance.

Hi, do you solve this problem ? Same for me ....

[Jetfixer]

new version of buds2 out now. Maybe that will help...