Messages

11

Mach4 General Discussion / Re: Feed Hold in MDI Window hangs up mach 4?

« on: August 03, 2019, 06:03:20 AM »

Filed a Ticket to Newfangled.

12

Mach4 General Discussion / Re: Feed Hold in MDI Window hangs up mach 4?

« on: August 03, 2019, 05:57:31 AM »

Yes, this would be options.

But this "Fix something during milling" usecase is way more convinient in other software.
For Example in bCNC Stop button does what in Maach 4 the "Feed Hold" Button does.
But you can just press start again after this and everything just continue.

Also on Mazak machines feed hold is working that way.
If you have to stop the spindle, coolant or move the cutter away, there is a dedicated "Restart" button to start the programm from the last Feed hold position.

Haas Machines further more store the last position of feed hold when jogging. Then there is a "Jog Return" Button, followed by Cylce start to continue the program.

Also Mach 3 based machines like Tormach even use feed hold for the door switch sensor and just continue after closing doors and press cycle start.


But all those super fancy features are not even expected in Mach 4 Hobby... Only to do a defined operation for all G-/M- Codes and not for "all but with the exception of one not". It just doent make sense to interrupt all other Gcodes but not G4.

13

Mach4 General Discussion / Re: Feed Hold in MDI Window hangs up mach 4?

« on: August 03, 2019, 04:20:38 AM »

This is not really an option, because after stop you can not continue your programm.
Spindle will not start again, colant will not flow again ....


So if this is true what you say, then mach 4 has no way to reliable pause a program in order to fix something and then continue the program... This is even in all the open source software like GRBL/bCNC,... possible and an absolute must for professional machining. You can not loose a part all the time when a miner issue happen. Nor can you restart the complete program from beginning after such changes. Nor can you all the time create custom "Finish this part" Program for all stop locations...

14

Mach4 General Discussion / Re: Feed Hold in MDI Window hangs up mach 4?

« on: August 03, 2019, 02:55:51 AM »

This is a critical safety issue in my opinion.

Imagine you hit feed hold during a G4 to manual fix something - for example adjust the cooling nozzle or vacuum device.
You can not tell if the machine still is stopped due to the G4 or the Feed hold, you see only it is not moving and can not tell the difference.

So you manipulate on your device and the machine starts running again out of the sudden.
You can loos fingers or your hand/arm with such behavior.

Pause or stop need to be really reliable to stop the machine from harming or killing you...

15

Mach4 General Discussion / Re: Feed Hold in MDI Window hangs up mach 4?

« on: August 03, 2019, 02:37:20 AM »

Thank you for your test and confirming that you also see this bug there with G4 in MDI.
Would be interesting to see, if this also happen if the G4 ist in a gcode file.
Unfortunately I can not test this for 2 weeks, because of vacation .

So this seems to be really a bug in the core or in the ESS Plugin, because expectation would also be to pause the pause.
Any idea how to find out if this is related to the Plugin or the core?
And how to submit this bug report then?

16

Mach4 General Discussion / Feed Hold in MDI Window hangs up mach 4?

« on: August 02, 2019, 09:22:09 AM »

Hi,

Feed hold is working fine in gcode files.
But if I enter something very simple like:

M3 S3000
G04 p5000
M5

And Press "Feed Hold" during this G4 - Mach will not offer the "Cycle Start" Button to be active as usual when pressing feed hold.
Also spindle keep running forever, the complete program hangs.
Even when exiting Mach 4 - it can not be started again because a "Mach 4 GUI" Process is still running as seen in the task manager. You have to manual quit this task with windows task manager and start complete mach 4 again.

Using Mach 4 with ESS.

17

Mach4 General Discussion / Re: No GCode Movement after pressing stop

« on: May 03, 2019, 05:24:58 AM »

You are absolutely right about bad practice.
But for savety reasons, there should not be a tool thrown around if the operation presses a bad practice button.

By tests i proved, that stop is not exiting m6 script.
Stop will only terminate the current mcCntlGcodeExecuteWait and continues in the script.
So you must check for estop, stop,... each second line in your script.


I solved it by checking the coordinates after mcCntlGcodeExecuteWait if this was executed successful.
Found no ther way to test if stop was called.

If coordinates ware wrong - I exit m6 script.
This also solves the "no movement possible" problem.

Stuck in M6 seems not to be a detectible machine state, it sais still idle, even stucking in middle of m6 lua.

18

Mach4 General Discussion / Re: No GCode Movement after pressing stop

« on: May 03, 2019, 03:36:23 AM »

The state shows "Idle" in that case.

But Im shure it depends on m6.
I think the current "mcCntlGcodeExecuteWait" is skipped and the next instruction still executed.
This means - the current tool it thrown all over the workshop in some cases, because the clamp opens in wrong position. -> Very very very bad.

How to check if stop was pressed before the next command?
How to cancel m6 if stop is pressed?
Why gcode is no longer working, in idle state, but stuck in middle of m6 execution?

19

Mach4 General Discussion / Re: No GCode Movement after pressing stop

« on: May 02, 2019, 02:35:57 PM »

Not now, its in the middle of the night.
Will do it tomorrow in the workshop. Promised.

20

Mach4 General Discussion / Re: No GCode Movement after pressing stop

« on: May 02, 2019, 01:25:47 PM »

Thank you for all the input.
Im using Stop as a intermediate, when something goes wrong but no estop is needed.


I found out, that mach 4 ist stuck in the m6 script.
I think stop only breaks the current Gcode execution and the script continues to run.
Might that be true?

How to check in the script, if stop was called?
I check already for extop each logical block.