- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
Lost postion
I have been getting a lost position error with the G17 at the end of the Parallel1 toolpath line N18420, I think it is anyway.
I was able to get it to reproduces the error 4 times in a row, today I removed the G17 and it did not lose position at all.
The lost position was a random number in X, Y, and Z work position each time, it would happen when it hit the end of the Parallel1 toolpath then I would have to reset it for Parallel2 toolpath then it was fine to the end.
Any ideas for things for me to try yell out.
Win10 pro | 16 GB ram | 4 GB graphics Quadro K2200 | Intel(R) 8Xeon(R) CPU E5-1620 v3 @ 3.50GHz 3.50 GHz
Daniel Lyall
The Big Boss
Mach3 User
My Websight, Daniels Wheelchair Customisations.
Facebook | Twitter | LinkedIn
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
Daniel,
Couple questions;
1) I thought that Mach3 didn't always play nice with vertical arcs and/or I,J,K statements?
2) You could just disable arcs for anything but XY plane. That would be over here:
That would restrict arcs to the XY plane and linearize them in all other planes. Is that an option for you to try?

Seth Madore
Customer Advocacy Manager - Manufacturing
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
Yes I will try that,
It is fine with arcs if you tune the machine by running a toolpath that Mach3 hates like a Vcarve toolpath, it usually sits between 0.001 and 0.002 for me over 1000 moves, I also set the steps/per over 1m.
It is one of those strange problems that Mach3 can have.
Win10 pro | 16 GB ram | 4 GB graphics Quadro K2200 | Intel(R) 8Xeon(R) CPU E5-1620 v3 @ 3.50GHz 3.50 GHz
Daniel Lyall
The Big Boss
Mach3 User
My Websight, Daniels Wheelchair Customisations.
Facebook | Twitter | LinkedIn
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
Hi @daniel_lyall We discussed this a bit in another thread, the problem with G17 on a line on its own. I wonder does G17 need to be reset for anything other than arcs?
Throughout the post G17 is reset, here for example in onLinear.
Is it worth using a search\replace and comment them out with
//writeBlock(gPlaneModal.format(17));
All the arc moves will set the correct plane when needed so not sure if G17 is needed anywhere else. It might be needed for drill cycles, if so just add it to onCyclePoint.
Mark
Mark Hughes
Owner, Hughes Tooling
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
I could not find anything saying a G17 needs an Axis move or Anything like that the G17 in the G code other than a couple of times it comes up at the end of the Gcode is fine.
It May not be the G17 but was the only thing I changed on the last run it will be a few weeks before I get to test it again.
I will try both ideas just to test to see if it really is the G17.
Win10 pro | 16 GB ram | 4 GB graphics Quadro K2200 | Intel(R) 8Xeon(R) CPU E5-1620 v3 @ 3.50GHz 3.50 GHz
Daniel Lyall
The Big Boss
Mach3 User
My Websight, Daniels Wheelchair Customisations.
Facebook | Twitter | LinkedIn
Fusion