Hello Guest it is March 29, 2024, 03:16:13 AM

Author Topic: Mach3 not reading g-code properly?? Help Please....  (Read 2602 times)

0 Members and 1 Guest are viewing this topic.

Offline Davek0974

*
  •  2,606 2,606
    • View Profile
Mach3 not reading g-code properly?? Help Please....
« on: May 01, 2016, 05:32:47 AM »
Wasted a lot of valuable time on this :(

I need to cut four arcs - open lines so no offsets or lead-ins etc.

The code tests perfect in Sheetcam simulation but when loaded into the plasma/mach3 it only cuts four very sort lines, maybe 5mm long?

I have attached the code file below but I am not upto reading I/J arcs yet.
 
Does this code cut long 120degree arc or short 5mm lines please??

Mach is V067
« Last Edit: May 01, 2016, 05:36:06 AM by Davek0974 »

Offline ger21

*
  • *
  •  6,295 6,295
    • View Profile
    • The CNC Woodworker
Re: Mach3 not reading g-code properly?? Help Please....
« Reply #1 on: May 01, 2016, 07:41:02 AM »
I had to delete the M98's and M22's to get it to show anything.

Your arcs as coded are less than 5mm long.

The first one goes from X436.319 Y 897.932 to X434.437 Y900.268.
About 2mm in X, and 3mm in Y.


Gerry

2010 Screenset
http://www.thecncwoodworker.com/2010.html

JointCAM Dovetail and Box Joint software
http://www.g-forcecnc.com/jointcam.html

Offline Davek0974

*
  •  2,606 2,606
    • View Profile
Re: Mach3 not reading g-code properly?? Help Please....
« Reply #2 on: May 01, 2016, 09:00:33 AM »
Must be a sheet-cam bug then, it works perfectly in simulation!

The lines cut are exactly as you describe.

Thanks for looking


BTW
The M98 is my IHS macro and the M22 are CandCNC codes for the THC ;)
« Last Edit: May 01, 2016, 09:05:41 AM by Davek0974 »

Offline Davek0974

*
  •  2,606 2,606
    • View Profile
Re: Mach3 not reading g-code properly?? Help Please....
« Reply #3 on: May 02, 2016, 09:57:42 AM »
Les from Sheetcam, sorted it - I had over-cut turned on and it seems on an open line with over-cut you get the over-cut and not the job!

He is looking into it but turning it off sorted the issue and the job is done :)