I am not able to achieve much speed before the steppers lock up or growl on my
Cartesian clay printer.
Arthur suggested this is caused by resonance. But after reading the thread about Simplify 3d which I was using I thought maybe bad G-code was the problem.
But it seems to happen almost as frequently with Repetier slicer. I don't think its resonance because I can travel at higher rates of speed and some prints will run fast with no problem but other prints will get halfway through and then start to lock up and growl like a bear.
Here's is some of my settings.
default_feed_rate 750 # Default rate ( mm/minute ) for G1/G2/G3 moves
default_seek_rate 750 # Default rate ( mm/minute ) for G0 moves
mm_per_arc_segment .5 # Arcs are cut into segments ( lines ), this is the length
# these segments. Smaller values mean more resolution,
# higher values mean faster computation
mm_per_line_segment 5 # Lines can be cut into segments ( not usefull with cartesian
# coordinates robots ).
# Arm solution configuration : Cartesian robot. Translates mm positions into stepper positions
alpha_steps_per_mm 2200 # Steps per mm for alpha stepper
beta_steps_per_mm 2200 # Steps per mm for beta stepper
gamma_steps_per_mm 2200 # Steps per mm for gamma stepper
# Planner module configuration : Look-ahead and acceleration configuration
planner_queue_size 32 # DO NOT CHANGE THIS UNLESS YOU KNOW EXACTLY WHAT YOU ARE DOING
acceleration 50 # Acceleration in mm/second/second.
#z_acceleration 500 # Acceleration for Z only moves in mm/s^2, 0 uses acceleration which is the default. DO NOT SET ON A DELTA
acceleration_ticks_per_second 1000 # Number of times per second the speed is updated 1000/50
junction_deviation 0.005 # Similar to the old "max_jerk", in millimeters,.
# see https://github.com/grbl/grbl/blob/master/planner.c
# and https://github.com/grbl/grbl/wiki/Configuring-Grbl-v0.8
# Lower values mean being more careful, higher values means being
# faster and have more jerk
#z_junction_deviation 0.0 # for Z only moves, -1 uses junction_deviation, zero disables junction_deviation on z moves DO NOT SET ON A DELTA
#minimum_planner_speed 0.0 # sets the minimum planner speed in mm/sec
# Stepper module configuration
microseconds_per_step_pulse 1 # Duration of step pulses to stepper drivers, in microseconds .
base_stepping_frequency 100000 # Base frequency for stepping, higher gives smoother movement
# Cartesian axis speed limits
x_axis_max_speed 750 # mm/min
y_axis_max_speed 750 # mm/min
z_axis_max_speed 250 # mm/min
The only way I can get any speed at all is by lowering the acceleration way down and lowering the jerk number substantially. I sure could use some help trying to work through these problems.
Mark
when I increase the acceleration and junction deviation it only gets worse
Triffid
I've included the specifications for the NEMA23, any comments
Adam
are you suggesting changing the wire order going into the stepper motor, I've never heard of this before.
--
You received this message because you are subscribed to the Google Groups "Smoothieware Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to smoothieware-sup...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Arthur I'm driving directly off of the smoothieboard
alpha_current 2.0 # X stepper motor current
power supply 24 volts. Look at the my last post for the motor information chart
--
You received this message because you are subscribed to the Google Groups "Smoothieware Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to smoothieware-sup...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Smoothieware Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to smoothieware-sup...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
To unsubscribe from this group and stop receiving emails from it, send an email to smoothieware-support+unsub...@googlegroups.com.
Yes, the current limit is dictated entirely by heat.
There's an unavoidable thermal resistance between the silicon and the PCB which sets a hard upper limit depending on ambient temperature, but the more efficiently we can suck heat away with the PCB, the closer we can approach that hard limit - asymptotically of course.
As wolfmanjm says, the entire smoothieboard is a colossal heatsink which greatly exceeds the recommended heatsink requirements in the chip's datasheet , and as a result the limitations and examples listed therein aren't entirely valid.
Real world testing is always more useful than guesstimates from numbers in the datasheet, and indeed we have wide verification that with smoothieboard's epic thermal design (which I'm super proud of) we really can push these chips all the way to their absolute maximum.
The stepper drivers have built-in thermal overload protection, and to my knowledge we have zero reports of it ever kicking in at 2A or less.
The trouble with the daughter board drivers popularised by other electronics is that the heatsink area and access to free moving air is rather less than the requirements in the datasheet - not only does this mean that the drivers overheat at a measly 1A, but the insufficient thermal mass also renders the thermal overload protection less effective than it should be.
Furthermore, I'm firmly convinced that a significant proportion of the daughterboard driver death rate is caused by having them on headers - small spring contacts coupled with moderate currents and lots of vibration is a perfect recipe for intermittent poor contact, noise, inductive kicks, ohmic hot spotting and other electrical effects well known to rapidly destroy chips.
Ironically, the very nature of making the drivers easily replaceable causes them to be replaced often.
On smoothieboard, the drivers simply do not overheat, and do not randomly die at anywhere near the rate reported by the wider reprap community for daughterboard drivers - Our minuscule driver failure rate (excluding user errors) seems to be comparable to a reasonable expectation of unavoidable manufacturing defects.
Of course, silicon degrades rapidly near it's maximum temperature and heat is proportional to square of current, so if the thermal overload protection doesn't kick in at 2A the drivers should last almost forever at 1.5A.
The only downside of smoothie's thermal design is that it's difficult to impossible to rework with a normal soldering iron - hot air is critical.
Paul that some good advice. I decided to increase my pitch on the lead screw and at least it keeps me away from the problem rpm. So if I understand correctly going to .9 degree motor also helps. I'm trying to stay away from Digital stepper driver because of the added expense and complexity.