Specifications

A-16

A LAUER driver

„.“ This point lights as so soon as the corresponding channel has rec-

eived a tested package and is thus ready for the data interchange

between the PCS 830.3/31 and the programmable controller. With

an increasing data throughput this point will be dimmed (scan time

depended). This can be influenced by specifying the ZV, S,... timeout

parameter and the „AA“ driver parameter. This determines both the

time monitoring for the communication as well as the maximum packet

length for the serial transfer. For some PCS operating consoles, this

time can also be influenced by deactivating the transfers (LEDs,

message blocks).

„F“ (flashing). The corresponding channel is set to the DIAG diagnosis

function. The cross-reference list was incorrectly received. This

function is only possible along with the CL300 and CL500 and the

examples con-tained on the floppy disk.

A2.2 Description of the handling software

The following directories are located on the floppy disk:

CL300: 3P83110.300 for CL300

CL400: 4P83110.C00 for CL400

CL500: 5P83110.500 for CL500

PC600: 6P83110.600 for PC600

The enclosed -PCSKOMM PB (for the PC600 it is an FB) determines the

data transfer between the transfer area (a data block by default) and the

PCS 830.3. The data block can be parameterized and can be used for all

three channels of the PCS 830.3. It can also be used for the PCS830.1.

Call examples along with the handling blocks are available on the floppy

disk. The README.DOC file contains current notes concerning the use

of the various projects. The calls of the handling block for the interface

two and three must be removed if you use the PCS 830.1.

1. The handling block uses the MBs 246 to 255 (PC600: MBs 502 to

512) as temporary flags. Writing to these MWs does not influence

the handling block as long as they are not simultaneously used by

interrupt programs. The contents must be written newly on entring

the PB and saved on exit if these MWs are required by other PBs or

FBs. In no case interrupt programs are allowed to write to these

MWs. This also applies to the parameterizable INIT PB or FB which

is called at communication start. The use of these flag bytes in this

block is not recommended.

2. The transfer area may not be specified within the data block when

using EPROM modules (for the programmable controller program).

In this case, the cross-reference DBs must be adjusted in such a

way that the system area and the used variables are located in the

RAM area of the CPU (for instance in the data buffer).