Masso 4.02 Beta repeating cycle weirdness

[thewatchmker]

Cycle Runs fine, returns to zero and when i hit start, runs again fine.

But if i jog the spindle out of the way, then start. the machine crashes.

Uploaded File and video of it working properly, as well as it crashing. (Coordinates stay correct while crashing and violate soft limits.)

Machine is homed and soft limits work prior to running the program.

Also a weird thing that has happened a few time where i have to reload a program to get it to run after it running 1 cycle.

 

[breezy]

@thewatchmker

Couple of things

When you have run a program and wish to run it again, it should start if the end of the file has M30 that has been terminated with a CR/LF or New Line character, but a good habit to get into is to press the Rewind button before the Cycle Start, this ensures that the program is at the start of the file.

We need to see what is happening on the F2 screen when it crashes, not the crash.

Please do a screen dump of F2 & F4 after the crash. You will need to connect a keyboard to do this. Use the Print Screen Key or Ctrl + P.

Also supply PRINTABLE config text file.

Save & Load Settings

docs.masso.com.au

Regards,

Arie.

 

[cncnutz]

Hi TheWatchMker

Following in from the post related to this topic on https://www.masso.com.au/forums/topic/probe-not-changing-zero-and-erroring/?part=2#postid-17902

The error that was the biggest issue for me in the beta was that after a program was run it would return to home.

The comment you made was that one of the problems with the Beta version is that it returned to the home position after machining.
The reason it does this is that it the Gcode is telling it to do this and it doesn't matter if you use G28 or G53 to do it. If you don't want the axis to move to the home position after machining then don't tell it to go there.
If you can't turn it off in the post processor or define a finish location of your choosing , you could manually edit the last lines to move it to a more suitable location for your job especially if you are running a high number of the same job. Moving the Y axis 6 inches back from the part being machined would be more than enough to switch out the part and save a lot of production time.

There is nothing wrong with using G53 but my thought is that this is the cause of the jogging related crash.
I think adding a G54 just before the M30 would prevent a crash if the example was repeated.
The scenario you demonstrate is unusual so no one may have done this sequence before but even so it should not crash.
I have created a ticket to investigate this further.

Cheers Peter

 

[thewatchmker]

When I re download the beta, I ll try adding in a G54 and see if that solves it.

would be nice if that s all it was.

appreciate you opening a ticket. Sorry for so much work these last couple days but I really do appreciate the help.

@cncnutz

 

[cncnutz]

Hi TheWatchMker

I have now tracked down the issue that you had when jogging the machine.
It has nothing to do with the G53 or G54 or G28

It is actually the External cycle start button that is the problem.
If you use the on screen cycle start button it will work properly and walk the X,Y & Z axis back to the starting point before you jogged the machine and start from there.

If you use the External start button it doesn't walk back and continues as if it is back at it's starting point and crashes.

I have further investigation to do but that is the temporary solution at this time.

Thank you for pointing this out.
Cheers Peter

 

[thewatchmker]

Very interesting, glad you tracked it down and glad I could help.