GearHeads Corner

Bobby,  I loaded your image into Augs.  Set the output size in X axis to 4" which made the Y Axis size 3.9582".  I set the ramp to 0.5".  Hit generate and got the .aug and .tap files as expected.  Loaded the .tap file and it appears to be all set to run.  I didn't execute the file but it looked all ok to me.

Mark

MarkW wrote: Bobby,  I loaded your image into Augs.  Set the output size in X axis to 4" which made the Y Axis size 3.9582". 

Mark

Thanks Mark for the test.
Yes if you put any X dimmension than "230" will work without problems.
I work with mm so at me x230 is mean W230mm.
Maybe depends of the individual system and motors config.
Well that annoying because some days ago i got the same error on other photo , no reason why . I just modify the original photo
from W2000px to W2100px and working fine.
Of course annoying me because i dont understand why :(
I edit all photo to grayscale and ajust everything to look nice until to generate augie code.

I notice all photo are different interpretated "color-grey" in auggie and i try to find a way to get a stable reference for all photo .
That to dont test , retest and adjust until i got a optim result.
Thanks to all
Bobby

Hi everyone .
Seems i got in same point again .
That error come on the same point doesn't matter what i use to generate GCODE .
And now commin again .
Is not realy the issue , i remove that little part where auggie stop and i build other one .
I just want to understand what's going on . Or maybe help someone in the future.
https://prnt.sc/yotyfz
Thanks
Bobby

Bobby:

Hmm ,maybe send me the Gcode so I can see what is crashing. I may be able to trace it internally..Sounds like
a division by zero in there somehow..

Art

ArtF wrote: Bobby:

Hmm ,maybe send me the Gcode so I can see what is crashing. I may be able to trace it internally..Sounds like
a division by zero in there somehow..

Art

Well the file was drawed manualy , and is clean . I can send you the svg file also if you need it.
I put below the code.
Thanks Art
Bobby

Bobby:

  This file runs fine her with no crash or error. Im not sure what may be causing this one..

Art

ArtF wrote: Bobby:

   This file runs fine her with no crash or error. Im not sure what may be causing this one..

Art

Well , is not realy a big deal, sure is in my PC something wrong.
I has hard time to install win7 , the bios was protected and maybe i mess up something in my PC.
That happen rarely . I remove that point where program stop, created a new GCODE & work just fine after.
Single problem remain , after auggie crash , the polywood are damaged and i cant reload from same point as before.
But like in life good & bad = knowledge  :D :D :D
Thanks
Bobby

Hi everyone
I have some trouble for a while with my code . I try to find a extension for inkskape
to generate the GCODE to fit with Auggie and to cut and engrave by color lines.
So far i found some , but not useful , no one change the power,speed by line color.
So keep reading and combine some pieces of codes also writing new ones i manage
to generate the GCODE with 4 different power speed by color.
To good to be true , sometime after engraving , when the time come to cut , the laser dont fire
on some small parts . I noticed if the part need to be cutted have less than 4 points sometime
miss to cut random pieces. If you run the code again , same parts are not cutted.
If i generate separately the GCODE , one for engrave and one for cut , everything is ok.
That happen only when cut and engrave with different power speed are combined in one file.
I put below a pic with that error and also the GCODE , maybe experimented guys can
figure out what is wrong .
I try to figure out but no chance for me .
Also if someone want i can send the inkscape extension , single problem is
variable are writed 30% romanian and the rest in english . In SVG file , black line generate cut
, blue deep engrave and blue+green light engrave.
Thanks
Bobby

You may want to try it without all the M5 and M3's. Just put one at the start. Auggie will not cut in G0.
The laser will only cut or burn when G1 moves are in progress , otherwise power is off. ITs possible
all the redundant script calls are threadlocking or something. Just put m3 at start, and an M5 at end of
the code and rely on the G0 moves to not cut while the G1 moves do.

Art

ArtF wrote: You may want to try it without all the M5 and M3's.

Art

Thank you Art , you are the boss  :)
Well soon i wake up i saw you answer and i start to modify .
I let M3 only an beginning and M5 at the end of code .
Surprised , the laser cut all lines , dont miss any line and everything is fine.
Second good thing , now the extension generate the GCODE way more faster ,
i mean if before for 20000 GCODE lines need 20 sec , now in 6-10sec is done.
Still i'm not sure if is necesary the line "G00 (LASER OFF) "
because if i pass that on next will be the " power" and " feed " set and
start again in "G0" >
I mean the laser will never " accidentaly " burn without that line , right ?
For me was a little difficult , without any knowledge about GCODE ,
my start was from "0". All good now , still learning.
Thanks Art
Bobby

Hi Bobby:

  The G0 line is not required for laser control. It is a given that any G0 move will
not turn on the laser. SO really, only an M3 at start is necessary, and the M3 is really only a
safety.

Art

Ok . Understood .
I remove all unnecesary comands and now work ok.
So at the end wasn't the extension issue , M3 M5 G0
repeately on each path just saturate the script .
And also the code is generated way more fast of course.
Thanks Art
Bobby

Bobby:

  Those scripts, M3 etc.. were written to be executed as laser on and probably dont contain a
syncing variable to wait for completion of the command. In that case the m3 may not actually turn on till
a few ms after the next command causes motion.  Ill have to check that as it could cause a loss of burn
in such a case as yours.
  Recently one user made cnc scripts for spindles and I think he had to add a sync to make sure
the spindle was up to speed before continuing.

Art

ArtF wrote: Bobby:

  Recently one user made cnc scripts for spindles and I think he had to add a sync to make sure
the spindle was up to speed before continuing.

Art

Yea , on laser a burn miss is not big deal but on CNC it is .
I got the point about that .
And now with all pieces together , i remember , when i write first time the extension
to fit with Auggie was ok , but in that time my motors wasn't realy "good " tuned.
in time , getting experience , i figure out my laser can go to 12000 without any problem
the motors are with encoders and never miss one step , many time i engrave a photo 6 or 7 times
just to test and never miss the 0 point . But... after G00 go from 4000 to 12000 "max 4000 was my old config"
the laser start to miss some very small points .
And now working normaly.
When i start to build i was with '0" experience in CNC and GCODE and of course
i made many mistakes when i design the laser .
the very big one , the X ax are so heavy + big motor , totaly pointless to move 200g
laser head , the ax itself is at least 20 times more heavy than the laser head,
but if we dont mistake we can not learn , so ... we go on. :D
thanks Art
Bobby

Hi everyone .
Just to say i want to cut a small shape , doesn't matter the complexity
and i dont want to travel all time to my PC to rewind the code and start my job.
So it is possible via script to program some push buttons connected to Pokeys IO ?
Like " Run " Stop " Rewind ' Cont.
That can be possible via script ?
Thanks
Bobby