Art has recomended that IF you run into this problem Go to General config page and turn ON debug this run. THen try using the mdi many times to get the m3 to work. THen send them the file that mach generates to help them find the bugger that causes it.
(;-) TP
ART's instructions:
One thing you CAN do is , if the MDI problem occurs and things wont move,
select "Debug This Run" in config/general, then
try quite a few MDI commands. Close the program and show us the entries in the
..hmm, I think its called debug.txt or LastErrors.txt file in the mach3 folder.
Im not sure it will help, but the debugrun logging has allot more in it than
normal mode, so it may show a possible bug location. Also, on the Diags page of
the program is a queue depth DRO. Try several MDI moves, do they get queued and
just not execute, or do they not get queued.. in the end the more info we can
giev brian in that area, the faster he can zero in on a possability..
Thanks,
Art