GearHeads Forum

Ok Art

Thanks sorry, looks like I opened a can of worms.

Would you rather I  use the G38 over G31?

G38.2 G38.4 a little less coding my be able to eliminate the "ProbeInvert"

Gary

Gary:

  I may end up adding support for probe pullout, but Ill wait till I see what all these changes do.
I have recoded the sync after probe as well as sync after zero axis. Its a lot of changes so I may
just release it with this done to see how it reacts before I add more. Ill see if
I can get it out tomorrow or Wed.  Im getting much better results so far but Im only
running my own script tests, we'll see how you do.

Art

Ok Art

Thanks, was only kidding about g38.2 g38.4 got distracted by a gran kit running around and never got to add that to the message..

and forgot to go back and edit it oops..

not sure how different our scripts are but for the most part mine did work except for the touch plate probing... and jogging the zeroing axis..

I did try to fix the windows10 auto reboot, auggie still reboots after I close it sometimes not sure what else I can change in windows 10,
so far auggie seems to be the only program on my computer that does this..

and it does it on both computers I have it on they have different cpus one intel and the other amd, but both run windows 10


Gary

Art


GlobalSet("FeedMaster",0); I added this to the probe script, don't think it fix's the problem it a strange one I tried things differently this test..

I ran the z probe g31 z-1 F5 then retract to g0 Z+ZstartPos F30 it worked good in simulation, now instead of jogging, I manual entered a 0.1 in the Z axis DRO
then ran the probe again  it probed to 1 and retracted ok to 0.1 but the feed rates were off it showed 3.3 and then 33 on retract, so now I entered 0.2 in the dro
and the feed rate changed again now it was 6 and 36 on retrack.. strange that changing the DRO value would effect the feed rate..

Gary

Gary:

>>g0 Z+ZstartPos F30

  You mean you used g1 right? go wouldnt respect the feedrate, it would go full out
and just change the feedrate.

Art

Art

yep G1 and had another typo it was 5.3 not 3.3 Feedrate it was always a littler higher than the value I had in the engine,gcode..

Gary

Gary

Ahh ok. I had assumed the error was the one I foudn where sometimes the F word was
ignored. The LED on FeedMaster was out so it should have worked in the GCode
but was ignored.  This version has a lot of changes, should be out tomorrow and
we'll see how the syncing goes..

Art

Art

Of course I didn't think the whole feed rate thing though and said it only went higher, then I remembered I never tried it changing the DRO in the - direction so gave it a shot entered a -0.1 and the feed rate that had 5 in the gcode changed to 4.5 so it it does go down if you enter a neg value in the Z axis DRO..

Also I have noticed in the multi line mdi it only seems to run the first line for me..
I entered G0 X1 line 1 G0 Y1 line 2 but only line 1 runs no matter how may times I hit the Run button.

Gary   

Gary:

  I just uploaded version 3.65 , lets see how it does on all these things. Theres quite a bit
of new code and calls to ensure syncing in scripts. The only rule is the need for a block
on motionstill after a probe call. There is also a known bug that in GCode MDI you cannot probe
unless a G0 is the next move, this is being investigated.

  Be cautious, with this much code chang eI worry about unintended consequences...

Art

Thanks art

Will give it a shot tonight when it cools down alittle..

So no new script calls functions variables  just use what I have been using..

in the MDI I didn't use the probe call just the GO on each line and only would run the first line...

Gary