Module Objective:
Module Description:
Content:
A007
Sinumerik OperateThe electronic logbook function of the 840D sl controller is used to enter data such as
manufac-turer (OEM), dealer and user information, 1st and 2nd commissioning dates as well as records of
service
visits.
This data is then saved to a log file. The log file has to be uploaded into the EUNA database via
the upload website.
The function is not only necessary for warranty issues but also for service personnel (Records of
new and previous service visits) and also for quality control measures.
Upon completion of this module the course participant will be able to do the following:
Import/Enter Logbook data
Make logbook entries
Save and load the log file using the Online Registration website.
Electronic Logbook
Logbook information
Importing/Entering Logbook data
1st Commissioning-Start-up Complete
2nd Commissioning-Machine Installed
Electronic Logbook: START Logbook information Importing/ Entering Logbook data 1st Commis-sioning- Start-up Complete 2nd Commis- sioning-Machine Installed Recording a Service Visit Saving the Logbook Data- identSNAP-SHOT Uploading to the Online Registration Website Electronic Logbook: END
Logbook Information
In the past, the validity of warranty claims was difficult to man-age and was the cause of delayed service response times. System/hardware faults were logged in paper logbooks which were then usually left on the machine and often became dam-aged or lost.
By using EUNA and the Electronic Logbook system, the war-ranty will automatically start, a record of the machine details and breakdowns will also be available on the controller. The time and date of each entry is recorded; it is impor-tant that the time and date settings of the controller are correct. Incorrect time and date settings can lead to early expiry of the warranty.
It is necessary to make entries at certain stages during the life of the machine:
- Manufacturer information at OEM
- Dealer information at delivery and installation of machine - End user information at delivery and installation of machine - 1st Commissioning - End of start-up at Manufacturer - 2nd Commissioning Machine installed - End of start-up at
end user - All service visits
Importing/Entering the Logbook Data
The OEM and Dealer information can be imported to the con-troller in three ways:
Import the XML file via the “Import” soft-key. (Preferred method)
Copy/paste the XML file in the “System data” area.
Type the information directly on the controller. (When the files are not available)The preferred method is to obtain the correct xml files from your Siemens contact partner. These are pre-populated files containing the relevant OEM/machine information etc. Using this method guarantees the consistency between the data stored in EUNA and the data stored on the machine. The following files can be imported:
The files are imported using the “Import” soft-key.
If the files are not available they can be created directly on the controller or offline on a computer.
Machine Identity File (identity.xml)
When the information has been imported the “identity.xml” file is automatically created which contains all the information from the imported xml files.
If data is already present in the logbook area and needs to be overwritten, then the identity.xml should first be deleted from the system.
The machine name/number is stored in General Machine Data 17400. This is individual to the machine and needs to be en-tered here.
File Function
oem.xml Manufacturer information
oemsubs.xml Manufacturer subsidiary information
dealer.xml Dealer information
user.xml End user information
ma_types.xml List of available machine types
identSNAPSHOT
When the information has been entered it needs to be saved, this is via a soft-key on the Logbook screen. This procedure will create a log file.
This is known as the “identSNAPSHOT” function and is a snapshot of the system including version data, cycle data, hardware components etc
Each time a logbook entry is made, the log file should saved and uploaded to the EUNA database via the Online Registra-tion Website.
The name of the file is made from a combination of the ma-chine name and system CF card serial number.
OEM Data oem.xml/oemsubs.xml:
Load via “Import” soft-key.
Concept for Electronic Logbook Data Import and Upload:
Dealer Data dealer.xml:
Load via “Import” soft-key.
User Data user.xml:
Load via “Import” soft-key.
OEM Data (identity.xml)
*Customer number* *Country* *Manufacturers name*
*Town*
Dealer Data (identity.xml)
*Customer number* *Country* *Dealers name*
*Town*
User Data (identity.xml)
Not usually available until point of sale.
Logbook entries
1st Commissioning 2nd Commissioning
Service visits
Export & upload Online Registration
Configuration data:
components, machine identity, licences, version information,
logbook entries etc. Offline preparation identSNAPSHOT-Controller
(identity.xml, MD17400) File upload
If the controller has existing machine identity data, it is necessary to delete the “identity.xml” file. The location of the file varies between systems operating with a PCU50 or NCU.
The location of the “identity.xml” file:
PCU50: System hard disk\F:\HMI\hmisl\user\sinumerik\hmi\data\version\identity.xml
Data Import function
The Electronic Logbook is located in the Diagnostics area of the controller:
Ensure that the files to be imported are available on the control-ler, network PC or USB memory device.
Select the location of the file to be imported, e.g. USB.
Select the file to be imported, e.g. oem.xml
The information will now appear on the screen. In this example the Manufacturer file (oem.xml) was loaded.
To see data for Dealer or End User select the relevant soft-key. Default Manufacturer screen with no data entered:
A machine name/number is compulsory.
Enter the machine name and/or number, e.g. VMC123. The value entered here is transferred to General MD 17400.
Machine type
The machine type can be manually typed at the same time as the name/number is entered. Alternatively a list of machine types can be viewed if the “ma_types.xml” has been imported. Example of an “ma_types.xml” file that has been edited to in-clude three machine types.
When the file is imported, the machine types will appear in the drop down list.
Copy and Paste Option
It is also possible to copy the files from USB/networked PC via the “system data” area using the copy and paste functions.
The controller now needs to be powered off/on. Cursor to the source containing the file e.g. USB device.
Locate the destination folder (Machine identity).
Once the choice of machine type is made it cannot be undone unless the “identity.xml” file is deleted.
Subsidiary files
Subsidiary files are used to define the details of manufacturer regional offices.
Example: A machine manufacturer has its head office in Ger-many, and also has regional offices in other countries, e.g. United Kingdom.
In this case, “oem.xml” would contain the details of the head office; “oemsubs.xml” would contain the details of the regional office.
When an “oemsubs.xml” file is imported to the controller, the “Manufacturer” soft-key is used to toggle between the OEM and OEM subsidiary data.
Example: Import the “oem.xml” and “oemsubs.xml” files as described previously.
The default screen displays the manufacturer data.
Select the “Manufacturer” soft-key to view the “oem subsidi-ary” data
No data will be displayed until an “Address selection” has been made. This is the name of the branch, i.e. the subsidiary.
Select the branch/subsidiary name; in this case “ABC SUB”
The subsidiary details will be displayed.
To return to the manufacturer details, select the “Reg. office of manufact.” soft-key.
This the original manufacturer soft-key with different text. The text of the soft-key changes depending on the current selected screen.
Templates for xml Files
Templates for the various xml files are available in the “HMI data\Templates\Examples\Machine identity” folder.
The templates can be used if the files cannot be obtained from the Siemens partner. They should be copied and edited to leave the original templates intact.
Example template for dealer.xml.
The file contains various xml commands but no dealer data.
Example: A “dealer.xml” file with dealer information. The file can be imported using the method described earlier.
Or Or
Example: Manually entered “End user” data.
Manually Entering Machine Identity Data
If the data has to be manually entered due to lack of an xml file, the data can be typed directly into the controller.
Select which data is to be entered; Manufacturer, Dealer, End user.
1st Commissioning-Start-up Complete
When the machine has been commissioned at the manufac-turer the “Start-up Complete” soft-key is selected. This auto-matically logs the current time and date.
To confirm that 1st Commissioning is complete. The information will appear on the main logbook page.
To confirm that 2nd Commissioning is complete.
The information is now added to the main logbook page
.
Recording a Service Visit
Whenever an engineer visits the machine to carry out mainte-nance etc, a record of the visit and information about the work carried out should be entered into the Logbook. To do this select the “New Entry” soft key.
The name and company/department of the engineer should be entered followed by a detailed description of the fault and work carried out.
2nd Commissioning-Machine Installed
When the machine has been installed at the end-user (2nd commissioning) the “Machine Installed” soft-key is pressed This automatically logs the current time and date.
The details of the service visit are now shown on the Logbook page.
The file is given a default name using details from the machine information page. This can be changed. A comment can also be added.
Two files are created by default, Version data and Configura-tion data.
The “Version data (.TXT)” file is a text file and contains details regarding the versions of the controller, drives etc.
The “Configuration data (XML)” file is an xml file and contains more information about the whole system including the log-book entries. It is this file which needs to be uploaded to the database via the internet.
Saving the Logbook data
The following procedure shows how to save the newly entered data to a file.
The file contains all information about the system (Controller, drives, software and hardware etc) as well as the information entered on the logbook pages.
The file should be saved to the default “Version data” folder as a standard procedure to ensure that a copy is locally available . The file is to be uploaded to the online registration website via an external PC, therefore it should also be saved to an external USB/CF device.
The information will now be saved.
In this example, the files are saved in the “version” folder. PCU50: System hard disk\F:\HMI\hmisl\user\sinumerik\ hmi\data\version
NCU: System CF card\user\sinumerik\hmi\ data\version
The save procedure should be carried out after each data entry in the logbook.
To save the data to a file first locate and select the “Save” soft-key.
The file can be opened for viewing in the “System data” area: The information that was entered via the Logbook screen is now stored in the xml file.
Uploading to the Online Registration Website
Use the copy/paste function to transfer the xml file to a USB stick in preparation for uploading to the Online Registration Website.
New Log Files
A new log file needs to be created when anything new is added to the logbook.
The file must then be uploaded to the EUNA database. The Online Registration website address is:
www.siemens.com/sinumerik/register
A language selection is available and an email address is required. Notification emails will be sent to this address if the “Enable email status notification“ option is selected.. To continue use the “Next” key.
Service visits are found at the end of the file:
Entering the email address and enabling the “enable email status notification” selection.
Continue with the “Next” button.
To upload the XML file select the “XML Upload” key.
Use the “Browse” key to locate the file.
The selected file is now ready to upload, select the “Upload” key.
Problems with uploading the XML files The “Action Bar” of the assigned files list is used for various
functions.
Refresh the page Upload an XML file View the file
Delete the file In the event of an error during the upload process will be
necessary to email the xml file to:
service.euna.industry@siemens.com
A007: END After a short delay an information box will indicate a successful
upload operation.
