reading Pokeys pins

[gburk]

Small world kirt

I'm in cape coral near pine island off burnt store road nw cape...

Hoping we don't get hit, last one we had was a lot of flooding, and as usual they don't know exactly the direction its going..


Gary 

[ArtF]

Gary:

  Thx for the test. I see what you mean , Ill do some tests and see why that is so
and attempt a repair.

  Your step numbers show you should move in .000625 intervals. Ill check mine
to see how it matches. I usually just use single line mdi to do incremental jog,
I assume your DRO is just tied to a G1 move button for the dro incrment?

Art

[ArtF]

Gary:
 
  I think Ive found our main issue. When reading Gcode there is a strict ordering
condition for execution of the queue, but that function was broken badly , I just didnt
see it as Gcode is restricted in order in other ways. Your scripts show it more clearly.

  Commands meant to be in order were being shoved to the bottom of the queue, instead
of to the top. This means when MotionStill consition was required, the command was simply
postponed to last and the next command allowed to execute.

A new version will be posted in a few minutes with this corrected. Let me know what you see
as a result. This affected everything from dwell to toolchanges so its a pretty dramatic change.

To test your problem I used


Engine.GCode( "g1x10" );
Engine.GCode( "g04P4" );
Engine.GCode( "g1y10" );
Engine.GCode( "g1z10" );

  The dwell happened after the x,y,z moves. (They did happen one after the other though..)

With the fix the dwell occurs after the X move. As this affects most operations, use caution but I suspect
it fixes a great many script ordering functions and troubles youve had.

Ill post when fix in online.

Art

[ArtF]

Gary:

Fix is online.

  Let me know how its works out. In regards to a previous question about order
of motion with the x,y and z, you shouldnt need any yields or blocks in that
question, three gcode lines following each other should move only 1 at
a time without any special consideration. Put a dwell between them if the
motions are short as a test. If they are small moves then its possible the DRO's
will all update at once, thats a matter of DRO timing, but the motion of the z
should have always ended before that x,y move. We may need to take
another look at that one.

This version should fix all manner of other errors though on your probing
and toolchanging issues..

Art

[Mooselake]

Small world kirt

I'm in cape coral near pine island off burnt store road nw cape...

Hoping we don't get hit, last one we had was a lot of flooding, and as usual they don't know exactly the direction its going..


Gary   

So anything we don't bring inside might end up in your yard?  Hope the latest forecast is right and it head up the east coast, will know around Monday.  This is our first hurricane here, and my first since about 1972 in Houston; that one went elsewhere and we only got some heavy rain, 24 inches in 24 hours iirc.

Never been this close to another Gearotic user, other than visiting Tweakie on a trip to England some years back.  We should think about getting together.  I'll try and remember to PM you after the storm is past

Kirk

[gburk]

Sounds good

I have been though 4 here the last one had the most flooding, it does look like we may get lucky on this one right now, but you are right won't be sure till Monday at some point..

I use a few of the cnc software, mach3 mach4 auggie, just a fun and frustrating hobbie at times also have a couple 3d printers..

Gary

[gburk]

Art

this is how I am exiting the toolchange dialog
I removed all yields and blocks and put in looks like a pause..

this is called before the dialog saving the current positions and setting up the gcode to return to pos.

    GcodeReturnToPos[0] = ("G90 G01 X"+GlobalGet("Axis1CurPos")+" F20");
    GcodeReturnToPos[1] = ("G90 G01 Y"+GlobalGet("Axis2CurPos")+" F20");
    GcodeReturnToPos[2] = ("G90 G01 Z"+GlobalGet("Axis3CurPos")+" F20");

this is the close dialog
but before I closed it I may have jogged the axis's to make tool change then moved the Z down to re touch off top of part and set Z to Zero
now I want to return to start positions, they all do move back to start but all at the same time, I want to make sure the Z has moved first even has finished its move before x or y move I don't want to chance the tool dragging on the part..
Make more sense?

global MyToolChangeClose = function()
{
print("Exiting Manual Tool Change");
//print("Z position= "+GcodeReturnToPos[2]);
Engine.GCode(GcodeReturnToPos[2]);
Engine.GCode( "g04P4" );
//yield();
//block("MotionStill");
//print("Z position= "+GcodeReturnToPos[0]);
Engine.GCode(GcodeReturnToPos[0]);
//yield();
//block("MotionStill");
//print("Z position= "+GcodeReturnToPos[1]);
Engine.GCode(GcodeReturnToPos[1]);
//yield();
//block("MotionStill");
};

update
I tested it again and upped the P to 5000 and I just don't see any pause or wait time..

Also tested not being called from the dialog, ran the code in the script window and it was fine I may not even have needed the dwell pause ran each enging.gcode before the next one and it paused at the end of the first engine.gcode so it waited a few after finishing to run the next line of engine.gcode..

So to me it has something still to do with the dialog box code doesn't seem to want to pause or wait for the p4 at all and still Executes all the engine.gcode at the same time 

Thanks Gary

[ArtF]

Gary:

Thx, much clearer. Ill try it in the closeDialog and see why its screwing up..

Art

[ArtF]

Gary:

  It was the jogging. In the context of running Gcode, the system was assuming the last point reached
was the last Gcode call. The next Gcode call would be from that point. When you jogged it displaced the
known coordinates to plan from. Try this new version online now one and see if its better. If
you jog, the Gcode pointer is updated to the new coordinate after the jog completes.

Art

[gburk]

Art

Ok jog seems better as the dros but I think my mind is in a fog, and I am not getting the script code right.. so I am attaching the panel and scripts for jogging and the toolchange plus dialog... gcode moves seem the same from closing the dialog... I sure your mind is sharper that mine is right now, seems like everthing I touch breaks Starting to think SSR relays don't last replaced 3 in two weeks and need another, even bought a couple form automation direct thinking they would be better, nope both bad, wiring is correct they worked the way I have them wired for a couple weeks...

Also I think anything jog below 0.0005 will not update on the DRO ...

Thanks gary