HEIDENHAIN iTNC 530 Service Manual page 135

Hide thumbs Also See for iTNC 530:
Table of Contents

Advertisement

The PROFIBUS diagnosis described is mainly suitable for static failures.
Log files
An analysis of sporadic failures is thus difficult.
Experience has shown, however, that sporadic failures account for the mayority of PROFIBUS
errors.
For the analysis of sporadic failures special PROFIBUS log files are suitable which record
important events during start-up and run time.
All these files are saved in the path PLC:\PROFIBUS.
For analysis of a PROFIBUS error this file is read out from the control by the TNCremoNT and
are sent to your machine manufacturer or to a HEIDENHAIN service agency.
July 2010
PBCONFIG_FAIL.LOG
Protocol of the last start of the PROFIBUS system (if the start was aborted due to an error).
PBCONFIG_OK.LOG
Log recording the last successful start of the PROFIBUS system.
PBLOGBOOK.LOG
Log of the PROFIBUS system start indicating the software versions and possible errors.
The log is continuously added to.
As of 1 MB the contents is copied toPBLOGBOOK.LOG.OLD.
REPORT.TXT
Protocol of the last PROFIBUS start (will be overwritten during the next HSCI/PROFIBUS
start.)
REPORT_EXT.TXT
Saves diagnostic messages of the slave. The log is continuously added to, but it is limited to
approx. 1 MB. After the limit has been reached, the "old" diagnostic messages will be moved
to REPORT_EXT.TXT.OLD.
11 – 135

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents