Application description 11/2016 Converting Diagnostic pages https://support.industry.siemens.com/cs/ww/en/view/109474896
Warranty and liability Warranty and liability Note The Application Examples are not binding and do not claim to be complete regarding the circuits shown, equipping and any eventuality. The Application Examples do not represent customer-specific solutions. They are only intended to provide support for typical applications. You are responsible for ensuring that the described products are used correctly. These Application Examples do not relieve you of the responsibility to use safe practices in application, installation, operation and maintenance. When using these Application Examples, you recognize that we cannot be made liable for any damage/claims beyond the liability clause described. We reserve the right to make changes to these Application Examples at any time without prior notice. If there are any deviations between the recommendations provided in these Application Examples and other Siemens publications e.g. Catalogs the contents of the other documents have priority. We do not accept any liability for the information contained in this document. Any claims against us based on whatever legal reason resulting from the use of the examples, information, programs, engineering and performance data etc., described in this Application Example shall be excluded. Such an exclusion shall not apply in the case of mandatory liability, e.g. under the German Product Liability Act ( Produkthaftungsgesetz ), in case of intent, gross negligence, or injury of life, body or health, guarantee for the quality of a product, fraudulent concealment of a deficiency or breach of a condition which goes to the root of the contract ( wesentliche Vertragspflichten ). The damages for a breach of a substantial contractual obligation are, however, limited to the foreseeable damage, typical for the type of contract, except in the event of intent or gross negligence or injury to life, body or health. The above provisions do not imply a change of the burden of proof to your detriment. Any form of duplication or distribution of these Application Examples or excerpts hereof is prohibited without the expressed consent of the Siemens AG. Security information Siemens provides products and solutions with industrial security functions that support the secure operation of plants, systems, machines and networks. In order to protect plants, systems, machines and networks against cyber threats, it is necessary to implement and continuously maintain a holistic, state-of-the-art industrial security concept. Siemens products and solutions only form one element of such a concept. Customer is responsible to prevent unauthorized access to its plants, systems, machines and networks. Systems, machines and components should only be connected to the enterprise network or the internet if and to the extent necessary and with appropriate security measures (e.g. use of firewalls and network segmentation) in place. Additionally, Siemens guidance on appropriate security measures should be taken into account. For more information about industrial security, please visit http://www.siemens.com/industrialsecurity. Siemens products and solutions undergo continuous development to make them more secure. Siemens strongly recommends to apply product updates as soon as available and to always use the latest product versions. Use of product versions that are no longer supported, and failure to apply latest updates may increase customer s exposure to cyber threats. To stay informed about product updates, subscribe to the Siemens Industrial Security RSS Feed under http://www.siemens.com/industrialsecurity. Item-ID: 109474896, V1.1.0, 11/2016 2
Table of contents Table of contents Warranty and liability... 2 1 Task... 4 1.1 Overview... 4 1.2 Requirements... 5... 6 2.1 SIMOTION... 6 2.1.1 Activation of the web server... 6 2.1.2 Transfer of the diagnostic pages... 8 2.1.3 Implementation into user program... 10 2.1.4 Data structures... 10 2.1.5 Interconnection of parameters... 13 2.1.6 Visualization of the diagnostic pages... 14 2.2 SIMATIC... 15 2.2.1 Activation of the web server in SIMATIC Manager... 15 2.2.2 Activation of the web server in TIA Portal... 16 2.2.3 Generate and transfer diagnostic pages in SIMATIC Manager... 17 2.2.4 Generate and transfer diagnostic pages in TIA Portal... 19 2.2.5 Data structures... 21 2.2.6 Interconnection of parameters in user program... 24 2.2.7 Activation of user defined web pages... 26 2.3 SINAMICS... 27 2.3.1 Multi usage of websites... 29 3 Functionality... 30 3.1 Content of web pages... 30 3.2 Elements of web pages... 31 3.2.1 Variables... 31 3.2.2 Languages... 32 4 Related literature... 34 5 Contact... 34 6 History... 34 Item-ID: 109474896, V1.1.0, 11/2016 3
1 Task 1 Task 1.1 Overview Introduction For a proper operation of machines the right settings of process parameters is essential. The parameters are normally optimized while commissioning and are adapted while operation to the actual situation. The values of actual parameters can be monitored via engineering system or in the HMI. To have the possibility to check the values in the HMI it must be implemented while programming. This can cause a lot of user tags for the HMI which perhaps never been used in the HMI. Normally the end customer has no PC/PG with engineering system available so the diagnostic with engineering system is also not possible. Another possibility for the diagnostic is the use of the internal webserver of the controller. The actual versions of SINAMICS, SIMATIC and SIMOTION devices have a webserver implemented with access to the process parameters. Overview of the automation task Figure 1-1 The following picture shows an overview of the access to the process parameters. The web browser on the PC opens a web page which is stored on the web server of the device. The web page contains the graphical information and also JavaScript code for the cyclic access to the process parameters. The browser calls cyclically the access function and actualizes the graphical elements of the page. + M web browser Internet Explorer Firefox Chrome Call web page transmitt actualization actualization web server standard pages user defined pages access to process parameter Item-ID: 109474896, V1.1.0, 11/2016 4
1 Task 1.2 Requirements Web browser The converting diagnostic pages contain elements of type inline SVG. The following web browsers support inline SVG 1 : Table 1-1 browser Internet Explorer >= IE9 Firefox >= Firefox 4 Opera >= Opera 11.01 Chrome >= Chrome 10.0 Safari >= Safari 5.0 remarks Connection To access the web pages with process parameters an Ethernet connection to the device where the web server is running is necessary. NOTE Administrator rights are possibly necessary to call the web page and accordingly the access of the process parameters. These can be set at the configuration of the device. It is also possible that the access to the web pages is limited to one or more interfaces of the device. 1 Source: Wikipedia http://en.wikipedia.org/wiki/scalable_vector_graphics 2014-09-17 Item-ID: 109474896, V1.1.0, 11/2016 5
2.1 SIMOTION 2.1.1 Activation of the web server The web server of the device must be activated. This is the case if the device is in factory default settings. Since SIMOTION V4.4 the functions of the web server are adjustable. These settings you can do in the settings dialog of the device. This you can reach by double click the CPU in HW-Config. For the converting diagnostic pages at least the functions HTTP/OPC XML DA or HTTPS/OPC XML DA in case you want to have a secure connection is necessary. To transmit the pages via FTP to the controller this function must also be selected. Item-ID: 109474896, V1.1.0, 11/2016 6
For the data access and the FTP connection an administrator account is necessary. This can be with a dialog in the standard web pages. For more information please read in the documentation of SIMOTION of the topic SIMOTION IT. Take care that the user account you create has administrator rights. Item-ID: 109474896, V1.1.0, 11/2016 7
2.1.2 Transfer of the diagnostic pages Standard pages Files In the standard web pages of SIMOTION you have the possibility to transfer user defined pages into the file system. This happens in the dialog Files. NOTE The structure of the file system must be created manually. Use the button Create Directory. FTP Upload If the FTP functions are enabled in HW-Config it is possible to transfer the diagnostic pages via FTP connection. For this you can use a common FTP Client e.g. Filezilla. The pages will be stored directly into the storage medium of the SIMOTION device. Item-ID: 109474896, V1.1.0, 11/2016 8
To connect your client with the FTP server you need the IP Address of the connected interface of the SIMOTION and the user credentials of your administrator account. The connection starts in the root folder of the storage system of the SIMOTION device. Change the folder to USER/SIMOTION/HMI/FILES for the upload and transfer all pages including the sub folders. NOTE When you use the FTP Client FileZilla the folder structure will be created automatically. Simotion IT standard frame If the Simotion IT standard frame is used the application needs to be copied to USER/SIMOTION/HMI/FILES/Applications/Converting/Winder. Further information to the usage you can find in the documentation of the Simotion IT standard frame. Item-ID: 109474896, V1.1.0, 11/2016 9
2.1.3 Implementation into user program ST-Source The data for the web access are combined in the source dconitdiag. This source is part of the application in form of an xml export. This source contains global variables which are necessary for the web pages. The parameters are combined thematically and declared as an array of structures. This allows the usage of multiple instances of the winder. For this the array length is to adjust and afterwards the instances need to be connected to the winder blocks. The standard website contains a namespace which detects the length of the array automatically. The variables must be connected with the converting application afterwards. 2.1.4 Data structures sdrivevaluestype This structure contains drive related parameters. This structure is used by winder and line tension control. Tabelle 2-1 variable name data type description r64drivespeedsetpoint LREAL complete speed setpoint r64drivespeedactual LREAL actual speed of drive r64torqueactual LREAL actual torque of drive r64torqueprecontrol LREAL precontrolled torque r64torqueupperlimit LREAL upper torque limit of drive r64torquelowerlimit LREAL lower torque limit of drive slineaxisvaluestype This structure contains data for the material axis. This structure is used by winder and line tension control. Tabelle 2-2 variable name data type description r64linesetvelocity LREAL velocity setpoint of material axis r64lineactvelocity LREAL actual velocity of material axis measured r64linesetacceleration LREAL acceleration setpoint of material Item-ID: 109474896, V1.1.0, 11/2016 10
stensionvaluestype This structure contains data for tension controlled axes. This structure is used by winder and line tension control. Tabelle 2-3 variable name data type description r64tensionsetpoint LREAL tenson setpoint r64tensionsetpointrfg LREAL tension setpoint after ramp function r64tensionactual LREAL actual tension r64torquecorrection LREAL correction value of torque by technology controller r64speedcorrection LREAL correction value of speed by technology controller r64velocityoverride LREAL override value of velocity for torque control sdancervaluestype This structure contains data for dancer control. This structure is used by winder and line tension control. Tabelle 2-4 variable name data type description r64dancersetposition LREAL setpoint of dancer position r64dancersetpositionrfg LREAL setpoint of dancer position after ramp function r64danceractualposition LREAL actual measured dancer position r64speedcorrection LREAL correction value of speed by technology controller r64torquecorrection LREAL correction value of torque by technology controller sdiametervaluestype This structure contains data for diameter calculation. This structure is used by winder and line tension control. Tabelle 2-5 variable name data type description r64diameteractualvalue LREAL actual diameter value r64materialthickness LREAL webthickness (for diam addition mode) r64shaftspeed LREAL winder shaft speed r64materialvelocity LREAL web velocity Item-ID: 109474896, V1.1.0, 11/2016 11
variable name data type description r64winderposition LREAL winder position (just in mode positioning axis) r64externalsensorvalue LREAL measurement value of sensor sdrawvaluestype This structure contains data for draw control. This structure is used by line tension control. Tabelle 2-6 swinderwebvaluestype Variablenname Datentyp Beschreibung r64drawfactor LREAL draw factor between two axes This structure contains all data for winder axes. Tabelle 2-7 variable name data type description i32controlmode DINT set controller mode sdrivevalues sdrivevaluestype drive related values slineaxisvalues slineaxisvaluestype values of material stensionvalues stensionvaluestype data for tension controlled modes sdancervalues sdancervaluestype data for dancer controlled modes sdiametervalues sdiametervaluestype data for diameter calculation sltcwebvaluestype This structure contains all data for line tension controlled axes. Tabelle 2-8 variable name data type description i32controlmode DINT set controller mode sdrivevalues sdrivevaluestype drive related values slineaxisvalues slineaxisvaluestype values of material stensionvalues stensionvaluestype data for tension controlled modes sdancervalues sdancervaluestype data for dancer controlled modes sdrawvalues sdrawvaluestype data for draw control Item-ID: 109474896, V1.1.0, 11/2016 12
2.1.5 Interconnection of parameters Example winder The program source dconitdiag should be implemented in the interface part of the unit where the winder blocks are called. In that case local variables can be interconnected also. Variable interconnected to remarks i32controlmode <inst>.controlmode controlmode of winder instance sdrivespeedactual sdrivespeedsetpoint r64torquelowerlimit r64torqueprecontrol r64torqueupperlimit r64linesetvelocity <winder>.actordata.actualsp eed <winder>.actordata.totalsetp oint <winder>.torquelimitnegativ e.value <winder>.additivetorque.val ue <winder>.torquelimitpositive.value <line>.motionstatedata.setv elocity actual value of winder drive speed total speed setpoint of drive lower torque limit torque precontrol upper torque limit set velocity of material axis r64lineactvelocity tachovalue measured value of tachometer r64linesetacceleration <line>.motionstatedata.seta cceleration set acceleration of material axis r64tensionactual loadcellvalue measured value of load cell r64tensionsetpoint tensionsetpoint set value of tension r64tensionsetpointrfg fbtensionrfg.y output value of ramp funciton r64velocityoverride swinderconfig.r32override override velocity for torque controlled mode r64torquecorrection <winderfb>.controlleroutput output of TPID r64speedcorrection <winderfb>.controlleroutput output of TPID r64danceractualposition dancermeasvalue measured value of dancer position r64dancersetposition positionsetpoint set value of dancer position r64dancersetpositionrfg fbdancerrfg.y set value after ramp funciton r64speedcorrection <winderfb>.controlleroutput output of TPID r64diameteractualvalue <winderfb>.diameter diameter actual value r64materialthickness r64shaftspeed r64materialvelocity <winderconfig>.sdiamconfi g.r32webthickness <winder>.actordata.actualsp eed <lineaxis>.motionstatedata. actualvelocity web thickness actual shaft speed actual web velocity Item-ID: 109474896, V1.1.0, 11/2016 13
r64winderposition Variable interconnected to remarks <winder>.positioningstate.act ualposition actual position of winder r64externalsensorvalue <winder>.diamextval measurement value of sensor It is not necessary to interconnect all parameters. The interconnection depends on the settings of control mode. 2.1.6 Visualization of the diagnostic pages User s Area In the standard pages you can show the diagnostic pages in the working area by clicking to the link Users Area in the navigation menu. The web pages which are stored in the Files folder are shown in the selection bar above the visualization window. Standalone If the diagnostic pages should be shown without the standard frame the path to the file must be entered in the address line of the browser. The document root is USER/SIMOTION/HMI Example: http://169.254.11.22/files/winderexample.mwsl Alternatively you can implement a LOCALLNK to the file. How to create a LOCALLINK is described in the SIMOTION IT documentation. Item-ID: 109474896, V1.1.0, 11/2016 14
2.2 SIMATIC 2.2.1 Activation of the web server in SIMATIC Manager The activation of the web server of S7 300 and S7 400 devices in Step 7 can be done in HW-Config. For this open the settings dialog of the CPU and open the label Web. NOTE The cyclic actualization of the parameters is implemented in the JavaScript code of the web pages. That s why the automatic actualization is to disable. An administrator account is necessary to access the user defined pages and the process parameters. Item-ID: 109474896, V1.1.0, 11/2016 15
2.2.2 Activation of the web server in TIA Portal The activation of the web server in TIA Portal needs to be done in the properties menu of the CPU. Figure 2-1 A user with the following authorization is required to use the Converting Diagnostic Pages: Figure 2-2 NOTE You have to be logged on with a user with this authorization later! Item-ID: 109474896, V1.1.0, 11/2016 16
2.2.3 Generate and transfer diagnostic pages in SIMATIC Manager The diagnostic pages are part of the project in SIMATIC devices. Because of this the pages must be converted to DataBlocks. The SIMATIC Tool S7-Web2PLC converts the diagnostic pages. You can find it under the project in main menu under options. Please execute following steps in your project: 1. Create a new Web2PLC project: click to File and select New project. Enter the name for the new project. 2. Select under File the point Change Project Settings afterwards 3. Browse the folder where the diagnostic pages and all sub folders are stored in your file system. 4. Under the point Start HTML page you need to select the default page of your application. Item-ID: 109474896, V1.1.0, 11/2016 17
5. Optional you can enter a name for your application, shown in the web browser afterwards. 6. Select the label parser. Here you need to define the file extension for the files which contains AWP command. The extension.dat is to add in the field File types with AWP instructions 7. Close the dialog with OK and create the DB source. 8. Compile and load the source afterwards. NOTE Implement and compile the SCL Source dconitdiag before you generate the Web-DBs. This source creates the necessary data structures and data blocks with the process parameters for the web pages. Item-ID: 109474896, V1.1.0, 11/2016 18
2.2.4 Generate and transfer diagnostic pages in TIA Portal The diagnostic pages are part of the project in SIMATIC devices. Because of this the pages must be converted to data blocks. The block generation will be done in the properties menu of the PLC. Figure 2-3 Execute the following steps to generate the data blocks for your device: 1. HTML directory: Select the folder where the Web pages and all sub folders are stored. NOTICE Dependent on the storage capacity of the SIMATIC PLC, not all control mode web pictures (e.g. W_loadCellMAdapt.xml) can be generated and transferred to the PLC. If there is too less capacity, the compiler will show a warning after generating the web server blocks and compiling the project. In this case not used control mode web pictures (xml files) should be deleted from the folder DATA before generating the blocks. 2. Default HTML page: Select the default page e.g. ControlStructure.mwsl. 3. Application name: Set a name for the application e.g. Converting. 4. Files with dynamic content: Add the extension.mwsl 5. Web DB number: the number defined here need to be entered in the variable DBNumber in LCon_Data_ITDiag 6. Generate the data blocks. Item-ID: 109474896, V1.1.0, 11/2016 19
After the generation of the blocks, the data blocks are part of the program blocks in the project: program blocks/system blocks/webserver and will be downloaded with the project. NOTE The web pages need to be generated and downloaded every time you make changes at the files. For S7-15xx devices you need to switch from Stop to Run to access the new pages. Item-ID: 109474896, V1.1.0, 11/2016 20
2.2.5 Data structures The necessary PLC data types are provided in the folder LCon_Types in the global TIA library LCon. WinderITDiagValuesType This structure contains all data for winder axes. Tabelle 2-9 variable name data type description i32controlmode DINT set controller mode i32diammode DINT set diameter mode sdrivevalues sdrivevaluestype drive related values slineaxisvalues slineaxisvaluestype values of material stensionvalues stensionvaluestype data for tension controlled modes sdancervalues sdancervaluestype data for dancer controlled modes sdiametervalues sdiametervaluestype data for diameter calculation SectionalDriveITDiagValuesType This structure contains all data for sectional drive axes. Tabelle 2-10 variable name data type description i32controlmode DINT set controller mode sdrivevalues sdrivevaluestype drive related values slineaxisvalues slineaxisvaluestype values of material stensionvalues stensionvaluestype data for tension controlled modes sdancervalues sdancervaluestype data for dancer controlled modes sdrawvalues sdrawvaluestype data for draw control Item-ID: 109474896, V1.1.0, 11/2016 21
sdrivevaluestype This structure contains drive related parameters. This structure is used by winder and line tension control. Tabelle 2-11 variable name data type description r64drivespeedsetpoint REAL complete speed setpoint r64drivespeedactual REAL actual speed of drive r64torqueactual REAL actual torque of drive r64torqueprecontrol REAL precontrolled torque r64torqueupperlimit REAL upper torque limit of drive r64torquelowerlimit REAL lower torque limit of drive slineaxisvaluestype This structure contains data for the material axis. This structure is used by winder and line tension control. Tabelle 2-12 variable name data type description r64linesetvelocity REAL velocity setpoint of material axis r64lineactvelocity REAL actual velocity of material axis measured r64linesetacceleration REAL acceleration setpoint of material stensionvaluestype This structure contains data for tension controlled axes. This structure is used by winder and line tension control. Tabelle 2-13 variable name data type description r64tensionsetpoint REAL tenson setpoint r64tensionsetpointrfg REAL tension setpoint after ramp function r64tensionactual REAL actual tension r64torquecorrection REAL correction value of torque by technology controller r64speedcorrection REAL correction value of speed by technology controller r64velocityoverride REAL override value of velocity for torque control Item-ID: 109474896, V1.1.0, 11/2016 22
sdancervaluestype This structure contains data for dancer control. This structure is used by winder and line tension control. Tabelle 2-14 variable name data type description r64dancersetposition REAL setpoint of dancer position r64dancersetpositionrfg REAL setpoint of dancer position after ramp function r64danceractualposition REAL actual measured dancer position r64speedcorrection REAL correction value of speed by technology controller sdiametervaluestype This structure contains data for diameter calculation. This structure is used by winder and line tension control. Tabelle 2-15 variable name data type description r64diameteractualvalue REAL actual diameter value r64materialthickness REAL webthickness for addition mode r64externalsensorvalue REAL measurement value of sensor sdrawvaluestype This structure contains data for draw control. This structure is used by line tension control. Tabelle 2-16 Variablenname Datentyp Beschreibung r64drawfactor REAL draw factor between two axes Item-ID: 109474896, V1.1.0, 11/2016 23
2.2.6 Interconnection of parameters in user program DB LCon_Data_ITDiag The data block LCon_Data_ITDiag contains the variable instance that is interconnected with the. NOTE Always index [0] is used for gaswinderitdiagvalues and gassectionaldriveitdiagvalues Table 2-17 Variable Data type Description DBNumber DB_WWW Start number of the data blocks generated for the web server. The number can be defined during the generation of the blocks; described in the chapters above. Afterwards it can be find out in Program blocks System blocks Web server InstanceNumberWinder Int Winder instance which is being displayed at the diagnostic page. InstanceNumberSectionalDrive Int Sectional drive instance which is being displayed at the diagnostic page. gaswinderitdiagvalues gassectionaldriveitdiagvalues ARRAY of WinderITDiag ValuesType ARRAY of SectionalDriv eitdiagvalue stype Variables for interconnection with the winder function Variables for interconnection with the sectional drive function OB ITDiag This example OB contains the variable connection of the winder and sectional drive data to the Diagnostic Pages variables. NOTE The actual data always need to be connected to index [0] of gaswinderitdiagvalues and gassectionaldriveitdiagvalues. The following table shows exemplary the connection for the winder variables: Item-ID: 109474896, V1.1.0, 11/2016 24
Variable interconnected to remarks i32controlmode < winder >.controlmode Control mode of winder instance to select the respective drawing for the web site r64danceractualposition <winder>.cntrlactual measured value of dancer position r64dancersetposition positionsetpoint set value of dancer position r64dancersetpositionrfg <winder>.cntrlsetpoint set value after ramp function r64speedcorrection <winder>.pidoutvalue output of TPID r64diameteractualvalue <winder>.diameter diameter actual value r64diamsensorvalue sensorvalue measure value of sensor r64materialthickness <winderconfig>.webthickne ss web thickness sdrivespeedactual <winder>.actshaftspeed actual value of winder drive speed sdrivespeedsetpoint <winder>.setdrivespeed total speed setpoint of drive r64torqueactual <winder>.drivetorqueactual Actual torque value of the drive r64torquelowerlimit r64torqueprecontrol r64torqueupperlimit <winder>.instdrivecontrol.lo wertorquelimit <winder>.instdrivecontrol.tot altorqueprectrl <winder>.instdrivecontrol.up pertorquelimit lower torque limit torque precontrol upper torque limit r64lineactvelocity r64linesetacceleration r64linesetvelocity <lineaxisdrivecontrol>.spee dactual <lineaxissetpointchannel>.a cceleration <lineaxissetpointchannel>.s etvelocity measured value of tachometer set acceleration of material axis set velocity of material axis r64speedcorrection <winder>.pidoutvalue output of TPID r64tensionactual <winder>.cntrlactual measured value of load cell r64tensionsetpoint tensionsetpoint set value of tension r64tensionsetpointrfg <winder>.cntrlsetpoint output value of ramp funciton r64torquecorrection <winder>.pidoutvalue output of TPID r64velocityoverride <WinderConfig>.overrideVel ocity override velocity for torque controlled mode NOTE The interconnection of the sectional drive values follows the same rules. Item-ID: 109474896, V1.1.0, 11/2016 25
2.2.7 Activation of user defined web pages In SIMATIC devices the System function WWW needs to be called cyclic to initialize the web server and synchronize the user defined web pages with the user program in the CPU. This function can be called in the free cycle or in a time OB. For SIMATIC 300/400 devices it is recommended to call this function in a time OB, for 12xx/15xx the OB1 or a cyclic interrupt OB can be used. Item-ID: 109474896, V1.1.0, 11/2016 26
2.3 SINAMICS Activation of the Web server In the default settings the webserver of the SINAMICS device is not active. You can enable it while configuration or afterwards by right click the device in the project navigator. Figure 2-1 Item-ID: 109474896, V1.1.0, 11/2016 27
Figure 2-2 NOTE Make sure that for each user a password is defined to protect your application. Upload of user defined pages In the standard pages of the SINAMICS web server a page to upload user defined pages is available. For this you must be logged in as user SINAMICS or Administrator. Item-ID: 109474896, V1.1.0, 11/2016 28
2.3.1 Multi usage of websites Figure 2-3 If more than one instance of winder should be monitored via websites the standard website WinderExample.mwsl needs to be copied. The namespace for each file is to set to the referred drive object. Further information of the namespace you find under 3.2.1. After logging in it is possible to create the folder structure and upload the files to the server. Another possibility to transfer the web pages is to copy the files with help of a card reader to the storage medium of the device. The data must be stored in the Folder OEM/SINAMICS/HMI/USERFILES. Item-ID: 109474896, V1.1.0, 11/2016 29
3 Functionality 3 Functionality 3.1 Content of web pages Data structure The web pages contains of one file which provides a frame for the visualization of the controller structure. In this file an initialization sequence is included to adjust the target system. The JavaScript File communication.js sets the communication settings based on the settings in the initialization part. The work flow in general is as following: 1. Detection of controller mode: In the first step one parameter of the controller is read which defines the controller mode of the application. 2. Load data object: Depending on the read value for the controller mode a picture file will be load by the JavaScript code. This picture is in form of a scalable vector graphic SVG stored in the file system. 3. Detect variables The file contains next to the graphical elements information of the used variables. These information will be concluded to a collection and read cyclic from the controller. The values will be used to display the actual values in the graphical part. 4. Language settings: Further information in the file is the language depending texts. These are as the other information stored in XML tags in the file. The application checks the browser settings and sets the language depending on the browser settings. Is the detecting language not included in the file English will be set. Display element The display element will be added depending on the actual values. For this an object Element will be implemented in which the SVG data will be loaded. The display element will be added just one time to the web page. Because of this the page needs to be reloaded if the controller mode changes. Item-ID: 109474896, V1.1.0, 11/2016 30
3 Functionality 3.2 Elements of web pages 3.2.1 Variables Structure of the XML Tags For the variables a XML-node named variables is implemented directly under the root node of the XML file. The structure of this is shown in the following graphic. Figure 3-1 Variable tag Graphic tag <vspeed> <provider>simotion</provider> <varname>r32drivespeed</varname> <unit>1/min</unit> <type>float</type> <sinamicspar>63</sinamicspar> <simaticpar>drivespeed</simaticpar> </vspeed> - Drive Speed 123.45 1/min Variable source vspeed Textelement ID = vspeed The relation between the display and variable is set by the tag name of the variable. In the graphical part is one element with ID vspeed this text node will be adapted depending on the read value of the variable. Node plattform description provider SIMOTION OPCXML provider varname SIMOTION OPCXML var name (as prefix the namespace will be used) sinamicspar SINAMICS parameter number of DO simaticpar SIMATIC name of file which contains the access information unit all displayed unit type all information for the display format Item-ID: 109474896, V1.1.0, 11/2016 31
3 Functionality Namespace The variable destination is defined by the variable information in the xml tag and additionally a namespace can be used. For SIMATIC variables the namespace is not available. The namespace is as the target system adjustable in the main html file. Example: Table 3-1 namespace variable provider (just SIMOTION) SIMOTION unit/dglobal / element to read gr32speed SIMOTION Variable gr32speed in of program unit dglobal of SIMOTION - to/achse_1.motionstatedata.actual Velocity SIMATIC nicht möglich SINAMICS SIMOTION Variable actualvelocity of Technological objekt Achse_1 globvars.r32speed - Variable r32speed in DB globvars SERVO_02 63 - Parameter 63 of drive object SERVO_02 - SERVO_03.61 - Parameter 61 of drive object SERVO_03 The namespace is at SIMOTION and SINAMICS optional. This must be can be set to the common part of the variable name of all variables. 3.2.2 Languages Structure of the XML Tags The information of the language depending texts are concluded in one xml tag named language. The structure is similar to the variable node. This is shown in the following graphic. Item-ID: 109474896, V1.1.0, 11/2016 32
3 Functionality Language Tag Graphic tag <lactualspeed> <english>drive Speed</english> <deutsch>drehzahl</deutsch> <francais>vitesse</francais> </lactualspeed> - Drive Speed 123.45 1/min Language information lactualspeed Textelement ID = lactualspeed The application reads in the initialization step the content of the variable node and adds every found language to the language selection box. At first start of the application the browser settings are read to set the default language of the application to the read settings. If the language setting is not found in the XML file English will be set as default language. Extension The language elements are easy to extend. For this just a new text with surrounded with a tag of the new language is to add. For example: <mylanguage>mytext</mylanguage> After reloading the application in the web browser mylanguage will be selectable in the language selection box. Item-ID: 109474896, V1.1.0, 11/2016 33
4 Related literature 4 Related literature Table 4-1 No. Topic \1\ Siemens Industry Online Support https://support.industry.siemens.com \3\ Link to this entry https://support.industry.siemens.com/cs/ww/en/view/109474896 \2\ 5 Contact Siemens AG Digital Factory Division Factory Automation Production Machines DF FA PMA APC 2 Frauenauracher Str. 80 91056 Erlangen Germany mailto: tech.team.motioncontrol@siemens.com 6 History Table 6-1 Version Date Modifications V1.0 09/2014 First version V1.0.1 03/2015 Interface extension for diameter detection V1.1.0 11/2016 Updates of diagnostic pages for SIMOTION and SIMATIC Item-ID: 109474896, V1.1.0, 11/2016 34