You are not logged in.
Pages: 1
Currently when there is a typo or data entry error in Vericut, the results can be unpredictable. It appears Vericut will read each address with NULL values as 0, set the register and wait. When there is a move later, even for another axis the -0- is executed.
Example, DPRNT was typed as BPRNT and the control was not set up for BPRNT. Each address B, P, R, N and T was set to 0. The B axis rotated to 0 later. Z also changed location in some cases. The results were very hard to track since they did not appear in the display for many lines later. Also when the errors are in Macro B subroutines, they may not be visible in the toolpath list.
These kind of data errors can take the average user hours to track down since the scrambling of the simulation is often many lines later.
We need some way to catch these errors. Rather than having a complex spell checker, maybe Vericut can be made to catch NULL entries for an address and warn when no value was entered. An EVENTS macro similar to the following outline.
MACRO "ErrorOnNull" {
OVERRIDE_VALUE 1 TEXT_OVERRIDE_VALUE "A B C D F H I J K L N P Q R S T U V W X Y Z"
}
The OVERRIDE_VALUE could determine if it is a warning, error etc. The TEXT_OVERRIDE_VALUE would list the addresses to check.
The Warning message would be similar to "MISSING NUMERIC DATA OR BAD WORD FORMAT"
Since the control has defined valid words, comment markers and text address & number combinations, spelling errors or missing numbers with text could be caught with this kind of macro.
Offline
6.2 added syntax checking utility for the NC Program. Should be able to catch these problems.
Offline
Pages: 1