G0 traverses exceed $x/y/zvm speed

ictoamn Oct 9, 2014 #

Hello,
I just recently built an OX cnc and I'm using TinyG. I'm still in the process of tuning and learning. I have tried to slow down the z axis max velocity as the coupling is slipping when traveling around 30mm or more.

I set $zvm to slow it down but didn't notice a change in the g0 commands.
I can even set $zvm=25 mm/min and a g0 z30 runs faster than a g1 z30 f500

I checked to make sure the settings are saving and they are correctly storing the speeds I set.

I'm not sure if there's some other setting that is overriding the max velocity.
Any Help would be appreciated.

Thanks,
Chris

Here's my board settings...

[fb] firmware build 438.02
[fv] firmware version 0.97
[hp] hardware platform 1.00
[hv] hardware version 8.00
[id] TinyG ID 3X3566-JVY
[ja] junction acceleration nan mm
[ct] chordal tolerance 0.0100 mm
[sl] soft limit enable 0
[st] switch type 0 [0=NO,1=NC]
[mt] motor idle timeout 0.10 Sec
[ej] enable json mode 0 [0=text,1=JSON]
[jv] json verbosity 1 [0=silent,1=footer,2=messages,3=configs,4=linenum,5=verbose]
[js] json serialize style 1 [0=relaxed,1=strict]
[tv] text verbosity 0 [0=silent,1=verbose]
[qv] queue report verbosity 2 [0=off,1=single,2=triple]
[sv] status report verbosity 1 [0=off,1=filtered,2=verbose]
[si] status interval 100 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 0 [1-6 (G54-G59)]
[gpa] default gcode path control 0 [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 60.0000 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 60.0000 mm
[2mi] m2 microsteps 8 [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 60.0000 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 2 [0=X,1=Y,2=Z...]
[4sa] m4 step angle 1.800 deg
[4tr] m4 travel per revolution 8.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 600 mm/min
[xfr] x feedrate maximum 800 mm/min
[xtn] x travel minimum 0.000 mm
[xtm] x travel maximum-199384200000000000000000000000000000000.000 mm
[xjm] x jerk maximum 5000 mm/min^3 * 1 million
[xjh] x jerk homing 10000 mm/min^3 * 1 million
[xjd] x junction deviation 0.0100 mm (larger is faster)
[xsn] x switch min 0 [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 nan mm/min
[xlv] x latch velocity nan mm/min
[xlb] x latch backoff nan mm
[xzb] x zero backoff nan mm
[yam] y axis mode 1 [standard]
[yvm] y velocity maximum 300 mm/min
[yfr] y feedrate maximum 800 mm/min
[ytn] y travel minimum 0.000 mm
[ytm] y travel maximum 500.000 mm
[yjm] y jerk maximum 5000 mm/min^3 * 1 million
[yjh] y jerk homing 10000 mm/min^3 * 1 million
[yjd] y junction deviation 0.0100 mm (larger is faster)
[ysn] y switch min 0 [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 nan mm/min
[ylv] y latch velocity nan mm/min
[ylb] y latch backoff nan mm
[yzb] y zero backoff nan mm
[zam] z axis mode 1 [standard]
[zvm] z velocity maximum 25 mm/min
[zfr] z feedrate maximum 100 mm/min
[ztn] z travel minimum 0.000 mm
[ztm] z travel maximum 200.000 mm
[zjm] z jerk maximum 50 mm/min^3 * 1 million
[zjh] z jerk homing 1000 mm/min^3 * 1 million
[zjd] z junction deviation 0.0100 mm (larger is faster)
[zsn] z switch min 0 [0=off,1=homing,2=limit,3=limit+homing]
[zsx] z switch max 0 [0=off,1=homing,2=limit,3=limit+homing]
[zsv] z search velocity nan mm/min
[zlv] z latch velocity nan mm/min
[zlb] z latch backoff nan mm
[zzb] z zero backoff nan mm
[aam] a axis mode 0 [disabled]
[avm] a velocity maximum nan deg/min
[afr] a feedrate maximum nan deg/min
[atn] a travel minimum nan deg
[atm] a travel maximum nan deg
[ajm] a jerk maximum nan deg/min^3 * 1 million
[ajh] a jerk homing nan deg/min^3 * 1 million
[ajd] a junction deviation nan deg (larger is faster)
[ara] a radius value nan deg
[asn] a switch min 0 [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 nan deg/min
[alv] a latch velocity nan deg/min
[alb] a latch backoff nan deg
[azb] a zero backoff nan deg
[bam] b axis mode 0 [disabled]
[bvm] b velocity maximum nan deg/min
[bfr] b feedrate maximum nan deg/min
[btn] b travel minimum nan deg
[btm] b travel maximum nan deg
[bjm] b jerk maximum nan deg/min^3 * 1 million
[bjd] b junction deviation nan deg (larger is faster)
[bra] b radius value nan deg
[cam] c axis mode 0 [disabled]
[cvm] c velocity maximum nan deg/min
[cfr] c feedrate maximum nan deg/min
[ctn] c travel minimum nan deg
[ctm] c travel maximum nan deg
[cjm] c jerk maximum nan deg/min^3 * 1 million
[cjd] c junction deviation nan deg (larger is faster)
[cra] c radius value nan deg
[p1frq] pwm frequency nan Hz
[p1csl] pwm cw speed lo nan RPM
[p1csh] pwm cw speed hi nan RPM
[p1cpl] pwm cw phase lo nan [0..1]
[p1cph] pwm cw phase hi nan [0..1]
[p1wsl] pwm ccw speed lo nan RPM
[p1wsh] pwm ccw speed hi nan RPM
[p1wpl] pwm ccw phase lo nan [0..1]
[p1wph] pwm ccw phase hi nan [0..1]
[p1pof] pwm phase off nan [0..1]
[g54x] g54 x offset nan mm
[g54y] g54 y offset nan mm
[g54z] g54 z offset nan mm
[g54a] g54 a offset nan deg
[g54b] g54 b offset nan deg
[g54c] g54 c offset nan deg
[g55x] g55 x offset nan mm
[g55y] g55 y offset nan mm
[g55z] g55 z offset nan mm
[g55a] g55 a offset nan deg
[g55b] g55 b offset nan deg
[g55c] g55 c offset nan deg
[g56x] g56 x offset nan mm
[g56y] g56 y offset nan mm
[g56z] g56 z offset nan mm
[g56a] g56 a offset nan deg
[g56b] g56 b offset nan deg
[g56c] g56 c offset nan deg
[g57x] g57 x offset nan mm
[g57y] g57 y offset nan mm
[g57z] g57 z offset nan mm
[g57a] g57 a offset nan deg
[g57b] g57 b offset nan deg
[g57c] g57 c offset nan deg
[g58x] g58 x offset nan mm
[g58y] g58 y offset nan mm
[g58z] g58 z offset nan mm
[g58a] g58 a offset nan deg
[g58b] g58 b offset nan deg
[g58c] g58 c offset nan deg
[g59x] g59 x offset nan mm
[g59y] g59 y offset nan mm
[g59z] g59 z offset nan mm
[g59a] g59 a offset nan deg
[g59b] g59 b offset nan deg
[g59c] g59 c offset nan 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

chmr Oct 9, 2014 #

Hi, I have no idea what could cause this, but some things you could try:
Check the status report while traversing. What velocity does it report? Might give a hint where to look.
Also might want to try to reset the settings to default and reenter your configuration, in case something got corrupted in there.

aldenStaff Oct 9, 2014 #

I'm not familiar with the OX machine. From your settings it looks like X is GT3 belt, Y is a dual gantry of the same, and Z is a screw axis. Can you enlighten me on this? This would help the diagnosis.

cmcgrath5035Staff Oct 9, 2014 #

Alden Have a look at the other active Ox thread

https://www.synthetos.com/topics/a-little-confused-and-annoyed/

Chmr provides a good summary of the construction.

cmcgrath5035Staff Oct 9, 2014 #

ictoamm
The value for $xtm above looks bogus. Did you set that? Compare your settings to the Ox thread posted to Alden above.

Bogus parameters can sometimes be cleared with a defa=1 . Note that you will then have to reset the configuration parameters specific to your machine.

What is particularly interesting is that the other Ox thread has the opposite issue - G0 Z20 move moving too slow .

You might also consider trying $4mi=4. Alden recommends Z microsteps = 4 in Shapeoko world, but Ox has a very fast (8mm/rev) lead screw, so that may not be good answer here.

The travel per revolution parameters for the Ox are quite different from Shapeoko space, where much of the tinyG testing takes place. There is the remote possibility that a calculation issue (bug) has been triggered.

ictoamn Oct 9, 2014 #

Here's a down traverse and back up to zero

qr:31, qi:1, qo:0
posz:-0.015,vel:32.93,stat:5
posz:-0.189,vel:207.01
posz:-0.830,vel:574.20
posz:-2.206,vel:1068.18
posz:-4.301,vel:1550.96
posz:-7.258,vel:1958.51
posz:-10.559,vel:2178.67
posz:-14.255,vel:2240.23
posz:-17.975,vel:2223.48
posz:-21.395,vel:2085.02
posz:-24.598,vel:1753.12
posz:-27.005,vel:1302.10
posz:-28.718,vel:786.97
posz:-29.598,vel:369.11
posz:-29.945,vel:93.63
posz:-30.000,vel:3.04
posz:-30.000,vel:0.00,stat:3
qr:32, qi:0, qo:1
qr:31, qi:1, qo:0
posz:-29.982,vel:37.87,stat:5
posz:-29.792,vel:221.08
posz:-29.120,vel:596.71
posz:-27.703,vel:1094.26
posz:-25.568,vel:1574.64
posz:-22.578,vel:1974.51
posz:-19.260,vel:2185.39
posz:-15.559,vel:2240.48
posz:-11.840,vel:2220.14
posz:-8.433,vel:2072.93
posz:-5.258,vel:1732.00
posz:-2.889,vel:1276.34
posz:-1.218,vel:762.32
posz:-0.345,vel:332.99
posz:-0.048,vel:85.01
posz:-0.000,vel:2.11
posz:0.000,vel:0.00,stat:3
qr:32, qi:0, qo:1

I guess, I'll reset to default and try setting everything again when I get home from work later.

Thanks,
Chris

cmcgrath5035Staff Oct 10, 2014 #

Just curious, What power supply voltage you using with your tinyG and motors? 24V?

ictoamn Oct 10, 2014 #

I am using a 24v unit.

Ok, so it looks like resetting the default config has fixed whatever cause the problem. Looking at the default settings, I can tell that when I first got the TinyG it came with completely different settings. The xtm setting being as strange as it was and now after the defa=1 the xtm is 150mm. Maybe the config was corrupted when being loaded at manufacturing?

Either way, thanks for the help guys.

-Chris

cmcgrath5035Staff Oct 10, 2014 #

Chris
Yes, it has been apparent for a while that some units shipped a while ago with what I'll call an 'unclean' loaded default.
Bogus parameters in $$ dump are an indicator, alas you are not seeing everything with $$, so sometimes we have to recommend defa=1 sort of blindly.

Have fun

Rhinofart Oct 11, 2014 #

@ictoamn

How are you liking your OX so far? How does your system start up with a job? Mine is still traversing from the start into the work area at a dead turtle's pace, and then runs fine once the Z drops down and the "work" begins.

cmcgrath5035Staff Oct 11, 2014 #

Rhino
Looking at your Gcode "Lots o Shapes.cnc", nothing looks "illegal" in the startup lines.
I'll just comment that code I run does not have the line 'G90 G21 G49'; but those are legit commands.
As a general rule, when I run a job, I follow this workflow
I don't have home or limit switches, by the way.
1. Move to my desired start (0,0,0) location either manually, by jogging or by G0 commands (or a combination)
2. Reset tinyG
3. Send the Gcode

What are you using to send Gcode? Coolterm, tgFX, etc....

I have noted a couple quirks, which may/may not apply to fw 438.02.
+Some jogging implementations leave tinyG in a funky state
+tgFX frequently has trouble running a second job without a tgFX restart
+ My jobs always(by template in Gcode generator) end with an M60, after which tinyG seems to be in JSON mode and needs to get switched back to text, which it does automatically when it sees a non-JSON command, but the first text mode command gets dropped. So, for example, to move back to zero manually, I have to enter G0, then G0 X0.
+Aggressive manual movement of you gantry can send non-trivial voltages back into tinyG (the steppers becomes generators). The resulting noise could be improperly flipping bits. A reset of tinyG should clear any impact.

Try the reset before running your jobs.

Also, consider having you Gcode generated with line numbers. Makes the file larger, but easier to discuss.

BTW, this is sort of a hijack(by me) of this thread, continue the start up topic,if desired, in a new thread.

ictoamn Oct 11, 2014 #

Hey Rhino,
Yeah so far it seems nice. Before I did the default reset, things (mainly speeds) were all over the place. Now things are running smooth. I'm using Chilipeppr to run the machine.

Right now I'm working on running the final wiring and mounting the limit switches. I ran your gcode on the Chilipeppr sim and it works fine. Once I have it all put back together I'll try it on the machine.

If you're using TGFX I'd recommend trying Chilipeppr... It's pretty nice.

-Chris