L10 Operating and Programming Manual
L10 Operating and Programming Manual
L10 Operating and Programming Manual
Hydraulics
Pneumatics
Service
R911322944 Edition 01
Title
Operating and Programming Instructions DOK-CONTRL-IC*L10*****-AW01-EN-P RS-9db4a560c7626adf0a6846a00091ba7b-1-en-US-9 This documentation provides an overview on the system components belong ing to the control IndraLogic L10 and describes their project planning and programming.
Edition 120-0401-B344-01/EN Release Date 01.2008 Notes First edition
Record of Revision
Copyright
2007 Bosch Rexroth AG Copying this document, giving it to others and the use or communication of the contents thereof without express authority, are forbidden. Offenders are liable for the payment of damages. All rights are reserved in the event of the grant of a patent or the registration of a utility model or design (DIN 34-1).
Validity
The specified data is for product description purposes only and may not be deemed to be guaranteed unless expressly confirmed in the contract. All rights are reserved with respect to the content of this documentation and the availa bility of the product. Bosch Rexroth AG Bgm.-Dr.-Nebel-Str. 2 97816 Lohr am Main, Germany Phone +49 (0)93 52/ 40-0 Fax +49 (0)93 52/ 40-48 85 http://www.boschrexroth.com/ Dep. BRC/EAY2 (MK/MePe) Dep. BRC/EAC4 (BA/MePe)
Published by
Note
I/III
Table of Contents
Table of Contents
Page
1
1.1 1.2
2
2.1 2.1.1 2.1.2 2.2
3
3.1 3.1.1 3.1.2 3.1.3 3.1.4 3.2 3.2.1 3.2.2 3.2.3 3.2.4 3.2.5 3.2.6 3.2.7 3.2.8
4
4.1 4.2 4.3 4.3.1 4.3.2
4.3.3
4.3.4
II/III
Table of Contents Page 4.5 4.5.1 4.5.2 4.5.3 4.6 4.6.1 Project Rexroth Inline Modules ............................................................................................................ 29 Overview............................................................................................................................................ 29 Inserting Inline Modules..................................................................................................................... 29 Configuring Inline Modules................................................................................................................ 30 IndraLogic L10 as Ethernet/IP Slave ................................................................................................... 32 Configuring IndraLogic L10 as Ethernet/IP Slave ............................................................................. 32 Overview......................................................................................................................................... 32 Adapting Slave-Specific Basic Settings.......................................................................................... 32 Parameterizing the Coupling Area.................................................................................................. 34 Ethernet/IP Connection Types........................................................................................................ 36 Features of the Cyclic Data Transmission...................................................................................... 37 Configuring IndraLogic L10 as CIP Data Server............................................................................... 38 Overview......................................................................................................................................... 38 Projecting........................................................................................................................................ 38 Features of the Acyclic Data Transmission.................................................................................... 38 Configuring IndraLogic L10 as CIP Data Client................................................................................. 39 PLC Programming with IndraLogic ...................................................................................................... 39 Overview............................................................................................................................................ 39 Target Settings ................................................................................................................................. 40 Task Configuration ........................................................................................................................... 42 Library Manager ............................................................................................................................... 43 Creating a PLC Program .................................................................................................................. 45 Saving IndraLogic Project Data ........................................................................................................ 46 Compatible IEC Programming between Different Controls.................................................................. 46 Overview............................................................................................................................................ 46 Using of Pointers within Structures ................................................................................................... 47 Packing Structures for IndraLogic L10/20......................................................................................... 48 Alignment for I/O Addresses ............................................................................................................. 49 Assigning Structures to I/O Addresses ............................................................................................. 50 Download and Commissioning............................................................................................................. 50 Loading Configurations and PLC Program into the Control ............................................................. 50 Online Functions ............................................................................................................................... 50
4.6.2
4.6.3 4.7 4.7.1 4.7.2 4.7.3 4.7.4 4.7.5 4.7.6 4.8 4.8.1 4.8.2 4.8.3 4.8.4 4.8.5 4.9 4.9.1 4.9.2
5
5.1 5.1.1 5.2 5.3
Additional Functions..................................................................................................... 55
Firmware Management......................................................................................................................... 55 Firmware Update Control ................................................................................................................. 55 Importing IndraLogic Project Data ....................................................................................................... 56 IndraLogic Functions ........................................................................................................................... 56
6
6.1 6.2 6.2.1 6.2.2 6.3
Libraries ...................................................................................................................... 59
Overview............................................................................................................................................... 59 BuepE_Client ....................................................................................................................................... 60 General Information........................................................................................................................... 60 BuepE_Client..................................................................................................................................... 60 RIH_CML10 ......................................................................................................................................... 62
III/III
Table of Contents Page 6.3.1 6.3.2 6.3.3 6.4 6.5 6.5.1 6.5.2 6.5.3 6.5.4 6.5.5 Overview............................................................................................................................................ 62 IH_GetOhcCtrl .................................................................................................................................. 62 IH_SetDisplay ................................................................................................................................... 63 RIL_Check ........................................................................................................................................... 63 RIL_EtherNetIP..................................................................................................................................... 65 Overview............................................................................................................................................ 65 IL_ReadDataTable............................................................................................................................. 65 IL_WriteDataTable............................................................................................................................. 67 Error Messages IL_ReadDataTable and IL_WriteDataTable............................................................ 69 IL_Status............................................................................................................................................ 70 General Information........................................................................................................................ 70 Example.......................................................................................................................................... 70 Error Messages of IL_Status............................................................................................................. 71 RIL_VExUtil........................................................................................................................................... 71 IL_VExKeys....................................................................................................................................... 71
7
7.1 7.2 7.3 7.3.1 7.3.2 7.3.3 7.3.4 7.3.5 7.3.6 7.3.7 7.3.8 7.4
8
8.1 8.2
9
9.1 9.2 9.3 9.4
Index............................................................................................................................ 83
1/84
System Overview
1
1.1
System Overview
Components
Control
The control IndraLogic L10 consists of: Hardware: IndraControl L10 including plug set Firmware: IndraLogic L10 (on Compact Flash Card)
The modular and scalable hardware platform IndraControl L10 can be used in combination with the IndraLogic L10 Firmware for PLC applications.
Software
The software "IndraWorks Logic" serves to commission and project the IndraLogic L10. It consists of the following components: IndraWorks: Project planning, configuration IndraLogic: PLC programming IndraWorks HMI: Visualization and user interface as well as diagnostic functions (ProVi) IndraWorks WinStudio: Engineering tool to create user screens for Indra Works HMI IndraLogic L10 TSP: Target system files (Target Support Package) to edit the IndraLogic L10 using IndraWorks and IndraLogic Target Manager: Tool for TSP data administration and installation, Inline module description files and libraries
1.2
No Title . /1/ /2/ /3/ /4/ /5/ /6/ /7/
Related Documentation
Identification DOK-CONTRL-IC*L10*****-PR..-EN-P DOK-CONTRL-IL**PRO*V02-AW..-EN-P DOK-CONTRL-R-IL*PBSSYS-AW..-EN-P DOK-CONTRL-R-IL*PB*-BK-FK..-EN-P DOK-IWORKS-ENGINEE*V..-AW..-EN-P DOK-CONTRL-WIS*PC**V06-KB..-EN-P Rexroth IndraControl L10; Project Planning Manual PLC Programming with Rexroth IndraLogic; Operating and Programming Instructions Rexroth Inline Profibus DP; Application Manual Rexroth Inline Profibus DP Terminal and Module Supply; Functional Description Rexroth IndraWorks Engineering; Operating and Program ming Instructions Rexroth WinStudio; Overall View
Rexroth PLCopen Function Blocks For Field Bus Drives; Ap DOK-CONTRL-PLCOPENFB*D-AW..-EN-P plication Manual
Fig.1-1:
Related documentation
3/84
2
2.1
2.1.1
Physical and property damage due to the inappropriate use of products! WARNING
The products are designed for their use within the industrial environment and may therefore only be used for the intended purpose. If the use is inappropriate, situations causing physical damage as well as property damage can occur. Rexroth disclaims as manufacturer any warranty, liability or for damages occurring due to inappropriate use of the products. Fur thermore, Rexroth is not paying any compensation. The user is responsible for any risks resulting from the products not being used as intended. Before using Rexroth products, the following pre-requisites must be fulfilled to ensure an appropriate use of the products: Anyone handling one of the Rexroth products in any way has to read and understand the respective safety instructions as well as the instructions on the appropriate use. Hardware products have to remain in their original state, in other words, no modification regarding the design are allowed. Software products may not be decompiled and their source codes may not be modified. Damaged or faulty products are not to be implemented or put into opera tion. It is to be ensured that the corresponding products are installed according to the specifications of the documentation.
2.1.2
4/84
Important Instructions on Use The Systemen IndraLogic L10 may only be operated under the assembly con ditions and installation conditions, in the specified position of application and under the specified ambient conditions (temperature, degree of protection, hu midity, EMC etc.) given in this documentation.
2.2
Inappropriate Use
The application of IndraLogic L10 that are not within the specified areas of ap plication or under operating conditions deviating from the operating conditions and technical data specified in the documentation is considered as "inappro priate". IndraLogic L10 may not be used if ... they are exposed to operating conditions that do not fulfill the ambient conditions specified. Operation under water, under extreme temperature fluctuations or extreme maximum temperatures is not allowed for exam ple:. the Rexroth applications that are not released explicitly. Please note the general statements in the general safety instructions! when using in household devices or devices belonging to the categories 1 to 7 and 10 of the directive 2002/96/EC ("WEEE") in the appendix IA.
5/84
3
3.1
3.1.1
WARNING
Improper use of these devices, failure to follow the safety instructions in this document or tampering with the product, including disabling of safe ty devices, may result in material damage, bodily harm, electric shock or even death!
Observe the safety instructions!
3.1.2
6/84
Safety Instructions for Electric Drives and Controls Follow all safety regulations and requirements for the specific application as practiced in the country of use. The devices have been designed for installation in industrial machinery. The ambient conditions given in the product documentation must be ob served. Only use safety-relevant applications that are clearly and explicitly ap proved in the Project Planning Manual. If this is not the case, they are excluded. Safety-relevant are all such applications which can cause dan ger to persons and material damage. The information given in the documentation of the product with regard to the use of the delivered components contains only examples of applica tions and suggestions. The machine and installation manufacturer must make sure that the delivered components are suited for his individual application and check the information given in this documentation with regard to the use of the components, make sure that his application complies with the applicable safety regulations and standards and carry out the required measures, modifications and complements.
Commissioning of the delivered components is only permitted once it is sure that the machine or installation in which they are installed complies with the national regulations, safety specifications and standards of the application. Operation is only permitted if the national EMC regulations for the appli cation are met. The instructions for installation in accordance with EMC requirements can be found in the section on EMC in the respective documentation (Project Planning Manuals of components and system). The machine or installation manufacturer is responsible for compliance with the limiting values as prescribed in the national regulations.
Technical data, connection and installation conditions are specified in the product documentation and must be followed at all times.
National regulations which the user must take into account European countries: according to European EN standards United States of America (USA): National Electrical Code (NEC) National Electrical Manufacturers Association (NEMA), as well as local engineering regulations regulations of the National Fire Protection Association (NFPA) Canada: Canadian Standards Association (CSA) Other countries: International Organization for Standardization (ISO) International Electrotechnical Commission (IEC)
3.1.3
7/84
Warning symbol
Signal word
Danger
Warning
Caution
Fig.3-1:
3.1.4
DANGER
Dangerous movements! Danger to life, severe bodily harm or material damage by unintentional motor movements! DANGER
Observe the safety instructions!
High electric voltage because of incorrect connection! Risk of death or bodily injury by electric shock! WARNING
Observe the safety instructions!
Health hazard for persons with heart pacemakers, metal implants and hearing aids in proximity to electrical equipment! WARNING
Observe the safety instructions!
CAUTION Risk of injury by improper handling! Risk of bodily injury by bruising, shearing, cutting, hitting or improper handling of pressurized lines! CAUTION
Observe the safety instructions!
8/84
CAUTION
3.2
3.2.1
High electrical voltage! Danger to life, electric shock and severe bodily injury! DANGER
Only those trained and qualified to work with or on electrical equipment are permitted to operate, maintain and repair this equipment. Follow general construction and safety regulations when working on pow er installations. Before switching on the device, the equipment grounding conductor must have been non-detachably connected to all electrical equipment in ac cordance with the connection diagram. Do not operate electrical equipment at any time, even for brief measure ments or tests, if the equipment grounding conductor is not permanently connected to the mounting points of the components provided for this purpose. Before working with electrical parts with voltage potentials higher than 50 V, the device must be disconnected from the mains voltage or power supply unit. Provide a safeguard to prevent reconnection. With electrical drive and filter components, observe the following: Wait 30 minutes after switching off power to allow capacitors to discharge before beginning to work. Measure the electric voltage on the capacitors before beginning to work to make sure that the equipment is safe to touch. Never touch the electrical connection points of a component while power is turned on. Do not remove or plug in connectors when the component has been powered. Install the covers and guards provided with the equipment properly before switching the device on. Before switching the equipment on, cover and safeguard live parts safely to prevent contact with those parts. A residual-current-operated circuit-breaker or r.c.d. cannot be used for electric drives! Indirect contact must be prevented by other means, for example, by an overcurrent protective device according to the relevant standards. Secure built-in devices from direct touching of electrical parts by providing an external housing, for example a control cabinet.
9/84
Safety Instructions for Electric Drives and Controls For electrical drive and filter components with voltages of more than 50 volts, observe the following additional safety instructions.
High housing voltage and high leakage current! Risk of death or bodily injury by electric shock! DANGER
Before switching on, the housings of all electrical equipment and motors must be connected or grounded with the equipment grounding conductor to the grounding points. This is also applicable before short tests. The equipment grounding conductor of the electrical equipment and the devices must be non-detachably and permanently connected to the power supply unit at all times. The leakage current is greater than 3.5 mA. Over the total length, use copper wire of a cross section of a minimum of 10 mm2 for this equipment grounding connection! Before commissioning, also in trial runs, always attach the equipment grounding conductor or connect to the ground wire. Otherwise, high vol tages may occur at the housing causing electric shock.
3.2.2
High electric voltage by incorrect connection! Risk of death or bodily injury by electric shock! WARNING
If extra-low voltage circuits of devices containing voltages and circuits of more than 50 volts (e.g. the mains connection) are connected to Rexroth products, the connected extra-low voltage circuits must comply with the requirements for PELV. 2)
3.2.3
Dangerous movements can occur immediately after equipment is switched on or even after an unspecified time of trouble-free operation.
1) 2)
10/84
Safety Instructions for Electric Drives and Controls The monitoring in the drive components will normally be sufficient to avoid faulty operation in the connected drives. Regarding personal safety, especially the danger of bodily harm and material damage, this alone cannot be relied upon to ensure complete safety. Until the integrated monitoring functions become effective, it must be assumed in any case that faulty drive movements will occur. The extent of faulty drive movements depends upon the type of control and the state of operation.
11/84
Dangerous movements! Danger to life, risk of injury, severe bodily harm or material damage! DANGER
Ensure personal safety by means of qualified and tested higher-level monitoring devices or measures integrated in the installation. These measures have to be provided for by the user according to the specific conditions within the installation and a hazard and fault analysis. The safety regulations applicable for the installation have to be taken into consideration. Unintended machine motion or other malfunction is possi ble if safety devices are disabled, bypassed or not activated. To avoid accidents, bodily harm and/or material damage: Keep free and clear of the machines range of motion and moving parts. Possible measures to prevent people from accidentally entering the machines range of motion: use safety fences use safety guards use protective coverings install light curtains or light barriers
Fences and coverings must be strong enough to resist maximum possible momentum. Mount the emergency stop switch in the immediate reach of the operator. Verify that the emergency stop works before startup. Dont operate the device if the emergency stop is not working. Isolate the drive power connection by means of an emergency stop circuit or use a safety related starting lockout to prevent unintentional start. Make sure that the drives are brought to a safe standstill before accessing or entering the danger zone. Additionally secure vertical axes against falling or dropping after switching off the motor power by, for example: mechanically securing the vertical axes, adding an external braking/ arrester/ clamping mechanism or ensuring sufficient equilibration of the vertical axes.
The standard equipment motor brake or an external brake controlled di rectly by the drive controller are not sufficient to guarantee personal safety! Disconnect electrical power to the equipment using a master switch and secure the switch against reconnection for: maintenance and repair work cleaning of equipment long periods of discontinued equipment use
Prevent the operation of high-frequency, remote control and radio equip ment near electronics circuits and supply leads. If the use of such devices cannot be avoided, verify the system and the installation for possible mal functions in all possible positions of normal use before initial startup. If necessary, perform a special electromagnetic compatibility (EMC) test on the installation.
12/84
3.2.4
Protection Against Magnetic and Electromagnetic Fields During Oper ation and Mounting
Magnetic and electromagnetic fields generated by current-carrying conductors and permanent magnets in motors represent a serious personal danger to those with heart pacemakers, metal implants and hearing aids.
Health hazard for persons with heart pacemakers, metal implants and hearing aids in proximity to electrical equipment! WARNING
Persons with heart pacemakers and metal implants are not permitted to enter following areas: Areas in which electrical equipment and parts are mounted, being operated or commissioned. Areas in which parts of motors with permanent magnets are being stored, repaired or mounted.
If it is necessary for somebody with a pacemaker to enter such an area, a doctor must be consulted prior to doing so. The noise immunity of pres ent or future implanted heart pacemakers differs greatly so that no general rules can be given. Those with metal implants or metal pieces, as well as with hearing aids, must consult a doctor before they enter the areas described above. Oth erwise health hazards may occur.
3.2.5
CAUTION
Do not touch surfaces of device housings and chokes in the proximity of heat sources! Danger of burns! Do not touch housing surfaces of motors! Danger of burns! According to the operating conditions, temperatures can be higher than 60 C, 140F during or after operation. Before accessing motors after having switched them off, let them cool down for a sufficiently long time. Cooling down can require up to 140 mi nutes! Roughly estimated, the time required for cooling down is five times the thermal time constant specified in the Technical Data. After switching drive controllers or chokes off, wait 15 minutes to allow them to cool down before touching them. Wear safety gloves or do not work at hot surfaces. For certain applications, the manufacturer of the end product, machine or installation, according to the respective safety regulations, has to take measures to avoid injuries caused by burns in the end application. These measures can be, for example: warnings, guards (shielding or barrier), technical documentation.
3.2.6
13/84
Risk of injury by improper handling! Bodily injury by bruising, shearing, cutting, hitting! CAUTION
Observe the general construction and safety regulations on handling and mounting. Use suitable devices for mounting and transport. Avoid jamming and bruising by appropriate measures. Always use suitable tools. Use special tools if specified. Use lifting equipment and tools in the correct manner. If necessary, use suitable protective equipment (for example safety gog gles, safety shoes, safety gloves). Do not stand under hanging loads. Immediately clean up any spilled liquids because of the danger of skidding.
3.2.7
Battery Safety
Batteries consist of active chemicals enclosed in a solid housing. Therefore, improper handling can cause injury or material damage.
CAUTION
Do not attempt to reactivate low batteries by heating or other methods (risk of explosion and cauterization). Do not recharge the batteries as this may cause leakage or explosion. Do not throw batteries into open flames. Do not dismantle batteries. When replacing the battery/batteries do not damage electrical parts in stalled in the devices. Only use the battery types specified by the manufacturer. Environmental protection and disposal! The batteries contained in the product are considered dangerous goods during land, air, and sea transport (risk of explosion) in the sense of the legal regulations. Dispose of used batteries separate from other waste. Observe the local regulations in the country of assembly.
3.2.8
14/84
CAUTION
Do not attempt to disconnect, open or cut pressurized lines (risk of explo sion). Observe the respective manufacturer's operating instructions. Before dismounting lines, relieve pressure and empty medium. Use suitable protective equipment (for example safety goggles, safety shoes, safety gloves). Immediately clean up any spilled liquids from the floor. Environmental protection and disposal! The agents used to operate the product might not be economically friendly. Dispose of ecolog ically harmful agents separately from other waste. Observe the local regulations in the country of assembly.
15/84
4
4.1
The IndraWorks Logic package is installed. The target system information (Target Support Package) of the IIndraLogic L10 are available in IndraWorks. All relevant data are auto matically generated during the installation of IndraWorks. IndraWorks Engineering is started. An IndraWorks project exists and is indicated in the project explorer. For detailed information on the user interface and the handling of IndraWorks refer to the IndraWorks documentation /5/ or online help.
Required Steps
1. 2. 3. 4. 5.
Creating a new IndraLogic L10 device with IndraWorks. Defining basic settings with IndraWorks. Defining field bus and I/O configuration with IndraWorks. PLC programming with IndraLogic. Loading configuration and PLC program data into the hardware of the IndraLogic L10 and activating them with IndraWorks.
4.2
16/84
Fig.4-1:
4.3
4.3.1
Fig.4-2:
Device Name Comment Author
Device settings
Please enter here any device name. The field contains by default the name of the library. With this name the project appears later in the project explorer. Please enter here any comment to describe the device in detail. Please enter here the name of the project author.
17/84
Project Planning and Programming These details can still be changed later, please refer to chapter 4.3.5 "Modifying Basic Settings" on page 23. Confirm the settings with "Next >>".
4.3.2
General Information
Fig.4-3:
Enter the Firmware version and the settings for the field bus interfaces
After inserting the new IndraLogic L10 device into the project ex plorer, versions can no longer be modified!
Target and Firmware release DP Onboard
Select the target system version and the Firmware for this version. This also affects further settings provided in this dialog. "Profibus/M": Via the onboard Profibus DP interface (X7P) subordinated Profi bus DP slaves are to be coupled to the IndraLogic L10. From the view of the slave connected there the IndraLogic L10 is its master. "Profibus/S": Via the onboard Profibus DP interface (X7P) the IndraLogic L10 is to be coupled to a superordinated Profibus DP master as subordinated Pro fibus DP slave.
Ethernet/IP Slave
Activate this option to use the IndraLogic L10 via the onboard Ethernet interface (X7E) as follows: As CIP data server(CIP: Communication Industrial Protocol): Allows the simultaneous access for a maximum of 6 CIP data clients to enabled var iables of the IndraLogic L10 via acyclic DataTable services ("Unconnected Explicit Messaging" and "Class 3 Connected Messaging"). As CIP data client: Allows the access to enabled variables via the "RIL_EtherNetIP" library of a CIP data server via acyclic DataTable serv ices. As Ethernet/IP slave (target): Allows the cyclic exchange of I/O data blocks with a superordinated control (master/originator) via an "Exclusive Owner
18/84
Project Planning and Programming Connection", (Transport Class 1) and a further "Listen Only Connection", (Transport Class 1).
Type of Addressing
Click on the "Extended..." button to set the desired I/O addressing type (byte or word). Basic settings of the I/O addressing type: lower than Firmware version 03 VRS: word higher than Firmware version 03 VRS: Bytes
Fig.4-4:
Select the setting which corresponds to the type of addressing in the PLC pro grams to be used. For word addressing applies for example: Output byte 10 (QB10) is addressed by "QW5". For byte addressing applies: Output byte 10 (QB10) is addressed by "QW10". After inserting the new IndraLogic L10 device into the project ex plorer the type of addressing can no longer be modified! Confirm the settings with "Next >>". The dialog to define the communication settings opens.
4.3.3
Communication Settings
Define here the settings for the communication between IndraWorks and the IndraLogic L10. When opening this dialog the IndraLogic gateway server used to enable the communication starts automatically. If the gateway server is al ready provided with communication settings, it is possible to select a setting via the "Channels" dropdown list. If there is no entry yet, a dialog to create a communication channel appears automatically. If there is no suitable entry, a new or modify an already existing communication channel can be created. Click on the "Communication parameters..."button. Further procedure is described in chapter "Communication Param eters" on page 19.
General Information
19/84
Fig.4-5:
The boxes highlighted in gray indicate the parameters of the entry selected under "Channels". The communications settings have to correspond to the actual setting of the IndraLogic L10 also refer to chapter 7.3.4 "Network Configuration " on page 76 or chapter 7.4 "Network Settings via Configuration File" on page 78. Further information about the topic "Communication" in provided in the IndraLogic help, or in the IndraLogic manual /2/. Finish the settings by pressing the "Finish" button. With this action, the wizardguided basic settings are terminated. The new IndraLogic L10 device appears in the project explorer. The basic settings can be changed later, refer to chapter 4.3.5 "Modifying Basic Settings" on page 23. More detailed information on the device are available in chapter 4.3.4 "Com ponents of the IndraLogic L10 Device" on page 21.
Communication Parameters
New communication channels (communication instances) can be created, modified or deleted in the dialog "Communication Parameters".
20/84
Fig.4-6:
Communication parameters
Create a new communication channel: Click on the "New... "button to create a new communication channel. The following dialog appears:
Name Device
Fig.4-7:
Name Device
Please enter here a name for the new communication channel. Select the desired communication driver in the field "Device" to communicate between IndraWorks and the IndraLogic L10. Click in the "Name" column on the corresponding line and confirm the settings with the "OK" button. The new communication channel appears in area in fig. 4-8 "Adapt the pa rameters of a communication channel" on page 21.
21/84
Fig.4-8:
Modify a communication channel: Select the new communication channel with the left mouse button and adapt its parameters. For this, double-click on the corresponding line in area (see fig. 4-8 "Adapt the parameters of a communication channel" on page 21) and change the entry in the "Value" column according to the requirements. Confirm the modifications with the <Enter> key. Delete a communication channel: Select the desired communication channel and click on the "Delete" button. Further information on the individual parameters is provided in the IndraLogic help, or in the IndraLogic manual /2/.
4.3.4
General Information
22/84
Fig.4-9:
The object tree of the IndraLogic L10 can contain the following objects: "Logic": part of the IndraLogic L10 device responsible for processing by programming of all I/O signals. This includes e. g. PLC modules (POUs), the PLC task management and global variables. Double-clicking on the object "Logic" object starts IndraLogic with the target system "IndraLogic L10". "Onboard I/O": local I/O area of the IndraLogic L10 (Onboard I/O). This equipped with 8 high-speed inputs and 8 high-speed outputs each. The configuration is described in chapter 4.4 "Configure Onboard I/O " on page 25. "Inline I/O": Local Inline I/O area of the IndraLogic L10. It contains the I/ Os of Rexroth Inline modules that can be coupled to the IndraLogic L10. The configuration is described in chapter 4.5 "Project Rexroth Inline Mod ules " on page 29. "EthernetIP slave": only available, if the IndraLogic L10 has been config ured as Ethernet/IP slave, see fig. 4-3 "Enter the Firmware version and the settings for the field bus interfaces" on page 17. The corresponding settings of the IndraLogic L10 can be configured using this object, refer to chapter 4.6.1 "Configuring IndraLogic L10 as Ethernet/IP Slave " on page 32.
23/84
4.3.5
Use the "Properties" menu item in the context menu of the IndraLogic L10 de vice.
Fig.4-10:
The dialog to modify the device settings appears, see fig. 4-2 "Device settings" on page 16.
Modifying Communication Settings
Use the "Properties" menu item in the context menu of the object"Logic".
Fig.4-11:
24/84
Fig.4-12:
Please note the chapter 4.3.3 "Communication Settings" on page 18. Besides the communication settings, the tabs also provide also fur ther settings (see fig. 4-13 "The tab "Further settings" in the project settings" on page 25). For further information refer to the docu mentation and the online help of IndraWorks /5/.
25/84
Fig.4-13:
4.4
4.4.1
26/84
Fig.4-14:
Inputs Outputs
The digital inputs and outputs available on the slots 1 to 4 (from the left to the right) are assigned to light-emitting diodes and bit addresses according to the following table:
Inputs Slot Status LED Byte-bit view Byte Bit Module Terminal point (signal) Terminal point (24 V) Terminal point (last ground) 0 1.1 1.2 1 2.1 2.2 1 2 1 3 4 1 2 2 3 4 1 2 Outputs 3 3 4
IX0.0 0.7 (Standard) 2 1.4 1.3 3 2.4 2.3 4 1.1 1.2 5 2.1 2.2 6 1.4 1.3 7 2.4 2.3 -
QX0.0 0.7 (Standard) 0 1.1 1.2 1 2.1 2.2 2 1.4 1.3 3 2.4 2.3
Fig.4-15:
27/84
Fig.4-16:
Fig.4-17:
"Onboard settings"
Name: Internal name, specified by the installed target device. Based on: Name of the used device description file. The file is a fixed part of the installed target system. ID: Internal ID, specified by the installed target system. Comment: Please enter here any comment to describe the onboard I/O in detail.
Assign here the I/O areas of the onboard I/O to the physical addresses of the control (I/O addresses of the PLC). Identifier: This column shows the two input and output modules. It is possible to switch between the byte and bit view with the plus and minus symbol. For each absolute address the assignment of a symbolic address is possible (double-click on the particular field). After entering the symbolic address, it is created automatically as global variable in the PLC project. The symbolic address of a node also appears in the project explorer:
28/84
Fig.4-18:
Address: I/O address. Enter the desired I/O address as byte address (e. g. % IB10). Entries in italics serve only for display and cannot be edited. An automatic readdressing is possible in the "I/O settings" tab. Data type: Byte addresses are identified with "BYTE", bit addresses with "BOOL". Comment: Please enter here any comment about an address. Status: Physical status of the input/output. The status is only indicated in diag nostic mode during the communication between IndraWorks and IndraLogic L10.
Register "I/O addresses"
Start here the automatic assignment of I/O addresses. From output/From input: Current or desired start addresses of the outputs and inputs. "Apply": Renumbers automatically all outputs/inputs of the onboard I/O in as cending order starting with the indicated start addresses (see "From output / From input"). Please note, that existing address gaps are closed during this process! If the automatic numbering causes collisions with already assigned address areas, IndraWorks indicates the collision cause and determines automatically the next free address area.
29/84
Fig.4-19:
4.5
4.5.1
4.5.2
30/84
Fig.4-20:
4.5.3
Fig.4-21:
31/84
Fig.4-22:
"Module settings"
Name: Internal name, specified by the installed target system. Based on: Path and name of the used device description file. The file is a fixed part of the installed target system. ID: Internal ID, specified by the installed target system. Comment: Please enter here any comment to describe the Inline module in a detailed manner.
Assign here the I/O areas of the Inline modules to the physical addresses of the control (I/O addresses of the PLC). Identifier: This column shows the input and output structure. It is possible to switch between the byte and bit view with the plus and minus symbol. For each absolute address the assignment of a symbolic address is possible (double-click on the particular field). After entering the symbolic address, it is created automatically as global variable in the PLC project. The symbolic address of a node also appears in the project explorer. In fig. 4-18 "Symbolic and absolute addresses of I/O objects" on page 28 an example is shown for onboard I/O. Address: I/O address. Enter the desired I/O address as byte address (e. g. % IB10). Entries in italics serve only for display and cannot be edited. An automatic readdressing is possible in the "I/O settings" tab. Data type: Byte addresses are identified with "BYTE", bit addresses with "BOOL". Comment: Please enter here any comment about an address.
32/84
Project Planning and Programming Status: Physical status of the input/output. The status is only indicated in diag nostic mode during the communication between IndraWorks and IndraLogic L10.
Register "I/O addresses"
Start here the automatic assignment of I/O addresses. From output/From input: Current or requested initial addresses of the inputs and output. Corresponding to the used Inline module functionality (module with inputs, module with outputs) only relevant input boxes are indicated. Parame terizing an Inline module with only inputs for example, the input box "From output" is missing. "Apply": Renumbers automatically all outputs/inputs of the Inline module in as cending order starting with the indicated start addresses (see "From output / From input"). Please note, that existing address gaps are closed during this process! If the automatic numbering causes collisions with already assigned address areas, IndraWorks indicates the collision cause and determines automatically the next free address area.
Fig.4-23:
4.6
4.6.1
Overview
33/84
Fig.4-24:
Fig.4-25:
"Ethernet/IP Slave Settings"
Name: Internal device name of the slave Based on: Name of the used device description file. The file is a fixed part of the installed target system. ID: Internal ID, specified by the installed target system. Comment: Please enter here any comment to describe the slave in a detailed manner.
Start here the automatic assignment of I/O addresses. From output/From input: Desired start addresses for the automatic numbering of the I/O coupling area. "Apply": Renumbers automatically all outputs/inputs of the I/O coupling area in ascending order starting with the indicated start addresses (see "From output /
34/84
Project Planning and Programming From input"). Please note, that existing address gaps are closed during this process! If the automatic numbering causes collisions with already assigned address areas, IndraWorks indicates the collision cause and determines automatically the next free address area.
Fig.4-26:
Select the data capacity for the input and output box of the Ethernet/IP slave
To configure the inputs/outputs, double-click on the corresponding module en try in the project explorer. A window opens in the workspace:
35/84
Fig.4-27:
"Ethernet/IP module settings"
Name: Internal name, specified by the installed target system. Based on: File name of the used device description file. The file is a fixed part of the installed target system. Assembly Instance: Internal identification. Comment: Any text to describe the I/O field in a detailed manner.
Assign here the coupling area to the physical addresses of the control (I/O ad dresses of the PLC). The addresses are the local I/O addresses of the IndraLogic L10. Identifier: This column shows the input and output structure. It is possible to switch between the byte and bit view with the plus and minus symbol. For each absolute address the assignment of a symbolic address is possible (double-click on the particular field). After entering the symbolic address, it is created automatically as global variable in the PLC project. The symbolic address of a node also appears in the project explorer. In fig. 4-18 "Symbolic and absolute addresses of I/O objects" on page 28 an example is shown for onboard I/O. Address: I/O address. Enter the desired I/O address as byte address (e. g. % IB10). Entries in italics serve only for display and cannot be edited. An automatic readdressing is possible in the "I/O settings" tab. Data type: Byte addresses are identified with "BYTE", bit addresses with "BOOL". Comment: Please enter here any comment about an address.
36/84
Project Planning and Programming Status: Physical status of the input/output. The status is only indicated in diag nostic mode during the communication between IndraWorks and IndraLogic L10.
Register "I/O addresses"
Start here the automatic assignment of I/O addresses. From output/From input: Current or desired start addresses for the automatic numbering of the I/O coupling area. "Apply": Renumbers automatically all outputs/inputs of the I/O coupling area in ascending order starting with the indicated start addresses (see "From output / From input"). Please note, that existing address gaps are closed during this process! If the automatic numbering causes collisions with already assigned address areas, IndraWorks indicates the collision cause and determines automatically the next free address area.
Fig.4-28:
37/84
Fig.4-29:
The consumer instance of the IndraLogic L10 monitors the cyclic transmission of the master output image by means of a monitoring time (timeout time). For this, the IndraLogic L10 receives during the initialization of the cyclic data chan nel corresponding parameters from the master. The resulting monitoring time can be calculated using the following formulas:
Fig.4-30:
Timeout Multiplier Value Timeout Multiplier Requested Packet Interval (in s) Monitoring time (in ms)
Examples:
38/84
Fig.4-31:
4.6.2
Overview
Projecting
To use the IndraLogic L10 as CIP data server please execute the following steps: 1. Define the IndraLogic L10 as Ethernet/IP slave, refer to chapter 4.3.2 "Device and Function Module Settings" on page 17. Only in this case the required subordinated "Ethernet/IP slave" object is available in the project explorer. If no additional cyclic communication is required, parameterize the data capacities of the I/O coupling area equal to 0. For this, use the particular context menu item "Replace module" and select the modules "0 Byte In put" or "0 Byte Output...", see fig. 4-26 "Select the data capacity for the input and output box of the Ethernet/IP slave" on page 34. Define the variables relevant in IndraLogic. Ensure that the options "Generate icon entries" and "Generate XML icon table" are activated in IndraLogic under Project Options Icon config uration. Open the IndraLogic dialog "Set object attributes" via Project Options Icon configuration Configure icon file. Select the desired variables and activate the "Output variables of the object" option. The "Writing access" option affects the write protection of a variable. To avoid an external overwriting of the variable value, deactivate the writing access.
2.
3. 4.
5.
39/84
Project Planning and Programming The data server acknowledges the read and write accesses. Reasons for negative acknowledgements are listed in the following table:
Error code 0x1F 0x1F 0x1F 0x1F Additional error code 0x0101 0x0106 0x0107 0x0108
Description No symbol information for variable available Variable is read-only Too many data sent during the write access Too less data sent during the write access
Fig.4-32:
4.6.3
2.
3. 4.
4.7
4.7.1
40/84
Project Planning and Programming The PLC project planning with IndraLogic is activated via the "Logic" object in the project explorer.
Fig.4-33:
Double-clicking on the object "Logic" object starts IndraLogic with the tar get system "IndraLogic L10". By double-clicking on an entry below "POEs" (e.g. PLC_PRG) the corre sponding module is opened in IndraLogic for further editing, refer to chapter 4.7.5 "Creating a PLC Program " on page 45. By double-clicking on "Tasks" the task configuration starts in IndraLogic, refer to chapter 4.7.3 "Task Configuration " on page 42.
Update Project
All modules generated in IndraLogic as well as the modifications of the settings are applied in the IndraWorks project explorer as soon as the context menu function "Update" is selected in the "Logic" object:
Fig.4-34:
4.7.2
Target Settings
Each modification of the preset target configuration can have serious effects on the behavior of the target system!
CAUTION
The target settings may only be modified by instructed specialists, who are aware of the effects of this modifications! The target settings are optimized to the most frequently used applications. For special applications some settings can be adapted. The target settings are modified via the properties dialog of the "Logic" object, when the application IndraLogic is closed. Settings, that are not available on the IndraWorks level (e.g. "Network func tions") can be made in IndraLogic under "Target settings". These settings can be reached in IndraLogic by clicking on "Target settings" in the "Resources"
41/84
Project Planning and Programming tab, refer to fig. 4-35 "IndraLogic, resources, "target settings" object" on page 41. For further information about the target settings refer to the docu mentation and the online help of IndraLogic /2/.
Fig.4-35:
Interrupting the Database Connec tion
Usually, a connection to the database server is active. If a connection is active, it can be recognized by the addition "<R>" in the name of the "Target set tings" object. To be able to modify the target settings, at first, the connection to the database has to be interrupted. For this, select in the context menu of the target settings menu item Project database Check Out, refer to fig. 4-36 "Target settings: Check out from the database" on page 42. After changing the target settings the database connection can be reestablished via Project database Check In. After modifying the settings menu function Project database Get Latest Version can be executed to synchronize the database between IndraWorks and IndraLogic.
42/84
Fig.4-36:
4.7.3
Task Configuration
For many application cases it is sufficient to execute the program without spe cial task management. The program processing is simply executed via the "Main program" PLC_PRG. PLC_PRG is automatically generated as module of type "Program" and is called up exactly one time in each control cycle. For special application cases it is possible to control the processing of the tasks. For this, the task configuration is required. Calling the task configuration: In the project explorer of IndraWorks: Double-click on the "Tasks" object of the relevant "Logic" objects - or in the "Resources" tab of IndraLogic: Double-click on the "Task configu ration" object.
43/84
Fig.4-37:
For further information about the task properties refer to the docu mentation and the online help of IndraLogic /2/. The IndraLogic L10 provides a special task-controlled function:
Triggered by External Event
A task can be started by a rising edge/ by rising edges at one or several onboard inputs. For this, select in the "Task properties" tab the "Triggered by external event" option and in the "Event" box the required event: Local input bit 0 ... Local input bit 7: As soon as a rising edge is applied to the selected bit input of the onboard I/O, the task is started. Local input byte: As soon as a rising edge is detected at least one of the eight onboard inputs, the task is started. Even if positive signal level are already applied to the individual inputs, the task starts with each new rising edge of an input. Simultaneously incoming rising edges are recognized as event and, thus, do not start the task several times. The independent task starts when the program is started. After ex ecution, it starts again without waiting time. In order to start other tasks, the independent task, must be the task with the lowest priority of all programmed tasks. It can only use one independent task.
4.7.4
Library Manager
For further information on the library manager refer to the docu mentation and the online help of IndraLogic /2/. Information on the libraries of the IndraLogic L10 are available in chapter 6 "Libraries " on page 59.
44/84
Project Planning and Programming With the IIndraLogic L10 already a few libraries are indicated in IndraLogic in register "Resources". IndraWorks loads libraries for internal use (refer to chapter 6 "Li braries " on page 59) automatically as soon as they are refer enced. It is not necessary to insert them manually with the library manager. To link further libraries with the current project, double-click at first in the "Re sources" tab on the "Library manager" object. The library manager opens:
Fig.4-38:
"Resources" tab "Library manager" object Display of the loaded libraries Display of all modules contained in a selected library
Library manager
Select menu function Insert Further library or in the context menu of area (3) Furthe"r" library... A dialog for library selection appears, refer to fig. 4-39 "Li brary directory of the IndraLogic L10 target" on page 45. Select the library directory of the installed IndraLogic L10 files (target files). The data are archived by default in directory "...\Rexroth\IndraWorks\IndraLogic \Targets\<TargetSystemName>\lib". Example: Library directory of the IndraLogic L10 03 VRS: "C:\ProgramFiles \Rexroth\IndraWorks\IndraLogic\Targets\ IndraLogic_L10_DP_04VRS\lib\"
45/84
Fig.4-39:
Select the required library and acknowledge the selection by pressing the "Open" button. The library can be applied and used in area (3) (refer to fig. 4-38 "Library manager" on page 44).
4.7.5
46/84
Fig.4-40:
4.7.6
4.8
4.8.1
47/84
4.8.2
Program:
TYPE OutStruct : STRUCT Out01 : BYTE; Out02 : WORD; Out03 : BYTE; Out04 : DWORD; END_STRUCT END_TYPE
Depending on the platform this structure is mapped to the memory as follows (here a comparison between the controls IndraLogic L10 and L20):
IndraLogic V, IndraLogic VEP, IndraLogic VPP, IndraLogic L40 ADR0 Out01 : BYTE; ADR1 Out02 : WORD; ADR3 Out03 : BYTE; ADR4 Out04 : DWORD; ADR8 : ADR0 Out01 : BYTE; ADR1 (filling byte) ADR2 Out02 : WORD; ADR4 Out03 : BYTE; ADR5 (filling byte) ADR6 (filling byte) ADR7 (filling byte) ADR8 Out04 : DWORD; ADR12 : IndraLogic L10/L20
Fig.4-41:
The structure elements are differently mapped, so that a compatible program ming method being independent of the control's mapping must be used when accessing the structure elements.
Permissible Addressing
Thus, the compatible use of structures provides for a direct addressing of the elements via the point operator: Structure name.Element name := Element value; If the address of a structure is to be transferred to subfunctions via a pointer, the addressing of the elements is also only permissible by the offset calculation of the compiler: Structure pointer^.Element name := Element value;
Program:
StructInst : OutStruct; pt : POINTER TO StructInst; (* Declaration structure instance *) (* Declaration pointer to structure instance *)
StructInst.Out03 := 2#11110000; (* Access to structure element *) pt := ADR (StructInst); pt^.Out02 := 16#FF00; (* Pointer initialization *) (* Access to structure element by pointer *)
48/84
The addressing of a structure element by calculations in the code is not al lowed: Structure element pointer := ADR (Structure name.Element); Structure element pointer := Structure element pointer + n; Structure element pointer^ := value; This is not allowed and causes incompatibilities, as it is not ensured, that the offset creation to address a structure element by calculation in the code is re liable. The number of filling bytes is different for the platforms.
4.8.3
Program:
STRUCT {pack} Element_01 : USINT; Element_02 : DWORD; Element_03 : BYTE; Element_04 : INT; END_STRUCT END_TYPE
The structure of this program listingis archived in the memory of the different systems as follows:
Byte ad dress IndraLogic V, IndraLogic VEP, IndraLogic VPP, IndraLogic L40 0 1 2 3 4 5 6 7 8 9 10 11 Element_01 Element_02 (byte 0) Element_02 (byte 1) Element_02 (byte 2) Element_02 (byte 3) Element_03 Element_04 (byte 0) Element_04 (byte 1) Element_01 Filling byte Filling byte Filling byte Element_02 (byte 0) Element_02 (byte 1) Element_02 (byte 2) Element_02 (byte 3) Element_03 Filling byte Element_04 (byte 0) Element_04 (byte 1) Element_01 Element_02 (byte 0) Element_02 (byte 1) Element_02 (byte 2) Element_02 (byte 3) Element_03 Element_04 (byte 0) Element_04 (byte 1) IndraLogic L10/L20 without pragma {pack} IndraLogic L10/L20 with pragma {pack}
Fig.4-42:
Memory assignment
49/84
Project Planning and Programming By specifying the pragma {pack} a structure archive compatible to the IndraLogic L40 is created. The individual structure elements can be accessed like in the IndraLogic L40.
Example to pack structures
Program:
VAR str001: struct001; len_struct001: INT := 0; array001: ARRAY [0..15] OF BYTE; ps001: POINTER TO BYTE; pa001: POINTER TO BYTE; i: INT := 0; END_VAR ---------------------------------------------------------len_struct001:=SIZEOF(str001); str001.s001_byte1:=16#01; str001.s001_DW:=16#05040302; str001.s001_byte2:=16#06; str001.s001_Word:=16#0807; ps001:=ADR (str001); pa001:=ADR (array001); FOR i :=0 TO len_struct001 BY 1 DO pa001^:=ps001^; pa001:=pa001+1; ps001:=ps001+1; END_FOR;
To pack structures with the help of the compiler instruction {pack} causes a deceleration of the PLC program processing in the Indra Logic L10/20, as the access to word or double-word operands occurs byte wise.
4.8.4
Fig.4-43:
During the declaration of variables without assignment of an I/O address the IndraLogic compiler ensures an optimum alignment corresponding to the illus trated table.
Example
Variable1: WORD even address Variable2: DWORD address divisible by 4 During the declaration of variables with assignment of an I/O address the align ment in the memory depends on the assigned address. Out01 AT %QB0 : DWORD; even address Out02 AT %QB5 : DWORD; uneven address
50/84
Project Planning and Programming To assign word/byte variables to uneven I/O addresses causes a deceleration of the PLC program processing in the IndraLogic L10/ L20, as the access to word and double-word operands occurs byte wise.
4.8.5
Due to the processor architecture used for the IndraLogic L10/L20, the 64 bit data type LREAL is not mapped task and interrupt save. The processor type used contains only tabs with a 32 bits width. Operations executed with LREAL variables can be stopped during task change or interrupt processing so that consistency errors occur. Use the LREAL variables in one IEC task only to exclude consis tency errors.
4.9
4.9.1
After finishing the programming the project can be verified in IndraLogic with menu function Project Rebuild all. With menu function Online Login the communication between programming system and the IndraLogic L10 is started, and a change to the online mode occurs. If the current project was not compiled after opening it or after the last modifi cation, it is compiled now (as for Project Build). If errors occur during the compilation, IndraLogic does not change to the online mode. If the current project was modified after the last download into the control, but not closed, and if the last download information was not deleted with command Project Clean all, a dialog with the following request is opened: "The program has been changed. Load changes? (Online Change)" "Yes" confirms that confirm during log in the changed project parts are to be loaded into the control. With "Load all" the complete project is reloaded into the control. With "No" a logging in occurs, but the changes made after the last download are not loaded into the control. Also refer to the "Online Functions" in the IndraLogic documentation or help /2/.
4.9.2
Online Functions
Then, information on the control state can be obtained using the "online func tions".
Connection Test
To switch a control online, a connection must have been established between the computer being provided with the IndraWorks installation and the control. This connection can be checked via the context menu of the device, refer to fig. 4-44 "Checking the connection of a device" on page 51.
51/84
Fig.4-44:
The result of the connection test is provided in the short acknowledgement. If the device can be reached, the control can be switched to online.
Switch online
To switch to online with the device go to menu Project Switch Devices On line, refer to fig. 4-45 "Switch device to online" on page 51.
Fig.4-45:
A dialog opens where the requested device can be selected, refer to fig. 4-46 "Select devices to switch online" on page 52.
52/84
Fig.4-46:
Single devices can also be switched online directly using the context menu of the device in the project explorer. Devices switched online are displayed in the project explorer via a small circle at the device icon: .
Switch on monitor function
As soon as a device is switched online, the monitor function of IndraWorks can be used. When the monitor is switched on, the I/O status data can be read in decimals. The monitor is to be switched on via the context menu of the device switched online, refer to fig. 4-47 "Switch monitor function on/off" on page 52.
Fig.4-47:
When the monitor is switched on, the I/O status data can be read in decimals. To view the addresses double-click on "Onboard I/O" in the project explorer. In the "Status" column, the corresponding values can be found fig. 4-48 "Output the I/O status data" on page 53.
53/84
Fig.4-48:
Setting time
The time can be set when the device is switched to online. Select the function "Set time" in the context menu. Also refer to the Online Functions in the IndraLogic documentation or help /2/.
55/84
Additional Functions
5
5.1
5.1.1
Additional Functions
Firmware Management
Firmware Update Control
Firmware downloads can be only executed, if the control is in the stop status. 1. 2. Copy the Firmware files of the IndraLogic L10 (*.fw files) required for download in a local directory or in a directory in the network. Open the dialog of the Firmware management. Use the Firmware man agement menu item in the context menu of the IndraLogic L10 device (in the project explorer). The following dialog opens:
Fig.5-1:
1 2 3 4
Path to the new Firmware versions Available Firmware versions Currently installed Firmware versions Activation option for a restart after the download
3. 4.
Select the directory selected in step 1 via the button figure 5-1.
, refer to in
Mark the requested Firmware on the left, refer to in figure 5-1. Only Firmware versions that are compatible to the current version of the device are displayed. The file names of the Firmware updates should not be changed. The new Firmware is only activated after a restart of the control. Tick "Restart after download" (refer to in figure 5-1) if the control should restart immediately after installing the new Firmware. Click on the Download button. Follow the further screen instructions.
5.
6.
Risk to damage the device due to voltage breakdown during Firmware change! CAUTION
Ensure that the supply voltage of all participating devices is never interrupted during the Firmware change!
56/84
Additional Functions For further information refer to the documentation and the online help of IndraWorks /5/.
5.2
Fig.5-2:
For further information refer to the documentation and the online help of IndraWorks /5/.
5.3
IndraLogic Functions
The context menu functionality of the "Logic" object in the project explorer is dependent of the current system status:
Fig.5-3:
57/84
Additional Functions
Fig.5-4:
Context menu of the "Logic" object when the IndraLogic is not started
Available functions: Printing, saving and compiling (Compile all) an IndraLogic project Starting and closing IndraLogic Logging the control in or out Updating all modules created in IndraLogic as well as modifications of configuration settings in the IndraWorks project explorer. The access on the context menu items Save PRO file as... and Properties is only possible, if IndraLogic is closed.
further settings
Further functions and settings of IndraLogic are summarized under the "Further settings" tab: Saving IndraLogic settings Safety mode Offline mode Symbol file generating and sending Substitute constants Address verification Optimized IndraLogic call Automatic loading of the boot project
The properties can be called up via the context menu of the "Logic" object, if IndraLogic is not started.
58/84
Additional Functions
Fig.5-5:
For further information refer to the documentation and the online help of IndraWorks /5/.
59/84
Libraries
6
6.1
Library
Libraries
Overview
Libraries available for the IndraLogic L10:
Function Analysis of expressions See /2/
AnalyzationNew BuepE_Client HMI_Mkeys Iecsfc NetVarUdp_LIB_V23 ProViDiagnosis RIH_CML10 RIL_Check RIL_CheckRtv RIL_CommonTypes RIL_EthernetIP RIL_VExUtil Default SysLibCom SysLibFile SysLibFileAsync SysLibIecTasks SysLibMem SysLibRtc SysLibSockets SysLibSocketsAsync SysLibStr
Communication between the IndraLogic L10 and the Bosch controls See chapter 6.2 "BuepE_Client of the CL series " on page 60 M key functionalities of the HMI (IndraWorks HMI) For internal use Application of network variables and the parameter manager (for data exchange between two or several controls) Access to the PLC diagnostics (ProVi) Modules for the status of the IndraLogic L10 Automatic monitoring of internal over-ranges Like RIL_Check For internal use Functions in connection with Ethernet/IP Safe key transmission to an HMI device Default FBs and functions of the IEC 61131-3 Serial communication with the IndraLogic L10 File system support on the IndraLogic L10 Asynchronous file accesses from the IEC application Management of IEC tasks Memory management Access to the real-time clock and the battery status of the IndraLogic L10 Access to sockets for the communication via TCP/IP and UDP /5/ Networkfunctionality.pdf1) /5/ See chapter 6.3 "RIH_CML10 " on page 62 See chapter 6.4 "RIL_Check " on page 63 See chapter 6.4 "RIL_Check " on page 63 See chapter 6.5 "RIL_Ether NetIP" on page 65 See chapter 6.6 "RIL_VExUtil" on page 71 /2/ SysLibCom.pdf1 SysLibFile.pdf1 SysLibFileAsync.pdf1 SysLibIecTasks.pdf1 SysLibMem.pdf1 SysLibRtc.pdf1 SysLibSockets.pdf1
SysLibStr.pdf1
1)
Documentation about the system libraries (SysLibXXX.pdf) are located in a subdirectory of the IndraLogic installation, e.g.: ".../Rexroth/IndraWorks/IndraLogic/ Documents/English"
60/84
Libraries
Library SysLibTime Util Function Retrieve time and date See SysLibTime.pdf1
As supplement to the Default.lib: BCD converting, bit/byte functions, /2/ mathematic help functions, controllers, signal generators, function manipulators and analog value processing
Fig.6-1:
To link libraries with the current project, please consider PLC Programming with IndraLogic the chapter 4.7.4 "Library Manager " on page 43 in chapter. IndraWorks loads libraries for internal use automatically as soon as they are referenced. It is not necessary to insert them manually with the library manager. Concerning the system and Firmware libraries please also consider the online help of IndraLogic.
6.2
6.2.1
BuepE_Client
General Information
The library BuepE_Client provides the communication between the IndraLogic L10 and the Bosch controls of the CL series. The IndraLogic L10 maps the client functionality. The CL control represents always the server.
6.2.2
BuepE_Client
The BuepE_Client function block can be simultaneously used several times. A new instance is required for every order.
Fig.6-2:
Name VAR_INPUT Start Write Type BOOL BOOL
BuepE_Client
Comment TRUE: The transmission is started TRUE: Writing access FALSE: Reading access
61/84
Libraries
Name Command Type BYTE Comment Field type of the Bosch control: 16#44: Data block 16#43: Data field 16#4D: Flag Index Offset DataType WORD WORD BYTE Number of the data block (only for the "Data block" field type) Byte offset address within the selected data field or data block Data type: 0: BYTE 1: WORD DataCnt Coord BlockAdr DataPtr IPAdr VAR_OUTPUT State WORD WORD WORD POINTER TO BYTE DWORD WORD Number of the data = f(DataType), depending on the setting in DataType Coordination flag 0: Uncoordinated Module block address, only for CL200, CL400 and CL500 16#FFFF: without block address Pointer to the source data (for "Write"=TRUE) or pointer to the target data (for "Write"=FALSE) IP address of the Bosch CL control Status: 0: Without errors 16#0100: Order in process 16#0305: Order faulty 16#0405: Order not started Further states about the communication functionality of the particular control are described in the documentation . Error WORD Error: 0: Without errors 16#FF04: No order in process 16#FF20: No UDP socket free (e.g. too many active instan ces at the same time) 16#FF21: Error during "bind" (e.g. too many active instances at the same time) 16#FF22: Error during "sendto" (e.g. wrong IP address or partner not activated) 16#FF23: Error during "UDP-receive" 16#FF24: Errors in UDP-receive length 16#FF25: To many repetitions (partner does not respond, e.g. wrong IP address). Further states are described in the documentation of the communication functionality of the re spective control.
Fig.6-3:
Interface of BuepE_Client
62/84
Libraries The following program extract shows an example of the BuepE_Client call.
Program:
VAR Bclient : BuepE_Client; (* Declare instance *) MyDB : ARRAY [0..511] OF BYTE; (* Data block data array*) END_VAR (* example: Read a DB from a CL500-ZS1 *) Bclient( Start := TRUE, (* Start transmission *) Write := FALSE, (* Reading access) Command := 16#44, (* Data block *) Index := 0, (* DB number *) Offset := 0, (* No address offset *) DataType := 0, (* Byte *) DataCnt := 512, (* 512 bytes *) Coord := 0, (* Uncoordinated *) BlockAdr := 16#0008, (* ZS 1 *) DataPtr := ADR(MyDB),(* Pointer to data block-data array *) IPAdr := SysSockInetAddr('10.110.244.46'), (* state=> ,*) (* error=>*) );
6.3
6.3.1
RIH_CML10
Overview
IH_GetOhcCtrl: Reading operating hours meter of the control Outputting IH_SetDisplay user indications on the display
6.3.2
IH_GetOhcCtrl
Supplies the operating time of the control in hours. It is not possible to reset the operating hours meter.
Fig.6-4:
Name VAR_INPUT VAR_OUTPUT Enable Done Error ErrorID Type BOOL BOOL BOOL
IH_GetOhcCtrl
Comment TRUE: FB is processed FALSE: FB is not executed TRUE: OperatingHours relevant FALSE: OperatingHours in process Always 0 Undefined and cannot be evaluated
ERROR_CODE
63/84
Libraries
Name ErrorIdent OperatingHours Type ERROR_STRUCT DWORD Comment Undefined and cannot be evaluated Operating time of the control in hours
Fig.6-5:
Interface of IH_GetOhcCtrl
6.3.3
IH_SetDisplay
Indicates a user message on the IndraControl Service Tool.
Fig.6-6:
Name VAR_INPUT Execute Message VAR_OUTPUT Done Error ErrorID ErrorIdent Type BOOL STRING[80] BOOL BOOL
IH_SetDisplay
Comment With a positive edge the output of the string transmitted at input Message is started. String to be output with up to 80 characters. Empty string: Delete the active display. TRUE: String is output FALSE: Processing not yet finished Always 0 Undefined and cannot be evaluated Undefined and cannot be evaluated
ERROR_CODE ERROR_STRUCT
Fig.6-7:
Interface of IH_SetDisplay
To read the message, switch to the "Diagnostics" view, refer to chapter 7.3.6 " Diagnostics " on page 77.
6.4
RIL_Check
Faulty accesses (accidentally) programmed outside of the ranges of arrays and subrange types of variables, as well as the division by zero, are not compen sated by the IndraLogic compiler and/or the runtime system and cause partly unpredictable errors during program processing. When implementing the RIL_Check.libm, such over-ranges are monitored and prevented. Thereby, the access for arrays and subrange types are limited to the smallest or highest possible value. Thus, e. g. concerning an array, the element with the highest indices is accessed, even if a higher index value was specified in the PLC pro gram. For a division by zero the divisor is replaced by "1". If the RIL_Check.lib library is integrated in the PLC project, before each testable operation the corresponding test function is automat ically inserted (invisible for the user). Further function calls are not necessary!
64/84
Libraries If library RIL_Check.lib is integrated in the PLC project, the PLC cycle time is charged, as each testable operation is automatically monitored. With respect to the robustness of a PLC project and the safety of the whole system we recommend to use the RIL_Check.lib in the PLC project. When using the MP_PLCOpen.lib, the RIL_Check.lib is required. In this case the RIL_Check.lib must be integrated in the PLC project.
Functions
All functions contained in the RIL_Check library (see fig. 6-8 "Functions of RIL_Check" on page 64) are automatically integrated in the PLC program and must not be explicitly called.
Description Automatic verification, if the permissible indices of the access to array elements is exceeded or fallen below the minimum value. Automatic verification on division by zero (BYTE access). Automatic verification on division by zero (DWORD access). Automatic verification on division by zero (REAL access). Automatic verification on division by zero (WORD access). Automatic verification, if the permissible value range of a signed variable is exceeded or fallen below the minimum value. Automatic verification, if the permissible value range of an unsigned variable is ex ceeded or fallen below the minimum value.
Fig.6-8:
CheckExceedingOccurred
Functions of RIL_Check
The error cause can be determined exactly by requesting the bits in the global variable "CheckExceedingOccurred" directly. All error accesses are prevented by RIL_Check, so that the permissible value range is not exceeded or fallen below the minimum value and that no division by zero occurs. The single bits have the following meaning:
Value 16#01 Meaning CheckBoundsLowerLimitation: The permissible indices of the access to array elements are fallen below the minimum value.
CheckExceedingOccurred.1 CheckExceedingOccurred.2
16#02 16#04
CheckBoundsUpperLimitation: The permissible indices of the access to array elements are exceeded. CheckBoundsExceedingLimitation: The permissible indices of the access to array elements are exceeded or fallen below the minimum value.
CheckExceedingOccurred.3
16#08
CheckRangeLowerLimitation: The permissible value range of a variable is fallen below the minimum value.
CheckExceedingOccurred.4
16#16
65/84
Libraries
Bit variable CheckExceedingOccurred.5 Value 16#32 Meaning CheckRangeExceedingLimitation: The permissible value range of a variable is exceeded or fallen below the minimum value. CheckExceedingOccurred.6 16#64 DivisionByZeroPrevention: Division by zero.
Fig.6-9:
Sample Program
CheckExceedingOccurred
The following PLC sample program shows the use of variable CheckExcee dingOccurred. The limitation of arrays with CheckBounds always sets the respective bit in error case, when the permissible value range is exceeded or fallen below the minimum value (CheckBoundsLowerLimitation or Check BoundsUpperLimitation) and the general bit of the access violation (Check BoundsExceedingLimitation). Thus, a general or detailed verification, if a limit value was exceeded, can be realized.
Program:
CheckExceedingOccurred := 16#00; (* Resetting the variables *) IF Axis_Data[AxisNo].bCheckAccessOK (* Array access *) THEN ... IF CheckExceedingOccurred.2 (* Array access violation detected? *) THEN IF CheckExceedingOccurred.0 (* Bit set, if value below specified range? *) THEN String := 'Access below the possible array range' ... END_IF IF CheckExceedingOccurred.0 (* Bit set, if value above specified range? *) THEN String := 'Access above the possible array range' ... END_IF ELSE String := 'Access successful' END_IF
6.5
6.5.1
RIL_EtherNetIP
Overview
A control configured as CIP data client is able to read and if write access is allowed to describe variables of a CIP data server.
FB FB FB
Read variables provided by the CIP data server Write on variables provided by the CIP data server For diagnostics of the cyclic communication
Fig.6-10:
6.5.2
IL_ReadDataTable
Brief Description Interface Description
66/84
Libraries
Fig.6-11:
Name VAR_INPUT bExecute StrPath StrRemoteTag UdiMaxReadSize PbyReadData UiElements Type
Structure of IL_ReadDataTable
Comment Positive edge starts the service. IP address of the CIP data server (e.g. "192.168.73.105") STRING(80) UDINT POINTER TO BYTE UINT Name of the variable to be read (e.g. "Test1"). Size of the receiver array "PbyReadData". Pointer to the array, in which the data are to be written. The array has to be provided by the user of the FB. Number of array elements to be read. For atomic data types (SINT, DINT...) UiElements has to be set to value 1. Specifies the maximum time in ms that the CIP data server may need to respond. Number of received data bytes. TRUE: The service is stopped or an error occurred. TRUE: An error occurred. See error messages.
BOOL STRING(80)
Fig.6-12:
Example
Read the DINT variable "diCounter" from the CIP data server with the IP ad dress "192.168.73.105". As "diCounter" is used in the PLC program "PLC_PRG", the user has to enter "PLC_PRG.diCounter" as name of the var iable to be read. The reading process can be started by a positive edge change of variable "Read2Fb_bExecute" (FALSE -> TRUE). Status TRUE of variable "bDone" confirms the execution of the service.
Program:
PROGRAM PLC_PRG VAR (************************************************* ** Variables for IL_ReadDataTable **************************************************) Read2In1: IL_ReadDataTable; Read2Fb_bExecute: BOOL; Read2Fb_strPath: STRING; Read2Fb_strRemoteTag: STRING; Read2Fb_udiMaxReadSize: UDINT;
67/84
Libraries
Read2Fb_diReadData: Read2Fb_uiElements: Read2Fb_udiTimeout: Read2Fb_udiReadSize: Read2Fb_bDone: Read2Fb_bError: Read2Fb_enErrorID: Read2Fb_stErrorIdent: Read2Fb_udiCtrErr: Read2Fb_udiCtrGood: Read2Fb_CtrValidInput: (*for automation test*) Read2Fb_bAutoTest: DINT; UINT; UDINT; UDINT; BOOL := FALSE; BOOL; ERROR_CODE; ERROR_STRUCT; UDINT := 0; UDINT := 0; UDINT := 0; BOOL := FALSE;
Program:
(****************************************************************** ** Explicit message: Read data table - 2 DINT *******************************************************************) Read2Fb_strPath := '192.168.73.105'; (*IP-Address of the Data table server*) Read2Fb_strRemoteTag := 'PLC_PRG.diCounter'; (*Name of the variables to be read*) Read2Fb_uiElements := 1; (*Number of the elements to be read*) Read2Fb_udiTimeout := 100; (*Timeout in ms*) Read2In1( bExecute := Read2Fb_bExecute, strPath := Read2Fb_strPath, strRemoteTag := Read2Fb_strRemoteTag, udiMaxReadSize := SIZEOF(Read2Fb_diReadData), pbyReadData := ADR(Read2Fb_diReadData), uiElements := Read2Fb_uiElements, udiTimeout := Read2Fb_udiTimeout, udiReadSize => Read2Fb_udiReadSize, bDone => Read2Fb_bDone, bError => Read2Fb_bError, enErrorID => Read2Fb_enErrorID, stErrorIdent => Read2Fb_stErrorIdent); (*Automation test*) IF Read2Fb_bAutoTest = TRUE THEN IF Read2Fb_bDone = TRUE THEN IF Read2Fb_bError = TRUE THEN Read2Fb_udiCtrErr := Read2Fb_udiCtrErr + 1; ELSE Read2Fb_udiCtrGood := Read2Fb_udiCtrGood + 1; END_IF Read2Fb_bExecute := FALSE; ELSE Read2Fb_bExecute := TRUE; END_IF END_IF
6.5.3
IL_WriteDataTable
Brief Description
Writes values in variables provided by a CIP data server. Write access at the CIP data server has to be allowed for the rele vant variables.
Interface Description
68/84
Libraries
Fig.6-13:
Name VAR_INPUT bExecute StrPath StrRemoteTag EnCipType PbyWriteData Type
Structure of IL_WriteDataTable
Comment Positive edge starts the service. IP address of the CIP data server (e.g. "192.168.73.105") STRING(80) CIP_TYPE POINTER TO BYTE UINT Name of the variable to be written (e.g. "Test1"). Type of the written data. Is verified by some CIP data server. Pointer to the array that contains the data to be written on the CIP data client. The array has to be provided by the user of the FB. Number of array elements to be written. For atomic data types (SINT, DINT...) UiElements has to be set to value 1. Specifies the maximum time in ms that the CIP data server may need to respond. TRUE: The service is stopped or an error occurred. TRUE: An error occurred. See error messages.
BOOL STRING(80)
UiElements
Fig.6-14:
Example
Write the SINT variable "siWriteData" on a CIP data server with the IP address "192.168.73.105". As "siWriteData" is used in the PLC program "PLC_PRG", "PLC_PRG.siWriteData" is to be entered as name of the variable to be written. The writing process can be started by a positive edge change of variable "WriteFb_bExecute" (FALSE -> TRUE). Status TRUE of variable "bDone" con firms the execution of the service.
Program:
(************************************************* ** Variables for writing data SINT **************************************************) WriteIn1: IL_WriteDataTable; WriteFb_bExecute: BOOL; WriteFb_strPath: STRING; WriteFb_strRemoteTag: STRING; WriteFb_enCipType: CIP_TYPE; WriteFb_uiElements: UINT; WriteFb_siWriteData: SINT;
69/84
Libraries
WriteFb_udiTimeout: WriteFb_bDone: WriteFb_bError: WriteFb_stErrorIdent: WriteFb_udiCtrErr: WriteFb_udiCtrGood: WriteFb_udiCtrValidInput: (*for automation test*) WriteFb_bAutoTest: UDINT; BOOL := FALSE; BOOL; WriteFb_enErrorID: ERROR_STRUCT; (*Diagnostics*) UDINT := 0; UDINT := 0; UDINT := 0; BOOL := FALSE;
ERROR_CODE;
Program:
(****************************************************************** ** Explicit message: Write data table - 1 SINT *******************************************************************) WriteFb_strPath := '192.168.73.105'; WriteFb_strRemoteTag := 'PLC_PRG.siWriteData'; WriteFb_uiElements := 1; WriteFb_enCipType := CIPTYPE_SINT; WriteFb_udiTimeout := 1000; (*ms*) WriteIn1( bExecute := WriteFb_bExecute, (*FALSE after TRUE starts FB*) strPath := WriteFb_strPath, (*IP address of the server*) strRemoteTag := WriteFb_strRemoteTag, (*Name of the variable to be written*) enCipType := WriteFb_enCipType, (*Data type of the variables*) uiElements := WriteFb_uiElements, (*Number of the elements to be written.*) (* For atomic data types *) (* (SINT, DINT...)always 1.*) pbyWriteData := ADR(WriteFb_siWriteData), (*Pointer to the data, you want to write*) udiTimeout := WriteFb_udiTimeout, (*Timeout der Expicit Message*) bDone => WriteFb_bDone, (*TRUE => FB is ready with order.*) bError => WriteFb_bError, (*TRUE => Error*) enErrorID => WriteFb_enErrorID, stErrorIdent => WriteFb_stErrorIdent); (*Automatic test*) IF WriteFb_bAutoTest = TRUE THEN IF WriteFb_bDone = TRUE THEN IF WriteFb_bError = TRUE THEN WriteFb_udiCtrErr := WriteFb_udiCtrErr + 1; ELSE WriteFb_udiCtrGood := WriteFb_udiCtrGood + 1; WriteFb_siWriteData := WriteFb_siWriteData + 1; END_IF WriteFb_bExecute := FALSE; ELSE WriteFb_bExecute := TRUE; END_IF END_IF
6.5.4
Error ID 2 2 2 2
Fig.6-15:
70/84
Libraries
6.5.5
IL_Status
The FB IL_Status is used for the diagnostics of the cyclic communication ("Implicit Messaging"), also refer to chapter 4.6.1 "Configuring IndraLogic L10 as Ethernet/IP Slave " on page 32.
General Information
Fig.6-16:
Name VAR_INPUT bEnable Type
IL_Status
Comment If the status is positive (TRUE), the status of the cyclic Ethernet/IP communication is requested with each call of the FB. TRUE: An error occurred. See error messages.
BOOL
VAR_OUTPUT
Fig.6-17:
Interface of IL_WriteDataTable
Example
The following example shows how to use FB IL_Status. Program:
(************************************************* ** Variables for IL_Status **************************************************) PROGRAM PLC_PRG VAR Diag: IL_Status; CtrValidInput: DINT ... END_VAR; ... ... ... (************************************************* ** Program **************************************************) Diag(bEnable:=TRUE); IF(Diag.bError = TRUE) THEN (*Insert error treatment here.*) ... Diag (bEnable:=FALSE ); (*Reset error (bEnable)*) ELSE (*valid data: Insert input and output data processing here *) CtrValidInput := CtrValidInput +1; END_IF ...
71/84
Libraries
6.5.6
Error ID
ETHERNET_IP(151)
0x10000002
0x00000000
Idle
ETHERNET_IP(151)
0x10000003
0x00000000
Timeout
ETHERNET_IP(151)
0x10000004
0x00000000
Closed
Fig.6-18:
6.6
6.6.1
RIL_VExUtil
IL_VExKeys
Brief Description
With the function block the user can transmit the keystrokes on an HMI device safely to the control. The connection occurs via UDP. Each time when the function block is called, the last data is copied. If the connection is interrupted, all outputs are reset to 0. Thus, the user is able to program safe properties, whereby in the output data of the function block the safety mode is assigned to 0.
Interface Description
Fig.6-19:
Name VAR_IN_OUT Data IPAddress VAR_INPUT VAR_OUTPUT Enable Type
ARRAY [0..7] OF BYTE Contains data as byte array. The meaning of the particular bit is described in the documentation of the HMI. STRING(25) BOOL Entered IP address "." notation, e.g. "10.104.73.193" As long as the input is TRUE, the data is permanently updated. If it is inactive, the output data are all 0. If TRUE, the output data are valid and are updated.
InOperation BOOL
72/84
Libraries
Name Error ErrorID ErrorIdent Type BOOL ERROR_CODE ERROR_STRUCT Comment Indicates that an error has occurred within the function block. The output data are all set to 0. Error recognition (see next table "Error codes"). Error structure with further division of the errors.
Fig.6-20:
Error Codes ErrorID INPUT_INVALID_ERROR (16#0001) COMMUNICATION_ERROR (16#0002) DEVICE_ERROR (16#0008) STATE_MACHINE_ERROR (16#0005)
The function block generates in Additional1/Additional2 "MLC_ETHERNET" the following error messages:
Additional1 10 11 12 1 Additional2 0 0 0 0 Description Wrong IP syntax Unknown IP address or no connection Invalid internal buffer size Invalid status of the state machine
for
table
Fig.6-21:
73/84
7
7.1
7.2
Fig.7-1:
Actuation of the reset button will abort processing of a running pro gram.
Reset button
The reset button can only be pressed using a tool, for instance with the tip of a pencil. Three different actions can be activated using the Reset button: 1. Short actuation of the reset button during the operation resets the com plete assembly and forces a restart the without a switch off of the supply voltages. Long actuation of the reset button during the operation resets the complete assembly and forces a restart without a switch off of the supply voltages. Additionally, the IP address is reset to the delivery status (192.168.1.10). Therefore, the reset button is to be pressed till the booting phase ends.
2.
74/84
Display and Operating Components The period of the booting phase is indicated with an orange status light emitting diode. 3.
Status LED
If the reset button is pressed during the switch-on voltage of the power supply, the existing boot project is deleted.
The light-emitting diode is a diagnostic / status indicator. The meanings on the LED display can be seen below.
LED display LED OFF LED red flashing (15 Hz) LED orange LED green flashing (15 Hz) LED green LED green flashing Meaning Control is in status "STOP" Watchdog error Booting phase No boot project exists Control is in status "RUN" Outputs are disabled
Fig.7-2:
7.3
7.3.1
Depending on the rights (refer to user management), not all pages are dis played to every user. The writing rights of individual pages ( "Network config uration" or "Diagnostics" for example) are restricted for some users.
7.3.2
Browser Settings
In order to display the IndraControl Service Tools correctly and to ensure that all functions are available, some security setting changes are required. As ex ample, the following list shows the required settings (security settings for the web content zone) for the Internet Explorer 6:
Function Execute ActiveX control elements secure for the scripting Setting Activate
Initialize and execute ActiveX control elements that are not Prompt secure Execute ActiveX control elements and plug-in Automatic prompt for ActiveX control elements Binary behavior and script behavior Activate Activate Activate
75/84
Fig.7-3:
This function uses popups.Therefore, they may not be blocked for the IP ad dress of the control.
7.3.3
Login
Fig.7-4:
Login
The user name and a password are to be entered on the first page. The fol lowing user names and passwords are already assigned when delivered from the supplier:
User Administrator Service User Password Rexroth Service User
Fig.7-5:
Language of the application Save login information
The language of the application can be set via the selection field "Language selection". German and English are currently available. With the option "Save login information" the login data is saved locally as "cookie".
76/84
7.3.4
Network Configuration
Fig.7-6:
The page "Network configuration " displays the following network parameters: MAC address IP address Subnet mask Default gateway
Apart from the MAC address, all values can be edited if the rights are given to the current user. To change these parameters, set the curser in the requested field using the mouse. The highlighted presentation shows the modified values. The modified values are applied after closing the network configuration and after a question for confirmation. To activate the modified values for the control, restart the control.
7.3.5
Hardware Overview
Fig.7-7:
The page "Hardware overview" provides the following information: Part short text of the hardware Change index Serial number Firmware version Board support package Technology function Type and status, hardware, part number, serial number and index of the function modules
77/84
Display and Operating Components Temperature specifications (current and maximum temperature, fan sta tus and temperature warning) Operating hours meter of the control as well as of the fan
7.3.6
Diagnostics
Fig.7-8:
The page "Diagnostics" provides information on the PLC project as well as several PLC operating functions. The following information is shown. The user or the creator as well as the project name of the project currently loaded in the IndraControl. Inline status Profibus status Status of the equipped function modules Status of the PLC Display of the PLC user string
The following PLC operating functions are available if the rights were given to the current user: Starting and stopping the PLC Blocking and unblocking of outputs Deleting the boot project Restarting the PLC
7.3.7
Variable Editor
Fig.7-9:
The variable editor provides the possibility to edit single PLC variables. The icon name of the variable is entered in the field "Variable" and confirmed using "Enter". If the input of the variable name is correct, the field "value" shows the
78/84
Display and Operating Components current value. This value can be modified and transferred to the control using "Enter". The new value is immediately applied by the control.
7.3.8
User Management
Fig.7-10:
The page "User Management" provides the opportunity to assign certain rights for the pages listed. Select the user on the left of the Explorer. Assign the rights "View" and "Change" on the right. Save the setting using the "Save" button. Changing the passwords of single users and deleting existing users are part of the basic functions.
7.4
Program:
[ethernet] ip_adress subnet_mask gateway 192.168.1.10 255.255.0.0 0.0.0.0
The network settings can also be reset to the default values using the Reset button, refer to chapter 7.2 "Reset Button and Status LED" on page 73.
79/84
Technical Data
8
8.1
Technical Data
Equipment
IndraLogic L10-04VRS Processor Random access memory (RAM) Interfaces: Interface to I/O modules Communication interfaces Inputs and outputs Rexroth Inline interface 1 x Ethernet connection (RJ 45, 10/100 Base-T) 8 electrically isolated digital inputs 4 electrically isolated digital outputs STMicroelectronics ST40 with 192 MHz Minimum of 32 Mbyte DRAM and Minimum of 32 kByte NvRAM
Fig.8-1:
Equipment
8.2
Power Data
IndraLogic L10-04VRS User memory for program code User memory for data Remanent memory Task number Processing time, typical (1000 instructions in AWL, bit and word commands mixed) 1 Mbyte 2 Mbyte 32 kbytes 8 150 s
Fig.8-2:
Power data
81/84
9
9.1
9.2
Service Hotline
Out of helpdesk ours please contact our German service department directly: +49 (0) 171 333 88 26 or +49 (0) 172 660 04 06 Hotline numbers for other countries can be found in the addresses of each region on the Internet (see below).
9.3
Internet
Additional notes regarding service, maintenance and training, as well as the current addresses of our sales and service offices can be found on http://www.boschrexroth.com Outside Germany please contact our sales/service office in your area first.
9.4
Helpful Information
For quick and efficient help please have the following information ready: detailed description of the fault and the circumstances Information on the name plate of the affected products, especially type codes and serial numbers Your phone and fax numbers and E-mail address, so we can contact you in case of questions.
83/84
Index
Index
A
Address verification 57 Alignment for I/O addresses 49 Appropriate use 3 Case of application 3 Inserting EthernetIP slave object 22
Basic settings specified (wizard-guided) 16 Boot project 57 Bosch controls of the CL series 60 BuepE_Client 60
Libraries 59 Library Manager 43 Loading Configurations and PLC Program 50 Login 50, 75
M N
CheckExceedingOccurred 64 CL control 60 Communication settings 18 Compatible IEC programming 46 Compiler instruction 48 Creating a PLC program 45 Creating new IndraLogic L10 device 15
PLC programming 39 Power data 79 Pragma pack 48 Project Planning and Programming 15
G H I
Gateway server 18 Hardware overview 76 IH_GetOhcCtrl 62 IH_SetDisplay 63 IL_VExKeys 71 Importing IndraLogic project data 56 Inappropriate use 4 Inappropriate Use Consequences, exclusion of liability 3 IndraControl L10 1 IndraLogic 1 IndraLogic functions 56 IndraLogic settings 57 IndraWorks 1 IndraWorks HMI 1 Inline modules 29
Safety instructions for electric drives 5 Safety mode 57 Saving project data 46 Service Tool 74 State-of-the-art 3 Status LED 73 Structures to I/O addresses 50 Substitute constants 57 Symbol file 57 System overview 1
Target Manager 1 Target settings 40 Target Support Package 1 Target system files 1 Task configuration 42 Technical data 79 TSP 1 Type of addressing 18
84/84
Index
Use Appropriate use 3 Inappropriate use 4 User management 78 Using of pointers within structures 47
Variable editor 77
Web-based IndraControl Service Tool 74 Diagnostics 77 Hardware overview 76 Login 75 Network configuration 76 User management 78 Variable editor 77 WinStudio 1
Notes
Bosch Rexroth AG Electric Drives and Controls P.O. Box 13 57 97803 Lohr, Germany Bgm.-Dr.-Nebel-Str. 2 97816 Lohr, Germany Phone +49 (0)93 52-40-50 60 Fax +49 (0)93 52-40-49 41 [email protected] www.boschrexroth.com
R911322944