You are not logged in.
MDI entries need to process sub programs called from G & M code definitions. MDI also needs to process sub programs when called directly in MDI. The machines do.
Currently, 6.1, when we have an M code defined in a .ctl file that calls a sub program, see below, MDI mode will not run the command. It ignores the sub program action.
Also when a sub program is called directly, G65P9024, it is also ignored in most cases of MDI processing.
To get MDI to work for sub program calls 1. You must have started a simulation, moved forward in the program. 2. then after you execute the MDI command G65P9024, you have to select the > command.
If the sub program is in a group of blocks in MDI and then all blocks are played, the sub program is ignored.
When using M90 in the MDI call, it just wont work.
It all works correctly when run from a program.
At times the NC Program position display gets lost, or jumps forward, when these kinds of commands are entered via MDI.
WORD_VALUE "M" "90" {
MACRO "NullMacro" {
TEXT_OVERRIDE_VALUE "Pallet shuttle"
}
MACRO "CallSubName" {
OVERRIDE_VALUE 9024
}
}
Offline
Slight modification. An Mcode calling a sub program will work if executed by itself in MDI. Must be done after starting the scan or nc program, executed in MDI then the selecting > will cause it to work. When run from a MDI group of commands, it is ignored.
In short I don't want my users to be Vericut machine building Experts to do something as seemingly simple as execute a M code in MDI mode.
Offline