PRELIMINARY II 1.7.2010 Commissioning a project 8.5 Commissioning an RFID tag 4. Press "Save ID". The ID is sent to the RFID tag and stored there. A check mark is set in the "Tag" list, if the configured tag ID is successfully written to the RFID tag. NOTICE Recording the ID of the RFID tag If you replace the RFID tag at a later date due to a defect, for example, you will always need the ID of the RFID tag. Therefore, record the ID of the RFID tag so that it is at hand at all times.
PRELIMINARY II 1.7.2010 Commissioning a project 8.6 Replacing an RFID tag 8.6 Requirement Replacing an RFID tag If it is not possible to log onto an effective range, the HMI device or RFID tag may be defective. This section describes the configuration work carried out after replacement of a defective RFID tag. ● The defective RFID tag has been replaced. ● The ID of the defective RFID tag is available. ● The project, in which the RFID tag has failed, is still on the HMI device.
PRELIMINARY II 1.7.2010 Commissioning the plant 9.1 9 Overview The acceptance of the plant involves the following: ● Safety-related project ● Safety program ● RFID tags with effective ranges 9.2 Acceptance of the plant All of the relevant application-specific standards and the procedure described in this section must be observed in the course of final acceptance of the plant.
PRELIMINARY II 1.7.2010 Commissioning the plant 9.3 Diagnostics Acceptance of the safety program ● Print and archive the safety program. ● Check the printed copy of the safety program for existence of the criteria specified in the "S7 Distributed Safety, Configuring and Programming" manual, section "Acceptance of a safety program." ● Download the entire safety program to the F-CPU. ● Test all functions of the safety program.
PRELIMINARY II 1.7.2010 Commissioning the plant 9.3 Diagnostics Diagnostic information for internal errors All LEDs of the LED display go out when an internal error of the HMI device causes a failure. When a project is running on the HMI device, the following occurs: ● The project is closed.
PRELIMINARY II 1.7.2010 Commissioning the plant 9.3 Diagnostics Error code for discrepancy errors The following table lists the error codes for discrepancy errors. You may be able to find a remedy for a discrepancy error yourself, depending on the situation. The first six digits of the error code are decisive for the correct identification of the error. Error code Error type Remedy 000 008 Discrepancy error at the EMERGENCY STOP button Release the EMERGENCY STOP button.
PRELIMINARY II 1.7.2010 Fail-safe operation 10.1 10 Organizational measures The HMI device should only be operated in the plant with a main rechargeable battery or in the docking station. You must adhere to the organizational measures described in this section to ensure fail-safe operation of the HMI device. WARNING EMERGENCY STOP button out of service when HMI device is removed If the HMI device is not integrated in the safety program of the F-CPU, the EMERGENCY STOP button will be out of service.
PRELIMINARY II 1.7.2010 Fail-safe operation 10.2 Switch-off behavior 10.2 Switch-off behavior The shutdown reaction of the plant will vary according to cause and effect. DANGER Shutdown The shutdown response described in the next sections is only triggered in the plant if the FCPU has been programmed accordingly. Programming the F-CPU accordingly.
PRELIMINARY II 1.7.2010 Fail-safe operation 10.3 Integrating the HMI device 10.3 Integrating the HMI device During fail-safe operation, a safety program runs in the F-CPU. The HMI device is integrated into this safety program. The HMI device and F-CPU communicate via PROFINET IO. When there is a project for a safety program on the HMI device, it is automatically integrated following the start of the project. The "SAFE" LED lights up to indicate that integration is complete.
PRELIMINARY II 1.7.2010 Fail-safe operation 10.4 Logging onto a machine 10.4 Logging onto a machine The following figure shows the logon of an HMI device to a machine within a protection zone.
PRELIMINARY II 1.7.2010 Fail-safe operation 10.4 Logging onto a machine Procedure Proceed as follows: 1. Switch to the screen that contains the "Effective range name (RFID)" button labeled "Scan". 6FDQ 2. Bring the HMI device into the effective range of the RFID tag to which you want to log on, for example, "RFID Tag 1". The following table shows how to align the HMI device to the RFID tag. Alignment Logon Possible Not supported Not supported 3. Press the button labeled "Scan".
PRELIMINARY II 1.7.2010 Fail-safe operation 10.5 Logging off the machine The "Confirmation of logon" dialog is displayed with the following symbol. 6. Confirm the logon with the enabling button. The successful logon is indicated by the "RNG" LED on the HMI device. Result You are logged onto the machine and the machine can operate within the protection zone in fail-safe mode. The "Effective range name (RFID)" operator control is shown in green and labeled with the name of the effective range.
PRELIMINARY II 1.7.2010 Fail-safe operation 10.6 Removing the HMI device 10.6 Removing the HMI device You have the following options for removing the HMI device: ● Close the project. ● Press and hold the "ON/OFF" button for at least 4 seconds. WARNING EMERGENCY STOP button out of service when HMI device is removed If the HMI device is not integrated in the safety program of the F-CPU, the EMERGENCY STOP button will be out of service.
PRELIMINARY II 1.7.2010 Fail-safe operation 10.6 Removing the HMI device NOTICE Global rampdown A global rampdown will occur, if you do not confirm the "Confirm removal" dialog within 60 seconds with the enabling button. Press an enabling button within 60 seconds. The "Confirm removal" dialog closes. – The "SAFE" LED on the HMI device goes out. – PROFIsafe communication is terminated. – The HMI device has been successfully removed from the safety program of the FCPU. – The project is closed.
PRELIMINARY II 1.7.2010 Operating a project 11.1 11 Starting the project Note A project may demand operator actions that require in-depth knowledge of the specific plant on part of the operator. Proceed with caution, for example, when you use jog mode. Refer to your plant documentation for additional information. Requirement The following requirements have to be met to start the project: ● The plant has been accepted. ● The main rechargeable battery is charged and inserted in the HMI device.
PRELIMINARY II 1.7.2010 Operating a project 11.1 Starting the project Procedure Proceed as follows: 1. Press the "ON/OFF" button. The HMI device performs the following tasks: – The HMI device starts. – The "PWR" LED lights up. – The "BAT" LED shows the remaining charge of the main rechargeable battery. – The WLAN connection is established. The "COM" LED flashes while the connection is being established. The "COM" LED lights up when the WLAN connection is established. The project is started.
PRELIMINARY II 1.7.2010 Operating a project 11.2 Operator input options 11.2 Operator input options A project may demand operator actions that require in-depth knowledge of the specific plant on part of the operator. Proceed with caution, for example, when you use jog mode. Refer to your plant documentation for additional information. CAUTION Unintentional action If you press several operator controls at once, you may trigger an unintentional action. Do not carry out several operations simultaneously.
PRELIMINARY II 1.7.2010 Operating a project 11.2 Operator input options Feedback from an operator control The HMI device provides optical feedback as soon as it detects that an operator controls has been selected. The operator control receives the focus and is selected. The selection is independent of any communication with a PLC. Therefore this selection does not indicate whether the relevant action is actually executed or not. The selection of an operator control can deviate from the standard.
PRELIMINARY II 1.7.2010 Operating a project 11.3 Direct keys 11.3 Direct keys A direct key on the HMI device is a direct way to set a bit in the I/O area of the controller. A direct key enables an operation with a fast response time. Fast response time is essential, for example, for jogging mode. NOTICE Leaving the WLAN Note that leaving the WLAN area will cause the PROFINET IO device to fail and therefore result in a PLC stop.
PRELIMINARY II 1.7.2010 Operating a project 11.4 Setting the project language 11.4 Setting the project language The HMI device supports multilingual projects. You must have configured a corresponding operator control which lets you change the language setting on the HMI device during runtime. The project always starts with the language set in the previous session.
PRELIMINARY II 1.7.2010 Operating a project 11.5 Operating the screen keyboard in the project ● Alphanumerical screen keyboard The alphanumerical screen keyboard has the following levels. – Normal level – Shift level The shift level includes uppercase letters. – Special character level Note The ' character (button between ";" and "\") appears only when followed by a space. If the ' character is followed by a letter, then the result will be an accent, such as "á".
PRELIMINARY II 1.7.2010 Operating a project 11.5 Operating the screen keyboard in the project Procedure for adjusting the size of the screen keyboard Note icon only appears on the screen keyboard if in the "Siemens HMI InputPanel" dialog The you have selected the "Show Resize button" check box. Proceed as follows: 1. Touch the symbol and drag the screen keyboard to the appropriate size. 2. When the size you want is reached, release contact with the icon.
PRELIMINARY II 1.7.2010 Operating a project 11.5 Operating the screen keyboard in the project Note Data input - numerical text box Hexadecimal values When you enter a value in hexadecimal format, the alphanumerical screen keyboard opens. Decimal places The configuration engineer can define the number of decimal places for a numerical text box. The number of decimal places is checked when you enter a value in this type of I/O field. – Decimal places in excess of the limit are ignored.
PRELIMINARY II 1.7.2010 Operating a project 11.6 Device-specific displays Note If an infotext was configured for the current control object as well as the current HMI screen, you can switch between both infotexts by touching the infotext window. Close the infotext window with the button. Depending on the project, infotext can also be called by an operator control configured for this purpose. For additional information, refer to the online help of WinCC flexible. 11.6 Device-specific displays 11.6.
PRELIMINARY II 1.7.2010 Operating a project 11.6 Device-specific displays 11.6.3 Displaying WLAN quality The "WLAN quality" object indicates the signal strength of the wireless network at the location of the HMI device. The HMI device measures the signal strength and depicts it with the "WLAN quality" object.
PRELIMINARY II 1.7.2010 Operating a project 11.7 Project security 11.6.4 Displaying the "Effective range name (RFID)" object The "Effective range name (RFID)" object is only available for an HMI device of the RFID tag system. The "Effective range name (RFID)" object displays the following information: ● Logon status ● "Scan", "Scanning...
PRELIMINARY II 1.7.2010 Operating a project 11.7 Project security Central user administration using SIMATIC Logon Users, user groups and authorizations can be stored on a central server. If user administration cannot contact the server, an error message is displayed. If this is the case, you can only log on locally. More detailed information is available in your plant documentation.
PRELIMINARY II 1.7.2010 Operating a project 11.7 Project security Backup and restore Note Backup and restore is not available to central user administration with SIMATIC Logon. The user data is encrypted and saved on the HMI device to protect it from loss due to power failure. The users, passwords, group assignments and logoff times set up on the HMI device can be backed up and restored. This prevents you having to enter all of the data again on another HMI device.
PRELIMINARY II 1.7.2010 Operating a project 11.7 Project security Simple user view If you are not logged onto the HMI device, the only entry contained in the simple user view is "". If you are logged onto the HMI device, the simple user view only displays the user name and user group. Extended user view The extended user view displays information about the users.
PRELIMINARY II 1.7.2010 Operating a project 11.7 Project security 11.7.3 User logon Use the logon dialog of the HMI device to log onto the security system. Enter your user name and password in the logon dialog.
PRELIMINARY II 1.7.2010 Operating a project 11.7 Project security 11.7.4 User logoff Requirement ● You have logged into the security system of the HMI device. Procedure You have the following options for logging off: ● Press an operator control that is configured for logging off the security system. ● If you do not operate a project and exceed the logoff time, your user account will be locked. Your user account will be automatically logged off if you enter an incorrect password.
PRELIMINARY II 1.7.2010 Operating a project 11.7 Project security The following dialog appears: 2. Enter the desired user name and password. Touch the corresponding text box. The alphanumerical screen keyboard is displayed. 3. Touch the "OK" button. The following dialog appears: 4. Assign the user to a group. In order to do so, open the "Group" drop down list box by means of the and to scroll in the drop down list box. button. Select 5. Touch the required entry in the drop down list box.
PRELIMINARY II 1.7.2010 Operating a project 11.7 Project security 11.7.6 Changing user data You have opened a screen with a user view. The data you are allowed to change depends on your authorization: Requirement ● You are an administrator or a user with user management authorization. In these cases you are allowed to change the data for all the users on the HMI device in the user view: – User name – Group assignment – Password – Logoff time ● You are a user without user management authorization.
PRELIMINARY II 1.7.2010 Operating a project 11.7 Project security 11.7.7 Deleting users Requirement ● You have opened a screen with a user view. ● You are an administrator or you have permission for user management. Procedure Note The "Admin" and "PLC_User" users exist by default. You cannot delete these users. 1. Delete the entered user name. Result The affected user can no longer use the operator controls with permission.
PRELIMINARY II 1.7.2010 Operating a project 11.8 Error cases in the project operation 11.8 Error cases in the project operation During fail-safe operation, you must be aware that the following error cases may arise: ● Leaving an HMI device logged onto a machine CAUTION Shutdown possible If the HMI device is in a state where it is constantly ready for operation, the main rechargeable battery will lose its charge. A discharged main rechargeable battery causes communication failure.
PRELIMINARY II 1.7.2010 Operating a project 11.9 Closing the project 11.9 Closing the project The procedure for closing the active project is identical to the procedure for removing the HMI device.
PRELIMINARY II 1.7.2010 Service and maintenance 12.1 12 Maintenance and care Read sections "Safety-related operator controls (Page 88)" and "Safety instructions (Page 72)" for information on service and maintenance. Scope of maintenance The HMI device is designed for maintenance-free operation. Remember to include accessories and peripheral equipment in the maintenance. The scope of maintenance includes: Function test Perform an annual function test for the enabling button and EMERGENCY STOP button.
PRELIMINARY II 1.7.2010 Service and maintenance 12.2 Replacing the rechargeable buffer battery Procedure CAUTION Damage possible The use of compressed air, steam cleaners or aggressive solutions or scouring agents will damage the HMI device. Use a cleaning cloth dampened with a cleaning agent to clean the equipment. Only use water with a little liquid soap or a screen cleaning solution. Proceed as follows: 1. Switch off the HMI device. 2. Spray the cleaning solution onto a cleaning cloth.
PRELIMINARY II 1.7.2010 Service and maintenance 12.3 Spare parts and repairs Proceed as follows: 1. Remove the enclosure. The enclosure is not needed for installation. 2. Open the connection compartment. 3. Pull out the connector. 4. Slide the rechargeable buffer battery out of the guide and put it down. 5. Insert the new rechargeable buffer battery, as shown in the following illustration. 5HFKDUJHDEOH EXIIHU EDWWHU\ 3OXJ DQG VRFNHW &RQQHFWLQJ FDEOH 3ULQWHG FLUFXLW ERDUG 6. Connect the plug. 7.
PRELIMINARY II 1.7.2010 Service and maintenance 12.
PRELIMINARY II 1.7.2010 13 Technical specifications 13.1 Dimension drawings 13.1.
PRELIMINARY II 1.7.2010 Technical specifications 13.1 Dimension drawings 13.1.
PRELIMINARY II 1.7.2010 Technical specifications 13.1 Dimension drawings 13.1.3 RFID tag Fixing pocket $OO GLPHQVLRQV LQ PP Spacer $OOH $QJDEHQ LQ PP You can additional illustrations on the Internet at Image database (http://www.automation.siemens.com/bilddb/index.aspx?att14s=35).
PRELIMINARY II 1.7.2010 Technical specifications 13.2 Specifications 13.2 Specifications 13.2.1 Wireless Teach Pendant F IWLAN V2 General information Weight with battery, without packaging Approx. 2 kg Drop height with main rechargeable battery, max. 0.5 m Buffer time of internal clock with battery inserted Approx. 4 days Type Color TFT LC display Display area, active 132.5 mm x 99.
PRELIMINARY II 1.7.2010 Technical specifications 13.2 Specifications Ports 2 x USB USB host; conforms to USB standard 1.1 Supports low-speed and full-speed USB devices. Current load per port, max. 100 mA 1 x WLAN For PROFINET WLAN 1 x RJ45 For LAN WLAN antenna Antenna type Dual port patch antenna Polarization Vertical and horizontal Antenna gain in principle ray direction, max.
PRELIMINARY II 1.7.2010 Technical specifications 13.2 Specifications Other safety-related characteristic values Acknowledgement time 13.2.2 40 ms Response time with no fault, max. 25 ms Discrepancy time – EMERGENCY STOP 500 ms Discrepancy time – enabling button "Enabling" position "Panic" position 2 sec 1 sec Interface description USB The figure below shows the pin assignment of the USB interface. Pin Assignment 1 +5 VDC, out (max.
PRELIMINARY II 1.7.2010 Technical specifications 13.2 Specifications WLAN Operation of a wireless interface in the frequency bands 2.4 GHz and 5 GHz. The wireless interface is compatible with the following standards: ● IEEE 802.11a ● IEEE 802.11h ● IEEE 802.11b ● IEEE 802.11g Receiver sensitivity WLAN standard Data transfer rate Receiver sensitivity IEEE 802.
PRELIMINARY II 1.7.2010 Technical specifications 13.2 Specifications Transmission power WLAN standard Data transfer rate Receiver sensitivity IEEE 802.11a/h (5.18 ∼ 5.7 GHz) 54 Mbps 13.5 dBm 48 Mbps 15 dBm 36 Mbps 16 dBm 6-24 Mbps 17 dBm 54 Mbps 11.5 dBm 48 Mbps 13 dBm 36 Mbps 14 dBm 6-24 Mbps 15 dBm 54 Mbps 16 dBm 48 Mbps 17 dBm 36 Mbps 17 dBm 6-24 Mbps 17 dBm 11 Mbps 20 dBm 5.5 Mbps 20 dBm 2 Mbps 20 dBm 1 Mbps 20 dBm IEEE 802.11a/h (4.92 ∼ 5.16 GHz) (5.745 ∼ 5.
PRELIMINARY II 1.7.2010 Technical specifications 13.2 Specifications 13.2.4 Docking station Weight without packing Approx. 1.1 kg Power supply 13.2.5 Nominal voltage +24 VDC via external power supply Transients, maximum permitted 35 V (500 ms) Time between two transients, minimum 50 s Power consumption with Wireless Teach Pendant F IWLAN Typical Constant current, maximum Power on current surge I2t Fuse, internal Electronic Approx. 1.5 A Approx. 1.8 A Approx. 1.
PRELIMINARY II 1.7.2010 Technical specifications 13.2 Specifications 13.2.
PRELIMINARY II 1.7.2010 A Appendix A.1 ESD guideline What does ESD mean? An electronic module is equipped with highly integrated electronic components. Due to their design, electronic components are highly sensitive to overvoltage and thus to the discharge of static electricity. Such electronic components are labeled as electrostatic sensitive devices (ESD).
PRELIMINARY II 1.7.2010 Appendix A.1 ESD guideline 9ROWDJH The following diagram shows the maximum voltage values to which a person can be charged electrostatically. The values depend on the material and humidity. The shown values are in conformity with the specifications of EN 61000-4-2. >N9@ > @ 5HODWLYH KXPLGLW\ ① ② ③ Synthetic materials Wool Antistatic materials such as wood or concrete Protective measures against dis
PRELIMINARY II 1.7.2010 Appendix A.2 Typical operating procedures and potential fault scenarios A.2 Typical operating procedures and potential fault scenarios A.2.1 Overview This section describes typical application cases for the HMI device. The following states are graphically represented in the application cases.
PRELIMINARY II 1.7.2010 Appendix A.2 Typical operating procedures and potential fault scenarios A.2.2 Switch on the HMI device. Requirement ● The HMI device is switched off. ● The rechargeable battery is fully charged. LED display 6$)( Procedure EMERGENCY STOP button 3:5 &20 51* Enabling button %$7 1. Switch on the HMI device using the ON/OFF button. Communication via WLAN starts up. While the WLAN connection is being established the "COM" LED flashes.
PRELIMINARY II 1.7.2010 Appendix A.2 Typical operating procedures and potential fault scenarios A.2.3 Requirement Integrating the HMI device ● The HMI device is switched on. ● WLAN communication is established. ● The HMI device shows the Windows CE Desktop with the Loader. LED display 6$)( EMERGENCY STOP button 3:5 &20 51* Enabling button %$7 Procedure 1. Start the project. – PROFIsafe communication is established.
PRELIMINARY II 1.7.2010 Appendix A.2 Typical operating procedures and potential fault scenarios A.2.4 Communication error for the integrated HMI device Requirement ● The HMI device is integrated in the safety program of the F-CPU. ● The HMI device is not logged onto a machine. LED display 6$)( EMERGENCY STOP button 3:5 &20 51* Enabling button %$7 Procedure 1. You are leaving the WLAN range with the HMI device. The "COM" LED flashes.
PRELIMINARY II 1.7.2010 Appendix A.2 Typical operating procedures and potential fault scenarios LED display 6$)( EMERGENCY STOP button 3:5 &20 51* Enabling button %$7 Result 2 – No return to the WLAN range ● The project will be closed immediately if you confirm the Confirm removal dialog within 60 seconds. ● The active project will be closed automatically if you do not confirm the "Confirm removal" dialog within 60 seconds. ● The Windows CE desktop with the loader is shown on the display.
PRELIMINARY II 1.7.2010 Appendix A.2 Typical operating procedures and potential fault scenarios A.2.5 Discrepancy error during enabling The enabling button is two-channel. Both contacts must be closed at the same time to reach the enabled state. A discrepancy error is generated if one of the contacts is open while the other is closed. The following fault scenarios can occur: ● The enabling button is askew ● The enabling button is defective. A.2.5.
PRELIMINARY II 1.7.2010 Appendix A.2 Typical operating procedures and potential fault scenarios The dialog stays open until this discrepancy is corrected. Additional information on discrepancy time is available in "Wireless Teach Pendant F IWLAN V2 (Page 244)", section "Fail-safe operation". Enabling is made possible by pressing the enabling button again from the zero position. ● The HMI device is integrated but not logged onto a machine.
PRELIMINARY II 1.7.2010 Appendix A.2 Typical operating procedures and potential fault scenarios Procedure 1. Press the enabling button. Result – Scenario 1 ● The enabled state is not activated. The "Discrepancy error enabling button" dialog opens with the following symbol when the discrepancy time expires. The dialog stays open until the enabling button is released. This step cancels the discrepancy. A discrepancy error is displayed again when the operator presses the enabling button once again .
PRELIMINARY II 1.7.2010 Appendix A.2 Typical operating procedures and potential fault scenarios Procedure 1. Touch the "Effective range name (RFID)" object labeled "Scan". The HMI device searches for RFID tags, the "Effective range name (RFID)" object is shown in yellow labeled "Scanning". 6FDQQLQJ If the "Effective range name (RFID)" object is configured with password protection, enter a valid user name and a valid password. The "Effective range logon" dialog opens with the following symbol. 2.
PRELIMINARY II 1.7.2010 Appendix A.2 Typical operating procedures and potential fault scenarios A.2.7 Leaving a protection zone without logging off Requirement ● A security system is installed for the protection zone, for example, a photoelectric sensor or a contact pressure mat. ● The HMI device has been logged on to a machine, such as "Robot 1", via an RFID tag. 5RERW LED display 6$)( EMERGENCY STOP button 3:5 &20 51* Enabling button %$7 Procedure 1.
PRELIMINARY II 1.7.2010 Appendix A.2 Typical operating procedures and potential fault scenarios A.2.8 Communication errors with logged on HMI device Starting situation The HMI device is logged on to a machine. 5DQJHQDPH LED display 6$)( EMERGENCY STOP button 3:5 &20 51* Enabling button %$7 Fault A communication error occurs. The F-CPU initiates a shutdown and stops the machine. The "SAFE" and "RNG" LEDs are off. The operator is alerted that no safety-related communication is available.
PRELIMINARY II 1.7.2010 Appendix A.2 Typical operating procedures and potential fault scenarios LED display 6$)( A.2.9 Requirement EMERGENCY STOP button 3:5 &20 51* Enabling button %$7 Logging off the machine ● The HMI device is logged on to a machine. ● The "Effective range name" object will be displayed in green. 5DQJHQDPH LED display 6$)( Procedure EMERGENCY STOP button 3:5 &20 51* Enabling button %$7 1. Confirm the "Effective range name (RFID)" object.
PRELIMINARY II 1.7.2010 Appendix A.2 Typical operating procedures and potential fault scenarios A.2.10 Removing the HMI device Requirement ● The project must be started. ● The HMI device is integrated in the safety program of the F-CPU. ● The HMI device is not logged onto a machine. LED display 6$)( EMERGENCY STOP button 3:5 &20 51* Enabling button %$7 Procedure 1. To close the project, use the operator control designed for this purpose. The "Start removal" dialog opens with the following symbol.
PRELIMINARY II 1.7.2010 Appendix A.2 Typical operating procedures and potential fault scenarios LED display 6$)( A.2.11 Requirement EMERGENCY STOP button 3:5 &20 51* Enabling button %$7 Switching off the HMI device ● The project must be started. ● The HMI device is integrated in the safety program of the F-CPU. LED display 6$)( Procedure EMERGENCY STOP button 3:5 &20 51* Enabling button %$7 1. Close all open dialogs. 2. Press and hold the "ON/OFF" button for at least 4 seconds.
PRELIMINARY II 1.7.2010 Appendix A.3 Example of an application Result ● Safety-related communication is terminated. ● The HMI device has been successfully removed from the safety program of the F-CPU. ● The project is closed. ● The HMI device will be switched off. LED display 6$)( EMERGENCY STOP button 3:5 &20 A.3 Example of an application A.3.1 Configuration and operation 51* Enabling button %$7 This application example shows one possible application with the safety features of the HMI device.
PRELIMINARY II 1.7.2010 Appendix A.3 Example of an application Configuration example The following example configuration shows a robot cell which is secured by a wire mesh fence with a contact pressure mat.
PRELIMINARY II 1.7.2010 Appendix A.3 Example of an application Function Symbolic name Signal Explanation Contact pressure mat "Contact_Mats" I11.0 "0": Step on contact pressure mat "1": Do not step on contact mat "Key1" button, configured as direct key on the HMI device: E0.0 "0": Button not pressed "1": Button pressed Enabling button ENABLE (F_FB_RNG_4) "0": No enable "1": Enable Power ON-OFF robot "E_Stop_Robot" O11.0 "0": EMERGENCY STOP triggered. "1": Normal operation of plant.
PRELIMINARY II 1.7.2010 Appendix A.3 Example of an application A.3.2 Configuring the controller and HMI device in STEP 7 This section describes the most important parameters you need to set in "HW Config" for the F-CPU and for the HMI device. WARNING Safety category Any changes to parameters may result in the loss of the safety category. Set the parameters as described. The parameters will contribute to meeting safety category 4 PL e/SIL 3.
PRELIMINARY II 1.7.2010 Appendix A.3 Example of an application Setting Explanation This is where you set the cycle time for OB35. Note If the cycle time for OB35 is set lower than the PBIO update time, the message frame may be lost and the evaluation of the "E-STOP" output of F_FB_RNG_4 or F_FB_RNG_16 may be delayed. Set the cycle time of OB35 to a value higher than the PNIO update time. Assign a password for the safety program. Set the "CPU contains safety program" check box.
PRELIMINARY II 1.7.2010 Appendix A.3 Example of an application Procedure – Configuring Wireless Teach Pendant F IWLAN Proceed as follows: 1. Insert the Wireless Teach Pendant F IWLAN in "HW Config" as shown in the following figure. 2. Open the properties dialog of the HMI device by double-clicking the "WTPfiwlan" icon. 3. Enter the device name of the HMI device in the properties dialog. 4.
PRELIMINARY II 1.7.2010 Appendix A.3 Example of an application The table below shows the most important settings: Setting Explanation Device name Here you assign a device name to the HMI device, which is unique in the local Ethernet network segment. This name must match the name defined in the Control Panel of the HMI device under "PROFINET" in the text box "Device name:". Additional information is available in the section: "Specifying the computer name of the HMI device (Page 145)".
PRELIMINARY II 1.7.2010 Appendix A.3 Example of an application A.3.3 Safety program S7 Distributed Safety In the safety program of the S7-CPU, the operation sequence of the application example is implemented by the following programming: ● Once the HMI device is logged on to a machine, the signal lamp and the "Override" mode are enabled. ● In the protection zone, the operator can operate the robot with the "Key1" button and the enabling button.
PRELIMINARY II 1.7.2010 Appendix A.3 Example of an application F-CALL (FC 1) F-CALL (FC1) is the F-run-time group and is called from the cyclic interrupt OB (OB35). F-CALL (FC1) calls the F-program block (in this case: FB1). FB1 For reasons of program modularity, all other F-FBs are called from this FB. In FB 1, you have to call the F-FBs in the following order. 1. Network 1 '% )B)%B03 ) B:73)DLOVDIHB,2 4%$' ) B:73)DLOVDIHB,2 $&.B5(4 03 B)%B6 B03B5( 03 B)%B6 B$&.
PRELIMINARY II 1.7.2010 Appendix A.3 Example of an application 2. Network 2 '% )B)%B51*B &RQWDFWB0DWV (GJHB &RQWDFWB 0DWV 1(* (1 0B%,7 4 ,QWHUIDFHB'% (5 B51*B%86< 51*B,' 29(55,'( 03 B)B'$7$B3,, 03 B'$7$ 03 B)B51*B3,, 03 B51* 03 B)B.(< 03 B'$7$ (B6723 03 B51* */2%B5' 03 B)B.(< 03 B'$7$ /2&B5' 03 B51* 6+87'2:1 03 B)B.
PRELIMINARY II 1.7.2010 Appendix A.3 Example of an application 3. Network 3 '% )B(6723 ,QWHUIDFHB'% (5 B(B6723 (1 (B6723 $&.B1(& $&. 7,0(B'(/ 4 4B'(/$< $&.B5(4 ',$* (12 (B6WRSB5RERW In network 3, the EMERGENCY STOP signal of the HMI device is monitored via F_ESTOP1 from the F-library of S7 Distributed Safety. F_ESTOP1 ensures that the plant is only able to restart following an EMERGENCY STOP after acknowledgment by the operator via the input "ACK".
PRELIMINARY II 1.7.2010 Appendix A.3 Example of an application 5. Network 7 ( $ ,QWHUIDFHB'% (5 B(QDEOH If the operator simultaneously presses the Key1 key and the enabling button, the robot is activated via the output Q11.1. 6. Network 8 $ ,QWHUIDFHB'% (5 B51*B%86< If the "RNG_BUSY" signal is set in F_FB_RNG, output Q11.2 is used to control the signal lamp that indicates whether or not the machine is in use.
PRELIMINARY II 1.7.2010 Appendix A.4 Safety-related messages A.4 Safety-related messages The following safety-related messages are displayed in fail-safe mode depending on the operating situation. In contrast to system alarms, no message window needs to be configured for safety-related messages. Dialog Reaction Establishment of safety connection "Yes" button No safe connection available.
PRELIMINARY II 1.7.2010 Appendix A.4 Safety-related messages Dialog Reaction Situation Effective range logon "Yes" button "No" button The HMI device is located directly in front of an RFID tag and is not yet logged on to the corresponding machine. The operator has activated the "Scan" object to log on.
PRELIMINARY II 1.7.2010 Appendix A.4 Safety-related messages Dialog Reaction Situation Forced logoff "OK" button The operator has left the protection zone with a logged-on HMI device via the safety system. "OK" button The remaining charge of the main rechargeable battery is less than 20%. You are automatically logged off from the effective range. A local rampdown has been triggered! Confirm the logoff from the effective range. Low battery alarm Battery charge is less than 20 percent.
PRELIMINARY II 1.7.2010 Appendix A.4 Safety-related messages Dialog Reaction Situation Enabling switch discrepancy error Release both enabling buttons. The HMI device detects a discrepancy at one of the two enabling buttons in switch position "Enable". Please release the enabling button.
PRELIMINARY II 1.7.2010 Appendix A.5 System alarms A.5 System alarms Introduction System alarms on the HMI device provide information about internal states of the HMI device and PLC. The following overview shows the causes of system alarms and how to eliminate the cause of error. Some of the system alarms described in this section are relevant to individual HMI devices based on their range of features. Note System alarms are only indicated if an alarm window was configured.
PRELIMINARY II 1.7.2010 Appendix A.
PRELIMINARY II 1.7.2010 Appendix A.5 System alarms 10000 - Printer alarms Number Effect/cause Remedy 10000 The print job could not be started or was canceled due to an unknown error. Faulty printer setup. Or: No authorization is available for accessing the network printer. Power supply failure during data transfer. Check the printer settings, cable connections and the power supply. Set up the printer once again. Obtain a network printer authorization.
PRELIMINARY II 1.7.2010 Appendix A.5 System alarms 30000 - Alarms for IFwSetValue: SetValue() Number Effect/causes Remedy 30010 The tag could not accept the function result, e.g. when it has exceeded the value range. Check the tag type of the system function parameter. 30011 A system function could not be executed because Check the parameter value and tag type of the invalid the function was assigned an invalid value or type in parameter. If a tag is used as a parameter, check its the parameter.
PRELIMINARY II 1.7.2010 Appendix A.5 System alarms 70000 - Win32 function alarms Number Effect/causes Remedy 70010 The application could not be started because it could not be found in the path specified or there is insufficient memory space. Check whether the application exists in the specified path or close other applications. 70011 The system time could not be modified. The error alarm only appears in connection with area pointer "Date/time PLC".
PRELIMINARY II 1.7.2010 Appendix A.5 System alarms Number Effect/causes Remedy 70023 Acknowledgment to starting the Export Password List action. -- 70024 The range of values of the tag was exceeded in the system function. No calculation of the system function. Check and correct the calculation. 70025 The range of values of the tag was exceeded in the system function. No calculation of the system function. Check and correct the calculation.
PRELIMINARY II 1.7.2010 Appendix A.5 System alarms Number Effect/causes Remedy 70037 An e-mail cannot be sent for unknown reasons. The contents of the e-mail are lost. Check the e-mail parameters (recipient etc.). 70038 The SMTP server has rejected sending or forwarding an e-mail because the domain of the recipient is unknown to the server or because the SMTP server requires authentication. The contents of the e-mail are lost.
PRELIMINARY II 1.7.2010 Appendix A.5 System alarms Number Effect/causes Remedy 80012 Log entries are stored in a buffer. If the values are read to the buffer faster than they can be physically written (using a hard disk, for example), overloading may occur and recording is then stopped. Archive fewer values. Or: Increase the logging cycle. 80013 The overload status no longer applies. Archiving resumes the recording of all values. -- 80014 The same action was triggered twice in quick succession.
PRELIMINARY II 1.7.2010 Appendix A.5 System alarms Number Effect/causes Remedy 80026 This alarm is output after all logs are initialized. Values are written to the logs from then on. Prior to this, no entries are written to the logs, irrespective whether WinCC flexible Runtime is active or not. -- 80027 The internal Flash memory has been specified as the storage location for a log. This is not permissible. No values are written to this log and the log file is not created.
PRELIMINARY II 1.7.2010 Appendix A.5 System alarms Number Effect/causes Remedy 80049 The log could not be renamed while preparing to export it. The job can not be completed." Check whether the storage medium is correctly inserted and if there is sufficient space on the medium. 80050 The log which shall be exported is not closed. The job can not be completed. Make sure the "CloseAllLogs" system function is called before using the "ExportLog" system function. Change the configuration as required.
PRELIMINARY II 1.7.2010 Appendix A.5 System alarms Number Effect/causes Remedy 90048 The Audit Trail cannot be printed while data relevant to the audit is being logged. Stop logging using the system function "StopLogging". 90049 Access to required file is not possible. Check the network connection or the storage medium. 90056 The recipe was not imported because the file contains no checksum. Select a file with a checksum. The recipe was not imported because the file contains an invalid checksum.
PRELIMINARY II 1.7.2010 Appendix A.5 System alarms 130000 - System information alarms Number Effect/causes Remedy 130000 The action was not executed. Close all other programs. Delete files no longer required from the hard disk. 130001 The action was not executed. Delete files no longer required from the hard disk. 130002 The action was not executed. Close all other programs. Delete files no longer required from the hard disk. 130003 No data medium found. The operation is canceled.
PRELIMINARY II 1.7.2010 Appendix A.5 System alarms 140000 - Connection alarms chns7: Connection + device Number Effect/causes Remedy 140000 An online connection to the PLC is established. -- 140001 The online connection to the PLC was shut down. -- 140003 No tag updating or writing is executed. Check the connection and if the PLC is switched on. Check the parameter definitions in the Control Panel using "Set PG/PC interface". Restart the system.
PRELIMINARY II 1.7.2010 Appendix A.5 System alarms Number Effect/causes Remedy 140010 No S7 communication partner found because the PLC is shut down. DP/T: The option “PG/PC is the only master” is not set in the Control Panel under “Set PG/PC interface.” Switch the PLC on. DP/T: If only one master is connected to the network, disable "PG/PC is the only master" in "Set PG/PC interface". If several masters are connected to the network, enable these.
PRELIMINARY II 1.7.2010 Appendix A.5 System alarms 150000 - Connection alarms chnAS511: Connection Number Effect/causes Remedy 150000 No more data is read or written. Possible causes: The cable is defective. The PLC does not respond, is defective, etc. The wrong port is used for the connection. System overload Ensure that the cable is plugged in, the PLC is operational, the correct port is being used. Restart the system if the system alarm persists.
PRELIMINARY II 1.7.2010 Appendix A.5 System alarms 170000 - S7 dialog alarms Number Effect/causes Remedy 170000 S7 diagnostics events are not indicated because it is not possible to log on to the S7 diagnostics functions at this device. The service is not supported. -- 170001 The S7 diagnostics buffer cannot be viewed because communication with the PLC is shut down. Set the PLC to online mode.
PRELIMINARY II 1.7.2010 Appendix A.5 System alarms 190000 - Tag alarms Number Effect/causes 190000 It is possible that the tag is not updated. -- 190001 The tag is updated after the cause of the last error state has been eliminated (return to normal operation). -- 190002 The tag is not updated because communication with the PLC is down. Select the system function "SetOnline" to go online. 190004 The tag is not updated because the configured tag address does not exist. Check the configuration.
PRELIMINARY II 1.7.2010 Appendix A.5 System alarms 190100 - Area pointer alarms Number Effect/causes Remedy 190100 The area pointer is not updated because the address configured for this pointer does not exist. Type 1 Warnings 2 Errors 3 PLC acknowledgment 4 HMI device acknowledgment 5 LED mapping 6 Trend request 7 Trend transfer 1 8 Trend transfer 2 No.: Consecutive number displayed in WinCC flexible ES. Check the configuration.
PRELIMINARY II 1.7.2010 Appendix A.5 System alarms 210000 - PLC job alarms Number Effect/causes Remedy 210000 Jobs are not processed because the address configured in the PLC does not exist/has not been set up. Change the address or set up the address in the PLC. 210001 Jobs are not processed because read/write access to the Change the address or set up the address in the address configured in the PLC is not possible. PLC in an area which allows read/write access.
PRELIMINARY II 1.7.2010 Appendix A.5 System alarms 230000 - View alarms Number Effect/causes 230000 The value entered could not be accepted. The system Enter a practical value or delete any unneeded users. discards the entry and restores the previous value. Either The value range has been exceeded Illegal characters have been entered The maximum permitted number of users has been exceeded. 230002 The currently logged in user has not the required authorization.
PRELIMINARY II 1.7.2010 Appendix A.5 System alarms Number Effect/causes Remedy 230202 WININET.DLL has detected an error. This error is usually generated if it is not possible to connect to the server or if the server denies access because the client could not authenticate itself. A rejected server certificate could also cause a communication error in secure SSL connections. For details, refer to the error text in the alarm.
PRELIMINARY II 1.7.2010 Appendix A.5 System alarms Number Effect/causes Remedy 230306 Error in the connection to the remote server. This may occur as a result of network problems. The attempt to connect failed. Check whether The bus cable is plugged in There are network problems. 230307 The connection to the remote server was shut down because The remote server was shut down, or The user instructed the server to close all connections. -- The connection is closed.
PRELIMINARY II 1.7.2010 Appendix A.5 System alarms Number Effect/causes Remedy 250002 The tag in the specified line in "Status Force" is not updated because it is not possible to map the PLC type in the tag type. Check the set address. 250003 An attempt to connect to the PLC failed. The tags are not updated. Check the connection to the PLC. Check that the PLC is switched on and is online.
PRELIMINARY II 1.7.2010 Appendix A.5 System alarms Number Effect/causes Remedy 260028 Upon system start-up, an attempt to log on, or when Check the connection to the SIMATIC Logon Server trying to change the password of a SIMATIC log-on and its configuration; for example: user, the system attempts to access the SIMATIC Logon 1. Port number Server. 2. IP address If attempting to log on, the new user is not logged in. If a 3. Server name different user was logged on before, then this user is 4.
PRELIMINARY II 1.7.2010 Appendix A.5 System alarms Number Effect/causes Remedy 260044 It was not possible to log the user on to the SIMATIC Logon Server as his account is blocked. Check the user data on the SIMATIC Logon Server. The new user is not logged in. If a different user was logged on before, then this user is logged off. 260045 The SIMATIC Logon user is not associated to any or several groups. The new user is not logged in.
PRELIMINARY II 1.7.2010 Appendix A.5 System alarms 280000 - DPHMI alarms Connection Number Effect/causes Remedy 280000 Connection is up because the cause of the interruption has been eliminated. -- 280001 No more data is read or written. Possible causes: The cable is defective The PLC does not respond, is defective, etc. The wrong port is used for the connection System overload Check whether The cable is plugged in The PLC is OK The correct port is used.
PRELIMINARY II 1.7.2010 Appendix A.5 System alarms 290000 - Recipe system alarms Number Effect/causes Remedy 290000 The recipe tag could not be read or written. It is assigned the start value. The alarm can be entered in the alarm buffer for up to four more failed tags if necessary. After that, alarm 290003 is output. Check in the configuration that the address has been set up in the PLC.
PRELIMINARY II 1.7.2010 Appendix A.5 System alarms Number Effect/causes Remedy 290013 An attempt was made to save a record under a record number which already exists. The action is not executed. The following remedies are available: Check the source for the number (constant or tag value). First, delete the record. Change the "Overwrite" function parameter. 290014 The file specified to be imported could not be found. Check: The file name Ensure that the file is in the specified directory.
PRELIMINARY II 1.7.2010 Appendix A.5 System alarms Number Effect/causes Remedy 290040 A record error with error code %1 that cannot be described in more detail occurred. The action is canceled. It is possible that the record was not installed correctly on the PLC. Check the storage location, the record, the "Data record" area pointer and if necessary, the connection to the PLC. Restart the action after a short time. If the error persists, contact Customer Support.
PRELIMINARY II 1.7.2010 Appendix A.5 System alarms Number Effect/causes Remedy 290063 This occurs with the system function "ExportDataRecords" when the parameter "Overwrite" is set to No. An attempt has been made to save a recipe under a file name which already exists. The export is canceled. Check the "ExportDataRecords" system function. 290064 Alarm reporting that the deletion of records has started. -- 290065 Alarm reporting that the deletion of records has successfully completed.
PRELIMINARY II 1.7.2010 Appendix A.5 System alarms 300000 - Alarm_S alarms Number Effect/causes Remedy 300000 Faulty configuration of process monitoring (e.g. using PDiag or S7 Graph): More alarms are queued than specified in the specifications of the CPU. No further ALARM_S alarms can be managed by the PLC and reported to the HMI devices. Change the PLC configuration. 300001 ALARM_S is not registered on this PLC. Select a controller that supports the ALARM_S service.
PRELIMINARY II 1.7.2010 Appendix A.5 System alarms 320000 - Alarms Number Effect/causes 320000 The movements have already been indicated by another Deselect the movements on the other display units device. and select the motion control screen on the required The movements can no longer be controlled. display unit. 320001 The network is too complex. The faulty addresses cannot be indicated. View the network in STL. 320002 No diagnosable alarm message (error) selected.
PRELIMINARY II 1.7.2010 Appendix A.5 System alarms 330000 - GUI alarms Number Effect/causes Remedy 330022 Too many dialogs are open on the HMI device. Close all dialogs you do not require on the HMI device. 330026 The password will expire after the number of days shown. Enter a new password. 350000 - GUI alarms Number Effect/causes Remedy 350000 PROFIsafe packages have not arrived within the necessary period. There is a communication problem with the F-CPU. Check the WLAN connection.
PRELIMINARY II 1.7.2010 Appendix A.
PRELIMINARY II 1.7.
PRELIMINARY II 1.7.
PRELIMINARY II 1.7.2010 Glossary "Transfer" mode "Transfer" is an operating mode of the HMI device in which an executable project is transferred from the configuration PC to an HMI device. Access point See Wireless access point. Ad hoc network An ad hoc network in information technology refers to a wireless network between two or more mobile devices, for which no fixed infrastructure is necessary. This technique is used with Bluetooth, for example, to spontaneously link mobile phones.
PRELIMINARY II 1.7.2010 Glossary Bootloader Used to start the operating system. Automatically started when the HMI device is switched on. After the operating system has been loaded, the Loader opens. Configuration PC A configuration PC is a programming device or PC on which HMI projects are created for a plant with a configuration software.
PRELIMINARY II 1.7.2010 Glossary Field array A field is configurable object. A reserved area is used for the input and output of values. Flash memory Non-volatile memory with EEPROM chips, used as mobile storage medium or as memory module installed permanently on the motherboard. Half Brightness Life Time Time period after which the brightness reaches 50% of the original value. The specified value is dependent on the operating temperature.
PRELIMINARY II 1.7.2010 Glossary IO field An IO field is configurable object. It enables values to be entered on the HMI device and transferred to the controller, and values to be output from the controller. IO field, symbolic A symbolic IO field is configurable object. It enables values to be entered on the HMI device and transferred to the controller, and values to be output from the controller. Contains a list of default entries from which one can be selected.
PRELIMINARY II 1.7.2010 Glossary PROFINET Within the framework of Totally Integrated Automation, PROFINET represents an enhancement of the following bus systems: ● PROFIBUS DP as well-established fieldbus ● Industrial Ethernet as the communication bus on the device level The experience gained from both systems has been and continues to be integrated in PROFINET. PROFINET as an Ethernet-based automation standard from PROFIBUS International defines a vendor-independent communications and engineering model.
PRELIMINARY II 1.7.2010 Glossary Project A project is the result of a configuration using an configuration software. The project normally contains several HMI screens, in which plant-specific objects are embedded. If it has been configured in WinCC flexible, the project is saved in a project file with the file name extension, "hmi". You need to distinguish between the project on the configuration PC and the runtime project on an HMI device.
PRELIMINARY II 1.7.2010 Glossary Runtime project file A runtime project file is a file that is generated from the finished project file for a specific HMI device based on the configuration. It can therefore only be run on a particular HMI device type. The runtime project file is transferred to the corresponding HMI device and used there to operate and monitor a production process. The file extension of a runtime project file is "fwx".
PRELIMINARY II 1.7.2010 Glossary System alarm A system alarm is assigned to the "System" alarm class. A system alarm refers to internal states on the HMI device and the PLC. Tab sequence The tab order is the configured order of the objects that are accessed by successively pressing the "TAB" key. Tag Defined memory location to which values can be written to and read from. This can be done from the PLC or the HMI device.
PRELIMINARY II 1.7.
PRELIMINARY II 1.7.
PRELIMINARY II 1.7.
PRELIMINARY II 1.7.
PRELIMINARY II 1.7.
PRELIMINARY II 1.7.
PRELIMINARY II 1.7.
PRELIMINARY II 1.7.
PRELIMINARY II 1.7.
PRELIMINARY II 1.7.
