SILworX®

First Steps Manual

The effi cient programming tool for HIMax and HIMatrix systems

All HIMA products mentioned in this manual are protected by the HIMA trademark. Unless noted otherwise, this also applies to other manufacturers and their respective products referred to herein. All of the instructions and technical specifications in this manual have been written with great care and effective quality assurance measures have been implemented to ensure their validity. For questions, please contact HIMA directly. HIMA appreciates any suggestion on which information should be included in the manual. Equipment subject to change without notice. HIMA also reserves the right to modify the written material without prior notice. For further information, refer to the CD-ROM and our web site http://www.hima.de and http://www.hima.com © Copyright 2008, HIMA Paul Hildebrandt GmbH + Co KG All rights reserved Contact HIMA Paul Hildebrandt GmbH + Co KG P.O. Box 12 61 68777 Brühl, Germany Tel: +49 (6202) 709 0 Fax: +49 (6202) 709 107 E-mail: info@hima.com HI 801 103 Rev.3.0

I

Contents

1 BRIEF OVERVIEW ............................................................1 1.1 Scope of delivery ..........................................................................1 1.2 Information about this manual ......................................................1 1.3 Additional Manuals .......................................................................2 1.4 Support .........................................................................................2

2 INSTALLATION .................................................................5 2.1 System requirements....................................................................5 2.2 How to start the installation...........................................................5 2.3 De-installation ...............................................................................5 2.4 License Management ...................................................................6

3 IMPORTANT PHRASES AND SYMBOLS ......................11

4 INTRODUCTION TO THE HANDLING OF SILWORX ....13 4.1 Screen layout and operation.......................................................14

4.1.1 Simple operation principle ................................................................. 15 4.1.2 Structure Tree ................................................................................... 17 4.1.3 Action bar .......................................................................................... 18 4.1.4 Work Area ......................................................................................... 20 4.1.5 Symbol Bar / Menu Bar ..................................................................... 23 4.1.6 Log book............................................................................................ 24

4.2 Table handling ............................................................................25 4.3 Variables .....................................................................................28

4.3.1 Global Variables ................................................................................ 28 4.3.2 Local Variables.................................................................................. 29

II

5 CREATION OF NEW PROJECT......................................31 5.1 Creation of a project structure.................................................... 31 5.2 Properties of the Resource ........................................................ 33 5.3 Properties of the Program.......................................................... 35 5.4 Definition of Global Variables..................................................... 37 5.5 Hardware.................................................................................... 42

5.5.1 Resource type / Racks / Modules ......................................................42 5.5.2 Assign redundant IO Modules ...........................................................48 5.5.3 Module settings .................................................................................50 5.5.4 Assignment of Variables to Hardware ...............................................52

5.6 Create Logic (Program) ............................................................. 55 5.7 Code Generation........................................................................ 60 5.8 Offline Simulation....................................................................... 62

6 START-UP OF A HIMAX SYSTEMS ...............................67 6.1 Basic knowledge ........................................................................ 67

6.1.1 SRS – System Rack Slot ...................................................................68 6.1.2 „Responsible Attribute“ for a SB module............................................68 6.1.3 MAC Address ....................................................................................68 6.1.4 IP Address .........................................................................................69 6.1.5 Set IP-Address for the Network-Adapter of your PC.......................... 71 6.1.6 Mode Switch on the CPU...................................................................73 6.1.7 INIT/STOP/RUN - LEDs on the CPU.................................................74

6.2 Start-Up procedure for basic rack (rack 0)................................. 75 6.2.1 Start-Up procedure for a SB module .................................................77 6.2.2 Start-Up procedure for a CPU ...........................................................81

6.3 Start-Up extension rack ............................................................. 88 6.4 Loading Resource (PES) and start running ............................... 93 6.5 Set Date/Time ............................................................................ 98

III

7 WORKING WITH EXISTING PROJECT (ONLINE) .........99 7.1 Open existing project ..................................................................99 7.2 Start connection to PES, Start Control-Panel...........................101

7.2.1 Online Login .................................................................................... 101 7.2.2 Control Panel (CP) .......................................................................... 102

7.3 Program Online (watch status of logic).....................................104 7.3.1 Navigation in the logic ..................................................................... 106

7.4 Global variable Cross-Reference list ........................................108 7.5 Forcing ......................................................................................109

7.5.1 Force releases and deactivation...................................................... 110 7.5.2 Force-Editor..................................................................................... 112 7.5.3 Forcing of Variables ........................................................................ 113 7.5.4 Start/Stop Forcing ........................................................................... 116

7.6 Diagnostics ...............................................................................118 7.6.1 System Diagnostic - Control Panel.................................................. 118 7.6.2 Hardware Diagnostic ....................................................................... 118 7.6.3 Monitor values and status of modules ............................................. 121 7.6.4 Longterm/Shortterm diagnosic buffer .............................................. 122

7.7 Reload.......................................................................................124

8 SAVE PROJECT............................................................127

9 INDEX.............................................................................129

IV

1

1 Brief overview 1.1 Scope of delivery The SILworX scope of delivery includes: • This manual

The manual “First Steps” enables you to obtain a speedy and simple introduction to the operation of SILworX. For this purpose, in addition to an overview of the functions, it provides step-by-step instructions to create a project, start-up of a HIMax system and will introduce the major Online functions.

• CD-ROM Besides the SILworX software, the CD-ROM also contains some examples and tools and the documentation for the current HIMax systems.

• Software protection, either a Hardlock (Dongle) or a licence number (Softlicence)

1.2 Information about this manual The user will find all necessary knowledge within this manual to learn either during a training secession or for himself about the major functions of SILworX. This Manual and all screenshots refer to SILworX version V 3.X Chapter 2 explains the Installation and Deinstallation of SILworX. Chapter 4 describes in general terms how to use and operate SILworX. Users without any prior knowledge should read through these chapters very carefully. Chapter 5 shows to a programmer how to create a complete project Chapter 6 shows the Start-up procedure of a newly installed HIMax Chapter 7 shows all Online functionalities and is designed for operators and maintenance, mainly working online (Online-test, Forcing, Diagnostic …)

2

1.3 Additional Manuals This manual is showing a guideline for the first steps that will be done with SILworX and also giving first and general instructions in handling of system. It can not be all possible information within this small manual so for further and additional information the user is kindly requested to have a look for the following manual. Especially for real and safety related applications it is necessary to read closely through the relevant manuals. Safety purposes HIMax Safety Manual System purposes HIMax System Manual Communication HIMax Communication Manual Data Sheets for modules and components

1.4 Support You have a choice of various possibilities if you have any questions on operation or reporting program errors, or if you wish to make suggestions about improvements.

News, Manuals Data Sheets

Our Web page www.hima.com

Consulting Per email: himax.support@hima.com Phone: +49-(0)6202-709 259 Fax: +49-(0)6202-709 199

Between 8:30 and 16:30 Central European Time (on working days)

Hotline Phone: +49-(0)6202-709 185

Between 8:30 and 16:30 Central European Time (on working days)

3

NOTE

i This manual is part of the documentation for the SILworX seminars at HIMA training centre. Because of the powerful nature of SILworX, we can only show the most important functions of the program here. It is recommended to participate in a seminar in order to deepen your knowledge. For further information about trainings have a look to HIMA homepage www.hima.com and then go for training.

5

2 Installation

2.1 System requirements Besides the personal computer, you need the hardlock/license and the installation CD-ROM. The computer hardware requirements are as follows: Minimum Recommended Processor Intel Pentium IV® Fast Dual2Core or

better Hard disc 500 MB > 10 GB RAM 250 MB 4 GB Graphic card resolution 1024x768 1600x1200 Operating system Windows XP,

Service pack 2 or higher, Windows Vista Ultimate/Business

Windows XP, Service pack 3, Windows Vista Ultimate/Business

Interface Ethernet interface Ethernet interface Table 1: PC hardware requirements

TIPP For huge projects we recommend high performance PC’s with maximum power for efficient working!

2.2 How to start the installation Standard Windows Installation, execute “Setup.exe” from CD.

2.3 De-installation Windows Start-Menue: Programs Hima SILworX De-install SILworX

6

2.4 License Management SILworX is released either with a USB-Hardlock (Dongle) or with a Soft-License. The Dongle doesn’t require any additional actions. He automatically contains a valid license. The Dongle is portable and can be used with any PC. The Softlicense is related to one particular PC Installation and therefore not portable. The Softlicense requires a valid license key. You get this key via Internet (E-Mail), means you must have a working Internet connection. Request License:

Pic. 1

7

Pic. 2

Create license request file:

Pic. 3

Send this file per E-mail to HIMA: silworx.registration@hima.com

8

After commercial clarifications are finished you get a valid SILworX license file. Activate the license:

Pic. 4

Pic. 5

Click to “Open” and the file is read in an activated.

9

NOTE

i The software license is depending on the PC hardware. Therefore after a new installation of Windows or installing new components (e.g. harddisk) the license is getting invalid. In this case please contact HIMA customer support in order to get a new license.

10

11

3 Important phrases and symbols PES Programmable Elektronic System (PLC) Resource Configurable PES with all necessary programming and

settings Drag&Drop Drag the chosen element while keeping left mouse button

pressed and let it drop on final position by releasing left mouse button

POU Program Organisation Unit All elements that are necessary to build up the logic of the user application as programs, functions and building blocks

PADT Programming and Debugging Tool Abbreviation for the programming tool that will be used to program the application and is necessary to communicate with the PES

Module Hardware unit to plug in a rack SB System Bus safeethernet Safety related communication between HIMA PES

12

13

4 Introduction to the handling of SILworX (Tutorial with the example of a Demo-Project)

Open the Demo-Project. Menu: Project Open Select the project and open it. (The Demo-project is available on the installation CD or you get it on demand from HIMA customer support)

Pic. 6

14

4.1 Screen layout and operation

Pic. 7

The screen layout can be changed by shifting the separation lines.

Pic. 8

Action bar

Structure Tree

Work Area

Log book

Menu- and Symbol bar

15

TIPP A double click on the separation line maximizes the Work Area or the Log book. A second double click on the separation line returns to the normal screen layout.

4.1.1 Simple operation principle SILworX has realized a simple and intuitive operation principle. From the Structure Tree the user has to select the object that he wants to use (by clicking on it once). Then the required Action is selected from the Action Bar: i.e. Program > Edit => The selected program opens in Edit mode or: Program > Online => The selected program opens in Online mode or: Program > Properties => Opens properties of the selected program So the operation principle is from left to right by Selection – Action – Working. The sequence of the Actions by topwards down is according to the normal sequence of work during designing a project – from starting with new elements via Edit mode to final documentation. The result of selection and chosen action opens up in the Work Area. Within the Work Area all usable objects (i.e. Variables, Building blocks, Connectors, Modules etc.) are available in the Object Selection Area. The objects are moved to the Work Area by Drag&Drop.

16

TIPP Dialogs:

It is recommended to set the general property of the dialogs to: “Automatically close the dialog upon success”

17

4.1.2 Structure Tree

Pic. 9

The Structure Tree shows all structure elements of a SILworX project. Like in Windows Explorer you can click on + to open up further sub levels. Within the Stucture Tree the object will be selected for the required Action (by clicking once). Within the Structure Tree objects can be copied, inserted and deleted. Clicking on an object by right mouse button will open the relevant context menu for that object:

Pic. 10

18

4.1.3 Action bar

Pic. 11

Create new objects

Edit the properties of an object

Open objects in Edit mode

Verification of objects

Open an object in Offline simulation

Start code generation for an object

Open object in Online mode (with PES)

Print out / documentation of an object

19

Depending on the prior chosen object in the Structure Tree only the enabled actions for this object are shown by colored icons. All other, disabled actions are shown by gray icons:

Pic. 12

All actions can alternative be started via context menu (right mouse button).

Pic. 13

Action enabled

Action disabled

20

4.1.4 Work Area Example: Open the program in Edit mode. Selection: Program Action: Edit

Pic. 14

Pic. 15

Edit Area

Object Selection Area Navigation Area

21

All objects, available for the chosen editor, can be taken from the different registers in the Object Selection Area by Drag&Drop into the Edit Area and used there. (Example see chapter 5.5.3 and chapter 5.6) Drag&Drop directly from Structure Tree into Edit Area is not possible! Also the registers in the Object Selection Area are only corresponding with the chosen editor. Within the Logic Editor i.e. variables, building blocks, connectors etc. are offered. In the Hardware Editor different racks, modules and variables that can be assigned to hardware. Navigation: (see also chapter 7.3.1) Logic overview: Select a logic page in the graphic overview and click on it. The requested page is displayed in the Edit Area.

Pic. 16

22

Pagelist: Select a logic page in the list and click on it. The requested page is displayed in the Edit Area.

Pic. 17

Cross References: In case a variable, a connector or an instance is selected in the Object Selection Area you can read all cross references in this table. Using the “Goto” – Function you can directly jump to the reference.

Pic. 18

23

4.1.5 Symbol Bar / Menu Bar

Pic. 19

Menus and symbols are highlighted if they are enabled for the chosen object. All disabled menus and symbols are gray. In case the meaning of a symbol or a column headline is not clear to you the Tool Tips will help you. For this stay with the mouse for a short time i.e. on a symbol and the attached Tool Tip is displayed.

Pic. 20

Example for a shortened expression in a table:

Pic. 21

Project overview / actual object

Symbol Bar Menu Bar

24

4.1.6 Log book

Pic. 22

Contents of the log book:

o Tracing of important steps in operation as code generation, forcing and loading of PES

o Hints according faults in operation o Results of verification o Results of code generation

25

4.2 Table handling Many settings in SILworX can already be done in the tables. All tables in SILworX are working the same way. Open e.g. the editor for the Global Variables.

Pic. 23

Double click on an editable field and modify contents:

Pic. 24

In some cases after a double click on an editable field a selection menu appears, i.e. when defining the Data type:

Pic. 25

26

For changing the content of a Check box just click on it:

Pic. 26

Standard functions as Copy/Paste are working for a complete line as well as for one cell. (see context menu, CTRL-V, CTRL-C)

Pic. 27

For each column a filter can be activated. The filter function is activated or deactivated by clicking with the mouse on the filter symbol:

Pic. 28

27

Use wildcard character:

Pic. 29

By one click on the headline of a column the complete table is sorted in alphabet way – upwards or downwards. Direction of sort is shown by the arrow symbol:

Pic. 30

28

4.3 Variables SILworX uses Global Variables and Local Variables.

4.3.1 Global Variables For the Global Variables exists in each Resource automatically an object:

Pic. 31

Global Variables are required for: Assignment to Hardware (i.e. analogue Input, digital Output) Assignment to Communication (i.e. Modbus, OPC, safeethernet) Assignment to System Variables Data exchange between building blocks (POU’s) Global Variables have the same status where ever they are used in the project and can be forced at all points of use. Global Variables can also be created on level „Configuration“ or on project level. All Global Variables defined on these levels can be used in all sub-levels. I.e. all Global Variables defined in Configuration level can be used in all Resources of this Configuration. To organize data exchange of Global Variables between different Resources you must define a safeethernet connection between these Resources.

29

4.3.2 Local Variables Local Variables are part or a POU (building block). They can not be assigned to hardware or communication. A Local Variable can also be forced by function „Local Forcing“.

NOTE

i In the register “Local Variables” in the FBS Editor appear also the localy used “Global Variables” as VAR_EXTERNAL” These variables are no “Local Variables” in the meaning of this chapter! Local Variables in the meaning of this chapter are exclusively: VAR, VAR_TEMP, VAR_INPUT, VAR_OUTPUT

Typical use: Interface Variable (VAR_INPUT, VAR_OUTPUT)

Pic. 32

30

Value pre-setting (initialized Variable):

Pic. 33

Connecting different logic parts:

Pic. 34

Advantage: In opposite to the alternatively use of connectors this method avoids the creation of huge network. The two parts of logic in the example remain two different networks. Respect the rules for the sequential execution of logic!

31

5 Creation of new project 5.1 Creation of a project structure Project New

Pic. 35

Choose project path and project name:

Pic. 36

TIPP It is recommended to set the general property of the dialogs to: “Automatically close the dialog upon success” This will have effect to all command dialogs.

32

The new created project already contains all basically relevant objects:

Pic. 37

33

5.2 Properties of the Resource Resource Properties

Pic. 38

Pic. 39

Change Resource Name

Change System ID (SRS

34

All settings are explained in the HIMax System Manual Choose name of the Resource Choose System ID, (This will be the unique number of each system within one configuration) Example: System-ID = 10 The Standard value 60000 must be changed; otherwise the generated code is regarded to be invalid!

Make settings for Safety Time and Watchdog. Please read carefully through the relevant chapters of the HIMax Safety Manual!

TIPP For a first test use the default settings!

Make setting for allowed activities. Please read carefully through the relevant chapters of the HIMax Safety Manual and follow the requirements of the approval board!

TIPP For a first test use the default settings!

For standard applications (normal communication load, no multitasking, no conversion from older Versions) all other settings can remain on standard settings. Click on button OK.

35

5.3 Properties of the Program Task Program Properties

Pic. 40

Pic. 41

36

All settings are explained in the HIMax System Manual

Make settings for allowed activities. Please read carefully through the relevant chapters of the HIMax Safety Manual and follow the requirements of the approval board!

TIPP For a first test set use the default settings!

For standard applications (no multitasking, no conversion from older Versions) all other settings can remain on standard settings. Click on button OK!

37

5.4 Definition of Global Variables Global Variables Edit

Pic. 42

Right mouse click in table “New global variable“

Pic. 43

TIPP Use the “Insert” key for creating easily some test variables

38

Result:

Pic. 44

Change a name: Double click on existing variable name and then change name

Pic. 45

Change data type: Double click on Data type, open list and select new data type

Pic. 46

39

Initial value: Double click in field Init Value and type in the inital value (matching the given data type).

Pic. 47

NOTE For the Initail Value there is a special meaning in SILworX. Variables attached to hardware will take the initial value in case of error. In the same way variables attached to communication will take initial value in case of failure in communication (mostly settable). Therefore the Initial Value must be the safe value for a variable!

Description: Double click on Description and fill in free text.

Pic. 48

NOTE

i The written description will automatically shown in the Logic Editor as an attached comment field next to the variable.

Setting attributes (Retain/Constant):

40

Pic. 49

Retain: Variable is buffered during power trip and will start after power is back with that last value. Constant: Variable can only be read out but not be written to.

NOTE

i You can work with whole lines as well as with contents of single fields of a table by using the standard copy functions of Windows ®. Import or Export via CSV-files (i.e. for Excel) is also possible.

Pic. 50

41

For further exercises please add some more variables:

Pic. 51

Save Global Variables:

Pic. 52

TIPP The star-symbol * in a register indicates a not (yet) saved editor!

42

5.5 Hardware 5.5.1 Resource type / Racks / Modules Hardware Edit

Pic. 53

Select Resource type: HIMax

Pic. 54

43

Select Rack type:

Pic. 55

As standard the rack with 15 slot is offered, In case you want to use a different rack type take the relevant rack from register „Racks“ and place it by using Drag&Drop on the existing rack (light grey area, see arrow).

NOTE

i In case the existing rack has already some modules attached, the modules and all their setting s are lost!

Pic. 56

Confirm with “OK”

44

Option: Adding of extension racks: All additional racks will be placed by Drag&Drop on the dark gray surface above or below existing racks.

Pic. 57

In the following examples no extension racks are used!

45

NOTE

i Rack 0 is a must within every HIMax System. The sequence of numbers of additional racks is defined according their position: Upwards increasing odd numbers, so rack 1, 3, 5, …. Downwards increasing even numbers, so rack 2, 4, 6, …. All racks must be connected in the same way (UP/DOWN Ports of the SB connection module). See also System Manual!

46

Set Name and properties for a rack: Double click to the Rack number:

Pic. 58

Enter a Name for the Rack and set Power supply (normally redundant) and Temperature monitoring:

Pic. 59

TIPP A good and short Rack name supports orientation and identification of modules in this rack!

Simplified explanation for temperature setting: Temperature threshold 1 means: Environment temperature in the cabinet is > 40°C (Recommended in normal air conditioned cabinets) Temperature threshold 2 means: Environment temperature in the cabinet is > 60°C (Urgently recommended because the module components are approaching the specified limits) For details please respect the HIMax System Manual!

47

Insert modules: Take the selected module from register „Module“ and place in the requested position by using Drag&Drop. Take care: Creating redundant IO module couples requires a special procedure, see chapter 5.5.2. Do not insert redundant IO’s with the standard procedure!

Pic. 60

Please pay attention to the rules that certain positions can only be used by certain modules, see also “System Manual”. Here you can find only the basic rules: Slot 1-2 only for System Bus modules (SB modules). Slot 3-6 for Processor modules (CPU modules) Slot 3-18 for Communication and/or IO-Modules

48

5.5.2 Assign redundant IO Modules Once redundant Connector Boards or redundant FTA are in use the respective modules must be set as redundant couples: Assign the first (left) module by Drag&Drop (see chapter 5.5.1)

Pic. 61

Right mouse click to the module: “Associate redundancy group”. The first proposal is always the next free slot right of the selected module.

Pic. 62

49

Result:

Double click to one of the redundant modules or to the newly created redundancy object in the table for all settings and variable assignments. All assigned variables include automatically the redundancy result. (Complies to an “OR” for Digital Inputs or “MAX” for Analog Inputs) See chapter 5.5.4.

IO redundancy object

50

5.5.3 Module settings Example of configuration:

Pic. 63

Within this manual we can only advise the major settings. To see all possible settings, System Variables and options please have a closer look into System Manual or according Data Sheets. Setting IP-Addresses of SB and CPU: The programming tool (PADT) later on can be connected to the PADT port of the SB modules as well as every other Ethernet port of the CPU or COM modules. The IP address of the SB is normally only used for the first Start-Up procedure, in the example we keep it on factory settings 192.168.0.99. The CPU can be used for PADT connection and/or safeethernet, therefore set a correct IP-Address. For a simple test example set the following addresses: Module type, slot IP address SB module, slot 1 keep 192.168.0.99 SB module, slot 2 keep 192.168.0.99 CPU module, slot 3 set to 192,168.0.11 CPU module, slot 4 set to 192.168.0.12

51

For real projects please pay attention to the standard regulations for IP addressing and have a look to the System Manual and Communication Manual. For real IP addresses please also contact the local IT administration accord what IP numbers can be used in that project! Double click on the X-CPU 01_1 in Slot 3: Type in the requested IP address (in our example: 192.168.0.11):

Pic. 64

TIPP Select a Standard Interface for your PADT. This will be on top of the available interfaces in the login option list.

Keep the other settings on standard. They match most of the situations. “Close” Detail view to Hardware Configure in the same way the IP addresses of the second CPU module in Slot 4.

52

5.5.4 Assignment of Variables to Hardware In order to use the status of a hardware channel within the logic the requested channel must be connected to a Global Variable. This Global Variable must already be defined and must have the correct data type.

NOTE

i For real projects please refer to the according Data Sheets and see the meaning of parameters and settings.

Example: Settings and assignment for the analogue input module AI 32 01 Double click on i.e. module X-AI 32 01 (in example slot 9): Open register “IO-Submodul AI32_01: Channels” Assign the variable per Drag&Drop to the hardware channel.

Pic. 65

53

NOTE

i For redundant modules click to the redundancy object, displayed in the register “Redundancy”. See also chapter 5.5.2

An assignmet can be deleted by clicking to a certain table cell and delete the existing name.

NOTE

i The Process value can be scaled by the parameters “Process value at 4 mA” (4 mA) and “Process value at 20 mA” (20 mA) automatically. Also the input is supervised for line break and line short as defined in NAMUR recommendations (NE43). In case of faults the assigned variable takes its initial value. Alternative you can use the not scaled value (raw value) with the resolution: 1mA=10000. Then you must define the line monitoring and the status “Channel ok” within the logic yourself. For details please refer to Data Sheet and Safety Manual. Example for scaling:

Pic. 66

Close Detail view

Pic. 67

54

Assign in the same way the other hardware variables: Example: X-DO24 01

Pic. 68

Example: X-DI32 01

Pic. 69

Close Detail view, save Hardware and close Editor!

55

5.6 Create Logic (Program) Open program in Edit mode: Program Edit

Pic. 70

Open register „Blocks“ in the Object Selection Area and sort the table according „Libtype“.

Pic. 71

56

For the example look for following Blocks (POUs) and take them per Drag&Drop into the Edit Area: From type „Bitstr“ take an AND From type „Compare“ take a „GE“ From type „Timer“ take a TON Result:

Pic. 72

Now click on register „Global Variables“ and drag the variable „Sensor 1“ into the Edit Area:

Pic. 73

57

TIPP If necessary Zoom In the picture of the Edit Area for comfortable work:

Pic. 74

Connect the variable to the input connection point of the AND:

Pic. 75 Now drag in variable „Sensor 2“ into Edit Area and connect with the second input connection point of the AND. The AND needs one more input. So move the cursor to the lower frame of the AND until you can see a double-arrow. Press left mouse button and keep hold. Now move the mouse downwards and extract the AND by as many inputs as required. In the example we need 3 inputs. (Maximum number of inputs or outputs is 16)

Pic. 76

Press left mouse button and keep hold Release left mouse

button

58

Create Value Field fort he comparator „GE“ and for the timer „TON“: A right mouseclick on any free position in the Edit Area opens the context view. Select “Create ValueField”.

Pic. 77

Click on the Value Field and fill in the requested value in the correct format. In our example it has to be a REAL value, so fill in „800.0“.

Pic. 78

Pic. 79

Ignore first the indicated error. The error appears because the final data type is not yet specified and will be fixed later.

59

NOTE

i The color of the value field automatically adapts to the typical color for the data type after you finish the entry. Take care about the correct spelling (see Online Help) Examples:

Pic. 80

Create in the same way a value field for the timer TON. Enter: T#10s

Pic. 81

Take now the variables „Process Value“ and „Valve1“ from the table of Global Variables and complete the simple logic network:

Pic. 82

Update the data type conflict and the error mark disappears.

Pic. 83

Save the Program and close the editor!

60

5.7 Code Generation Close (if open) the Version Comparison Select Resource Code Generation

Pic. 84

Pic. 85

Request Reload Code. For Reload see the according chapters in the System Manual and Safety Manual

Like Verification for the Resource, but no Code

File is generated

61

In the example we don’t create a reloadable code! The result of Code Generation is a Configuration file that contains all prior done programming and settings. The result appears temporally in a dialogue and finally in the logbook. For details explore the line.

Pic. 86

As major information you find here the generated code version. A code with persisting warnings can be loaded anyway, but for real projects the programmer should note the warnings. They’re mostly hints about forgotten or not completed tasks. Errors you must fix first. A code with persisting errors is not valid. Use the “Goto” function (right mouse click to the message)!

For safety related operation the code must be generated twice! The code is only valid if twice the same Code-Version is generated. With this comparison theoretically possible errors during code generation can be detected. See also the hints in the Safety Manual!

62

5.8 Offline Simulation Within the Offline Simulation SILworX simulates the execution of the programmed logic. Most function are identically to Online Test. For this read chapter 7.3 . Simulation of variables during Offline Simulation is similar to forcing. For this read chapter 7.5 Select Program Offline, confirm by click on OK button:

Pic. 87

Also fort he Offline Simulation a code is generated. The result appears temporally in a dialogue and finally in the logbook. Please check about eventually shown warnings or errors!

Pic. 88

63

The Simulation must be started: Menu Online Applications Application Cold Start

Pic. 89

Pic. 90

64

Double click on a variable opens the Force Dialogue. Insert the requested Force Value and activate the Force Switch (set hook within box). Confirm by pressing OK button.

Pic. 91

TIPP For variables of type BOOL you also can type in „1“ instead of „TRUE“.

If you want to simulate several variables you can select the requested variables by clicking on them with mouse while the CRTL key is pressed (similar to standard Windows handling). Afterwards open context menu with right mouse button and select “Edit global force data“.

Pic. 92

65

Now fill in the requested simulation value (Force Value) for each variable shown and activate the Force Switch (set hook in box). Result:

Pic. 93

Now you see the new status of the selected variables with all consequences for the logic program.

Pic. 94

NOTE

i The Offline Simulation can be used for pure logic simulation. Real effects e.g. caused by hardware or communication can normally not be simulated. Offline Simulation never replaces real tests!

66

67

6 Start-Up of a HIMax Systems

6.1 Basic knowledge A HIMax PES consists out of 1 or 2 System Bus modules (SB), 1-4 Processor modules (CPU) and additional I/O modules and COM modules. These modules have to be positioned within a rack according the rules of the System Manual. The configuration must be according the hardware programming of SILworX (layout must match!). Basically we must assume the modules are in delivery status (default factory settings) or they have some history (i.e. they are taken from an other HIMax System). The SBs and the CPUs need to have corresponding settings. While these settings are done correctly the connected modules will “know each other” and will form a „system”. This status we call “System Operation” and it is the aim of StartUp procedure. Only in System Operation you can load the configuration file, created by code generation, and start the system. The basic conditions for System Operation are: SBs and CPUs have the same SRS (see 6.1.1) The “Responsible Attribute“ is set correctly (see 6.1.2) The Mode Selection Switch on the CPU is on position STOP or RUN The HIMax is in System Operation when the yellow LED „STOP“ on all SBs and all CPUs is ON or blinking!

68

6.1.1 SRS – System Rack Slot One of the most important settings for SB and CPU is the so called SRS: System Rack Slot System: The number for system is a property of the resource. It marks the system, i.e. for communication purposes between resources Rack: Each rack has its own number = Rack address (according to the settings in Hardware-Editor). In rack 0 exists one or more CPUs. This rack always exists. In the extension racks are normally only I/O and/or COM modules. The racks are connected to each other over the System Bus modules (SB’s). Therefore each rack number within a System Bus must be unique. Slot: Slot for a module. The slot depends on the positioning of modules in Hardware Editor. So by SRS you will have the exact position of a module within one HIMax system and even within a complete project.

6.1.2 „Responsible Attribute“ for a SB module An additional major property is the attribute „Responsible“ for a SB module. In each system bus (left: Bus-A, right: Bus-B) it must be defined, that one SB module takes the role of a “Main Supervisor”. The „Responsible“ SB coordinates the access of CPUs to this System Bus. For rack 0 this setting is fixed to the left SB module „SB-A“. In most standard configurations the „Responsible“ task for System Bus B will be attached to the right SB module “SB-B” in rack 0. Both, SRS and property „Responsible“, is saved in a non volatile memory area on the connection modules of the SBs and CPUs. So this important information is remains in a rack even if the modules is exchanged.

6.1.3 MAC Address Each HIMax module becomes its own individual hardware address - the MAC address, when it is manufactured. The MAC address is written on a sticker on each SB and CPU module. Via the MAC address you can get in touch with the module even if you do not have any information about the set IP address and SRS.

69

6.1.4 IP Address For SB, CPU and COM you can set IP addresses. A normal Login requires access over an IP address. The IP address is not important for System Operation! The IP address of a module is saved in a non volatile memory area within the module. The IP address is determined according following priorities: If a valid (SILworX) configuration is loaded, the IP addresse is taken from that configuration. If there is no valid (SILworX) configuration, the last used IP address for the module is getting active. That may become interesting for modules with some history. SB modules without history get automatically the delivery (default) settings and CPUs that have been booted with Mode Selection Switch in position „INIT” get the standard IP address 192.168.0.99 . As this algorithm is not always easy to understand, we recommend to read out the actual IP address by using the MAC browsing dialogue and to use them afterwards. The IP address of the programming tool (PADT – normally a PC) must be in the same network area as the IP address of the module that you want to connect to (described by the Subnetmask). Eventually the IP address of the PC must be set correctly first. Example for a working connection: HIMax module:

IP address: 192.168.0.99, Subnet mask: 255.255.255.0

PC IP Address: 192.168.0.215, Subnet mask: 255.255.255.0

70

ARP problem: For the first Start-Up procedure of a HIMax you will have to connect several times to different modules, that may have the same standard (default) IP address. That can be the reason that the so called ARP Cache of the PC has stored the requested IP address in combination with a different (“old”) MAC address and will block the connection. In that case the ARP Cache must be cleared by using the DOS command: “arp –d”.

Pic. 95

That ARP problem can be avoided if (as recommended) during StartUp procedure only point-to-point connections between PC and modules is used and no installed network with switches.

71

6.1.5 Set IP-Address for the Network-Adapter of your PC First select the right Network Adapter:

Pic. 96

Set the properties of the Internet Protocol:

Pic. 97

72

Set matching IP address and Subnet mask:

Pic. 98

NOTE

i The IP address in only accepted if the physical connection is already established.

73

6.1.6 Mode Switch on the CPU The Mode Switch on the CPU is only relevant during Booting (powering up). Booting in Mode Selection Switch position INIT: Standard IP address 192.168.0.99 is in use Standard SRS 60000.X.X is in use Standard Login is valid Standard release settings are in charge Reset to delivery (default) settings is possible Booting in Mode Switch position STOP: Booting in Mode Switch position STOP will prohibit that a CPU with a valid configuration and set “Auto start” goes directly to RUN and start the (eventually unknown) application program. If a valid configuration is loaded to a CPU and the conditions for System Operation are fulfilled, all settings as SRS and IP addresses from the valid configuration are activated. That must be paid attention to when during a first Start-Up procedure a CPU with some history is placed in the system and booted. Recommendation: For CPUs with unknown history always reset to delivery (default) settings. During STOP the application program is not executed yet! A new application program can be loaded. Booting in Mode Selection Switch position RUN or turning from INIT>RUN In case no valid configuration is loaded, the CPU it remains in status „STOP / Invalid configuration“ (yellow LED “STOP” is blinking). Then a valid configuration must be loaded (Download). When „Auto start“ is set and a valid configuration is existing, the CPU goes to normal RUN mode and executes all loaded application programs in cyclic operation.

74

6.1.7 INIT/STOP/RUN - LEDs on the CPU „INIT“ LED is blinking CPU is in “INIT” mode. No System Login is possible – only Module Login. Set to delivery (default) setting is possible. “STOP“ LED is blinking CPU is already in System Operation, and „knows“ all other CPU and SB modules. System Login is possible. CPU has no valid configuration. Download of a valid configuration (result of code generation) is possible. „STOP“ LED is on CPU is already in System Operation, and „knows“ all other CPU and SB modules. System Login is possible. CPU has a valid configuration and can be started. „RUN“ LED is on CPU is in RUN. The user application program is executed. This status is defined as normal operation!

75

6.2 Start-Up procedure for basic rack (rack 0) Prepare start situation: Two SB modules and one CPU are positioned within rack 0 (additional CPUs can be placed later on and synchronize then automatically) Mode Selection Switch of CPU is on position “INIT”.

Pic. 99

The connections towards extension racks are not yet established. A Cross-Over Ethernet cable is ready for use. A SILworX project is prepared according the steps described in chapter 5. Now establish a connection between your PC and the PADT port on the left SB (SB-A). It is absolutely necessary to use a Cross-Over cable for this!

Pic. 100

76

Open your project in SILworX and click on Hardware Online:

Pic. 101

As there is no System Login possible go to “Module Login”:

Pic. 102

77

6.2.1 Start-Up procedure for a SB module In the example the Start-Up procedure for the left SB for System Bus A is described. The procedure for the right SB for System Bus B is the same. Double click on SB module in slot 1 opens the Module Login dialogue:

Pic. 103

A Login always needs the entry of the relevant SRS and IP address of the selected module. Normally these information are not known for the first Start-Up procedure. The main settings for the Start-Up can be executed also via MAC-Login. Click to “Search” In the following dialogue you have to fill in the MAC address of the module that you want to connect to (see sticker on the module).

Pic. 104

Then click “Search” and “Change”

78

Possible errors, troubleshooting:

Pic. 105

In case the search function via MAC address is not working, it could have one of the following reasons for that:

o MAC address is typed in wrong o No Cross-Over cable for the connection to SB is used o Network card in the PC has no fixed IP address o Physical connection problems. Check the LED on PC

network card and HIMax module o Windows XP Firewall is disturbing

79

Enter now the matching SRS (according your project), in example 10. Set SB Responsible (see also chapter 6.1.2.!) (This setting would not be necessary for SB in Slot1 but it’s also not disturbing and doing so keeps the procedure identical for both SB’s) The setting for IP address is now not necessary because later on (after loading) the IP, already set in the project, is getting valid. Click on button “User Name” and enter the standard user name. That can easily be done by using the keys „Ctrl“ + „A“! Example for SB in Slot 1:

Pic. 106

Set the values by giving the command “Write”:

Close the dialogue: “Search per MAC” with “Cancel” Close the Module Login with “Cancel”

80

Check now the report in the logbook (explore line):

Pic. 107

Start-Up of the second SB module: Connect to the PADT port of the second SB module on slot 2 by using the Cross-Over cable and repeat the prior steps in this chapter. Repetition of the most important settings of SB modules: SB-A module (slot 01): set SB responsible and SRS SB-B module (slot 02): set SB responsible and SRS

81

6.2.2 Start-Up procedure for a CPU Double-click on the CPU in slot 03 opens the Module Login dialogue:

Pic. 108

A Login always requires the entry of the correct SRS and IP address for the relevant module. Due to the INIT mode of the CPU a standard SRS and standard IP is now available. Click to “Edit” set for IP address and SRS the “Default value”:

Pic. 109

82

Click now in the field “User Name” and enter the standard user “Administrator” , empty password and Administrator Rights. Shortcut: Just enter „CTRL“ + „A“! Click to “Login”

Pic. 110

The Online Detail View of the CPU opens:

Pic. 111

83

Possible errors, troubleshooting: This is now an IP based Login, therefore you have to respect the general rules for IP networking. If the Login does not work check whether the IP address of the PC is within the same network and the selected IP address of the module. See also example in chapter 6.1.4 Check whether you are really in the right lane: Hardware Online, Module Login (don’t try System Login)

84

Step 1, set CPU to factory (default) settings (Global reset): Menu „Online“ Maintenance/Service Assemble Module Factory Settings

Pic. 112

By the command „ Assemble Module Factory Settings“ all existing settings and configurations of this CPU are deleted. This step is always recommended, if the CPU is supposed to have a history.

Pic. 113

Finish action by clicking on button „Ok“.

Pic. 114

FS = File System

85

Step 2, Special situation: Mono configuration: System is supposed to be in MONO Operation if only one SB module and one CPU is configured. Execute this Step only if you really have a Mono configuration (mostly not, standard is a redundant configuration)! In this case the switch for configured MONO Operation must be activated: Menu Online Start-up Set Mono/Redundancy Operation

Pic. 115

Set Redundancy to Mono and acknowledge by clicking on button „Ok“.

Pic. 116

NOTE

i This setting will is only relevant if also a MONO project is loaded. Otherwise this setting is ignored.

86

Step 3, Set SRS on CPU: Menu „Online“ Start-up Set SRS

Pic. 117

Fill in the correct SRS (from project):

Pic. 118

Pic. 119

NOTE

i The connection to the module is interrupted now because your Login was based on the now overwritten (“old”) SRS! It doesn’t matter – the CPU is now finished anyway!

Close the opened registers of HW Editor.

87

Summary of the most important settings of CPU: - Set Module Factory Settings - For Mono configuration set „Mono Operation“ - Set SRS Now turn the Mode Switch on the CPU from INIT to RUN. After a few seconds the yellow LED “STOP“ starts blinking. Now check all “STOP” LED’s on both SB and the CPU. If all LED’s are blinking yellow, the system has turned to System Operation (STOP / invalid configuration) and is ready to be loaded now with a new configuration. In case no extension rack has to be installed proceed with Start-Up in chapter 6.4 .

88

6.3 Start-Up extension rack Attention: The connections between already installed racks and new extension rack must not be established! Leave the connection open! Open your project in SILworX and click on Hardware Online:

Pic. 120

As there is no System Login possible go to “Module Login”:

Pic. 121

89

In each rack you must set the SRS address in both SB modules! In the example the Start-Up procedure for the left SB for System Bus A is described. The procedure for the right SB for System Bus B is the same. Double click on SB module in slot 1 opens the Module Login dialogue:

Pic. 122

A Login always needs the entry of the relevant SRS and IP address of the selected module. Normally these information are not known for the first Start-Up procedure. The main settings for the Start-Up can be executed also via MAC-Login. Click to “Search” In the following dialogue you have to fill in the MAC address of the module that you want to connect to (see sticker on the module).

Pic. 123

Then click “Search” and “Change”

90

Enter now the matching SRS (according your project), in example 10.1 (System-ID = 10, Rack-ID = 1) The setting for IP address is now not necessary because later on (after loading) the IP, already set in the project, is getting valid. Click on button “User Name” and enter the standard user name. That can easily be done by using the keys „Ctrl“ + „A“! Example for SB in Rack 1, Slot 1:

Pic. 124

Set the values by giving the command “Write”:

Close the dialogue: “Search per MAC” with “Cancel” Close the Module Login with “Cancel”

91

Check now the report in the logfile (explore line):

Pic. 125

Start-Up of the second SB module: Connect to the PADT port of the second SB module on slot 2 by using the Cross-Over cable and repeat the prior steps in this chapter. Repetition of the most important settings of SB modules: SB-A module (slot 01): set SRS SB-B module (slot 02): set SRS

92

Now connect the new extension racks as shown in the hardware configuration:

The System Bus is very fast. Use for the System Bus wiring only HIMA released (high performance) cables and devices. No standard Ethernet-Switches allowed! (see System Manual)

Pic. 126

port: DOWN

port: DOWN

port: UP

port: UP

93

6.4 Loading Resource (PES) and start running For loading you must log in by a System Login procedure: Resource Online

Pic. 127

Before the first loading the existing (default) IP address is still relevant. The SRS has already been set to the correct value (see chapter 6.2) If there is any doubt start dialogue “Search per MAC” and take over the then shown connection data.

Pic. 128

94

The read out data (IP address and SRS) can now be seen in the left part of the window. Click now on button “User Name” and type in the standard user. Therefore you can also use the keys „CNTR“ + „A“!

Pic. 129

Click on button „Login“ Result: Control-Panel (CP) opens

Pic. 130

95

Afterwards click on icon „Download resource“

Pic. 131

NOTE

i For Download the System must be in STOP. If not, execute first the STOP command:

Pic. 132

Start Download procedure with button „OK“

Pic. 133

Pic. 134

96

After the Download the new (Project)-IP is getting valid. The used link was based on the old (Standard)-IP. Therefore the link is disconnected!

Pic. 135

Login again by clicking to the “Connect” button. Select the right IP address from the option list (best you’ve defined a Standard interface, see chapter 5.5.3).

Pic. 136

Pic. 137

97

Start the Resource with the command icon „Cold Start“.

Pic. 138

Result: Both SB modules and the CPU module will change to status RUN. If more then one CPU is configured, insert now one by one the redundant CPU modules. The newly inserted CPU’s are automatically synchronized and go to RUN mode.

98

6.5 Set Date/Time Menu Online Start-up Set Date/Time

Pic. 139

Pic. 140

99

7 Working with existing project (Online) 7.1 Open existing project Menu: Project Open

Pic. 141

Explore the project in order to see the project structure:

Pic. 142

100

Following objects from the structure tree area of a resource can be monitored Online: Resource: Control Panel for system overview, diagnostics and loading procedures Program: Online monitoring of user application program Hardware: Online Hardware monitoring for diagnostics, module handling Protocol: Online monitoring of communication variables (not yet possible) SafeEthernet: Online monitoring of communication variables (not yet possible) Global variable: Online monitoring of Global variables (not yet possible)

101

7.2 Start connection to PES, Start Control-Panel Generally it is recommended (but not absolutely necessary) first to get an overview about system when starting Online activities. Therefore open the Control panel.

7.2.1 Online Login Resource Online

Pic. 143

Select the IP Address of the module to which you are physically connected. Normally this is the top shown IP Address indicated as <Standard> (This is configurable in the Hardware settings by the programmer, see chapter 5.5.3). In case of problems (IP Login not working) see chapter 6.1.4 and 6.1.5. Fill in the Access Data: If no user management is used (Standard) get the standard access: Click on field “User name“ and insert the standard user. For this just enter “CRTL“ + „A“! (User: „Administrator“, no password, rights „Administrator”) If a user management is established for this resource you have to know and to use the valid „User name“, „Password“ und „Rights“!

102

7.2.2 Control Panel (CP) Result:

Pic. 144

The Control Panel (CP) informs you i.e. about:

o System Status o Force Status o I/O Errors o Communication errors o Cycle time o Safety parameters o Status of programs o Status of existing safeethernet links o Used or needed licenses

103

NOTE

i As long there is an existing Online connection to the PES, an additional Status Line comes up at the bottom of the screen, containing the most important Online information.

Status line:

Pic. 145

PADT Usermanagement

PES Usermanagement

System state System status

Force information

Reserve cycle time

104

7.3 Program Online (watch status of logic) Resource (in example “PES10“) Program Online Result: (for example we show an advanced logic)

Pic. 146

If there is no other Online window opened you first have to login yourself. The procedure for this is described in chapter 7.2.1 . Status „TRUE“ is visualized by a red line. Status „FALSE“ is visualized by a blue line. Variable status (process value) is shown additionally within the tables of the Object Selection Area.

105

Also automatic Online-Test(OLT)-Fields can be activated. Give a right mouse click in the Work Area Activate Auto OLT-fields. Now on all lines the actual variable status is displayed:

Pic. 147

Free OLT Fields: If you want to display on a logic page the status of further variables (not included within the normal logic on that page) you just take the requested variable by Drag&Drop from the table of the Object Selection Area into a free space on a logic page:

Pic. 148

106

7.3.1 Navigation in the logic Using the Logic Overview in Navigation Area:

Pic. 149

By a simple mouse click you can select any zone from the graphical overview. With the mouse wheel adjust the zoom factor. Using the Page list in the Navigation Area:

Pic. 150

For selection of a certain page just give a double click on the relevant “Page position“.

107

Using Local Cross References in the Navigation Area:

Pic. 151

In the register „Local Variables“ of the Object Selection Area you can find all variables used in this building block (POU). Search for the requested variable and mark it by clicking once on it. Please refer to the hints in chapter 4.2 according table handling (i.e. sort, filter, ...). Now all locations where this variable is used can be seen in the Navigation Area together with access direction “Reading” or “Writing”. Double click on the indication in column “Usage” opens the relevant logic page, where the selected position of that variable is located, in the Work Area.

Mouse double click

108

7.4 Global variable Cross-Reference list Global Variables are used for: Mapping to Hardware (i.e. analogue input, digital output) Mapping to Communication (i.e. Modbus, OPC, safeethernet) Mapping to System Variable Data exchange between different Program Organisation Units (POU) (for this see also chapter 4.3.1) The cross reference for Global Variables therefore is a central instrument for navigation within the system. Everywhere, where the list of Global Variables is seen, the cross references are also displayed: Global Variables Editor Protocol Editor Hardware Editor Logic (FBS) Editor Example for Program (Online):

Pic. 152

Double click on the “Usage” position opens the relevant editor and shows the use. (in V3 the target editor opens only offline)

Mouse double click

109

7.5 Forcing

Forcing is always a safety relevant interference to the normal operation of a Safety System. Please respect the according hints in the Safety Manual! Forcing is spited in two areas: Global Forcing and Local Forcing. Both areas have their own activation and own displays and tables. The handling itself for both areas is generally identical. In the following chapters only Global Forcing is explained. For the Local Forcing you just have to pay attention that only variables of type VAR can be forced!

110

7.5.1 Force releases and deactivation The release of „Global Forcing“ is a property of the resource. You can check the releases in: Resource Property (see chapter 5.2)

Pic. 153

NOTE

i This setting is part of the loaded code. In case forcing is not allowed in here, a new code generation must be started and the resource has to be loaded newly (new code version!)

111

The release for „Local Forcing“ is a property of the program. You can check the releases in: Program Property (see chapter 5.3)

Pic. 154

NOTE

i This setting is part of the loaded code. In case forcing is not allowed in here, a new code generation must be started and the resource has to be loaded newly (new code version!)

Additionally there is a possibility to disable forcing (global and local) via a System Variable. This variable can be operated i.e. by a key switch. The System Variable is called „Force Deactivation“ and available for the system HIMax within the Hardware Editor. The status of the „Releases“ and of „Force Deactivation“ can be seen within the „Force-Editor“.

112

7.5.2 Force-Editor As soon as an Online connection to the PES is established an additional menu „Forcing“ appears. Start the „Force-Editor“!

Pic. 155

The Force-Editor shows an overview about the most important force information:

o Force status (stopped, prepared, active) o Forced variables (yes, no) o Remaining Force time o Force-Timeout reaction o Forcing allowed (property of the resource) o Force deactivation (System Variable)

Pic. 156

113

7.5.3 Forcing of Variables Double click on a variable in the list opens the Force Dialogue:

Pic. 157

Also (standard Windows) multiple selection is possible. For this just select your requested variables by clicking on them with mouse while the key “CTRL” is pressed. Then with right mouse click open context menu and select „Edit global force data“:

Pic. 158

114

Result:

Pic. 159

Now insert the relevant force value and activate the force switch (set hook in box in column F)

Pic. 160

NOTE

i For variables of type BOOL you can edit simply a „1“ instead of „TRUE“.

Click on „OK“ button.

115

Alternative: Forcing directly in the logic: Open the program (or any building block) Online (see chapter 7.3). Double click on a variable within the logic opens again the dialogue “Edit global force data”. Enter force value and activate forcing:

Pic. 161

A forced variable can be identified by a switch symbol close to the variable:

Pic. 162

NOTE

i Forcing by using OLT Fields does not work!

116

7.5.4 Start/Stop Forcing Starting and stopping the forcing is only possible if the Force Editor is visible and opened! Menu „Forcing“ Start global forcing

Pic. 163

Eventually the Force Duration has to be defined. Start with „OK”:

Pic. 164

Result:

Pic. 165

The active value is marked in yellow color! The variable is successfully forced and effective!

117

Stop forcing: Menu „Forcing“ Stop global forcing

Pic. 166

You can select whether all force data (force values and force switches) should be reset also (recommended!). As long as force data are not reset the forcing has not really ended and the force status changes to “Forcing Prepared“.

Pic. 167

Stop forcing by clicking on „OK“.

118

7.6 Diagnostics

7.6.1 System Diagnostic - Control Panel The Control Panel shows a complete system overview. For more detailed analysis it is recommended to open the Online view of the different editors, i.e. for problems within the I/O area you should open the Hardware editor Online (see chapter 7.6.2)

7.6.2 Hardware Diagnostic Hardware Online If no other Online window is already opened you must first login. For this please refer to chapter 7.2.1 . Result:

Pic. 168

Modules with existing warnings are in yellow color (in example slot 04). Modules with faults/failures are in red color (in example slot 05).

119

Double click on the module opens the Detail View: Modul Status:

Pic. 169

Firmware (OsVersion):

Pic. 170

120

From Online Menu you get the “Module Data Overview”:

Pic. 171

Pic. 172

(BS is the “Firmware”) The Module Data Overview shows for all modules the Module Name, Firmware data, Hardware Version and Serial Number.

TIPP Save the content of the table in a .CSV file!

121

7.6.3 Monitor values and status of modules Open the Force Editor (see 7.5.2):

Pic. 173

Inputs: All modules are displayed in a tree structure with the information of SRS.

Pic. 174

For the exact meaning of the indicated information see the according data sheet of the module. Please find some examples: Ch.Value Status of a digital input Channel OK Result of the internal self test of a channel LB Line break LS Line Short circuit Process value For Analogue Inputs the scaled value according

parameterization Raw value Value in mA, 1mA = 10000 Digit

Measured value is 4.2849mA

Channel is OK

Line break active channel is not OK

System 10, Rack 0, Slot 7

122

7.6.4 Longterm/Shortterm diagnosic buffer For each module there is an internal diagnostic buffer. This diagnostic buffer can be evaluated by experienced users with good system knowledge and with the help of the according data sheet. If you don’t know where the problem was or is, first have a look into the diagnostic buffer of a CPU (one CPU is enough, anyway which one, because all CPU’s collect diagnostic data from all over the system). Or open directly the diagnostic buffer of the module supposed to have a problem. Go to Hardware Online (see chapter 7.6.2) Right mouse click on the module Diagnosis

Pic. 175

Click on „All entries“ (the read out may take some seconds). Right mouse click on any entry in the table Save

Pic. 176

123

Save the diagnostic file with a clear file name and send the file to HIMA Hotline.

Pic. 177

Contact: himax.support@hima.com For fault analysis HIMA Hotline needs minimum following information:

o LED status of all CPU modules and the faulty module o Module data of the CPU modules and the faulty module

(Module Data Overview) o Diagnostic file of all CPU’s and the faulty module o SILworX version

124

7.7 Reload

Reload is always a safety relevant interference to the normal operation of a Safety System because the executable code is changed. Please respect the according hints in the Safety Manual! Preconditions for Reload:

• Resource is already loaded and in RUN condition • The loaded Resource Configuration (file set) is available on PC • A modification is properly (error free) finished with respect to all

existing restrictions. See System Manual! • Reload is allowed according the Resource and Program properties • Sufficient reserve cycle time in the PES

Reload is independent of any redundancy structure, means it also works with only one CPU in operation! For the Code Generation a reloadable code must be requested. See also chapter 5.7.

Pic. 178

125

Result is shown in the logbook, explore the line.

For safety related operation the code must be generated twice! The code is only valid if twice the same Code-Version is generated. With this comparison theoretically possible errors during code generation can be detected. You must compare both, the main Code Version and the Reload description code. See also the hints in the Safety Manual!

Pic. 179

Execute the Reload: You need a System Login, see chapter 7.2.1 Menu “Online” Resource Reload

Pic. 180

126

New and old Code Versions are indicated:

Pic. 181

Pic. 182

The Reload is finished if also the phase “RELOAD CLEAN” is finished. During “RELOAD CLEAN” no further Online command is possible.

Pic. 183

Pic. 184

127

8 Save Project When closing the project the relevant project file (see chapter 5.19) is automatically updated and „packed“. The project appears within Windows Explorer only as one file with name: “Project.E3“. This file can be copied, renamed, shifted, packed and restored and afterwards the project can be opened and modified again. Also during project work the user can make as many copies of the project as requested. This can be done i.e. after every loading procedure or to fix the actual project status at that time. Project Duplicate

Pic. 185

TIPP Save project title together with date and time

Pic. 186

128

129

9 Index Access Data 101 Action Bar 18 Administrator 101 ARP problem 70 Assemble Module Factory

Settings 84 Code Generation 60, 110, 111,

124 Code Version 61, 126 Cold Start 63, 97 Communication 108 Communication Error 102 Computer hardware 5 Connect 96 Connection 101 Constant 40 Control Panel 102, 118 CPU 81 Cross Reference 22, 107, 108 Cross-Over cable 75 CSV-files 40 Cycle time 102 Data type 25, 38 De-installation 5 Diagnostic Buffer 122 Diagnostics 118 Dialogs 5, 16 Dongle 1 Download resource 95 Edit Area 21

extension rack 44, 88 Fault/Failure 118 filter 26 Force 113 Force Activation 110 Force Deactivation 111, 112 Force Dialogue 64 Force releases 110 Force Status 102 Force Switch 64, 114 Force Value 64 Forced variables 112 Force-Editor 111, 112, 121 Force-Timeout Reaction 112,

116 Forcing 109 Forcing Prepared 117 Global 37 Global Forcing 109 Global reset 84 Global Variables 28 Hardlock 1 Hardware 42, 52, 108 Hardware Diagnostic 118, 121 I/O Fault 102 INIT 73, 74 INIT mode 81 Initial value 39 initialized Variable 30 Installation 5

130

De~ 6 Introduction 13 IP address 50, 69, 101 License 6 Line Break 121 Line Short 121 Load 93 Local Forcing 109, 111 Local Variables 29 Log book 24 Login 101 MAC address 68 MAC-Login 77, 89 Menu Bar 23 Mode Switch 73 Module 42, 50 Module Login 77 MONO Operation 85 Multiple Selection 113 Navigation 21, 104, 106 Network-Adapter 71 New Project 31 Object Selection Area 21 Offline Simulation 62 OLT-Field 105 Online 99, 101 Operating System Version 119 operation principle 15 PADT 11 Page Position 106 Pagelist 22 pagename 22 Password 101

PES 11 POU 11, 108 Process Value 53, 121 Program 55 Project 99 Project structure 31 Properties 33, 35 Rack 42, 43, 75, 88 Raw Value 121 Reading 107 Reload 124 RELOAD CLEAN 126 Remaining Force time 112 Resource 11, 33, 93 Responsible Attribute 68 Retain 40 RUN 73, 74 Safety Parameters 102 SB 77 Screen layout 14 set date/time 98 software license 9 SRS 68, 121 Standard Interface 51 standard user 82, 94 Standard User 101 Start 101 Start Forcing 116 Start-Up 67, 75, 77, 81, 88 Status Line 103 STOP 73, 74 STOP command 95 Stop Forcing 116

131

Stop global forcing 117 Store Project 127 Structure Tree 17 Symbol Bar 23 System Bus 92 System Diagnostics 118 System Operation 67 System requirements 5 System Status 102 System Variable 108, 111 Table handling 25 Tool Tip 23 UP/DOWN Ports 45 User 101

User Management 101 value field 59 VAR 109 VAR_INPUT 29 VAR_OUTPUT 29 Variable 28, 52, 113 Warning 118 wildcard 27 Windows XP Firewall 78 Work Area 20 Work with Global Force Data

113 Writing 107 Zoom Factor 106

HIMA Paul Hildebrandt GmbH + Co KG P.O. Box 1261 I 68777 Brühl I GermanyPhone +49 6202 709-0 I Fax +49 6202 709-107www.hima.com

HIMax, HIMatrix and SILworX are registered trademarks of HIMA Paul Hildebrandt GmbH + Co KG

HI

80

1 10

3 E

© b

y H

IMA

Pau

l Hild

eb

ran

dt

Gm

bH

+ C

o K

G