reading Pokeys pins

[ArtF]

>>10,000 holes is there enough time in a day for that many holes Huh Huh

  only with a galvo laser doing 10 ms drilling shots.. :)


Art

[gburk]

Art

I never messed with a laser Most likely won't read some stuff on the laser's but i'm thinking it would be way to much money for a hobby at last one that can cut metal.

Messed with the baby stepping function seems to work now, I'm missing something in the code to go pos and neg, if I step pos to at .001 to .1 and then hit the neg button, it go's past 0 to -.1 plus .001 so didn't reverse just 0.001..

Making any sense?

Gary 

[gburk]

Art

Did some Z probing test to see how close the tool is to the top of part after the probe hit and G01 retract to 1" and a touch plate thickness of .475
this is all in the probe button function and reading the probing dro's for the values..

I didn't have any feeler gauge's handy but after the retract to 1.0 I removed the touch plate and sent the Z to 0, it was really good as far as I am concerned
the tool wasn't pressing into the top of part I could still move the part slightly, but I couldn't fit a peace of paper between the tool and top of part..

I don't know if it would get any better with the probeinvert,1 release on back off or not, there is not much room for improvement. maybe only a thousand or so.

Gary

[ArtF]

Gary:

>> don't know if it would get any better with the probeinve rt

  Yes, generally with fast hardware your within 1 step when a probe hits, if you move back to the probe hit point,
otherwise your within 1 step plus deceleration, so that varies with speed of approach. With a low feedrate and
fair acceleration, youll be within a few steps even without a reverse probe. Thats good enough for most people.

  The jog is odd.. I have your jog screen so Ill check why it goes back so far. It doesnt make much sense, if the
planner wasnt syncing it should fail while jogging forward. First press in negative should only go back .001
from .1.

>> read some stuff on the laser's but i'm thinking it would be way to much money for a hobby at last one that can cut metal.

  It would be. We who play with lasers generally cut paper or wood.  While 3d engraving is fun
with lasers, Im playing with hole sizes in materials as experiments. Here is a photo of one of yesterdays tests
in a piece of normal paper.  This has about 2000 holes I think.. not really sure, each is .2mm in diam. The colors
are because the paper is standing against my monitor screen as the photo is taken. It took about 8 minutes I think
to do all the holes. ( In auggie a laser hole is drilled by a modified G04 "G04P.01R95" which means laser a hole
at 10ms long at 95% power. ), I have a PWM reformatter on mine which then reduces the power to a setting
at the laser, these holes were done at 10% power. ) There is a secret module in vexx that produces Gcode for laser
drilling any matrix of holes at any power and time length in any shape and drills them in an order that allows previous
holes to cool down by drilling the furthest next hole next. :)

Art


Art

[gburk]

Art

Thanks,

Hard to see the holes really small. but cool.

The only real thing I could see myself doing with a laser is engraving, could put one of them together cheep enough for plastic or wood, but also running out of room in a two car garage, with two mills a lathe 2 3d printers and all kinds of tools or toys.. wife would not be happy can't park her car in there, anymore stuff may not be able to walk though it  ;D

Will wait and see what you come up with probeinvert.

I assume my problem with the jog is i'm not zeroing or setting position's correct, maybe one of the global var's..

Gary

[ArtF]

Gary:

Ill let you know..


Art

[ArtF]

Gary:

  I didnt play with the script to figure out where its wrong, but I traced and coudl see whan the neg
button is pressed, it goes all that distance because the script is commanding it to.

I modified the script to test for sync as follows..

gcode  = "G91 G01 X.1"; switch to incrmental,
Engine.GCode(gcode);
gcode  = "G90";
Engine.GCode(gcode);  //switch back to absolute.

  and I used -.1 for the negative jog, all worked as I expected. The G91 makes it temporarily incrmental..

Id suggest you try making the jog using G91.. but what you have will work if the logic bug is sorted
out to figure out why the first press of neg goes to -2 after the last posative set it to 2.0 on a jog..

Art

[gburk]

Art

Thanks I Do think if I remember right that I tried G91 but I will double check and make sure,,

I also am sure you will figure things out.

Gary

[gburk]

Art

Went back and tried G91 again I didn't see any change's

I Still Think I'm Messing up on the way I am jogging up and then down, but that doesn't explain why the G90 and G91 are not jogging to different positions..

OK if I have a .0020 distance entered to move the X I hit the jog X+ it moves to .0020, now if I hit the jog X- it moves to -.0037 this is with G91
I ran the same script with G90 and they were exactly  the same values.

Gary

[gburk]

Art

I Think I Got jogging working, It was as I thought I was trying to make things way more complicated than need to be, so removed most of the global's
and just used the engine,gcode without trying any fancy stuff and it seems to jog correctly now..
The only thing I left in the script was reading the jog distance dro..

gary 

[ArtF]

Gary:

Yes, thats what I found, the error was somewhere in the script logic.

Just a note, and Im not sure this is it, but if you declare a global variable, you
dont need to global it again.. it may have no effect or it may screw up , Im not sure,
but globals should be declared as such, and then used as a variable..

Example:

global MyGlob = 0;

function foo( var )
{
  MyGlob = 6; //not "Global MyGlob = 6";

}

  Im not sure if using global again makes a duplicate variable or not.. Id have to check..

Glad its working though, sounds like almost all the weirdness is gone..



Art

[gburk]

Art

I will also check the globals, I think right now only thing is the probeinvert,1 backoff but works without it, but I got the impression from you that the 0 position could be closer than my results...

Gary

[ArtF]

Gary:

Well, the ProbeHit positions registers tell you the actual position of the hit. It then decelerates to zero speed.
So its all a function of speed. IF your moving very slow, the probe pretty much can stop instantly. If you
query the hit registers and do a g1 to that location, your about as accurate as you can get.

  So the routine should be

1) probe down.
2) If probehit is true, read hit registers and do a g1 to that location.


  Its probe condition at that point is unknowable, it may close or not depending on system flex,
tolerance etc... but thats about as accurate as you can get ..

Art

[gburk]

Art

Back to computer power shutting off while booting, think it may be that the water pump died I got into the bios for a few seconds  to I see the cpu temp going to 130 and raising them power shuts off..

any way I had copied all of auggies files and folders to a sd drive a couple days ago.
And I have an old laptop so I installed auggie and then copied all the files folders to laptop, but auggies configs are not being changed.

The steps are staying at installed version and not changing when I copy all the files over, what file stores this info..
I had all the steps set good I was getting very good travel distances, I really am hoping I don't have to recalibrate again..
Seeing I didn't write them down.. :-\

any suggestions..

Gary

[gburk]

Art

If I ProbeInvert,1 should that chance it from false to true in the planner config The ProbePolarity doesn't seem to change back and forth from false to turn,
always stays the same as you set it in the config.. so if I want to invert it to back off it doesn't seem to be inverting..

Not sure want you are seeing this but maybe that could be part of my back off problem..

I ran one line of code in the script window to ProbeInvert,1 and them checked the config it was still false.. don't know if you are updating the config on every change or not.. just a thought..

Gary