G code bug

Moderators: TomKerekes, dynomotion

Post Reply
GabrielR922
Posts: 74
Joined: Thu Aug 13, 2020 10:07 pm

G code bug

Post by GabrielR922 » Fri Mar 12, 2021 3:01 pm

Hi tom.

Have been running my machine for aprox 4 months now and now g-code problem.
But I can't run the attached g-code. (IAGO3.txt) also attached is another code with higher engraving speed that runs fine.

What happens:

When it reaches the engraving part (T4), at the "i" point, it simply disables the machine.

ok. re-enable the machine, try to run again: it disables when call the N25 G53 G0 Z-1 with a error Following Error Disabled Axis:0.

The 0 axis is the X axis, so nothing to do with the command.

for it to run again i have to power off k-flop when power it on again.
Any other thing i do simple disables the machine.

Thanks.
Attachments
inocencio.txt
(107.79 KiB) Downloaded 8 times
iago3.txt
(191.09 KiB) Downloaded 8 times

GabrielR922
Posts: 74
Joined: Thu Aug 13, 2020 10:07 pm

Re: G code bug

Post by GabrielR922 » Fri Mar 12, 2021 4:39 pm

little update:

installed a fresh version of KMotion435f, same configs for everything, worked fine.

I have changed the screen and used a default one.

is it possible to be the screen?

also, in the old installion the software run very slow, sometimes even getting buffer error. now i have decreased the buffer time from 10sec to 5sec and it runs perfectly fine.

Maybe the axis/spindle power meters are consuming cpu? (the script are running in both, i'm just not loading them in screen)

attached the old screen.
Attachments
screen.PNG

GabrielR922
Posts: 74
Joined: Thu Aug 13, 2020 10:07 pm

Re: G code bug

Post by GabrielR922 » Fri Mar 12, 2021 5:11 pm

Same error now with a slighty different file

attached also TP config.
Attachments
iago4.txt
(200.86 KiB) Downloaded 7 times
TP.PNG

GabrielR922
Posts: 74
Joined: Thu Aug 13, 2020 10:07 pm

Re: G code bug

Post by GabrielR922 » Fri Mar 12, 2021 5:36 pm

Tom, new update.
Found the problem but not the solution.
last version with the GCodeInterpreter from the other topic here in bug report.

with facet angle of: 0.3 everything runs fine.

with facet agle of: 0.2, machine stops.

then i did this steps:
enable the machine again
moved Z up
moved X Y away from part

MDI G1 G53 Z0 F1000

machine went to Z0.7 and stopped,
axis dimensions where as photo
ZaxisZero2.PNG
init again, the dimensions where the same in dest and pos

MDI G1 G53 Z0 F1000 again

axis dimensions where as photo
ZaxisZero.PNG
Init again, axis dimensions fine, can move with jog, if mdi or start program, ERROR!

Also got this code in console
MoveEx Failed! chan=0 a0=0 v0=0 dx=1.00001e-06 MaxVel=0 Accel=990000 Decel=990000 Jerk=3.5e+06
MoveType:INVALID_ZERO_NEG_CONSTRAINT
Following Error Disabled Axis:0

Thanks Tom

User avatar
TomKerekes
Posts: 1515
Joined: Mon Dec 04, 2017 1:49 am

Re: G code bug

Post by TomKerekes » Sat Mar 13, 2021 11:21 pm

Hi Gabriel,

I haven't been able to duplicate any problem running your GCode with those Trajectory Planner settings with V4.35f with the curvature patch installed.

Facet angle of 0.2 degrees is very small. That causes every 90 degree angle to generate 450 segments. We recommend 1 degree or higher. But this should only cause the machine to slow down not disable. KFLOP can process ~ 2000 motion segments/second.

You have the Trajectory Planner Velocity of 20 inches/sec. Can your machine actually do this? Please post a step Response Screen showing that velocity.

If you get a following error and the Position and Destination are far apart, if you try to enable there will likely be a big jump or an immediate following error. You must use EnableDest() to Enable the axis with a destination of the current Position. Post the code you are using to initialize your system.
Regards,

Tom Kerekes
Dynomotion, Inc.

GabrielR922
Posts: 74
Joined: Thu Aug 13, 2020 10:07 pm

Re: G code bug

Post by GabrielR922 » Mon Mar 15, 2021 5:47 pm

Hi Tom. the system runs perfect with facet angle of 0.3, also its using a feed of ~1000mm/min for the specified g-code operation.
the machine is capable of around 30in/sec.

here is a plot of it doing ~23in/sec

What's this error for ?

MoveEx Failed! chan=0 a0=0 v0=0 dx=1.00001e-06 MaxVel=0 Accel=990000 Decel=990000 Jerk=3.5e+06
MoveType:INVALID_ZERO_NEG_CONSTRAINT
Following Error Disabled Axis:0

Also, my init program always work flawless, also the ref program.
I just have problem while using the 0.2 facet angle.
If the machine disable for whatever other reason, I can enable it again and it will work fine.

For the facet angle, I was trying to eleminate jerk with g-codes created from splines, this is why i used a low facet angle, will use 0.5 by now.

Thanks Tom
Attachments
plotvelocirt.PNG

User avatar
TomKerekes
Posts: 1515
Joined: Mon Dec 04, 2017 1:49 am

Re: G code bug

Post by TomKerekes » Mon Mar 15, 2021 7:09 pm

Hi Gabriel,
here is a plot of it doing ~23in/sec
Very fast machine. Btw it is good to also post the raw data. That way we can re-plot it to show Velocity, zoom in, etc. An error plot alone doesn't tell us much.

What's this error for ?

MoveEx Failed! chan=0 a0=0 v0=0 dx=1.00001e-06 MaxVel=0 Accel=990000 Decel=990000 Jerk=3.5e+06
MoveType:INVALID_ZERO_NEG_CONSTRAINT
This indicates an independent axis move trajectory was requested with a max allowed velocity of 0, which is impossible. The length of the move is only 1e-6 counts so probably caused by some round off error somewhere. When does it occur? Can you re-produce it?
Regards,

Tom Kerekes
Dynomotion, Inc.

GabrielR922
Posts: 74
Joined: Thu Aug 13, 2020 10:07 pm

Re: G code bug

Post by GabrielR922 » Mon Mar 15, 2021 7:39 pm

Hi Tom,
The length of the move is only 1e-6 counts so probably caused by some round off error somewhere. When does it occur? Can you re-produce it?
This error occur when I use the file and the configurations of this post:
GabrielR922 wrote:
Fri Mar 12, 2021 5:11 pm
Same error now with a slighty different file

attached also TP config.
with facet angle 0.3 it don't happen. maybe it's because the software divide the line in to many short lines?
did you run the file in inch mode or mm mode ?

GabrielR922
Posts: 74
Joined: Thu Aug 13, 2020 10:07 pm

Re: G code bug

Post by GabrielR922 » Mon Mar 15, 2021 7:40 pm

Btw it is good to also post the raw data. That way we can re-plot it to show Velocity, zoom in, etc. An error plot alone doesn't tell us much.
Yeah, in the topic with the info about the configuration of the servos i will do a full report.

Thanks Tom.

Post Reply