Ditto, using G40 with a D word in the safety block (G90 G0 G17 G40 D0 G54 etc) generates an error in PP, and must simply be a rule violation in the LinuxCNC implementation because without D0 there's no problem. Other errors (starting in the wrong place, commanding a G1 move without an F word, stuff like that) in the generated posts are pretty obvious and easy to fix in the post generator. Both incremental and absolute reference frames worked fine in M3.
CAMBAM TABS ON WRONG SIDE CODE
Absolute (G90) code had similar problems. It's obviously a function of some calculation in the code interacting with PathPilot. That is the remaining problem I'm working on- wrong depth of thread. When I switched to Pathpilot, incremental (G91) code started in random places, and PathPilot complained -wouldn't run, actually) with tool diameter compensation reset (G40 D0) and with compensation turned on, generated threads of the wrong depth (G41 D(toolnumber) when sharp V correction was used. The Fanuc 0M post has worked well with the 1100 controlled by Mach3. It comes with posts for Fanuc and multiple other machines. I've used it for 5 years or so, under Mach3, and it just runs. It has very flexible control over start/stop point, lead-in/out, material speeds/feeds, internal/external, pretty much anything one can imagine. It can produce both I/J and R helical code, for pretty much any known thread (UN, ISO, NPx, or custom spec) using either sharp V or threadform cutters.
CAMBAM TABS ON WRONG SIDE GENERATOR
What is the error message/problem that occurs? Post the code here and perhaps some of the gurus can point out the fix.I'm using a commercial gcode generator (Advent2008) which seems very good.
0 kommentar(er)
