snap motor driver problems
Hey guys, I'm currently building a version 2 printer, and since I'm still waiting for my acrylic to come in, I though I'd play around with the snap motors and the fabinterpreter, but i'm having some issues with the drivers for the servos. First off, let me say that i'm not the most computer inclined, so feel free to use small words and ask obvious questions that might be common sense for a normal person, lol.
So the problem i'm having is that the drivers are not auto-installing. I have my box set to passthru mode, and anytime i tell the installation pop-up box to "install automatically" it tells me that no drivers were found, and anytime I try to point it to the snapmotor CD information (installed on my hard drive), it doesn't fine any driver files.
So that begin said, I found an installation tutorial here:
http://robots.iit.edu/index.php?n=Public.SettingUp3DPrinter
that I followed, and after installing the FTDI USB to serial driver, my PC now recognized the snap motor hub. Now the problem is that anytime I try to load a printer configuration (after changing the COM port in them), it reboots my PC...
any help/ideas?
It happened kind of the same. I solved the installation issue by changing the PC : an old HP laptop vs a recent DELL optiplex. We failed to install it on Ubuntu, and my boss doesn't want to by a Mac.
Bertrand
guess i should also mention i'm running 32X WIN XP...
Wow I have never heard of that before. Make sure that you have the right drivers from FTDI for windows xp.
I downloaded the "x86 (32-bit)", 2.08.08 version for windows. I don't need to use an old release version or anything do I?
so it looks like it's a problem with the FTDI driver and something else on my PC. I installed the FTDI driver on my laptop, and I can move the servos without any problems with the program supplied with the snap hub, but when I try to do it on my PC it reboots my machine...
but of course I still can't try out the interpreter software because it won't load on my laptop now, lol. I can never win when it comes to computers, lol.
I got it working...not sure what caused it, but it was a good excuse to reinstall windows.