Instead of opening every program by hand, the plugin checks a whole directory - or all files of the current session - in one run and collects every finding in a single report.
Checked files
- the active file in the editor,
- all opened *.LS files of the current session,
- all files found in a given directory - with a file filter and optional recursive search.
Only Folge, UP, Makro, Makrosps, Makrostep, Motn and Suchl programs are checked; for any other file type the plugin reports File type not supported and moves on.
The syntax check is started by the plugin itself, so it does not depend on the option Check programm syntax on load in the Fanuc configuration panel.
Options
- File filter - which files are taken from the search directory. Several patterns can be separated by a comma, for example folge*.ls,up*.ls,makro*.ls.
- Directory - the directory to be searched.
- Search recursively - include all subdirectories. Subdirectories whose name starts with @ are skipped.
- All opened *.LS files - check the files of the current session instead of a directory.
- Open file in editor if any syntax error occurs - every file with an error is opened in a new editor tab, so it can be corrected right away.
- Report warnings as well - besides the errors, the report also lists the warnings of the parser (uninitialized point, unknown tech command, a point whose UF/UT differs from the one of the program, unknown command in the APPL section, comment too long, payload out of range, inactive group, UP called inside a UP, recursive UP call). Switched off by default: in an otherwise correct archive the warnings can easily outnumber the errors.
- Compare block-to-block original and generated program (experimental) - in addition to the syntax check, the program is loaded once more through the Fanuc viewer and every line is compared with the line the viewer produces from it. Comments and differences in spacing are ignored, so what remains is a command that was read but not reproduced identically. Such lines are listed in the report under Command validation failed.
Report
The findings are not shown in a message window - a scan of a large directory produces far more lines than a dialog can display.
They are written to an HTML report: the file name, the line and the message for every finding. At the end of the run a short summary is shown - how many files were checked, how many errors and - if collected - how many warnings were found, and the report can be saved from there.
All options are stored and restored the next time the plugin is started.