Professional Documents
Culture Documents
ACS790 V9.00.xx
Engineering and
Operating Software.
Important Notes:
This version of ACS790 requires a Windows 7 or Windows 8 operating system
The devices used in this guide need to be adapted to the project or to the training equipment
available
Correct planning needs to be carried out prior to beginning with the engineering
The site installation must contain the same devices and have the same topology as the ACS
project
This version of ACS supports only the current devices in the engineering workflow (September
2013)
2
1.0 New Project - Offline Engineering
3
1.4 Set Language, Temperature and time settings and service contact details. The
highlighted field above is for use with Synco900 only and can be ignored. (Only available
in certain regions)
2.1 It is recommended to start by creating the “Site topology”. Click “Site topology” then the
drop down box “Structure”.
2.2 By adding and naming “Nodes” (like folders) the geography of the building(s) can be
created. Drag a node from “Structure” to the project “Topology”.
4
2.3 Right click on the node to rename
2.4 Add and rename the nodes until the “Site Topology” is complete. The drop down boxes
can now be opened to allocate controllers to their respective location within the building.
Use:
RMH760B for the boiler plant
RMS705B for the chiller plant
RMU730B for AHU’s
RDF301 for the FCU’s
Or, according to the requirements of your project.
5
2.5 When complete we can progress to create the bus topology. Use cut and paste as
required.
NOTE: In this example only 1 RDF301 FCU controller has been added to each floor at his
stage. The reason being that configured devices can be copied and pasted when multiple
plant has the same configuration. Therefore additional RDF301 can be added following
configuration of those currently allocated to floors 1 and 2.
2.6 While not technically necessary in this example, we will add line couplers to create 2
lines, one for main plant and one for the rooms on the ground and first floors. The line
couplers once included in the topology are addressed in the properties window. Always
start the topology in Area 0.
6
2.7 The bus network is completed and an OZW772 is added to the backbone (Area 0).
NOTE: The messages in the Error and Warning viewer will be dealt with during and
following configuration.
2.8 The topology set up is now complete and the workflow assistant can be marked as such
as we move to the next step.
7
3.0 Configuring devices
3.1 Firstly click on the “Plant Engineering” button, and then expanded the tree and navigate
to the first controller to be configured.
3.2 For this exercise we will choose a simple boiler application, H3-0
8
3.3 Make the Clock Time a Slave (We will use the Clock in the OZW772 the Time Master).
Configuration of communication will follow after setting up the functions of each
controller.
3.4 The only other setting to make in this simple standard application is to set the outside
temperature as RMH760.X2 in the Miscellaneous>Inputs folder
9
3.6 Text can be added for all Inputs, function blocks, faults etc.
3.7 Again we make the Clock Time a Slave. Configuration of communication will follow after
setting up the functions of each controller.
10
3.8 Set N.X8 as digital, since we will use the Outside temperature sensor in the RMH as the
OT sensor for the whole building
3.10 Since there are no standard applications for the RMS705, we make a very simple chiller
application for simplicity.
11
3.11 Set basic type S
3.13 Set Controller 1 “Main controlled variable” as N.X1 and “Start condition” as “Refrig
request 2 position”
12
3.14 Set Rotary step switch 1 “Start condition 1” and “Start condition 2” as Sequence
controller 1-S4
3.15 Set Motor 1 “Motor A” as N.Q1, “Motor B” as N.Q2, “Start condition 1” as Rotary step sw
1A precom and “Start condition 2” as Rotary step sw 1B precom
3.16 Set Logic 1 ”Logic A input 1” as Rotary step sw 1A command and “Logic relay” as N.Q3
13
3.17 Set Logic 2 ”Logic A input 1” as Rotary step sw 1B command and “Logic relay” as N.Q4
Note: Many more settings can be made including text for all inputs, function blocks, faults etc.
However for simplicity in this exercise may be omitted
3.19 Set an RDF301 “Plant type” as 2 pipe with electric heater and “Control sequence”
cooling only.
14
3.20 Select Outside temperature as “Additional display information
3.21 Room 1 RDF301 may now be copied and pasted into Room 2 RDF301
3.22 Room numbers can be added if/as required. No more settings are required for this
exercise.
15
3.23 Parameterisation is now complete and is marked accordingly in the workflow window.
4.1 Click on Current parameter set (you may wish to adjust the window sizes at this point)
16
4.2 Since the RDF301 can only receive from Outside temperature zone 31 (you can see
above that it is shown in grey and it cannot be changed), we will put a transmitter and all
receivers in this zone. Remove the RMH760B from zone 1 with right click and delete.
4.3 Outside temperature zone 1 can be deleted with right click and delete
4.4 With a right click the OT zone (31) can be renamed if required. In all cases additional
zones can be added with a right click in the Current parameter set window, for all zone
types.
17
4.5 Drag the RMH from “Assignment selection – Transmitters” to “Current parameter set –
transmitter” this sets the RMH outside temperature sensor as the source for the whole
building. Observe the Warning and Error window.
4.6 Drag AHU controllers and thermostats from “Assignment selection – Receivers” to
“Current parameter set – receivers. Note the warning in the Warning and Error window
concerning no OT transmitter has now disappeared.
4.7 In the same manner as described above, assign a producer (RMH) and Consumers
(RMU’s) to the heat distribution zone.
18
4.8 Repeat for the Refrigeration zone as shown above.
4.9 Add geographical/time switch zones for the First and Second floor RDF301 room
controllers.
4.10 Assign AHU-1 as the master for first floor RDF301’s and AHU-2 as the master for second
floor RDF301’s.
19
4.11 Drag and Drop all controllers to the OZW772 device list
4.12 Check for Warnings and Errors. There are no errors for communication zones, but a
Clock Time Master is not defined.
4.13 In the OZW772 “Time of day/date” folder, set “Time synchronisation” to Quartz.
4.14 In the OZW772 “Communication>KNX” folder, set “Clock time mode KNX” to Master
20
4.15 There should be just 2 warnings in the Warning and Error viewer. Devices will be
assigned during commissioning. In this version of ACS790 it is not possible to add
power supplies to the structure, the error therefore only serves as a reminder.
4.17 Click on “Archive parameter set. The offsite configuration work is now complete.
(In future versions it may be possible to add User defined graphics and pop-cards at this stage,
however in the current versions we can only add any background images into the project
documentation folder for later import into the project)
21
4.18 Project related documents can be copied into the project folder. Double click on the “Add
project related documents” highlighted above, this opens the corresponding project
folder into which project drawings and other related documents can be pasted.
4.19 In the final step of off-site engineering, double click “Handover project to commissioner”,
this opens the Pack & Go window. By clicking on the highlighted buttons, the projects
can be e-mailed to the commissioning engineer and/or saved to a folder on the PC.
22
5.0 On Site Commissioning
5.3 A window will pop-up, select the connection type. It is recommended to use the OCI700
since this will provide access to all device settings. Click “Continue”
23
5.5 The next step is to search for and assign the devices. Click on “search and assign
devices, A window will pop-up
5.6 Put the selected device into programming mode and click “Assign”, this can take a few
minutes.
5.7 The device is assigned. Repeat the above for the second Line coupler.
24
5.8 The second line coupler is assigned. Click “Continue”.
5.9 ACS searches for devices. In this plant we have one area (0) and two lines, line 2 and 3,
therefore all lines are searched (This can take some minutes)
5.10 We now assign the devices found. There are two ways this can be done, either by the
serial number of the controller or by placing the controller in to programming mode. Note
that devices where there is only one of each in the project are automatically assigned!
25
5.11 If we happen to know that AHU1 is controlled by the RMU730B with KNX serial number
00FD00085113, we can assign by serial number as shown above. Enter the serial number
and click “Assign”
5.12 AHU 1 is now assigned to the controller with the serial number 00FD00085113.
26
5.13 For the next device we will put each it into programming mode to assign the device.
Highlight the device to be assigned, put that device in to programming mode and click
“Assign”.
27
5.15 Repeat using either of the above methods until all devices in the project are assigned.
Click “Continue”.
28
5.18 Following parameter download, the concerned device(s) will be stopped. Click any
devices shown as stopped to start the device
5.19 Make any device setting adjustments, check communications are working correctly and
rectify if not.
5.20 Click “Write configurations”. Click “Select changed” then OK. Devices where changes
have been made will be downloaded.
29
5.21 Set time and date on central unit
5.22 Time can also be sent to all devices by clicking on the clock. Check off tick boxes in the
Workflow assistant.
Note that in newer versions of ACS some if not all of the above bugs should have been
rectified.
30
6.2 Device 0.2.3 is started
7.1 In the workflow window, click “Create commissioning report“, a pop-up window opens,
any or all devices may be selected, the current parameter sets can also be archived or
overwritten. Click the tick box “Create commissioning report”. After making your
selection, click “OK”.
Note: This operation can take some time, so for test purposes select just a few devices.
31
7.2 Check the tick box against commissioning reports. The reports can be printed
7.3 Archive the project and check the corresponding tick box
32
8.0 Plant Operating
8.2 Hide workflow and property windows by clicking on the highlighted pins.
33
8.3 Disconnect from the OCI
8.4 Connect with the OZW772 by checking the tick box and clicking “Continue”.
34
8.5 Switch between Bus topology and site topology views
9.1 Standard plant diagrams are available by default for “standard applications, however
being standard, they cannot be modified, and sometimes do not completely match the
installed plant. One timesaving solution can be to copy the “Standard” diagram and
paste it back to the project, thus making a “Custom” editable diagram with little effort.
For custom applications the plant diagrams must be produced in .bmp or .png format
35
10.0 Changing a Standard Plant Diagram
10.2 Right click the desired destination and paste the diagram
36
10.3 The user defined plant diagram is created, and can be renamed with a right click and
renaming in “Properties”
10.4 Right click on the diagram then click “Edit mode” to start the modification process.
37
10.5 Right click on the diagram to open the editing menu. In this menu you can-
a) Add a new data point, new text or a link to another diagram
b) Edit the background picture using Paint
c) Change the background picture to another image from you libraries
38
10.7 Double click on a data point to modify, such as text size, colours etc. Here you can see
the background and text colour are changed
39
11.0 User defined plant diagram
11.1 User defined plant diagrams can be imported from a previously prepared image such as
here where a Standard plant diagram for the Chiller(s) is not available
11.2 In the left hand window left click the location for the new diagram, then right click in the
right hand window and select New>Plant diagram
40
10.8 Name the new plant diagram, browse to the image and click Open>OK
10.9 The new plant diagram background image is inserted into the project. Data points, text,
links etc can be added as described above
41
11.0 Copy/Paste Plant diagrams
12.1 Plant diagrams can be copied from one device and pasted in to another. This is very
useful when more than one identical plant exists with a custom diagram. Copy AHU 1 diagram.
42
12.3 AHU 2 now has the same custom diagram as AHU 1. Data points are automatically
changed!
13.1 Plant diagrams can be exported to a library or other back-up location and may be re-
imported into the same or a different project.
43
14.0 User defined Pop cards
14.1 In a similar manner to creating user defined plant diagrams, user defined pop-cards can
be created. This can be useful for creating groups of frequently used data.
44
14.4 New pop card for boiler temperatures
Note: Once created, user defined plant diagrams and pop card
ONLY, will be visible when logged on as End User
15.1 To create an online trend click on the highlighted icon. The popup widow opens, details
of the trend can be entered
45
15.2 Click on the interval tab and set the trend sampling interval, then click “OK”.
15.3 Another window will open allowing navigation to select the data point(s) to be trended.
Right click on the data point and click “Add”. Close the window when complete.
15.4 Right click on the trend definition and click “Start trend logging”. You can give the trend
a name such as a date and click “OK”.
46
15.5 Trending is started and may be stopped when required with a right click on the definition.
47
16.0 Offline Trends – Only with Web Server
16.1 Right click the right hand window and select New>Offline trend definition
16.2 Complete name and details for the trend. Click “Next”.
48
16.3 Set the frequency and interval for the trend. Click “Next”.
16.5 Select and add required points to be trended and close the window when complete.
49
16.7 Files may be viewed/printed, firstly “Read trend log”
16.9 The file is now visible and can be exported to Excel or printed
50
17.0 History File Transfer – Only with Web Server
17.1 Message History Files are retrieved from the web server by clicking on the required file.
51
18.0 Web pages in the OZW772
18.1 Firstly verify that all required devices are included in the central unit device list
52
18.2 Save all plant diagrams as .tar files and close ACS
18.3 Open the web browser and login to the OZW772 using the address 192.168.250.1 (USB
connection-cannot be changed)
53
18.5 Generate device web pages
54
18.7 Click” Import”, Browse to the saved .tar file for AHU 1, click the file, then “Open”. Finally
click “Upload”.
18.8 Complete the Plant diagram properties window and click “OK”.
55
18.9 When importing standard graphics or copies of standard graphics, very often some data
is incorrectly presented due to multiple layers in the standard diagrams. These data need
to be corrected in Edit mode. Click “Edit”.
18.10 The filter data point was lost and needed to have the address reassigned. Click “OK” on
the inner window. Mostly the errors are overlaid data, requiring the faulty data point to be
deleted. When all corrections are completed, click “OK” in the main window.
56
18.11 Repeat the above until all graphics have been imported and adjusted as required.
18.12 Finally check and set all green limits for the energy indicators
57
19.0 ACS Alarm – Only with OZW771.xx
19.1 ACS Alarm must be started using the above icon, if not already running. When used on
projects ACS alarm should be start when the computer boots up by including it in the
start menu
19.2 A driver needs to be set for the COM port being used for communication with the plant,
in this example we are using COM5.
58
19.3 Double click in the Driver column next to the COM port being used and a dropdown box
will appear.
19.4 Scroll down and select the OZW771 driver then click the Supervise button to make the
connection, a green tick should now be in the Status column, and click OK.
RS 232
P2 M P1 M CE- CE+ LED3
T1 T2
S1S2
LED1
LED2
N - L
19.5 Check the system is running correctly without any alarms, then, on the OZW771, set
switch S2 to On.
59
19.6 Open the ACS Alarm log; you should have an empty screen.
19.7 Create an alarm; you should get a Pop-up as shown above. You can also see that the
alarm is already shown in the alarm log.
60
19.8 If you wish, by clicking in the Comment box in the alarm Pop-up, you can add a
comment.
61
19.10 Click Confirmation and then Close on the alarm Pop-up.
19.11 If you wish to make a change to the way alarms are received, click on the Tools>Settings
menu.
62
19.12 Here you can change the sound generated for an incoming alarm by browsing and
selecting a different WAV file or if no sound is required, deselect the sound check box..
You can select alarms to be printed on reception by ticking the select box and then
browsing to the required printer. The Pop-up alarm can also be disabled by deselecting
the check box.
19.13 If you wish to change the order or details displayed in the alarm log, this can be done in
Tools>Arrange columns.
63
19.14 By double clicking on an Alarm entry, an alarm can be Acknowledged, can have a Rectify
until (before) date tag added, or a Comment can be added.
64
19.16 A new window is opened
65
19.18 To add a “Rectify until” date click the corresponding button
19.19 Select a date from the calendar, and enter the time as required, then click OK
66
19.20 To enter a comment click on the Edited by button
67
19.21 Click OK when all actions have been carried out.
19.22 Details of the entries are shown in the corresponding columns in the alarm log, so long
as the columns in question have been selected for display.
68
20.0 Tips and Tricks for efficient Working with ACS790 V9
Screenshot
Description - In “Default device setting” dialogue, enter language, temperature unit, time
format and business card.
- Click on “Apply to all devices”
- “Ok” set the data automatically to all controllers in this project
- Also new devices which you add to the project get these settings
automatically
Comments - Text entries of KNX-devices may not be longer than 20 characters, given
by controller restrictions
- Special characters: Limited to ASCII characters
69
20.2 Restrict area for device search
Workflow Commissioning
Screenshot
70
20.3 Bus errors in “Error and Warning Viewer”
Screenshot …
Description - Not only configuration warnings are displayed in the Error and Warning
Viewer, but also fault information that is transmitted on the bus (KNX or
LPB)
- Examples:
o OCI700:The most critical bus alarm is listed
o OZW772 central units: Up to 10 bus faults are listed
Comments
Screenshot
Description - In the commissioning application (plant level), all devices are visible with
their current status
- Multiple or all devices can be selected (Shift+mouse, Ctrl+mouse) and their
status changed in one step
Comments
71
20.5 Maximum speed for commissioning with OCI700
Workflow Commissioning
Screenshot
Description - Always use the OCI700 connection for plant commissioning, in particular
for device search, write & read back of parameters (exception: parameters
of central units)
- Commissioning via central units such as OZW… is also possible, but much
slower in speed and limited in functionality.
Comments - The central units can now also be engineered in the office and are
contained in the same project as OCI700. Therefore, the same project can
be used for commissioning and plant operation.
- See also next topic “Commissioning of controllers and OZW…”
72
20.6 Commissioning of controllers and web server OZW…
Workflow Commissioning
Screenshot
Description - As OCI700 is the fastest connection to commission the controllers and the
OZW… need to be commissioned with a direct connection, those two tasks
can be executed in parallel
- However, it is important to keep a strict working sequence in order to avoid
inconsistent configurations!
- Engineering sequence (office or on site):
o Complete engineering of all controllers and their topology /
addresses
o Only once the step before is completed, create device list for OZW
- Commissioning sequence:
o Select two connections (OCI700 and OZW) in parallel
o Write down parameter sets
- ACS automatically uses the OCI700 connection for writing down the
controller configuration, the OZW connection for writing down the OZW
configuration.
Comments - The OZW configuration can ONLY be written in direct connection to the
OZW…, not via OCI700
- The controller configurations could also be written via OZW…, but this is
much slower (see topic “Maximal speed for commissioning with OCI700”)
- Before ACS790 V9, it was impossible to have several central units in one
project and also impossible to establish several simultaneous connections.
- However, with such simultaneous connections, additional care has to be
taken to manage the connections correctly.
73
20.7 Commissioning protocol and parameter set
Workflow Commissioning
Screenshot
Description - Reading parameter set and commissioning protocol in one step (time
saving)
- Data of commissioning protocol can be restored to current parameter set
and downloaded
Comments
Screenshot …
Description - For plants with several / many identical devices (typically room controllers
or room thermostats), there is a very efficient workflow:
o First, complete a first full device of its type, including full
parameterization.
o Then, copy the device in the topology application, if necessary
several times
o Last, if necessary, adapt the copies as much as necessary (e.g.
naming, maybe address, maybe selected settings)
- When the device is copied within the project, it carries automatically all
settings from its origin (of course except the address)
Comments - It is of course much less efficient, if you add first several copies of the
“empty” (non-parameterized or standard) device to the topology and then
make same or similar changes to all devices of the same type.
74
20.9 Efficient working on multiple projects with your own “reference device library”
Efficient working on multiple projects with your own “reference device library”
Benefit Massive time saving in office engineering across multiple projects
Screenshot …
Description - For “typical” applications in your field of experience, you will usually want
to reuse the same configurations, plant diagrams, possibly trends.
- Instead of re-creating those applications always from scratch, it’s
recommended to set up an own “reference device library” including the
most frequent device/application combinations
- For such a “reference device library”, we recommend creating a specific
project, e.g. called “reference device collection”, and store the most
frequent devices with all their parameterizations, popcards and plant
diagrams.
- If you want to use an existing reference device from your collection for a
new customer project, you can export it from the reference device
collection project and import it to the new project.
- The other way around, if you created a new device configuration in a real
customer project and want to store it for further use, you can export it from
the customer project and import it to the reference device collection.
- You can also store the exported reference device files (with a speaking
name) in a separate directory. By this, you can avoid the export step if you
did this already once, and you can import without closing the running
project.
- If you don’t need popcard and plant diagram in every case, you may still
add it to the reference device collection, as it is much faster to delete it
than to create it multiple times.
Comments - It is more efficient to create, store, manage, export and import individual
devices than complete projects.
- Nevertheless, you can also create, store, manage, export and import
entire projects (with many devices that may be also fully configured) in the
same way as mentioned above.
- Of course you can and should also share and exchange reference device
collections with your colleagues, either as individual devices
(export/import) or as entire collections (the entire project).
75
20.10 Pack & Go: One file for entire project
Description - All project relevant data is packed automatically to a ACS compatible file
- Data package can be directly saved or attached to an e-mail.
Comments
Description - Device assignment for plants with several identical devices (e.g:
RX…room controllers)
- The device assignment can now be done with the barcode reader, as it is
known from Desigo
- When installing the room controllers or thermostats, the bar codes are
taken from the device and stuck to the floor plan.
- Then, the device assignment can easily be done from one location without
moving from room to room
-
Comments - So far (before ACS V9.0), the device assignment had to be done by
putting each device in programming mode (by pushing a button on the
device). This led to a very high effort in larger buildings with many room
controllers or thermostats.
76
20.12 Engineering in both S and LTE mode.
If both S-Mode and LTE-Mode communication is required, then we highly recommend following this
sequence:
b) ACS Engineering: read back parameter settings, check and adjust them, set up
communication (zone addresses), configure device.
Why???
Warning: Once V9 is installed and projects opened all projects will be migrated and it will not
be possible to open them with V8 anymore.
2. Download
77
5. First Start Recommendations
Set a password for each level. Use a “company standard” Maintenance and Administrator password
Later changes
Any changes to the above settings can be made using the following menu, according to access level
78
6. Startup application
On Startup ACS can have a default application set, use Plant Operation for customer projects
79
21.0 Plants with previous version controllers
ACS790 v9.00 does not support offline engineering of older versions of Synco controllers, therefore,
on older plant, the first step after creating the project is to connect to the site. In the event that plant
files exist from a previous version of ACS, the following procedure is not required since ACS v9.00 can
open and convert files from ACS v8.xx
21.2 According to the plant, make selections from the “Read back data” window. If the plant is fully
operational select “Full read back”. If the plant doesn’t have a multi line topology, the search time can
be reduced by selecting “Advances device search options. In this window you can select “Device
connected or Area/line connected. Finally click “Continue”.
80
21.3 Device(s) are found and parameters uploaded.
81
21.5 Plant may be operated in the normal way.
82