You are on page 1of 102

Software Description

Advant Controller 31
Intelligent Decentralized
Automation System
Installation /
Special Functions

07 KP 90

07 KT 97

07 DC 92

07 AC 91

ABB Schaltund Steuerungstechnik

Contents
1

907 AC 1131 installation ........................................................................................... 1-1

1.1

Installation disc...................................................................................................... 1-1

1.2
1.2.1

Necessary files...................................................................................................... 1-1


Important parameters in the INI file AC1131.INI................................................... 1-4

1.3

Uninstalling the software ....................................................................................... 1-6

1.4
1.4.1
1.4.2
1.4.3
1.4.4

Installing ARCNET cards using Windows NT........................................................ 1-7


ARCNET card for desktop PC using Windows NT ............................................... 1-7
ARCNET PC card for notebooks using Windows NT (without PCMCIA cards) .... 1-8
ARCNET PC card for notebooks using Windows NT (with PCMCIA cards) ......... 1-10
Uninstalling the ARCNET driver ........................................................................... 1-11

1.5
1.5.1
1.5.2

Installing ARCNET cards using Win95/98 SE ....................................................... 1-12


ARCNET card for desktop PC using Win95/98 SE............................................... 1-12
ARCNET card for notebook PC using Win95/98 SE ............................................ 1-13

Special functions of the software 907 AC 1131 ...................................................... 2-1

2.1

Whats new in version V4.1 ................................................................................... 2-1

2.2

Creating a "new" project for the controller 07 KT 97 ............................................. 2-2

2.3
2.3.1
2.3.2
2.3.3

Entering the PLC into the controller configuration ................................................. 2-16


How to enter the PLC into the controller configuration ......................................... 2-17
Changing the PLC for a project ............................................................................ 2-18
Configuration files for the controllers .................................................................... 2-19

2.4
2.4.1
2.4.2

Menus which are not described in the operating instructions ................................ 2-22
Menus in the main menu "Online" ........................................................................ 2-22
The PLC browser ................................................................................................. 2-24

2.5

Peculiarities for forcing and overwriting in version V4.1"....................................... 2-27

2.6

Peculiarities of batch operation in version V4.1..................................................... 2-30

2.7
2.7.1
2.7.2
2.7.3

Notes concerning frequently asked questions....................................................... 2-32


Project protection for logging in to the controller .................................................. 2-32
RETAIN variables - note for program change....................................................... 2-33
Creating and modifying your own library .............................................................. 2-38

907 AC 1131/Issue: 07/00

Contents

Importing projects from 907 PC 331 ........................................................................ 3-1

3.1

Introduction............................................................................................................ 3-1

3.2
3.2.1
3.2.2

Creating the ASCII files for the program and variables using 907 PC 331 ............ 3-1
Creating an ASCII file of the variables list............................................................. 3-2
Creating an ASCII file of the program (IL)............................................................. 3-4

3.3
3.3.1
3.3.2
3.3.3
3.3.4

Importing the programs to 907 AC 1131................................................................ 3-6


Sequence of steps to import the program to 907 AC 1131 ................................... 3-6
Importing the variables to 907 AC 1131................................................................ 3-7
Importing the programs to 907 AC 1131 ............................................................... 3-8
Importing the step chains...................................................................................... 3-9

3.4

Reworking programs.............................................................................................. 3-10

Notes concerning the OPC server ........................................................................... 4-1

4.1
4.1.1
4.1.2

Installing the OPC server....................................................................................... 4-1


Server settings...................................................................................................... 4-2
Selecting the variables in the programming software 907 AC 1131...................... 4-5

4.2
4.2.1
4.2.2
4.2.3
4.2.4

Testing the OPC server ......................................................................................... 4-7


Testing the starting behavior and parallel operation ............................................. 4-7
Preparing the dynamic tests ................................................................................. 4-8
Testing using VisiWin client .................................................................................. 4-9
Testing using WIZCON client................................................................................ 4-11

4.3
4.3.1
4.3.2
4.3.3
4.3.4

Test results ............................................................................................................ 4-13


VisiWin test row 1 ................................................................................................. 4-13
VisiWin test row 2 ................................................................................................. 4-16
Wizcon test row 1 ................................................................................................. 4-20
Wizcon test row 2 ................................................................................................. 4-23

Index ........................................................................................................................... I

Contents

907 AC 1131/Issue: 07/00

907 AC 1131 installation

1.1

Installation disc
Insert the CD into your CD-ROM drive and follow the setup instructions.

Caution:
If you want to use programming via ARCNET, you must install the ARCNET card first.
The installation of the ARCNET driver is described in section 1.3.

1.2

Necessary files
With the installation the following files for 907 AC 1131 are installed on your PC:
Directory 907 AC 1131:
AC1131.EXE
AC1131.HLP
AC1131.CNT
SPEZ_S90.HLP
SPEZ_S90.CNT
Bibliotheken.HLP
Bibliotheken.CNT
Base_S90.HLP
Base_S90.CNT
RCOM_S90.HLP
RCOM_S90.CNT
ARCNET_S90.HLP
ARCNET_S90.CNT
CS31_S90.HLP
CS31_S90.CNT
COM_S90.HLP
COM_S90.CNT
Datenablage_S90.HLP
Datenablage_S90.CNT
SystemInfo_S90.HLP
SystemInfo_S90.CNT
PROFIBUS_S90.HLP
PROFIBUS_S90.CNT
SYSTEM40.HLP
SYSTEM40.CNT
D2HTLS32.DLL
ABB.DFR
ABB_DFR.BMP
BROWSERINIFILE.INI
AC1131.INI
CoDeSysOPC.EXE
OPCCFG.EXE
OCS_PROXY.DLL

907 AC 1131/Issue: 07/00

executable file of 907 AC 1131


help file for 907 AC 1131 operating instructions
required for help file
help file for special functions
required for help file
help file providing library overview
required for help file
help file for basic block library
required for help file
help file for RCOM library
required for help file
help file for ARCNET library
required for help file
help file for CS31 library
required for help file
help file for COM library
required for help file
help file for data storage library
required for help file
help file for system information library
required for help file
help file for PROFIBUS library
required for help file
help file for system technology
required for help file
DLL for online help
example print layout
ABB logo for print layout
ini file for PLC browser
ini file for AC1131.EXE (copy of WINNT)
OPC server
gateway configurator for OPC server
DLL for OPC server

1-1

Installation

Subdirectory Library:
IEC_S90_V41.LIB
IECSFC_S90_V41.LIB
Base_S90_V41.LIB
RCOM_S90_V41.LIB
ARCNET_S90_V41.LIB
CS31_S90_V41.LIB
COM_S90_V41.LIB
Datenablage_S90_V41.LIB
SystemInfo_S90_V41.LIB
Coupler_S90_V41.LIB
PROFIBUS_S90_V41.LIB
ABB-BIB4.LIB
*.BMP
AUSLAST.EXP
FEHLER_M.EXP
SY_CONST.EXP
STEP_VAR.EXP
KT98_ONB.EXP
KT97_DEA.EXP
KT97_ONB.EXP
KT96_ONB.EXP
KT95_ONB.EXP

standard IEC library for series 90


IEC sequencial steps for series 90
basic block library for series 90
RCOM/RCOM+ block library for series 90
ARCNET block library for series 90
blocks for CS31 bus for series 90
blocks for serial communication for series 90
blocks for SMC and FLASH for series 90
blocks for system information for series 90
basic coupler routines library for series 90
PROFIBUS library for series 90
ABB block library (in V4.1 for importing a project)
bitmaps for IEC function blocks
import file for capacity utilization flag
import file for error flag
import file for system constants
import file for importing step chains from 907 PC 331
import file for 07 KT 98 / binary and analog I/Os
import file for 07 KT 97 / only digital inputs/outputs
import file for 07 KT 97 / binary and analog I/Os
import file for 07 KT 96 / binary and analog I/Os
import file for 07 KT 95 / binary and analog I/Os

Subdirectory Library \ Save_V40:


STANDARD.LIB
STANDARD.OBJ
IECSFC.LIB
ABB-BIB4.LIB
RCOM_V40.LIB
RCOM_V40.OBJ
CIF104.LIB
PROFI_40.LIB

907 AC 1131 standard library


OBJ file of STANDARD.LIB
library for IEC sequential function chart (SFC)
library for ABB blocks V4.0
library for RCOM/RCOM+ blocks
library for OBJ file of RCOM/RCOM+ blocks
basic coupler routines library
PROFIBUS library

Subdirectory Library \ PLCCONF


BrowserIniFile.TRG
CPUABB.SEL
*.CON
*.DIB
*.GSD
*.GSE
*.GSG

command file for PLC browser


additional file for PLC selection
configuration files for PLCs
logos for PROFIBUS
modules master data files for PROFIBUS, default
modules master data files for PROFIBUS, english
modules master data files for PROFIBUS, german

Subdirectory PROJEKTE
BSPDT.PRO
AMPEL.PRO
ABB_LEER.PRO

example program for editors


example program from documentation
empty project for importing projects created with
907 PC 331

The subdirectory PROJEKTE contains further additional subdirectories with example


projects, e.g. for the connection of terminals.

Installation

1-2

907 AC 1131/Issue: 07/00

Files in directory: WINNT\SYSTEM32 (for operating system Windows NT from V4.0


onwards)
or WINDOWS/SYSTEM (for operating system Windows 95 or Windows 98 SE)
GATEWAY.EXE
GATEWAY for communication DLL
COMMSYM.DLL
communication DLL
COMMUSR.DLL
communication DLL
GCLIENT.DLL
communication DLL
GDRVBASE.DLL
communication DLL
GDRVSTD.DLL
communication DLL
GSYMBOL.DLL
communication DLL
GUTIL.DLL
communication DLL
GDRVABBARCNET.DLL
ABB ARCNET driver DLL
GDRVABBRS232.DLL
ABB RS232 driver DLL
ARCNET32.DLL
ARCNET DLL for Windows NT4.0
GARCNET3F4F.DLL
ARCNET DLL for 3F and 4F protocols
Subdirectory ARCNET\ARCNET_NT\Treiber: (SOHARD ARCNET NT driver)
FARC
ARCNET NT driver V4.0 (SOHARD)
SIMPLE.C
licence: 34687-2-304-2710-0105877
UARCINST.DLL
SIMPLE.EXE
FARC.H
ARCNET.HLP
OEMSETUP.INF
FARC.SYS
PCM20_NT.REG
registry file for PCMCIA card
Subdirectory ARCNET\ARCNET_NT:
ARCNET32.DLL
ARCNET DLL for Windows NT4.0
Subdirectory ARCNET\ARCNET_95_98\Treiber: (SoHard ARCNET 95/98 drivers)
arcread.exe
DOS test program for telegram reception
arcsend.exe
DOS test program for telegram transmission
arcread.cpp
source of arcread.exe
arcsend.cpp
source of arcsend
farc.h
header file for drivers
farc20.reg
registry file for drivers
install.bat
batch file for installation
readme.txt
help file
Install.pif
required for installation
FARC20.VXD
ARCNET driver for Windows 95 / 98
ARCNET32.DLL
ARCNET DLL for Windows 95 and Windows 98 SE
Subdirectory ARCNET \ ARCNET_95_98 \ PCMCIA:
findpcm20.exe
auxiliary program for I/O address
pcm20.inf
required for installation
pcm20.vxd
PCMCIA card driver for Windows 95 / 98
pcmenabler.exe
readme.txt
Notes concerning PCMCIA card installation

907 AC 1131/Issue: 07/00

1-3

Installation

1.2.1 Important parameters in the INI file AC1131.INI


The initialization file AC1131.INI for the 907 AC 1131 software is written to the system directory
WINNT\System32 (for operating system Windows NT from V4.0 onwards)
or
WINDOWS\System (for operating system Windows 95 / 98 SE)
together with the software. A copy of the file is written to the program root directory of the
907 AC 1131 software.

Caution:
In order to keep the capability of undoing faulty modifications always create a copy of
the file before performing any modifications to this file.
Most of the parameters are automatically updated or entered together with the 907 AC 1131
software. Parameters which are relevant for the user are described below. These parameters
are:
- InitZero=No
- DebugCode=Yes
- KT94WaitTime=2200
- UpdateRate=200
- Autoload=Yes
- LibraryDir=c:\Programme\AC1131\library
- ProjectsDir=c:\Programme\AC1131\Projekte
- ImportExportDir=c:\Programme\AC1131\Library\
- DocuframeDir=c:\Programme\AC1131
- TraceDir=c:\Programme\AC1131\Projekte
- WatchDir=c:\Programme\AC1131\Projekte
- Project0=c:\Programme\AC1131\Projekte\Ein_Ausgang.pro
- Project1=c:\Programme\AC1131\Projekte\Bspdt.pro
- Project2=c:\Programme\AC1131\Projekte\Ampel.pro

Parameter InitZero:
If InitZero=Yes, initialization code is created for all variables (including all variables which are
initialized by zero or FALSE). In this case the program code becomes considerably larger. If
InitZero=No, initialization code is only created for variables which are initialized by TRUE or not
equal to zero. When the controller is started the non-buffered memory areas are initialized by
zero (see volume 3 - System technology, Initialization and buffering of data areas).
Default value: InitZero=No

Installation

1-4

907 AC 1131/Issue: 07/00

Parameter DebugCode:
Code for which all the online functions such as breakpoint, single step, etc. are possible is only
created if the setting is DebugCode=Yes. If the parameter is set to DebugCode=No the program
code is becoming smaller but the program cannot be tested any more using all online functions.
Default value: DebugCode=Yes

Parameter KT94WaitTime:
The parameter KT94WaitTime is used to set the wait time until a communication error is
reported in case of serial communication disturbances.
Default value: KT94WaitTime=2200 (corresponds to approx. 10 sec.)

Parameter UpdateRate:
The parameter UpdateRate is used to set the refresh time in milliseconds for the variables.
Default value: UpdateRate=200 (smaller values are not possible)

Parameter Autoload:
If Autoload=Yes the project opened last is automatically opened again when the 907 AC 1131 is
started. For batch operation on read-only projects this parameter must be set to Autoload=No
(refer to section "Peculiarities of batch operation in version V4.1").
Default value: Autoload=Yes

Parameter LibraryDir:
This parameter is used to set the library path. The parameter is set to
"Projekt/Optionen/Verzeichnisse/Bibliotheken".
Default value: LibraryDir=c:\Programme\AC1131\Library

Parameter ProjectsDir:
This parameter is used to set the project path.
Default value: ProjectsDir=c:\Programme\AC1131\Projekte

Parameter ImportExportDir:
The parameter ImportExportDir is used to set the path for *.exp files.
Default value: ImportExportDir=c:\Programme\AC1131\Library\

Parameter DocuframeDir:
The parameter DocuframeDir is used to set the path for the online help system files.
Default value: DocuframeDir=c:\Programme\AC1131

907 AC 1131/Issue: 07/00

1-5

Installation

Parameter TraceDir:
The parameter TraceDir is used to set the path for trace files.
Default value: TraceDir=c:\Programme\AC1131\Projekte

Parameter WatchDir:
The parameter WatchDir is used to set the path for the watch lists *.WTC.
Default value: WatchDir=c:\Programme\AC1131\Projekte

Parameter Project0..Project9:
The file names of the projects opened last and their paths are entered to the parameters
Project0 ..Project8. If Autoload=Yes the project in parameter Project0 is loaded when starting
the 907 AC 1131 software.
Example: Project0=c:\Programme\AC1131\Projekte\Ein_Ausgang.pro

Note:
The parameters Project0.. can be deleted in case a project cannot be opened any
more.

1.3

Uninstalling the software


Before you can uninstall the 907 AC 1131 software you must exit the software and the gateway.
In order to close the gateway, click with the right mouse button on the 907 AC 1131 icon in the
status bar of the operating system and select "Exit".
To uninstall the software in Windows NT:
- select "Start" => "Settings" => "Control Panel"
- double click on the "Software" icon
- select "AC1131"
- click on the "Add/Remove" button and confirm the uninstall confirmation dialog with "Yes".
All files and directories created during the installation are deleted. If you have modified any
directories and / or their content, these directories are not deleted.

Installation

1-6

907 AC 1131/Issue: 07/00

1.4

Installing ARCNET cards using Windows NT

1.4.1 ARCNET card for desktop PC using Windows NT


For programming a PLC via ARCNET using Windows NT 4.0, SoHards FARC E3 card (ISA
card) and FASRC.SYS driver can be used.
On the card, set the I/O range and the interrupt IRQ according to the enclosed documentation.

Note:
The factory settings are applicable.
(I/O address = 120 hex, IRQ = 10, KOAX mode, 2.5 MHz).
Copy the content of the 907 AC 1131 programming software subdirectory
ARCNET\ARCNET_NT\Treiber
from your PC to an empty floppy disk without any subdirectory!!!
Copy the file ARCNET32.DLL in the 907 AC 1131 programming software subdirectory
ARCNET\ARCNET_NT
to the operating system subdirectory System32 (e.g. WINNT\SYSTEM32)!
For installing the driver proceed as follows:
1. Execute Settings=>Control Panel=>Network.
2. In the Control Panel select "Network".
3. Select "Add" => Floppy disk A:.
(The installation routine does not permit subdirectories !)
4. Select the option "ISA card", "COM20020".
5. The following settings ("Properties") match with the factory settings:
- Interrupt:
- IO address:
- Mem address:
- Controller:
- Driver:
- Licence number:

IRQ10
120 hex (decimal 288)
0
COM20020
FARC
ABB number: 34687-2-304-2710-0105877
(or request own number from SoHard)

After restarting the computer the settings are applied and the communication should work.
The following problems can occur:
1. The IRQ or the I/O range set is already used by another hardware device on your PC.
This can be checked using:
"Programs" => "Administrative Tools" => "Windows NT Diagnostics" => "Resources"
2. The used IRQ is configured for PCI interrupts and not for ISA interrupts. This setting is
performed in the BIOS.

907 AC 1131/Issue: 07/00

1-7

Installation

1.4.2 ARCNET PC card for notebooks using Windows NT (without PCMCIA cards)
For programming the PLC via ARCNET using a notebook Contemporary Controls PCMCIAARCNET adapter PCM 20E can be used (can be obtained from SoHard).
SoHards NT (ISA card!!) driver FARC.SYS is used because Contemporary Controls does not
provide a NT driver. During the installation the I/O range and IRQ which NT has assigned to the
PCMCIA slot must be predetermined for the driver. The ISA card driver is not able to perform a
"normal" PCMCIA configuration with the PCMCIA controller. The driver assumes that the
PCMCIA controller can predetermine standard settings for the card.
Proceed as follows if your PC is not yet equipped with PCMCIA cards:
Copy the content of the 907 AC 1131 programming software subdirectory
ARCNET\ARCNET_NT\Treiber
from your PC to an empty floppy disk without any subdirectory!!!
Copy the file ARCNET32.DLL in the 907 AC 1131 programming software subdirectory
ARCNET\ARCNET_NT
to the operating system subdirectory System32 (e.g. WINNT\SYSTEM32)!
Switch-off the computer, insert the PCMCIA card and connect the adapter.
After switching-on the PC and booting Windows NT, select:
"Settings" => "Control Panel" => "PC Card (PCMCIA)".
Now the card should be detected in one of the PCMCIA slots as:
"Contemporary Control Systems, Inc. PCM20 ARCNET Adapter".
If the card is not detected automatically the card or the PCMCIA controller is faulty.
In the second step some settings in the registry must be entered which tell the SoHard ARCNET
ISA card driver, that the inserted card is a PCMCIA card. For this purpose, a registry file
"PCM20_NT.REG" is provided which contains the most settings correctly. If you double-click on
this file in the Windows NT Explorer you should receive the message
"The information from C:\...\PCM20_NT.REG was entered in the registry".
Restart NT so that the settings become valid. After starting select:
"Settings" => "Control Panel" => "PC Card (PCMCIA)".
In
"Socket State" => "Properties" => "Resources"
the parameters should be set as follows:
- Interrupt Request:
10
(Example)
- I/O Range:
300-30F
(Example)

Installation

1-8

907 AC 1131/Issue: 07/00

The values 10 and/or 300-30F are probably different in your system. Note down the values. It
does not matter that it is displayed in
"Socket State" => "Properties" => "Drivers"
that no driver was installed for this device.
If in
"Socket State" => "Properties" => "Resources"
nothing is displayed, your Laptop or your PCMCIA controller is not able to predetermine
standard settings for a PCMCIA card for which no driver was loaded.
In this case the ARCNET PCMCIA controller cannot be used in your system! In order to rule out
errors you should check and if necessary repeat the steps described above. Please contact
your PC supplier.
With the following tested laptops the ARCNET PCMCIA adapter did not work:
- Gateway 2000 Solo
- ...
Now install the Farc driver performing the same procedure as for the ISA card (steps 1-5). For
the bus type you must select "ISA", not PCI, PCMCIA, PnP or anything else. For the I/O
address enter the I/O address assigned by NT (in the example above: 300 hex) and also the
IRQ (in the example above: 10)! For the Mem memory area select 0, for the controller type
select "COM20020" as you did for the ISA card, for the driver select FARC and enter your
licence number.
1. Select "Settings" => "Control Panel" => "Network".
2. Double-click on the "Network" icon in the control panel.
3. Select "Add" => Floppy disk A:.
4. Select the option "ISA card", "COM20020".
5. Enter the settings ("Properties"):
- Interrupt IRQ:
IRQ assigned by NT!!! (in the example: 10)
- I/O address:
I/O address assigned by NT!!! (in the example: 300hex)
- Mem address:
0
- Controller:
COM20020
- Driver:
FARC
- Licence number:
ABB number: 34687-2-304-2710-0105877
(or request own number from SoHard)
After restarting the computer the settings are applied and the communication should work.

907 AC 1131/Issue: 07/00

1-9

Installation

1.4.3 ARCNET PC card for notebooks using Windows NT (with PCMCIA cards)
The installation is described for the Toshiba notebook T460CDX.
Copy the content of the 907 AC 1131 programming software subdirectory
ARCNET\ARCNET_NT\Treiber
from your PC to an empty floppy disk without any subdirectory!!!
Copy the file ARCNET32.DLL in the 907 AC 1131 programming software subdirectory
ARCNET\ARCNET_NT
to the operating system subdirectory System32 (e.g. WINNT\SYSTEM32)!
For installing the PCMCIA ARCNET card proceed as follows:
1. Uninstall the AVM card (FRITZ modem card) if necessary
The AVM card assigns IRQ5. For uninstalling use SETUP from the CD supplied with the AVM
card.
2. Determine and enter the assignment for ARCNET
- Switch-off the computer.
- Remove all PCMCIA cards with the exception of the ARCNET card.
- Switch-on and reboot the computer.
- Check the assignment for PCMCIA ARCNET (IRQ, I/O).
"Settings" => "Control Panel" => "PC Card" => "Contemporary Control Systems" =>
"Properties" => "Resources"
3. Now some settings in the registry must be entered which inform the SoHard ARCNET ISA
card driver that the inserted card is a PCMCIA card. For this purpose, a registry file
"PCM20_NT.REG" is provided which contains the most settings correctly. If you double-click on
this file in the Windows NT Explorer you should receive the message
"The information from C:\...\PCM20_NT.REG was entered in the registry".
4. Now install the Farc driver performing the same procedure as for the ISA card (steps 1-5).
For the bus type you must select "ISA", not PCI, PCMCIA, PnP or anything else. However, for
the I/O address enter the I/O address assigned by NT (in the example above: 300 hex) and also
the IRQ (in the example above: 10)! For the Mem memory area select 0, for the controller type
select "COM20020" as you did for the ISA card, for the driver select FARC and enter your
licence number.
1. Select "Settings" => "Control Panel" => "Network".
2. Double-click on the "Network" icon in the control panel.
3. Select "Add" => Floppy disk A:.
4. Select the option "ISA card", "COM20020".
5. Enter the settings ("Properties"):
- Interrupt IRQ:
IRQ assigned by NT!!! (in the example: 10)
- I/O address:
I/O address assigned by NT!!! (in the example: 300hex)
- Mem address:
0
- Controller:
COM20020
- Driver:
FARC
- Licence number:
ABB number: 34687-2-304-2710-0105877
(or request own number from SoHard)

Installation

1-10

907 AC 1131/Issue: 07/00

5. Switch off the PC.


- Insert the other cards again.
- Switch-on and boot the PC.
6. Set the soundcard interrupt to interrupt level 5 (current setting is 11).
"Programs" => "Toshiba Utilities" => "Hardware Setup" => "Hardware Options" =>
"Sound System"
7. Restart the system.
8. Set network Dlink to IRQ 3 and I/O range 260.
"Control Panel" => "Network" => "Adapter"
9. Remove Remote Access Service!
"Control Panel" => "Network" => "Services"
The settings are valid after restarting the computer. After this installation the network as well as
the ARCNET worked with the Toshiba T460CDX.

1.4.4 Uninstalling the ARCNET driver


To uninstall the driver perform the following steps:
1. Go to
"Settings" => "Control Panel" => "Network".
2. Select
"Adapter".
3. Select the driver to be removed
"ARCNET ISA adapter (20020).
4. Press "Remove".
5. Restart your PC.

907 AC 1131/Issue: 07/00

1-11

Installation

1.5

Installing ARCNET cards using Win95/98 SE

1.5.1 ARCNET card for desktop PC using Win95/98 SE


For programming a PLC via ARCNET using Win95/98 SE, SoHards FARC E3 card (ISA card)
and FARC20.VXD driver can be used.
On the card, set the I/O range and the interrupt IRQ according to the enclosed documentation.

Note:
The factory settings are applicable
(I/O address = 120 hex, IRQ = 10, KOAX mode, 2,5 MHz).
For installing the driver proceed as follows:
1. If you need other settings for I/O range or IRQ than the standard settings, edit the file
FARC20.REG in the directory
907 AC 1131\ARCNET\AECNET_95_98\Treiber.
Do not double click to open! This would already start the registration.
The file has the following content:
REGEDIT4
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\FARC20]
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\FARC20\Parameters]
"IoPortAddress"=dword:00000120
"IoPortIrq"=dword:0000000A
"Clock"=dword:00000001
"LicenceNumber"="0000"
"ControllerType"="20020"
"MainVendor"="SOHARD ARC95"
Enter hexadecimal values for your I/O address after "IoPortAddress" and for your IRQ after
"IoPortIrq".
2. In the following directory double click on the file Install.bat to execute it:
907 AC 1131\ARCNET\ARCNET_95_98\Treiber
The driver FARC20.VXD and the file ARCNET32.DLL are copied to the operating system
subdirectory SYSTEM (e.g. WINDOWS\SYSTEM). The driver is entered to the registry.
3. Reboot your computer.
Using the provided DOS test programs you can test in the MS-DOS shell whether the
communication with another ARCNET subscriber (e.g. a PLC) works properly.

Installation

1-12

907 AC 1131/Issue: 07/00

1.5.2 ARCNET card for notebook PC using Win95/98 SE


For programming the PLC via ARCNET using a notebook Contemporary Controls PCMCIAARCNET adapter PCM 20E can be used (can be obtained from SoHard).
SoHards Win95/98 SE (ISA card!!) driver FARC20.VXD is used because Contemporary
Controls does not provide a driver. During the installation the I/O range and IRQ which Windows
has assigned to the PCMCIA slot must be predetermined for the driver. The ISA card driver is
not able to perform a "normal" PCMCIA configuration with the PCMCIA controller. The driver
assumes that the PCMCIA controller can predetermine standard settings for the card.
For installing the PCMCIA ARCNET card proceed as follows:
1. Copy the files located in the directory 907 AC 1131\ARCNET\Windows_95_98\PCMCIA to
an empty floppy disk.
2. Switch off your PC and remove all PCMCIA cards.
3. Insert the PCMCIA-ARCNET card PCM 20E.
4. Switch on your computer. It is signalized that a new hardware component was found. Insert
the floppy disk created before and select "Installation from floppy disk". Click on "OK". Now
the PCMCIA enabler is loaded.
5. Reboot your computer when requested.
6. Note down the I/O range and interrupt values displayed in
"Start" => "Settings" => "Control Panel" => "System" => " Device Manager" => "PCM20" =>
"Resources".
For example, for Win98 SE and a Toshiba Tecra8100 the following is displayed:
I/O range: 0240-024F (hex)
Interrupt: 10 (dec)
7. In
"Start" => "Settings" => "Control Panel" => "PC card (PCMCIA)"
you will find e.g. PCM20 - Socket 2.
Double click on the entry and go to "Global Settings".
If necessary, uncheck the option "Automatic setting" and close the dialog.

907 AC 1131/Issue: 07/00

1-13

Installation

8. Edit the file FARC20.REG in the directory


907 AC 1131\ARCNET\AECNET_95_98\Treiber.
Do not double click to open. This would already start the registration.
The file has the following content:
REGEDIT4
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\FARC20]
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\FARC20\Parameters]
"IoPortAddress"=dword:00000120
"IoPortIrq"=dword:0000000A
"Clock"=dword:00000001
"LicenceNumber"="0000"
"ControllerType"="20020"
"MainVendor"="SOHARD ARC95"
Enter the hexadecimal values noted down for your I/O address after "IoPortAddress" and for
your Interrupt after "IoPortIrq" (in our example: I/O = 00000240 and IRQ = 0000000A).
9. In the following directory double click on the file Install.bat to execute it:
907 AC 1131\ARCNET\AECNET_95_98\Treiber
The driver FARC20.VXD and the file ARCNET32.DLL are copied to the operating system
subdirectory SYSTEM (e.g. WINDOWS\SYSTEM). The driver is entered to the registry.
10. Reboot your computer.
The following problems can occur:
1. For the Toshiba Tecra8100 using Windows 95 it was not possible to detect the new
hardware component. This problem did not occur when using Windows 98.
2. Even a manual start with
"Start" => "Settings" => "Control Panel" => "Hardware"
Hardware detection "Next"
Other components "Next"
"Disk" A:\ "Browse"
and a subsequent installation of the enabler was not successful.

Installation

1-14

907 AC 1131/Issue: 07/00

Special functions of the software 907 AC 1131

2.1

Whats new in version V4.1


Compared to version V4.0 the software 907 AC 1131 V4.1 contains the following changes:

907 AC 1131/Issue: 07/00

Programming via ARCNET using the operating systems Windows95 and Windows98 SE
(refer to installation).

Entering the basic unit into the controller configuration of 907 AC 1131 (refer to section
"Entering the PLC into the controller configuration").

New functions for FORCING and OVERWRITING (refer to section "Peculiarities for forcing
and overwriting").

Reorganization and enlargement of the block libraries (refer to volume 6 "Libraries"). New
ARCNET blocks (in ARCNET_S90_V41.LIB / ARCNET new) and blocks for ASCII
communication (DRUCK / EMAS replacement). Due to reasons of compatibility the version
V4.0 libraries are still installed (in Library\Save_V40).

Example projects including documentation for:


Connecting the control unit MT45 to 07 KT 97 via MODBUS
Connecting the control unit MT45 to 07 KT 97 via ARCNET
Connecting the control unit MT91 to 07 KT 97 via MODBUS
Connecting the control unit MT91 to 07 KT 97 via ARCNET
Sending and receiving SMS, data exchange via SMS
INSUM coupling to 07 KT 97
... (refer to subdirectory Projekte\Beispielprogramme)

Batch operation was extended by entering the communication partners.

Description for testing the remote maintenance using 907 AC 1131.

Notes concerning the OPC server

2-1

Special functions

2.2

Creating a "new" project for the controller 07 KT 97


In the following procedure we want to create a small example project for the controller 07 KT 97,
download it and finally test it.
Task: Input E62_00 shall be routed to output A62_00 of the controller 07 KT 97.
Perform the following steps:
1. Connect the controller 07 KT 97 to 24 V DC (refer to volume 1 Hardware 07 KT 97).
2. Connect COM1 of the controller 07 KT 97 to the serial interface of your PC.
3. Start the 907 AC 1131 software. The project you edited last is opened. If necessary, close
this project by selecting "File/Close".
4. Select "File/New".

Special functions

2-2

907 AC 1131/Issue: 07/00

5. A window appears where you can select the PLC. Using the mouse, select the controller
"07KT97" and click on "OK".

6. A window appears where you can select the block name, the block type and the PLC
language. For the name and the type keep the settings PLC_PRG and PROGRAM. Select
"FBD" for the language and confirm with "OK".

907 AC 1131/Issue: 07/00

2-3

Special functions

7. You have now opened a new project. When inserting the block PLC_PRG the following
global variables were already created in the folder "Global Variables" of the "Resources"
page.
Object "Systemkonstanten" containing the default values of the system constants (refer
to volume 3 - System technology, section "System constants").
Object "Fehlermerker" containing all the system and error flags (refer to volume 3 System technology, section "System and diagnosis flags").
Object "Auslastung" containing the system flags for the indication of the controller
capacity utilization (refer to volume 3 - System technology, section "System and diagnosis
flags").
The empty objects "Global Variables" and "Variable_Configuration" to enter further global
variables.
Switch to the "Resources" page by double clicking on the "Resources" tab.

Special functions

2-4

907 AC 1131/Issue: 07/00

In this page, click on "Global Variables" or open the respective folder. You can see the
respective variables if you open the individual objects with a double click.
(In the example, the object "Systemkonstanten" is opened).

In the "Resources" page, select the folder "Global Variables".


Now select "Project/Import".

907 AC 1131/Issue: 07/00

2-5

Special functions

All *.exp files are displayed now (in the Library directory). Select "KT97_onb" and confirm it
by clicking on "Open". Now the import file "KT97_onb.exp" is loaded. This file contains the
declaration of all onboard in- and outputs of the 07 KT 97.

When you create a new project the IEC standard library IEC_S90_V41.LIB is also loaded
into the library management. Select "Window/Library Manager".

Special functions

2-6

907 AC 1131/Issue: 07/00

In the upper left window of the library management you can see "IEC_S90_V41...". (If you
need further libraries for your project, you can open a menu in this window with a right
mouse click and then select "Additional Library" from this menu. A window is opened where
you can select the desired library).

For our small example shown here we do not need a library.


8. Switch back to the blocks by clicking on the "Blocks" tab and select the only existing entry
"PLC_PRG".

907 AC 1131/Issue: 07/00

2-7

Special functions

9. In the network "0001", position the mouse cursor onto the project cursor (which is
represented by a "quadrilateral") and press <CTRL><A> (press the keys <CTRL> or
<STRG> and <A> simultaneously) or click with the right mouse button and then select
"Assign" from the appearing context menu. The display is as following:

10. Instead of the question marks, enter the symbolic name for input E62_00 on the left side
and on the right side the name for output A62_00. To do this, left-click on the question
marks, type the name and confirm with <Enter>. These names are predefined in the import
file KT97_onb.exp. If you want to use other symbolic names, you have to change the
names in the object "KT97_Onboard" located in the folder "Global Variables" of the
"Resources" tab. After changing the names you must translate the project by pressing the
<F11> key or by selecting "Project/Rebuild All" from the menu in order to announce the
global variables to the block(s).

Special functions

2-8

907 AC 1131/Issue: 07/00

11. The definition of the project is now completed and the project has to be translated. To do
this, press the <F11> key or select "Project/Rebuild All" from the menu.

12. If no errors were detected the message "0 errors" is displayed in the last line of the
message box. In the next to last line the code and data size of the program is displayed in
bytes. For the data size the size of the data segments is displayed. The default setting is
always 2 data segments.
Now the communication parameters for the connection to the controller have to be set. To
perform this, please click on "Online/Communication Parameters".

907 AC 1131/Issue: 07/00

2-9

Special functions

A window for setting the communication parameters appears. First click on "Gateway" and
then select "Connection", "Local" in the subsequently appearing window. Confirm the
setting with "OK".

Select the driver "ABB SST" or "ABB RS232". This selects the standard serial driver for
COM1 of the PC with the settings 19200 baud, no parity, 8 data bits and 1 stop bit.
If you use the serial interface COM2 of your PC, you have to add a new gateway setting.
To perform this, please click on "New":

Special functions

2-10

907 AC 1131/Issue: 07/00

Enter any name of your choice for the gateway channel into the "Name" field (in our
example "RS232 COM2"), select "ABB RS232" for the device and confirm with "OK".
Youll return to the "Communication Parameters" window.
In the window on the right, select the "Port" by double clicking on "COM1".

Click on "OK" to apply the communication parameters.


13. In the next step we will save the project. (You can also perform this much earlier, e.g.
immediately after the creation.) For this, select "File/Save as"

907 AC 1131/Issue: 07/00

2-11

Special functions

and then specify the desired path and project name:

In our example the project is saved under the name "Ein_Ausgang" to the folder "Projekte".
The file extension "pro" is automatically created by 907 AC 1131 software.
14. In the next step we will load the program into the controller. To perform this, please select
"Online/Login":

Special functions

2-12

907 AC 1131/Issue: 07/00

The gateway icon appears on the right side of the windows status bar and the controller
reports the project information and the runtime system version:

Confirm with "OK".


Now a verification is performed whether the project is identical to the project on the PC. If
there are any differences the PC reports the following message:

Select "Yes" and subsequently the new program is loaded. During the load process a
progress display informs about the currently loaded bytes. When starting the load process
the PLC changes to the STOP mode.

907 AC 1131/Issue: 07/00

2-13

Special functions

15. The next step is to store the program in the FLASH memory of the PLC to protect it against
voltage breakdown. To perform this, please select "Online/Create Boot Project (Flash user
program)":

The project is stored to the Flash memory. During the flashing process the entry "FLASH"
is displayed in black in the status bar of 907 AC 1131 and also the LED "Batt." on the PLC
flashes.
16. Now the program has to be started. To perform this, select "Online/Run":

The status bar of 907 AC 1131 displays "RUN" in black color and the LED "RUN" on the
PLC lights up.

Special functions

2-14

907 AC 1131/Issue: 07/00

17. In order to test the program we are going to force input E62_00 by TRUE. To do this,
please double click on the icon "E62_00". Next to "E62_00" the entry "TRUE" is displayed.
After performing another double click, "FALSE" is displayed followed by "Release Force".
This way you can choose the desired value for forcing. In our example "TRUE" is used.

Now the variable E62_00 is prepared for forcing.


Press the <F7> key or select "Online/Force Values" from the menu. This will force the
variable. On the PC, A62_00 becomes blue and the output A62_00 of the PLC is
connected through. The LED for output A62_00 lights up. The LED "RUN" on the PLC
flashes to indicate the process of "Forcing" (as well as "Overwriting", "Single step",
"Breakpoint", etc.).

Now you can force the output to FALSE again or "Release Force". Using "Online/Logout"
the connection to the PLC is disconnected again. To exit the software 907 AC 1131 use
"File/Exit".

907 AC 1131/Issue: 07/00

2-15

Special functions

2.3

Entering the PLC into the controller configuration


From version V4.1 of the software 907 AC 1131 onwards, the PLC type is entered into the
controller configuration. This is necessary to adapt the software to the various controllers, e.g.
- for different memory areas of the controllers 07 KT 95..97 and 07 KT 98 or
- to prepare a differentiation of series 90 and series 40...50.
Note:
The controllers 07 KT 95, 07 KT 96 and 07 KT 97 use the same memory areas. When
creating projects for those controllers you can enter "07KT95", "07KT96" or "07KT97" into
the controller configuration. If you want to load the same project into the controller
07 KT 98, you have to modify the controller configuration entry to 07KT98.
When logging into the controller a verification is performed whether the entry in the controller
configuration matches the controller. If this is not the case an error message is displayed:
"The connected CPU is not 100% compatible to the CPU used in the controller configuration. It
is not possible to go online. Please replace the CPU module!"
If you try to translate a project without any entry in the controller configuration, the following
error message is displayed:
"No CPU set. Please enter a CPU module into the controller configuration."
In this case it is also possible that various secondary errors are signalized.

Special functions

2-16

907 AC 1131/Issue: 07/00

2.3.1 How to enter the PLC into the controller configuration


There are several possibilities to enter the PLC into the controller configuration:
1. Entering the PLC into a new project
When creating a new project (see section "Creating a new project for the 07 KT 97") you are
requested for the PLC after selecting "File/New". The selected PLC is entered into the
"PLC Configuration" folder in the "Resources" tab.

907 AC 1131/Issue: 07/00

2-17

Special functions

2. Entering the PLC into an existing project (e.g. created in V4.0)


Proceed as follows to enter the controller in an existing project:
- Switch to the "Resources" tab.
- Double click on the "PLC Configuration" folder to open it.
- In the window on the right, click on "Hardware Configuration". From the appearing context
menu select "Append Subelement" and then the desired PLC. Confirm the subsequently
appearing window with "OK".

2.3.2 Changing the PLC for a project


If you want to load a project which was created for the controllers 07 KT 95..97 into the
controller 07 KT 98 (or vice versa) you have to modify the entry in the controller configuration
accordingly.
For this, the following steps are required:
- Switch to the "Resources" tab.
- Double click on the "PLC Configuration" folder to open it.
- If the "Hardware Configuration" entry is preceded by a plus sign, open it by clicking on the plus
to make the subelements visible.
- Select the controller (e.g. 07 KT 97) and press the <Del> key (or <Del>) or open the context
menu by clicking with the right mouse button and select "Delete".
- Now the controller configuration is empty again. Open the context menu once again by clicking
with the right mouse button. Select "Append Subelement" and then the desired PLC. Confirm
the subsequently appearing window with "OK".

Special functions

2-18

907 AC 1131/Issue: 07/00

2.3.3 Configuration files for the controllers


The configuration files for the controllers are located in the subdirectory "Library/PLCCONF".
These files are the GSD files for the PROFIBUS configurator as well as the *.con files for the
individual controllers.
Controller
07 KT 95
07 KT 96
07 KT 97
07 KT 98

Configuration file
CPUKT95.con
CPUKT96.con
CPUKT97.con
CPUKT98.con

The file CPUABB.SEL contains all selectable controllers.

Please do not modify this file!!!


The configuration files for the controllers 07 KT 95..97 contain the following parameters and
values:
; Basic address %M area
Param1=BaseMerker;DWORD:=16#1b8000;16#1b8000;16#1b8000;
; Basic address %I area
Param2=BaseInputs;DWORD:=16#2f8000;16#2f8000;16#2f8000;
; Basic address %Q area
Param3=BaseOutputs;DWORD:=16#2fc000;16#2fc000;16#2fc000;
; Basic address RETAIN variable
Param4=BaseRetains;DWORD:=16#1C0000;16#1C0000;16#1C0000;
; Size of user program (480 kB-16 kB I/O description = 464 KB)
Param5=CodeSize;DWORD:=16#74000;16#74000;16#74000;
; Size of user program without RETAIN (240kB)
Param6=DataSize;DWORD:=16#3c000;16#3c000;16#3c000;
; Size of RETAIN variable (16kB)
Param7=RetainSize;DWORD:=16#4000;16#4000;16#4000;
; Segment size user data (32kB)
Param8=DataSegmentSize;DWORD:=16#8000;16#8000;16#8000;

Please do not modify these files!!!

907 AC 1131/Issue: 07/00

2-19

Special functions

The configuration file for the controller 07 KT 98 contains the following parameters and
values:
; Basic address %M area
Param1=BaseMerker;DWORD:=16#02800000;16#02800000;16#02800000;
; Basic address %I area
Param2=BaseInputs;DWORD:=16#710000;16#710000;16#710000;
; Basic address %Q area
Param3=BaseOutputs;DWORD:=16#714000;16#714000;16#714000;
; Basic address RETAIN variable
Param4=BaseRetains;DWORD:=16#02810000;16#02810000;16#02810000;
; Size of user program (1 MB := 1024 kB-64 kB I/O description = 960 kB)
Param5=CodeSize;DWORD:=16#0F0000;16#0F0000;16#0F0000;
; Size of user data without RETAIN
; Standard: 1MB:=1024kB:=16#100000
Param6=DataSize;DWORD:=16#100000;16#100000;16#100000;
; Size of RETAIN variable (256kB)
Param7=RetainSize;DWORD:=16#40000;16#40000;16#40000;
; Segment size user data
; max.:
256 kB := 16#40000
; possible:
64 kB := 16#10000
;
128 kB := 16#20000
; standard:
32 kB :=16#8000
Param8=DataSegmentSize;DWORD:=16#8000;16#8000;16#8000;
For the controller 07 KT 98 the parameter "Param8" can be modified if necessary (if a block in
the project requires more than 32 kB of data). In this case the modification applies to all
projects.

Displayed code and data size:


When translating a project using the function key <F11> or "Project/Rebuild All" the code and
data size information is displayed in the message window in the next to last line.
For our example project "Ein_Ausgang.pro":
Code Size 1065, Data Size 45200

Code Size - program size:


The displayed code size corresponds exactly to the size of the program code, but without I/O
description (inputs and outputs for the tasks).
For the controllers 07 KT 95..97 the maximum program size is 464 kB = 475136 bytes =
16#74000 bytes. In addition the I/O description takes 16 kB which results in a maximum user
program size of 480 kB.
For the controller 07 KT 98 the maximum program size is 960 kB = 983040 bytes =
16#0F0000 bytes. In addition the I/O description takes 64 kB which results in a maximum user
program size of 1 MB = 1024 kB.

Special functions

2-20

907 AC 1131/Issue: 07/00

Data Size amount of data:


For the data size the size of the required data segments is displayed. Additionally 12432 bytes
are required for internal extra code (tables for block start addresses and block lengths, auxiliary
functions for online change, debugging, etc.).
The data segment size is determined in the configuration file by the parameter Param8 and is
set to 32 kB := 32768 bytes = 16#8000 bytes.
The number of data segments is set in the 907 AC 1131 software for each project using
"Project/Options/Build/Number of Data Segments". The default value is 2 which means 1
RETAIN segment and 1 data segment. The size of the RETAIN segment is not included in the
displayed data size.
Following this, a displayed data size of "Data Size 45200" means:
- 1 data segment with 32768 bytes: 1 *
32768 bytes
- internal extra code
12432 bytes
- data size
45200 bytes
The actually used data in the data segment are not displayed. The following error message is
displayed if you enter more data than a data segment can accommodate: "The data occupy too
much memory. Increase the number of data segments."
For the controllers 07 KT 95..97 the size of the variable memory (refer to parameter Param6 in
the configuration file) is 240 kB = 245760 bytes. Subtracting 12432 bytes of internal extra code
results in 233328 bytes. These are approx. 7 data segments of 32768 bytes each. Following
this, you can set the number of data segments to a maximum of 8 (7 data segments + 1
RETAIN segment).
For the controller 07 KT 98 the size of the variable memory (refer to parameter Param6 in the
configuration file) is 1 MB := 1024 kB := 1048576 bytes. Subtracting 12432 bytes of internal
extra code results in 1036144 bytes. These are approx. 31 data segments of 32768 bytes each.
Following this, you can set the number of data segments to a maximum of 32 (31 data
segments + 1 RETAIN segment). If you change the size of the data segments, the maximum
number of possible data segments changes accordingly.

907 AC 1131/Issue: 07/00

2-21

Special functions

2.4

Menus which are not described in the operating instructions

2.4.1 Menus in the main menu "Online"


The following menus contained in the main menu "Online" are not described in the operating
instructions of the 907 AC 1131 software:

"Create boot project (Flash user program)"

"Settings for Force"

"Import variables from ABB 907 PC 33 projects into global variables list"

"Import program from ABB 907 PC 33 project"

"Perform PLC cold start (and log out)"

"Info on project on PLC"

"Write user program to SMC"

"Write project source code to SMC"

Menu "Create boot project (Flash user program)"


This menu is only available in the logged in state. In the offline state the menu is grayed out.
After selecting this menu item the program stored in the RAM memory of the PLC is written to
the Flash memory of the PLC resulting in a voltage breakdown-safe storage. During the flash
process the indication "FLASH" is displayed in black in the status bar of the 907 AC 1131
software (otherwise the indication is displayed in gray). The LED "Batt." on the PLC flashes.

Note:
If the controller is in the RUN mode, this operation can take some minutes.
Together with the user program the areas of the constants %MW3000.0..%MW3089.15 and the
double word constants %MD4000.0..%MD4023.15 as well as the PROFIBUS configuration data
and, if necessary, the force list are stored in the Flash memory.

Menu "Settings for Force"


Using the menu item "Settings for Force" the forcing parameters "Do not release force when
logging out" and "Save force list in boot project (Flash/SMC)" are set. This is described in more
detail in section "Peculiarities for forcing and overwriting in version V4.1".

Menu "Import variables from ABB 907 PC 33 projects into global variables list"
The menu item "Import variables from ABB 907 PC 33 projects into global variables list" is part
of importing projects created with 907 PC 331 and is described in the corresponding chapter.

Menu "Import program from ABB 907 PC 33 project"


The menu item "Import program from ABB 907 PC 33 project" is part of importing projects
created with 907 PC 331 and is described in the corresponding chapter.

Special functions

2-22

907 AC 1131/Issue: 07/00

Menu "Perform PLC cold start (and log out)"


The menu item "Perform PLC cold start (and log out)" is only available in the logged in state
(otherwise grayed out). This menu item initiates a cold start on the PLC. A warm start on the
controller is initiated using the menu item "Online/Reset". For both menu items a logout is
performed. The cold and the warm start of the controller are described in detail in volume 3 System technology.

Menu "Info on project on PLC"


The menu item "Info on project on PLC" is only available in the logged in state (otherwise
greyed out). Selecting this menu item displays the same information about the runtime system
of the controller and the project on the PLC as displayed when logging in to the controller.

Menu "Write user program to SMC"


The menu item "Write user program to SMC" is only available in the logged in state (otherwise
grayed out). After selecting this menu item the program stored in the Flash memory of the PLC
is written to an inserted SmartMedia Card.
In order to store the user program to a SmartMedia Card the following procedure is necessary:
- Load the program to the PLC (download).
- Write the program to the Flash memory using "Online/Create boot project (Flash user
program)".
- Insert the SmartMedia Card (chip side up).
- Write the program from the Flash memory to the SmartMedia Card using "Online/Write user
program to SMC".

Caution:
The SmartMedia Card is formatted prior to writing data to it. Data which are possibly
stored on the card are deleted without any inquiry.
If both parameters under "Online/Settings for Force" are set to "yes":
- "Do not release force when logging out" - yes (checked)
- "Save force list in boot project (Flash/SMC)" - yes (checked)
you are asked whether you really want to write the force values to the SmartMedia Card. The
menu is aborted if you answer with no.
(Refer to chapter "Peculiarities for forcing and overwriting in version V4.1").
The following error is displayed if no SmartMedia Card is inserted in the controller:
"The controller has performed the last online service incorrect".

Menu "Write project source code to SMC"


The menu item "Write project source code to SMC" is intended for later software versions. It is
not effective in version V4.1.

907 AC 1131/Issue: 07/00

2-23

Special functions

2.4.2 The PLC browser


The PLC browser provides additional online functions for users which use pointers and indirect
memory accesses frequently. Furthermore it provides information about the user tasks.
You can find the PLC browser in the "Resources" tab. The PLC browser works only in the
logged in state.
The following functions are available:
-?
Get a list of the implemented commands.
- mem
Memory dump. Syntax: mem <start-addr> <end-addr>.
- memc
Same as mem, addresses are added to the start address of the code area.
- memd
Same as mem, addresses are added to the start address of the data area.
- tsk
Output IEC task list with task information.
If you select the PLC browser and click on the sign [...] a window displaying the possible
functions appears. You can click on the commands in this window. The commands are then
entered into the command line where you can enter the required parameters, if necessary.

Special functions

2-24

907 AC 1131/Issue: 07/00

If you enter a question mark followed by <Enter>, the functions implemented in the controller
are displayed.

Using the command "mem <start address> <end address>" you can directly view the memory
areas.

907 AC 1131/Issue: 07/00

2-25

Special functions

Using the command "tsk" you can obtain detailed information about the user tasks.

Special functions

2-26

907 AC 1131/Issue: 07/00

2.5

Peculiarities for forcing and overwriting in version V4.1"


In version V4.0 of the software 907 AC 1131 only one buffer was available for the functions
forcing and overwriting. This is why it was only possible to either force or overwrite.
From version V4.1 of the software 907 AC 1131 onwards, separate buffers are used for forcing
and overwriting. Furthermore it is now possible that the force values are not deleted when
logging out or that the force values are even written to the Flash memory or the SMC to become
voltage breakdown-safe.

Caution:
The new features for forcing and overwriting are only available on controllers with a
runtime system from version V4.1 onwards. The force parameters described below
are without any effects on controllers with runtime system version V4.0x.
Using "Write Values" values are written once. After this, the variables can immediately change
their value again initiated by the program.
Using "Force Values" the values are written at each beginning and each end of a cycle until
this process is cancelled with "Release Force". For example when you force a digital input to
TRUE, the I/O image of the tasks works with the forced TRUE, independently from the actual
status of the input. But, for instance, if you force an INT variable to 0 and increment this variable
in the program, the variables value inside the program is set to 1 (and not 0). This applies to all
variables and also to outputs.
The "Online" menu contains the menu item "Settings for Force". If you select this menu item a
window containing the force parameters appears.

907 AC 1131/Issue: 07/00

2-27

Special functions

When you click on "Do not release force when logging out" the entry is marked by a checkmark
(indicating that the function is selected) and the entry for the parameter "Save force list in
boot project (Flash/SMC)" is displayed in black and can be selected now.

The following behavior can be set using these two parameters:


1. - "Do not release force when logging out" - empty (not checked)
- "Save force list in boot project (Flash/SMC)" - empty (not checked)
This is the default setting. The behavior is as for version V4.0 which means that
- the force values are deleted when logging out and
- the force values are not stored in the Flash memory or on the SmartMedia Card.
The LED RUN flashes as long as the logged in state is kept and the values are forced. After
logging out the LED lights as usual.
2. - "Do not release force when logging out" - yes (checked)
- "Save force list in boot project (Flash/SMC)" - empty (not checked)
Using this setting the force values are kept in the RAM memory after logging out. When
logging out you are asked whether the force values should be kept. If you answer with "No"
the force values are deleted. If you answer with "Yes" the force values are kept. In addition
the LED RUN flashes. When logging in the force list is read from the RAM memory of the
PLC. The status bar of 907 AC 1131 displays "FORCE" in black. The forced values are
marked in color.
The force list is deleted on a cold or warm start or when switching the control voltage off/on.
(The behavior is as for the 07 KT 94 with EBS operating system). The LED RUN is lighting
again.

Special functions

2-28

907 AC 1131/Issue: 07/00

3. - "Do not release force when logging out" - yes (checked)


- "Save force list in boot project (Flash/SMC)" - yes (checked)
You must store the user program to the Flash memory using "Online/Bootprojekt erzeugen
(Anwenderprogramm flashen)" before logging out. Prior to flashing the user program you
are again reminded that force values are present and that they are also written to the Flash
memory. After this the force values are saved in the RAM and in the Flash memory. The
LED RUN flashes. If you store the user program to a SMC the force values are also stored.
You are once again reminded to this fact.
When performing a cold or warm start or when switching the control voltage off/on the force
list is loaded from the Flash memory together with the user program and then activated. The
LED RUN flashes.
The force list can only be deleted using the software 907 AC 1131. When logging in the
force list is read from the RAM memory of the PLC.
4. - "Do not release force when logging out" - empty (not checked)
- "Save force list in boot project (Flash/SMC)" - yes (checked)
This setting is not possible!

907 AC 1131/Issue: 07/00

2-29

Special functions

2.6

Peculiarities of batch operation in version V4.1


The batch operation with the software 907 AC 1131 is described in appendix F "Command line
and command file commands" of volume 5 - Operating instructions.
In order to enable loading of the same project to several controllers using a command file, the
batch operation was expanded by setting the communication parameters.

Caution:
To obtain a correct function of the batch operation for write protected projects, the
parameter Autoload in the file AC1131.INI (for WinNT in the folder WINNT\SYSTEM32
or for Win95/98 in the folder WINDOWS\System) must be set to off (Autoload=No).
By default Autoload is set to on, i.e. Autoload=Yes.
Below an example project is introduced together with the corresponding command file. The lines
beginning with a semicolon are comment lines. Comments written in command lines are also
preceded by a semicolon.
The content of the command file ABB.CMD shall be as follows:
; the following line can be omitted if the project has no access passwords
; insert "query off ok" already at this point if the project file is write protected
query off cancel ; ignore the password request - no writing permission
;file open downloadbatch.pro ; project name => enter your own project here
file open c:\programme\ac1131\projekte\downloadbatch.pro ; or enter file with path
query off ok ; all following dialogs with OK
online sim off ; switch off the simulation
gateway local ; local access to gateway (shared memory)
; Example for serial communication
;device guid {83BC99E0-3455-11d3-A2A8-00104BB37AA1} ; ABB RS232
;device parameter 1000 COM2 ; COM port 2
;device parameter 1001 19200 ; baud rate
; Select ARCNET driver
device guid {F41F2C40-346C-11d3-A2A8-00104BB37AA1}
; enter target address of the controller
; address of first controller:
device parameter 1101 35 ; target node number 35 (ARCNET address)
online login ; login to controller
delay 15000 ; wait time for download (15 seconds, long enough?? => change if necessary)
online createbootproject ; start flashing
delay 10000 ; 10 sec for flashing process
online run ; start program
delay 2000
online logout ; logout from the controller
delay 7000 ; 7 sec. for logout

Special functions

2-30

907 AC 1131/Issue: 07/00

; address of second controller:


device parameter 1101 2 ; target node number 2 (ARCNET address)
online login
delay 15000 ; for download (15 seconds, long enough?? => change if necessary)
online createbootproject ; start flashing
delay 10000 ; 10 sec for flashing process
online run
delay 2000
online logout
delay 7000 ; 7 sec. for logout
; repeat from target address for further controllers
file close
file quit

In our example the write protected project download.pro is sent via ARCNET to the ARCNET
subscribers 35 and 2. The project is flashed in each controller and then started. If necessary,
the set wait times must be modified according to the program length.
To call the command file:

Select "Start" => "Run"

Enter:
c:\programme\ac1131\ac1131.exe /cmd c:\programme\ac1131\projekte\abb.cmd

In this case the command file abb.cmd and the project downloadbatch.pro are located in the
directory
c:\programme\ac1131\projekte.

907 AC 1131/Issue: 07/00

2-31

Special functions

2.7

Notes concerning frequently asked questions

2.7.1 Project protection for logging in to the controller


The following procedure is recommended to ensure that a project cannot be modified
unintentionally and that a login to the controller can be performed again and again without
producing the message "Controller contains other project..." (and causing the controller to
STOP on "OK").
1. - Translate the project using <F11> or "Project/Rebuild All".
- Save the project.
- Set up a password by selecting:
"Project/Options/Passwords/Write Protection Password"
(e.g. enter AC31 and repeat for confirmation)
- Exit the 907 AC 1131 software.
2. - Start the 907 AC 1131 software.
- Open the project (or automatically opened).
- Do not enter the password. Confirm with <Cancel>.
- Login to controller 1, "Controller contains other project...", download, bootproject, start,
logout.
- Login to controller 2, ...
Exit The message "Project was changed. Save..." appears.
3. - Start the 907 AC 1131 software.
- Open the project (or automatically opened).
- Do not enter the password. Confirm with <Cancel>.
- Login to controller 1 (without message "Controller contains other project...").
- Login to controller 2, ...
If you want to call the following menus in a write protected project (as described above), you can
update the menus using <F11> or "Project/Rebuild All".
- "Project/Show Call Tree ..."
- "Project/Show Cross Reference ..."
- "Project/Show unused Variables ..."
The project will not be changed so that a new login is possible.
Please do not enter the write protection password when opening the project!

Special functions

2-32

907 AC 1131/Issue: 07/00

2.7.2 RETAIN variables - note for program change


The starting behavior and the buffering of variables are described in section "Initialization and
buffering of data areas" of volume 3 - System technology.
RETAIN variables only keep their order when the program change is performed using online
change. When performing a download or when changing the variables (add, delete, change
order) the order of the REATIN variables is also lost resulting in a loss of their values.
Below a method is described how to keep the RETAIN variables even when changing the
program. A small example program is used to simplify the description.
The following small project is created (here in ST):

907 AC 1131/Issue: 07/00

2-33

Special functions

For our project we create one (or more) watch list(s) containing the RETAIN variables. Note that
the initialization value is entered after the variable name (without ;). In our example the watch
list was saved using the name VAR_RETAIN_1.WTC.

Now the program is saved, provided with write protection, downloaded to the controller and
flashed.

Special functions

2-34

907 AC 1131/Issue: 07/00

After starting the program the variables change as desired:

The next step is to add one more counter. Prior to modifying the program we must read the
current state of the RETAIN variables. For this, we login to the controller with the project still
unchanged. Then we set the controller to STOP mode ("Online/Stop") and in the watch and
recipe manager we open a context menu by right clicking with the mouse.
Select "Read Recipe". The variables are updated once again.

After this we open the context menu again and select "Save Watch List". In our example the
name VAR_RETAIN_2.WTC was chosen. Now we logout and delete the watch list (same
context menu, "Delete Watch List").

907 AC 1131/Issue: 07/00

2-35

Special functions

After that we modify the project (or close it and open it again entering the write protection
password for modifying). Now we add one more counter to the VAR_RETAIN list which is also
incremented by 3 every 5 seconds in the program. After the modifications are completed,
translate the project using the <F11> key, save it and download it to the controller.

You can see that the values are now incorrect!


This is the reason why we must log out again and load the watch list containing the stored
RETAIN variables (in our example VAR_RETAIN_2.WTC). The name inquiry was answered
with VAR_RETAIN_3. Now the watch list is supplemented by the new variable iZaehler_neu
and saved again. After logging in again the watch list contains the values currently read from the
controller and the correct values saved before.

Special functions

2-36

907 AC 1131/Issue: 07/00

To write the correct values back to the controller, you must open the context menu again using
the right mouse button (or menu "Extras") and then select the command "Write Recipe". Answer
the question "Do you really want to write the current recipe" with "Yes". The "old" values are
written and the new counter is initialized by zero.

If the program is now started the values go on correctly. The new counter begins to count
correctly. After this log out again.

907 AC 1131/Issue: 07/00

2-37

Special functions

2.7.3 Creating and modifying your own library


Creating a library:
Proceed as follows to create a library containing self-made blocks:
1. First a project is created containing the blocks.
2. The PLC_PRG can contain all the block calls. Consequently the program can be tested.
3. The project is saved for testing.
4. All parts of the project which are not required for this library are deleted:
- the block PLC_PRG in the "Blocks" tab and
- the objects in the "Global Variables" folder of the "Resources" tab (such as "Auslastung",
"Fehlermeldungen", "Systemkonstanten", "KT97_Onboard", etc.).
5. For the number of data segments (which can be found under
"Project/Options/Build/Number of data segments") "2" must be entered.
6. The "PLC Configuration" of the "Resources" tab must contain a PLC of series 90 (e.g.
07KT97).
7. Now the project is built one more time using the <F11> key or "Project/Rebuild All".
An error message occurs:
"The project does not contain a block PLC_PRG (vector function)".
8. To protect the library with a password, select "Project/Options/Passwords" and enter the
desired password in the fields "Password" and "Confirm Password".
9. To save the library, use
"File/Save as...".
Select "File type - Internal library (*.lib)" in the appearing dialog. The desired name for the
library is entered in the "File name" field. The file name extension LIB is automatically
attached.

Modifying a library:
To modify a library which was created this way, use "File/Open", select the file type "Library
(*.lib) and enter the file name to open the library.
Now existing blocks can be modified or deleted and/or new blocks can be added. To save the
library perform the steps 5, 6, 7 and 9 as described above in the section "Creating a library".

Caution:
The manufacturer libraries are password protected and may not be modified by the
user.

Special functions

2-38

907 AC 1131/Issue: 07/00

Importing projects from 907 PC 331

3.1

Introduction
The programming and test software 907 AC 1131 offers the option to import programs (in IL)
which were created for the controllers 07 KR91, 07 KT 92, 07 KT 93 and 07 KT 94 using the
programming and test software 907 PC 331. Aim of the import is to avoid laborious typing out of
existing programs. However, it will always be necessary to rework the programs. The
functionality of the blocks which are not contained in the 907 AC 1131 library ABB-BIB4.LIB
must be adapted. A list of these blocks can be found in the block library documentation. In
section 3.4 "Reworking the programs" the peculiarities to be observed are once again
described.
To import projects created with 907 PC 331 perform the following steps:

3.2

Create an ASCII file containing the variable list using 907 PC 331
Create an ASCII file containing the translated IL using 907 PC 331
Load the variable list into the 907 AC 1131
Load the program file into the 907 AC 1131
Correct the created project, if necessary

Creating the ASCII files for the program and variables using 907 PC 331
To import a project generated with 907 PC 331, the variables list and the instruction list are
required as ASCII files.

907 AC 1131/Issue: 07/00

3-1

Importing projects

3.2.1 Creating an ASCII file of the variables list


The ASCII file of the variables list is generated by printing the variables list from the 907 PC 331
into a file. To receive uniform files the following print parameters have to be set:
Menu: Print param./Print parameter

Page length:
Left margin:
Papersave:
Convers. file:
Initial. file:
Re-init file:

100
0
Y
(none)
(none)
(none)

Menu: Print param./Print format editor


No. of header lines:
No. of footer lines:

0
0

Menu: Print 1/Variable list

Start variable:
End variable:
Start symbol:
End symbol:
Sorting Abs./Symb. (A/S):
Print with cover sheet (Y/N):
First page:
Print destination:

Importing projects

(none)
(none)
(none)
(none)
A
N
1
projectname.VAR

3-2

907 AC 1131/Issue: 07/00

The ASCII file is represented as follows: (Examples for variables)


E

Variable

Symbol

Long text

E 02,00
E 62,00
E 62,09

Eingang E2,0
Onboard E0

Input 0 at module 2
Input 0 at basic unit

EW 06,00

Analn1

Analog input channel 1

A 62,01
AW 02,00
M 000,00
M 000,01
M 255,15

I+
JR2
1.SPS-Zykl

MW 000,01
MW 013,04

FKT_Feld+0
TXT-Nummer

Text numbers register

K 00,00
K 00,01
K 00,01

Bit=0
B1
Bit=1

0
1
1

KW
KW
KW
KW
KW
KW
KW
KW
KW

MAST_SLV
INIT_M
INIT_MW
INIT_MD
INIT_S
INIT_VW
MODE_SST
SLV_SEND
SLV_REC

-2
0
0
0
0
0
101
0
0

KW 01,00
KW 01,01

0
1

0
1

KD 00,00
KD 00,06

ZYKL_ZEIT
25

10
25

# +00001
# +00004
# +00127
#H C800

1
#_4
#H 7F

1
#_4
127

MRK 199

MRK 199

Label 199

B 000
B 000

BA-Nr

Block no (pre-assigned 0)

00,00
00,01
00,02
00,03
00,04
00,05
00,06
00,10
00,11

AREC_5 received job from node 2

MD 00,00

907 AC 1131/Issue: 07/00

3-3

Importing projects

3.2.2 Creating an ASCII file of the program (IL)


Section 2.4 "Reworking the programs" describes the peculiarities to be observed when
importing the program. Please read this section before starting the import. To facilitate the
reworking, the program should be prepared as follows:

As only comment lines are added into the instruction list which start with a semicolon, all
comment lines to be imported must start with a semicolon.
To quickly find again segment plans, a comment line with the segment plan number should
be added at the beginning of each segment plan.
The connection elements of the 907 PC 331 (I+, I-, RS, SR, =1) should also be marked by
comment lines, if they should be replaced by blocks of the 907 AC 1131 when reworking the
program.
If you have used blocks, which have been converted to several types, you have to verify
whether the constants K 00,00 or K 00,01 are assigned to the block input for selecting the
operand type. Otherwise it is possible that the wrong block is used.
907 PC 331
907 AC 1131
SHIFT SHIFTW, SHIFTD
FIFO
FIFOB, FIFOW
LIFO
LIFOB, LIFOW
INITS
INITSB, INITSW, INITSD
INITV
INITVB16, INITVB32, INITVW16, INITVW32, INITVD16, INITVD32

The program ASCII file is generated by printing the translated IL from the 907 PC 331 into a file.
To receive standardized files the following print parameters have to be set:
Menu: Print param./Print parameter

Page length:
Left margin:
Papersave:
Convers. file:
Initial. file:
Re-init file:

100
0
Y
(none)
(none)
(none)

Menu: Print param./Print format editor


No. of header lines:
No. of footer lines:

0
0

Menu: Print 1/Variable list

Start variable:
End variable:
Start symbol:
End symbol:
Sorting Abs./Symb. (A/S):
Print with cover sheet (Y/N):
First page:
Print destination:

(none)
(none)
(none)
(none)
A
N
1
projectname.AWL

Note:
If the program was created in FBD/LD, only comment lines which start with a
semicolon are imported to the IL.

Importing projects

3-4

907 AC 1131/Issue: 07/00

The ASCII file is represented as follows: (Example for program start)


Set

Word

00000 00000
00001

907 AC 1131/Issue: 07/00

Command Operand

Symbol

Long text

; ARCNET - CEs
!BA
000
APOLL
; Initialization of the ARCNET coupler

00001 00002
00004

!
=N

00002 00006
00007
00008
00009
00010
00011
00012
00013
00014
00015
00016
00017
00018
00019

!BA
AINIT

M
M

NODE=7

255,15
238,01
000

M
238,01
KW 30,04
M
017,02
M
017,00
MW 030,02
MW 030,03
MW 030,00
M
017,03
MW 030,05
MW 030,04
MW 030,01
M
017,04
; Receiver block ARCNET

3-5

TIMOUT

100

Importing projects

3.3

Importing the programs to 907 AC 1131

3.3.1 Sequence of steps to import the program to 907 AC 1131


The project to be imported is loaded into an "empty" 907 AC 1131 project. The "empty" project
must contain the following:

A PLC_PRG block with at least one "dummy statement" (e.g. in IL LD 0, in FBD TRUE).

The libraries "Standard.lib" and "ABB-BIBx.lib" must be included in the library management.

The provided project file "ABB_LEER.PRO" already contains these entries.

Caution:
The file Step_Var.EXP must be located in the route directory of the 907 AC 1131.

Sequence of steps to import the project:


To import a project into the 907 AC 1131 perform the following steps:

Copy the files "projectname.VAR" and "projectname.AWL" into your project directory.

Start the 907 AC 1131.

Open the provided project "ABB_LEER.PRO".

Save the project under the desired project name.

Translate the project using "Project/Rebuild All" or <F11>.

Load the variables list "projectname.VAR" to the project. For that purpose, select the menu
item "Online/Import variables from ABB 907 PC 33 projects into global variables list". A
window appears to select the *.VAR files. Select your variables file. The variables list is
loaded. In the folder "Resources/Global Variables" one or several new entries (according to
the size of the variables file) "GlobalVariables3" ... "GlobalVariablesYY" and the entry
"Schrittketten" are created.

Translate the project using "Project/Rebuild All" or <F11>.

If necessary, correct the reported errors and translate the project again.

Load the program file "projectname.AWL" to the project. To do this, call the menu
"Online/Import program from ABB 907 PC 33 project". A window appears to select the
*.AWL files. Select your program file. For loading into the language IL confirm with "OK".
The program file is loaded. A new block of the type program (PRG) named "projectname" is
created in the folder "Bausteine" of your AWL file (projectname.AWL).

Caution:
Loading the program file can take several minutes.

If necessary, correct the reported errors and translate the project again.

In the PLC_PRG insert a block call for your block or delete PLC_PRG and rename your
block to PLC_PRG.

Importing projects

3-6

907 AC 1131/Issue: 07/00

After successful translation, the block can be converted to Function Block Diagram (FBD).
Please verify your project after conversion. Pay special attention to program parts with set S - and reset -R - instructions.

Translate the project using "Project/Rebuild All" or <F11>.

Check your project for non-importable functionality (refer to section "Peculiarities") and
redesign them.

Set the cycle time for the program using the task configuration.

Check the system constants.

3.3.2 Importing the variables to 907 AC 1131


The variables from the variable file "projectname.VAR" are imported as global variables to the
addressable flag area "%Mxxx" of the 907 AC 1131 software.

Variable name
The unique identification of a variable is only possible via the absolute variable name (refer to
example of the variables list) because the symbolic name:

either does not have to be available,

can include special characters (symbols which are not conform to the IEC1131-3 ),

or can be assigned twice.

Therefore the variable names are generated from the absolute variable names during the
import. If a symbolic name exists, it is attached to the absolute name. Special characters are
replaced by "_".
The long text of a variable is added as a comment to the variables list.
For the constants word KW xx,yy and double word KD xx,yy the value appears in the long text
and is entered as initialization value during the import.
The variable K 00,00 (boolean constant 0) is not included in the variables list and replaced by
FALSE when importing the program. K 00,01 (boolean constant 1) is replaced by TRUE
accordingly.
The direct constants #, #H are not included in the variables list and directly entered as constants
when importing the program. As the IEC1131-3 does not allow HEX constants with the upper bit
set as INT, these numbers are displayed as negative decimal values.
Examples:

# +00001
#H 5F
#H FFFF

1
16#5F
-1

The block number B 000 is not imported to the variables list, because it is not required for
907 AC 1131 blocks.

907 AC 1131/Issue: 07/00

3-7

Importing projects

Examples for variables


907 PC 331:

EW 06,00

Analn1

Analog input channel 1

907 AC 1131: EW006_00_AnaIn1 AT %IW1006.0 : INT; (*Analog input channel 1 *)


907 PC 331:

EW 06,01

Analn2

Analog input channel 1

907 AC 1131: EW006_01_AnaIn2 AT %IW1006.1 : INT; (*Analog input channel 2 *)


907 PC 331:

KW 00,00

MastSlv

-1

907 AC 1131: KW00_00_MastSlv AT %MW3000.0 : INT := -1;


907 PC 331:

KW 01,00

Time Out

100

907 AC 1131: KW01_00_Time_Out AT %MW3001.0 : INT := 100;

3.3.3 Importing the programs to 907 AC 1131


After the variables were imported into the 907 AC 1131 and translated successfully after
correction (if necessary), the program IL can be loaded. The necessary steps for this procedure
are described in section "Procedure for importing the project".
During the import the ABB operators are converted into IEC operators. The ABB blocks are
converted to the corresponding 907 AC 1131 ABB blocks. The corresponding operators / blocks
are described in the block library documentation. Section 2.4 of this documentation describes all
the cases for which a program rework is necessary.
For blocks with several variants (because of duplication) the optimum block for the given
number of duplications is selected.
Example:

907 PC 331:
907 AC 1131:

FKG with 6 sample points


FKG8 and entry n:=6

For the blocks which have been converted into function blocks, instances are created
automatically as local variable (for every block call).
For the timing element blocks, a type conversion DINT_TO_TIME is inserted automatically
before the time value input.
As intermediate flag, the local variable d_u_mm_y : BOOL; is inserted.
In the operating system of the controllers 07 KR 91, 07 KT 92, 07 KT 93 and 07 KT 94, the rules
of the boolean algebra (AND before OR and MULTIPLICATION/DIVISION before
ADDITION/SUBTRACTION) are observed automatically. In order to keep this functionality also
with the 907 AC 1131, the corresponding parentheses are set while importing the project.

Importing projects

3-8

907 AC 1131/Issue: 07/00

3.3.4 Importing the step chains


In 907 AC 1131 (as well as in the IEC 1131-3) no operands of the type step chain are available.
To import projects created with 907 PC 331, for the step chains S000,00-S255,15 the range
%MW5000-%MW5255 has been reserved in the addressable flag range %M.
While loading the variables list, the steps are correspondingly entered into the global variables.
While loading the program, the file Step_Var.EXP is loaded to the folder "Global
Variables/Schrittketten". It includes one definition of the step chain number for each step chain.
Chain0 AT %MW5000 : INT;
...
Chain255 AT %MW5255 : INT;
The steps 0...15 are defined as Step00...Step15 as follows:
Step00 : INT := 1;
Step01 : INT := 2;
Step02 : INT := 4;
...
Step15 : INT := -32768;
When importing the program the steps are called as follows:
907 PC 331
S000,00
S000,01
S255,00
S255,15

907 AC 1131
Chain0 Step00
Chain0 Step01
Chain255 Step00
Chain255 Step15

Example for a step combination:


907 PC 331:
!
S127,06
& M080,06
= S127,07
=S M250,00

907 AC 1131/Issue: 07/00

907 AC 1131 (import)


LD
Chain127
EQ
Step06
AND
M080_06
ST
d_u_mm_y
LD
d_u_mm_y
SEL
Chain127,Step07
ST
Chain127
LD
d_u_mm_y
S
M250_00

3-9

Importing projects

3.4

Reworking programs
After the program has been loaded, it has to be translated using "Online/Rebuild All" or <F11>.
If no errors are reported, the blocks could be imported successfully. If any errors are reported,
they can be displayed one after the other by pressing <F4>.
In the most cases, errors result from impossible type conversions which must be
reprogrammed.
Example: Cannot convert DINT to INT.

Not imported program parts


Now check the program for parts which were not imported. For this, select the menu
"Project/Global Search". Select your block "projectname [PRG]" and search for:
ERROR!!! Import not possible
The cursor then jumps to the first program part which was not imported. The program code is
included as comment with the line number of the projectname.AWL file in the new program.
Program parts which can not be imported are for instance all blocks which were not converted
into the 907 AC 1131 block library. These are blocks such as APOLL, ABORT, PE which are not
required any more.
The functionality of those blocks which are not converted (e.g. ADAPT, FEHSU, SFEHSU,
SINIT, DRUCK, EMAS) must be programmed again.

Accessing direct addresses:


If you have used blocks with direct memory access in the program, these program parts must
also be edited. Either the functionality must be reworked or the new 32 bit addresses must be
entered in any case. This can be done by placing the address operator ADR before the address
input. This particularly concerns the following blocks:

WOS
DWOS
WOL
DWOL
COPY
AWM
USM

Importing projects

Write word to direct memory address


Write double word to direct memory address
Read word from direct memory address
Read double word from direct memory address
Copying memory areas
Selection multiplexer
Switchover MUX

3-10

907 AC 1131/Issue: 07/00

Accessing addresses of boolean variables:


If you have used blocks in the program which access addresses of boolean variables, this
program parts must also be edited. The boolean variable input of the following blocks has to be
prefixed by the block ADR as described in the block library documentation. This particularly
concerns the following blocks:

IDLB
IDSB
INITSB
INITVB
FIFOB
LIFOB

Indirect binary reading


Indirect binary writing
Initialization of operand memory areas
Initialization of binary variables with values
Stack memory (first in/first out) for binary data
Stack memory (last in/last out) for binary data

In most cases the address operator ADR is inserted automatically. Verify for completeness.

Blocks with several types:


The following 907 PC 331 blocks with different types at the inputs and outputs were converted
to multiple blocks.
907 PC 331
SHIFT
FIFO
LIFO
INITS
INITV
COUNTB
SHIFT block:
Conversion:
Rework:
FIFO block:
Conversion:
Rework:
LIFO block:
Conversion:
Rework:
INITS block:

Conversion:

Rework:

907 AC 1131/Issue: 07/00

907 AC 1131
SHIFTW, SHIFTD
FIFOB, FIFOW
LIFOB, LIFOW
INITSB, INITSW, INITSD
INITVB16, INITVB32, INITVW16, INITVW32, INITVD16, INITVD32
COUNTBW, COUNTBD
SHIFT block for word/double word
Input D/W of type E, A; M, K, S := 0 word / := 1 double word
D/W := K0,0, E, A, M, S SHIFTW
D/W := K0,1 SHIFTD
Check the block type
Stack memory (first in/first out) for binary or word data
Input B/W of type E, A; M, K, S := 0 word / := 1 binary
B/W := K0,0, E, A, M, S FIFOW (do not prefix by ADR)
B/W := K0,1 FIFOB (input ANF must be prefixed by ADR)
Check the block type, ADR
Stack memory (last in/last out) for binary or word data
Input B/W of type E, A; M, K, S := 0 word / := 1 binary
B/W := K0,0, E, A, M, S LIFOW (do not prefix by ADR)
B/W := K0,1 LIFOB (input ANF must be prefixed by ADR)
Check the block type, ADR
Word wise initialization of operand memory areas
Input VAR of type
E, A, M, K, S binary, number of words (2 bits
each)
EW, AW, MW, KW word, number of words
MD, KD double word, number of words ( *2)
E, A, M, K, S INITSB (prefix input VAR by ADR,
number of bits/BOOLS)
EW, AW, MW, KW INITSW (do not prefix by ADR, number in words)
MD, KD INITSD (do not prefix by ADR, number in double words)
Check block type, ADR, adapt number

3-11

Importing projects

INITV block:

Conversion:

Rework:
COUNTB block:
Conversion:
Rework:

Initialization of binary and word variables with numerical values


Input #W/B := 0 word variable / := 1 binary variable
Input #n number of duplications
#W/B := 0 and #n < 17 INITVB16 (ADR before V0...V15)
#W/B := 0 and 16 < #n < 32 INITVB32 (ADR before V0...V31)
#W/B := 1 and #n < 17 INITVW16 (do not prefix by ADR)
#W/B := 1 and 16 < #n < 32 NITVW32 (do not prefix by ADR)
Check the block type, ADR
Testing number of bits in word/double word
Input W/DW of type E, M, K, S := 0 word / := 1 double word
D/W := K0,0, E, A, M, S COUNTBW
D/W := K0,1 COUNTBD
Check the block type

Word conversion blocks:


The blocks for packing or unpacking two words into one double word and vice versa (in EBS
operating system blocks WWDW, DWWW) are loaded to the blocks WSWDW and DW2W. In
contrast to WWDW, for the block W2WDW the first word is stored in the high part of the double
word and the second word is stored in the low part of the double word. Correspondingly for
block DW2W, the low part of the double word is unpacked to the second word and the high part
of the double word is unpacked to the first word.
In order to obtain correct results again, the first and the second word at these blocks must be
changed. This is not performed automatically.

ARCNET blocks:
The block APOLL is not required any more.
For every operation at the block AREC a block AREC is generated. The operand at the
907 PC 331 AREC block output UJOB is entered to all UJOB outputs of the new AREC blocks.
When reworking, another variable of the type BOOL has to be assigned to the output UJOB
(e.g. AREC_0_UJOB ... AREC_n_UJOB). These variables must be connected with an OR
operation after the last AREC block and are to be assigned to the original variable UJOB.
The blocks ASEND, ASEND+ are transferred into the corresponding blocks ASEND1, ASEND4
and ASEND16.

Importing projects

3-12

907 AC 1131/Issue: 07/00

CS31 system bus blocks:


The blocks CS31QU, CS31CO and CS31TE for the CS31 system bus are converted into the
corresponding blocks.
For the block CS31TE you have to observe, that one block CS31TE is generated for each
module (parameter #n in 907 PC 331). The block header (parameter 0/1, TIME, RDY, OK,
ERNO) is not converted. The outputs at the 907 PC 331 blocks MO and ME are assigned to the
outputs OK (block found, connected to bus) and AER (error module address, address not found
on bus). The output DER (error data transfer range) must be allocated a new variable
(e.g. CS31TE_n_DER : BOOL;). For an evaluation the combination of the output bits must be
observed. Explanation:
AER
DER
OK
FALSE
FALSE
TRUE
TRUE
FALSE
FALSE
FALSE
TRUE
FALSE
Other combinations are not possible.

Meaning
Module connected to bus
Module address not found
Module address ok, data range incorrect

RCOM/RCOM+ blocks:
In the 907 PC 331, the RCOM/RCOM+ blocks were used as connection elements (CE). This
must be observed for programs which are using the remote protocol RCOM/RCOM+.
Correspondingly the CEs are resolved in the IL. The program code of the RCOM/RCOM+ CEs
must be replaced with the new blocks from the RCOM library.

MODBUS blocks:
The 907 AC 1131 provides uniform blocks (MODINIT, MODMAST) for the communication via
the serial interfaces COM1 and COM2 or the external MODBUS coupler 07 KP 93. For the
basic unit 07 KT 94, the setting of the MODBUS slave address is done using the system
constant
KW 00,06 / %MW3000.6.
For
the
07 KT 97,
the
system
constant
KW 00,06 / %MW3000.6 is not longer significant. The setting of the interface is done using the
MODINIT block.
The MODBUS master functionality must be programmed with the MODMAST block.

907 AC 1131/Issue: 07/00

3-13

Importing projects

Connection elements in 907 PC 331:


In the 907 PC 331 software, the following blocks are implemented as connection elements (CE):
907 PC 331
I+ R_TRIG
IF_TRIG
SR RS
RS SR
=1 XOR

907 AC 1131
Positive edge
Negative edge
Reset memory, dominating
Set memory, dominating
Exclusive OR for binary values

The CEs are resolved in the IL. In order to use the 907 AC 1131 blocks, the imported IL must be
reworked accordingly. Reworking is not absolutely necessary since the logical connection is
performed correctly.
Positive edge: (I+ R_TRIG)
907 PC 331/IL:
Import
!N M 238,02
0_1
LDN
=R M 000,00
Q
R
!
M 238,02
0_1
LD
&N M 000,00
Q
ANDN
=S M 000,00
Q
S
=
M 020,00
PULS
LD
ANDN
ST

Rework
M238_02_0_1
M000_00_Q
M238_02_0_1
M000_00_Q
M000_00_Q
M238_02_0_1
M000_00_Q
M020_00_PULS

Negative edge: (I- F_TRIG)


907 PC 331/IL:
Import
!
M 238,02
1_0
LD
=S M 000,00
Q
S
!N M 238,02
1_0
LDN
& M 000,00
Q
AND
=R M 000,00
Q
R
=
M 020,00
PULS
LDN
AND
ST

Rework
M238_02_1_0
M000_00_Q
M238_02_1_0
M000_00_Q
M000_00_Q
M238_02_0_1
M000_00_Q
M020_00_PULS

Reset memory, dominating: (SR RS)


907 PC 331/IL:
Import Rework
!
M 238,02
S
LD
M238_02_S
=S M 000,00
Q1
S
M000_00_Q1
!
M 238,00
R
LD
M238_00_R
=R M 000,00
Q1
R
M000_00_Q1
!
M 000,00
Q1
LD
M000_00_Q1
=
M 020,00
Q
ST
M020_00_Q

Importing projects

3-14

Declaration:
R_TRIG1 : R_TRIG;
Instructions:
CAL
R_TRIG1(CLK := M238_02_0_1)
LD
R_TRIG1.Q
ST
M020_00_PULS

Declaration:
F_TRIG1 : F_TRIG;
Instructions:
CAL
F_TRIG1(CLK := M238_02_1_0)
LD
F_TRIG1.Q
ST
M020_00_PULS

Declaration:
RSInst1 : RS;
Instructions:
CAL
RSInst1(SET := M238_02_S,
RESET1 := M238_00_R);
LD
RSInst1.Q1
ST
M020_00_Q

907 AC 1131/Issue: 07/00

Set memory, dominating: (RS SR)


907 PC 331/IL:
Import Rework
!
M 238,02
R
LD
M238_02_R
=R M 000,00
Q1
R
M000_00_Q1
!
M 238,00
S
LD
M238_00_S
=S M 000,00
Q1
S
M000_00_Q1
!
M 000,00
Q1
LD
M000_00_Q1
=
M 020,00
Q
ST
M020_00_Q

Binary exclusive OR: (=1 XOR)


907 PC 331/IL:
Import
!
M 010,00
E1
LD
&N M 010,01
E2
ANDN
/N M 010,00
E1
ORN
& M 010,01
E2
AND
=
M 011,00
A1
ST

Rework
M010_00_E1
M010_01_E2
M010_00_E1
M010_01_E2
M011_00_A1

Declaration:
SRInst1 : SR;
Instructions:
CAL
SRInst1(SET := M238_00_S,
RESET1 := M238_02_R);
LD
SRInst1.Q1
ST
M020_00_Q

LD
XOR
ST

M010_00_E1
M010_00_E2
M011_00_A1

User connection elements:


User connection elements are resolved in the IL and correspondingly imported as IL.

907 AC 1131/Issue: 07/00

3-15

Importing projects

Notes concerning the OPC server

4.1

Installing the OPC server


The OPC server is installed together with the programming software 907 AC 1131. In the
AC1131 directory you can find the following files:
- CoDeSysOPC.EXE
OPC server
- OPCCFG.EXE
setting/verification of the communication parameters
- OCS_PROXY.DLL
DLL for OPC server
The registration is performed using: "CoDeSysOPC /RegServer".
The registration is executed automatically during installation.
The following entries are made (example):
[HKEY_LOCAL_MACHINE\SOFTWARE\3S-Smart Software Solutions GmbH\CoDeSys
OPC\Config]
Updaterate"=dword
"Wait for target"=dword
"Sync startup"="yes"
"Public groups"="yes"
"Reconnect Interval"="dword"
"Notify on quality change"="yes"
[HKEY_CURRENT_USER\Software\3S-Smart Software Solutions GmbH\CoDeSys
OPC\Connections]
"Project0"=hex (current communication parameters for the OPC server including project ID)
"Motorola0"="Yes"
"Timeout0"="dword"
The OPC server (and the gateway) is automatically started by the operating system as soon as
one of the clients establishes a connection. The server is automatically exited as soon as all
clients have cleared the connection.

Caution:
If a download to the target system is performed while the OPC server is active, its
configuration becomes invalid and all items get the quality "Bad".

907 AC 1131/Issue: 07/00

4-1

OPC test

4.1.1 Server settings


The server tasks are set using the configuration program OPCCfg.exe. After starting this
program the following window appears:

OPC test

4-2

907 AC 1131/Issue: 07/00

For the test the following settings were selected first:

Meanings of the individual settings:

907 AC 1131/Issue: 07/00

Motorola Byteorder: no
The target system of the project does not use Motorolas byte order (especially to be
observed for 68K, 8051, Power PC!).

Public Groups anlegen: yes


The OPC server establishes one public group for each IEC block as well as for the global
variables.

Synchrone Initialisierung: yes


When starting, the OPC server does not return until the symbol configuration is loaded.

Notification bei Quality-nderung: yes


The client is informed that the status of an object has changed (e.g. if a download was
newly performed while the OPC server was active) and is then able to initiate corresponding
actions.

Update rate (ms): 200


Basic update rate of the OPC server in milliseconds = Cycle time with which all item values
are newly read from the controller (these values are written to the Cash memory the client
communicates with using a separately defined update rate).

Wartezeit Zielsystem (s): 60


Time in seconds that the OPC server waits until the controller is ready (important for
controller autostart).

Reconnect Intervall (s): 5


Time interval for the OPC server to attempt to reestablish the connection to the controller via
the gateway after a communication break-off.

Kommunikations-Timeout (s): 3
The OPC server finishes automatically after this time period if it does not receive an answer
from the controller to a transmitted service.

Puffer-Gre (Byte): 0
Communication buffer size on the target system. If it is set to 0 it is attempted to receive this
information from the device driver. If nothing is stated there it is assumed that the buffer size
is infinite.

4-3

OPC test

Using the menu item "Konfiguration/Verbindung" the communication channel is set. This is
performed the same way as for the programming software 907 AC 1131.

As well as the serial coupling all the linking can be set as for the programming software
907 AC 1131.
After this, the settings are saved and the configurator is exited.

Note:
If another hardware is loaded on the same computer when using the programming
software 907 AC 1131, the connection to the hardware must be defined in the dialog
"Online/Communication Parameters". This setting is applied and also used for the
OPC server without any notice. Due to this, the configuration program must be started
again after the process of loading in order to correct the OPC connection.

OPC test

4-4

907 AC 1131/Issue: 07/00

4.1.2 Selecting the variables in the programming software 907 AC 1131


All variables to be used in the OPC server must be determined in the 907 AC 1131 software.
For this, some settings have to be made under "Project\Options\Symbol configuration".

Selecting the option "Dump symbol entries" ensures that a symbol file which provides the
selected variables for the OPC data exchange is prepared on each translation process.

Note:
The file is not written to the hard disk of the PC (C:\Winnt\Gateway Files) until the
project is sent to the target hardware. The file name is equal to the corresponding
project but with the extension "sym".
The OPC data exchange cannot be performed prior to this.

907 AC 1131/Issue: 07/00

4-5

OPC test

The selection of the variables is done using the button "Configure symbol file".

Note:
If you want to select individual objects (e.g. BOOL_100 in the folder "Global
variables"), first all attributes must be reset for the entire selection. This must be
concluded with the button "OK". After this, only the desired object (e.g. BOOL_100)
must be selected (or highlighted) to activate the desired attributes.
Explanation:

"Export variables of object": The variables of the desired object are written to the symbol file.

"Export data entries": Entries for accessing the total variables are created for structures and
arrays of the object. Assumption: "Export variables of object" is activated.

"Export structure components": For the structures of the object one entry is created for each
component of the variable. Assumption: ": "Export variables of object" is activated.

"Export array entries": For the arrays of the object one entry is created for each component
of the variable. Assumption: ": "Export variables of object" is activated.

"Write access": The OPC server can modify the variables of the object.

OPC test

4-6

907 AC 1131/Issue: 07/00

4.2

Testing the OPC server

4.2.1 Testing the starting behavior and parallel operation


A short test program (OPC_Server_Test.pro) containing 10 counters and 5 flashing flags is
loaded via the ARCNET card to a 07 KT 97 and stored in the Flash memory. All the objects of
the program are marked as OPC variables as described above. The symbol file can be
generated for all objects or only for a selection of objects, as described in the chapter "Selecting
the variables in the programming software 907 AC 1131".

Note:
The selection is not effective until the project is downloaded to the target hardware.
Using the Visiwin developers package the variables of the symbol file can be entered into a
Visiwin database in order to be available in the visualization interface. A form was filled with the
ten counters and the flashing flags. Consequently the update of the OPC variables became
continuously visible.
After rebooting the PC and starting the test client or the Visiwin application, the OPC data
exchange was restarted again without any problems.
OPC off; start 907 AC 1131 and login:
OK
PC off/on; start OPC; start 907 AC 1131 and login:

Note:
During parallel operation via ARCNET no problems will occur if both, OPC and
907 AC 1131, work to the same node. The connection established first will experience
a communication error as soon as it is attempted to operate different nodes. The
communication error in the Visiwin application will cause the computer to crash. The
ARCNET driver cannot handle 4F telegrams to different nodes at the same time.
Repeated login onto 2 different controllers containing the same program:
Altering between 2 controllers containing identical programs (node 1 and node 2) is performed
without any problems for the OPC server with the configuration program. Connection and
display were frequently altered between the two nodes during one PC session. It is of no
importance whether the login is performed via COM1 or ARCNET.

Note:
If a program requires a modification, the program must be loaded to both controllers
and stored in the Flash memory. The OPC server does not work anymore if there are
any differences between the programs on the controller and on the PC. No data
exchange is performed any more.
Using the write protection ("Write Protection Password" under
"Project\Options\Passwords") will protect against unintentional program modifications
if the same program is used for multiple controllers.

907 AC 1131/Issue: 07/00

4-7

OPC test

4.2.2 Preparing the dynamic tests


Using the programming software 907 AC 1131, different objects were created which can be
arranged in a test program as required.
Program blocks:
_1000binaere_Anweisungen
_10000binaere_Anweisungen (assumes _1000binaere_Anweisungen)
_1000binaereSetAnweisungen
_10000binaereSetAnweisungen (assumes _1000binaereSetAnweisungen)
_1000WortAdd
_10000WortAdd (assumes _1000WortAdd)
_1000WortMul
_10000WortMul (assumes _1000WortMul)
Arcnet_Datenverkehr (test program with 5 basic units)
Modbus (COM1 as master, COM2 as slave)
Variables objects:
Auslastung
OPC-Allgemein
Bool_100
Bool_100_I
Bool_100_M
Byt_10_I_Linie1
Byt_10_I_Linie2
Byt_100_I_Linie1
Byt_100_I_Linie2
Int_10
Int_10_I
Int_10_M
Int_100
Int_100_I
Int_100_M
Int_1000
Int_2000
Sampling cycles
In the world of OPC two sampling cycles exist. One from the client to the server and one from
the server to the target hardware. Both sampling cycles are adjustable. They should be
synchronized, i.e. they should be in the same range.
Using its sampling interval the server reads all the defined values from the controller and writes
them to the Cash memory.
The client communicates with this Cash memory using the grid of its sampling interval.
The definition of the server sampling time (interval) is performed as described in chapter "Server
settings". Here it is the parameter "Update rate". The time is entered in milliseconds. The tests
described here were performed using fixed sampling rates of 100 ms.

OPC test

4-8

907 AC 1131/Issue: 07/00

4.2.3 Testing using VisiWin client


Two images (so called Forms) are created using the visualization package Visiwin, the
"Central_Form" and a "Form1". The "Central_Form" is automatically used after starting the
visualization (starting Visual Basic). It contains the following variables:
Zykluszaehler:
With every cycle this variable is incremented by 1 in the PLC test program.
Auslastung:
Corresponds to the value of %MW1259.0 in the PLC.
Prg_Rechenzeit:
Corresponds to the program calculation time which is calculated in the PLC. It is determined at
the beginning and at the end of the PLC program using the block SYS_TIME.
Zyklusdifferenz:
Internal Visiwin variable. For each recognized change of the cycle counter in the PLC, this value
is newly calculated by using the internal VisiWin variable "VW_Zykluszaehler".
The update time can be calculated using the Prg_Rechenzeit (for cyclic program processing) or
the call interval (for task configuration) and the cycle difference.
MaxZeitAenderung:
Using this internal VisiWin variable the maximum update time is displayed over the entire
running time. By clicking with the mouse on this value, a calculation restart can be performed
during running operation.
MinZeitAenderung:
Using this internal VisiWin variable the minimum update time is displayed over the entire
running time. By clicking with the mouse on this value, a calculation restart can be performed
during running operation.
In addition, the system oscillators %MX255.0, %MX255.1, %MX255.2, %MX255.4 and
%MX255.5 are displayed on the Form.
Using the button "Aufruf_Form1" the second image of the test application is opened without
OPC variables. To leave it again click on the button "Central_Form".

Note:
Using VisiWin an image sensitive variables update can be switched on. This
automatically switches off all variables which are not contained on the currently used
image (Form).

Caution:
When switching to the Form1, all the OPC variables are correctly logged off at the
server. This also sets the data exchange between the server and the target hardware.
If the "Central_Form" is now used again, the variables update does not start any more.
This condition can only be corrected by re-starting VisiWin.

Caution:
If the visualization is active and a program modification is loaded to the target
hardware, the variables update is interrupted and does not start any more.

907 AC 1131/Issue: 07/00

4-9

OPC test

The sampling time for the visualization package VisiWin is set in milliseconds using the
parameter "Abtastzeit" under "Konfigurationen/Treiber-Schnittstellen".
1st test row: fixed number of OPC variables, increasing PLC program size
Basic information:

Seven OPC variables (objects "Auslastung" and "OPC-Allgemein"). The variables used in
the figure were updated using the setting "nicht benutzte Variablen/Items abmelden".
Both sampling times set to 100 ms.
PLC program size varies.
Serial or ARCNET coupling.

The results of this test row are listed in the table located at the end of this chapter.
2nd test row: fixed PLC program size, increasing number of OPC variables
Basic information:

PLC program with binary/word processing, ARCNET telegram and MODBUS traffic.
Using the setting "nicht benutzte Variablen/Items abmelden" ensures that all variables are
always updated.
Both sampling times set to 100 ms.
Different OPC variables (refer to the table for objects).
The symbol configuration for the objects "Auslastung", "OPC_Allgemein" and "Int_1000" is
established using 907 AC 1131.
The number of OPC variables is adapted in the VisiWin data base using "Objekt/Aktivieren"
or "Objekt/Deaktivieren". This results in the number 200, 300, etc.
Caution:
Only 499 OPC variables (as arranged in the table) can be called via the OPC server.
The PLC will crash (restart!) if 500 variables are defined.

The results of this test row are listed in the table located at the end of this chapter.

OPC test

4-10

907 AC 1131/Issue: 07/00

4.2.4 Testing using WIZCON client


Using the visualization package WIZCON an image is created which contains the following
variables:
Zykluszaehler:
With every cycle this variable is incremented by 1 in the PLC test program.
Auslastung:
Corresponds to the value of %MW1259.0 in the PLC.
Programmrechenzeit:
Corresponds to the program calculation time which is calculated in the PLC. It is determined at
the beginning and at the end of the PLC program using the block SYS_TIME.
Zyklusdifferenz:
Internal WIZCON variable. For each recognized change of the cycle counter in the PLC, this
value is newly calculated by using the internal WIZCON variable "VW_Zykluszaehler".
The "Aenderungszeit" can be calculated using the program calculation time (for cyclic program
processing) or the call interval (for task configuration) and the cycle difference.
Aenderungszeit:
This variable always displays the result of the multiplication cycle difference * program
calculation time. For cyclic program processing this is the OPC update time. The
"Aenderungszeit" was simultaneously entered into a diagram that a curve shape was also
available for the min-max evaluation.
In addition, the system oscillators %MX255.0, %MX255.1, %MX255.2, %MX255.4 and
%MX255.5 are displayed on the Form.

Note:
WIZCON always updates all defined gates. That means there is no image sensitive
switch-on/off of the gates. Therefore it was not possible to switch on/off OPC variables
during a running application by altering the image (refer to test with VisWin).
Adding/deleting of gates is performed "online". If a current image variable is deleted
the status "bad" is assigned. It is then no longer updated. Adding this variable again
does not automatically result in an update of the image. The current value of the
variable is not visible until the image is switched off and called again.

Caution:
When installing the communication driver under
"Konfiguration/Kommunikationstreiber", the CoDeSys server is not offered in the
combo box. This means that it is not recognized. Communication was only possible
after it was entered manually into the combo box.

907 AC 1131/Issue: 07/00

4-11

OPC test

In WIZCON the sampling time is given for each gate. The setting can be made in seconds and
milliseconds.
1st test row: fixed number of OPC variables, increasing PLC program size
Basic information:

Seven OPC variables (objects "Auslastung" and "OPC-Allgemein").


Both sampling times set to 100 ms.
PLC program size varies.
Serial or ARCNET coupling.

The results of this test row are listed in the table located at the end of this chapter.
2nd test row: fixed PLC program size, increasing number of OPC variables
Basic information:

PLC program with binary/word processing, ARCNET telegram and MODBUS traffic.
Both sampling times set to 100 ms.
Different OPC variables (refer to the table for objects).
The symbol configuration for the objects "Auslastung", "OPC_Allgemein" and "Int_1000" is
established using 907 AC 1131.
The number of OPC variables is adapted in the WIZCON gate definition by adding or
deleting them. This results in the number 200, 300, etc.

The results of this test row are listed in the table located at the end of this chapter.

Caution:
Only 499 OPC variables (as arranged in the table) can be called via the OPC server.
The PLC will crash (restart!) if 500 variables are defined.

OPC test

4-12

907 AC 1131/Issue: 07/00

Test results

PLC_PRG
_10000binre Anweisungen
_10000WortAdd
_10000binreSetAnweisungen

PLC_PRG
_10000binre Anweisungen
_10000WortAdd
_10000binreSetAnweisungen
_10000WortMul

Auslastung
OPC-Allgemein

Auslastung
OPC-Allgemein

907 AC 1131/Issue: 07/00

PLC_PRG
_10000binre Anweisungen
_10000WortAdd

PLC_PRG
_10000binre Anweisungen

Program
Blocks

Auslastung
OPC-Allgemein

Auslastung
OPC-Allgemein

OPC variables

4.3.1 VisiWin test row 1

4.3

C
C

serial
ARCNET

ARCNET

serial

ARCNET

ARCNET

serial

serial

Connection
to the PLC

Cyclic task
(C)
Task
(T=xxms)

4-13

100

100

100

100

99-100

99-100

97-100

118

118/131

65/ 66

66/ 76

49/ 50

47/ 58

12/13

12/16

ms

%
97-100

Program
calculation
time

Capacity
utilization of
the PLC

12

10

sec

2-3

3-4

2-4

3-5

2-4

3-5

7-9

13-14

cycles

Required
cycles to
recognize
changes

OPC test

Initialization
time (in the
image)

236/357

380/500

130/264

225/340

98/196

170/300

84/108

168/224

ms

Required time
to recognize
changes
(min / max)

PLC_PRG
_10000binre
Anweisungen_10000WortAdd
ARCNET-Datenaustausch
MODBUS

PLC_PRG
_10000binre Anweisungen
_10000WortAdd
_10000binreSetAnweisungen
_10000WortMul

Auslastung
OPC-Allgemein

Auslastung
OPC-Allgemein

OPC test

PLC_PRG
_10000binre Anweisungen

PLC_PRG
_10000binre Anweisungen
_10000WortAdd
ARCNET-Datenaustausch

Auslastung
OPC-Allgemein

Auslastung
OPC-Allgemein

Program
Blocks

OPC variables

T=150
T=150
T=150

serial
ARCNET

T=150

ARCNET

serial

ARCNET

ARCNET

serial

Connection
to the PLC

Cyclic task
(C)
Task
(T=xxms)

4-14

15-24

20-40

82-85

84-86

100

100

12

12/16

117

118/131

54/59

54/55

55/64

ms

%
100

Program
calculation
time

Capacity
utilization of
the PLC

10

sec

Initialization
time (in the
image)

1-2

3-5

2-4

3-5

cycles

Required
cycles to
recognize
changes

907 AC 1131/Issue: 07/00

150

150

150/300

300

162/295

106/216

189/320

ms

Required time
to recognize
changes
(min / max)

Auslastung
OPC-Allgemein

907 AC 1131/Issue: 07/00

PLC_PRG
_10000binre Anweisungen
_10000WortAdd
ARCNET-Datenaustausch
MODBUS

Auslastung
OPC-Allgemein

PLC_PRG
_10000binre Anweisungen

Program
Blocks

PLC_PRG
_10000binre Anweisungen
_10000WortAdd
ARCNET-Datenaustausch

Auslastung
OPC-Allgemein

OPC variables

ARCNET

ARCNET

T=60

T=60

T=60

T=20

ARCNET
serial

T=20

serial

Connection
to the PLC

Cyclic task
(C)
Task
(T=xxms)

4-15

96-100

94

96-100

70-71

54/59

52/52

51/53

11/12

12/16

ms

%
73-75

Program
calculation
time

Capacity
utilization of
the PLC

sec

3-5

2-4

4-6

5-7

5-10

cycles

Required
cycles to
recognize
changes

OPC test

Initialization
time (in the
image)

180/300

120/240

240/360

100/140

100/200

ms

Required time
to recognize
changes
(min / max)

PLC_PRG
_10000binre Anweisungen
_10000WortAdd
ARCNET-Datenaustausch

Auslastung
OPC-Allgemein
Int_100

Auslastung
OPC-Allgemein
Int_1000, 300 of
them released

OPC test

PLC_PRG
_10000binre Anweisungen
_10000WortAdd
ARCNET-Datenaustausch

PLC_PRG
_10000binre Anweisungen
_10000WortAdd
ARCNET-Datenaustausch

PLC_PRG
_10000binre Anweisungen
_10000WortAdd
ARCNET-Datenaustausch

Auslastung
OPC-Allgemein
Int_10

Auslastung
OPC-Allgemein
Int_1000, 200 of
them released

Program
Blocks

OPC variables

4.3.2 VisiWin test row 2

ARCNET

ARCNET

serial

ARCNET

serial

ARCNET
serial

serial

Connection
to the PLC

Cyclic task
(C)
Task
(T=xxms)

4-16

100

100

100

100

100

100

99-100

54/55

61/62

53/55

63/65

53/55

57/67

53/55

65/67

ms

%
99-100

Program
calculation
time

Capacity
utilization of
the PLC

22

29

20

26

13

19

10

sec

Initialization
time (in the
image)

33-35

64-66

23-25

44-46

12-14

23-24

3-5

5-6

cycles

Required
cycles to
recognize
changes

907 AC 1131/Issue: 07/00

1782/1925

3904/4092

1219/1375

2816/2990

636/770

1608/1325

156/275

325/408

ms

Required time
to recognize
changes
(min / max)

PLC_PRG
_10000binre Anweisungen
_10000WortAdd
ARCNET-Datenaustausch

Auslastung
OPC-Allgemein
Int_10

907 AC 1131/Issue: 07/00

PLC_PRG
_10000binre Anweisungen
_10000WortAdd
ARCNET-Datenaustausch
MODBUS

PLC_PRG
_10000binre Anweisungen
_10000WortAdd
ARCNET-Datenaustausch

PLC_PRG
_10000binre Anweisungen
_10000WortAdd
ARCNET-Datenaustausch

Program
Blocks

Auslastung
OPC-Allgemein
Int_1000, 486 of
them released

Auslastung
OPC-Allgemein
Int_1000, 486 of
them released

Auslastung
OPC-Allgemein
Int_1000, 400 of
them released

OPC variables

T=70
T=70

serial
ARCNET

ARCNET

ARCNET

ARCNET

serial

serial

Connection
to the PLC

Cyclic task
(C)
Task
(T=xxms)

4-17

83-85

89-90

100

100

100

100

51/52

61/65

53/56

52/55

54/56

53/55

58/60

ms

%
100

Program
calculation
time

Capacity
utilization of
the PLC

31

30

55

25

47

sec

1-3

4-6

53-54

52-54

106-107

44-45

87-89

cycles

Required
cycles to
recognize
changes

OPC test

Initialization
time (in the
image)

70/210

280/420

2809/3024

2704/2916

5830/5936

2332/2430

5046/5280

ms

Required time
to recognize
changes
(min / max)

PLC_PRG
_10000binre Anweisungen
_10000WortAdd
ARCNET-Datenaustausch

PLC_PRG
_10000binre Anweisungen
_10000WortAdd
ARCNET-Datenaustausch

PLC_PRG
_10000binre Anweisungen
_10000WortAdd
ARCNET-Datenaustausch

Auslastung
OPC-Allgemein
Int_1000, 200 of
them released

Auslastung
OPC-Allgemein
Int_1000, 300 of
them released

Auslastung
OPC-Allgemein
Int_1000, 400 of
them released

OPC test

PLC_PRG
_10000binre Anweisungen
_10000WortAdd
ARCNET-Datenaustausch

Auslastung
OPC-Allgemein
Int_100

Program
Blocks

OPC variables

T=70
T=70

ARCNET

T=70

ARCNET
serial

T=70

T=70

ARCNET
serial

T=70

T=70

ARCNET
serial

T=70

serial

Connection
to the PLC

Cyclic task
(C)
Task
(T=xxms)

4-18

87-88

93

87-88

90-93

86-88

91-92

86-88

51

54/57

51

51

51

51/53

51/52

52/62

ms

%
92-93

Program
calculation
time

Capacity
utilization of
the PLC

15

44

13

32

12

24

10

12

sec

Initialization
time (in the
image)

14-16

66-67

11-13

49-50

8-9

33-35

4-6

18-19

cycles

Required
cycles to
recognize
changes

907 AC 1131/Issue: 07/00

980/1120

4620/4690

770/910

3430/3500

560/630

2310/2450

280/420

1260/1330

ms

Required time
to recognize
changes
(min / max)

PLC_PRG
_10000binre Anweisungen
_10000WortAdd
ARCNET-Datenaustausch

PLC_PRG
_10000binre Anweisungen
_10000WortAdd
ARCNET-Datenaustausch
MODBUS

Auslastung
OPC-Allgemein
Int_1000, 486 of
them released

Auslastung
OPC-Allgemein
Int_1000, 486 of
them released

907 AC 1131/Issue: 07/00

Program
Blocks

OPC variables

T=60

T=70

ARCNET

T=70

ARCNET

ARCNET

T=70

serial

Connection
to the PLC

Cyclic task
(C)
Task
(T=xxms)

4-19

89-90

96-100

87-88

51/52

52

51

53

ms

%
93

Program
calculation
time

Capacity
utilization of
the PLC

18

21

14

40

sec

19-20

52-56

17-19

79-80

cycles

Required
cycles to
recognize
changes

OPC test

Initialization
time (in the
image)

1330/1400

3120/3360

1190/1330

5530/5600

ms

Required time
to recognize
changes
(min / max)

PLC_PRG
_10000binre Anweisungen
_10000WortAdd

PLC_PRG
_10000binre Anweisungen
_10000WortAdd
_10000binreSetAnweisungen

PLC_PRG
_10000binre Anweisungen
_10000WortAdd
_10000binreSetAnweisungen
_10000WortMul

Auslastung
OPC-Allgemein

Auslastung
OPC-Allgemein

Auslastung
OPC-Allgemein

OPC test

PLC_PRG
_10000binre Anweisungen

Auslastung
OPC-Allgemein

Program
Blocks

OPC variables

4.3.3 Wizcon test row 1

ARCNET

serial

ARCNET

serial

ARCNET

serial

serial
C

Connection
to the PLC

ARCNET

Cyclic task
(C)
Task
(T=xxms)

4-20

100

100

100

100

99-100

99-100

97-100

118/119

118/134

65/66

66/80

49/50

49/59

12/13

12/16

ms

%
97-100

Program
calculation
time

Capacity
utilization of
the PLC

sec

Initialization
time (in the
image)

2-3

3-4

2-4

4-5

2-4

4-6

7-8

13-14

cycles

Required
cycles to
recognize
changes

907 AC 1131/Issue: 07/00

236/357

390/516

132/264

280/340

98/196

212/306

84/108

168/210

ms

Required time
to recognize
changes
(min / max)

PLC_PRG
_10000binre Anweisungen
_10000WortAdd
ARCNET-Datenaustausch

PLC_PRG
_10000binre Anweisungen
_10000WortAdd
ARCNET-Datenaustausch
MODBUS

PLC_PRG
_10000binre Anweisungen
_10000WortAdd
_10000binreSetAnweisungen
_10000WortMul

PLC_PRG
_10000binre Anweisungen

Auslastung
OPC-Allgemein

Auslastung
OPC-Allgemein

Auslastung
OPC-Allgemein

Auslastung
OPC-Allgemein

907 AC 1131/Issue: 07/00

Program
Blocks

OPC variables

T=150

T=150

serial
ARCNET

T=150

T=150

ARCNET

serial

ARCNET

ARCNET

serial

Connection
to the PLC

Cyclic task
(C)
Task
(T=xxms)

4-21

15-22

20-30

82-85

86-88

100

100

11/12

11/15

117

131/132

53/59

53/55

58/67

ms

%
100

Program
calculation
time

Capacity
utilization of
the PLC

sec

1-2

1-2

2-3

2-4

2-4

4-5

cycles

Required
cycles to
recognize
changes

OPC test

Initialization
time (in the
image)

150

150/300

150/300

300/450

106/220

108/216

232/340

ms

Required time
to recognize
changes
(min / max)

PLC_PRG
_10000binre Anweisungen
_10000WortAdd
ARCNET-Datenaustausch

PLC_PRG
_10000binre Anweisungen
_10000WortAdd
ARCNET-Datenaustausch
MODBUS

Auslastung
OPC-Allgemein

Auslastung
OPC-Allgemein

OPC test

PLC_PRG
_10000binre Anweisungen

Auslastung
OPC-Allgemein

Program
Blocks

OPC variables

serial

ARCNET

ARCNET

ARCNET

serial

T=70

T=60

T=60

T=60

T=20

T=20

Connection
to the PLC

ARCNET

Cyclic task
(C)
Task
(T=xxms)

4-22

85-87

96-100

94

97-100

69-71

51/53

51/53

51/52

51/53

12

12/15

ms

%
77-78

Program
calculation
time

Capacity
utilization of
the PLC

sec

Initialization
time (in the
image)

1-2

3-5

2-4

4-6

4-6

9-11

cycles

Required
cycles to
recognize
changes

907 AC 1131/Issue: 07/00

70/140

180/300

120/240

240/360

80/120

180/220

ms

Required time
to recognize
changes
(min / max)

PLC_PRG
_10000binre Anweisungen
_10000WortAdd
ARCNET-Datenaustausch

PLC_PRG
_10000binre Anweisungen
_10000WortAdd
ARCNET-Datenaustausch

PLC_PRG
_10000binre Anweisungen
_10000WortAdd
ARCNET-Datenaustausch

PLC_PRG
_10000binre Anweisungen
_10000WortAdd
ARCNET-Datenaustausch

Auslastung
OPC-Allgemein
Int_10

Auslastung
OPC-Allgemein
Int_100

Auslastung
OPC-Allgemein
Int_1000, 200 of
them released

Auslastung
OPC-Allgemein
Int_1000, 300 of
them released

907 AC 1131/Issue: 07/00

Program
Blocks

OPC variables

4.3.4 Wizcon test row 2

C
C

ARCNET

ARCNET
serial

ARCNET
serial

ARCNET
serial

serial

Connection
to the PLC

Cyclic task
(C)
Task
(T=xxms)

4-23

100

100

99-100

100

99-100

100

99-100

53/54

60/61

52/55

63/64

53/55

64/67

53/55

64/66

ms

%
99-100

Program
calculation
time

Capacity
utilization of
the PLC

sec

33-35

65-66

23-25

45-46

12-14

23-24

3-5

5-6

cycles

Required
cycles to
recognize
changes

OPC test

Initialization
time (in the
image)

1782/1890

3900/3965

1196/1375

2835/2944

636/770

1560/1608

156/275

325/396

ms

Required time
to recognize
changes
(min / max)

PLC_PRG
_10000binre Anweisungen
_10000WortAdd
ARCNET-Datenaustausch

PLC_PRG
_10000binre Anweisungen
_10000WortAdd
ARCNET-Datenaustausch
MODBUS

PLC_PRG
_10000binre Anweisungen
_10000WortAdd
ARCNET-Datenaustausch

Auslastung
OPC-Allgemein
Int_1000, 486 of
them released

Auslastung
OPC-Allgemein
Int_1000, 486 of
them released

Auslastung
OPC-Allgemein
Int_10

OPC test

PLC_PRG
_10000binre Anweisungen
_10000WortAdd
ARCNET-Datenaustausch

Auslastung
OPC-Allgemein
Int_1000, 400 of
them released

Program
Blocks

OPC variables

T=70
T=70

serial
ARCNET

ARCNET

ARCNET

ARCNET
serial

serial

Connection
to the PLC

Cyclic task
(C)
Task
(T=xxms)

4-24

84-86

87-89

100

99-100

100

100

51

61/63

55/59

53/54

53/54

54/55

57/58

ms

%
100

Program
calculation
time

Capacity
utilization of
the PLC

sec

Initialization
time (in the
image)

1-3

5-6

52-53

51-53

104-106

44-45

87-89

cycles

Required
cycles to
recognize
changes

907 AC 1131/Issue: 07/00

70/210

350/420

2860/3021

2754/2862

5512/5724

2376/2475

5959/5162

ms

Required time
to recognize
changes
(min / max)

PLC_PRG
_10000binre Anweisungen
_10000WortAdd
ARCNET-Datenaustausch

PLC_PRG
_10000binre Anweisungen
_10000WortAdd
ARCNET-Datenaustausch

PLC_PRG
_10000binre Anweisungen
_10000WortAdd
ARCNET-Datenaustausch

PLC_PRG
_10000binre Anweisungen
_10000WortAdd
ARCNET-Datenaustausch

Auslastung
OPC-Allgemein
Int_100

Auslastung
OPC-Allgemein
Int_1000, 200 of
them released

Auslastung
OPC-Allgemein
Int_1000, 300 of
them released

Auslastung
OPC-Allgemein
Int_1000, 400 of
them released

907 AC 1131/Issue: 07/00

Program
Blocks

OPC variables

T=70
T=70

ARCNET

T=70

ARCNET
serial

T=70

T=70

ARCNET
serial

T=70

T=70

ARCNET
serial

T=70

serial

Connection
to the PLC

Cyclic task
(C)
Task
(T=xxms)

4-25

87-88

92-93

87-88

92-93

86-88

91-92

86-88

51

53/56

51

51/52

51

51/58

51

52/61

ms

%
91-93

Program
calculation
time

Capacity
utilization of
the PLC

sec

14-16

66-67

11-13

50

8-9

34-35

4-6

18-19

cycles

Required
cycles to
recognize
changes

OPC test

Initialization
time (in the
image)

980/1120

4620/4690

770/910

3500

560/630

2380/2450

280/420

1260/1330

ms

Required time
to recognize
changes
(min / max)

PLC_PRG
_10000binre Anweisungen
_10000WortAdd
ARCNET-Datenaustausch
MODBUS

Auslastung
OPC-Allgemein
Int_1000, 486 of
them released

OPC test

PLC_PRG
_10000binre Anweisungen
_10000WortAdd
ARCNET-Datenaustausch

Auslastung
OPC-Allgemein
Int_1000, 486 of
them released

Program
Blocks

OPC variables

T=60

T=70

ARCNET

T=70

ARCNET
ARCNET

T=70

serial

Connection
to the PLC

Cyclic task
(C)
Task
(T=xxms)

4-26

89-90

96-100

87-89

51

52/53

51

51/52

ms

%
93

Program
calculation
time

Capacity
utilization of
the PLC

sec

Initialization
time (in the
image)

19-20

49-53

16-18

78-80

cycles

Required
cycles to
recognize
changes

907 AC 1131/Issue: 07/00

1330/1400

2940/3180

1120/1260

5460/5600

ms

Required time
to recognize
changes
(min / max)

Index

ABB_LEER.PRO 3-6
accessing address of boolean variables when
importing a project 3-11
accessing direct addresses when importing projects
3-10

not imported program parts from 907 PC 331 3-10

P
peculiarities for forcing and overwriting in version
V4.1 2-27
peculiarities of batch operation in version V4.1 2-30
Perform cold start 2-23
PLC browser 2-24
procedure for importing the project 3-8
project protection for logging in to the controller 2-32

C
code and data size 2-20
code size 2-20
configuration files for the controllers 2-19
controller configuration - changing the PLC 2-18
controller configuration - entering the PLC 2-16
controller configuration - how to enter the PLC 2-17
Create boot project 2-22
creating and modifying your own library 2-38

R
RETAIN variables - note for program change 2-33
reworking projects from 907 PC 331 3-10

data size 2-21

sequence of steps to import the project 3-6


Settings for Force 2-22

E
V

entering the PLC into the controller configuration 216


example program using 07 KT 97 2-2

variable name for importing a project from


907 PC 331 3-7

Flash user program 2-22

what's new in version V4.1 2-1


Write user program to SMC 2-23

H
how to enter the PLC into the controller configuration
2-17

I
importing a project - creating an ASCII file of the
program 3-4
importing a project creating an ASCII file of the
variables list 3-2
importing a project sequence of steps 3-6
importing projects from 907 PC 331 3-1
importing step chains from 907 PC 331 3-9
Info on project on PLC 2-23

M
menus in the Online main menu 2-22

907 AC 1131/Issue: 07/00

Index

Printed on chlorine-free bleached paper

ABB Schalt- und Steuerungstechnik GmbH


Eppelheimer Strae 82 Postfach 10 50 09
D-69123 Heidelberg
D-69040 Heidelberg
Telephone
Telefax
E-Mail
Internet

+49 6221 777-0


+49 6221 777-111
desst.helpline@de.abb.com
http://www.abb-sst.de

Printed in the Federal Republic of Germany (07.2000)