TinyG failing at corners | Synthetos Forum

Started by Gaylord on Dec 23, 2017 in TinyG Support. 3 replies, last activity Jan 5, 2018.

Gaylord Dec 23, 2017 #

I'm getting errors and the program won't finish. I think it's the board
posx:3.078,posy:4.021,posz:0.463,vel:4.70
qr:4

tinyg [inch] ok>
X2.476
tinyg [inch] err: Arc specification error: X2.476

tinyg [inch] ok>
X3.05 9868IX3..4229 I0.0355 J0.0476 Y3.952.5 J0.04J0476 Z0.3968 I0.
tinyg [inch] err: Bad number format: X3.05 9868IX3..4229 I0.0355 J0.0476 Y3.952.5 J0.04J0476 Z0.3968 I0.
X3.0578 Y4.0476 Z0.3838 I0.0355 J0.0476
tinyg [inch] ok>
posx:3.075,posy:4.027,posz:0.463,vel:2.21
posx:3.068,posy:4.038,posz:0.463,vel:0.09
qr:4
posx:3.059,posy:4.046,posz:0.462,vel:4.00
qr:3
posx:3.054,posy:4.050,posz:0.462,vel:4.59
qr:4
posx:3.045,posy:4.055,posz:0.461,vel:0.19
posx:3.033,posy:4.058,posz:0.461,vel:2.37
qr:4

tinyg [inch] ok>
X2.9868 Y376
tinyg [inch] err: Arc specification error: X2.9868 Y376

tinyg [inch] ok>
X3.0578 Y4.0476 Z0.3317 I0.0355 J0.posx:3.026,posy:4.059,posz:0.461,vel:4.56
qr:5
posx:3.017,posy:4.059,posz:0.460,vel:0.19
posx:3.004,posy:4.056,posz:0.460,vel:2.36
qr:6
posx:2.999,posy:4.054,posz:0.460,vel:4.71
qr:7
posx:2.990,posy:4.050,posz:0.459,vel:0.53
posx:2.979,posy:4.041,posz:0.459,vel:0.89
qr:8
posx:2.974,posy:4.034,posz:0.459,vel:4.95
qr:9
posx:2.970,posy:4.028,posz:0.458,vel:2.53
posx:2.965,posy:4.016,posz:0.458,vel:0.08
qr:10
posx:2.964,posy:4.006,posz:0.458,vel:4.42
qr:11
posx:2.963,posy:4.001,posz:0.457,vel:2.58
posx:2.964,posy:3.988,posz:0.457,vel:0.12
qr:12
posx:2.967,posy:3.978,posz:0.457,vel:4.48
qr:13
posx:2.970,posy:3.973,posz:0.456,vel:3.26
qr:14
posx:2.976,posy:3.962,posz:0.456,vel:0.00
posx:2.986,posy:3.953,posz:0.456,vel:2.90
qr:15
posx:2.992,posy:3.950,posz:0.455,vel:4.83
qr:16
posx:2.999,posy:3.945,posz:0.455,vel:0.53
posx:3.013,posy:3.941,posz:0.455,vel:1.44
qr:17
posx:3.019,posy:3.941,posz:0.454,vel:4.67
qr:18
posx:3.027,posy:3.941,posz:0.454,vel:0.52
posx:3.041,posy:3.944,posz:0.453,vel:1.43
qr:19
posx:3.047,posy:3.947,posz:0.453,vel:4.84
qr:20
posx:3.054,posy:3.950,posz:0.453,vel:1.11
posx:3.065,posy:3.959,posz:0.452,vel:0.38
qr:21
posx:3.071,posy:3.967,posz:0.452,vel:4.69
qr:22
posx:3.075,posy:3.973,posz:0.452,vel:3.49
posx:3.079,posy:3.984,posz:0.451,vel:0.00
qr:23
posx:3.081,posy:3.995,posz:0.451,vel:3.87
qr:24
posx:3.081,posy:4.000,posz:0.451,vel:3.48
posx:3.080,posy:4.012,posz:0.450,vel:0.00
qr:25
posx:3.077,posy:4.023,posz:0.450,vel:3.92
qr:26
posx:3.074,posy:4.028,posz:0.450,vel:3.95
qr:27
posx:3.068,posy:4.038,posz:0.449,vel:0.05
posx:3.058,posy:4.047,posz:0.449,vel:2.02
qr:28
posx:3.058,posy:4.048,posz:0.442,vel:5.07
qr:29
posz:0.433,vel:0.18
posz:0.418,vel:3.04
qr:30
posz:0.413,vel:4.30
qr:31
posz:0.400,vel:0.00
posz:0.388,vel:4.60
posz:0.384,vel:0.00,stat:3
qr:32
g0 x0 y0 z0
g0 x0 y0 z0
tinyg [inch] ok>

Can anyone assist

cmcgrath5035Staff Dec 23, 2017 #

tinyG is Fussy about Arcs, the beginning of one arc and the end of the prior must meet certain criteria. Ultimately, this can be cause by a math precision error.

Frequently, regenerating the design using mm, rather than inch, will resolve it.

Gaylord Jan 2, 2018 #

Thanks for your previous troubleshooting help. I re-created the identical model in F360 after changing the preferences to mm. I did the CAM setup in mm and published the gcode. The simulation worked fine.

I homed the machine, zeroed Z at WCS, work piece top using G92 Z0. I'm using G54.

The machine stops at the same line stat:3 So I did a $sr and got:

posx:76.833,posy:102.443,posz:9.031,vel:23.49
posx:76.522,posy:102.607,posz:9.034,vel:18.84
qr:30
posx:76.313,posy:102.660,posz:9.036,vel:119.69
qr:31
posx:76.151,posy:102.696,posz:9.037,vel:36.07
posx:75.805,posy:102.697,posz:9.040,vel:16.91
posx:75.802,posy:102.697,posz:9.040,vel:0.00,stat:3
qr:32
$sr
$sr
tinyg [mm] err: Bad number format: X76.16 Y99.703 Z8$sr

Your Thoughts?

cmcgrath5035Staff Jan 5, 2018 #

Hmmm, the only reference I see to "Bad number format" uses the example of G0 X1..23 rather than G01.23, basically a typo entering Gcode.
That is unlikely with generated Gcode, e.g. F360.

Are you able to locate a line of Gcode in your file that includes "X76.16 Y99.703 Z8"?
Perhaps the offending "Bad Number" is near this line, sitting in the buffer having been pre-fetched by the planner.

I recall (can't locate the thread) someone commenting that using the F360 post processor to reduce the number of digits beyond the decimal point from 4 to 3 (or perhaps 2) resolved some unusual behavior.
Also, these lines of Gcode from your first post in this thread do look strange

tinyg [inch] ok>
X3.05 9868IX3..4229 I0.0355 J0.0476 Y3.952.5 J0.04J0476 Z0.3968 I0.
tinyg [inch] err: Bad number format: X3.05 9868IX3..4229 I0.0355 J0.0476 Y3.952.5 J0.04J0476 Z0.3968 I0.

Can you provide a segment of your Gcode before and after the offending line?

I don't trust the auto formatting that goes on with this web tool - better to put the code in a Cloud drive text file and provide a URL