Case FBD - Premier Pas

First Steps
First Steps
User's Manual
7000931003 P11
CASE FBD Version 5.0

novaPro32 Version 5.0
CASE Prj Version 5.2
CASE HWC Version 2.41
This document replaces the previous versions

of First Steps. It describes the installation of
above mentioned program versions and is
subject to amendment without prior notice.
7000931003 P11 Sauter Systems 1

First Steps
2 7000931003 P11 Sauter Systems

First Steps
Table of contents 0
1 Installing CASE FBD/novaPro32........................................................................... 11
1.1 PC Requirements ........................................................................................... 11
1.2 Licensing ........................................................................................................ 12
1.2.1 General ................................................................................................... 12
1.2.2 Install the license..................................................................................... 12
1.2.3 Remove the License................................................................................ 14
1.2.4 Updating the License............................................................................... 15
1.3 Program installation ........................................................................................ 17
1.3.1 Update the licence................................................................................... 21
2 The first CASE FBD project................................................................................... 23

2.1 General........................................................................................................... 23
2.2 Fundamental procedure.................................................................................. 23
2.3 Interconnection between hard- and software .................................................. 24
2.4 Creating a new project.................................................................................... 25
2.5 Workbench ..................................................................................................... 29
2.6 Creating an AS ............................................................................................... 30
2.7 Starting CASE FBD ........................................................................................ 31
2.7.1 Creating a function plan........................................................................... 32
2.7.1.1 Programming of an AND-Function.................................................... 33
2.7.1.2 Programming of an OR-Function...................................................... 36
2.8 Creating an AS-Network ................................................................................. 37
2.9 Configuring a link to the AS-Network .............................................................. 38
2.10 Down-Load / testing of Programmes............................................................... 40
2.10.1 Down-Load of the Programme................................................................. 40
2.10.2 Programme test....................................................................................... 41
3 Project handling..................................................................................................... 43
3.1 Topology Wizard and Project-Directory-Structure ........................................... 43
3.1.1 Creating a new project............................................................................. 45
3.1.2 Editing an existing project........................................................................ 52
3.1.2.1 Create a Workbench or a PDBL ....................................................... 54
3.1.2.2 Configure connections...................................................................... 57
3.1.2.3 Create a new Workbench................................................................. 60
3.1.2.4 Edit the project topology................................................................... 62
4 Functions CASE FBD/novaPro32 ......................................................................... 65

4.1 Creating a PDB/PDBL .................................................................................... 65
4.2 Generate data with the Workbench................................................................. 66
4.2.1 General ................................................................................................... 66
4.2.2 Save Password ....................................................................................... 67
4.2.3 Save the Workbench for this project (*.dew) ............................................ 68
4.2.4 Defragment data base ............................................................................. 69

First Steps
0 Table of contents
4.2.5 Objects into the autostart group ...............................................................70

4.2.5.1 General.............................................................................................70
4.2.6 Configuration house address....................................................................72
4.3 FBD-Backup....................................................................................................74
4.4 Plant Device Table Local (BMTL) ....................................................................76
4.4.1 General ....................................................................................................76
4.4.2 Synchronisation of objects within the DPE-Browser .................................76
4.4.3 Synchronisation of house addresses (BmTConfig-Object) .......................77
4.4.4 Important notes ........................................................................................78
4.5 AS-Groups ......................................................................................................79
4.5.1 The Master/Slave-Group ..........................................................................82
4.5.2 Connections .............................................................................................84
4.5.2.1 Connections within an MS-Group......................................................84
4.5.2.2 Connections to an AS outside of this MS-Group ...............................85
4.5.3 House Addresses.....................................................................................88
4.5.3.1 Configuration ....................................................................................89
4.6 Programme Start .............................................................................................90
4.6.1 CASE FBD ...............................................................................................90
4.6.2 novaPro32 (IconMaker)............................................................................90
5 Installation of CASE Project ..................................................................................91
6 Installation of CASE HWC......................................................................................93

6.1 Program Installation ........................................................................................93
6.2 Starting CASE HWCs Trouble-Shooting mode ................................................93
7 Tips and Tricks .......................................................................................................95

7.1 Data back-up...................................................................................................95
7.2 Settings NT4 ...................................................................................................95
7.2.1 IBM-PC with EYSA290.............................................................................95
7.3 Creating a new project.....................................................................................95
7.4 Adjusting of existing projects ...........................................................................96
7.4.1 Convert of existing projects into the version 5 ..........................................96
7.4.2 Update of existing projects .......................................................................99
7.4.2.1 Starting the Update-Tool .................................................................100
7.4.2.2 Update the project data...................................................................101
7.4.2.3 Update the autostart group .............................................................102
7.4.2.4 Update the system environment (dse).............................................102
7.4.3 Migrating the Directory-Structure............................................................103
7.4.3.1 Migrating of an existing project (< Vers. 2.05) maintaining the existing
Directory-Structure..........................................................................104
7.4.3.2 Migrating (moving) of an existing project to the new Default-Project-
Directory-Structure..........................................................................114
7.5 Topology Wizard Debug mode ......................................................................115

First Steps
Table of contents 0
7.5.1 General ................................................................................................. 115
7.5.2 Starting in Debug mode......................................................................... 115
7.5.3 Description of the functions ................................................................... 116
7.6 CASE FBD.................................................................................................... 119
7.6.1 Still open points ..................................................................................... 119
7.6.1.1 General .......................................................................................... 119
7.6.1.2 Error at undo check-out for AS ....................................................... 119
7.6.1.3 Import of function plans .................................................................. 119
7.6.1.4 Maximum number of new objects within “DPE-Browser” ................ 119
7.6.1.5 Maximum size of the PDB .............................................................. 120
7.6.1.6 Miscellaneous ................................................................................ 120
7.6.2 Template function plans ........................................................................ 121
7.6.2.1 General .......................................................................................... 121
7.6.2.2 Template I/O function plans ........................................................... 122
7.6.2.3 Template control function plans...................................................... 122
7.6.2.4 New version of template control function plans .............................. 123
7.6.3 Import/export of “User Blocks“ ............................................................... 124
7.6.4 Simultaneous working with the Topology Wizard and Workbench ......... 124
7.6.5 Import of functions plans created in older versions ................................ 124
7.6.5.1 Import from pre-version dated 31.07.98 ......................................... 124
7.6.5.2 Import from version 1.0 and 1.1...................................................... 124
7.6.6 Working with more than one project ...................................................... 125
7.6.6.1 Creating an additional project......................................................... 125
7.6.6.2 Changing between projects ............................................................ 125
7.6.7 Semicolon “;” within AS ......................................................................... 125
7.6.8 Information about installed versions ...................................................... 125
7.6.9 Functionality Index ................................................................................ 126
7.6.9.1 Description of Functionality Index/ µProgram Index........................ 126
7.6.9.2 Handling of the Functionality Index................................................. 126
7.6.10 Length of one function plan ................................................................... 127
7.7 CASE Prj ...................................................................................................... 128
7.8 Licensing ...................................................................................................... 129
7.8.1 General ................................................................................................. 129
7.8.2 Delaying the expiring date of the licence ............................................... 129
7.8.3 License related error codes ................................................................... 129
7.8.3.1 Error code -1002 ............................................................................ 129
7.8.3.2 Error code 37 ................................................................................. 129
7.8.3.3 Error code -64 ................................................................................ 130
7.8.3.4 Error code -25 ................................................................................ 130
7.9 CASE HWC .................................................................................................. 131
7.9.1 General ................................................................................................. 131
7.9.2 CASE HWC and CASE FBD/novaPro32 ............................................... 131

First Steps
0 Table of contents
7.9.3 Routel ....................................................................................................131

7.10 Remote Access onto an AS Island, with CASE FBD / novaPro32..................132
7.10.1 Set-up: ...................................................................................................132
7.10.2 Configuration of the Router side modem: ...............................................132
7.10.3 Set-up of the PC-side: ............................................................................135
7.10.4 Operation: ..............................................................................................135
8 Method of working................................................................................................137
8.1 General .........................................................................................................137
8.1.1 Introduction ............................................................................................137
8.1.2 Data structure ........................................................................................137
8.1.3 Contents of the Plant Device Table (BMT/BMTL) ...................................138
8.1.4 Default-Project-Directory-Structure.........................................................139
8.2 Multi-User Mode ............................................................................................141
8.2.1 Data located on a sharable directory (Master-PC)..................................141
8.2.2 Data on a file server ...............................................................................142
8.2.3 Network access......................................................................................142
8.2.3.1 Drive Mapping.................................................................................142
8.2.3.2 "UNC" (Unified Name Convention)..................................................142
8.3 Method of working .........................................................................................143
8.3.1 The PCs are connected with each other all the time (Multi-User mode) .143
8.3.2 The PCs are not always connected to each other (disconnected mode) 144
8.3.3 Tips for large projects.............................................................................147
8.3.3.1 Preparation of work.........................................................................147
8.3.3.2 Working method: Suggestion 1 .......................................................147
8.3.3.3 Working method: Suggestion 2 .......................................................148
8.3.4 Migrating (moving) of an existing project to another PC (PC1 to PC2) ...149
8.3.4.1 Maintaining the existing Directory-Structure on PC2 .......................149
8.3.4.2 Different Directory Structure-Structure on PC2 ...............................149
8.3.5 System environment ..............................................................................150
8.4 Communication via Socket (DCOM) ..............................................................151
8.4.1 General ..................................................................................................151
8.4.2 Pre-condition..........................................................................................151
8.4.3 Required settings within the Registry .....................................................152
8.4.4 Required settings within the Topology....................................................153
8.4.5 Starting a project ....................................................................................154
8.4.6 Link information......................................................................................155
8.4.7 Check the Network connection...............................................................156
8.4.7.1 Configure the file HOSTS................................................................157
9 News and Improvements .....................................................................................159

9.1 CASE FBD ....................................................................................................159
9.1.1 New functions from Version 2.50 to 3.0..................................................159

First Steps
Table of contents 0
9.1.1.1 New DPE-System environment (*.dse)........................................... 159
9.1.2 List of improvements in Version 3.0....................................................... 160
9.1.4 New functions in Version 4.0 ................................................................. 162
9.1.5.1 Known bugs in Version 4.0............................................................. 163
9.2 CASE Prj ...................................................................................................... 166
9.2.1 New functions from Version 4.6 to 4.7 ................................................... 166
9.3 CASE HWC .................................................................................................. 172
9.3.3 New functions in Version 2.30 ............................................................... 172
9.4 novaPro32 .................................................................................................... 173
9.4.5.1 Known bugs in Version 4.0............................................................. 179

First Steps
0 Table of contents
List of icons and symbols
Keyboard operation
Wait
Diskette
Mouse operation
Single mouse click with left button
Single mouse click with right button
Double mouse click with left button
Double mouse click with right button
Description
Application
Information
Attention
Note

First Steps
Table of contents 0
Trademarks
Designer Trademark of Micrografx, Inc.
Micrografx Designer Trademark of Micrografx, Inc.
Media Manager Trademark of Micrografx, Inc.
Windows Trademark of Microsoft Corporation
Microsoft Office 97 Professional Trademark of Microsoft Corporation
MS Office Trademark of Microsoft Corporation
Microsoft Access 97 Trademark of Microsoft Corporation
Microsoft Office 2000 Trademark of Microsoft Corporation
Microsoft Word Trademark of Microsoft Corporation
Acrobat Reader Adobe Systems Incorporated
Pentium Trademark of Intel Corporation

First Steps
0 Table of contents

First Steps
Installing CASE FBD/novaPro32 1
1 Installing CASE FBD/novaPro32

1.1 PC Requirements
Remark
The program CASE FBD requires the following PC hard- and software pre-installed.
Caution
HW requirements:
PC:
Processor: Intel Pentium II or later
Working memory: minimum 192 Mbyte (recommended: 256 Mbyte)
Hard-disk: min. 1.8 Gbyte (for program, library and data)
Diskette drive: Internal 3½ “ 1.44 Mbyte (for the installation of the license)
CD-drive: for the installation
Ports: 1 mouse
1 printer
1 network
SW requirements:
Windows NT4.0(SP6a)/ Windows 2000/ Windows XP

Microsoft Internet Explorer 4.01 or higher

First Steps
1.2 Licensing
1.2.1 General
Warning
Licenses delivered since 01.02.2000 (Dat Code M2) can be used with Win9x, NT4,
Win2000 and Win XP.
Licenses delivered since January 2002 (Dat Code P1), will not have an expiry date
anymore and are valid therefore unrestricted time.
Warning
Floppy disk drives with USB-Interface or LS120 drives are not supported from the
licensing system.
1.2.2 Install the license
Application
The directory shall be created manually using windows explorer.
1. Insert the license diskette into drive A: (Attention: The diskette shall not be write
protected):
2. Start the licensing by executing (double click) install.exe.
3. In the field “License - Path” you select the directory where you want to install the
license. This directory can be located anywhere on the hard disk, but has to exist al-
ready. Use the button to select the directory.
4. Execute the licensing by pressing the button "Transfer-License"

First Steps
5. The successful program installation is prompted onto the screen.
Warning
Important! On each PC, only one license can be installed.

First Steps
1.2.3 Remove the License
Warning
The license should not be deleted manually from the hard disk, because the license will
be lost. Therefore, the license must be removed with the same license diskette as one
executed the licensing. Afterwards, the license can be used again for another PC.
If would like to make modifications at the partitioning of the hard disk, the license must
be first removed, since it is destroyed otherwise.
The removing is done in the same manner as the license installation, except that the
option „License to master disk“ must be selected. See also chapter 1.2.2 Install the li-
cense.
The correct license directory must be adjusted under "License-Path”.
The successful license transfer is prompted onto the screen.
If the license diskette was not adjusted yet (see chap. 1.2.4 Updating the License),, the
license on the diskette has possibly still the old expiration date. Thus with a renewed
installation, the license could not function any longer and when starting of a program the
error message
appear. This means that the expiration date is past. Now the license update must be
started (see chap. 1.2.4 Updating the License). Afterwards the license is functional
again.

First Steps
1.2.4 Updating the License
Because older licenses (DatCode < P1) contain an expiration date, they must be ad-
justed, this means the expiry date must be removed. This can be done on two different
methods.
1. Installation of CASE FBD or novaPro32 from version 4.0 SR2 removes the expiry
date of the installed license.
2. Execute the license update at the CASE FBD/novaPro32 program CD from version
4.0 SR2.
Execute the update:

1. Execute the program „LicUpgrade.exe“ within the directory “License_Upgrade“ on
the CD. The program find out the version and indicated onto the screen.
2. Start the update by pressing the button “upgrade“.
Now, a new file LIC3600.dll is copied on the hard disk. Thus the expiry date of the li-
cense is removed.
3. The upgrade is confirmed with the follwing message.
From version 5.0 of CASE FBD/novaPro32 and CASPrj 5.2, the update of the disk-
ette is ask.
4. Press the button „Yes“ to upgrade the license diskette, if the Dat Code of the license
diskette is before P1.

First Steps
Note
A second update of the license diskette or the installed license does not have effect
on the functionality of the license.
5. Now you must insert the license diskette into the floppy drive.
Afterwards press „OK“.
6. The successful upgrade is prompted onto the screen with the message „License
diskette - upgrade successful“. Close the window with the button „close“ and remove
the diskette from the drive.
Thus the Upgrade is successfully executed.

First Steps
1.3 Program installation

The procedure below reflects a first installation of CASE FBD and novaPro32. Depend-
ing on the PCs configuration, the installation process can vary (some additional steps
necessary).
In case you have already installed an elder Version, then you just do the installation de-
scribed under chapter 1.3 “Program installation”. The license and the already existing
project data are not affected.
Note:
• For an update installation, one has to use the same directory as for the first installa-
tion.
• We suggest to save all the project data before the installation of a new version
and freeze these data.
Important
Before the update installation, remove all EY3600 programs from “Windows Autostart”
and restart Windows again!
Installation
1. Make sure, that the license is installed see chapter 1.2 “Licensing”
Insert the program CD into the CD drive. After a few seconds, the following window
opens, respectively you execute the program setup.exe on the program CD:
Start the installation by

selecting „CASE FBD /
novaPro32 <Lan-
guage>„.
Please follow the instruc-

tions given by the installa-
tion program.

First Steps
Click on “Next“
Select the folder. For a first installation, the program suggest the following path:
C:\Program Files\Sauter\FBD_novaPro32\.
For an update installation, one has to use the same directory as for the first installation.

First Steps
Select the product to install.
Review the settings and click on

“Next“ to begin copying files.
Click on „OK“.

First Steps
Select the language of the template editor „List&Label“.
The successful program installation is prompted onto the screen.

In some cases the installation program is asking for a complete restart of Windows.
Click on “Finish“.
Note
Execute an update of your existing projects.
See chap. 7.4, “Adjusting of existing projects“.

First Steps
1.3.1 Update the licence
During the installation of CASE FBD/novaPro32, the license will be updated automati-
cally when it’s necessary.
In order to take away the expiry date of the licence, the installation program is replacing
the file lic3600.dll on the hard-disc with a new version from the CD
(please refer also to chapter 1.2.4 “Updating the License”).

First Steps

First Steps
The first CASE FBD project 2
2 The first CASE FBD project

2.1 General
This chapter shows, step by step, the creation of an “simple” project using CASE FBD.
The following pre-conditions apply:

• Installation of the Licence (chapter 1.2 “Licensing“)
• Installation of the required programmes (chapter 1.3 “Program installation“)
In order to down-load and test the function-block-diagram, also the following pre-
condition apply:
• Availability of an AS with novaNet-connection
• novaNet-communication with either EYS290 or Router EYZ291
• Operator-Panel EYT240
2.2 Fundamental procedure

1. Project engineering using CASE Project
2. Creating a project using CASE FBD
3. Data export into CASE FBD
4. Completing the programme within CASE FBD
5. Down-load of the data into the AS
In the following project named „Getting Started“ are only a few in- outputs used. There-
fore, the items 1 and 3 are not executed.

First Steps
2.3 Interconnection between hard- and

software
Using CASE FBD, one is creating the process specific software for the Automation-
Stations (AS) of a project.
The AS controls and supervises the process of the plants. The in- and outputs have their
individual addresses.
PC with communica-
tion device CASE FBD-Editor
Down-loading the pro-

gramme into the AS
novaNet
Automation-Station (AS)
Operating-Panel Plant
(EYT240)

First Steps
2.4 Creating a new project

The Topology Wizard supports the creation of a new project. The project structure as
well as all necessary files are created automatically. The project structure allows to store
the relevant data in a logical manner.
Start the Topology Wizard within the Windows Start Menu under
Start | Programme | EY3600 | Topology Wizard
Enter the project name

”Getting Started“.
Press the button “Next”.
CASE FBD as well as novaPro32 are supporting the simultaneous working on the proj-
ect of several users at the same time.
Therefore, the project is split into shared data (Sharable Data) and in local, individual
used data (Private Data).
The project “Getting Started“ will be created as a single user project.

First Steps
Within this window, the

shared data structure is
being created.
Up to the project name,

the individually required
project path can be en-
tered, if necessary (e.g.
D:\EY3600).
Press the button “Stan-

dard for empty directo-
ries”.
Press the button “Next”.
Press the button “Yes to all”.
The directories are being created.
In this window, the local

directory structure is being
created.
Up to the project name,

enter the same directory
structure as in the window
before „Sharable Data“
(e.g. D:\EY3600).
Press the button “Standard

for empty directories”.
Press the button “Next”.....
...... Press the button “Yes to all”.

The directories are being created.

First Steps
Select the language of the projects.
This selects the different Firmware-

Block-Libraries and templates.
It is not changing the programme lan-

guage. This is being selected upon
the programme installation.
The project and all necessary files are now being created.
This library consist of a great variety of

templates and pre-defined solutions.
Press the button “Yes”.
Now, the AS-Network (novaNet) can be created

automatically. Each individual AS must be integrated
within an AS-Network.

First Steps
Each address (e.g. in- / out-

puts) is automatically entered
into a so called “BMTable”.
Such an empty bmtable is
being created now.
Press the button “OK”.
The password database for

novaPro32 will now be cre-
ated.
The configuration of the connection (PC-AS) can

now be specified.
For the project „Getting Started“, we will do this
later.
Press the button “No”.
Now, the project can be started automatically.

First Steps
2.5 Workbench
After the creating the project, the workbench will be started. The workbench shows all
objects (AS, AS-Networks etc.) available within the project database. Via the work-
bench, these objects can be started, for working with them (e.g. working on a function
block diagram).
The workbench file can be found within the projects directory under ...\Private_Data\
*.dew (e.g. D:\EY3600\Getting Started\Private_Data\Getting Started01.dew).
Open this file using a double click on it.
The following window opens:
Window with the

files linked to this
workbench.
Property win-
dow of the se-
lected directory
or object.
Object browser
The object browser shows an “explorer”-view of the linked files.
System environment: contains the library

of firmware blocks, AS-types as well as
other necessary objects.
Local project database: here, the

individual project data are stored.
CasePrjLib: library with tem-

plates and solutions

First Steps
2.6 Creating an AS
Open the project folder by double-clicking or clicking on the + symbol.
Select the folder ”AS“.
Press the icon “New

MDBO” within the
symbol bar or via a
right mouse click and
“New DB Object”.
Enter a name for the AS within the next window.

Overwriting the default name with “AS 1”.....
...... Within the folder AS, a new AS object has been created.

First Steps
2.7 Starting CASE FBD

Before drawing a function plan, the respective AS has to be opened.
Open the AS 1 by double-clicking it

within the browser.
Opening the AS for the first time, it has

to be defined as a Single AS or an “AS
Group”.
Define this AS as a “Single-AS”.......
.....Press the button “OK”.
Now, the hardware

type of the AS is
selected.
AS-Type, Func-
tionality-Index and
AS-Address......
....... Afterwards, press the button “open FBD”.

First Steps
2.7.1 Creating a function plan
After opening the CASE FBD-Editor, the Overview Diagram is displayed. Within an AS,
this overview plan represents the most upper working level.
In order to achieve a well structured programme, it can be divided into several different
parts. These are called Overview Blocks.
The next picture shows an Overview Diagram.
IInserting of Online ob- Inserting of Func-

Blocks servation tion-Blocks
Connecting
Tools
Overview
Block
Function blocks can not be placed within the Overview Diagram (controllers, PLC-links,
I/O-Blocks etc.).
Open the Overview Block by double-clicking on it......
...... Now the inside of the Overview Block is displayed.

First Steps
2.7.1.1 Programming of an AND-Function
In the following example, an AND-Function is programmed.
Function:
Switch 1 Switch 2 The lamp is on, when switch 1
Lamp and switch 2 are activated.
Inserting a new function block.
Select the category (Logic).
Select Firmware-Block “AND“ and

press “OK“.
The selected Firmware-Block can be

placed now on the workspace of
CASE BFD-Editor (”Insert“ is dis-
played on the cursor).
For this example, hardware-inputs (switch 1 and 2) as well as the hardware-output

(lamp) are missing.
• Select a new Firmware-Block (category Inputs/Outputs).
• Select Firmware-Block “BI“ and pull it, pressing the left mouse-button, onto the work-
space. (The Firmware-Block selection window remains open).
• Select Firmware-Block “DO“ and pull it, pressing the left mouse-button, onto the
workspace.
• Place , in the same manner, the Firmware-Block ”f8_com” within the category “Sig-
nal Formatting onto the workspace.

First Steps
Move the Firmware-Blocks on the workspace until it matches the following diagram:
The links in-between the Firmware-Blocks must be created:
Select the connector “fC1“ of

the Firmware-Block “BI“ as
well as the connector „fB1“ of
the ”AND“ block.
The button for “Single-link” is

visible now on the symbol bar.
Press the button “Single-link”.
Link the other connectors as following:

• BI fC2 AND fC2
• AND fC f8_com fCI
• f8_com cC DO cB

First Steps
An address must be assigned to the I/O-Blocks. This address corresponds to the re-
spective hardware input (terminals).
Select the Firmware-Block “BI“,

press the right mouse- button and
select “Properties”.
Enter 52 into the field “MFA”.
Proceed as above for the block

“DO” but enter 32 into the field
“MFA”.
A comment can be entered into the field “Comment”.

First Steps
2.7.1.2 Programming of an OR-Function

In the following example, an OR-Function is programmed.
Function:
The lamp is on, if switch 3 or switch 4
Switch 3 is activated.
Switch 4 Lamp
Place a Firmware-Block
“OR”, category “Logic”, below
the already existing AND-
Function.
Place a “f8_com” and a “DO”
next to it.
The Firmware-Block “DO“

gets the address 33.
Link the other connectors as following:

• BI fC3 OR fC1
• BI fC4 OR fC2
• OR fC f8_com(2) fCI
• f8_com(2) cC DO(2) cB

First Steps
2.8 Creating an AS-Network

A project can consist of several physical AS-Networks (novaNet). Therefore, these net-
works have to be created and the respective AS assigned to the appropriate networks.
Close the CASE FBD-Editor and change to the Workbench. Open the project folder and
select the folder AS Nets.
Within this folder, an AS-Network is already existing.

This AS-Network has been created automatically during the
creation of the project.
Open this object by double-clicking......
......... Press the button “Add”.
Select the AS 1 and un-select “Com-

mon“.
Press the button ”OK“.
Now, the AS 1 is assigned to the

ASNet1.
Close the AS-Network.

First Steps
2.9 Configuring a link to the AS-Network

Before down-loading the programme into the AS, a link has to be configured for each
AS-Network.
Close the CASE FBD-Editor and the Workbench.
Open the Topology Wizard and se-

lect the project “Getting Started“.
Press the button “Next“......
..... Select “Configure Connections”

and then press the button “Next”.....
Press the button “New”.......
..... Select as a new Device

“novaNet291“.
Enter a name for this device.

Complete the empty fields.
Check the COM-Port and the settings of
the baud-rate.
Press the button “OK“.
This device can also be used for other

projects.

First Steps
Under AS Network, select:
“AsNet1“.
Select under via : “EYZ291“.
Enter a name in the field Con-

nection: “Getting Started AsNet1
via EYZ291“.
Press the button “Save Connec-

tion”.
Press the button “Finish”.
Now, the link onto AsNet1 is configured.
Open the workbench again.....
......Open the AS 1 and the CASE FBD-Editor

again.

First Steps
2.10 Down-Load / testing of Programmes

In the following chapter, the just created programme is down-loaded to the AS and the
function is tested.
2.10.1 Down-Load of the Programme

First check the correct connection of novaNet and the communication device (EYS290,
EYZ291).
Select the function Program | Download

within the menu File.
There are the following options for the down-load:
AS Initialisation With this option the AS is initialised before the download.
Reset Counters With this option all counters are reset. Without this option all
values are maintained (also after AS initialisation).
Reset HRC and Tt With this option all hours-run counters and totalisation values
are reset. Without this option all values are maintained (also
after AS initialisation).
Time Programs With this option the time program prepared in novaPro32 is
also sent (also after AS initialisation). Without this option all AS
time programs are maintained. If an initialisation is executed
the AS time program is deleted.
Calendar With this option the calendar prepared in novaPro32 is also

sent (also after AS initialisation). Without this option the AS
First Steps
calendar is maintained. If an initialisation is executed the AS
calendar is deleted.
XS/L With this option all set points (XS) and limit values (L) from I/O-
blocks, adjusted in the FBD are sent into the AS. Without this
option all values are maintained (also after AS initialisation).
FBD Program With this option the complete program is sent into the AS.
Increased Download With this option the download with message priority 9 is exe-
Message Priority cuted and thus with a higher priority than the spontaneous
messages of the AS to the PC (MP 8). Without this option
message priority 5 is used.
Select the required options and press the button “OK“.
During the download, a window showing the current progress is prompted.
Press “OK“ when the download is finished.
2.10.2 Programme test

After a successful down-load, the programme can be tested online.
Click on the icon “Online observation“.
Activate the switch 1 and switch 2 (in-

put 1 and input 2 of address 52, termi-
nals 46 and 47 at a AS nova220).
The conditions of
the connectors
are indicated with
blue numbers.

First Steps

First Steps
Project handling 3
3 Project handling
3.1 Topology Wizard and Project-
Directory-Structure
The Topology Wizard supports the creation of a new project.
The Default-Project-Directory-Structure also supports the Windows main directories

structure with “Program Files” and “My Documents” to better support regular backups of
all your own documents and projects. It also divides the Project files into Private and
Sharable files, to support network installations, where sharable files are to be located on
a file server.
The Topology Wizard supports the set-up of Dial-Up-Connections (installation and

configuration of modem connections for remote access) and of the LAN set-up (set-up of
the DCOM connections between and allocation of the Event-Publisher and HDB-Server
Modules to the different PC’s) and of any combination of these options.
Note
The Topology has to be applied for each individual PC. In a network installation each
individual PC has to be configured with the Topology Wizard, even if the *.ntp-file and
the program files and some of the data are located on a file server!

First Steps
3 Project handling

First Steps
Project handling 3
3.1.1 Creating a new project
With the Topology Wizard, it is now possible to create a whole project automatically
(PDB, PDBL etc.).
For the set-up of a new project, we strongly recommend to use the new Default Direc-
tory Structure shown above!
The advantages are:

• The support of the Windows main directories structure with “Program Files” and
“My Documents”. This simplifies regular Back-Up's of the PC, since all data (of all
programs) which are not included on program CD's (and therefore are the ones to
regularly back-up) are within one directory “My Documents”.
• The division of the EY3600 Project Files into Private and Sharable files, which
support network installations, where sharable files are thought to be located on a
files server. Under Sharable_Data, the files are unique into a project and acces-
sible for all PC’s in the project. Under Private_Data are local, individual used data
for each PC.
New Projects are created with the Topology Wizard, which very much supports the new
Default Directory Structure.
1. Open your Topology Wizard “topologyWizard.exe or

Start Programs EY3600 Topology Wizard:
Enter your Project Name (max. 24 Char.) and click "Next".

First Steps
3 Project handling
2. The following dialog appears:
The entry in the first line is showing your default project path. Only if required for a
particular reason, change it to the path, where your sharable data should go.
See chap. 8.2.3 “Network access“.
Normally (for a new, single PC installation) do not change this path!

First Steps
Project handling 3
Click on "Standard for empty directories" which will enter all the remaining directo-
ries, as sub-directories to the first one:
then, click on "Next"
3. And you will be asked weather the folders should be created (if they don't exist al-
ready):
Confirm with "Yes to all".

First Steps
3 Project handling
4. Repeat the same procedure for the Private Data:
Click on "Next", "Yes to all"
5. Select the language of the projects. This selects the different Firmware-Block-
Libraries and templates. It is not changing the programme language. This is being
selected upon the programme installation.
6. The project is created automatically.

The system environment (*.dse) of the corresponding language is copied from the
template folder (Factory_Data) into the project folder (...\Private_Data\System\).

First Steps
Project handling 3
7. The system environment is linked into the project.
The PDB is created.
The PDBL is created.
The project topology is saved.
The autostart objects are linked.
8. You are asked if you want to link the CASE-Library. This library consist of a great
variety of templates and pre-defined solutions.
Click on “Yes“ and select a library.
9. The Workbench is saved.
10. Now, an AS-Network (novaNet) can be created automatically.
In normal case, the AS-Network will be created by the export from CASE Prj.

First Steps
3 Project handling
11. If you chose “Yes“, confirm the next asks.

Afterwards, you are asked to configure a connection to the created AS-Network.
If you chose “Yes“, go to chap. 3.1.2.2 “Configure connections”.
12. You are asked if you want to start the project.
If you chose “Yes“ the project is started.
13. By first opening, you will get the following messages:
Press “OK” and the plant device table (BMT) will be created.
Press “Yes”.

First Steps
Project handling 3
14. The workbench opens.
To create your AS-Network, your AS-Stations etc., confirm the manual „CASE
FBD Editor“, 7 000866 00X.
Afterwards, continue with the Topology Wizard to configure connections.

See chap. 3.1.2.2 “Configure connections.

First Steps
3 Project handling
3.1.2 Editing an existing project
Open the Topology Wizard “topologyWizard.exe” or

Start Programs EY3600 Topology Wizard:
Select the project:
Click on “Next”.
You can select one of the projects registered on this PC.

If you can’t select the project (e.g. project copied from another PC), you can select a
ntp-File with the “Browse” button.
Note
You can open the ntp-File also directly with a double click within the Windows-Explorer.

First Steps
Project handling 3
The following window is opened:
You can select the most important functions of the Topology Wizard directly.
• Create a Workbench or a PDBL

- To create a new Workbench (new workstation).
- A PDBL can be created automatically.
• Configure Connections
- Direct jump to the configuration of connections
• Create a new Workbench

- Based on an existing PDBL a new Workbench is created
• Edit the project topology

- Access to all functions of the Topology Wizard

First Steps
3 Project handling
3.1.2.1 Create a Workbench or a PDBL

With this function you can create further workstations (PC’s within the network) and fur-
ther local project data bases (PDBL’s).
Note:
Don’t create a new PDBL with the Workbench anymore, use the functions of the
Topology Wizard instead.
After selecting this function and the button “Next” the window for Private_Data appears.
If you create a new Workspace, push “Standard for empty directories”.

First Steps
Project handling 3
If you copied a project (with existing structure) select each folders where your data is
stored with the Button :
e.g.:
After you specified all folders, click “Next”.
Select the language of the projects. This selects the different Firmware-Block-Libraries
and templates. It is not changing the programme language. This is being selected upon
the programme installation.
• The PDBL is created automatically.

The system environment (*.dse) of the corresponding language is copied from the
template folder (Factory_Data) into the project folder (...\Private_Data\System\).
The system environment is linked in the workbench.
The PDBL is created.
The Project topology is saved.
The Workbench is saved.

First Steps
3 Project handling
You are asked if you want to link the CASE-Library. This library consist of a great variety
of templates and pre-defined solutions.
Click on “Yes“ and select a library.
14. The Workbench is saved.
You are asked if you want to start the project.

If you chose “Yes” the created workbench is started.

First Steps
Project handling 3
3.1.2.2 Configure connections
On this page, you have to configure your connection to your AS-Network:
E.g. for a standard EYS290 connection:
First define your connection device by clicking on "New"...
Choose "novaNet290" and confirm with "OK":

First Steps
3 Project handling
Enter the physical address of your EYS290, your PC address desired (e.g. 31877)
and a name for this device (e.g. A290_1) (this device with its name may be used for
other projects on the same computer):
(Tip: If you don't know the physical location of your EYS290, you can check the
coding on the card or go into a DOS-Window, Enter "Debug", then "dc800:0000". If
the return contains something like "2SYE B09", it's your card. Try other possible ad-
dresses like d800 if it isn't, until you find it.)
then click "Save" and "OK" (you have to click "Save" first, there is a known bug)
E.g. for a novaNet-Router EYZ291 connection:
Define your connection device by clicking on "Neu..." (New...)
select "novaNet291" and click on "OK"
Enter your the baud rate of the novaNet-Router concerned, the COM-Port number,
the PC-Address desired and a name for this connection:
Please make sure, that the chosen baud rate is also set at the novaNet-Router!

First Steps
Project handling 3
then click "Save" and "OK" (you have to click "Save" first, there is a known bug)
E.g. for a Modem connection:
Select your modem (if there isn't a modem in the list, install it first on your PC) from
the drop down list ("via"):
E.g. for a DCOM (Network) connection:
Select DCOM from the drop down list ("via") and proceed as in "modem connection"

First Steps
3 Project handling
Then select the AS-Network concerned and give this connection a name.
Use the Project Name to name the connection e.g.:
Click "Save Connection" and "Finish". You have to click "Save Connection" first, there is
a known bug.
3.1.2.3 Create a new Workbench

With this function you can create a new Workbench based on an existing PDBL. This
could be necessary if you want to link a new system environment or if you are unable to
start the Workbench anymore.
Chose the system environment you want to work with:

First Steps
Project handling 3
Chose the PDBL.
Save your workbench file *.dew.
You are asked if you want to start the project.

If you chose “Yes” the created workbench is started.

First Steps
3 Project handling
3.1.2.4 Edit the project topology

With this selection you have access to all functions of the Topology Wizard.
Sharable Data settings:
Private Data settings:

First Steps
Project handling 3
Configuration of the HDB-Server:
Click on “HDB-Server konfigurieren” (Configure HDB-Server):
Specify here via which PC you want to access the HDB data of the available AS net-
works.

First Steps
3 Project handling
Configuration of the connections:

First Steps
Functions CASE FBD/novaPro32 4
4 Functions CASE FBD/novaPro32

4.1 Creating a PDB/PDBL
With Version 3.0 Topology Wizard has been considerably enhanced. It is now possible
to create a whole project automatically. A few other features have been improved as
well.
Note:
Don’t create a new PDBL within the workbench, make use of the functions of the
Topology Wizard.
Caution
With Version 3.0, the PDBL-name must be unique into the project.
See chapters 3.1.1 “Creating a new project“ and 3.1.2.1 “Create a Workbench or a
PDBL“.

First Steps
4.2 Generate data with the Workbench

4.2.1 General
The workbench starts all linked files (System environment, PDBL, Autostart objects)
Similar the Windows Explorer, the Workbench shows all objects (AS, AS-Networks etc.)
available within the project database. Via the workbench, these objects can be started,
for working with them (e.g. working on a function block diagram).
The workbench file can be found within the projects directory under
...\Private_Data\*.dew.
Open this file using a double click on it.
Path indication of the cor-

responding data base.
PDBL PDB
Window with the
files linked to this
workbench.
Property window of the se-

Object browser lected directory or object.

First Steps
4.2.2 Save Password
Note
The password can be disabled on project start-up by activating the „Kennwort
speichern“ (save password) in the workbench file. This will prevent the password prompt
on workbench start-up.
File | Properties
Save password

First Steps
4.2.3 Save the Workbench for this project (*.dew)

File | Save
or with the button in the Toolbar.

First Steps
4.2.4 Defragment data base

With version 4.0, you have the possibility to defragment data bases (PDB, PDBL, DSE).
Those, all deleted objects from the selected data base will be take off and the file size
will be reduced.
Select the correspond-

ing PDBL
In Menu Administrator, you will get the following possibilities.
Defragment the selected

data base (DSE, PDBL).
Defragment the correspond-

ing (PDB) of the selected
data base (PDBL).
Defragment the selected

PDBL and the correspond-
ing PDB.
After the defragmentation, you must restart the workbench.

First Steps
4.2.5 Objects into the autostart group
These objects will be started automatically when the workbench (*.dew) is starting.
Note
• The Topology Wizard add the objects automatically into the autostart group!
• Actualise missing autostart objects in existing projects with the Update-Tool.
See chap. 7.4.2.3 “Update the autostart group“.
4.2.5.1 General
Select the object and press the right mouse button.
Execute ”Insert in Autostart“.

First Steps
You can observe the order in which the parts are brought into the autostart group under
Information | Autostart objects.
The entry BMT must be at the top.
The following objects will be opening automatically:

• “BMT“ under “Plant devices”
• “StandardFilter“ under “Filter“
• “Groups“ under “Common Groups”
• “Password“ under “System“
• “Logbook“ under “System“
By the first opening, you will get the following messages:
Press ”OK” and the plant device table (BMT) will be created.
Press ”Yes” and the password data base will be created.

First Steps
4.2.6 Configuration house address
Note
Configuration the house addresses of AS-Groups, see chap. 4.5.3, “House Addresses“.
Open the workbench.

Open the folder ”System“ into the project.
Execute ”BMT Config“ (BmTConfig-Object) with double-
click.
Define the distinction of the

house address.
Press the button ”House address
configure“.
Create the structure of the house address.
Select in above Window 4 components.
The sum of the number of characters must

be 24.

First Steps
These settings should correspond with the settings in CASE Prj, but only from the
level “IFP“ (Information focus point) to the level “Plant“!
See also manual “Case Project User“, 7 000839 00X, Chap. 5.2.7.2.
The parameter “Installation com-

ponent“ defines, all plants are
listed within novaPro32 (Address
List).
In these example, all house ad-

dresses of an plant will be shown
within one folder of the address
selection novaPro32.
Afterwards, press the button “Insert in BMT/BMTL“. The configuration will be saved into
the BMT.
Warning
You must have a connection to the BMT.
Please check in the manual “novaPro32 Installation”, 7 000915 00X, Chap 5.2 for the
meaning of the parameters ”Installation component“ and ”Limit per installation list”.

First Steps
4.3 FBD-Backup
In some cases, the FBD couldn’t save the data correctly into the PDBL. Because of this,
you can lost some FBD-data.
That’s why, the FBD has a Backup functionality.
Open the workbench and select “Properties” in the “File”

menu bar.
You see the observed server under the “Backup

options”.
With “Add”, you can add additional servers into

the backup functionality.
You can delete a selected entry with the button

“Delete”.
If “No server” is chosen, no backup is activated.
If “All server” is chosen, all activities are ob-

served.
All in the backup observed actions will be stored in a file with the extension *.lbk.

First Steps
If a backup be there, you will be-
come a message when you start
the workbench.
Only the backup object will be indicate into the browser (e.g. an AS).
Select the object and you can choose different options with the right mouse button or
“Backup” within the menu “Browser”.
• With “Display Origi-

nal”, you can open
and check the origi-
nal state of the ob-
ject.
• With “Display
Backup”, you can
open and check the
backup state of the
object.
Afterwards, you can select which version has to be use by the next start of the work-
bench.
• ”Use Original“ using the original state.
• “Use Backup“ using the backup state.
These two options, you chan choose only one time and are definitely.
Close the workbench. Restart the workbench and you work in a good condition.

First Steps
4.4 Plant Device Table Local (BMTL)
4.4.1 General
From version 3.0 of CASE FBD, a so called "Plant Device Table Local" (BMTL) is cre-
ated when the PDBL get started. This allows an easy and correct simultaneous working
of several people at the same project.
Access overview:
novaPro32
Sharable Data Private Data CASE Prj
BMT BMTL
PDB PDBL
CASE FBD
There are two possibilities to synchronise the BMTL with the BMT.
1. Synchronisation of objects within the DPE-Browser.

2. Synchronisation of house addresses (BMTConfig-Object).
4.4.2 Synchronisation of objects within the DPE-

Browser
Insert or return within the DPE-Browser AS-Objects from the PBDL into the PDB (Syn-
chronisation | “Publish“, “Return“). Simultaneously, all connected house addresses with
these AS will be synchronise with the BMT. All disconnected house addresses will be
available within the BMTL.

First Steps
4.4.3 Synchronisation of house addresses (BmTCon-
fig-Object)
Execute in the DPE-Browser “BMT Config“ within the System folder.

The following windows opens:
Configure the house address. See

chap. 4.2.6 “Configuration house ad-
dress“.
Select “AS-Synchro“, the following window appears:
In BMT-View:
Select an AS or an AS-Net.
Press the button “Read“.
All connected house addresses with these
AS will be read from the BMT into the BMTL.
In BMTL-View:
Select an AS or an AS-Net.
Press the button “Publish“.
All connected house addresses with these
AS will be published into the BMT.
No synchronisation between PDB and PDBL!
BMT-View BMTL-View

First Steps
Select House Address Synchro., the following window appears:
In this window, you see all discon-

nected house addresses.
In BMT-View:
Select a house address.
Press the button “Borrow“. The
house address will be transfer into
the BMTL.
In BMTL-View:
Select a house address.
Press the button “Return“. The
house address will be transfer into
the BMT.
You can delete individual house

addresses with the button “Delete“.
No synchronisation between
PDB/PDBL.
BMT-View BMTL-View
4.4.4 Important notes
• If you make a synchronisation between BMTL and BMT, you must have a connec-
tion to the BMT (PC-Network) !
• A disconnected house address can’t be published into the BMT, when this house
address is connected to another AS within the BMT. Before, the original AS must be
“Return” into the PDB.
• If an AS is published within the DPE-Browser (“Publish”, “Return”), the AS can’t be

after published with the BmTConfig-Object. The AS must be published within the
DPE-Browser.
• A deleted (not connected) house address must be return into the BMT and borrow
into the BMTL (BmTConfig-Object). After that, they can reselect within the FBD.

First Steps
4.5 AS-Groups
Using the functionality “AS-Groups”, the efficiency of the engineering can be increased
dramatically.
The following pre-conditions apply for a group:
• identical programmes
• identical AS-Types
The following diagram shows an example for AS-Groups:
AS-Group 1
(North) AS
Room 1.01 Room 1.02 Room 1.03 Room 1.04 Room 1.05
Office 1 Office 2 Office 3 Office 4 Office 5
Room 1.11 Room 1.12 Room 1.13 Room 1.14 Room 1.15
Chief Office 6 Office 7 Office 8 Office 9
AS-Group 2
(South)
The shown floor is split into 2 groups (north and south). For each room, one AS is used.
A new object is created for each group

within the browser in the folder “AS”.
Upon opening the AS-Object for the first
time, it has to be defined as an AS-Group.

First Steps
After this definition, the following window is prompted:
Address of the AS-Group: Insert a new AS

(1-3071) (Master) as a
(one address per AS- group-member.
Group)
List of all group-

members

First Steps
If a new AS has to be added to this group, then press the button “Insert Master”.
AS-Name: AS-Address:
e.g. room number (0-28671)
(1.11) Coded on AS with DIL-Switches
MS-Group name:
e.g. room name
(Office CEO)
MS-Address:
(1-3071)
(one address per
MS-Group)
Caution
The AS-Group address and the master address must be different and unique within a
AS-Network and preferably within a project (1-3071).
Example for a range of addresses:

• AS-Group addresses 1-99 (one address per AS-Group)
• MS-Addresses 100-3071 (one address per MS-Group)

First Steps
4.5.1 The Master/Slave-Group

In addition, there is the possibility to create Master/Slave-Groups within the AS-Group.
This functionality is used when a flexible room size is required and the room is build of
several segments.
AS-Group 1
MS-Group 1 MS-Group 2
Master
R1.03 R1.04 Slave

R1.01 R1.02 R1.05
Secretary Purchase
Room segment
Chief Marketing
R1.11 R1.12 R1.13 R1.14 R1.15
MS-Group 3 MS-Group 4
AS-Group 2
In diagram, the room “Purchase” is build of 3 room-segments. Each of these segments

has its own AS. The AS in room-segment R1.03 is defined as Master. The AS of room-
segment R1.04 and R1.05 are defined as Slaves and are assigned to the Master.
Therefore, the office “Purchase” represents a MS-Group with 1 Master and 2 Slaves.
Remark:
Each MS-Group has to have one Master and the number of Slaves can be 0 - n.

First Steps
The Master/Slave-Configuration is done within the window AS-Group:
A MS-Group is created automatically as soon as, by using the button “Insert Master”, a
new Master is created. Each Master is automatically a MS-Group.
To create a Slave, select the respective Master within the “List of objects” and press the
button “Insert Slave”.
If the room sizes are changing, then the Slaves can be moved by “drag and drop” into
an other MS-Group.
In order to convert a Slave to a Master, select the Slave and press the button
“Slave Master“. In the same manner, a master can be converted into a Slave.

First Steps
4.5.2 Connections
There are two kinds of connections:
• Connections within an MS-Group
• Connections to an AS outside of this MS-Group
4.5.2.1 Connections within an MS-Group

The connections within the same MS-Group are all AS-AS connections and are defined
within a separate window.
The required links are then created automatically within the function-plan.
Press, within the window AS-Group the button

”MS Group Template“.
Enter the max. number of Slaves needed

within a MS-Group.
Outputs are defined by pressing the button

“Add”.
Each output (red ball) is created automati-
cally, within the Overview-Diagram, as an
output (Master) and input (Slave).
A check can be done within the firmware

block “Slave” in the function plan. This block
shows the status of the AS (Slave/Master).
Change to ”Slave“.
Outputs of the Slave are defined by pressing

the button “Add”.
Each output (blue ball) is created automati-
cally, within the Overview-Diagram, as an
output (Slave).
The number of inputs (Master) depends on
the max. number of Slaves.

First Steps
Therefore, the following connectors where created within the Overview-Diagram:
4.5.2.2 Connections to an AS outside of this MS-Group
4.5.2.2.1 Common-Connections
Common-Inputs:
Common-Inputs are created within the Overview-Diagram. The connection is available
for all AS within the AS-Group.
Common-Outputs:
Within AS-Network, a symbolic

name is created for each
Common-Output.
Afterwards, open the respective AS-Group.
Common-Outputs are only created on Masters.

Select the required Master.
Click onto “Common Connection“.

First Steps
Press the button “New”
Enter a connection name. This connection will

be created automatically in the Overview-
Diagram (right-hand side).
Press the button “Assign”.
Now, for the selected Master, the connection

can be assigned to a Common-Variable.
If necessary, select the next Master within

the AS-Group and press the button “Com-
mon Connection”.
Select the “Identifier” and press the button

“Assign”.
This connection can be assigned to the next
Common-Variable.

First Steps
4.5.2.2.2 AS-AS Connection
AS-AS connections are first created within the Overview Diagram. The connection is
available for all AS within the AS-Group.
Create an identifier on the edge connector

within the Overview Diagram and define it
as an Interface. This connection will be
marked in green colour.
Change into the AS-Group.
AS-AS connections are only assigned to a Master-AS.

Select the required Master and click on “AS-AS Connection”.
Select the identifier (in- or outputs).

Press the button “Create Connection” and estab-
lish the link to the appropriate AS.
For further information see manual „CASE FBD

Editor“ 7 000866.
If required, select the next Master within the

AS-Group and create further connections in the
same manner by pressing the button “AS-AS
Connections”.

First Steps
4.5.3 House Addresses

The house address is made up of a fixed and a variable part for members of the AS-
Group.
The fixed part has to be entered for each in- and output firmware-block using
CASE FBD. The variable part is given by the member of the AS-Group.
The combination of fixed and variable part is forming the complete house address for
the I/O Firmware-Block of each member of the group.
Variable part
member AS- Fixed part
Fixed part Group FBD: I/O-
AS-Group Block
GB02 +S101 ASA1
=R1.01
=R1.02
=R1.03
GB02 +S101 RMTM01.I1
GB02 +S101 =R1.01 ASA1

GB02 +S101 =R1.02 ASA1
GB02 +S101 =R1.03 ASA1
GB02 +S101 =R1.01 RMTM01.I1

GB02 +S101 =R1.02 RMTM01.I1
GB02 +S101 =R1.03 RMTM01.I1
Resulting house Resulting house

address of the address of the
AS I/O-Block

First Steps
4.5.3.1 Configuration
Open the workbench.

Open the folder “System” within the project.
Start “BMT Config” by double clicking on it.
Enter the number of the required

“Distinctions” and press the but-
ton “House address configure”.
See also chapter 4.2.6

“Configuration house address“.
Enter the structure of the house address.

The sum of the number of characters must
be 24.
See also chapter 4.2.6 “Configuration

house address“.
Define the structure of the variable part of

the house address within the structure. The
variable part can consist of more than one
parts.
Press the button “OK“.

Afterwards press “Insert in BMT/BTL“.
Caution
After executing the function ”Insert in BMT/BMTL”, the structure of the house address
can not be changed anymore. There is only one structure possible per project !

First Steps
4.6 Programme Start

4.6.1 CASE FBD
The FBD-Editor has to be opened with the respective workbench (*.dew).
4.6.2 novaPro32 (IconMaker)

See manual, 7 000915 00X.

First Steps
Installation of CASE Project 5
5 Installation of CASE Project

See manual “Case Project User“, 7 000839 00X.

First Steps
5 Installation of CASE Project

First Steps
Installation of CASE HWC 6
6 Installation of CASE HWC

6.1 Program Installation
See manual “CASE HWC Operating manual“, 7 000825 00X
6.2 Starting CASE HWCs Trouble-Shooting

mode
Trouble-Shooting functionality’s (Inb_nova) are integrated into CASE HWC.
Starting CASE HWC with the command
“case_hwc”
is starting the program for the hardware commissioning as usual.
In order to get these Trouble-Shooting functionality’s available, the program has to be

started using the following command:
“case_hwc /ext”
A password is required at the start of CASE HWC in the extended mode. This password
can be modified within the program itself.
The following password is active after the first installation: 12345
Important
This extended functionality is meant for testing and Trouble-Shouting purposes only!
It is possible to change all parameters and structures of an AS within this extended
mode. These modifications are not transferred into the Project Data Base (PDB)! In fu-
ture, there will also be no technical way to integrate these information into the PDB!

First Steps
6 Installation of CASE HWC

First Steps
Tips and Tricks 7
7 Tips and Tricks

7.1 Data back-up
We advise to store the project data daily on a save place for back-up purposes. This
could be done on CD, a tape device, server or any other suitable device. It is recom-
mended to have at least the two last days work available as a back-up.
The easiest way to achieve a complete back-up is to save the complete directory “\My
Documents\project\”, which “project” is the name of the Project, including all subdirecto-
ries and files.
7.2 Settings NT4

7.2.1 IBM-PC with EYSA290
Using IBM PCs, you must edit the setting in the BIOS to support the EYSA290:
Under <ISA Legacy Recourses> <Memory Resources> <Speicheradressen>

(Memory addresses) the memory address, on witch the card A290 is configured, must
be set to “ISA Resource“.
7.3 Creating a new project

The new Topology Wizard is reducing the necessary steps creating a new project. For
more information see chapter 3.1.1 “Creating a new project“.

First Steps
7 Tips and Tricks
7.4 Adjusting of existing projects

7.4.1 Convert of existing projects into the version 5
The data of existing CASE of FBD projects must be converted first into the version 5.
You will get several error messages, if you try to open the Workbench, with project data
which are present in an older version.
Acknowledge all messages and afterwards, start the convert tool with Start | Programs |
EY3600 | Tools | Convert project.
You will get a list of all projects registered
on this PC.
Choose the corresponding project, select

the options and afterwards, press the but-
ton „convert“.
The following options are possible:
Convert Project Converts all files within the project directory (System envi-
ronment *.dse, PDB *.spf, PDBL *.lpf, Workbench *.dew).
Convert Library_Data Converts all existing libraries CasePrjLib*.lpf (Library-

PDBL), wich are located within the directory
\\Libraray_Data\.
Convert Factory_Data Converts all existing system environments *.dse, wich are

First Steps
Tips and Tricks 7
located within the directory \\Factory_Data\. You must exe-
cute this option only, if you created user-defined system
environments. With the program installation, automatically
new system environments are copied into the directory
\\Factory_Data\.
Options for original files • If no option is selected, the original files are copied
and with an extension *. V40 renamed.
• make ZIP-files: The original files are packed in a ZIP
file.
• delete original files: Deletes the original files, if they
were successfully packed.
Afterwards, the process of the

conversion is represented in a
window.
Close the window, if the conver-

sion is successfully finished.
Afterwards, open the Windows Explorer:

Move in your project the directory „Print_Server“
from „\\Sharable_Data\System“ to
„\\Private_Data\System“.
Note:
If you work in your project with several worksta-
tions, copy the directory „Print_Server“ on all
workstations.

First Steps
7 Tips and Tricks
Afterwards, open the project in the Toplogy Wizard.:
• Change the path entry under „Print Server“ with the button to
„\\Private_Data\Print_Server“.
• Press the button „Standard for empty directories”. Thus, the new directory „Copy of
Sharable“ is created.
Press the button “Next” and save the Topology-File.
The conversion of the project data onto the version 5 is completed. Proceed for the
remaining projects in the same way. Existing project data must at least in version 2.5 are
present.
Afterwards, execute an update for the existing projects, thus you have new firmware
blocks, firmware icons etc. available (see chap. 7.4.2).
Note
In a multi-user project at least one workspace must have a connection to the „Shara-
ble_Data“, so that also the global project data are converted.

First Steps
Tips and Tricks 7
7.4.2 Update of existing projects
With the Update-Tool, you have the possibility to update your existing projects very
easy.
Especially:
• Update the System environment (dse)
• Update the firmware block library and the AS-type library
• Update the Firmware-Icons
• Update of autostart objects
• Update of forms
• Etc.

First Steps
7 Tips and Tricks
7.4.2.1 Starting the Update-Tool
1. Start the workbench of your project.

2. Start the Update-Tool with with Start | Programs | EY3600 | Tools | Update project.
The following window appears:
The tool is structured in 3 main functions:

• Update the project data
• Update the autostart group
• Update the system environment (dse)
You can also choose the respective functions seperatly from each other.
With the option “Acces rights”, also for normal users the necessary read/ write accesses
are set.

First Steps
Tips and Tricks 7
7.4.2.2 Update the project data
For an update of the project data, the following options are possible:
Update project Update the project data in the selected language.
Update novaPro32 files NovaPro32 forms will be copied from Factory_Data in the
project.
Update FBD documentati- Update FBD documentation, incl. all files.

on (incl. files)
Select printer Simultaneously update of the documentation files and se-

lecting the printer.
Printer selection available The chosen Printer will be copied back to Factory_Data of
for system the selected language. Those, you have a pre-selection
for further projects.
Select printer only (FBD Select only the printer for the FBD documentation.
documentation)

First Steps
7 Tips and Tricks
7.4.2.3 Update the autostart group
Not existing objects in the project will be completed and inserted in the autostart group.
7.4.2.4 Update the system environment (dse)

For an update of the project data, the following options are possible:
Update system environ- Update the system environment into the selected lan-
ment guage.
Update firmware library Import the current firmware block library and firmware
icons within the system environment (dse).
Update AS type library Import the current AS-type library within the dse.
Update documentation Update the documentation folders within the dse.
Remarks
Select the options „Update system environment“ and „Update firmware library“, those
you have the firmware icons available for existing projects.

First Steps
Tips and Tricks 7
7.4.3 Migrating the Directory-Structure
Migrating an existing project to the new Toptree Wizard (and thus open it to the Dial-UP
and Network functions) can be done to a variable extend:
1. Maintaining the existing Directory-Structure (except print support files).

2. Moving all project files to the new Default-Project-Directory-Structure
and also
3. Partially moving the project to the new Default-Project-Directory-Structure

4. Setting up of any customised directory structure according to your particular re-
quirements.
Which option to apply depends on your project and your requirements:
1. For very much completed projects, which will not require Networking. This option is
the most simple one and therefore tends to create the least work and the least
problems.
2. This option is the choice of the future. You will be compatible with future installations
and you will be able to properly support networking.
However, moving of the total project needs considerable effort and is possible and
feasible only for projects that are not to big (contents of the PDBL’s have to be
moved into the PDB in order to make the project movable to another location and for
the novaPro32 pictures, all the background pictures have to be reassigned and for
all the buttons that link to another picture, the pictures to jump to have to be reas-
signed).
3. This is the compromise option. It applies the new structure where possible. It doesn’t
move the PDB, PDBL and it doesn’t move the novaPro32 pictures where they and
the buttons included are to numerous to be moved within reasonable time.
4. If you have particular requirements you may set-up any directory structure. Each
path is selectable as it was with the previous toptree tool.

First Steps
7 Tips and Tricks
7.4.3.1 Migrating of an existing project (< Vers. 2.05) main-

taining the existing Directory-Structure
The process is explained based on a sample structure as follows:

First Steps
Tips and Tricks 7
1. IMPORTANT: First save your entire project data (e.g. into a ZIP-file) !!
2. Open your Topology Wizard “topologyWizard.exe”:
Click on “Browse” and select

your existing Topology file
(*.ntp).
Click “Open”
Note
You can open the ntp-File also directly with a double click within the Windows-Explorer.

First Steps
7 Tips and Tricks
3. The following dialog appears:
4. Chose “Edit the project topology”. The following dialog appears:
For all empty entries, select the paths, where your data concerned is actually
stored, using the - button:

First Steps
Tips and Tricks 7
• For “Sharable Data Root”, select your project parent directory, in this example:
This Path will be applied for the function of "Standard for empty directories”.
• For “Background Pictures”, select the directory where your “*.emf”, “*.bmp” files
are stored, in this example:
• For “Filters, Groups”, where your filter and group files “Filters.dat”, “
EpsGroup.dat” are located, in this example:
• For “AS-Time-Profiles”, where your AS-Time-Profiles, e.g. “ ASNet2AS0.dat”

are located, in this example:

First Steps
7 Tips and Tricks
• For the "Print-Server" we compulsory have to create a new path, so we

click on
which will create this path entry and as well the entry for the "Temporary"-path,
within the project root directory that we have entered under “Sharable Data
Root”.
Within the "Print-Server" path we have to remove the “System\”, so that these
two lines (in this example) look as follows:
Now, as all the pathes are

set, your dialog box should
look equivalent to the one
of this example:

First Steps
Tips and Tricks 7
5. Click on "Next" and the following dialog will appear:
Click on "Yes",
6. Which makes the equivalent dialog for the non-sharable paths (Private Data) to ap-
pear:
• We have to modify the “Private Data Root” entry with our project root folder:

First Steps
7 Tips and Tricks
• And the “HDB-Server” entry with:
Now, as these paths are set

too, your dialog box for the
non sharable files should look
equivalent to the one of this
example.
At this point we have adapted our project to the new Topology Wizard what pathes
are concerned.
7. We now have to set-up the remaining parameters of the Topology Wizard:
So, click on "Next", and the following dialog will appear:

First Steps
Tips and Tricks 7
Click on “Configure HDB-Server“.
Specify here via which PC you want to access the HDB data of the available AS
networks.
8. Then click on “Next”, which will make the last page of the Topology Wizard to ap-
pear:

First Steps
7 Tips and Tricks
This page provides (for the selected project) the option to create the (multiple)
“Connections” to AS-Islands, each consisting of a:
• The Connection Name

• The AS-Network to connect to
• The connection device to use (e.g. A290, A291, Modems...)
As we are working with an existing project within this chapter, this page will be pre-
set-up, with the settings of the project selected (taken over from the “old” Toptree
file).
Use the Project Name to name the connection.
We have to select the Connection Device manually within “via”. In this example
“ A291_1”:

First Steps
Tips and Tricks 7
9. Now, everything is set and we click on “complete”.
We will be asked for the name to save the Topology file under:
and since we have made a back-up-copy of our project anyway, we use the existing
name and click “Save”...
“Yes”
10. Our project tree now looks still pretty much as before (press "F5" to update the
explorer display!):
11. Execute an update of the project data.

See chap. 7.4 “Adjusting of existing projects“.

First Steps
7 Tips and Tricks
7.4.3.2 Migrating (moving) of an existing project to the new

Default-Project-Directory-Structure
Please note:
This is a brief description only! It’s thought for expert users. We don’t recommend
this option, unless your are well familiar with the EY3600 software.
The description covers the migrating of the PDB/BMT-Data and the novaPro32-pictures.
1. Execute a conversion and an update of your project data.

See chap. 7.4 “Adjusting of existing projects“.
2. Make a back-up copy of your entire project data.
3. Check in all objects (AS-Net and AS) from your PDBL into the PDB.
4. Open your existing *.ntp file and create your new (Default-) Directory Structure and
connections as described in the chapter 3.1.2.4 “Edit the project topology”.
5. Save your *.ntp file at the new location (“...\Sharable_Data”).
6. Copy all subdirectories (\novaPro32, \System, \Temp) and its content from your ex-
isting directory-structure into the new one. According to the locations shown in the
schema of the "Default Directory Structure".
7. Create a new PDBL from your PDB using the Topology Wizard (please see also
chap. 8.1.4 “Default-Project-Directory-Structure“).
8. Now re-open each picture in novaPro32 from the new location, check the back-
ground picture from the new location and then save it using the "Save" menu option.
Check all calls for all your buttons and “reactions” on dynamic points with the new di-
rectory structures.
Check all Time profiles, protocols, HDB-files.
Note:
Also in a network installation, the .ntp file is common to all PC's involved and thus
has to be located on the file server (e.g. \...\Sharable_Data\.ntp)!

First Steps
Tips and Tricks 7
7.5 Topology Wizard Debug mode

7.5.1 General
Please note, that this is a brief description only! It’s thought for expert users. We
don’t recommend this option, unless your are well familiar with the EY3600 soft-
ware!
Operating errors can lead to data loss !
Using the Debug Mode of the Toplogy Wizard, you can repair or edit the *.ntp files, and
also the corresponding entries in the Registry file.
7.5.2 Starting in Debug mode

In order to get these Trouble-Shooting functionality’s available, the program has to be
started using the following command:
<Installationpath>\topologyWizard.exe /debug

First Steps
7 Tips and Tricks
7.5.3 Description of the functions

Select the appropriate *.ntp-File. The following window opens:
Using the Combo Box and the button “Delete the selected PC”, PC names can be de-
leted from the ntp file.
The “Project-ID can be edited by using the button “Edit Project_Id”.
Warning
A wrong Project-ID causes trouble with the BMT (Plant Device Table!

First Steps
Tips and Tricks 7
With button “Edit AS Nets”, one can perform various changes of AS nets of the selected
project.
• Edit name and Net ID of the selected net with button: „AS-Netz bearbeiten“.
• Add a new net to the Topology environment with the button „AS-Netz hinzufügen“
(Add AS Net). This should be done only for repair purposes. E.g.: the AS Net is not
visible in the connection list. A configuration of a connection is described in chapter
3.1.1 „Creating a new project“.
• Delete a selected AS Net from the Topology environment with button “Delete AS
Net”.
Warning
AS Net Name and AS Net ID must be equal to the corresponding entries in the
BMT (Plant Device Table) !

First Steps
7 Tips and Tricks
Using the button “Edit Projects” shows the projects being in the registry data base.
Button “Delete Projects” deletes the selected Projects.
Button “Show all ntp Files” will show all ntp-Files in the selected drives.
Button “Delete selected files” deletes the selected ntp-file..

First Steps
Tips and Tricks 7
7.6 CASE FBD
7.6.1 Still open points
7.6.1.1 General
All remaining errors are eliminated as soon as possible. We continue to deliver updates
whenever indicated.
7.6.1.2 Error at undo check-out for AS

By using the function undo check-out at the workbench (entering the AS into the PDB
without modifications), afterwards the BMTL must be updated.
• Borrow the AS again and open the AS with double-click.
• Select in the window “AutomationStation” in the menu “Special” the function “BMTL
update”. Thus the BMTL is compared and updated with the current FBD plan.
• Afterwards, the AS can be returned or further processed again.
7.6.1.3 Import of function plans

Import of function plans shall only be executed after opening an AS / FBD-Editor and
before any other modification.
7.6.1.4 Maximum number of new objects within “DPE-

Browser”
Up to 128 Objects can be created within DPE-Browser without any data exchange to the
PDB. All entries within DPE-Browser, such as Automationstations, ASNetworks, any
Folders etc., are considered as an object.
Unfortunately, there is no information prompted onto the screen yet, when the number of
128 objects is reached. The only reaction of the system is to accept no new objects
anymore.
The required data exchange is done automatically by applying the following actions for
any of the existing objects:
• “Borrow” / “Return” objects from PDBL to PDB or vice versa
• “Read current version”

First Steps
7 Tips and Tricks
7.6.1.5 Maximum size of the PDB

The PDB shouldn’t be larger than 200-250 MB (200-250 single AS)
(PII 333MHz, 128MB RAM). Otherwise, it is possible that is a very restricted operation
due to the run-time behaviour.
• Split up the project in sub-projects (SuperBMT for novaPro32)

or
• Work only local with PDBL’s
Contact us for further information.
7.6.1.6 Miscellaneous
• ASNet must be read, before one or more AS are “Borrow”.
• In function plans created in CASE FBD Version 1, edge connectors can not be re-
named, as long as they are connected. First one has to delete the connection, then
the edge connector can be renamed and the connection being re-established.

First Steps
Tips and Tricks 7
7.6.2 Template function plans
7.6.2.1 General
Since the version 2.0, template function plans are available. Using these templates in-
creases the efficiency of CASE FBD.
These template function plans are in a special PDBL named

CasePrjLib_xxxxxxxxxx_DE.lpf (xxxxxx = year month day). It is available on the System
CD and will be installed under Programpath\Library_Data.
This special PDBL has to be added to the

projects ”DPE Workbench“ using the menu
item Workbench New PDBL Link.
Select the respective (*.lpf).
The link will be shown in the workbench:

First Steps
7 Tips and Tricks
7.6.2.2 Template I/O function plans

With Version 4, the templates are integrated within the CasePrjLib and not in the system
environment any more.
These function plans can be used either:

• Manually, copying within the browser
• Automatically, exporting data from CASE Prj to CASE FBD
Choose the corresponding template (AS)

within the CasePrjLib and the folder “Tem-
plates AS”.
It gives templates for single AS and AS
groups.
Then this “AS” has to be pulled, while

pressing the left mouse button, onto the AS
folder of the project data (drag and drop).
This leads in creating a new AS with all I/O
blocks already defined.
7.6.2.3 Template control function plans

These function plans can be used either:
• Manually, copying within CASE FBD
• Automatically, exporting data from CASE Prj to CASE FBD
All template function plans are documented

in our letter sent 09.06.1999.

First Steps
Tips and Tricks 7
7.6.2.4 New version of template control function plans
From version CasePrjLib_990624_DE.lpf to CasePrjLib_990909_DE.lpf the following
changes where made:
Category Modification Affected FBDs

01 Setpoint addresses changed to AIA_Soft 01701100 Equitherm
02 Sequence modified all temperature control FBDs
02 Summer compensations set to 0 at control all control loops without
loops without cooling sequence cooling sequence
02 In the de-humidification mode sequence of all control loops with re-
the re-heater modified (MUX integrated) heater
For Version CasePrjLib_010615_DE.lpf the following changes where made:
• Various modifications on AS templates for CASE FBD version 4

• Templates AS integrated (single AS and AS groups)
• New categories “Solutions single AS” and “Solutions AS groups” to integrate com-
plete solutions.

First Steps
7 Tips and Tricks
7.6.3 Import/export of “User Blocks“

In order to share “User Blocks” with other people, all categories of “User Blocks” can be
exported respectively be imported.
This function can be found within the function plan editor, menu items Libraries Import
respectively Libraries Export.
Under Libraries Info, one can see the functionality index of each “User Block” cate-
gory.
7.6.4 Simultaneous working with the Topology Wizard

and Workbench
Warning
The Topology Wizard and the Workbench are not allowed to be open at the same
time!
7.6.5 Import of functions plans created in older ver-

sions
7.6.5.1 Import from pre-version dated 31.07.98

Function plans exported from CASE FBD pre-version dated 31.07.98 (exported within
„Automationstation“ Program | Export... and with the extension „.fbd“) can be imported in
the CASE FBD ”AutomationStation“ Program | Import....
After the import, the function plans have to be checked!
The following has to be done manually after the import:

• External connections (AS->AS and Common) must be re-done again. The connection
to and from the edge connectors remain, but the information within the edge con-
nectors must be re-entered even they are visible.
7.6.5.2 Import from version 1.0 and 1.1

Importing function plans (.fbd) created with these versions are possible without any
problems.

First Steps
Tips and Tricks 7
7.6.6 Working with more than one project
7.6.6.1 Creating an additional project

Create a new project according to chapter 3.1, “Topology Wizard and Project-Directory-
Structure“.
7.6.6.2 Changing between projects

Before changing a project, it is no more necessary to start the ntp-file.
Requirement:
The connection names given in the Topology Wizard must be individual. Please refer to
chapter: 3.1.2.2 “Configure connections“.
7.6.7 Semicolon “;” within AS

The Semicolon “;” must not be used within the house addresses and normal texts. This
character is changed within the AS to the symbol and indicates within the User Panel
an acknowledged alarm.
7.6.8 Information about installed versions

During the program installation the following program is installed within the program di-
rectory:
FileVer.exe
Executing this file opens a window showing all programs and important .dll including
their version within the directory where FileVer.exe is located. The menu item
File Export allows to export the data into an text file.

First Steps
7 Tips and Tricks
7.6.9 Functionality Index
7.6.9.1 Description of Functionality Index/ µProgram Index
See also manual CASE HWC:
Microprogram F: This is the micro-program index. This index changes, when the
software version increases and corrections will be done on
existing functions.
Functionality Index 06: This is the software functionality index and has to do with the
functionality of the AS. This Index changes, when new firm-
ware blocks or new protocols etc. are implemented.
For detailed information on the current functionality index and the modifications see the
file “micr3600.zip” on CD or the PPL-Mailbox.
7.6.9.2 Handling of the Functionality Index
The information of the functionality index at the Automation Station document allows
CASE FBD to restrict/enable the use of AS-functionality’s corresponding to the used
microprogram of the AS.
This functionality index can not be entered/modified, as long as the respective program
(function plans) are open in the function plan editor.
A function plan / program drawn for instance with functionality index 4 can not be used
in an AS with functionality index lower than 4. This because the function used in the plan
are not available within the AS. If, for any reason the functionality index has to be re-
duced, the function block(s) corresponding to the higher index must be deleted before
the modification.

First Steps
Tips and Tricks 7
7.6.10 Length of one function plan
The length of one function plan within an AS program can be up to 15 pages long.
The maximum length of one AS program can also be up to 15 pages long.

First Steps
7 Tips and Tricks
7.7 CASE Prj

More information refer manual “CASE Prj User”, 7 000839 00X.

First Steps
Tips and Tricks 7
7.8 Licensing
7.8.1 General
Licenses delivered since 01.02.2000 (Dat Code M2) can be used with Win9x, NT4,
Win2000 and Win XP.
Licenses delivered since January 2002 (Dat Code P1), will not have an expiry date
anymore and are valid therefore unrestricted time.
Warning
Floppy disk drives with USB-Interface or LS120 drives are not supported from the
licensing system.
7.8.2 Delaying the expiring date of the licence

See chapter 1.2.4, “Updating the License“.
7.8.3 License related error codes
7.8.3.1 Error code -1002

Under certain circumstances, the files cc3216aa.dat, ccmv32aa.dat as well as
ccmv32aa.exe are created under the directory \windows\ by mistake. Later, the files
cc3216ab.dat, ccmv32ab.dat as well as ccmv32ab.exe are created, and so on until
cc3216zz.dat, ccmv32zz.dat as well as ccmv32zz.exe. After this, no more such files can
be created and an error message with the error code “-1002” is prompted. Until this error
is corrected, delete the files cc3216??.dat, ccmv32??.dat as well as ccmv32??.exe in
advance.
7.8.3.2 Error code 37

There are some information written onto the license diskette by transferring the license
from the diskette to the hard disk and vice versa. Therefore the diskette shall not be in
the write protected mode. If the diskette is in the write protected mode, the following
information is prompted onto the screen:
After pressing the button “OK” the diskette can

be removed from the drive and being set to the
write enable mode. Then one can start the
licensing process again.

First Steps
7 Tips and Tricks
7.8.3.3 Error code -64

The licensing system detects when one is setting back the date and time. This is de-
tected as an attempt to violate the license. The program(s) are not running anymore but
the following information is prompted onto the screen:
After pressing OK, the date and time can

be put forward again to resolve the
problem.
Warning
The date shall not be put further into the future than the respective expiring date
of the license. This will destroy the license definitely.
7.8.3.4 Error code -25

The following message appears with a program start, if the expiry date ran out and the
licence is not updated (see chap. 1.2.4 Updating the License) with CD version 4.0SR2
or 5.0:
Press the button „OK“ and afterwards

execute the license update (see chap.
1.2.4 Updating the License).

First Steps
Tips and Tricks 7
7.9 CASE HWC
7.9.1 General
• Under Windows NT4/2000, you can use the communication card novaNet290 with
the additional software “DOSEnabler. This program allows the ISA-BUS access (un-
der MS-DOS) with Windows NT4. The CD installation program also installs the addi-
tional software. You must specify the reserved memory range for the novaNet290
card.
• The parameter MaxZeilen in the file case_hwc.def has to be set to 25, when Win-
dows NT4 is used. This leads in a 25 line presentation of protocols and firmware
blocks. New, this parameter is set to 25 instead of 50 automatically after the program
installation. This value can be set to 50 manually, in case Windows NT4 is not used
(see also CASE HWC Operating Manual 7 000825 00X).
7.9.2 CASE HWC and CASE FBD/novaPro32

CASE HWC and CASE FBD/novaPro32 can not work at the same time on the same PC-
interface. Before CASE HWC is started, CASE FBD and / or novaPro32 have to be
closed!
7.9.3 Routel
Within the HWC Install path is a subdirectory “Routel” located.
Within the subdirectory ...\Routel\Bin, the Routel Microprograms are located.
Within the subdirectory ...\Routel\Data,the Routel Microprograms with created data are
located.

First Steps
7 Tips and Tricks
7.10 Remote Access onto an AS Island,

with CASE FBD / novaPro32
7.10.1 Set-up:
The two modem have to be connected into the RS232-link between PC and novaNet
Router:
novaPro32
local PC
M
SAUTER
M
29 1
novaN et Faul t
novaN et R x
novaN et Tx
Pow er
DS R
DC D
novaPro32 AS-Island
Remote Access PC
• Cable PC - Modem:
Standard PC to modem cable, which is provided with the modem.
• Cable modem - novaNet Router:

Standard PC to modem cable, which is provided with the modem.
7.10.2 Configuration of the Router side modem:
This modem does not have to be installed within WINDOWS.
1. Start your PC, inclusive of Windows.
2. Connect the modem concerned to your PC.
Set up a Hyper-Terminal to use for the configuration:
3. Click "Start", "Programs", "Accessories", (WIN98: "Communication"), "Hyper-

Terminal" and open "Hyperterminal.exe" (In case of the Hyper-Terminal program
being missing on your PC, you have to install it first: Click "Start", "Settings", "Control
panel", "Software", "Windows Set-up", "Communication", "Details" and add "Hyper-
Terminal".)
First Steps
Tips and Tricks 7
4. Name: "Config-RModem", "OK", "Connect using": "Direct to COMx" (where x, is
the COM port to which the modem is connected to), "OK"
5. "Bits per second": Here you have to set the Baud rate !IDENTICAL! to the one of
the novaNet-Router!, "OK"

First Steps
7 Tips and Tricks
Now test the connection with your modem:
6. Type "at" followed by the Enter key and check whether the modem correctly an-
swers with "OK". (If not, try "at&f", followed by the Enter key. If the modem still
doesn't answer with "OK", you need to find the cause for this!)
Configure the Modem:
7. Type the following commands each followed by the Enter key:
"at&f" Answer "OK" Sets the factory defaults.

"ats0=1" Answer "OK" Sets Auto-Answer.
"atq1" No "OK" displayed anymore! Sets no result code.
"ate0" Nothing displayed anymore! Disables echo.
"at&w0" Nothing displayed anymore! Saves settings in profile 0.
"atz0" Nothing displayed anymore! Load profile 0 on power on.

First Steps
Tips and Tricks 7
8. Typing "at&v" (probably "at&v0", "at&v1") you may now check your modem settings
(excl. "at&w0", "atz0").
9. Now disconnect this Modem from your PC and link it to the Router.
7.10.3 Set-up of the PC-side:
The Modem to be used on the PC-side has not to be configured, but to be installed
within WINDOWS.
The connection itself has to be set-up within the TopTreeWizard, please refer to the
section "Creating of a new Project"
7.10.4 Operation:
The operation of the connection is within novaPro32 using the "Connection" button, or
the menu "File" / "Connection"
The program can be set-up, for the connection to be established automatically, as soon
as the program is being started. Please refer to the description of the "Icon-Maker" for
further information..

First Steps
7 Tips and Tricks

First Steps
Method of working 8
8 Method of working
8.1 General
8.1.1 Introduction
With version 3.0 of CASE FBD, a so called "Plant Device Table Local" (BMTL) is created
when the PDBL (Local Project Data Base) get starting the first time. This allows an easy
and correct simultaneous working of several people at the same project.
Even so, one has to pay attention to several things when more than one person have to
work on the same project simultaneously.
In case, one does not observe these rules, data might be lost or damaged.
It isn’t possible to borrow all data from the Sharable Directory. It concerns some data in
particular of novaPro32 (Logbook, Password database, Filter, Groups).
In this document, we call the PC on which the main data (Sharable_Data) are stored the
"Master PC". The PCs accessing these centrally stored main data are called "Slave
PCs”.
8.1.2 Data structure

In the system EY3600, we distinguish between Sharable Data (collective used data) and
Private Data (PC specific data).
Within a project, all PCs are accessing respectively creating common data (Sharable
Data). On the other hand, each PC can create respectively access certain own data
(Private Data).

First Steps
8 Method of working
To enable all PCs to access the sharable data, they have to be located either on a file
server or on an accessible drive within a certain PC (Master-PC).
These sharable data are therefore stored public in a directory called "Sharable_Data",
but the own data on a directory called "Private_Data" on the respective PC.
The location, where the sharable data are located is stored within the private data. The
sharable data know which PCs and what AS-Networks trough which PCs are reachable.
These global information is stored within the topology file “<Project-name>.ntp”, which
can be created/modified using the "Topology Wizard”.
8.1.3 Contents of the Plant Device Table (BMT/BMTL)

The following data are stored within the BMT/BMTL:
• house addresses
• house address designation texts
• used I/O-blocks (Hardware and Software)
• machine fine addresses (MFA)
• all parameters and connecting information of the used in-/output blocks

First Steps
Method of working 8
8.1.4 Default-Project-Directory-Structure
The Default-Project-Directory-Structure also supports the Windows main directories
structure with “Program Files” and “My Documents” to better support regular backups of
all your own documents and projects. It also divides the Project files into Private and
Sharable files, to support network installations, where sharable files are to be located on
a file server.
Note
The Topology Wizard has to be applied for each individual PC. In a network installation
each individual PC has to be configured with the Topology Wizard, even if the *.ntp-file
and the program files and some of the data are located on a file server!

First Steps
8 Method of working

First Steps
Method of working 8
8.2 Multi-User Mode

To enable all PCs in a multi-user project to access the sharable data, they have to be
located either on a file server or on an accessible drive within a certain PC (Master-
PC).
These sharable data are therefore stored public in a directory called "Sharable_Data",
but the own data on a directory called "Private_Data" on the respective PC.
At least the following directories of the project, including their sub-directories, and all
containing data have to be accessible for everybody working on the project:
• \\Sharable_Data\
At least the following directories of the project, including their sub-directories, and all
containing data have to be located on the slave PCs:
• \\Private_Data\
8.2.1 Data located on a sharable directory (Master-PC)

All common data ("Sharable_Data") have to be on a shared directory of a PC (Master-
PC). For the procedure to share a directory, see the documentation of Windows Ex-
plorer.
Master-PC

First Steps
8 Method of working
8.2.2 Data on a file server

All common data ("Sharable_Data") have to be located on a file server.
Fileserver
8.2.3 Network access

The access to the Master-PC or the file server can either by Drive Mapping or UNC be
made.
8.2.3.1 Drive Mapping

The mapping of the sharable data has to be the same on all PCs. The advantage of this
solution is the easy portability of the data.
e.g.:
T:\projects\<project_name>\Sharable_Data\.....
8.2.3.2 "UNC" (Unified Name Convention)

This method can be easier in a LAN. But, in case the whole project has to be moved
(e.g. for an office environment to the project), all data have to be returned to the PDB
before moving. Afterwards, the PDBL(s) have to be created again.
The selection of UNC is done via “Network Environment ”.

e.g.
\\Machine_name\Volume\Projects\<project_name>\Sharable_Data\.....

First Steps
Method of working 8
8.3 Method of working
8.3.1 The PCs are connected with each other all the
time (Multi-User mode)
1. Start condition:
All PCs are connected via LAN with each other (see also chap. Fehler! Ver-
weisquelle konnte nicht gefunden werden.).
2. Install CASE FBD as well as the licenses, using the Default-Project-Directory-

Structure, on all PCs. (see also chap. Fehler! Verweisquelle konnte nicht gefun-
den werden.).
3. Create the project.

Create the Sharable_Data on the “Master PC" or file server (see also chap. 3.1.1).
4. On the “Slave PC”:

Start the Topology Wizard. Press the button “Browse” and select the topology file
<Project_name>.ntp of the respective project from the directory ...\Sharable_Data\ of
the "Master PC” (or file server).

Chose “Create a new workspace or a new PDBL”.
Create in the Topology Wizard the directories the directories of Private_Data such a
way that these directories on the Slave PC are produced. The PDBL is produced on
the Slave PC automatically (see also chap. 3.1.2.1).

Also create, using the Topology Wizard, the connection between the ASNetwork and
the communication unit novaNet290 or novaNet291 for this "Slave PC” (see also
chap. 3.1.2.2).
Now, you can work and all necessary information will be stored correctly into the
PDBL/BMTL of the "Slave PC". You can always synchronise (Borrow, Return) with the
PDB/BMT on the “Master-PC” (file server).

First Steps
8 Method of working
8.3.2 The PCs are not always connected to each other

(disconnected mode)
1. Pre-condition:
All steps of the chapter 8.3.1 "The PCs are connected with each other all the time
(Multi-User mode)" have to be done.
The directory "Sharable_Data" is located on a “Master PC” or a file server.
2. Remote (Slave) PC:

In order to work with an remote PC, the following procedure has to be followed.
Open the workbench (*.dew) and start novaPro32. Start novaPro32 and using the
function „Copy Shared Area“.in the menu File | Configuration.
Figure:
Recommended settings.
With this settings, also
address lists, HDB rep-
resentation, time pro-
grams etc. from no-
vaPro32 can to be used.
Afterwards, select the necessary options and press you the button „Copy“. The cor-
responding files are copied now in the directory „Copy_of_Sharable within the di-
rectory „Private_Data“.
Afterwards, close novaPro32.

While the PC is still connected, the required objects (AS, AS-Net) have to be bor-
rowed into the PDBL/BMTL. Later, when this PC is connected to the LAN, these
object can be returned to the PDB/BMT of the server again.
4. Disconnect the Remote (Slave) PC:

The "Slave PC" can be disconnected from the LAN.

First Steps
Method of working 8
5. Disconnected Remote (Slave) PC:
Start locally topology file (<Project_name>.ntp) with double-click. The file is located
within the project directory under \\Private_Data\Copy_of_Sharable.
Chose „Edit the project topology“.
Switch the settings for „Sharable Data Root“ to

„Private_Data\Copy_of_Sharable“. Use for it the button .
Afterwards, press the button “Standard for all directories”, so that all entries are
changed over.
Afterwards, press the button „Next“, check the connections and save the file.
6. Now, you can work on the remote "Slave PC”.
Note
Modified time programs, address lists etc. from novaPro32 cannot be returned from the
remote „Slave PC“.
Additional, you have to update these changes on the master PC or file server.

First Steps
8 Method of working
7. Re-connecting the Remote (Slave) PC:

Re-connect the "Slave PC" to the LAN.

Start, from the "Slave PC" the file <Project_name>.ntp of the server, located at the
directory "Sharable_Data". In the Topology Wizard, chose “Edit the project topol-
ogy”. Confirm the settings with the button “Next” and save the file. Thus, the directo-
ries are changed over to the server.

Now you can return the data from the PDBL/BMTL of the "Slave PC" into the
PDB/BMT of the "Master PC". They can now be borrowed from any other "Slave
PC" again.
Note
Modified time programs, address lists etc. from novaPro32 cannot be returned from the
remote „Slave PC“.
Additional, you have to update these changes on the master PC or file server.
If the same PC has to be disconnected from the LAN again, the whole procedure has to
be repeated (items 3-9). Exception: If the local Topology file is opened again, the set-
tings must be only confirmed with the button “Next”.

First Steps
Method of working 8
8.3.3 Tips for large projects
We advice to have only a limited number of AS within one PDBL. This will lead in a
much better overall performance and an easier portability of the data. The number of
PDBLs associated to one PDB is not limited. The maximum number of AS lend out into
the PDBL depends on the complexity of the programs required.
8.3.3.1 Preparation of work

House addresses, address texts, I/O blocks, I/O block parameters, function plans etc.
should be collected, prepared and transferred from CASE Prj to CASE FBD respectively
the plant device table (BMTL).
8.3.3.2 Working method: Suggestion 1

1 Create the Project with the Topology Wizard.
2 Open the Workbench (*.dew).
a) Export complete Astations (AS) from CASE Project or create AStations without
data (the maximum number of AS depend on the complexity of the program re-
quired).
b) Create ASNet and add the AS to it.
c) Define the Common areas and the Common variables (arrange for plenty of
spare Common variable names) within each AS.
d) “Publish” the ASNet into the PDB.
e) “Read current version” of the ASNet.
f) Create the required function plans, but don’t return the data’s into the PDB in a
large project!
g) Synchronise the BMTL with the BMT (House addresses), use the “Configuration
BMT” for this procedure.
3 In order to gain a reasonable performance, larger projects should be segmented into

several PDBL’s. Create an additional PDBL with the Toplogy Wizard.
a) Export complete Astations (AS) from CASE Project or create AStations without
data (the maximum number of AS depend on the complexity of the program re-
quired).
b) “Borrow” the required ASNet from the PDB.
c) Add the AS into this ASNet.
d) Define the Common areas and the Common variables (arrange for plenty of
spare Common variable names) within each new AS.
e) “Return” the ASNet into the PDB.
f) “Read current version” the ASNet in all already existing PDBLs.
g) Create the required function plans, but don’t return the data’s into the PDB in a
large project!
h) Synchronise the BMTL with the BMT (House addresses), use the “Configuration
BMT” for this procedure.
4 For additional PDBLs start at item 3 again.

First Steps
8 Method of working
8.3.3.3 Working method: Suggestion 2

1. Create the Project with the Topology Wizard.
2. Open the Workbench (*.dew). Within this particular PDBL, the project
structure has to be created.
2.1 Create all AS without FBD data, AS-networks and Common variable
names of the whole project. Arrange for plenty of spare Common-
variable names within each AS. Because of this “working method”,
one should use Common transfers rather than direct AS-AS transfers
(higher flexibility).
No further data must be created!
2.2 Configure the house address structure.
3. In order to gain a reasonable performance, larger projects should be

segmented into several PDBL’s. The maximum number of AS lend out
into one PDBL depends on the complexity of the program required.
Because of these reasons, the structure created at #2 has to be “Insert

into PDB” (“In PDB eintragen”). Afterwards, one is only working locally
using PDBL’s! The required AStations are “Borrowed” (“Ausleihen”) into
the PDBL and the ASNetwork is being “Read current version” (“Aktuelle
Version lesen”).
The PDB/BMT will be synchronised within the DPE-Browser.
By using PDBL’s on more than one PC, proceed according to chapter
8.3.1 “The PCs are connected with each other all the time (Multi-User
mode)“ or 8.3.2 “The PCs are not always connected to each other (dis-
connected mode)“.

First Steps
Method of working 8
8.3.4 Migrating (moving) of an existing project to an-
other PC (PC1 to PC2)
8.3.4.1 Maintaining the existing Directory-Structure on PC2
1. Make a back-up copy of your entire project data.
2. Copy the whole project (<Project name>\Sharable_Data and Private_Data) from

PC1 to PC2 with the same directory-structure.
3. Start on PC2 your existing Topology file <Project name>.ntp. It’s necessary to reas-
sign the Private_Data and create the “Connections” to AS-Islands again (because
different PC-name).
8.3.4.2 Different Directory Structure-Structure on PC2
Please note:
This is a brief description only! It’s thought for expert users. We don’t recommend this
option, unless your are well familiar with the EY3600 software.
The description covers the migrating of the PDB/BMT-Data and the novaPro32-pictures.
It does not include the moving of the Password set-up, the Groups/Filters set-up and so
on. We recommend to not move these parts but to re-generate them from scratch.
1. Copy the whole project (<Project name>\Sharable_Data and Private_Data) from

PC1 to PC2 with the same directory-structure.
2. All next steps, see chapter 7.4.3.2 “Migrating (moving) of an existing project to the
new Default-Project-Directory-Structure“.

First Steps
8 Method of working
8.3.5 System environment

Within a project, the groups as well as the users should be identical for all workplaces.
This can easily be achieved by using one system environment (*.dse) as a master. This
master will be copied onto the other PCs.
Caution:
It is recommended not to delete any users. In case an deleted user has still objects lend
out, they can not be integrated anymore. Not even, one is re-establishing the user. This
is because the system is working internally with an individual reference number for each
user.
One solution is, to link this user to an group without rights.

First Steps
Method of working 8
8.4 Communication via Socket (DCOM)

8.4.1 General
We are using Microsoft's Socket when we communicate with an ASNetwork connected
to an other PC.
This functionality is available since Version 5.0 of novaPro32 and CASE FBD.
8.4.2 Pre-condition
• All involved PCs must be connected via an PC-Network.
• Starting from Windows NT4, most protocols can be used.
• CASE FBD / novaPro32 version 5.0 or higher must be installed on all concerned
PCs. The required project must be available, according to chapter 8.3.1 "The PCs
are connected with each other all the time (Multi-User mode)”, on all concerned PCs.
• On the PCs communicating via other PCs to an AS-Network, DCOM must be set as
link within the topology.

First Steps
8 Method of working
8.4.3 Required settings within the Registry
This is a brief description only! It’s thought for expert users !
On all the PCs communicating via other PCs in a network, must be following settings in
the registry:
1. Start under Windows the Registry editor (regedit.exe)

2. Open the key „HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\OLE“
3. Set under “EnableDCOM“ and “EnableRemoteConnect“ the value to “Y“.
Registry settings for DCOM
Under Windows NT, you find only the name “EnableDCOM“.

First Steps
Method of working 8
8.4.4 Required settings within the Topology

On the PCs communicating via other PCs to a ASNetwork, DCOM must be set as link
within the topology.
For these settings, open the

file <Project_name>.ntp
using the Topology Wizard
and set the link via DCOM
(Socket).
Then press the button "Configure" and enter

the name of the PC accessing directly to the
required ASNetwork.
Press the button "OK".
Save the connection by pressing "Save Con-

nection".
Close the Topology Wizard and save the file
<Project_name>.ntp".

First Steps
8 Method of working
8.4.5 Starting a project

1. The file runNovaPro.exe must be started, on the PC with the direct link to the AS-
Network, before novaPro32 or CASE FBD, on the remote PC, starts to try communi-
cation via the PC-Network to the remote ASNetwork. The file runNovaPro.exe can
be found in the program directory of novaPro32/CASE FBD. This file runNo-
vaPro.exe can also be linked to Windows Autostart, for an automatic start-up.
A blue ball appears within the task-bar after starting runNovaPro.exe.
It is not necessary to start CASE FBD or novaPro32 on this PC.
2. Now, runNovaPro.exe can be started on the remote PC. RunNovaPro.exe can be

linked, using the "Iconmaker", to the start-icon of novaPro32.
A blue ball appears within the task-bar after starting runNovaPro.exe.
Remark:
The establishing of the link between the PCs can take up to one minute. Later, when the
PCs "found" each other, the communication is fast (depending on the load of the PC-
Network).
For connecting problems, the ball with a yellow exclamation mark are indicated in the
task border and the connecting list appear. In this list, you see the status of the connec-
tions and the time of the last change.

First Steps
Method of working 8
8.4.6 Link information
Pressing the right mouse button on top of the yellow ball in the task-bar, opens the fol-
lowing context menu:
Exit:
Terminates the link and closes runNovaPro.
ShowConnections:
Lists all connected PCs.
Note:
The connecting list shows only the connections on the Client side. On the Server side
the list does not show entries.
About runNovaPro:
Shows the current program version of runNovaPro.

First Steps
8 Method of working
8.4.7 Check the Network connection
Check the logic Network connection from any workstation to the Gateway and versus.
Open the MS-DOS window and type the command “ping” followed with the name of the
workstation to checked.
Example:
Check the connection from

Gateway-PC (np32-Gateway) to
np32-Client-1 np32-Client-2
the clients (np32-Client-1 and
np32-Client-2).
Type the following commands in LAN
the Command Prompt:
ping [PC-Name]
in Example:
ping np32-Client-1
np32-Gateway
ping np32-Client-2
AS-Netz / novaNet
In a good working, the Client

answers with its IP-Address and Example
the answer time.
Afterwards, check from any the Network connection. Type the following command in the
Command Prompt:
ping [PC-Name]
In Example:
ping np32-Gateway

First Steps
Method of working 8
If a message “Unknown Host...“ after the command “ping”, the operating system can’t
assign a IP-Address to the workstation. In this case, configure the file HOSTS on all PCs
on the network.
8.4.7.1 Configure the file HOSTS
With the file HOSTS, you can assign IP-Addresses individual HOST-name. Each time, a
PC from another subnet wants to connect via the PC-Name (HOST-Name), the file
HOSTS will be reading.
Directory of the file HOSTS:
C:\Winnt\system32\drivers\etc
Please note: The file HOSTS has no file extension. In the above directory, you find
an example file named HOSTS.SAM.
In the file HOSTS, insert the IP-Addresses followed the corresponding PC-Name
(HOST-Name) all novaPro32-workstations, incl. the nP32-Gateway. Use for each entry
(IP-Address) a new line. IP-Address and PC-Name must be separated with a blank
character.
Insert comments after the PC-Name, separated with the character # .
Note the following example:
Example of a HOSTS-file:
# This file contains the mappings of IP addresses to
# host names. Each entry should be kept on an indi
# vidual line. The IP address should be placed in
# the first column followed by the corresponding
# host name.
# The IP address and the host name should be
# separated by at least one space.
#
# Additionally, comments (such as these) may be
# inserted on individual lines or following the
# machine name denoted by a '#' symbol.
#
# For example:
#
# 102.54.94.97 rhino.acme.com # source server
# 38.25.63.10 x.acme.com # x client host
127.0.0.1 localhost
10.1.128.189 np32-Client-1
10.1.128.225 np32-Client-2
10.1.247.15 np32-Gateway

First Steps
8 Method of working

First Steps
News and Improvements 9
9 News and Improvements
9.1 CASE FBD

9.1.1 New functions from Version 2.50 to 3.0
General
• Enlarged functionality of Topology Wizard
• Local Plant device table (BMTL)
Browser
• No modifications
FBD
• FBD-Backup
9.1.1.1 New DPE-System environment (*.dse)
General
Because of a new Firmware Block Library, the Version 3.0 of CASE FBD comes with an
new DPE System Environment (*.dse). This new library corresponds also with the micro-
program index “E” and software functionality index “5”.
file “micr3600.zip” on the CD.
New AS-types
No modifications

First Steps
9.1.2 List of improvements in Version 3.0

General
• Topology Wizard
• CASE Prj-interfaces has been corrected
FBD
• Various corrections
Firmware Block Library

AI_Soft Corrections Parameter Print
BI_Soft Corrections Parameter Print
DI_Soft Corrections Parameter Print
AIA_Soft Corrections Parameter Print
DIA_Soft Corrections Parameter Print
CIV_Soft Corrections Parameter Print
Communication via novaNet291

The communication via novaNet 291 has also been improved. The file km.exe is closing
now correctly.

First Steps
General
• Docu Update
FBD
• PLC-Merker limit to MFA 127
Firmware Block Library

• Corrections in On-Line Mode
Mean_Hour Conversion of Definition of floating time windows

Pump Corrections in conversion

First Steps
9.1.4 New functions in Version 4.0

• AS-Group and Master-/Slave functionality
• Browser integrated in Workbench
• Multiple selection of objects within the Browser
• Actual status of the Objects (AS, AS-Networks etc.) is displayed within the
Browser
• Defragmentation of the data bases (PDB, PDBL)
• Extended back-up functions
• User defined toolbars
• Tool tips on boarder bar (link reference of signals)
• Simplified set up of User Blocks
• Set up of user plans
• Page numbering in FBD
• Progress display when downloading
General
program index “F” and software functionality index “6”.
New AS-types
No modifications

First Steps
whenever indicated.
9.1.5.1 Known bugs in Version 4.0

• No error message when the Router EYZ291 is switched-off and you try to down-
load.
• The diagnostic tool NovaMit not shows all telegrams using the Router EYZ291.
Using the card EYZ290 to peform a diagnostic on novaNet.
• Using OnLine-mode with Router EYZ291, the message “Can’t open ComPort” can
appears. After that, restart CASE FBD.
• During the creation of an ASNet and opened novaPro32, various error messages
appears in the background.

First Steps

• Copying edge connectors.
If you drag a marked area across modules and edge connectors in the function
chart, the marked edge connectors are copied as well.
• Firmware icons.
All firmware modules now have a graphic symbol in the module head. Use the up-
date tool so that you have the icons in existing projects.
• Uploading I/O parameters.
Current setpoints and limit values from I/O-modules can be read out of the AS.
The values read are saved in the FBD.
• The AS type and functionality index can be read by the AS. The read configuration
is entered automatically in the AutomationStation window.
• Full functionality of novaMit with the router EYZ291 (needs microprogram index F
in the router).
• For remote, mobile operation, there is a new folder (“Copy_of _Sharable”). The
files needed for mobile operation can be copied straight from novaPro32 into this
folder.
General
program index “G” and software functionality index “7”.
Firmware-module library
Firmware icons
App
New module “Application number” for novaflex and EYT250; (from FI 7)
New parameter (“SNr”) on all E/A modules (system number for BACnet); (from FI 6)
New AS-types
No modifications

First Steps
General
• Optimisation of memory and time due to new data structure. This has also solved
the problems with large projects > 350 objects (see Product Information D 02-007
on CASE FBD V4.0 SR2).
FBD
• Sorting order corrected in the documentation system.
• Various corrections in the documentation system.

First Steps
9.2 CASE Prj

9.2.1 New functions from Version 4.6 to 4.7
General:
• New actual Handbook and Help Files in German
• In order to simplify the creation of a new project, an input field for the project name is
indicated at first. Afterwards the complete path is arranged as default, which how-
ever can be changed as desired.
• When a new project will be produced, now a template project can be selected, from
which certain parameters can be transferred to the new project. Individual parame-
ters can also later be taken over from the menu.
• In the administrator NSO specific forms and reports can be merged, which are then
usable for the user.
Engineering:
• A printer-AS can be selected.
• Now the DP-function can be indicated to each data point.
The house address and the address text can be changed manually for each DP and
become closed for the automatism.
• The menu "houseadress-function / Text check" have been new arranged.

- With a button all texts and parameters can be checked for special characters,
which the FBD cannot process.
- In the hand control device a reproduction of the HA and the address texts can be
indicated.
- In case the HA are not clear, all duplicates are indicated in a table and can therein
be changed directly.
• Innovations in the HA definition

- Selection whether a printer-AS is present. The last place of the HA is used for this.
- Optimising the HA on the hand control device indication (indication on a line).
- Choice of the group name witch begins with the address text begins (IFP, Panel,
Plant, PC).
- Definition of the filler (blank, zero, hyphen, point).
• For the group names now any configurations can be stored and restored again.
In order to improve the clarity, the group names were distributed on different register
maps.
• The print menus were revised on uniformity.

First Steps
• New lists were provided for the printouts:
- Article sumlist for each plant
- Article sumlist for each panel
- Article sumlist for each building
- Article sumlist entire
- Commissioning check list
• The manually allocation of the Datapoints will go much faster.
Exchange of data with PDBL/FBD:

• According to standard first will be examined at the AS export and then the HW-HA
will be exported to the BMT.
• Own rider map for the export of the printer-AS

First Steps

General
• New up-to-date Handbook 7 000839 003 and Help Files in German for V5.0, English
and French for V4.7
• New Menu Items [Save Project As...], [Project Backup]
• NEW: Functional-Information-Package (FIP) for
EY-Configurator
Calculating Services
Automatical offer position generation
• The Item database has been redesigned
The present Item Group Combinations are cancelled
NEW: 10 Item Bundles (IB 0 .. 9)
Used for:
Set filter in item lists
Automatical offer position generation
Calculating with discounts
• Each Product-Data-Sheet is now a single file. The PDS file from each used product
can be stored within the project path.
• The Project-Info-Dialog has been revised.
NEW: Logbook for course-of-project-events documentation
NEW: Info shield for detailled program and project informations
Changed address and person administration
• The Options-Dialog has been revised
NEW: Definition of the HA-structur for the BMT
Printing function for group and data point names
• Many functions have been optimized.
Library
• The function group library has been redesigned
The template plants are now integrated with a link to the picture but WITHOUT any
subgroups
The folder of the template plants now include the corresponding pictures and the
object list text files.
• The tables of contents for the FBD-Blocks and text blocks can be created automati-
cally. For this purpose the file properties Title and Category of the text blocks are
used.
• The AS templates have been moved from the system environment to the
CASEPrjLib.
Calculation
• Any offer may now be calculated for more than one client with different sets of dis-
counts ("discount variants").
• Variable reports
Before printing you can choose between several texts:
Name (so far)
Short text (from IDB)
Description (form IDB)
Content of text files
First Steps
• Subtotals can be printed (for any level).
• For each offer position you can choose whether you like
Item single list
Item single price or only total sum
Total price
Start with a new page
Engineering
• Copy from function group library
The Copy-Dialog (selection list) now is exclusive tuned for the function group library.
• A new function supports multiple input of values
• The FBD- and VDI3814-parameter are shown clearly arranged in a new list.
• New VDI-List for single room controller
• The handling of templates and documents, for function descriptions, has been sim-
plified.
• Motor list
Now 3 stages are supported.
The techn. motor data are stored in the project item database.
• Cable list
You can now type in the values for U/P/I directly in the list.
If a target items is choosen, the data from the project item database are taken over.
• Valve list
Non-Sauter valves are now shown in the list also.
The technical valve data are stored in the project item database.
• Item list
The offer position number can be typed in for each item.
• Group property
An additional user reference can be typed in for each group.
The user reference can be used in the house address and in most of the reports.
• The short name for the Information Focus Point can now also be numeric.
Data exchange with PDBL/FBD:

• The house address structure for the BM Table can now be predefined within the
CASE Prj and transfered to the BMT
• AS groups together with a list of AS group members can now be exported also
• Renaming of house addresses is now possible.
• Apart from complete automation stations only
house addresses and address texts and/or
Parameter can be exported selectively.
For this purpose the CASE Prj can be linked with any AS in the PDBL. (Not only
those AS which were initially exported from the CASE Prj)
• The Alarm/Status parameter from the BI-Block is set corresponding to the settings in
the BI_Soft-Block.

First Steps
Editing AS / Allocation / House Addresses:

• With a new function in the House-Address-Dialog you can check if the source for the
addresstext will be clipped.
• AS Allocation
In reports and forms the data points needing a Ni1000/1V converter are marked with
a star (*).
Die digital inputs for real feedbacks now are supported.
No longer use the data point type "3-Point". In exchange for 3Point Com-
mand_OPEN and Command_CLOSE have been created.
The card EYS155 now can be configured as 1 or 2 stage command.
Now 7 labels are available in field modul EYY160.
The user defined order and filter will be considered if you use Option 3 (shown list).
• AS Groups
Any AS can defined as an AS Group.
For AS groups additional data can be entered like:
AS group members
Master/Slave groups
• Printing the AS list, all allocated plants will be listed too.
• NEW: AS list with additional informations.
Fixed problems:
• All parameters and the name of the plant picture will now be exported correct to the
EXCEL-SHEET (VDI list), without unnecessary messages.
• The parameter TgPTR and TgPL can now be entered via dialog (#Name?).
• In report "AS Allocation with PD" the house address has not been printed.
• If the control panel restrictions are used, the address text also has been cut after 21
characters.
• Internal ACCESS Error Messages appeared if the HA has been defined with more
than 24 characters.
• Sometimes the path to the item pictures has been lost.
• The terminal signs of modul EYY170 have been corrected.
• When creating a new item, a new supplier can be created too.
• Offer position numbers can now be greater than 255.

First Steps
Data exchange with PDBL/FBD (V5.0) works only with CASE Prj V5.2.
General information
• New updated manual (7 000839 001)
• There are now several navigators.
The Help function can now be called up and the form can now be opened via context
menus (right-click).
Data exchange with PDBL/FBD

• Data exchange has been adapted to the changes made to FBD Version 5.0.
Data exchange with novaPro Open

• There is now a form for data exchange with novaPro Open, via which the gates and
the data points can be linked with one another.
• It is possible to assign the house addresses to the gates automatically or singly.
Data exchange with EYT250 operating unit

• The data-point list of CASE Prj can be visualised in the EYT250 operating unit.
The data points shown in the data-point list are saved in a file in a special format and
are then imported using the programming tool of the EYT250 operating unit.
Minor improvements and modifications

• The ‘Index out of bounds’ message should no longer appear.
• It is now also possible to assign pictures on levels 1 and 2 (building, panel).
• The updating of the material project database works again.
• When editing the material database, you can now also enter the MV and PDS num-
bers.
• The AXT 111 is available in the valve/drive selection list.
• The method of selecting addresses (project information, orders ...) has been im-
proved.
• On printing the VDI list, the Project Name, User etc. are now entered correctly.
• The HA definition report is now translated as per the language set.
• On printing the project information, only those persons who were selected are
printed out.
• The print-out for the EY configuration works again.
• On printing from the main menu, the current group is pre-set.

First Steps
9.3 CASE HWC

• Parameterisation of Routel and EPROM creation
• Send AS-Time to AS-Groups

• Address List
• Time commands to groups of AS
• Optimised reading of a data set
• AS-Group membership
• Force a Garbage Collection (delete spontaneous messaging)
• Configuration A291
• New Routel functions

First Steps
9.4 novaPro32
Adress list
The tool “Address List” of novaPro32 allows direct operation and control of your
system. You get direct access to all functions of your system over released house
addresses. Thus, it is possible to operate and control your installations without
pictures.
Within an address list you get the same functionality as you get in pictures; i.e. you
can acknowledge alarms and limit value violations, change set points and limit
values, generate switching commands.
Directly from within an address list a picture with the address selected can be
opened.
You can open an address list by selecting an installation from the TreeView or by
pressing a predefined button in a novaPro32 picture.
Choose between an address list based on an installation (all addresses of the se-
lected installation are listed) or an address list based on a picture (all addresses of
the selected picture are listed).
HDB / Trend
novaPro32 offers you a comfortable tool for the graphical view of measured val-
ues, status and alarm messages. You get the possibility to display actual values
as well as historical data as a trace or in a table.
Traces show the process of a measured value over time in graphical form. Data
from the historical data base are used to display the process in the past. Actual
data are used to show trending.
Up to 10 different Traces can be displayed in a window of novaPro32. You can

configure (select shape and colour), edit and view the diagrams directly from
within novaPro32.
HDB-Server
From release V3.0 of novaPro32 the program HDB-Server can communicate over
the DCOM standard; i.e. in a network (LAN, WAN) HDB-Server has to run only
once.
An operation station with novaPro32 reads historical data directly from the HDB-
Server by using the DCOM-interface.
Save historical data in archive files:

From release V3.0 archive files can be created weekly, monthly, every half a year
or every year.
Now, the Refresh-time of the saving process is selectable.

First Steps
Messaging
A time program (scheduler) can be assigned to every messaging channel. This
allows time controlled enabling and disabling of a messaging channel. Thus a line
printer can be enabled during office hours only, or the home fax of the service staff
gets enabled on weekends only.
Pictures
Dynamic objects can be positioned precisely to a single pixel.
Parameter X and Y define the exact position of the upper left corner of a dynamic
object. (The upper left corner of a novaPro32 pictures defines point zero (X=0;
Y=0).
The possibility to open an address list has been added to the dynamic object
“button”.
Logbook
A logbook has been integrated into novaPro32. All actions of an operator are re-
corded in a log file. 13 files are created in the folder …Sharable_Data/System, one
file for a month. Thus, there is a file for the actual month and for every month of
the last year. The files are of type *.mdb (Microsoft Database, Access). You can
read and analyse the files with Microsoft Access.
Startup of novaPro32 / IconMaker

Now, an alarm list can be opened automatically at start up of novaPro32. Thus,
the user gets a quick overview of the actual condition of his installations.
The program runNovaPro.exe can be started automatically when starting no-

vaPro32 over a single icon (IconMaker). runNovaPro.exe is needed for DCOM
communications in a network.
Online Documentation
The online documentation (menu „?“) has been updated. Descriptions of the new
functions of novaPro32 release 3.0 have been added.

First Steps
• Routel
• SuperBMT (SuperProject)

• Stability (KM, HDB-Server, DCOM)
• “Acknowledge all“ in Alarm list
• various corrections

First Steps

novaPro32-Browser (Documents, Address and System Browser)
• The available documents in novaPro32, e.g. Schematics, pre-set-up Protocols,
HDB's / Trends, Time Programs etc. are now being displayed and managed in
a tree view. The documents can be opened by double clicking the icon con-
cerned.
• The properties for each of the documents can be displayed, using the right
mouse key.
Documents data base

• All Schematics, pre-set-up Protocols, HDB's / Trends, Time Programs are now
stored in a structured data base. There are no more *.npr files.
• All projects set-up with a previous version of nP32 have to be converted to the
new file format, using the program NovaProDocConverter.exe.
• The documents can be copied, renamed or moved within the tree view as re-
quired.
• Schematics can be copied from one project into an other one now, using the
new functions export, import.
AS-Groups
• nP32 fully supports the AS Groups functionality.
A Schematic can be set-up and dynamised for each AS-Group. This Schematic
is common for all AS within this AS-Group. The Schematic can be opened for
each Master AS of the Group and the values of this master are being dis-
played.
Schematics
• Buttons without a frame can be dynamised now.
HDB / Trend
• The Y-axis of a HDB / Trend graph can optionally be defined manually now.
• The settings of the frames within a HDB / Trend graph are memorised now,
when closing the graph..
Protocols
• Exporting of Protocols into a text file
The utility „Protexp.exe“ provides the functionality of calling a Protocol into a
file via command line. The protocol file is created in TAB delimited format. Us-
ing this utility, the call for a Protocol into a file can be executed via any third
party scheduling program. The data can afterwards be processed by a third
party software.

First Steps
Time Profiles
• >1 Time Profiles per Address can be stored.
• Copying of Time Profiles
• Time Profiles for AS-Group addresses
Calendar
• The result of the operation is displayed, when downloading a calendar. Auto-
mation Stations to which the download was not successful are marked in red.
Logbook
• The Logbook files are now password protected and can't be modified by a user
anymore.
Alarm List
• Within the Alarm List, the category is displayed now. With this feature, the
Alarm List can be sorted by category (importance of the alarms if generated
this way).
• Sophisticated acoustic signalling of an alarm:
A sound can be assigned to each category of alarms. The sound can be re-
petitive. It can be temporarily muted with the keyboard (all configurable).
• Configuration of the Alarm List with Address-Groups.
Online Messaging
• Attached texts can now be of up to 5000 characters. With this extension the
text field provides enough space to print reasonable instructions together with
the Alarms.
Address List
• Types of Address Lists:
o From Schematic: All Addresses of the Schematic con-
cerned. New!
o From AS-Group Schematic: All Addresses of the AS-Group
Schematic concerned. New!
o Logical Address List: Addresses according to the structure
of the HA.
o Physical Address List: All Addresses of a selected AS.
New!
o AS-supervision Address List: All AS-supervision addresses. New!
• The new AS supervision address List provides a overview of the operating
state of all AS.
Filter
• Three Filter types are provided:
o Addresses AS
o Addresses AS-Groups
o Addresses AS-Supervision
• Improved and working Filter assistant!
First Steps
Routel
• Support of the HDB-Server
The Routel functionality now supports the upload and the storage of HDB data
on the PC-HD.
Conversion of projects set-up with earlier versions of novaPro32:

1. Be sure to make a back up of your project data before starting the conversion.
Converted Projects can not be opened with novaPro's Version < 4.0
2. Start the Workbench of the Project to convert.
3. Start the program NovaProDocConverter.exe. You find it within the directory
FBD_novaPro32 (Default: C:\Program files\Sauter\FBD_novaPro32).
4. Click the icon „Convert Project“
(Ref. Manual „EY3600 novaPro32 Installation“ Nr. 7000 915 001 N06 Chapter 4.2)

First Steps
whenever indicated.
9.4.5.1 Known bugs in Version 4.0

• In AS-Gruppenbildern können keine AS-Überwachungsadressen dynamisiert wer-
den.
• Ein Benutzer, der im Novapro32 das Recht nicht hat, das Programm zu beenden,
kann es beenden wenn er sich vorher ausloggt.
• Wenn im Routelbetrieb ein Netz (eine Insel) während der Initialisierung nicht er-
reichbar ist, wird es vom Program unterdrückt. Dies ist am Bildschirm nicht erk-
ennbar (keine Fehlermeldung).
• Im Routelbetrieb ist das Quittieren in der Alarmliste während des Meldeanrufs
selbst nicht möglich (im Bild, oder in der Anlageliste möglich).
• Eine mit "ChangeItemPosition" veränderte Grösse einer Dynamisierung (Knopf)
wird beim Kopieren der Dynamisierung nicht mitkopiert.
• Die Aufstart-Alarmliste kann trotz aktivem Passwortschutz auch ohne entspre-
chendes Einloggen geschlossen werden.
• Bei stark belastetem novaNet können Alarme der AS-Überwachung ausgelöst
werden.
• Ist der On-Line-Drucker über längere Zeit nicht mehr verfügbar (z.B. kein Papier
mehr!), stürzt nP32 nach ca. 800 Druckmeldungen ab.
• Die Alarmliste des Users "Ohne Passwort" kann nicht gespeichert werden.
• Wird bei einer DCOM-Verbindung die Verbindung temporär unterbrochen (oder
der DCOM-Server fällt temporär aus), so werden danach die Bilder etc. auf dem
Client nicht mehr aktualisiert und dies wird dem User nicht angezeigt (Kugel wird
wieder gelb).
• Wenn die Workbench passwortgeschützt ist und novaPro32 (inkl. Workbench)
über Ikone gestartet wird, erscheinen zahlreiche Fehlermeldungen. Diese können
alle quittiert werden und danach kann die Workbench über den novaPro32-
Browser geöffnet werden. D.h. der FBD kann so, ohne Berechtigung (weder in
der Workbench, noch in novaPro32), gestartet und der entsprechende Funk-
tionsplan geändert werden.
• Beim Aufruf der Ausdruckvorlage im Menü Konfiguration/Adressliste wird der List
und Label Designer nur in der Taskleiste als Symbol geöffnet. Er dauert auch sehr
lange. Der User erhält keine Rückmeldung, dass im Hintergrund etwas abläuft und
klickt in der Folge wiederholt auf den Button "Öffnen". Dies führt zu Fehlermeldun-
gen.
• Beim Verschieben eines Dokuments muss der Name, nicht die Ikone angeklickt
werden.
• Ist ein Bild auf 2 PC geöffnet, wird beim Versuch eine Dynamisierung zu ändern
keine Meldung angezeigt.

First Steps

Scheduler
The Scheduler (PC time profiles) enables time-controlled operations to be carried out:-
• Carry out protocols
• HDB export
• Download AS time profiles
• Download AS calendar
• Synchronise AS time
Historical database (HDB)

• The historical data can now be exported as a graphic (bmp, jpeg) and a table (txt)
straight into a file.
Protocols
• Protocols for ‘Local’, ‘Auto’ and ‘Remote’ feedback signals (needs a microprogram
with FI 7 in the AS).
• Export
Protocols can now be exported straight from novaPro32 into a text file.
Pictures
• Default settings for dynamisations can now be adapted and saved. They are de-
fined in the ‘BMT Config’ object.
The settings can be exported and imported.
The default settings can be set for all dynamic objects (‘Text’, ‘Filling’, ‘Button’,
‘Web’, ‘Values’) and for every address type.
• New colour fillings: ‘Rectangle’, ‘Ellipse’ and ‘Thermometer’.
Network mode
• Communication is now effected via WinSocket instead of DCOM.
• The server can now also work as an operating station.
• Mixed operation as server/client is also now possible for every workstation.
• Functions resolved when user logs on again.
Remote monitoring (Routel)

• AS monitoring from EYZ291.
• Parameterisation resolved.
Project management (Icon Maker)

• For remote, mobile operation, there is a new folder “Copy_of _Sharable”. The files
needed for mobile operation can be copied straight from novaPro32 into this
folder.
• A start icon for mobile operation can be made using the ‘Icon Maker’.

Case FBD - Premier Pas

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Case FBD - Premier Pas

Uploaded by

Copyright:

Available Formats

First Steps

CASE FBD Version 5.0

This document replaces the previous versions

7000931003 P11 Sauter Systems 1

2 7000931003 P11 Sauter Systems

2 The first CASE FBD project................................................................................... 23

4 Functions CASE FBD/novaPro32 ......................................................................... 65

7000931003 P11 Sauter Systems 3

4.2.5 Objects into the autostart group ...............................................................70

5 Installation of CASE Project ..................................................................................91

6 Installation of CASE HWC......................................................................................93

7 Tips and Tricks .......................................................................................................95

4 7000931003 P11 Sauter Systems

7000931003 P11 Sauter Systems 5

7.9.3 Routel ....................................................................................................131

9 News and Improvements .....................................................................................159

6 7000931003 P11 Sauter Systems

7000931003 P11 Sauter Systems 7

List of icons and symbols

Single mouse click with left button

Single mouse click with right button

Double mouse click with left button

Double mouse click with right button

8 7000931003 P11 Sauter Systems

7000931003 P11 Sauter Systems 9

10 7000931003 P11 Sauter Systems

1 Installing CASE FBD/novaPro32

Windows NT4.0(SP6a)/ Windows 2000/ Windows XP

7000931003 P11 Sauter Systems 11

1.2.2 Install the license

2. Start the licensing by executing (double click) install.exe.

4. Execute the licensing by pressing the button "Transfer-License"

12 7000931003 P11 Sauter Systems

7000931003 P11 Sauter Systems 13

1.2.3 Remove the License

The correct license directory must be adjusted under "License-Path”.

The successful license transfer is prompted onto the screen.

14 7000931003 P11 Sauter Systems

Execute the update:

2. Start the update by pressing the button “upgrade“.

3. The upgrade is confirmed with the follwing message.

7000931003 P11 Sauter Systems 15

Afterwards press „OK“.

Thus the Upgrade is successfully executed.

16 7000931003 P11 Sauter Systems

1.3 Program installation

Start the installation by

Please follow the instruc-

7000931003 P11 Sauter Systems 17

18 7000931003 P11 Sauter Systems

Review the settings and click on

7000931003 P11 Sauter Systems 19

Select the language of the template editor „List&Label“.

The successful program installation is prompted onto the screen.

20 7000931003 P11 Sauter Systems

7000931003 P11 Sauter Systems 21

22 7000931003 P11 Sauter Systems

2 The first CASE FBD project

The following pre-conditions apply:

2.2 Fundamental procedure

2. Creating a project using CASE FBD

3. Data export into CASE FBD

4. Completing the programme within CASE FBD