Post by mhschumacher on Sept 22, 2018 9:12:03 GMT -5
Hello fellow chip makers.
I've had my WD-1 for 6 years and recently upgraded to a Win10 PC. A UC100 motion controller is required since there is no parallel port provided with the PC. My system in this configuration would not run more than 20 minutes without an EStop. Checking the error dialogue on the diagnostics page in MACH3, I got "UC100 Sync Error" every time. Long story short, this EStop was caused by interference sneaking in through the poorly shielded USB cable that communicates with the UC100. The fix is either buy a high end USB cable or (as I did) covered my existing USB cable with a shield. I used braid that I opened up by working a rod down the center of the braid which then allowed me to slide the small connector end through until I covered the entire cable. I soldered a jumper lead to the shield and then connected that to the CNC frame via alligator clip.
Mark
I've had my WD-1 for 6 years and recently upgraded to a Win10 PC. A UC100 motion controller is required since there is no parallel port provided with the PC. My system in this configuration would not run more than 20 minutes without an EStop. Checking the error dialogue on the diagnostics page in MACH3, I got "UC100 Sync Error" every time. Long story short, this EStop was caused by interference sneaking in through the poorly shielded USB cable that communicates with the UC100. The fix is either buy a high end USB cable or (as I did) covered my existing USB cable with a shield. I used braid that I opened up by working a rod down the center of the braid which then allowed me to slide the small connector end through until I covered the entire cable. I soldered a jumper lead to the shield and then connected that to the CNC frame via alligator clip.
Mark