Mach3 loses Y axis location during code

[chadcummings]

So I have ran 2 sets of gcode which cut the same pattern, just at different rates and overlap and have found at the same spot that the Yaxis loses about an inch of its orientation and starts cutting off in neverland.

I do not believe it is losing steps as it is in the same spot that it happens in and it is a consistent amount that it does it.  The area of gcode is around line 284000 so I know it is within the limits of mach3.

I also just realized I am running one of the 3.042 series code and will be updating it to the new one.

Any ideas?

[Tweakie.CNC]

Chad,

May be an idea if you post your GCode, this way it can be established if it is the fault of the code or your setup.

Tweakie.

[chadcummings]

the gcode is 35meg 

[Tweakie.CNC]

Well, that's that then as the forum limit is 6MB.

(I regularly run code in excess of 340,000 lines which zip to less than 4MB).

Tweakie.

[BR549]

Just cut out the section that gives the problem and post that part in a file(;-)

What version Mach are you running? 

(;-)TP

[chadcummings]

I realized last night I was using a 3.42 series of Mach3.

I am in the process this evening of upgrading it.

Here is the gcode.

[Tweakie.CNC]

Chad,

I am using version R3.043.022 and I just had a problem with X position when running your code.
May be me or it may be the code or it may just be the length / size of the code, in any event it deserves further investigation. I will try it again later and see just what is going on.

Tweakie.

[Tweakie.CNC]

Chad,

This appears to be a Mach / PC related problem in so far as the length of the GCode is concerned. I have now run your code twice and had errors on both occasions.
In my case the X axis Scale DRO is changing to -1.0000 of it’s own accord and the machine takes off to the other side of the table.

I have another PC which has the maximum RAM and I will try that just to see if it is a memory paging issue but I have examined the GCode itself and can find nothing that would cause this fault so I can only conclude that it is the size / length of the GCode which is upsetting either Mach3 or the PC.

Reworking your model to produce a number of smaller programs which could be executed concurrently may provide a practical solution and for now, be the best way to proceed.

Could anyone else perhaps try this CGode and see if they have problems also ?

Tweakie.

[Hood]

Have you tried turning off the toolpath view?
Hood

[Tweakie.CNC]

Hi Hood,

I just tried it with the toolpath view turned off but no difference it crashes at, more or less, exactly the same place.

Tweakie.