Closed Midlyhelpless closed 1 month ago
Midlyhelpless
commented
1 month ago The issue has been solved. The PostProcessor needed to be TinyG(mm) not TinyG(In) regardless of what the UGS Jog interface says. You can certainly change the Jog interface to metric or imperial based on preference but either/or should work even though the PostProcessor is metric.
This issue arose because I choose to use freedom units so I assumed the PostProcessor needed to match my preference.
ril3y
commented
1 month ago Thanks for updating this!
On Mon, May 20, 2024 at 10:41 PM Midlyhelpless @.***> wrote:
The issue has been solved. The PostProcessor needed to be TinyG(mm) not TinyG(In) regardless of what the UGS Jog interface says. You can certainly change the Jog interface to metric or imperial based on preference but either/or should work even though the PostProcessor is metric.
— Reply to this email directly, view it on GitHub https://github.com/synthetos/TinyG/issues/283#issuecomment-2121601822, or unsubscribe https://github.com/notifications/unsubscribe-auth/AABYSM7ORZHCSO5VPZLJ2ZLZDKX7JAVCNFSM6AAAAABIAFMWQCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRRGYYDCOBSGI . You are receiving this because you are subscribed to this thread.Message ID: @.***>
My CNC uses:
TinyG v8 board files made in Vcarve Pro 11.5 TinyG inches as post processor UGS as the interface ASUS laptop as controller
When trying to place dogholes on the spoilboard it keeps pausing at the same spot in the arch. but it doesn't do it for every doghole or all the depth passes. It also doesn't want to start the file at all except for! It would allow me to resume if I spammed the play button.
So to get the file started I have to mash the play button and at certain similar points it will pause again and I'll re-mash the play button to keep the file going ... after three of four rounds of button mashing UGS will throw a Unhandled message when no limits have been triggered. UGS also doesn't show any error code in console and everything mentioned also happens when cutting air.
An import detail is that the machine WILL flawlessly cut one single test doghole file of the exact same size, speed, location as the full file but the file does not contain any extra doghole data. The Gcode files differs in some notable ways but both files are made in Vcarve almost exactly the same the only difference is instead of: making one circle - saving toolpath. I make one circle - array the circle - array the toolpath - then save toolpath (this array action might be a problem ill test it out)
https://github.com/synthetos/TinyG/assets/170275392/f666d141-f13a-477b-9343-eac60547a1da