Home › Forums › TinyG › TinyG Support › tinyg Stepper motors hum and do not move
- This topic has 7 replies, 3 voices, and was last updated 8 years ago by cmcgrath5035.
-
AuthorPosts
-
November 30, 2016 at 11:47 pm #10038hlfshellMember
I setup a new tinyg with the following setup, but only get motor humming. After a couple of attempts to move the motor, chilipeppr or tinyg does not receive commands anymore, though the serial port on the computer odes not drop.
Power supply – 24V 14.6A
Motors: NEMA 23 345oz/in 3A max phase
Motors are definitely plugged in right via the wire pairing trick.Here is my $$:
$$
{“ej”:””}
[fb] firmware build 440.20
[fv] firmware version 0.97
[hp] hardware platform 1.00
[hv] hardware version 8.00
[id] TinyG ID 3Y2462-VGZ
[ja] junction acceleration 100000 mm
[ct] chordal tolerance 0.0100 mm
[sl] soft limit enable 0
[st] switch type 0 [0=NO,1=NC]
[mt] motor idle timeout 2.00 Sec
[ej] enable json mode 0 [0=text,1=JSON]
[jv] json verbosity 4 [0=silent,1=footer,2=messages,3=configs,4=linenum,5=verbose]
[js] json serialize style 1 [0=relaxed,1=strict]
[tv] text verbosity 1 [0=silent,1=verbose]
[qv] queue report verbosity 1 [0=off,1=single,2=triple]
[sv] status report verbosity 1 [0=off,1=filtered,2=verbose]
[si] status interval 250 ms
[ec] expand LF to CRLF on TX 0 [0=off,1=on]
[ee] enable echo 0 [0=off,1=on]
[ex] enable flow control 1 [0=off,1=XON/XOFF, 2=RTS/CTS]
[baud] USB baud rate 5 [1=9600,2=19200,3=38400,4=57600,5=115200,6=230400]
[net] network mode 0 [0=master]
[gpl] default gcode plane 0 [0=G17,1=G18,2=G19]
[gun] default gcode units mode 1 [0=G20,1=G21]
[gco] default gcode coord system 1 [1-6 (G54-G59)]
[gpa] default gcode path control 2 [0=G61,1=G61.1,2=G64]
[gdi] default gcode distance mode 0 [0=G90,1=G91]
[1ma] m1 map to axis 0 [0=X,1=Y,2=Z…]
[1sa] m1 step angle 1.800 deg
[1tr] m1 travel per revolution 1.2500 mm
[1mi] m1 microsteps 8 [1,2,4,8]
[1po] m1 polarity 0 [0=normal,1=reverse]
[1pm] m1 power management 2 [0=disabled,1=always on,2=in cycle,3=when moving]
[2ma] m2 map to axis 1 [0=X,1=Y,2=Z…]
[2sa] m2 step angle 1.800 deg
[2tr] m2 travel per revolution 1.2500 mm
[2mi] m2 microsteps 8 [1,2,4,8]
[2po] m2 polarity 0 [0=normal,1=reverse]
[2pm] m2 power management 2 [0=disabled,1=always on,2=in cycle,3=when moving]
[3ma] m3 map to axis 2 [0=X,1=Y,2=Z…]
[3sa] m3 step angle 1.800 deg
[3tr] m3 travel per revolution 1.2500 mm
[3mi] m3 microsteps 8 [1,2,4,8]
[3po] m3 polarity 0 [0=normal,1=reverse]
[3pm] m3 power management 2 [0=disabled,1=always on,2=in cycle,3=when moving]
[4ma] m4 map to axis 3 [0=X,1=Y,2=Z…]
[4sa] m4 step angle 1.800 deg
[4tr] m4 travel per revolution 360.0000 mm
[4mi] m4 microsteps 8 [1,2,4,8]
[4po] m4 polarity 0 [0=normal,1=reverse]
[4pm] m4 power management 2 [0=disabled,1=always on,2=in cycle,3=when moving]
[xam] x axis mode 1 [standard]
[xvm] x velocity maximum 800 mm/min
[xfr] x feedrate maximum 800 mm/min
[xtn] x travel minimum 0.000 mm
[xtm] x travel maximum 150.000 mm
[xjm] x jerk maximum 20 mm/min^3 * 1 million
[xjh] x jerk homing 40 mm/min^3 * 1 million
[xjd] x junction deviation 0.0500 mm (larger is faster)
[xsn] x switch min 1 [0=off,1=homing,2=limit,3=limit+homing]
[xsx] x switch max 0 [0=off,1=homing,2=limit,3=limit+homing]
[xsv] x search velocity 500 mm/min
[xlv] x latch velocity 100 mm/min
[xlb] x latch backoff 5.000 mm
[xzb] x zero backoff 1.000 mm
[yam] y axis mode 1 [standard]
[yvm] y velocity maximum 800 mm/min
[yfr] y feedrate maximum 800 mm/min
[ytn] y travel minimum 0.000 mm
[ytm] y travel maximum 150.000 mm
[yjm] y jerk maximum 20 mm/min^3 * 1 million
[yjh] y jerk homing 40 mm/min^3 * 1 million
[yjd] y junction deviation 0.0500 mm (larger is faster)
[ysn] y switch min 1 [0=off,1=homing,2=limit,3=limit+homing]
[ysx] y switch max 0 [0=off,1=homing,2=limit,3=limit+homing]
[ysv] y search velocity 500 mm/min
[ylv] y latch velocity 100 mm/min
[ylb] y latch backoff 5.000 mm
[yzb] y zero backoff 1.000 mm
[zam] z axis mode 1 [standard]
[zvm] z velocity maximum 800 mm/min
[zfr] z feedrate maximum 800 mm/min
[ztn] z travel minimum 0.000 mm
[ztm] z travel maximum 75.000 mm
[zjm] z jerk maximum 20 mm/min^3 * 1 million
[zjh] z jerk homing 40 mm/min^3 * 1 million
[zjd] z junction deviation 0.0500 mm (larger is faster)
[zsn] z switch min 0 [0=off,1=homing,2=limit,3=limit+homing]
[zsx] z switch max 1 [0=off,1=homing,2=limit,3=limit+homing]
[zsv] z search velocity 400 mm/min
[zlv] z latch velocity 100 mm/min
[zlb] z latch backoff 5.000 mm
[zzb] z zero backoff 1.000 mm
[aam] a axis mode 3 [radius]
[avm] a velocity maximum 230400 deg/min
[afr] a feedrate maximum 230400 deg/min
[atn] a travel minimum -1.000 deg
[atm] a travel maximum -1.000 deg
[ajm] a jerk maximum 5760 deg/min^3 * 1 million
[ajh] a jerk homing 11520 deg/min^3 * 1 million
[ajd] a junction deviation 0.0500 deg (larger is faster)
[ara] a radius value 0.1989 deg
[asn] a switch min 1 [0=off,1=homing,2=limit,3=limit+homing]
[asx] a switch max 0 [0=off,1=homing,2=limit,3=limit+homing]
[asv] a search velocity 600 deg/min
[alv] a latch velocity 100 deg/min
[alb] a latch backoff 5.000 deg
[azb] a zero backoff 2.000 deg
[bam] b axis mode 0 [disabled]
[bvm] b velocity maximum 3600 deg/min
[bfr] b feedrate maximum 3600 deg/min
[btn] b travel minimum -1.000 deg
[btm] b travel maximum -1.000 deg
[bjm] b jerk maximum 20 deg/min^3 * 1 million
[bjd] b junction deviation 0.0500 deg (larger is faster)
[bra] b radius value 1.0000 deg
[cam] c axis mode 0 [disabled]
[cvm] c velocity maximum 3600 deg/min
[cfr] c feedrate maximum 3600 deg/min
[ctn] c travel minimum -1.000 deg
[ctm] c travel maximum -1.000 deg
[cjm] c jerk maximum 20 deg/min^3 * 1 million
[cjd] c junction deviation 0.0500 deg (larger is faster)
[cra] c radius value 1.0000 deg
[p1frq] pwm frequency 100 Hz
[p1csl] pwm cw speed lo 1000 RPM
[p1csh] pwm cw speed hi 2000 RPM
[p1cpl] pwm cw phase lo 0.125 [0..1]
[p1cph] pwm cw phase hi 0.200 [0..1]
[p1wsl] pwm ccw speed lo 1000 RPM
[p1wsh] pwm ccw speed hi 2000 RPM
[p1wpl] pwm ccw phase lo 0.125 [0..1]
[p1wph] pwm ccw phase hi 0.200 [0..1]
[p1pof] pwm phase off 0.100 [0..1]
[g54x] g54 x offset 0.000 mm
[g54y] g54 y offset 0.000 mm
[g54z] g54 z offset 0.000 mm
[g54a] g54 a offset 0.000 deg
[g54b] g54 b offset 0.000 deg
[g54c] g54 c offset 0.000 deg
[g55x] g55 x offset 75.000 mm
[g55y] g55 y offset 75.000 mm
[g55z] g55 z offset 0.000 mm
[g55a] g55 a offset 0.000 deg
[g55b] g55 b offset 0.000 deg
[g55c] g55 c offset 0.000 deg
[g56x] g56 x offset 0.000 mm
[g56y] g56 y offset 0.000 mm
[g56z] g56 z offset 0.000 mm
[g56a] g56 a offset 0.000 deg
[g56b] g56 b offset 0.000 deg
[g56c] g56 c offset 0.000 deg
[g57x] g57 x offset 0.000 mm
[g57y] g57 y offset 0.000 mm
[g57z] g57 z offset 0.000 mm
[g57a] g57 a offset 0.000 deg
[g57b] g57 b offset 0.000 deg
[g57c] g57 c offset 0.000 deg
[g58x] g58 x offset 0.000 mm
[g58y] g58 y offset 0.000 mm
[g58z] g58 z offset 0.000 mm
[g58a] g58 a offset 0.000 deg
[g58b] g58 b offset 0.000 deg
[g58c] g58 c offset 0.000 deg
[g59x] g59 x offset 0.000 mm
[g59y] g59 y offset 0.000 mm
[g59z] g59 z offset 0.000 mm
[g59a] g59 a offset 0.000 deg
[g59b] g59 b offset 0.000 deg
[g59c] g59 c offset 0.000 deg
[g92x] g92 x offset 0.000 mm
[g92y] g92 y offset 0.000 mm
[g92z] g92 z offset 0.000 mm
[g92a] g92 a offset 0.000 deg
[g92b] g92 b offset 0.000 deg
[g92c] g92 c offset 0.000 deg
[g28x] g28 x position 0.000 mm
[g28y] g28 y position 0.000 mm
[g28z] g28 z position 0.000 mm
[g28a] g28 a position 0.000 deg
[g28b] g28 b position 0.000 deg
[g28c] g28 c position 0.000 deg
[g30x] g30 x position 0.000 mm
[g30y] g30 y position 0.000 mm
[g30z] g30 z position 0.000 mm
[g30a] g30 a position 0.000 deg
[g30b] g30 b position 0.000 deg
[g30c] g30 c position 0.000 deg
tinyg [mm] ok>When chilipepper/tinyg stops responding after a couple of attempts, I have to fully reset tinyg and the serial json console in order to get it working again.
Thinking it might be a current issue, I have carefully adjusted the current pots to its max by going clockwise.
I have switched out a NEMA 23 with a much smaller NEMA 17 – and still have the same issues.
I’m at a bit of a loss here on what to do.
December 1, 2016 at 1:55 am #10039ZootalawsMemberHumming would indicate a lack of current. The range of motion of the adjuster is from approx 8 o’clock to 4 o’clock, so around 270degrees. You shouldn’t need to turn further than 1-2 o’clock to get things moving. If you have turned it past 4 o’clock, there’s a reasonable chance you’ve broken your adjuster.
Did you use a voltmeter to confirm? . Did you follow this document? https://github.com/synthetos/TinyG/wiki/TinyG-Tuning
- This reply was modified 8 years ago by Zootalaws.
December 1, 2016 at 5:39 am #10041cmcgrath5035Moderatorhlfshell – Please copy your $$ dump to a cloud file (dropbox, gdrive, etc.) and post a URL here – much easier to read.
You parameter look a bit strange to me.
They show X,Y,Z and A axis all active, with same $_tr = 1.25mm, which sort of says you have a 4 axis screw machine. Is that correct?
We don’t see many 4 axis screw machines here, but of course they exist.Are you able to manually rotate any of the axes?
It is possible that your ballscrew bearings are adjusted too tight.To debug, you could mechanically disconnect a motor, say the Z axis motor, then see if a jog or G0 Z10 command will spin the stepper.
Note that with $mt=2 secs, all motors should energize at their current position(and hum) for 2 seconds after hitting tinyG reset, then go to standby low power mode(nohum).
If you have a Voltmeter, also check that 24V remains solid during the reset process. We have seen some supplies with defective current limiters drop output voltage when loaded.
When you report back, also describe your control computer.
Windows/Mac/Linux?
Running SPJS (version = ?) on same machine?
Also note that tinyG has an onboard hardware termination for the USB link – an FTDI device. So you computer may report seeing the USB link UP even when tinyG FW is not running or has crashed. And, the FTDI device has been known to look ‘sane’ to a connected PC when it is powered by much less than 3.3v, its normal Vcc.December 1, 2016 at 5:51 am #10042cmcgrath5035ModeratorAnd, what ‘move’ are you attempting? Try jogs of at least 1mm per click.
It’s possible to configure CP to joog .01 or .001mm, which don’t always generate motion.
I don’t think that is your problem, because such a move request would just be accumulated, not cause tinyG to crash.December 1, 2016 at 10:51 am #10043hlfshellMember@zootalaws – I have not done that tuning yet. I certainly hope I ahve no broken it – I haven to done anything with the board besides carefully plug it in and attempt this one jog move. I have not followed that document but will try so when I can tonight and report back to you.
On the question of the voltmeter – I have confirmed a steady 24 volts out on the power supply, before and during the motors being ran. I see no spikes. What else should I be checking with the voltmeter?
@cmcgrath5035 – Here is the requested reposting of the $$ http://pastebin.com/raw/fhxJ3LyAMy control computer is Windows 10, running SPJS on the same machine – version serial-port v1.92. I’m doing everything through Chilipeppr w/ tinyg.
I am attempting a jog of .1 mm, though have also ran commands like g1 f400 x50 – and nothing happens, though it does hum for the length of time that chilipeppr thinks its moving.
It is a 3 axis screw machine – I simply haven’t dont any config settings within the tiny-g so far and was just trying to move an individual motor. The NEMA 23 I tested is attached to the machine – the x-axis – the NEMA 17 I tested is just a floating motor, nothing attached. So I have tested the motors free floating.
I don’t think it’s mechanical. I can easily move the screws when the motor is unpowered to slowly but surely move the axis across.
As you can see above, I have shown that the 24V out is steady through the attempt to move the motors, though I will try it during the reset process as well.
December 2, 2016 at 9:50 pm #10044hlfshellMemberI have done more work on trying to debug this situation and am no further. I am still unable to move a motor and, after attempting to move the motors, need to completely reset the tinyg in order to get it to respond to me again.
I have done the following since my last post:
1. Slowly changed the current
2. Experimented with different feed and traversal rates
3. Switched to and fro inches/milimeter in case there was a command that was way off due to unit confusion
4. Checked the power supply again – in fact, it’s the power supply recommended in one of the wiki pages, found here: http://openbuildspartstore.com/24v-14-6a-power-supply/
5. Measured current during motor being ran by placing the voltmeter in series with the ground wire on the tinyg’s power supply. Running one motor, WHETHER it’s NEMA17 or 23, pulls .6A – which is low. Then the freeze occurs.I really don’t want to have to purchase another $130 on a control board when the tinyg showed so much promise, but at this point I’m at a loss of where to go or what to try with the setup. Please help!
December 5, 2016 at 8:37 pm #10045hlfshellMemberWith the weekend over, I grabbed from work a stepper motor controller I had built for an older proejct earlier this year. It’s based around the big easy stepper driver, found here. This stepper driver is based around the Allegro A4988, a popular stepper driver.
I wired the controller up to the same motor and power supply I tested earlier. The controlled worked and the motor moved (until the higher amperage motors burned the driver – whoops!).
The motor did not move smoothly, so I am waiting until I have from ebay some 3A drivers to try and confirm whether the problem is the power supply or the tinyg – so far I’m leaning towards the problem being the tinyg. I still need help on this.
December 7, 2016 at 7:22 am #10046cmcgrath5035ModeratorUnfortunately, your experiments are not much help without more context.
For example, when you connected the A4988s, what commands did you send and from what control system?I assume you tried to measure current with the ammeter function of a VOM, not a voltmeter. That really won’t work, most of the current in these systems is narrow pulses that cannot be read with a Multimeter (VOM).
My best suggestion – mechanically disconnect one or all of your motors from the Machine, connect tinyG and use CP or Coolterm to send some moves to spin each motor. Report results.
-
AuthorPosts
- You must be logged in to reply to this topic.