Page 53 of 59

Re: reading Pokeys pins

Posted: Thu Nov 07, 2019 11:00 pm
by gburk
Art

Here is a couple logs the 2 that are have a name Norun were not run in the script run window, the other i did run a probing script first,
funny thing is it doesn't matter which probing script i run anyone seems to fix it them all..

Also not sure how you setup the prints, but the last print seems to run in a loop till i exit or estop auggie.

Gary.

Re: reading Pokeys pins

Posted: Fri Nov 08, 2019 12:13 pm
by ArtF
Gary:

New version uploaded to stop that loop.. Im still tracing the flow..

Art

Re: reading Pokeys pins

Posted: Fri Nov 08, 2019 12:50 pm
by ArtF
Gary:

Think I found it. My version was defaulting to feedmode of FEED/Min while yours was
defaulting to TIME_INVERSE , a strange mode thats used for constant speed. It was only partially
defaulting to that however, so it was making up weird feedrates depending on Z and spindle speed.

  Tended to only happen when a script Gcode was sent..

This version will either fix it or tell me why. Its online now.

Art


Re: reading Pokeys pins

Posted: Fri Nov 08, 2019 3:27 pm
by gburk
Art

Think you will be happy,
Ran 4 or 5 probes, and feed rates looked good
here is the error.txt file

Gary

Re: reading Pokeys pins

Posted: Fri Nov 08, 2019 9:04 pm
by ArtF
Gary:

Thx, it explains a lot. I run in debug mode for technical reasons here, it zeros variables. Release doesnt
and this particular value, FeedrateMode wasnt being init'd..

Ill keep my fingers crossed.

Art

Re: reading Pokeys pins

Posted: Sat Nov 09, 2019 12:02 am
by gburk
Art

I have ran it many times now, and not seeing any feed rate problems..
Will let you know how things look when i get the back off's working in the x and y, have it going in z will test x y tomorrow, I think the code I added for back off's is right, but you know how that go's.

>>
>> I guess one way is to check the pin status to see if its hit, I repaired that as well so if you ask
>>the digital level of that probe pin you should get the right answer, it was broken but now reports
>>if the pin is high or low.

forgot to reply to this, what i have been doing is testing pin19
    pinstate = Pokeys1.GetPinDig(19); 
    //print("Pin 19 Changed");
    GlobalSet("ProbeLED",1);
    block( "MotionPin19");
not the complete script but as far as i know it has not stopped working, i only use it to toggle the probe hit LED on or off..

is there a better or faster way ?.



Thanks
Gary

Re: reading Pokeys pins

Posted: Sun Nov 10, 2019 7:23 pm
by gburk
Art

I seem to be having another small issue i can't figure out

right now it the bore or hole probe

I have an 1.5" hole i set the bore size to 1.5 this probe's and centers great every time and ZERO's the axis's
I also tried a .75 hole also worked fine every time.

but if i have one that is to .5 or below after it centers a axis it should Zero it, but this is a hit or miss, it seems to always move to the center but doesn't set the axis to Zero
its random sometimes it doesn't zero the X and sometimes i't's the Y.
I tried a pause before setting the axis to Zero
also tried both  Engine.SetAxisPos( 0, null, null, null );  and GlobalSet("Axis1CurPos",0);  or Axis2 get the same results.

This one is real strange don't know why it messes up on the smaller holes...

Gary

Re: reading Pokeys pins

Posted: Sun Nov 10, 2019 9:22 pm
by ArtF
Gary:

    pinstate = Pokeys1.G etPinDig(19);
    //print("Pin 19 Changed");
    GlobalSet("ProbeLED",1);  // I suspect you meant ", pinstate" rather than ,1?

  No, looks good.

>>but if i have one that is to .5 or below after it centers a axis it should Zero it, but this is a hit or miss, it seems to always move to the center but doesn't set the axis to Zero

  Strange symptom. Does the zero button work afterwards to set the zero?

Art

Re: reading Pokeys pins

Posted: Sun Nov 10, 2019 10:13 pm
by gburk
Art

I think i figured it out for now, i'm thinking the smaller the hole maybe its moving things to fast and loosing track, just a thought

I never thought to lower the feed rates, they were set at 10 slow probe and 40 for g01 moves, that works good for the holes larger than .5 or so
So i lowered the feed rates to 5 for slow probe and 20 for g01 moves and this seems to have fixed the problem Axis's get set to Zero correctly at these feed rates..

I think you can kill the print's to screen now also.

Gary

Re: reading Pokeys pins

Posted: Fri Nov 15, 2019 2:03 am
by gburk
Art

xx = Engine.GetAxisPos(3); this seems to return a random number if the Z axis is set to 0.
if i set the Z to .5 it will return the correct value, just seems to return a bad number at or around 0.
the x (1) and y (2) are fine they will return a 0 correct number..

GlobalGet Axis3 works corrent returns a 0

Sorry figured it out had to convert ToInt now works...

Thanks gary