Hello all,

I currently am working on a 6-axis CNC Router for applying a custom texture to lumber.  This morning I finally updated to the latest version of Mach3, I was running version D1.90.072.  The main intention of this update was to loose the lag between blocks (our program is 500 lines, repeated 3 to 6 times depending on the length of the board).  After the update I keep on getting "Please Wait...Generating Path" dialog box comes up, and will not finish.  The progress meter in the box is full, but it wont close.  If I hit cancel it goes away, and I am able to run the program just as normal. 

The program still runs great, the tool path comes up, and everything else works as it should.  Our operators have more of a problem with it than I do.

Anybody else have something like this happen?

Thanks in advance!

Ryan

Do you have any custom macros which are being called from your code?
Hood

There is a demo GCode in Mach3 that I believe says 'designs' which is actually about six different objects or designs within the program. 'Run from here' will not work with that demo program to separate out one of the designs. Appears that you must make the separation outside of Mach3 or edit all away but the one of interest and run each one independently -  OR -  Mach3 will not regenerate the chosen path within the whole. If your program contains all of the 500 line segments together, then that could be your problem.

WAC

Hope this helps - I observed this about Mach3 with the demo program and also another one of my own creation that was multiple independent programs in one presented program.

Do you have any custom macros which are being called from your code?

No I don't.  I even went as far as to remove the looping section (M98, etc) from the code and run just one pass.  I also removed the toolpath window from the screen.  Nothing seems to work.

Ryan

I probably use the run from here every day. WHat exactly is NOT working with it for you?

THe Please wait is shown to allow MACH to error check the code and setup the tool disp[lay path. IF you use a sub routine to loop through then MACH has to error check 500x6 lines of code sometimes it take a little while. IF you wait does it clear up on its own?


When you mentioned LAG between blocks can you describe this in more detail???

(;-) TP

THe run from here problem is a file problem not a MACH problem. Someone just took many file and made one large file . THe problem is they left in the M30 at the end of each file. When MACH sees the M30 it "ENDS program and resets like it is suppose to do. The run from here HAS to rerun all the mode settings to properly setup mach to continue from here(;-) So the M30 triggers amch to end program and reset.

If you want to use the program and run from here remove all the M30s from the middle of the program.

I am interested in the lag between blocks problem(;-) Normally Mach has to wait on the machine to process the holding cue where the movement commands are stacked up for the machine to run.

(;-) TP

THe run from here problem is a file problem not a MACH problem. Someone just took many file and made one large file . THe problem is they left in the M30 at the end of each file. When MACH sees the M30 it "ENDS program and resets like it is suppose to do. The run from here HAS to rerun all the mode settings to properly setup mach to continue from here(;-) So the M30 triggers amch to end program and reset.

If you want to use the program and run from here remove all the M30s from the middle of the program.

I am interested in the lag between blocks problem(;-) Normally Mach has to wait on the machine to process the holding cue where the movement commands are stacked up for the machine to run.

(;-) TP

I don't have any M30's within the program.  I only started seeing this when I upgraded.  I have a couple other program that close the dialog box automatically.  Just for fun I loaded Mach3 onto my development machine (Dual Zeon Quad Core @ 2.66ghz, 8gb ram), and I got the same problem. 

The lag I am talking about is there would be a momentary pause between blocks, I think it was because it was waiting for the motors to come to a complete stop. 

Thanks for all the help!

Ryan

Can you attach the code?
Hood

Sorry for the confusion I answered two questions at the same time.

Could you upload the problem file for us to see?

(;-) TP

I didn’t see you mention anything about "RUN FROM HERE" in your post but it was brought up.
To possibly help out I can tell you two way I am able to recreate your issue:

- You cannot "Regen" a toolpath after issuing a "Run From Here" till after the machine moves in to position (know issue).

- Always put "If (Isloading() = false Then" in your macros or Mach will read them while loading a file or a "RUN from Here".
There is now an option in the "Gen config" to ignore Mcodes while loading..but it best to have this in you Macros or any VB to make sure