Rockwell-automation 57C620 AutoMax Programming Executive Version 3.8 Instrukcja Użytkownika Pobierz pdf (Strona 26)

2Ć4 AutoMax Programming Executive Version 3.x

2.2 Introduction to Configuring Racks and

Variables

Once you create the system/section/rack structure for your

application, you can begin to configure the hardware in your

installation. Hardware configuration consists of adding modules to

each rack (including network and remote racks, UDC modules, and

PMI

rail hardware) to reflect the actual installation. AutoMax Executive

V3.x checks that modules are added properly

. F

or example, a

second AutoMax Processor module can be added only after a

Common Memory Module (M/N 57C413 or 57C423) has been

added.

If your application includes modules that are

not supported in

V3.x, you can use generic" modules. There are three generic

modules: one with 32,768 registers (GEN32K), one with 8000H

registers in hex (GEN32KH), and one with 32 registers (GEN32) for

use in a remote I/O rack (or in a main rack when 32 registers are

sufficient). Note that GEN32K and GEN32KH modules can be used

only in a rack that contains an AutoMax Processor module.

After you have added a module, you can map variables to I/O points

or common memory on that module using forms" tailored as

required for the specific register organization on each module. This

variable configuration map," along with information about the

application tasks for the rack, is stored in databases, and must be

compiled and downloaded to the rack along with application tasks

before application tasks can run in the rack. This configuration

information is sometimes called the configuration task.

After you have completed the physical configuration of your system,

you can generate a bill of material which lists all of the racks, heads,

rails, and modules used in the system along with the needed

batteries,

cables, and optional hardware and software. See Appendix

L for additional information.

2.3 Introduction to Creating Application Tasks

After you have configured I/O points and common memory using

variable

names, you can create application tasks

using these variable

names instead of locations. You can create BASIC tasks, PC/Ladder

Logic

tasks, and Control Block tasks. BASIC and

Control Block tasks

are stored in text files which are edited using a text editor; PC/Ladder

Logic tasks are stored in binary files and edited using a custom

editor. A text editor (Norton Editor) and the PC Editor are both

included with the AutoMax Programming Executive software. In

addition, you can create include" files which are added to a BASIC

or Block task when it is compiled (by using the BASIC language

INCLUDE statement).

Once the variables have been configured and the application tasks

created,

you can compile the tasks

to create object code that will run

on the AutoMax Processor or UDC module(s) in the rack. PC/Ladder

Logic tasks are stored as object code and do not need to be

compiled.

1 2 ... 21 22 23 24 25 26 27 28 29 30 31 ... 297 298

Komentarze do niniejszej Instrukcji

Brak uwag

Rockwell-automation 57C620 AutoMax Programming Executive Version 3.8 Instrukcja Użytkownika Strona 26

Komentarze do niniejszej Instrukcji

Powiązane produkty i podręczniki dla Ekwipunek Rockwell-automation 57C620 AutoMax Programming Executive Version 3.8