very true ger, I reproduced it hitting stop shifts the Zero over it did not happen with feed hold

Not sure if this has been reported but occasionally the display showing the tool paths that have been run by the machine does not line up with the toolpaths on the display.

The Mach4 screen editor is crashing on an hourly basis. You never KNOW what sets it off. A lot of times it is WHEN you go to SAVE that it crashes. AND that is a real treat to endure. When it crashes it locks Windows HARD requiring you to power it down then restart.

NOT good, (;-) TP

Build 2568 introduced a bug in the core that causes random crashes.

Build 2580 has just been posted and is supposed to include a fix.

http://www.pmdx.com/Downloads_Mach4/Mach4_Hobby_Releases/

Version updates, EVERYTIME I do a version update Mach4 DUMPS OUT all my setup info . I have to start over from scratch EVERY time.

yer that`s a pain fix it please

Make a copy of the Mach4Mill profile and use it instead.  That way, your settings do not get overwritten.

V2508 seems to have helped the Random crashing. BUT it introduced another bug in the SetVN  . The SetVN is reporting an error in the G code using #vars  EVEN though it was never called to define any named Vars UNLESS there is one hiding somewhere ??  We will get a View table to be able to SEE all the Named Variables that are created/associated. This example would be a good reason to have one.


Thanks, (;-) TP

Another glitch in the new function that reports the tool change status to the Mach4 status line. It is NOT reporting the status of the tools correctly ALSO the wording NEXT TOOL is wrong ,  that implies that it would be the NEXT TOOL in the Gcode file. The word that is correct would be Selected Tool.

Also the message itself should be standardized as to content   Selected Tool = 1   not == . And yes I know where that comes from.

NOW IT WOULD be nice to be able to see the next tool call in the gcode stack to be called (;-)  I can do it in Mach3.

(;-) TP

V2580  after a random period of time the toolpath stops responding to panning. All screen views are effected.  To make it work again I have to ether reload the screenset(stock) or load another screenset and it starts workiing again. THEN it works until it stops again.

It still has NOT crashed since I loaded V2580 (;-) Even in the screen editor it has not crashed out.

(;-) TP