• There were many reasons for the change of the site software, the biggest was security. The age of the old software also meant no server updates for certain programs. There are many benefits to the new software, one of the biggest is the mobile functionality. Ill fix up some stuff in the coming days, we'll also try to get some of the old addons back or the data imported back into the site like the garage. To create a thread or to reply with a post is basically the same as it was in the prior software. The default style of the site is light colored, but i temporarily added a darker colored style, to change you can find a link at the bottom of the site.

BUDS/BUDS2 Mini VCI Driver Conflicts!

Jetfixer

Jetfixer

Well-known member
So the latest version of BUDS2 released 09Aug23 (23.2.1 A6CC Update) was acting a little squirrely. I had a lot of difficulty connecting to a 2023 RTL. BUDS2 kept insisting it couldn't find the VCI device, even though it was showing me all the screens. So I downloaded and installed the latest Win 11 version of the MiniVCI Drivers. That seemed to clear up the connection problems with the 2023 RTL, but later on when I tried to use BUDS on a 2013 RTL, it would not find the VCI at all. I finally went back and uninstalled the latest Win 11 driver package, reinstalled the original driver package, and now BUDS seems to be finding the VCI. Can't fully test it yet since I don't have the 2013 here at the moment. It almost seems like I'm going to have to have a dedicated laptop for BUDS, and one for BUDS2...
 
Jetfixer said:
So the latest version of BUDS2 released 09Aug23 (23.2.1 A6CC Update) was acting a little squirrely. I had a lot of difficulty connecting to a 2023 RTL. BUDS2 kept insisting it couldn't find the VCI device, even though it was showing me all the screens. So I downloaded and installed the latest Win 11 version of the MiniVCI Drivers. That seemed to clear up the connection problems with the 2023 RTL, but later on when I tried to use BUDS on a 2013 RTL, it would not find the VCI at all. I finally went back and uninstalled the latest Win 11 driver package, reinstalled the original driver package, and now BUDS seems to be finding the VCI. Can't fully test it yet since I don't have the 2013 here at the moment. It almost seems like I'm going to have to have a dedicated laptop for BUDS, and one for BUDS2...
Click to expand...

I have a strong suspicion that it's absolutely imperative that the person ( ie. dealer Tech ) must know how to use either BUDS systems.... as an example the ROLO Laser alignment system does an excellent job of alignmebt ,..... but ONLY if the person using it knows how .... JMHO ... Mike :thumbup:
 
Turns out it was a driver issue with the VCI driver. After rolling back to the previous driver file, all is well again, both BUDS and BUDS2.
 
You must log in or register to reply here.

Similar threads

Jetfixer
Possible new function in BUDS2
Replies
1
Views
1K
pegasus1300
pegasus1300
Jetfixer
BUDS forum needed
Replies
4
Views
2K
Jetfixer
Jetfixer
Jetfixer
Latest version BRP BUDS2 21.1.0 (A68E UPDATE) buggy?
Replies
4
Views
2K
Jetfixer
Jetfixer
PMK
BUDS and BUDS2 questions
Replies
13
Views
5K
hadog
H
Back
Top