Professional Documents
Culture Documents
Administration Manual: Ac500 Multionlinechange Tool
Administration Manual: Ac500 Multionlinechange Tool
3ADR023074M0201, 1, en_US
© 2017
Table of contents
1 AC500 MultiOnlineChange Tool........................................................................................................... 4
1.1 Introduction..................................................................................................................................... 4
1.2 Preconditions.................................................................................................................................. 4
1.3 Usage of the MultiOnlineChange Tool............................................................................................. 4
1.3.1 Overview...................................................................................................................................... 4
1.3.2 Step-by-step Guide...................................................................................................................... 5
1.4 Performing a Multi Download.......................................................................................................... 8
1.5 Verifying the Download/Online Change Success.......................................................................... 10
1.6 Editing the Master PLC................................................................................................................. 12
1.7 Multi Online Change...................................................................................................................... 12
1.8 Online Access............................................................................................................................... 12
1.9 Limitations in V2.x......................................................................................................................... 13
1.10 Modify wait time of MultiDownload/Online Change..................................................................... 13
2 Index..................................................................................................................................................... 16
1.2 Preconditions
n An Automation Builder project has been created and tested.
n A V2.3 IEC 61131-3 programming project in the master PLC has been created.
n 1 download has been issued to create all the files needed for the MultiOnlineChange tool.
The MultiOnlineChange tool may not work with the autoload option enabled in IEC 61131-3 program-
ming V2.3.
Please check your current autoload option in CODESYS V2.3 in => Project => Options => Load&Save
=> uncheck "Auto load" option.
In the Project text box, you can enter the project, which shall be distributed to all the PLCs. This can either
be done via opening a project file from the harddisk (in MOC stand-alone tool, see figure above) or via selec-
tion of the project, if the MOC was started from within the Automation Builder.
The field Path to CODESYS shows the path, where the file CODESYS.exe is available. This path is read
from the registry. If the path cannot be retrieved from the registry, the tool will immediately exit after start-up.
The field Default Path for *.ri files is an optional field. It is recommended that you define a folder here.
If the checkbox Ignore PLC if IP address is not available is checked, then all functions will ignore any PLC,
which does not reply to a ping command (the IP state of the PLC is shown by different background colours).
In normal operation, this checkbox should be checked. Otherwise the tool will try to access the defined IP in
any case.
The checkbox Start PLC program after Multi Download defines, if the program is started on each PLC after a
multi download.
Check the checkbox Create boot project, if a boot project should be created.
Change the default for the Max. timout for results.
The field Gateway Driver allows the selection of one of the following two options:
n ABB TCP/IP Level 2 AC
n TCP/IP
If the checkbox Execute commands with CODESYS GUI is checked, the CODESYS V2.3 GUI will open up
while the commands are executed. If the checkbox is unchecked, all commands will be handled in back-
ground and the user is not disturbed by any opening and closing CODESYS GUI window.
The checkbox "Execute commands with CODESYS GUI" is only visible in the Stand-Alone tool
The checkbox Update Firmware first shall be checked, if the user wants to update the PLC firmware before
sending any configuration to the PLC. The tool supports the update of up to 5 firmware files per PLC:
n The user has to enter the name of each firmware file in the text box Selected firmware file 1-5.
n The user has to select the type of any given firmware file (e.g. firmware, boot code or display) within the
related box File type.
n The timeout to download one file and to reboot the PLC after all files have been downloaded may be
extended in the box Activation delay(s).
For this tutorial, we do not start any operations at the moment. Instead, switch to the tabpage PLCs,
where we configure the PLCs we want to address.
Tabpage PLCs
In the figure, there are already 2 PLCs added to the table. Each row represents 1 PLC.
The first row of the table has an orange frame: Here the master PLC must be defined. The master or refer-
ence PLC is the PLC, which will be used for changing the project and testing it later, before a download or
online change is performed to the other PLCs in the table.
In the columns of the table, the following data is entered:
n Column IP address: Enter the IP address of the PLC.
n Column Directory: Define the directory, in which the *.ri file will be stored. Each PLC must have its own
directory. If you double-click a selected cell, a browse button is shown. By clicking this button, you can
browse a directory (if you want to do this, the directory must exist already). If you type a directory which
does not exist yet, it will be created later during multi download.
If you have defined a default folder for *.ri files on the tabpage Settings, this column will be completed
automatically by entering an IP address and confirming it with Enter or Tab. In this case, the defined
folder is the default folder and a subfolder with IP of the PLC (dots in the IP address are replaced by
"-").
n Column Comment: A comment for each PLC can be made here. This comment has no influence on the
operation of the MultiOnlineChange tool, but will be stored in the data XML file.
n Column Go online: This column contains a button for each PLC. By pressing this button you can start
IEC 61131-3 programming and log in to the PLC defined in this row.
n Column Show results will be explained in Ä Chapter 1.5 “Verifying the Download/Online Change Suc-
cess” on page 10.
Each IP address and each directory must be unique. Do not define the same IP or directory twice. If you
do so, you will get an error message when you try to perform an action.
The context menu of the table can be opened by right mouse click and contains the following functions:
n Add single PLC line: Adds 1 row to enter a new PLC.
n Delete selected PLC lines: Deleted selected rows.
n Add IP range: With this function, you can add a range of IP addresses by defining the start IP address,
the end IP address and the increment. E.g. if you select start IP 192.168.3.1 and end IP 192.168.3.10
and increment 3, the following IP addresses will be created:
– 192.168.3.1
– 192.168.3.4
– 192.168.3.7
– 192.168.3.10
n Clear Data: Delete all entries in the table.
n Check IPs: Perform a check, using the ping command to see, if the defined PLCs are available. After the
check, the IP addresses of all available PLCs are shown with green background, unavailable PLCs with
a red background. White background means state unknown.
Important!
A multi download should be the first action you perform (after the configuration) when you start using
the MultiOnlineChange tool. The multi download builds necessary infrastructure by performing the fol-
lowing tasks:
– It creates all directories defined in the PLC table (this is the first and only time when folder are cre-
ated).
– It copies the *.ri files to the folders.
Without folder and the corresponding *.ri files in them, online access and online change are not possible. In
fact, an online change will be executed even if folders or files are not available, but any PLCs without a
defined folder or *.ri file will be skipped.
An error message will be shown if there are:
Multi download (as well as online change) might take a long time, depending on the number of PLCs.
Each PLC requires approximately 15 seconds (without firmware update), i.e. 100 PLCs would require
about half an hour. Therefore the timeout parameter in the tabpage Settings has to be adapted
according to the project dimension.
Important!
If you change the IP addresses of a PLC or the folder where the corresponding *.ri file is stored, a
multi download should be performed again to rebuild the infrastructure (folders etc.).
n RED colored line: Perhaps the PLC is offline, the IP address is wrong or the project has a wrong target
(so download will be rejected immediately). In these special cases there is no detail information available
because a log file could not be uploaded.
If the button “Show Results” is pressed the following window is displayed:
Important!
Do not edit any PLC except the master PLC!
Examples:
“Logfile cannot be read” (red line in PLC list even though the download/change was successful).
“Online Change not possible” (PLC changes state from “run” to “stop” during Online Change, because the
wait time for loading the project was not sufficient).
To avoid these timeouts and the resulting errors the user can extend the wait times of the MultiOnlineChange
plug-in/tool. These times can be adapted in the template XML file “CmdTemplate.xml” by increasing the
values in the delay lines. The file has the following content:
<CmdTemplates>
...
<DownloadPLC>
device instance "MyDriver"
device parameter "Address" @@@ipAddress
device parameter "Port" @@@port
device parameter "Motorola byteorder" Yes
onerror continue
delay 1000
query off no
online login
delay 5000
online logout
waitevent ONL_LOGGEDOUT
query off no
online login
delay 3000
online filewrite @@@iniFileForLogging
waitevent ONL_FILEWRITTEN
online filewrite @@@uniqueIdent
waitevent ONL_FILEWRITTEN
online logout
waitevent ONL_LOGGEDOUT
query off ok
online login
waitevent ONL_PROGRAMLOADED
waitevent ONL_FILEWRITTEN
delay 3000
@@@bootproject online bootproject;
waitevent ONL_FILEWRITTEN
delay 10000
online logout
waitevent ONL_LOGGEDOUT
query off no
online login
delay 15000 @@@enable online run
delay 20000 online fileread @@@uploadLogFile
waitevent ONL_FILEREAD
delay 5000 online logout
file save
delay 1000
system "@@@handleRiBatch"
delay 2000
</DownloadPLC>
...
<OnlineChangePLC>
project loadcompileinfo "@@@plcDirectory\@@@projectName.ri"
device instance "MyDriver"
device parameter "Address" @@@ipAddress
device parameter "Port" @@@port
device parameter "Motorola byteorder" Yes
delay 10000 onerror continue
query off no
online login
delay 10000 online filewrite @@@iniFileForLogging
waitevent ONL_FILEWRITTEN
online filewrite @@@uniqueIdent
waitevent ONL_FILEWRITTEN
online logout
waitevent ONL_LOGGEDOUT
query off ok
delay 1000
online login
waitevent ONL_PROGRAMLOADED
delay 3000
@@@bootproject online bootproject
waitevent ONL_FILEWRITTEN
delay 10000
online logout
waitevent ONL_LOGGEDOUT
query off no
online login
delay 15000
online fileread @@@uploadLogFile
waitevent ONL_FILEREAD
delay 3000 online logout
file save
delay 1000
system "@@@handleRiBatch"
delay 2000
</OnlineChangePLC>
</CmdTemplates>
Each delay defines a wait time in milliseconds, which can be adapted by the user. As an example some of
the delays are emphasized above:
n The three emphasized delay times in tag <DownloadPLC> can be increased to ensure that the MOC
waits long enough for the log-file to be accessible after reboot before reading it.
n The four emphasized delay times in tag <OnlineChangePLC> can be increased to ensure that MOC
waits long enough for loading the project, logging in to PLC and reading the log-file.
2 Index