Motor buzzes during the movement and stops until the next z movement.
Maybe im wrong (others please feel to correct me) but this indicates to me that the controller at least thinks it got close enough to the gcode setpoint and stops trying to move the Z.
Shooting in the dark here.
Is it a z axis speed/time thing? Is there a time limit that the program allows the z to move and if it’s close to the depth by a certain % at the end of x time, then it stops and continues with the cuts? Does the z axis need to move faster to reach this depth before time runs out?
1 Like
Darn, it sounds like you already tested the PID settings as a culprit…sorry I missed that.
Yes! This is set in your gcode. Usually the feedrate for the z-axis and XY axis are set separately when generating the gcode
wait, so if the time limit is exceeded the controller just says “close enough” and stops?
Ideas for my next steps?
What’s a good z axis feed rate?
I’m going to switch over from WC to Makerverse to see if the problem follows.
Again, thanks for all the help.
-Tim
thanks for sticking with it for as long as you have.
i typically use 2 in/min as my plunge feed rate
Increasing my plunge rate did not fix it.
Trying to get makerverse working but I have to install 51.28 firmware (have 51.27) can’t figure out how to do it. Arduino IDE won’t load the hex file
If you move the 51.30 firmware from the newer webcontrol folder into the older webcontrol firmware folder then webcontrol can flash it for you.
Arduino ide will make the hex file for you and then load it.
That worked, thx
Got makerverse up and going however, the gcode pauses for tool change and the message pops up to hit the resume but I cannot find the resume button anywhere
Manually removed the tool change from the gcode and ran it in makerverse. Still have the same problem.
I’m pretty sure that this is a problem in the firmware, where the problem is I
don’t know.
As you changed the PID settings, (increasing the P value) did the amount of
error change? does it continue to drift off over time as you repeat the same
movement?
David Lang
is the error the same no matter what the feed rate is? try setting it very slow
and see if the same sort of error happens.
When changing the PID settings there was no change to the amount of error. I tried plunge rates of 8 in/min and 50in/min with no change. Should I slow down x/y feed rate, had it at 30 and 40.
I haven’t been able figure out how to run WC or Orobs version as a service on linux(I’m a newbie) dont know if this could prevent me from properly using the newly implemented z axis PID tuning. Also on Orobs version, It gives me an error when trying to install 51.30. Currently have .94 WC and 51.28 firmware (had 51.27).
Problem exists on windows and linux webcontrols and in makerverse.
Update, I copied the 51.30 from oRobs version and pasted in .94 WC and was able to successfully upload it. Still no luck, when playing with PID.
When changing the PID settings there was no change to the amount of error. I tried plunge rates of 8 in/min and 50in/min with no change. Should I slow down x/y feed rate, had it at 30 and 40.
Since we’re doing a test of just moving the Z axis, the X/Y feed rate should not
matter.
I think someone else mentioned that they ran their Z at 2 in/min. keep slowing
it down until the test takes 2x or 3x as long as it did when you started (and
possibly keep going and do a test where it takes 10x as long)
I haven’t been able figure out how to run WC or Orobs version as a service on
linux(I’m a newbie) dont know if this could prevent me from properly using the
newly implemented z axis PID tuning. Also on Orobs version, It gives me an
error when trying to install 51.30. Currently have .94 WC and 51.28 firmware
(had 51.27).
running it as a service as opposed to starting it manually won’t matter for
testing.
Problem exists on windows and linux webcontrols and in makerverse.
This makes me very sure that whatever the issue is, it’s in the firmware, not in
WC.
I doubt that the 51.30 firmware would help, but we need to get you to where you
can switch to a different firmware so that you can test fixes to the firmware
David Lang
I doubt that the 51.30 firmware would help, but we need to get you to where you can switch to a different firmware so that you can test fixes to the firmware
51.30 only has provisions for shield numbering supporting the TB series of chips as well as the z axis software limits and the spindle speed control via the shield own output.
If it’s in the firmware would others easily be able to duplicate my problem?
from what ive been able to follow, you have tried different firmware, depending on what control interface you were using. You started with the current WC and used the firmware that was bundled with it. You tried the @Orob development WC and used his modified firmware for it. You also tried makerverse and used the firmware that came with it. Am I understanding this correctly?