Motors moving too fast

Home › Forums › TinyG › TinyG Support › Motors moving too fast

Viewing 9 posts - 1 through 9 (of 9 total)
  • Author
    Posts
  • August 25, 2015 at 12:11 pm #8668
    tumulte
    Member

    Hello. I’m very new so please bear with me. I put together a router using Nema 23’s for the X/Y. Things were working well for a while, but I felt like the motors were giving me issues. So I upgraded to a 480oz nema 23. After the upgrade I also updated the firmware on the tinyg and got the new json server running. Since then I have had a lot of problems. There is a lot of lag between jogging and the machine actually moving, but not the end of the world.

    I got everything working finally and cut a project but noticed that when the machine was moving between cuts it was moving at a rate of 2ipm. Before I updated I never had this issue. In an attempt to fix the issue I changed some settings and now my machine tries to fly when jogging and when starting a job, about 1000ipm and when it does that it binds up. It is still moving at 2 ipm between cuts. I have a video of what it is doing when I say “Binding up” but don’t know how to upload it. Basically if I try to tell it to move more than 4-5 inches it’ll move the initial 5 inches then bind up and stop.

    Other issues are settings not saving to the board correctly and things of that nature. I’m running the latest FW.

    Please help!

    August 25, 2015 at 8:42 pm #8671
    cmcgrath5035
    Moderator

    Need to see your parameters:

    Please be very specific when your report in, Versions sometimes change on an hourly basis.

    SPJS 1.83?
    Your parameter dump will provide $fw
    Jogging should be ~instantaneous, so lag is not the end of the world but is an indicator of problem(s)

    August 26, 2015 at 10:43 pm #8675
    tumulte
    Member

    Sorry, I don’t have a dropbox account and didn’t have time to make one, so here is the dump. I’m also using json 1.83

    [fb] firmware build 440.18
    [fv] firmware version 0.97
    [hp] hardware platform 1.00
    [hv] hardware version 8.00
    [id] TinyG ID 3X3566-2VX
    [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 59.7510 mm
    [1mi] m1 microsteps 8 [1,2,4,8]
    [1po] m1 polarity 0 [0=normal,1=reverse]
    [1pm] m1 power management 3 [0=disabled,1=always on,2=in cycle,3=when moving]
    [2ma] m2 map to axis 2 [0=X,1=Y,2=Z…]
    [2sa] m2 step angle 1.800 deg
    [2tr] m2 travel per revolution 8.0010 mm
    [2mi] m2 microsteps 4 [1,2,4,8]
    [2po] m2 polarity 1 [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 1 [0=X,1=Y,2=Z…]
    [3sa] m3 step angle 1.800 deg
    [3tr] m3 travel per revolution 59.7510 mm
    [3mi] m3 microsteps 8 [1,2,4,8]
    [3po] m3 polarity 0 [0=normal,1=reverse]
    [3pm] m3 power management 3 [0=disabled,1=always on,2=in cycle,3=when moving]
    [4ma] m4 map to axis 1 [0=X,1=Y,2=Z…]
    [4sa] m4 step angle 1.800 deg
    [4tr] m4 travel per revolution 59.7510 mm
    [4mi] m4 microsteps 8 [1,2,4,8]
    [4po] m4 polarity 1 [0=normal,1=reverse]
    [4pm] m4 power management 3 [0=disabled,1=always on,2=in cycle,3=when moving]
    [xam] x axis mode 1 [standard]
    [xvm] x velocity maximum 16002 mm/min
    [xfr] x feedrate maximum 16002 mm/min
    [xtn] x travel minimum 0.000 mm
    [xtm] x travel maximum 762.000 mm
    [xjm] x jerk maximum 5004 mm/min^3 * 1 million
    [xjh] x jerk homing 51 mm/min^3 * 1 million
    [xjd] x junction deviation 0.0102 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 508 mm/min
    [xlv] x latch velocity 102 mm/min
    [xlb] x latch backoff 5.004 mm
    [xzb] x zero backoff 0.991 mm
    [yam] y axis mode 1 [standard]
    [yvm] y velocity maximum 16002 mm/min
    [yfr] y feedrate maximum 16002 mm/min
    [ytn] y travel minimum 0.000 mm
    [ytm] y travel maximum 1270.000 mm
    [yjm] y jerk maximum 5004 mm/min^3 * 1 million
    [yjh] y jerk homing 51 mm/min^3 * 1 million
    [yjd] y junction deviation 0.0102 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 508 mm/min
    [ylv] y latch velocity 102 mm/min
    [ylb] y latch backoff 5.004 mm
    [yzb] y zero backoff 0.991 mm
    [zam] z axis mode 1 [standard]
    [zvm] z velocity maximum 1600 mm/min
    [zfr] z feedrate maximum 1600 mm/min
    [ztn] z travel minimum 0.000 mm
    [ztm] z travel maximum 75.006 mm
    [zjm] z jerk maximum 508 mm/min^3 * 1 million
    [zjh] z jerk homing 51 mm/min^3 * 1 million
    [zjd] z junction deviation 0.0102 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 406 mm/min
    [zlv] z latch velocity 102 mm/min
    [zlb] z latch backoff 5.004 mm
    [zzb] z zero backoff 0.991 mm
    [aam] a axis mode 3 [radius]
    [avm] a velocity maximum 0 deg/min
    [afr] a feedrate maximum 230400 deg/min
    [atn] a travel minimum-1831631800000000000.000 deg
    [atm] a travel maximum -1.000 deg
    [ajm] a jerk maximum 10973 deg/min^3 * 1 million
    [ajh] a jerk homing 16129 deg/min^3 * 1 million
    [ajd] a junction deviation 0.0500 deg (larger is faster)
    [ara] a radius value 0.0000 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.099 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>

    August 27, 2015 at 8:48 am #8676
    cmcgrath5035
    Moderator

    What follows is a somewhat ‘painful’ procedure, but I think you need it.

    I am bothered by some of your parameter values.
    Look at

    [xam] x axis mode 1 [standard]
    [xvm] x velocity maximum 16002 mm/min
    [xfr] x feedrate maximum 16002 mm/min
    [xtn] x travel minimum 0.000 mm
    [xtm] x travel maximum 762.000 mm
    [xjm] x jerk maximum 5004 mm/min^3 * 1 million
    [xjh] x jerk homing 51 mm/min^3 * 1 million
    [xjd] x junction deviation 0.0102 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 508 mm/min
    [xlv] x latch velocity 102 mm/min
    [xlb] x latch backoff 5.004 mm
    [xzb] x zero backoff 0.991 mm

    I see no good reason why you would have , for example, $xjerk to 5004 mm/mm^3 rather than 5000.
    Many of your parameters have this dangling precision that is just not normal, and indicative of parameter corruption.
    Unless you can explain these values, I suggest the following:

    1. Reset (the button) tinyG
    2. Connect via CoolTerm or CP.
    3 On the command line, enter $defa=1
    This will reset ALL your parameters to a set of defaults that are not useful on your machine, so you will need to reenter them.
    I recommend you do this one parameter at a time via the command line or the SP Command window, not the configuretinyG widget on CP
    Make sure your machine is in mm mode (not inch) when you make the parameter entries.
    Make a print out of your $$ dump BEFORE you do this, so you can follow along resetting your parameters.
    Other than $nTR values, which need to be tweaked for best movement precision, parameters should be ‘nice roundish numbers’.
    So, $1tr=59.7510 mm is understandable, but $xjm=5004 looks bogus.

    I’ll comment that we have seen this before, this procedure usually corrects it, but there is not good understanding how it happened.

    August 28, 2015 at 8:40 am #8679
    tumulte
    Member

    Thanks for the input! I have been curious about those as well. When I entered them, I was using the widget and not command line, but I put the rounded value and later it changed to having the number on the tail end without any input from me. I’ll follow your suggestion this weekend and see what happens. Do you think any of this would cause the motors to move so fast? I’ll see if I can get a dropbox set up and load a video of the machine and what it’s doing when trying to jog.

    Thanks again

    August 28, 2015 at 11:04 am #8680
    cmcgrath5035
    Moderator

    Do you think any of this would cause the motors to move so fast? I’ll see if I can get a dropbox set up and load a video of the machine and what it’s doing when trying to jog.

    Maybe, depend if whatever is causing 5000 to become 5004 (etc) is causing other parameter issues.

    I believe CP jogs at G0 speed

    You can compare
    G0 X30Y30
    to
    G1 X30Y30 F800

    Maybe G0 speed is just ‘fast’ to you”
    that would be $xvm=16002, if we trust that value.

    I highly recommend the $defa=1 procedure.
    Enter parameters via CoolTerm or the Serial port console.

    August 28, 2015 at 12:09 pm #8683
    cmcgrath5035
    Moderator

    Read This: https://plus.google.com/+FlorianSeffert/posts/eW3Yio7DChf

    August 31, 2015 at 11:29 am #8687
    tumulte
    Member

    Hey I just wanted to let you know that I went through the procedure you recommended. I also downgraded to spjs 1.80 and jogging was immediately lag free. It responded almost instantaneously when jogging. I also reset all parameters and entered them manually and the motors are moving at a much more reasonable speed without binding up. I haven’t cut anything just but I think it’s going to be fine. Thank you so much for your help!

    August 31, 2015 at 10:01 pm #8690
    cmcgrath5035
    Moderator

    Good news.
    Keep an eye out for SPJS >1.83, I know John is close to releasing a fix

  • Author
    Posts
Viewing 9 posts - 1 through 9 (of 9 total)
  • You must be logged in to reply to this topic.