reading Pokeys pins

[gburk]

Thanks art

Try to clear up the reboot.

When I exit and close out auggie, it looks like its closed but the profile identification dialog pops back up after auggie shuts down, it seems to reboot it on its own with the option to select your profile.. I never clicked on auggie to boot after closing it out..
If I select my profile and let auggie continue from here is what the scripts seem to get corrupted.

But if I exit the choose profile dialog now, its closes ok and if I wait a couple seconds and then reboot auggie double click auggie, the profile identification will display again, which it should I choose the profile and auggie loads and the scripts are running ok..

Just one more thing I only have to load auggie once, if it reboots itself and I continue the load form here, then the script that was in the scripter window will not work correct no matter how I load auggie after that..

Also I still think some problems still may be caused by where auggie thinks its axis position is, I seem to get the axis probing in the wrong direction after I do a manual jog and it doesn't move to entered distance when it does probe.

Also if I probe and it gives a backoff error the probe didn't reverse,  after this I get this error even if I jog off the part Zero the axis, then run probe again it seems to be stuck on the error it won't probe or move just get the backoff error message... seems like it may think the probe is still hit..

Hopefully this is a little clearer.

Gary

[ArtF]

Gary:

Thx. Unfortunately windows tries top restart a program it thinks hasnt shut down properly.
This seems to cause trouble.. the following can turn it off in Win7..

Advanced System Settings (under Control Panel > System and Security > System)
Click the Settings button under the "Startup and Recovery" heading.
Disable the "Automatically restart" checkbox.

  Now, I did see what I think was happening. IT put in the probing only recently for you
and it was a bit confusing how I did it. You set a probe polarity in the setup and if you
set a global variable called "ProbeInvert" it inverted that setting.
  The trouble is, I connected the probeinvert variable to the setting, so when Auggie
shutdown it might, if it shut down properly, reset your polarity setting.

  So it has changed. I will publish this week and post the change here. In the new version
you need to first go to config and set the new variable "ProbeLevel" to the state
of a normal hit. Test this by trying an MDI line for a probe. If the probe doesnt move
go back and change that setting. If the probe does move then the system variable is
set properly and nothing can change it except the config.

  The Global Variable ProbeInvert is now set to false on startup. It was remembered as
most globals are from run to run. This is true of your scripts as well by the way, if you declare
a global and need it to start at a set value, set it in the declaration or it will be set to
the last runs value. ProbeInvert however, will always start false. It will be remembered
for the run though. If you drop an LED on the screen and give it a variable name of ProbeInvert
you will be able to see if your script has set it properly. Id suggest always setting it true
or false before the probe call just to be sure its what your expecting. Dont set it, call the
probe and unset it immediately though, wait till the probe is done or at last moving before setting
ProbeInvert again.

  This may stop the seemingly random probe behavior and we'll go from there as to the scripts.
Ill try to get it out by Wed. or so. Im still looking for other possibilities.


Art
 

[gburk]

Art

I am running windows 10 it may be a challenge to set it not to restart on updates, there is no check mark for the option will check further..

As the probe invert in the config it seems to be set at its last state, so if its last state was true, it will be true when you reload auggie..

I have a probeinvert,0 before the first g31 and a block("MotionStill") after the g31, then a check to see if ( Globalget("ProbeHit") probe was hit
if it was I do another probeinvert,1 and then try to reverse the probe direction with a g31 till probe triggers, and another block("MotionStill").
This seems where the problem's happen doesn't want to reverse either stops there with probe triggered or plunges down..

I already had a LED on screen to check for the probe triggering also have one on the breakout board..
The led triggers but doesn't go off. when hitting touch plate.
now this problem is mostly with the touch plate, and as far as I can tell has a low signal till the tool touches it.

The touch probe seems to have a high signal till it touches the part, but this seems to work most of the time.

But I do still see a problem with the GCode run from the script after jogging and zeroing the axis not traveling to the correct distance just seems like the last jog is not clearing out.. and when I run the script if I have g01 z1 it ignores this value and runs to the last jog position. whatever it may have been seems that auggie may save this position sometimes when I reload auggie and run the script it will go to the last position before exiting auggie.. 

 

[gburk]

Art

May have come across the area where  running the jog button then zeroing the axis problem could be it seems like it jogs to the wrong position in user cord

It seems when I do a jog then zero the axis and then run the script, that it is now running to the machine cord and not the user

Zero axis then run script g31 z-1 only after the jog button and zero axis now it will run to 1 in mach cord but not in user, and then I reverse to 0 it go's to 0 in mach cord but not in user.

Just a thought

Gary

[ArtF]

Gary:

Thanks, Ill check it out.

Ive found a few problems so far, one was reading digital pins, one was probe syncing. Gcode syned properly
but it waits internally for the probe, scripts werent, I find under the new code, this makes it work properly synced.

GlobalSet("FeedMaster",0);
Engine.GCode("G38Z-10F50");
block("MotionStill");
Engine.GCode("G1X5");

  The block is necessary as the script doesnt know the other axis end positions for the g1x5 move.
The block makes sure its still, and that makes the end probe position sync up.

  The FeedMaster,0 is there because the reason your feedrate is sometimes not working is that
the feedrate override is sometimes not working right. Im working on it now as well. Setting
it to zero manually makes your program feedrates work. It may be late week before Im done,
I seem to have a found a nest of snakes Id like to kill in there..

Art

[gburk]

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

[ArtF]

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

[gburk]

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

[gburk]

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

[ArtF]

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

[gburk]

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

[ArtF]

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

[gburk]

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   

[ArtF]

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

[gburk]

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