Bit of a Newbie with UGS but I have been using Mach3 since 2012 on my old CNC Machine. My two new CNC Machines are a heavily modified 3018 Engraving machine and a Fox Alien Masuter 3S both of which only answer to GBRL Comms To which I have taken quite a shine to UGS.
I’m so glad to find that a Forum exists and look forward to hearing from others and helping where I can.
The annoying problem I’m having seems to happen every time UGS comes across a hole or a drilling.
The error report in the console is as follows:
An error was detected while sending ‘G3X23.32Y51.94I1.92J3.33’:
(error:33) Motion command target is invalid.
Streaming has been paused.
An error was detected while sending ‘G3X15.62Y51.94I1.92J-3.33’:
(error:33) Motion command target is invalid
. Streaming has been paused.
**** The communicator has been paused ****
**** Pausing file transfer. ****
I forgot to mention I am using CamBam to generate my G-Code…
Another clue to the error is that if I use Candle it runs fine.
As I have said I really like the loks and the features of UGS, but this error business is starting to make me think otherwise.
It’s been years since I’ve used UGS, but here is an explanation of that error code in the gSender documentation
Error 33
Can pop up as “Motion command target is invalid” and usually comes from issues with G2 or G3 arc/curve movements in the g-code. If the target is invalid you might want to verify the file again in gSender or regenerate it in CAM with the right post processor.
For example, there have been manyreports that if you use the inch post processor in Vectric, Carveco, or Fusion 360 then they won’t add enough decimal places to satisfy arc curve calculations – which will cause an Error 33. The best solution is to just use a mm post processor to get more accurate movements, or for Carveco use UGS grbl.
You may also want to ask on the UGS forum. Good luck. Please post back when you find the solution.
I now think I have resolved my issues in UGS The problem was partly identified by a chap on another forum called “cncmakers001” who gave me a hint what to look for.
cncmakers001 wrote and I quote verbatim:-
“GRBL is very strict about arcs being precise and valid, whereas Mach3 and even some senders like Candle are more lenient or even approximate arcs as tiny line segments behind the scenes.”
This sent me into hunt mode where I looked more closely at my G-Code generator, CamBam. In depth analysis identified that a radius or arc was being generated to a staggering 16 decimal places, absolutely crackers but true !
That was not a problem if the decimal places were at zero but UGS would spit it out like a nasty taste if it was something
like 4.45807984715249
to resolve the issue I simply rounding up most of the trailing digits to within five decimal places.
I’m back in love with UGS its slick looks and its lovely features as I was about to venture on ripping out the GRBL controllers and replacing them with USB Mach3 boards.