Getting Started AC500 V3
Getting Started AC500 V3
Getting started
AC500 V3 products
Table of contents
—
Table of contents
1 Getting started with AC500 V3 products....................................................................................................... 3
1.1 Introduction................................................................................................................................................ 3
1.2 Engineering software Automation Builder................................................................................................. 3
1.2.1 Installing Automation Builder...................................................................................................... 3
1.2.2 Licensing procedure................................................................................................................... 4
1.2.3 Set-up communication parameters in windows.......................................................................... 7
1.3 Hardware AC500 V3................................................................................................................................. 9
1.3.1 Configuration for example projects............................................................................................ 9
1.3.2 System assembly, construction and connection....................................................................... 11
1.4 Example project for central I/O expansion.............................................................................................. 12
1.4.1 Preconditions........................................................................................................................... 12
1.4.2 Create, set-up and save your AC500 V3 project..................................................................... 12
1.4.3 Configure the I/O module......................................................................................................... 17
1.4.4 Programming and compiling.................................................................................................... 21
1.4.5 Set-up the communication gateway......................................................................................... 30
1.4.6 AC500 V3 firmware installation and update............................................................................. 33
1.4.7 Log-in to CPU and download the program............................................................................... 35
1.4.8 Test the program...................................................................................................................... 36
1.4.9 Set-up visualization.................................................................................................................. 38
1.4.10 Create visualization................................................................................................................ 42
1.4.11 Enable web visualization........................................................................................................ 50
1.4.12 Reset the CPU....................................................................................................................... 54
1.5 Example project for remote I/O expansion with PROFINET................................................................... 56
1.5.1 Preconditions........................................................................................................................... 56
1.5.2 Set-up PROFINET controller.................................................................................................... 56
1.5.3 Set-up PROFINET device........................................................................................................ 59
1.5.4 Add remote I/O expansion to project........................................................................................ 63
1.5.5 Test the program...................................................................................................................... 67
1.5.6 Reset the CPU......................................................................................................................... 68
1.6 Further information on our AC500 portfolio............................................................................................. 69
2 Index............................................................................................................................................................... 70
—
1 Getting started with AC500 V3 products
1.1 Introduction
This document gives an overview of the steps for the first use of a PLC with AC500 V3 CPU
and describes:
● installation of the engineering software Ä Chapter 1.2 “Engineering software Automation
Builder” on page 3
● hardware needed for example projects Ä Chapter 1.3 “Hardware AC500 V3” on page 9
● setting up a first, simple project for a stand-alone CPU with central I/O expansion, including
visualization and web visualization Ä Chapter 1.4 “Example project for central I/O expan-
sion” on page 12
● commissioning a project for remote I/O expansion with PROFINET Ä Chapter 1.5 “Example
project for remote I/O expansion with PROFINET” on page 56
NOTICE!
Read safety instructions first
Read the safety instructions before first use of the products.
https://to.abb/eER6E15m
Fig. 1: Safety
instructions
Refer to our website to get details about the license model, the features of the editions and the
latest license information. new.abb.com/plc/automationbuilder/platform/software
Change the IP
address
1. Open Windows Control Panel. Click “Network and Internet
è Network and Sharing Center”.
2. Click Change adapter settings.
Table 2: Modules for example projects to get started with AC500 V3 PLC
Product name Type First project Second project
Ä Chapter 1.4 Ä Chapter 1.5
“Example project for “Example project for
central I/O expan- remote I/O expan-
sion” on page 12 sion with
PROFINET”
on page 56
PM5630- 2ETH AC500 V3 CPU x x
TB5620-2ETH terminal base for CPU x x
DA501 analog/digital mixed x x
input/output (I/O)
module
TU516-H terminal unit for I/O x x
module
CM579-PNIO PROFINET communi- -- x
cation module
Electrical con-
nection
In the training case, the control panel CP6607 is included. A control panel is not
needed for the example projects.
For testing the example project some inputs require to be connected as follows:
For the example projects, not all input switches and none of the potentiometers
included in training case are necessary.
You will need switch I1 for the example project for central I/O expansion.
You will need switch I5 for the example project for remote I/O expansion.
NOTICE!
Avoidance of electrostatic charging
PLC devices and equipment is sensitive to electrostatic discharge, which can
cause internal damage and affect normal operation. Observe the following rules
when handling the system:
– Touch a grounded object to discharge potential static.
– Wear an approved grounding wrist strap.
– Do not touch connectors or pins on component boards.
– Do not touch circuit components inside the equipment.
– If available, use a static-safe workstation.
– When not in use, store the equipment in appropriate static-safe packaging.
You can mount AC500 PLC either to DIN rail or to a metal plate. Here, we recommend to mount
on DIN rail.
1. Snap the terminal base onto DIN rail.
2. Snap the additional terminal units for I/O modules onto DIN rail.
3. Make the sensor/actuator wire connections according to the dedicated electronic module
you want to use. Provide external process power supply as required.
4. If required, make the fieldbus connections according to the dedicated master communica-
tion module you want to use.
5. Plug the appropriate electronic and I/O modules in the correct locations (processor
module, communication modules on terminal base, and eventually also communication
interface modules and I/O modules onto dedicated terminal units).
6. Connect a programming cable (Ethernet cable between ETH port of CPU and PC with
engineering software).
1.4.1 Preconditions
● Automation Builder is installed and licensed as, at least, basic edition Ä Chapter 1.2 “Engi-
neering software Automation Builder” on page 3.
● AC500 V3 CPU is assembled and connected to the PC.
3. Select “Projects”.
4. Select “AC500 project”.
5. Fill in project name.
6. Choose a location to save the project to.
7. Select “OK”.
8. Select “PLC - AC500 V3”.
9. Select the CPU according to your hardware set-up.
1. Double-click “PLC_AC500_V3”.
ð A tab opens in the editor view.
2. Select “CPU-Parameters Parameters”.
3. Under parameter “Check battery”, choose the value “Off” since there is no battery present
inside the CPU module.
4. Keep the default values for all other parameters.
1. Right-click “Application”.
2. Select “Add Folder”.
3. Type in "10 POUs". This is a name example. Here, the intention is to see this folder as a
last one.
The folder "10 POUs" is for program organization units (POU). POUs are objects of type
program, function or function block that are used to create a user program.
The suggested name convention is based on "Hungarian notation". A name prefix is describing
variable type: e.g., "x" = variable of type BOOL, "w" = WORD, "i" = INT (integer) etc. This
increases the code readability and is helpful for program analysis.
In the device tree, you see the objects “Task configuration” and “Task”. Both created automati-
cally with the project.
For this project you will use only one cycling task.
Priority This is how the CPU prioritizes the task, when more than one task is defined. Priority
0...15 = realtime tasks, priority 16 = non-realtime task.
Type In the CPU you can run tasks dependent on the demands of the process
Interval For cyclic tasks you can set the cyclical execution time. It is usually set in millisec-
onds with IEC time syntax
Watchdog To keep track of the time it takes to complete the task
Calls You can call in one or more program POUs in one single task
The PLC_PRG POU has been defined by default in ST (structured text) editor. Keep this setting
because of good visibility of the instructions at a glance and good handling for troubleshooting.
To optimize the project readability, you will work with the previously created folder "10 POUs"
and add the created subroutines (POUs) to this folder. The subroutines will be created in FBD
(function block diagram) editor.
1.4.4.3.2 Implementation
Create a new program POU in the project
5. Enter “_01_Assignment_NOT”.
6. Select “Program”.
7. Select “Function Block Diagram (FBD)”.
8. Select “Add”.
ð POU has been added.
4. Select “???” on the left side of the assignment, then select “...”.
5. Open the “Io Config_Globals_Mapping” mapping list and select “xDI_08_DA501_I1”.
6. Select “OK” to add this variable to the left side of the assignment connector.
7. Select “???” on the right side of the assignment connector and mark the "???".
8. Create a new local variable by typing in "xDrillerBroken1" which will replace the "???".
9. Press [Enter].
ð “Auto Declare” opens.
You see the written variable name and the data type BOOL. The scope is "VAR". It
means it is a local variable within this POU.
10. Select “OK” to accept the entries.
11. Drag and drop “Network” from the ToolBox to the down-arrow of network 1.
ð You added a network “2” below network 1.
1. Double-click “PLC_PRG”.
2. Select the first line in "PLC_PRG" and press [F2].
ð “Input Assistant” opens.
If you skip the compiling and select “Login”, the Automation Builder will automatically trigger
compiling in advance to logging-in.
3. Keep the default value in the IP address of the CPU or type in the current IP address, if
differs.
Network scan If you need to scan the network for the CPU or if you have multiple CPUs on the same network.
1. Right-click “PLC_AC500_V3” in the device tree.
2. Select “Communication Settings”.
3. Select “...”.
ð “Pick IP Address for "PLC_AC500_V3"” opens.
Check commu- If you need to check the communications settings or if you want to see more information about
nication set- the current selected CPU.
tings
A very new CPU has no pre-installed firmware. To guarantee the authenticity of delivered
AC500 firmware, V3 CPUs are delivered with a boot loader only. You need to download a valid
firmware to the CPU. After download, the functionality of the CPU is given.
An Automation Builder project with an AC500 V3 CPU is open.
CPU is in "stop" mode or shows uPdAtE (update) on the display.
After update the CPU shows either donE or StoP on the display
NOTICE!
Do not disconnect the power supply during the update process! The PLC
could be damaged.
ð StoP indicates a restart has been performed by the CPU. When donE is displayed
sometimes it is necessary to re-boot the CPU manually, e.g., by powering-off. Manual
re-boot might be, e.g., for some older CPU versions or if downgrading to an older firm-
ware version according to application settings.
The CPU display shows "stop" after re-boot. The update process is finished.
5. If necessary, refresh the version information by switching to another tab and back.
ð Successful firmware update:
Behavior of
LEDs during
firmware update
Generally, if the CPU is in "run" mode, i.e. in program execution mode, a down-
load will always cause the mode change to "stop". In stop mode the CPU is not
controlling the system!
Always, after selecting the "Login" command, read carefully the dialog box text
to ensure that you are aware of the CPU’s behavior after the command confir-
mation.
5. Select “Add”.
ð You added the objects “VisualizationManager” and “VISU-TASK” to the device tree.
2. Select “Settings”.
3. Open the drop-down menu “Selected style”.
4. Select “Default, x.x.x” (exemplary).
5. Open the drop-down menu “Selected language”.
6. Select “en” for English language in the visualization.
7. Enable “Visible” for advanced settings.
8. Keep the file transfer to enable the visualization on the PLC (mandatory for web server
function Ä Chapter 1.4.11 “Enable web visualization” on page 50).
5. Type in "PLC_VISU".
6. Select “Add”.
ð A tab opens in the editor view.
Fig. 4: PLC_VISU_tab
The name "PLC_VISU" has been chosen, because it is the default name for a
home screen in a web visualization.
If you have more than one visualization object in your project, it will be useful to
choose another name, e.g. "_01_Assignment_NOT_v". And to choose
"PLC_VISU" as a home screen to access all available visualization screens.
The name of a visualization object can be modified afterwards.
2. Select “ToolBox”.
2. Select “ToolBox”.
3. Select “Basic”.
4. Drag and drop the line. Then drag the line to the needed length.
5. Follow the same procedure to create the other shapes and labels.
2. Select “ToolBox”.
3. Select “Lamps/Switches/Bitmaps”.
4. Drag and drop “Lamp” to the screen.
5. Adapt the size, if required.
7. Double-click on “Variable” and select “...” to select a variable from the list.
If you skip the compiling and select “Login”, the Automation Builder will automatically trigger
compiling in advance to logging-in.
ð The VisualizationManager editor and there the tab “Visualizations” opens. All screens
and dialog elements created in the project are visible.
Here, you can select which screens are enabled or disabled for web visualization.
If you want to select another screen as a start visualization, you must modify the adequate
parameter in the webvisu.htm file: <param name="STARTVISU" value="PLC_VISU">
If you skip the compiling and select “Login”, the Automation Builder will automatically trigger
compiling in advance to logging-in.
Table 5: Behavior of variables of type VAR (local or global) and variables of type PERSISTENT
RETAIN
VAR VAR PERSISTENT RETAIN
After online command “Online change” no change no change
After online command “Download” initialization no change
After online command “Reset warm” initialization no change
After online command “Reset cold” initialization no change
After online command “Reset origin” initialization initialization
After power supply off initialization no change
Complete reset To do a complete reset of the CPU thereby erasing the application from the RAM and flash
of the CPU EEPROM do the following.
1.5.1 Preconditions
● Automation Builder is installed and licensed as, at least, standard edition Ä Chapter 1.2
“Engineering software Automation Builder” on page 3.
● AC500 V3 CPU is assembled and connected to the PC.
● Configuration and programming of this example project will be made in the existing example
project for central I/O expansion Ä Chapter 1.4 “Example project for central I/O expansion”
on page 12.
● CM579-PNIO communication module is inserted in terminal base and connected to the
PLC.
● CI502-PNIO communication interface module is inserted in terminal unit and connected to
the PLC.
Run on configuration This parameter will prohibit the PLC from running if the CM579-PNIO
fault has a configuration error/fault.
Bus behavior This parameter sets how the data from the bus flows in/out of the
CM579-PNIO.
3. Select “Status”.
ð This opens the bus controller status and gives a basic status overview.
4. Select “Information”.
ð This page contains general information about the CM579-PNIO.
5. For the example project, you can keep the default settings.
3. Select “General”.
4. Here, you can set-up the way, IP addresses are distributed out to the industrial bus net-
work. You can even set, what IP-address and DNS name (station name) the PROFINET
controller has.
For the example project, keep the default settings.
1. Double-click “CI502_PNIO_Device”.
ð A tab opens in the editor view.
2. Select “General”.
If the node has the same device address (the last two digits of the device name)
as set by means of the rotary switches on the module, all the node parameters
will be loaded automatically upon initialization scan of the CI50x module. This
allows, e.g., the module exchange without an engineering tool.
1. Double-click “CI502_IO”.
5. Fill in "_30_PNIO_test".
6. Select “Program”.
7. Select “Function Block Diagram”.
4. Select “???” on the left side of the assignment, then select “...”.
5. In “IoConfig_Globals_Mapping” list, select “xDI_08_CI502_I5”.
6. Select [OK] to add this variable to the left side of the assignment connector.
7. Select “???” on the right side of the assignment, then select “...”.
8. In “IoConfig_Globals_Mapping” list, select “xDO_08_CI502”.
9. Select [OK].
If you skip the compiling and select “Login”, the Automation Builder will automatically trigger
compiling in advance to logging-in.
Table 6: Behavior of variables of type VAR (local or global) and variables of type PERSISTENT
RETAIN
VAR VAR PERSISTENT RETAIN
After online command “Online change” no change no change
After online command “Download” initialization no change
After online command “Reset warm” initialization no change
After online command “Reset cold” initialization no change
After online command “Reset origin” initialization initialization
After power supply off initialization no change
Complete reset To do a complete reset of the CPU thereby erasing the application from the RAM and flash
of the CPU EEPROM do the following.
—
2 Index
A
Automation Builder
getting started . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
C
communication parameters
in Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Compiling a project . . . . . . . . . . . . . . . . 30, 48, 52, 65
E
example project with Automation Builder and
AC500 AC500 V3 products . . . . . . . . . . . . . . . 12, 56
I
IP address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
L
log-in to a CPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
P
PLC_PRG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
T
testing a program . . . . . . . . . . . . . . . . . . . . . . . 36, 67
V
visualization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
VisualizationManager . . . . . . . . . . . . . . . . . . . . . . . 38
—
© Copyright 2020 ABB.
We reserve all rights in this document and in the information contained therein. Reproduction, use or disclosure to third parties without express
authority is strictly forbidden.