My laser engraver from 0 knowledge to 32.461% .... probably

[gburk]

Art

I installed the new version, probing seems to be working correct now, but still get the message,  get current com invalid , after each g code call in the script g0 g31 and so on, get it with all them, you want a copy of the log file. but the good thing is the probing seems to be working ok.

Gary

[BobbyW]

Hi
First new Auggie test .
Way better when you see what you doing.
And of course the sugar dont missing.
Thanks
Bobby

[ArtF]

>>but still get the message,  get current com invalid , after each

  This message should be a warning internal to the debug log, I have lowered its priority
so it wont display on screen. It was simply a debugging log for me to let me know a
command was being injected to an empty command queue.

  Mainly a script thing, but is really a minor warning for me during development. IT may be
ignored.


Art

[gburk]

Art

How about the buffer underrun message.. i seem to get these mostly when using the freeaxis 5 - 8

Gary

[ArtF]

Gary:

Ill look into that as well, but I suspect its related to when I added the second planner. It basically means the
buffer for motion has run out in the axis 4-8 section. It may be motion has simply ended on that planner as the primary
one continues to have motion left. This is a little used area in Auggie as few use more than 4 axis, thus its little
debugged or tested. Auggie seems pretty solid now in most areas that have been used and debugged, but I know
thousands of potential bugs exist. Mach had over 100 thousand users reporting bugs so it was much tighter in the
end than Auggie will likely ever be. Always be careful ..its code is truly a beast that takes taming, even I dont know
what it may do in every situation.. Every time I go in there it scares the hell out of me. lol

Art

[gburk]

Art

I can relate to that, hell if i look at code i worked on 2 months ago it looks foreign to me now and almost like staring over to figure out what the heck was i thinking...

I have been testing the 5-8 axis's trying to use for tool change. over kill i know..

I won't knock mach3 from a lot of reading and video's, seems like quite a few users  have gone back to mach3, from mach4.

Thanks Gary

[ArtF]

yeah, for a program not updated in 14 years, Mach3 certainly has staying power..

Art

[Mooselake]

And they're still designing new hardware for Mach3!  I have a grbl based Sainsmart 3018 mini-router, a simple inexpensive (many would say cheap, my uptown Pro model was only $200US on sale) machine with a 300 x 180mm cutting area.  Sainsmart also has a proprietary (pretty sure they source it from somebody else) USB controller  model (formerly the MX3, now the "Genmitsu CNC Router 3018-PROVer Mach3 Kit") that only works with Mach3 (not 4) and DruefelCNC, no other drivers for the card available.

Unfortunately it's bitten a lot of new 3018 users who were expecting the simpler grbl/gcode streamer interface and not the much more complex Mach3 setup, nor the current $195US price for Mach3.  Sainsmart has a nice side business selling replacement grbl controllers for the machine, since it uses different connectors and wiring than the rest of the much-copied 3018s the usual ones won't work without a lot of extra work.

Kirk

[ArtF]

Amazing..

Art

[BobbyW]

Hi .
A short question about scripting.
I want to write a code who translate from
linear PWM grayscale pulse to linear dither grayscale pulse.
I dont know how to explain what is in my mind.
Basicaly i start to write a code who measure the length pulse
" assuming we use a standard PWM like 1 or 5KHz" know'ed before
to don't do unnecesary math of what frequency are.
So , instead to only decrease PWM period on 30% gray , decrease
frequency as well , pulse by pulse . I assume that will result in automatic
image dither+grayscale "at least that happen in my mind" .
My photo and GCODE experience was totaly 0 until to start here and build my laser
so my knowledge about image conversion are still limited.
I didn't test yet , i just found some dsPIC controllers on my garage
and i will use one to test what is in my mind.
I ask if can be done via script because if is working i will create a script for that
but now i'm way more comfortable coding pure C in microcontrollers.
Anyone know , changing the compiler will reset you skill close to 0  .
I never write something for windows so... i remain on what i know for sure .
The ideea come from old test when with 260Hz i get amazing result on " low gray " areas
but the problem is the speed , need to running low speed like A5 photo 1.6h to dont
get bad result at the small black edges. So in that way i assume the high black will
be at max fixed frequency and low gray at minimum fixed frequency limits.
In relation with speed travel the result will be in interrupted micro lines
that can not be done via normal dither . I mean can be in software but mechanic error and
laser delay will never do that.


Thanks
Bobby