I'm testing the new mach4 version 5325

I can get all mdi commands to run g31 g0 and all.

But a M6 T# doesn't seem to execute, i even created a M6 with only a messageBox() in it and that did not seem to run.
It also will not execute the M6 in a G code file when i try to run it, the g code will not run past the M6 line and the tool change led never lights up..
I notice the log file seems to be outputting a bunch of values in the that i have no meaning for maybe for mach4 testing values, but getting no errors  that i know of
I have ran the code in the lua script editor and it ran form there. also deleted the mcc files and let them be recompiled.

Any suggestion
Gary

Well... I am going to take a look at it now and I will inform Steve too... I will make a test!

Try 5327 instead of 5325.  I took 5325 down because it had some issues with system variables. 

This runs fine with 5327:
G20 G40 G80 G90
G00 X0 Y0
M6T1
G01 X1 F10
Y1
M6T2
X0
M6T3
Y0
M30


Steve

Hey, it's that Steve! 

Steve,

I tried 5327 i am getting the same results,
I did use the m6 macro that came with the mach4 install this time, to eliminate the macro..
I ran a G0 X1 and a G31 Z-1 in the mdi and they worked fine, i hit the probe and motion stopped.
But the M6 T# does nothing, ran a G Code file again and got struck on the first M6 command.

I switched to the simulator mode and the m6 works ok there..
I am using a smoothstepper.

Do you think i have a setting incorrect?. it was working a few versions back and i don't think i changed anything
I do see you made a few changes to these version's i looked at the screenload script and that has changed a lot..

Let me know what you think

Gary

I think if it works with Sim, then it should work with ESS.  Have you tried updating the ESS plugin?

Steve

Yes I have the latest plugin ver 309

I will mess with it some more later.

Gary

Hi Andy

I did some messing around with the 5327 ver and smoothstepper ver 309

I finally got the m6 to work with the mdi and gcode file.

But i am having some strange results, on the m6 lines. its seems to want to pick the next tool and not the one on the m6 line..
I a run the gcode it want to pick the the next tool change from the gcode, not always the m6 line it stops on so if the first m6 line looking for tool 13, and the next m6 line in the gcode has t4 on the m6 line it picks tool 4 as the tool change on the first m6 t13 line instead of t13 and the code will excite ok for here till it gets to the next m6 t4 now it thinks that t4 is already in the spindle so it doesn't stop and wait for the tool change.
Not sure if i am making any sense..
I am using the m6 macro that mach4 installed when i installed it and made no modes to it, and i am using the wx4 screen..
other than it seeming to be the wrong tool to change to the code will run and do its functions but without stopping for a tool change sometimes.

This is the first 3 tool change's in the gcode file if you see anything there that would cause the problem.

[
(SLICEHDMOUNTSPOTDRILL)
(EFFECTOR SLICE HOTEND MOUNT)
(T13  D=0.25 CR=0. TAPER=90DEG - ZMIN=-0.0394 - SPOT DRILL)
G90 G94 G91.1 G40 G49 G17
G20

(SPOTDRILL)
M5
T13 M6
S3000 M3
G54
M8
G0 X0.7162 Y0.0877
G43 Z0.689 H13
Z0.2953
G98 G81 X0.7162 Y0.0877 Z-0.0394 R0.1969 F6.
X0.374 Y-0.0878
Y-0.4815
X-0.374
Y-0.0878
X-0.7184 Y-0.1652
G80
Z0.689

(SLICEHDMOUNTLDXHOLES)
(EFFECTOR SLICE HOTEND MOUNT)
(T4  D=0.1339 CR=0. TAPER=118DEG - ZMIN=-0.6693 - DRILL)
(LDX HOLESDRILL)

M9
M5
T4 M6
S3000 M3
G54
M8
G0 X0.374 Y-0.0878
G43 Z0.689 H4
Z0.2953
G98 G83 X0.374 Y-0.0878 Z-0.6693 R0.1969 Q0.0138 F17.2
Y-0.4815
X-0.374
Y-0.0878
G80
Z0.689

(SLICEHDMOUNTLDOHOLES)
(EFFECTOR SLICE HOTEND MOUNT)
(T17  D=0.0984 CR=0. TAPER=118DEG - ZMIN=-0.6496 - DRILL)
(LDOHOLESDRILL)
M9
M5
T17 M6
S3000 M3
G54
M8
G0 X-0.7561 Y-0.1327
G43 Z0.689 H17
Z0.2953
G98 G81 X-0.7561 Y-0.1327 Z-0.6496 R0.2953 F4.7
X0.6785 Y0.1201
G80
Z0.689
/code]

thanks Gary
 

Andy,

Not sure if you are still checking this message.
But i was still having trouble with the m6 till a couple days ago, the only thing i have tried is that i was using the wx6 screen set, and a couple days ago i switched to the wx4 and haven't had a problem with the wx4, not sure if i had some sort of a glitch in the wx6 set or what but its working ok with the wx4 set

gary