Transcription

1 High-performance measured value acquisition via Oversampling SIMATIC ET Measurement technology Siemens Industry Online Support Unrestricted

2 Warranty and Liability Warranty and Liability 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 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 Entry ID: , V1.0, 07/2017 2

3 Table of Contents Table of Contents Warranty and Liability Introduction Overview Mode of operation Prerequisites Boundary conditions Components used SIMATIC ET200 for Oversampling and system limits Hardware setup Hardware configuration (HWCN) Default settings Activating PROFINET IRT with isochronous mode Activating oversampling Programming Accessing the address space at oversampling Isochronous application for capturing measured values Display of measured values and filling of measurement data memory Integration into the user project Operation Annex Service and support Links and literature Change documentation Entry ID: , V1.0, 07/2017 3

4 1 Introduction 1 Introduction 1.1 Overview The scalable and highly flexible peripheral system SIMATIC ET 200 serves to link process signals to a higher-level controller. Via the High Speed Version (HS) of the peripheral modules, process values can be captured quickly and also output. With the SIMATIC ET 200 peripheral system, this allows a realization of metrological applications in conjunction with a SIMATIC controller, e.g. for in-line testing. The following figure shows the process automation and the so-called in-line testing station combined in just one SIMATIC station. Figure 1-1 Production (SIMATIC) Test station (Mess-PC) Production line SIMATIC PLC upgrade if needed Additional decentral HW (ET 200) Production (SIMATIC) Test station (SIMATIC) Production line During the in-line testing, the measured data are captured cyclically within the production line. The measured data can be used for process control and Quality of Service. This allows a quick response to process changes in order to ensure the quality of the manufactured products and stabilize the production process. To efficiently transfer the process values to a controller, the High Speed peripheral modules not only support very small send clocks, but are also able to quickly capture and buffer measured values in time equidistant sub clocks. The buffered measured values are sent as data packages to the controller during each send clock. This functionality is called oversampling. The advantage is that with an inexpensive SIMATIC controller (e.g. S7-1515), measured values can be captured or output with high performance. Frei verwendbar Entry ID: , V1.0, 07/2017 4

5 Siemens AG 2017 All rights reserved 1 Introduction 1.2 Mode of operation An HS peripheral module of the ET 200 product family can sample and buffer several measured values during a send clock. In this, the PROFINET send clock is divided into time-adequate sub clocks. The buffered measured values are transmitted to the controller as data package. The figure below shows the oversampling functionality. Figure 1-2 Analog input signal Oversampling value capturing send clock PROFINET IRT IRT IRT IRT IRT Application (OB sync ) OB6x OB6x OB6x OB6x application cycle It should be noted that the measured values within a send clock are captured and buffered in the analog module (e.g. 15 measured values in 750 µs at a sampling rate of 50 µs). In the following clock, the buffered measured values are transmitted to the interface module (IM) and one clock later, they are transmitted to the IO-Controller via PROFINET IRT. The use of oversampling requires an additional send clock before the measured values can be processed in the controller (OB6x). The following figure shows the oversampling with a parametrizable oversampling factor of 15. In this example, 15 measured values are captured within a PROFINET send clock. Figure 1-3 value capturing send clock Frei verwendbar Entry ID: , V1.0, 07/2017 5

6 1 Introduction 1.3 Prerequisites To activate oversampling for an HS peripheral module, the following conditions must be fulfilled: Decentralized structure PROFINET IRT Isochronous mode The controller (OB6x) and the IO modules work completely isochronously. This guarantees that the sampling rate can be accurately kept to the millisecond and that no values get lost. For this, the data need to be processed in the OB6x or copied to the measured values memory. In a configuration with oversampling in the cycle run group (OB6x), do not use reduction (application cycle = send clock). This way, you can ensure that the processing of the measured data in the CPU s user program can be performed isochronously with the acquisition on the peripheral module. 1.4 Boundary conditions The following boundary conditions need to be observed: Minimum PROFINET send clock at oversampling is 250 µs. The smallest possible sub-clocks at oversampling are: o o 50 µs during read-in 35 µs during output The number of sub-clocks can be set, ranging from 2 to 16. (depending on the number of channels and the send clock, see also Table 1-2). 1.5 Components used This application example has been created with the following hardware and software components: Table 4-5 Component Numbe r Article number SIMATIC CPU PN 1 6ES AM01-0AB0 FW V2.1.0 SIMATIC ET 200SP IM155-6PN HF SIMATIC ET 200SP AI 2xU/I 2-/4-wire HS SIMATIC ET 200SP AQ 2xU/I HS SIMATIC STEP 7 Professional V14 SP1 (TIA Portal) 1 6ES AU00-0CN0 FW V3.3.1 (High Feature) 1 6ES HB00-0DA1 FW V2.0.1 (High Speed) 1 6ES HB00-0DA1 FW V2.0.1 (High Speed) 1 6ES Automationsoftware For this application example it is recommended to use at least a SIMATIC CPU PN, as the application cycle is set to 750 µs. Entry ID: , V1.0, 07/2017 6

7 1 Introduction With an oversampling factor of 15, the minimum sampling rate of 50 µs on the analog High Speed input module can then be reached. Figure 1-6 PROFINET IO This application example consists of the following components: Table 1-7 Component File name Documentation _Application_Oversampling_V1_0_de.pdf This document STEP 7 project _Application_Oversampling_V1_0.zap14 V14 SP1 1.6 SIMATIC ET200 for Oversampling and system limits Table 1-1 Product family ET 200SP ET 200MP The following table shows the ET 200 interface modules that support the isochronous mode. In the column, note the minimum send clock when using oversampling. Component Article number Min. Send clock IM155-6PN HF (High Feature) IM155-6PN HS (High Speed) IM155-5PN ST (Default) IM155-5PN HF (High Feature) 6ES AU00-0CN0 250 µs - 6ES AU00-0DN0 125 µs For oversampling, the min. send clock is = 250 µs. 6ES7155-5AA00-0AB0 6ES AA00-0AC0 250 µs For oversampling, the min. send clock is = 1 or 2 ms (depending on the oversampling factor, see Table 1-2). The oversampling function can only be used in a decentralized setup via PROFINET. In a central setup in conjunction with an ET 200SP CPU or an S CPU + ET 200MP (without IM), the oversampling function cannot be used, since the backplane bus does not support the isochronous mode. Entry ID: , V1.0, 07/ Frei verwendbar

8 1 Introduction Table 1-2 Product family ET 200SP ET 200MP The following table shows the analog High Speed peripheral modules that support the oversampling function. Component Function FW Max. Oversampling factor AI 2xU/I HS 6ES HB00-0DA1 AQ 2xU/I HS 6ES HB00-0DA1 AI 8xU/I HS 6ES NF10-0AB0 AQ 8xU/I HS 6ES HF00-0AB0 ±10V, ±5V, 0..10V, 1..5V, ±20mA, 0..20mA, 4..20mA ±10V, ±5V, 0..10V, 1..5V, ±20mA, 0..20mA, 4..20mA ±10V, ±5V, 1..5V, ±20mA, 0..20mA, 4..20mA ±10V, ±5V, 0..10V, 1..5V, ±20mA, 0..20mA, 4..20mA V channel: µs 2-channel: 8 V channel: µs 2-channel: 8 45 µs V2.1 8-channel: 16 (min. send clock = 1 ms) V2.1 8-channel: 16 (min. Send clock = 2 ms) 8-channel: 16 (min. send clock = 1 ms) Min. Sampling rate 62.5 µs 125 µs Table 1-3 Product family ET 200SP ET 200MP The following table shows the digital High Speed and time-based IO peripheral modules that support the oversampling function. DI 8x24VDC HS 6ES BF00-0DA0 DQ 4x24VDC HS 6ES BD20-0DA0 TM TIMER DIDQ 10X24V 6ES CG00-0BA0 TM TIMER DIDQ 16X24V 6ES AA00-0AB0 Component FW Max. Oversampling factor Min. Sampling rate V µs V µs V (not parameterizable) V (not parameterizable) DI: µs DQ: 100 µs DI: µsec DQ: 100 µs When using a digital output with the oversampling function, make sure that the combination of application cycle and the output 32bit sequence do not result in an output frequency that exceeds the maximum switch frequency. Maximum switch frequency: At resistive load: 10 khz At lamp load: 10 Hz NOTICE Overheating of unsuitable loads A high-speed output generates edges with a high degree of steepness. During a connected load, this allows high-energy charge reversals that may overheat the load at very high switch frequencies. This is why the connected load must be suitable for high input frequencies. Entry ID: , V1.0, 07/2017 8

9 1 Introduction The oversampling function for digital I/O modules will not be described in the following chapter. The engineering corresponds to the analog I/O modules. Entry ID: , V1.0, 07/2017 9

10 2.1 Hardware setup The figure below shows the device and network overview of the project example. Figure 2-1 Table 2-1 Component SIMATIC CPU PN SIMATIC ET 200SP IM155-6PN HF PLC-750usec PN device name PLC-750usec.ET200SP-HF To simulate an analog input signal, a sine curve (50 Hz and ±10 V) is generated via the analog output module. Oversampling is also used for this, with the following parameters: Output rate of 16 times per send clock Output interval of µs (Output interval = 750 µs / 16). Connect the analog output and input module with each other. Frei verwendbar Entry ID: , V1.0, 07/

11 2.2 Hardware configuration (HWCN) Default settings The individual steps to connect a PROFINET IO device to a SIMATIC controller are explained in the following table. For the assignment of names, it is recommended to use DNS-compliant characters (only a-z, 0-9, minus signs and period, no blank spaces). Thus, the configured name in TIA Portal matches the converted PN device name (see Device properties > Ethernet addresses > PROFINET ). In configured PN device names, capital letters are also allowed, however, on the device, it will be saved in lower case letters. With a., you can create several labels in the PN device name (see example above in Table 2-1 <PLC>.<Station name> ). Table 2-2 Action Description 1. Add the controller and the decentral ET 200 station. For the example project, an S with firmware as of V2 is required, since a program block uses arrays with variable array limits (Array[*] of type). 2. Assign the corresponding PN IO controller (PN-IO interface) to the ET 200 station. 3. Switch to the topology view and configure the PROFINET network topology. This configuration is needed for PROFINET IRT. Entry ID: , V1.0, 07/

12 Action Description 4. Go to the device view of the controller. Open the settings of the PROFINET interface and define the send clock (e.g. 750 µs) under "Real time settings" > "IO communication. The sync master and the sync slave for the PROFINET IRT communication (sync domain) will later be set automatically by TIA Portal, after the activation of the the isochronous mode. Alternatively, a SCALANCE X-200IRT can also assume the role of the synch master. This setting can also be done via Domain settings. A sync domain allows only one sync master, but several sync slaves. Entry ID: , V1.0, 07/

13 2.2.2 Activating PROFINET IRT with isochronous mode Table 2-3 Action The individual steps to connect a PROFINET IRT communication and isochronous mode are explained in the following table. Description 1. Add the OB6x that is processed isochronously with the PROFINET IRT send clock (application clock = PN IRT send clock). Here, the metrology application will later be called up to store the measured values clock synchronously in a measurement data memory (DB). The OB6x is needed in advance, in order to be able to accurately configure the isochronous peripheral modules (see action 3). For performance reasons, it is recommended to use the programming language SCL. Entry ID: , V1.0, 07/

14 Action Description 2. Activate the isochronous mode for the corresponding peripheral modules at "Isochronous mode" > "Detail overview. Entry ID: , V1.0, 07/

15 Action Description 3. For all isochronous peripheral modules, select the organization block (OB6x), with which the peripheral modules work isochronously. For this, mark the corresponding peripheral module and select the OB6x at "Input 0 1" > "I/O addresses, in which you would like to update the corresponding part process image. Also note, to which (part) Process image the isochronous peripheral modules are assigned to (e.g. PIP 1). This number will later be needed during the programming of the OB6x. Entry ID: , V1.0, 07/

16 2.2.3 Activating oversampling Table 2-4 Action The table below shows how to activate oversampling. Description 1. Activate oversampling at the analog High Speed peripheral module. For this, select the corresponding peripheral module and define the sampling rate under "Module parameters" > "AI configuration" > "Sampling rate. If a sampling/output rate of greater than 1 is set, the maximum input or output range per channel is occupied: e.g. for the analog input module AI 2xU/I 2-/4-wire HS with the maximum sampling rate 16, 32input bytes in the peripheral address area are occupied per channel as soon as the "sampling/output rate" is greater than 1. Entry ID: , V1.0, 07/

17 2.3 Programming Accessing the address space at oversampling Table 2-5 Action The table below shows how to access the measured values, if you use oversampling. Description 1. To actually and symbolically access IO addresses, a PLC data type typeoversampling (Array[0..15] of Int) has been defined. At a sampling rate of 15, only rawvalues[0]..rawvalues[14] are written with IO data. Unused IO addresses return the value 16#7FFF. Therefore, in the example, rawvalues[15] always returns the value 16#7FFF (32767) at a sampling rate of 15. Entry ID: , V1.0, 07/

18 Action Description 2. Create the corresponding PLC tags for the analog input and outputs. ( PCL tags ) an. For analog inputs and outputs that use the oversampling function, you can use the selfdefined typeoversampling data type Isochronous application for capturing measured values For isochronous applications, the part process image for the inputs and outputs is usually updated according to the IPO model: 1. Reading the Inputs 2. Processing 3. Writing the Outputs To update the part process image for the isochronous inputs, the SYNC_PI system function is first called up in the OB6x. After that, the program is processed (the user program). To update the outputs, the SYNC_PO function is called up in the end (see Figure 2-4). For a detailed description of the IPO or OIP model, please refer to the TIA Portal online help or the SIMATIC PROFINET with STEP 7 V14 manual: Entry ID: , V1.0, 07/

19 Figure 2-2: Program blocks of the example application In the following, the SCL program is described, which is called up in OB61 to copy the measured values to a measurement data memory ( MeasurementData.values ). With the CopyAnalogValuesToArrayOfReal function, the analog values are scaled and copied to the measurement data memory. At the beginning of the OB61 organization block, the related part process image is explicitly updated ( SYNC_PI ) and at the end of OB61, the isochronous outputs are written accordingly with the part process image ( SYNC_PO ). In OB61, the SinusGenerator function block with the SinusGenerator_DB instance is also called up. With this FB, a sinusoidal signal is generated and output at the analog analogoutput_1 output. For testing purposes, this signal can be read in at the analog analoginput_1 input. The SinusGenerator block is not dealt with further in the following. Figure 2-3: Synchronous cycle [OB61] - block interface In OB61, temporary tags are used for calling up the SYNC_PI and SYNC_PO system functions. tempdint tempword You can evaluate these return values in the user program (see online help SYNC_Px ). In the example program, these tags are not evaluated. Entry ID: , V1.0, 07/

20 Figure 2-4: Synchronous cycle [OB61] 1 #tempdint := SYNC_PI(PART := 1, FLADDR => #tempword); 2 3 IF "Global".enableMeasurement THEN 4 #tempword := "CopyAnalogValuesToArrayOfReal"( 5 rawvaluemax := 27648, 6 rawvaluemin := , 7 valuemax := 10.0, //in [V] 8 valuemin := -10.0, //in [V] 9 oversamplingfactor := 15, 10 srcarrayrawvalues := "analoginput_1".rawvalues, 11 destarrayofreal := "MeasurementData".values, 12 pos := "MeasurementData".nextIndex); IF #tempword = 16#8382 THEN 15 //The value at the #pos parameter is outside the limits of the array "Global".enableMeasurement := false; 18 "MeasurementData".nextIndex := 0; 19 END_IF; 20 END_IF; //create test signal for analog input 23 "SinusGenerator_DB"( 24 enable := TRUE, 25 frequency := 50.0, //in [Hz] 26 amplitude := 10.0, //in [V] 27 rawvaluemax := 27648, 28 rawvaluemin := , 29 valuemax := 10.0, //in [V] 30 valuemin := -10.0, //in [V] 31 oversamplingfactor := 16, 32 executioncycle := #SyncCycleTime, 33 rawvalues => "analogoutput_1".rawvalues); #tempdint := SYNC_PO(PART := 1, FLADDR => #tempword); In the example program, the measurement data memory MeasurementData.values has been implemented as array, not as ring buffer. With every new positive edge of the Global.enableMeasurement tag, the measurement data memory is filled once. If an element is addressed outside of the array limits, the CopyAnalogValuesToArrayOfReal function returns the return value 16#8382 (see online help on Serialize system function > Input/Output tag POS ). If the measured values are faultlessly copied to the measurement data memory, the CopyAnalogValuesToArrayOfReal function returns the return value 16#0000. The interface of the CopyAnalogValuesToArrayOfReal function will be explained in the following. Entry ID: , V1.0, 07/

21 2.3.3 Display of measured values and filling of measurement data memory With the CopyAnalogValuesToArrayOfReal function, the analog values are scaled and copied to a measurement data memory. The following input parameters serve to scale the raw value which is transmitted in S7 format. The input parameters are described in the following figure: rawvaluemax rawvaluemin valuemax valuemin Figure 2-6 physical value 100 % raw value (S7 format) 100 % For example, 10 V ( physical value ) correspond to 100 %, which equates to a raw value of V, for example, correspond to -100 % which equates to a raw value of (see also chapter on analog value display in the respective periphery manual, e.g. AI 2xU/I HS). Figure 2-5 CopyAnalogValuesToArrayOfReal [FC1] - block interface For the example project, an S with firmware as of V2 is required, since the CopyAnalogValuesToArrayOfReal function uses arrays with variable array limits (Array[*] of type). Frei verwendbar Entry ID: , V1.0, 07/

22 Figure 2-6: CopyAnalogValuesToArrayOfReal [FC1] 1 #CopyAnalogValuesToArrayOfReal := 0; //No error 2 3 #tempmaxindexarrayofreal := UPPER_BOUND(ARR := #destarrayofreal, DIM := 1); 4 5 #tempmaxindexrawvalues := LIMIT( 6 MN := 0, 7 IN := #samplingrate - 1, 8 MX := MAX_OVERSAMPLING_INDEX); 9 10 //check array limits 11 IF #tempmaxindexarrayofreal < (#pos + #tempmaxindexrawvalues) THEN 12 #CopyAnalogValuesToArrayOfReal := 16#8382; 13 //The value at the #pos parameter is outside the limits of the array //check if input pos is within the array 16 IF #pos > #tempmaxindexarrayofreal THEN 17 RETURN; 18 ELSE 19 //modify max index of raw values 20 #tempmaxindexrawvalues := #tempmaxindexarrayofreal - #pos; 21 END_IF; 22 END_IF; #tempoffset := (#valuemax + #valuemin) / 2.0; #tempgradient := (#valuemax - #valuemin) / DINT_TO_REAL(#rawValueMax - #rawvaluemin); FOR #i := 0 TO #maxindexrawvalues BY 1 DO #destarrayofreal[#pos] := #srcarrayrawvalues[#i] * #gradient + #offset; #pos := #pos + 1; END_FOR; The measurement data memory is transmitted to the function via the InOut parameter destarrayofreal (destination array) and as array with variable array limits. With the UPPER_BOUND system function, the actual upper array limit is defined. For this function, the measurement data memory must be a zero-based Array of Real. You can freely adjust the data type of the array in consideration of the resolution or the accuracy. Depending on the oversampling rate ( samplingrate ), the measurement data memory is filled with an FOR loop. Further details can be found in the source code (see Figure 2-6). Entry ID: , V1.0, 07/

23 2.4 Integration into the user project The CopyAnalogValuesToArrayOfReal function and the typeoversampling data type can be coped in your TIA Portal project via drag & drop. For this, it is recommended to work with the Reference projects view. Open the view by ticking the checkbox Reference projects under View. Open the supplied example project in the Reference projects view. Now, you can copy the blocks and data types in your project via drag & drop. Working with a second TIA Portal instance requires more system resources. Figure 2-7 For the application example, an S with firmware as of V2 is required, since the CopyAnalogValuesToArrayOfReal function uses arrays with variable array limits (Array[*] of type). Entry ID: , V1.0, 07/

24 2.5 Operation Table 2-7 Action The start of the measurement value acquisition is initiated with a positive edge of the Global.enableMeasurement tag. In this regard, it is to be noted that this tag is automatically reset in the program example as soon as the measurement data memory is full. 1. Select the tag you wish to control (1). Description 2. In the context menu, select Modify operand... (2). The Modify dialog box opens. 3. At Modify value: (3), enter the respective value you would like to set. 4. Confirm the entry with OK (4). The measured values are stored in the MeasurementData.values data block (see Table 2-8). Recording these measured values with TIA Portal Trace is unfortunately only possible to a limited extent. With oversampling, several measured values are transmitted to the controller as data package during each send clock. This data package cannot be displayed in a continuous trace. You can, for example, copy the measured data into an Excel file. The time axis (time value) can be defined in Excel in accordance with the sampling rate (see following table). Entry ID: , V1.0, 07/

25 Table 2-8 Action Description 1. Open the MeasurementData data block and generate a snapshot (1). This requires an online connection. The snapshot is located in the work memory of the S7. 2. You can select all values by double-clicking the Snapshot column (2). 3. Copy these values and paste the 1000 measured values into an Excel table. 4. The time axis (column A) can be created depending on the sampling rate (e.g. 50 µs). Alternatively, the measured values can also be sent to a PC via a TCP file server. This requires adjustments in the C# source code of the TCP file server. For further details on the TCP file server, please refer to TCP file server application example: Entry ID: , V1.0, 07/

26 3 Annex 3 Annex 3.1 Service and support Industry Online Support Technical Support Do you have any questions or need support? Siemens Industry Online Support offers access to our entire service and support know-how as well as to our services. Siemens Industry Online Support is the central address for information on our products, solutions and services. Product information, manuals, downloads, FAQs and application examples all information is accessible with just a few mouse clicks at Siemens Industry's Technical Support offers quick and competent support regarding all technical queries with numerous tailor-made offers from basic support right up to individual support contracts. Please address your requests to the Technical Support via the web form: Service offer Our service offer comprises, among other things, the following services: Product Training Plant Data Services Spare Parts Services Repair Services On Site and Maintenance Services Retrofit & Modernization Services Service Programs and Agreements Detailed information on our service offer is available in the Service Catalog: Industry Online Support app Thanks to the "Siemens Industry Online Support" app, you will get optimum support even when you are on the move. The app is available for Apple ios, Android and Windows Phone. Entry ID: , V1.0, 07/

27 3 Annex 3.2 Links and literature Table 1-2 No. \1\ Siemens Industry Online Support Topic \2\ Link to the entry page of the application example Change documentation Table 3-4 Version Date Modifications V1.0 07/2017 First version Entry ID: , V1.0, 07/