78
edits
CNC router, wood (Precix) ID:153: Difference between revisions
Jump to navigation
Jump to search
→Each Axis (XYZ): troubleshooting updates
Michael.fiss (talk | contribs) |
Michael.fiss (talk | contribs) (→Each Axis (XYZ): troubleshooting updates) |
||
| Line 190: | Line 190: | ||
In our setup, Mach3 sends pulses to the a servo driver which moves each servo while monitoring the axis' reported movement via direct feedback from the rotary encoder, at a resolution of 128ppr (x4 = 512). <ref>https://forum.protospace.ca/t/cnc-router-acting-funny/243/29</ref> That part of the system is “closed loop”. | In our setup, Mach3 sends pulses to the a servo driver which moves each servo while monitoring the axis' reported movement via direct feedback from the rotary encoder, at a resolution of 128ppr (x4 = 512). <ref>https://forum.protospace.ca/t/cnc-router-acting-funny/243/29</ref> That part of the system is “closed loop”. | ||
However, Mach3 doesn’t know if the servo kept up or not and if the machine is in the expected position. The servo driver knows if it went as far as it was commanded, but if the discrepancy gets too large, all it can do is raise an error signal or shut down the driver. When this happens | However, Mach3 doesn’t know if the servo kept up or not and if the machine is in the expected position. The servo driver knows if it went as far as it was commanded, but if the discrepancy gets too large, all it can do is raise an error signal or shut down the driver. When this happens, the "machine" no longer knows where it is and must be rehomed (Ref All) to the limit switches. | ||
| | | | ||
|- | |- | ||
| Line 230: | Line 230: | ||
==Troubleshooting== | ==Troubleshooting== | ||
===== "Logon method is not allowed on this computer" when trying to sign in to the computer with your Protospace username and password ===== | |||
Your account is not authorized/enabled to use this machine, have you taken the training? Did you pay for, attend on time and pass/participate in the training? Were you vetted at the time that you took your training? Did the instructor mark you as Attended? Please [https://my.protospace.ca/training verify your training records on Spaceport] and check in on the forums to update your account. | Your account is not authorized/enabled to use this machine, have you taken the training? Did you pay for, attend on time and pass/participate in the training? Were you vetted at the time that you took your training? Did the instructor mark you as Attended? Please [https://my.protospace.ca/training verify your training records on Spaceport] and check in on the forums to update your account. | ||
===== "ESS did not respond to wakeup message" Dialog box appears when starting Mach3. ===== | |||
This usually means the large black controller box for the machine is turned off, or did not have enough time to start before starting Mach3. | This usually means the large black controller box for the machine is turned off, or did not have enough time to start before starting Mach3. | ||
===== Spindle refuses to spin ===== | |||
VFD (Variable Frequency Drive motor driver - big controller box on the floor) overheated/off/tripped/reset? Power cycle with red switch next to floor. | VFD (Variable Frequency Drive motor driver - big controller box on the floor) overheated/off/tripped/reset? Power cycle with red switch next to floor. | ||
===== Mach3 errors, gantry refuses to home/move ===== | |||
Power is on and e-stops are out? | Power is on and e-stops are out? | ||
| Line 246: | Line 246: | ||
Did someone not log out properly and Mach3 has the port locked under another user? Try rebooting the PC. | Did someone not log out properly and Mach3 has the port locked under another user? Try rebooting the PC. | ||
===== Trying to use the Z probe and the machine dive-crashes into the table at 100mph ===== | |||
Well, don't do that. Something about the probe screen/script being lame and leaving the machine in the wrong units, from step 6 in quick start above: | Well, don't do that. Something about the probe screen/script being lame and leaving the machine in the wrong units, from step 6 in quick start above: | ||
6) Zero the Z axis using a piece of paper and ‘INCR” jog mode, or Z-PROBE. If using Z probe, first check probe speeds and distances in the probing screen. **Mach3 starts in INCH mode but the probe settings are whatever the last person left them at** Make sure you change the tool number to 99 before probing. Change the tool number to 1 or 0 after probing. | 6) Zero the Z axis using a piece of paper and ‘INCR” jog mode, or Z-PROBE. If using Z probe, first check probe speeds and distances in the probing screen. **Mach3 starts in INCH mode but the probe settings are whatever the last person left them at** Make sure you change the tool number to 99 before probing. Change the tool number to 1 or 0 after probing. | ||
===== Ethernet SmoothStepper ran out of data in the middle of a move ===== | |||
Briefly, run your file from the hard drive, and when your job is running don't mess with the computer. | |||
* '''Best Practices''' | |||
** Make sure your GCode is running from the hard drive. Never run GCode from a network drive or a USB stick, at some point, there will be a pause while trying to access the data and the ESS will run out of data! | |||
** Don't switch screens or applications while running GCode | |||
** Try not to zoom, pan / orbit the view port (3D preview) while code is running | |||
** Don't refresh your tool path while running GCode | |||
** Close all other software when running Mach3 (so they won't consume RAM or CPU time) | |||
======You can help expand this list by hopefully not breaking the Precix too badly! | * '''Advanced Options''' (consult with the Protospace local Precix experts before changing hardware/firmware settings) | ||
** Replace platter HDDs with SSDs | |||
** Run [https://warp9td.com/index.php/faq/faq-windows#HigherPriorityLevel Mach3 at a higher priority level]. This is done in the SCU's Windows Performance Tuning | |||
** Make sure that the [https://warp9td.com/index.php/faq/faq-mach3#MachThreeControllerFreq Controller Frequency] is set to a reasonable value. | |||
** Warp9 reports that electronic noise or ground loops from the dust collection or VFD may cause issues | |||
** Do an air cut and check how hard the CPU and RAM are working. If the computer is struggling, pitch an upgrade on the forum! | |||
For more details: [https://warp9td.com/index.php/faq/faq-mach3#RanOutOfData https://warp9td.com/index.php/faq/faq-mach3#MachThreeControllerFreq] | |||
===== The machine has lost its way ===== | |||
The driver/encoders can lose sync with Mach3 under the following conditions:<ref>https://warp9td.com/index.php/faq/faq-mach3#DROs</ref> | |||
* Mechanical Backlash (root cause is hardware) | |||
* Incorrectly configured Software Backlash Compensation settings | |||
* Pressing the physical E-Stop button while motion is in progress | |||
* Pressing the Mach software <code>Stop</code> button while motion is in progress | |||
* Improperly tuned acceleration or velocity settings that cause slippage on an axis | |||
* Power was removed from the motor drivers, and the axes drifted or moved from their set position | |||
===== You can help expand this list by hopefully not breaking the Precix too badly! ===== | |||
<nowiki>:</nowiki>D<br /> | <nowiki>:</nowiki>D<br /> | ||