Bosch Rexroth 1070072135 CL400 / CL500 PBK5MIF Software Module Software Module Description Manual

CL400 / CL500

PBK5MIF Software Module

Software Module Description

Antriebs- und Steuerungstechnik

Edition 102

CL400 / CL500

PBK5MIF Software Module

Software Module Description

1070 072 135-102 (99.11) GB

E

1992–1999 by Robert Bosch GmbH, Erbach / Germany

All rights reserved, including applications for protective rights.

Reproduction or distribution by any means subject to our prior written permission.

Discretionary charge 10.00 DM

Contents V

Contents

1070 072 135-102 (99.11) GB

2

2.1

2.2

2.3

2.4

1

1.1

1.2

1.3

1.4

1.5

1.6

3

3.1

3.2

3.3

4

4.1

4.2

6

7

7.1

7.2

7.3

5

5.1

5.2

5.3

5.4

5.5

5.6

5.7

5.8

5.9

5.10

Page

Safety Instructions

Standard operation

. . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Qualified personnel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Safety markings on components . . . . . . . . . . . . . . . . . . . . . . . . . .

Safety instructions in this manual . . . . . . . . . . . . . . . . . . . . . . . . . .

Safety instructions concerning the described product . . . . . . . .

Documentation, version and trademark . . . . . . . . . . . . . . . . . . . .

PBK5MIF and MOBY-I

Mobile Data Storage System

Filehandler

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Internal Structure of Mobile Data Storage Unit

Communications between PBK5MIF and PBK

. . . . . . . . . . . . . .

. . . . . . . . . . . . . .

Manufacturing Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

PBK5MIF Module Structure . . . . . . . . . . . . . . . . . . . .

Differences between PROFI and WinSPS-based programming

Module Calls and Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

PBK5MIF Data Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

WorkDB – Working Area Data Module WorkDB

PBK Parameters

. .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MOBY I/F Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BefDB – Command Area Data Module

Format

. . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Create . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Cover

Write

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Read

Delete

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Dir

Load

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Move . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5–1

5–4

5–6

5–7

5–8

5–9

5–10

5–11

5–12

5–14

5–15

DatDB – Data Area Data Module

Sample Program

OB1.P5O

. . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Anlauf.P5O

Beispiel.S5S

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6–1

7–1

7–2

7–4

7–5

2–1

2–4

2–5

2–7

2–8

3–1

3–1

3–2

3–5

4–1

4–2

4–4

1–1

1–1

1–1

1–3

1–4

1–5

1–6

VI Contents

Page

8

8.1

8.2

8.3

8.4

9

9.1

9.1.1

9.1.2

9.1.3

9.1.4

9.2

9.2.1

9.2.2

9.2.3

9.2.4

9.2.5

9.2.6

10

A

A.1

A.2

A.3

EAKO – Approach/Departure Monitoring . . . . . . .

Definition of Terms

EAKO 0

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

EAKO 1

EAKO 4

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

8–1

8–2

8–3

8–4

8–4

Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Error type 0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

P PBK5MIF parameter error . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

D Request-specific errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

> System Errors reported by the PBK hardware module . . . .

> System Error reproted by PBK5MIF FB.

. . . . . . . . . . . . . . . . .

Error Type 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

A Protocol Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B SLG Errors

C MDS Errors

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

D Request-specific errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

E Directory-related errors

F File–specific errors

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

9–1

9–2

9–2

9–3

9–4

9–4

9–5

9–5

9–6

9–6

9–9

9–10

9–10

Characteristic Data . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–1

Appendix

Abbreviations

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Amendments

Index

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

A–1

A–1

A–2

A–3

1070 072 135-102 (99.11) GB

Safety Instructions 1–1

1 Safety Instructions

Before you start working with the PBK5MIF Software Module, we recommend that you thoroughly familiarize yourself with the contents of this instruction manual. Keep this manual in a place where it is always accessible to all users.

1.1

Standard operation

This instruction manual presents a comprehensive set of instructions and information about the software module required for installation and operation of the Peripheral Bus Interface Module.

The products described hereunder

D were developed, manufactured, tested and documented in accordance with the relevant safety standards. In standard operation, and provided that the specifications and safety instructions relating to the project phase, installation and proper operation of the product are followed, there should arise no risk of danger to personnel or property.

The prerequisites for trouble-free service and safe operation of the product are proper transport, handling and storage, placement and installation, plus careful operation of the equipment.

1.2

Qualified personnel

The requirements pertaining to qualified personnel are based on the job specifications as outlined by the ZVEI (central association of the electrical industry) and VDMA (association of German machine and plant builders) professional associations in Germany. Please refer to the following Germanlanguage publication:

Weiterbildung in der Automatisierungstechnik

Hrsg.: ZVEI und VDMA

MaschinenbauVerlag

Postfach 71 08 64

60498 Frankfurt

This instruction manual is specifically designed for PLC specialists. They will require specific knowledge of the CL400/CL500 Programmable Logic Controllers and of the PBK5MIF Peripheral Bus Interface Module.

Interventions in the hardware and software of our products which are not described in this instruction manual may only be performed by specially trained

Bosch personnel.

Unqualified interventions in the hardware or software or non-compliance with the warnings listed in this instruction manual or indicated on the product may result in serious personal injury or damage of property.

1070 072 135-102 (99.11) GB

1–2 Safety Instructions

Installation and maintenance of the products described hereunder is the exclusive domain of trained electricians as per VDE 1000-10, who are familiar with the contents of this manual.

Trained electricians are persons of whom the following is true:

D

They are capable, due to their professional training, skills and expertise, and based upon their knowledge of and familiarity with applicable technical standards, of assessing the work to be carried out, and of recognizing possible hazards.

D

They possess, subsequent to several years’ experience in a comparable field of endeavour, a level of knowledge and skills that may be deemed commensurate with that attainable in the course of a formal professional education in this area.

With regard to the foregoing, please read the information about our comprehensive training program. You’ll find a listing of our seminars on the front inside cover of this instruction manual. The professional staff at our training centre will be pleased to provide detailed information. You may contact the centre by telephone at (+49) (0)6062 78-258.

1070 072 135-102 (99.11) GB

Safety Instructions 1–3

1.3

Safety markings on components

Danger: High voltage!

Danger: Battery acid!

Electrostatically sensitive components!

Disconnect at mains before opening!

Pin for connecting PE conductor only!

Functional earthing/low noise earth

For screened conductor only!

1070 072 135-102 (99.11) GB

1–4 Safety Instructions

1.4

Safety instructions in this manual

DANGEROUS ELECTRICAL VOLTAGE

This symbol is used to warn of the presence of a dangerous electrical

voltage. Insufficient compliance with or failure to observe this warning may result in personal injury.

DANGER

This symbol is used wherever insufficient or lacking compliance with instructions may result in personal injury.

CAUTION

This symbol is used whenever insufficient or lacking compliance with instructions may result in damage to equipment or data files.

.

This symbol is used to alert the user to an item of special interest.

1070 072 135-102 (99.11) GB

Safety Instructions 1–5

1.5

Safety instructions concerning the described product

DANGER

Danger to Personnel and Equipment!

Test every new program before operating the system!

DANGER

Retrofits or modifications may adversely affect the safety of the products described!

The consequences may be severe personal injury, damage to equipment or environmental hazards. Therefore, any system retrofitting or modification utilizing third-party components will require express approval by Bosch.

1070 072 135-102 (99.11) GB

1–6 Safety Instructions

1.6

Documentation, version and trademark

Documentation

The present instruction manual provides information about the PBK5MIF

Software Module required for the installation and operation of the PBK

Peripheral Bus Interface Module, and about the MOBY I/F Channel Module.

Overview of instruction manuals:

Instruction Manuals

PBK Peripheral Bus Interface Module, Module

Description

Language Part no.

German

English

1070 070 127

1070 072 133

Spanish

MOBY I/F Channel Module, Module Description German

1070 072 330

1070 070 139

PBK5MIF Software Module, Software Module

Description

English

Spanish

German

English

Spanish

1070 072 136

1070 072 331

1070 072 035

1070 072 135

1070 072 332

L

This asterisk symbol indicates that the instruction manual is describing an activity you shall be required to perform.

Amendments

Changes in this instruction manual from the previous manual version are denoted by black vertical bars in the right-hand margin.

.

The “LEERER MERKER Amendments” section lists the changes made since the preceding edition.

Trademarks

All trademarks referring to software that is installed on Bosch products when shipped from the factory represent the property of the respective manufacturers.

When shipped from the factory, all installed software is protected by copyright. It may therefore be duplicated only with prior permission by Bosch or in accordance with the licensing agreements with the respective manufacturer or copyright owner.

MS-DOS r und Windows t are registered trademarks of Microsoft Corporation.

MOBY r is a registered trademark of Siemens AG.

1070 072 135-102 (99.11) GB

PBK5MIF and MOBY-I Mobile Data Storage System 2–1

2 PBK5MIF and MOBY-I Mobile Data Storage System

The PBK5MIF Software Module controls the data traffic between the PLC program and the PBK Peripheral Bus Interface Module equipped with the

MOBY I/F channel module.

The MOBY I/F Channel Module is a component of the MOBY-I inductive identification system manufactured by Siemens AG. The identification system encompasses

D the MOBY I/F Channel Module,

D the SLG Read/write unit, and

D the MDS Mobile Data Storage unit.

The MOBY I/F channel module is inserted in the PBK Peripheral Bus Interface Module.

In addition, for the purpose of startup and testing the MOBY I/F, the STG 4F

Service and Testing unit is available.

With regard to its functionality, the Bosch MOBY I/F Channel Module corresponds to the Siemens CM 423 Channel Module.

.

For detailed information about the MOBY-I Identification System, refer to the documentation provided by Siemens AG. The following catalogue may provide introductory reading:

MOBY

Identsystem MOBY-I

E86060-K6910-A101-A2

For a detailed description of the PBK Peripheral Bus Interface Module, refer to the following instruction manual:

PBK Peripheral Bus Interface Module

Module Description

Order no. 1070 072 133

For a detailed description of the MOBY I/F Channel Module, refer to the following instruction manual:

MOBY r

I/F Channel Module

Module Description

Order no. 1070 072 136

The intelligent SLG Read/write unit is connected to the peripheral bus of the control unit via the MOBY I/F Channel Module and the PBK Peripheral Bus

Interface Module.

The data transmission between the SLG and the MDS is handled inductively via frequency modulation.

1070 072 135-102 (99.11) GB

2–2 PBK5MIF and MOBY-I Mobile Data Storage System

Read/ write unit

Read/ write unit

Read/ write unit

Read/ write unit

Mobile data storage

Mobile data storage

Mobile data storage

Mobile data storage

The PBK5MIF Software Module and the MOBY I/F support the Filehandler file management system.

To handle the data transfer, the use of the PBK5MIF Software Module is required. The PBK5MIF must be integrated into the PLC program.

.

The PLC program may utilize only the PBK5MIF module to access data on the PBK! All other types of read or write accesses to the addresses on the PBK Peripheral Bus Interface Module will cause loss of synchronization.

1070 072 135-102 (99.11) GB

1070 072 135-102 (99.11) GB

PBK5MIF and MOBY-I Mobile Data Storage System 2–3

Major PBK5MIF functions:

D

Adapting the data structure of the PLC application program to that of the

PBK and MOBY I/F.

D Exchanging commands and data with the PBK.

D

Processing error messages for the PLC program.

The data transfer sequence between the PBK5MIF and MDS may be divided into 3 sections:

D Transfer of commands, parameter values and/or data to the SLG.

D

Data exchange between SLG and MDS.

D Transfer of parameter values or data between CL500 and SLG.

2–4 PBK5MIF and MOBY-I Mobile Data Storage System

2.1

Filehandler

The Filehandler file management system facilitates a simple means of managing files on the MDS. The system has the characteristics of a DOS operating system:

D

The user can use filenames to address his data.

D Files of different sizes can be managed.

D

Access rights can be assigned to files.

Filehandler

MDS:

The data is stored in a RAM or

EEPROM module onboard the MDS.

SLG:

DOS operating system

Floppy disk:

The data is stored on a floppy disk.

The SLG modulates the data inbound from the MOBY I/F and demodulates the data inbound from the MDS.

Floppy disk drive:

The floppy disk drive modulates the data from the PC into a write current and demodulates the read current.

The MDS must be positioned within the transmission range of the SLG. Depending on the type of SLG employed, the transmission range may be several centimetres.

PLC:

The MOBY I/F and PBK comprise the interface to the PLC.

The positioning of the floppy disk above the read/write head must be very precise because the magnetic fields are very small.

PC:

The PC controls the floppy disk drive via an interface.

1070 072 135-102 (99.11) GB

PBK5MIF and MOBY-I Mobile Data Storage System 2–5

2.2

Internal Structure of Mobile Data Storage Unit

MDS system area

Directory

File Allocation Table (FAT)

Block

MDS system area contains all MDS-specific data (e.g., MDS name, MDS type, last SLG number, etc.).

The directory contains the names of all files being stored, together with the corresponding parameter values. In each case, the number of available directory entries depends on the respective MDS type.

The FAT File Allocation Table handles the allocation of all data blocks belonging to a particular file.

The payload data area is divided into blocks. In each case, both the number of blocks and the block size depend on the MDS type being used.

From the data held in both directory and FAT, the MOBY I/F Channel Module calculates a checksum. This checksum is stored onboard the MOBY I/F.

The “Move” and “Load” commands und Load can be used to write the information describing both the directory and the FAT into the data field of the of the PLC. In this way, the data will be available immediatly after a power failure, without having to be newly calculated.

1070 072 135-102 (99.11) GB

2–6 PBK5MIF and MOBY-I Mobile Data Storage System

When a new MDS arrives at an SLG, the MOBY I/F first compares the checksum.

D

If the checksum is identical to the checksum stored onboard the MOBY

I/F, the system will initiate the execution of the command.

D

If the checksum stored onboard the MOBY I/F is not identical with that of the MDS, the MDS checksum will be newly calculated.

D If the calculated checksum matches that of the MDS, this indicates that the data structure onboard the MDS has been modified. The corresponding directory and FAT information will then be stored onboard the MOBY I/F. This procedure can be extremely time-consuming, causing the production cycle to be halted.

To prevent this problem from occurring, the manufacturing process should utilize, onboard all MDS units, a standardized, fixed file structure; refer to Section 2.4 Manufacturing Sequence.

D

If the checksum calculation produces a value that differs from the

MDS checksum, the MDS will be defective.

1070 072 135-102 (99.11) GB

PBK5MIF and MOBY-I Mobile Data Storage System 2–7

2.3

Communications between PBK5MIF and PBK

On the hardware side, communications between the CL500 and the PBK/

MOBY I/F are implemented via a Dual-Port-RAM module.

The software-based interface is implemented on the basis of command and acknowledgement messages.

D When the PLC program initiates a command, it is transferred to the

MOBY I/F via data channel 1.

D The filehandler reads the data, starts command-specific functions and then returns a corresponding command acknowledgement to the CL500.

D

The PBK5MIF responds by updating the status bits, and by setting the

Ready bit.

The maximum size of the user data per message (and thus also per cycle) is

D

Reading: 240 bytes

D Writing: 226 bytes

1070 072 135-102 (99.11) GB

2–8 PBK5MIF and MOBY-I Mobile Data Storage System

2.4

Manufacturing Sequence

To ensure properly timed sequences within the manufacturing process, a uniform and permanent file structure is required for all MDS units. During the actual manufacturing process, data access by SLG Read/write units on the various MDS is read/write only.

Time-intensive commands, such as “Format”, are executed onboard a special SLG (head-end) outside of the actual manufacturing process. This ensures that all MDS units within the manufacturing process always utilize the same file structure. The checksum is therefore always identical, dispensing with the requirement of time-intensive reloading of MDS directory information and File Allocation Table.

Batch

Pallets with MDS

Head-end

SLG 1

SLG 2

Defective pallets/MDS

SLG 3

Produced units and pallets/MDS circulation

SLG 5 SLG 4

Finished batch

As dictated by requirements, an MDS at the end of the production process

(SLG 5) can be reprocessed at SLG 1 (head-end).

The head-end performs the following functions:

D Formatting MDS units.

D

Creating files with the use of the “Create” command.

D Sorting out defective MDS units.

D

Monitoring production data.

1070 072 135-102 (99.11) GB

PBK5MIF Module Structure 3–1

3 PBK5MIF Module Structure

This chapter describes the internal structure of the PBK5MIF Software Module. The first section discusses the module call in conjunction with the

PBK5MIF parameters. The second section explains the PBK5MIF data structure, and the division into the data modules.

3.1

Differences between PROFI and WinSPS-based programming

The present documentation discusses the representation of constants and program module calls in the notation generated by the PROFI programming device software. With the use of WinSPS however, constants and program module calls will appear in different notation due to the adaptation to the

IEC1131-3 standard.

The referred differences are shown in the following side-by-side comparison:

Differences in programming and notation of word constants

Data type

Explanation

UINT unsigned integer

Notation

Binary/Dual

INT integer

Text, STRING(2)

Time value, TVALUE

Decimal, word

Decimal, byte/byte

Hexadecimal

Decimal, word

ASCII

Time value (+time base r) r: 0 = 10 ms, 1 = 100 ms

2 = 1 s, 3 = 10 s

K’AB’

PROFI

PLC utility programs

WinSPS

K00000000 00000000B

K11111111 11111111B

K00000D – K63535D

K000/000 – K255/255

K0000H – KFFFFH

K–32768 – K+32767

K–32768D – K+32767D

K0.r – K1023.r

2#0000000000000000

2#1111111111111111

00000 – 65535 in IEC1131 Part 3 not defined

16#0000 – 16#FFFF

–32768 – +32767

‘AB’

T#10ms – T#10230s

T#0.r – T#1023.r

Differences in programming and notation of module calls

Program module/function call

(IEC1131-3)

CM PM

PROFI

PLC utility programs

CM FC

WinSPS

Differences in programming and notation of jump instructions

PLC utility program

PROFI

Jump instruction JPx –label JPx label

WinSPS

Jump destination –label label:

1070 072 135-102 (99.11) GB

3–2 PBK5MIF Module Structure

3.2

Module call

Module Calls and Parameters

The module call for the PBK5MIF must be issued cyclically, including the initial program cycle.

The PBK5MIF utilizes 4 parameters:

D 3 input parameters

D

KanalNr (channel number)

D

WorkDBNr (working data module no.)

D PBK Adr (PBK address)

D

1 output parameter

D Status

CM -PBK5MIF,4 ;Module call

P0 W K1D

P1 W K204D

P2 W AZ8

P3 BY -StatusK1

;Channel number

;Data module number

;Start address

P0 KanalNr

Channel number of MOBY I/F channel module onboard the PBK, word.

This parameter value transfers the channel number of the MOBY I/F to the

PBK5MIF. The channel number must be between 1 and 4, e.g., K1D for channel 1.

P1 WorkDBNr

Data module number for the work area of the PBK5MIF, word.

For each MOBY I/F channel module installed onboard the PBK, one

WorkDB data module (min. 450 Byte) must be generated. This parameter value transfers the data module number as a numerical value without operand identifier. The permissible value is between 0 and 511 (effective with function block v1.7), e.g., K16D for data module DB16.

1070 072 135-102 (99.11) GB

P2 PBKAdr

PBK5MIF Module Structure 3–3

PBK start address, word

The PBK occupies 4 input bytes and 4 output bytes on the CL500 control unit.

The PBK start address can only be a multiple of 4. The PBK start address must be entered with the operand identifier. The output range must be specified. The input range will then be automatically reserved in parallel with the input range. The following address ranges are permitted:

D IO0 through IO60

D

EO0 through EO60

The PBK start address is selected by setting the S1 DIP switch on the PBK.

The address range is set by positioning jumpers JP1 and JP2.

.

Refer to technical documentation:

CL500

PBK Peripheral Bus Interface Module

Module Description

Order no. 1070 070 133

The following assignments apply to address ranges:

PBK address range

I/O field

EI/EO field

Jumpers

JP1/JP2

Address range in PLC program

2 through 3 II/IO

1 through 2 EI/EO

Example of P2

IO4

EO4

1070 072 135-102 (99.11) GB

3–4 PBK5MIF Module Structure

P3 Status

PBK5MIF status, byte

The value of parameter P3 transfers the status of the PBK5MIF to the PLC program.

Bit

0

Name

Active

1 WorkDB

2 through 6

7 Error

Explanation

1: PBK5MIF is enabled for command execution

0: PBK5MIF is not active

1: The data module specified with parameter P1 does not exist, or has not been programmed with the required

450 byte minimum size.

0: No error not used

1: An error has occurred during command processing.

The precise cause of the error is stored in the WorkDB data module, in D7 Type and D8 ErrCode; refer to Chapter 4, WorkDB Working Area, and Chapter 9, Error Messages.

.

The bit remains set (HIGH) for the duration of only one PLC cycle.

For this reason, the data in D7 and D8 of the WorkDB data module must be interpreted or stored immediately.

0: No error detected.

1070 072 135-102 (99.11) GB

PBK5MIF Module Structure 3–5

3.3

PBK5MIF Data Structure

The data structure of the PBK5MIF encompasses 3 areas:

D Working area : WorkDB, refer to Chapter 4

D

Command area : BefDB, refer to Chapter 5

D Data area : DatDB, refer to Chapter 6

The areas are linked by means of pointers.

Example of PBK5MIF data structure distribution to data modules

-PBK5MIF

-WorkDB

P1 -WorkDBNr

-BefDB

-DatDB

1070 072 135-102 (99.11) GB

Example of data module layout table:

DM No.

DM

DM

DM

DM

Name Comment R/E

0 R

1 WorkDB1 Work area for channel module 1 R

2

BefDB DM contains command parameters

R

3

QuellDB Source data for “Write” command

R

DM

DM

4 ZielDB Destination area for “Read” command

5 DirDaten Destination area for “Dir” command

R

R

Length

0

450

98

512

512

512

.

The WorkDB data module must always be present and may not be used for other data!

A WorkDB must be created for each MOBY I/F channel module, e.g.,

WorkDB1, WorkDB2, and so forth.

3–6 PBK5MIF Module Structure

.

Appropriate programming can be used to combine the BefDB and

DatDB data modules.

To effect the division, or segregation, of commands and data, two structures are possible:

D All commands in one data module, and the data in one or more separate data modules (refer to illustration).

D Each command can be stored in a separate data module containing the parameters and data for that command.

In the example, all commands are entered in one data module. The data is handled by three data modules.

D

One QuellDB source data module, containing the data for the “Write” command.

D One ZielDB destination data module, into which the data for the “Read” command is written.

D

One DirDB directory data module, into which the “Dir” command writes the MDS directory.

1070 072 135-102 (99.11) GB

WorkDB – Working Area Data Module WorkDB 4–1

4 WorkDB – Working Area Data Module WorkDB

.

A WorkDB data module must be created for each MOBY I/F channel module.

The size of the data module must be a minimum of 450 bytes. The WorkDB data module encompasses 3 data areas:

D PBK parameters, D0 through D14

D

MOBY I/F parameters, D18 through D28

D Internal area, from D30 onwards

.

The WorkDB data module must always be present, and may not be used for other data!

1070 072 135-102 (99.11) GB

4–2 WorkDB – Working Area Data Module WorkDB

4.1

PBK Parameters

.

Some data in the WorkDB data module are processed and written in byte-wise fashion!

DB 1 Name: WorkDB1 Comment: FB working area for Channel1

No.

Byte

D 0

2

D 2 2

D 4 2

D 6 1

D 7

1

D 8 4

D 12 1

D 14 1

D 15

1

Symbol Type

PBKCom binary

BefDBNr decimal

BefOff

Chk

Typ decimal

ASCII

ASCII

ErrCode ASCII

Typ/Code ASCII

Module decimal

Sg

N

N

N

N

N

N

N

N

N

Data field / Comment

0

2

0

0

00 not assigned

Explanation

PBK commands, all-purpose

RAM/EPROM: R

F

B

Pointer at parameterized command D

Pointer at parameterized command

Data transfer with/without checksum

D

Refer to Chapter 9, Error Messages

Refer to Chapter 9, Error Messages

Active command type

Channel module type onboard the PBK H

D0 PBKCom

Bit Description

0 Start signal

1 through 15 not assigned

Start signal for the PBK5MIF to initiate execution of the command parameterized in the BefDB data module. The status, and not the Der Zustand, and not the edge, of Bit 0 is interpreted. Bit 0 must be set by the PLC program. Subsequent to the start of command execution, the PBK5MIF resets the bit.

D2 BefDBNr

Pointer to the BefDB data module. This data module stores the command that is to be applied on the MDS.

Example of D2:

DM2 data module: 2 D

D4 BefOff

Pointer to the data word in the BefDB data module containing the command.

Example of D4:

Offset for data word number 0 : 0 D

1070 072 135-102 (99.11) GB

D6 Chk

D7 Typ

D8 ErrCode

D12 Typ/Code

D14 Modul

WorkDB – Working Area Data Module WorkDB 4–3

Enabling/disabling the control byte which safeguards data transmission between the ZS and the PBK on the system bus of the CL500.

Data type: ASCII

D

1 : Operation with control byte

D 0 : Operation without control byte

.

The control byte extends the cycle time for reading files by the factor 1.3, and for writing to files by the factor 1.5.

The value in D7 will be valid only as long as Bit 7 in status parameter P3 of the

PBK5MIF is set.

The error type is described with ASCII characters 0 or 1. For a detailed description, refer to Chapter 9, Error Messages.

The value in D8 will be valid only as long as Bit 7 in status parameter P3

Status of the PBK5MIF is set.

The error code consists of 4 ASCII characters. For a detailed description, refer to Chapter 9, Error Messages.

D12 contains the current or the last-processed command type and command code.

D14 contains the code for the module type:

D

MOBY I/F 00

1070 072 135-102 (99.11) GB

4–4 WorkDB – Working Area Data Module WorkDB

4.2

MOBY I/F Parameters

.

Some data in the WorkDB data module are processed and written in byte-wise fashion!

DB 1 Name: WorkDB1 Comment: FB working area for Channel1

No.

Byte Symbol Type Sg Data field / Comment

D 16 2

D 18 2

D 20 1

Reserve

SLGNr

EAKO decimal

ASCII

N

N

65535; Test number

4

D 21 1

D 22 1

D 23 1

D 24

D 26

D 28

2

2

2

ECC ASCII

R esetTyp ASCII

ABTA

FHCom

FHStatus

DatSize hex binary binary decimal

N

N

N

N

N

N

0

C

0

0

0

Explanation

RAM / EPROM: R

F

D

D Read/write unit number

Control of approach/departure monitoring with/without error correcting code

“Reset” FH command cancellation type

Scanning time when addressing an

MDS

Short commands without parameters in

BefDB

Status messages from file handler module

Size of received payload data in bytes

D

B

B

B

D

D18 SLGNr2

SLG Read/write unit number; this number is written to the MDS prior to every processing task. It enables the Filehandler to distinguish the MDS from one another.

Possible SLG numbers range from 1 through 65534.

CAUTION

The number 65535 has been reserved for testing purposes. It has the effect that the next MDS subsequent to a “Next” command can be the same MDS.

.

Changes to data word D18 will take effect only after a Reset has been performed in D24 of FHCom.

1070 072 135-102 (99.11) GB

D20 EAKO

D21 ECC

D22 ResetTyp

WorkDB – Working Area Data Module WorkDB 4–5

Control of approach/departure monitoring, refer to Chapter 8, EAKO – Approach/Departure Monitoring.

Data type: ASCII

D 0, Presence fluctuation are reported to the PLC program. The “Next” command must be issued by the PLC program.

D

1, Prior to the initiation of the command, an MDS must be within transmission range of the SLG. The “Next” command is not mandatory.

D 4, The detection or recognition of an MDS is handled by the PLC program, e.g., via position switch.

.

Changes to data word D20 will take effect only after a Reset has been performed in D24 of FHCom.

Error Correcting Code, ECC driver for increased data security on the MDS.

.

The ECC driver extends the access time to the data onboard the MDS.

Data type: ASCII

D 0, ECC driver disabled

D

1, ECC driver enabled

.

Changes to data word D21 will take effect only after a Reset has been performed in D24 of FHCom.

The ResetTyp (Reset type) indicates the type and mode of the abort

(or reset).

Data type: ASCII

There are 2 kinds of ResetType:

D

B, Hard Reset, the Reset occurs immediately and without concern for the data structure.

D

C, Soft Reset, e.g., within the framing of a “Write” command, causes the currently valid internal MDS system areas (DIR, FAT) to be updated.

CAUTION

The responsibility for data rests with the user!

.

Changes made in data word D22 will take effect only after a reset has been performed in D24 of FHCom.

1070 072 135-102 (99.11) GB

4–6 WorkDB – Working Area Data Module WorkDB

D23 ABTA

D24 FHCom

Scanning interval in the presence of an MDS. The parameterization described below is applicable for all MDS types of the MOBY-I product range.

Bit Description

0 through 5 Time value

6 and 7 Time factor

Time value

D 0 through 3Fh (0 = continuous field scan)

Time factor:

D 00 = 0,01 s

D

01 = 0,1 s

D 10 = 1,0 s

D

11 = 10 s

Bit

0

Description

Reset

1 Next

2 through 15 internal use

Explanation:

D Reset

The Reset is initiated by the PLC program or PBK5MIF, and accepted at any point in time. Subsequent to the start of the command, the Reset bit is reset by the PBK5MIF.

The Reset command resynchronizes data exchange and also contains the “Next” command.

D

Next

The “Next” command is set by the PLC program. The processing of an

MDS is concluded. The next command is executed with the next MDS that follows.

In plants requiring critical timing accuracy, this procedure can be used to transfer the next command for the succeeding MDS already at a point where the old MDS is still within the transmission range of the SLG Read/ write unit, refer to Chapter 8, EAKO – Approach/Departure Monitoring.

1070 072 135-102 (99.11) GB

D26 FHStatus

1070 072 135-102 (99.11) GB

WorkDB – Working Area Data Module WorkDB 4–7

3

4

1

2

Bit

0

Explanation

ECC

Bat1

Bat2

War1

War2

5

6

7

Anw

STG enabled

Sys

8 through 15 not assigned

Explanation:

D ECC

The MDS data error correction was carried out.

D

Bat1

The MDS battery must be replaced.

D

Bat2

The auxiliary battery of the MDS must be replaced immediately! (Applies to MDS507 only, otherwise always 1.)

D War1

Warning. During command processing, the MDS was located outside of the SLG transmission range. Command execution was completed. However, there exists a possibility that the data read and/or write access onboard the MDS was incomplete.

D

War2

Warning. The correct execution of the “Read” command is not possible because the end of the file was reached.

D Anw

Presence of an MDS within the SLG transmission range.

D 0 no MDS within SLG transmission range

D

1 MDS within SLG transmission range

D STG enabled

Goes HIGH in the following conditions:

D An STG 4F Service and Testing Unit is communicating with the PBK.

and

D A command awaiting execution is present.

.

This may delay execution of the command.

D

Sys

The checksum of the MDS positioned within the SLG transmission range fails to match the checksum stored onboard the MOBY I/F, refer to Section 2.2, Internal Structure of Mobile Data Storage Unit.

.

This extends the execution time for the current command!

4–8 WorkDB – Working Area Data Module WorkDB

D28 “transmission range” DatSize

D28 contains information about the received payload data.

D

Subsequent to invoking the “Read” command with the addition of the

“Read Entire File” switch, the address D28 DatSize will contain the file size in bytes.

D

Subsequent to invoking the “Dir” command, the address D28 DatSize will contain the number of the files stored onboard the MDS.

1070 072 135-102 (99.11) GB

BefDB – Command Area Data Module 5–1

5 BefDB – Command Area Data Module

The PBK5MIF differentiates between two types of commands:

D Commands without parameterization:

D

“Reset” and

D “Next”

These are invoked by setting the associated bit in D24 of FHCom in the

WorkDB data module.

D

Parameterized commands, these are invoked by setting Bit 0, Start signal, in D0 of PBKCom in the

WorkDB data module.

This chapter describes the parameterized commands and related programming procedures.

The parameterized commands must be written into a data module. The payload data for the commands must also be written into a data module, refer to

Chapter 6, Datenbereich DatDB.

D2, BefDBNr, of the WorkDB data module contains the BefDB data module in which the parameterized commands are stored.

D4, BefOff, of the WorkDB data module contains the data word in the BefDB that contains the selected command. The subsequent data words contain the parameter values for the command.

.

Each command block in the BefDB data module must begin with an even-numbered byte address!

1070 072 135-102 (99.11) GB

5–2 BefDB – Command Area Data Module

Example of the command area, BefDB data module

DM 2 Name: BefDB Comment: DM contains command parameter values

No.

Byte Symbol Type Sg Data field/Comment Explanation

Read

D 20

D 28

D 30

D 32

D 34

D 36

D 38

D 0

D 2

D 10

D 12

D 14

D 16

D 18 Write

Format

ASCII

Word

Word

Word

Word

ASCII

ASCII

ASCII

ASCII

Word

Word

Word

Word

ASCII

N

N

N

N

N

N

Y

N

N

N

N

Y

N

N

1R

File.001

0

–1

4

0

1W

File.001

0

512

3

0

1I

[BOSCH ]

Parameterizable commands

Command Explanation

Format

Create

Cover

Write

Read

Delete

Attribute

Dir

Load

Move

Format MDS

Create new file onboard formatted MDS

Lock up MDS file structure

Write data to file

Read data from file

Delete file onboard MDS

Assign attribute to file

Read MDS directory

MDS system area (PLC !

MOBY I/F)

MDS system area (MOBY I/F ! PLC)

RAM/EPROM: R

F

1Y

1G

1L

1M

1G

1W

1R

1D

Command type/Code

1I

1B

D

D

D

D

D

D

D

D

1070 072 135-102 (99.11) GB

BefDB – Command Area Data Module 5–3

Initiating a parameterized command

.

Refer also to Chapter 7, Sample Program, Automatic “Read” command initiation.

Several data modules, connected by pointers, are required to initiate and execute a command.

–PBK5MIF

P1 –WorkDBNr

–WorkDB

–BefDBNr

–BefOff

–BefDB

–DatDB

D

Transfer the WorkDBNr data module number for the work area of the

PBK5MIF in parameter P1.

D

Enter data module for BefDB commands in D2, BefDBNr, of the WorkDB data module.

D Enter pointer to the data word in the BefDB data module containing the command in D4, BefOff.

D

Set start signal, Bit 0 in D0 of PBCom of WorkDB data module, to HIGH

(1).

1070 072 135-102 (99.11) GB

5–4 BefDB – Command Area Data Module

5.1

Format

The “Format” command is used to format an MDS. The MDS is given a name, the type, and an attribute.

CAUTION

Entire MDS data will be deleted!

DM 2 Name: BefDB Comment: DM contains command parameters

No.

Byte Symbol Type Sg Data field/comment Explanation

D

D

D

D

36

38

46

48

Format ASCII

ASCII

Word

Word

N

N

N

N

1I

[BOSCH ]

0006

0001

Command structure

No.

D36

D38

D46

D48

2

1

No. of bytes Designation

2

8

Command type/Code

MDS name

MDS type

Attribute

RAM/EPROM: R

F

H

D

Description

1I max. 8 ASCII characters refer to “MDS Type” table refer to “Attribute” table

1070 072 135-102 (99.11) GB

MDS type

Attribute

BefDB – Command Area Data Module 5–5

.

If an MDS is formatted for ECC operation, D21, ECC, must also be set, refer to Section 4.2, MOBY I/F-Parameters.

MDS type

(hex)

01

02

81

09

89

0A

8A

0B

8B

03

83

04

84

07

87

08

88

05

85

06

86

MDS capacity

(brutto), * operating with ECC

62

62

42

128

112 *

2,045

1,778 *

8,189

7,154 *

32,765

28,658 *

65,533

57,330 *

131,069

114,674 *

262,141

229,362 *

524,285

458,738 *

1,048,573

917,490 *

No. of files

256

256

512

512

512

512

128

128

256

256

32

32

64

64

16

16

3

3

1

2

1

Payload data

(Bytes)

27

12

7

60

45

1,680

1,440

7,456

6,464

31,488

27,520

62,976

54,784

126,720

110,336

257,024

224,256

514,048

448,768

1,035,264

904,960

Bit

0

Explanation

0 Always reads entire system area

1

2

1 Enables checksum mechanism

0 Deletes entire old directory

1 Sets up the old MDS directory on the MDS. Retains the existing file payload data size. If LOW (0), the payload data area will be deleted.

0 Deletes entire MDS

1 Deletes DIR and FAT, retains payload data area.

0 normal 3

1 In each case, counters for write cycles and/or EEC corrections are retained. The counters will be retained even if the system area is faulty.

4 through 7 not used

1070 072 135-102 (99.11) GB

5–6 BefDB – Command Area Data Module

5.2

Create

The “Create” command generates a new file onboard a formatted MDS. The file is entered in the directory and is assigned the file size 0.

.

It is not permitted to create a file with a file name that is already in use.

RAM/EPROM: R

F

DM 2 Name: BefDB Comment: DM contains command parameter values

No.

D

D

D

Byte

50

52

60

Symbol Type

Create ASCII

ASCII

Word

Sg

N

N

N

Data field/comment

1B

File.001

0

Explanation

Command structure

No.

D50

D52

D60

No. of bytes Designation

2

8

1

Command type/Code

File name

Attribute

D

Explanation

1B max. 8 ASCII characters

0 No attribute

1 Read-only

2 Single write access

4 Write access may not increase the file size.

5 As in 4h, but the file may only be read-accessed.

1070 072 135-102 (99.11) GB

BefDB – Command Area Data Module 5–7

5.3

Cover

The “Cover” command can be used to lock the file structure of an MDS. This means that any commands causing checksum modifications and/or additional DIR and/or FAT entries, can be transmitted only by specially autorized users.

Unauthorized access has occurred, if:

D

Files are deleted and/or created.

D File sizes are reduced and/or increased.

D Data storage units (data media) are formatted in the event that these are formatted already.

D Attributes are deleted and/or newly assigned.

DB 2 Name: BefDB Comment: DM contains command parameters

No.

D

D

D

Byte Symbol

COVER

Type Sg Data field/comment Explanation

RAM/EPROM: R

F

Command structure

No.

D

D

D

No. of bytes Designation

2

8

1

Command type/Code

File name

Attribute

Explanation

1C max. 8 ASCII characters

0 Modification of MDS file structure again permitted

1 MDS is to be locked

1070 072 135-102 (99.11) GB

5–8 BefDB – Command Area Data Module

5.4

Write

The “Write” command can be used to write payload data from a data module to a file which was created onboard a formatted MDS using the Create command.

DM 2 Name: BefDB Comment: DM contains command parameters

No.

D

D

D

D

D

D

Byte

18

20

28

30

32

34

Symbol

Write

Type

ASCII

ASCII

Word

Word

Word

Word

Sg

N

N

Y

N

N

N

Data field/comment

1W

File.001

0

512

3

0

Explanation

RAM/EPROM: R

F

D

D

D

D

Command structure

No.

D18

D20

D28

D30

D32

D34

2

2

8

2

No. of bytes Designation

2 Command type/Code

File name

Offset

2

Size

Data module number

DBOffset

Explanation

1W max. 8 ASCII characters

Start position for data writeaccess in the file.

Size of payload data, in bytes, that is to be written.

DM containing the data to be written.

Position in the DM marking the start point for the data write-access.

D28 Offset

The offset can be used to define the position within the file that will be the starting point for data write-access. If the data is to be appended to the existing end of file, the offset value must be defined as –1.

1070 072 135-102 (99.11) GB

BefDB – Command Area Data Module 5–9

5.5

Read

The “Read” command is used to read data from the MDS and write them into a data module.

DM 2 Name: BefDB Comment: DM contains command parameters

No.

D

D

D

D

D

D

Byte

0

2

10

12

14

16

Symbol Type

Read ASCII

ASCII

Word

Word

Word

Word

Sg

N

N

N

Y

N

N

Data field/comment

1R

File.001

0

–1

4

0

Explanation

RAM/EPROM: R

F

D

D

D

D

Command structure

D12

D14

D16

No.

D0

D2

D10

2

2

2

8

2

No. of bytes Designation

2 Command type/Code

File name

Offset

Size

Data module number

DBOffset

Explanation

1R max. 8 ASCII characters

Start position for readaccess in the file.

Size of payload data, in bytes, that is to be read.

DM to which the data from the MDS is to be written.

Start position for data writeaccess in the DM.

D12 Size

If the size is defined as “–1”, the entire file will be read. The size of the payload data, expressed in bytes, can be taken from D28, size, in the WorkDB data module; refer to Section 4.2 MOBY I/F Parameters.

1070 072 135-102 (99.11) GB

5–10 BefDB – Command Area Data Module

5.6

Delete

The “Delete” command removes a file from the MDS.

CAUTION

All data in the file will be lost!

DM 2 Name: BefDB Comment: DM contains command parameters

No.

D

D

Byte

68

70

Symbol Type

Delete ASCII

ASCII

Sg

N

N

Data field/comment

1D

File.001

Explanation

Command structure

No.

D68

D70

No. of bytes Designation

2 Command type/Code

8 File name

RAM/EPROM: R

F

Explanation

1D max. 8 ASCII characters

1070 072 135-102 (99.11) GB

BefDB – Command Area Data Module 5–11

5.7

Attribute

The “Attribute” command can be used to assign read or write attributes to a file.

DM 2 Name: BefDB Comment: DM contains command parameters

No.

D

D

D

Byte

78

80

88

Symbol Type

Attribute ASCII

ASCII

Word

Sg

N

N

N

Data field/comment

1Y

File.001

0

Explanation

RAM/EPROM: R

F

D

Command structure

No.

D78

D80

D88

No. of bytes Designation

2

8

1

Command type/Code

File name

Attribute

Explanation

1Y max. 8 ASCII characters

0 No attribute

1 Read-only, file data cannot be modified

2 One-time write-access following “Create”

4 File size must not be changed by commands requiring write-access.

5 As in 4h, but the file may only be read-accessed.

1070 072 135-102 (99.11) GB

5–12 BefDB – Command Area Data Module

5.8

Dir

D

D

62

64

Dir ASCII

Word

The “Dir” command writes the directory of the MDS into a selected data module.

DM 2 Name: BefDB Comment: DM contains command parameters

No.

Byte Symbol Type Sg Data field/comment Description

N

N

1G

5

RAM/EPROM: R

F

D

Command structure

No.

D62

D64

D66

No. of bytes Designation

2 Command type/Code

2 Data module number

2 DBOffset

Explanation

1G

DM to which the MDS directory is written.

Start position for directory write-access in the data module.

The directory can be written into a special DirDaten data module.

D

D

D

D

D

D

D

D

D

Directory structure in the DirDaten data module.

DM 2 Name: BefDB Comment: DM contains command parameters

No.

D

Byte

0

Symbol Type

MDS

Name

ASCII

ChkSum Word

Sg Data field/comment

N ........

N 0000

Explanation

22

24

26

34

36

8

10

12

14 freeSpce Word

Name1

Name2

Word

ASCII

Word

Word

ASCII

Word

Word

N

N

N

N

N

N

N

N

0000

........

........

RAM/EPROM: R

F

H

H

H

H

H

H

H

1070 072 135-102 (99.11) GB

Command structure

BefDB – Command Area Data Module 5–13

No.

D0

D8

D10

D14 through D24

D14

D22

D24

No. of bytes

8

2

4

8

3

1

Designation

MDS Name

ChkSum freeSpce

Explanation max. 8 ASCII characters

Internal checksum

Remaining available memory for payload data onboard MDS.

Repeated for every file in the directory.

Namex File name comprising max.

8 ASCII characters

File size in bytes

0 no attribute

1 read only

2 write once

Data word D28, DatSize, in the WorkDB data module contains the number of files stored onboard the MDS.

In the event that the DirDaten data module is configured with insufficient size, the data will be written to the end of the data module, with the remainder being lost. In the WorkDB data module, an error code is stored at address

D8, ErrCode; refer also to Chapter 9, Error Messages.

1070 072 135-102 (99.11) GB

5–14 BefDB – Command Area Data Module

5.9

Load

The “Load” command is used subsequent to the system startup to load the

MDS system area stored in the data field of the PLC into the MOBY I/F channel module.

DM 2 Name: BefDB Comment: DM contains command parameters

No.

D

D

Byte

94

96

Symbol

Load

Type

ASCII

Word

Sg

N

N

Data field/comment

1L

0

Explanation

RAM/EPROM: R

F

D

Command structure

No.

No. of bytes

D94 2

D96 2

Designation Explanation

Command type/Code 1L

Offset Offset in data field to the MDS system area

Value range: K0D through

K24532D

1070 072 135-102 (99.11) GB

BefDB – Command Area Data Module 5–15

5.10

Move

The “Move” command is used to store the system area of the current MDS in the data field of the PLC control unit. The command can be carried out, for example, if Bit 7, Sys, in data word D26, FHStatus, of the WorkDB data module indicates that the system area of the MDS has undergone a change.

DM 2 Name: BefDB Comment: DM contains command parameters

No.

D

D

Byte

90

92

Symbol Type

Move ASCII

Word

Sg

N

N

Data field/comment

1M

0

Explanation

RAM/EPROM: R

F

D

Command structure

No.

No. of bytes

D90 2

D92 2

Designation

Command type/

Code

Offset

Explanation

1M

Offset in data field under which the MDS system range is to be stored.

Value range: K0D through

K24532D

.

The administration of the data field is the responsibility of the user.

Area overlaps are not detected by the system. Only the data field limit

DF24575 is monitored.

The “MDS System Area Size” table below indicates the number of bytes that must be reserved in the data field to accommodate the system areas of the various MDS types.

1070 072 135-102 (99.11) GB

5–16 BefDB – Command Area Data Module

MDS System Area Size

MDS type

* operating with ECC

01H

02H

81H

03H

83H

04H

84H

05H

85H

06H

86H

07H

87H

08H

88H

09H

89H

0AH

8AH

0BH

8BH

Size of MDS system area (bytes)

25

41

25

63

61

443

413

923

861

1,397

1,335

2,785

2,657

4,583

4,455

5,601

5,345

11,193

10,687

15,265

14,247

1070 072 135-102 (99.11) GB

DatDB – Data Area Data Module 6–1

6 DatDB – Data Area Data Module

Data exchange for the commands

D Write

D

Read

D Dir is handled via the DatDB data module.

.

The data modules BefDB and DatDB can be combined by adjusting the program accordingly.

In the command frame for the respective command in the BefDB data module, the data module handling data traffic must always be entered with its data module number and the DBOffset value.

The following tables provide an example of the “Write” command.

DM 2 Name: BefDB Comment: DM contains command parameters

No.

D

D

D

D

D

D

Byte

18

20

28

30

32

34

Symbol Type

Write ASCII

ASCII

Word

Word

Word

Word

S

N

N

Y

N

N

N

Data field/Comment

1W

File.001

0

512

3

0

D

D

Explanation

D

D

D

D

RAM/EPROM: R

F

D

D

D

D

No.

D32

D34

No. of bytes Designation

2 Data module number

2 DBOffset

Explanation

DM which contains the data to be written.

Position in the DB marking the start of data writeaccess.

The data for the “Write”, “Read” and “Dir” commands may also be clearly divided over 3 data modules.

Data module layout table

DM No.

DM

DM

DM

Name

3 QuellDB

4 ZielDB

5 DirDaten

Comment

Source data for “ Write” command

Destination area for “ Read” command

Destination area for “ Dir” command

R/E

R

R

R

Size

512

512

512

D

A QuellDB data module, containing the data for the “Write” command.

D A ZielDB data module, into which the data of the “Read” command is written.

D

A DirDB data module, into which the “Dir” command writes the directory of the MDS.

1070 072 135-102 (99.11) GB

6–2 DatDB – Data Area Data Module

Notes:

1070 072 135-102 (99.11) GB

Sample Program

7–1

7

Sample Program

To describe the PBK5MIF software module, short extracts from a sample program have been used throughout Chapters 2 through 5. In the present chapter, this sample program is shown in full length.

This sample program is supplied as a component of the standard PBK5MIF software package; it is located on the diskette labelled: Function modules for

PBK Peripheral Bus Interface Module, Order no.: 1070 070 042.

The sample program comprises the following files:

D Module file OB1.P5O

D

Module file Anlauf.P5O

D Module file PBK5MIF.P5O

D

Symbol file Beispiel.S5S

Program requirements

The sample program will be executable without modifications only provided the following conditions are met:

D PBK start address: AZ20

D

A MOBY I/F v1.3 channel module is installed in module slot M1 (Channel 1)

D MDS is properly formatted

D

A file named File.001 is available.

The sample program was tested in conjunction with the following components:

D MOBY I/F v1.3

D SLG 1

D

MDS 505, 32k

1070 072 135-102 (99.11) GB

7–2

Sample Program

7.1

OB1.P5O

WorkDB definitions

DEF

DEF

DEF

DEF

DEF

DEF

D0,-PBKCom

D7,-Typ

D8,-CodeHigh

D10,-CodeLow

D24,-FHCom

D26,-FHStatus

The module call for the PBK5MIF must be issued cyclically, including the initial cycle (Cycle 1). It is therefore useful to program the module call instruction in OM1.

PBK5MIF parameter definitions

DEF

DEF

DEF

DEF

K1D,-Kanal1

K1D,-WorkDB1

AZ20,-PBKAdr

M0,-StatusK1

;Module slot M1 of MOBY I/F channel module

;Data module number for WorkDB1 for module slot M1

;Start address of PBK, extended I/O, byte address 20

;PBK5MIF status message for module slot M1

;PBK command, all–purpose

;Error type

;Error code Bytes 1 and 2

;Error code, Bytes 3 and 4

;Reset and Next commands

;Status message of PBK5MIF

Mask definition

DEF K0001H,-Start ;Mask for bit position 0

PBK5MIF module call instruction

CM

P0

P1

P2

-PBK5MIF,4

-Kanal1

-WorkDB1

-PBKAdr

P3 BY -StatusK1

;Module slot M1 of MOBY I/F channel module

;Data module number for WorkDB1 for module slot M1

;Start address der PBK, extended I/O, byte address 20

;PBK5MIF status message for module slot M1

Display of start parameter

L BY -StatusK1,C

Is the PBK5MIF active?

A

JPC

B M0.0

-Warten

Has an error occurred?

AN B M0.7

JPC -NoError

;Load -StatusK1 in register C

;PBK5MIF enabled bit

;Is the PBK5MIF working? -> yes

;P3 -StatusK1 Bit 7 Error

;Has an error occurred? -> no

1070 072 135-102 (99.11) GB

Sample Program

7–3

Read error type and error code from WorkDB

.

Bit 7, Error, is set for the duration of one PLC cycle only.

The information in D7, type, and D8, ErrCode, of the WorkDB must be interpreted immediately after the PBK5MIF has been called.

L

CM

L

L

L

-WorkDB1,A

[A]

BY -Typ,A

-CodeHigh,B

-CodeLow,C

;Open WorkDB1

;Error type in D7 of WorkDB

;Bytes 1 and 2 of error code

;Bytes 3 and 4 of error code

At this point, there follows the interpretation of the error message, refer also to Chapter 9, Error Messages. In addition, an application-specific response can be programmed.

EP

-NoError

Automatic Read" command initiation

.

D2 file name in DB2 of BefDB data module for the “Read” command must be adapted, refer also to table in Section 5.5 and BefDB Table in

Section 7.3.

T

L

O

T

L

CM

L

-WorkDB1,A

[A]

W -Read,A

W A,-BefOff

W -PBKCom,A

W -Start,A

W A,-PBKCom

-Warten

EP

;Open WorkDB1

;Address of command in BefDM data module

;via register A

;transfer to D4, BefOff, of WorkDB1

;Load D0 of PBKCom

;Set Bit 0 HIGH (1)

1070 072 135-102 (99.11) GB

7–4

Sample Program

7.2

Anlauf.P5O

The PBK5MIF module must also be called in the initial cycle. It is therefore useful to program the module call instruction in Anlauf.P50 as well. The trigger pulse, which is necessary for initializing the internal data areas of the

PBK5MIF, occurs only in the first cycle.

PBK5MIF parameter definitions

DEF

DEF

DEF

DEF

K1D,-Kanal1

K1D,-WorkDB1

AZ20,-PBKAdr

M0,-StatusK1

;Module slot M1 for MOBY I/F channel module

;Data module number for WorkDB1 for module slot M1

;Start address of PBK, extended I/O, byte address 20

;PBK5MIF status message for module slot M1

PBK5MIF module call instruction

CM

P0

P1

DEF

-PBK5MIF,4

-Kanal1

-WorkDB1

AZ20,-PBKAdr

P3 BY -StatusK1

EP

;Module slot M1 of MOBY I/F channel module

;Data module number for WorkDB1 for module slot M1

;Start address of PBK, extended I/O, byte address 20

;PBK5MIF status message for module slot M1

1070 072 135-102 (99.11) GB

Sample Program

7–5

7.3

Beispiel.S5S

Program modules

Type

OM

OM

Module name ;Comment

1 OB1

5 Anlauf (startup)

Organization modules

Type

PM

Module name ;Comment

0 PBK5MIF

Special markers

Address Symbol

SM 22.0

IstZykl

SM 24.0

MaxZykl

SM 26.0

MinZykl

Comment

Actual cycle time in ms

Maximum cycle time in ms

Minimum cycle time in ms

R/E

R

R

R/E

R

Type

Overview of data modules

DM No.

DM

DM

DM

DM

DM

Name

1 WorkDB1

2 BefDB

3 QuellDB

4 ZielDB

5 DirDaten

Comment

Work area for module slot M1

Command parameters

Source data for “Write” command

Destination area for “Read” command

Destination area for “Dir” command

D

D

D

D

WorkDB1

DB 1 Name: WorkDB1 Comment: Work area FB for Channel1

Symbol Type Sg Data field/Comment No.

D

D

D

D

D

D

D

D

D

Byte

6

8

12

14

18

20

0

2

4

PBKCom Word

BefDBNr Word

BefOff Word

Chk/Typ ASCII

ErrCode ASCII

Typ/Code ASCII

SLGNr

ASCII

Word

EAKO/

ECC

ASCII

ResetTyp ASCII

N

N

N

N

N

N

N

N

N

N

0

2

0

1

65535; Test number

40

C 22

24

26

28

FHCom

DatSize

Word

FHStatus Word

Word

N

N

N

0

0

0

Explanation

R/E Size

R

R

R

R

R

RAM/EPROM: R

F

B

D

D

D

B

B

D

450

98

512

512

512

1070 072 135-102 (99.11) GB

7–6

Sample Program

BefDB

DM 2Name: BefDB Comment: DM contains command parameters

Symbol Type Sg Data field/Comment No.

D

D

D

D

D

D

D

D

D

D

D

D

D

D

D

D

D

D

D

D

D

D

D

D

D

D

D

D

D

D

D

Byte

36

38

46

48

28

30

32

34

14

16

18

20

0

2

10

12

64

66

68

70

78

50

52

60

62

80

88

90

92

94

96

Read

Write

Format

Create

Dir

Delete

Attribut

Move

Load

ASCII

ASCII

Word

Word

Word

Word

ASCII

ASCII

Word

Word

Word

Word

ASCII

ASCII

Word

Word

ASCII

ASCII

Word

ASCII

Word

Word

ASCII

ASCII

ASCII

ASCII

Word

ASCII

Word

ASCII

Word

N

N

N

Y

N

N

N

N

Y

N

N

N

N

N

N

N

N

N

N

N

N

N

N

N

N

N

N

N

N

N

N

1R

File.001

0

–1

4

0

1W

File.001

0

512

3

0

1I

[BOSCH]

0006

0001

1B

File.001

0

1G

5

0

1D

File.001

1Y

File.001

0

1M

0

1L

0

Explanation

RAM/EPROM: R

F

D

D

D

D

D

D

D

D

H

H

D

D

D

D

D

D

1070 072 135-102 (99.11) GB

Sample Program

7–7

QuellDB

DM 3 Name: QuellDB Comment: Source data for “Write” command

Symbol Type Sg Data field/Comment Explanation No.

D

D

D

D

D

D

D

D

D

D

D

D

Byte

176

220

264

388

0

44

88

132

352

396

440

484

ASCII

ASCII

ASCII

ASCII

ASCII

ASCII

ASCII

ASCII

ASCII

ASCII

ASCII

ASCII

N

N

N

N

N

N

N

N

N

N

N

N

Descriptive Text

Descriptive Text

Descriptive Text

Descriptive Text

Descriptive Text

Descriptive Text

Descriptive Text

Descriptive Text

Descriptive Text

Descriptive Text

Descriptive Text

Descriptive Text

ZielDB

DB 4 Name: ZielDB Comment: Destination area for “Read” command

No.

D

D

D

D

D

D

D

D

D

D

D

D

Byte

0

44

88

132

176

220

264

308

352

396

440

484

Symbol Type

ASCII

ASCII

ASCII

ASCII

ASCII

ASCII

ASCII

ASCII

ASCII

ASCII

ASCII

ASCII

Sg Data field/Comment

N ........................................

N

N

N

N

N

N

N

N

N

N

N

........................................

........................................

........................................

........................................

........................................

........................................

........................................

........................................

........................................

........................................

...........................

Explanation

RAM/EPROM: R

F

RAM/EPROM: R

F

1070 072 135-102 (99.11) GB

7–8

Sample Program

D

D

D

D

D

D

D

D

D

D

D

D

D

D

D

D

D

D

D

DirDaten

DB 5 Name: DirDaten Comment: Destination area for “Dir” command

Symbol Type Sg Data field/Comment Explanation No.

D

Byte

0

MDS

Name

ASCII

ChkSum Word

N

N

........

0000

8

10

12

14

22

24

26

34

36

38

482

490

492

494

502

504

506 freeSpce Word

Name1

Name2

Name3

.

.

Word

ASCII

Word

Word

ASCII

Word

Word

ASCII

Name40 ASCII

Word

Word

Name41 ASCII

Word

Word

Name42 ASCII

.

.

N

N

N

N

N

N

N

N

N

N

N

N

N

N

N

N

.

.

0000

........

........

........

........

........

........

RAM/EPROM: R

F

H

H

H

H

H

H

H

H

H

.

.

H

H

1070 072 135-102 (99.11) GB

8

EAKO - Approach/Departure Monitoring

8–1

EAKO - Approach/Departure Monitoring

The term “EAKO approach/departure monitoring” describes a procedure that makes it possible to determine whether an MDS is positioned within the transmission range of an SLG. The user is provided with a choice of three different methods.

EAKO Explanation

0 D MDS recognition via range scanning.

D Command is stored by the Filehandler until an authorized MDS enters the SLG transmission range or leaves that range during command execution.

1

D

The “Next” command is mandatory.

D

Contiguous MDS flow control via the Filehandler.

D MDS recognition occurs in the PLC program, e.g., via position switch.

4

D

Command execution is immediate.

D

The “Next” command is optional but not mandatory.

D No contiguous MDS flow control.

D MDS recognition occurs in the PLC program, e.g., via position switch.

D Command is stored by the Filehandler until an authorized MDS enters the SLG transmission range or leaves that range during command execution.

D The “Next” command is optional but not mandatory.

D No contiguous MDS flow control.

The procedure is selected in data word D20, EAKO, of the WorkDB data module. The data type is ASCII.

1070 072 135-102 (99.11) GB

8–2

EAKO - Approach/Departure Monitoring

8.1

Definition of Terms

Before embarking on the following description of the 3 procedures, a few terms related to approach/departure monitoring shall be defined

.

Prerequisite: All SLG (read/write unit) stations feature different SLG numbers.

SLG number

Each SLG features a uniuqe SLG number. If work is being performed by an

MDS on a given SLG, the SLG number of the SLG will be written into the

MDS system area. The SLG number is written automatically before the first command is executed with the MDS. Therefore the SLG number reveals whether a new or old MDS is currently positioned within the SLG transmission range.

new MDS

The SLG number of the SLG and the SLG number on the MDS do not match.

old MDS

The SLG number of the SLG and the SLG number on the MDS are identical.

current MDS

All commands currently being executed refer to this MDS.

Example of an operational sequence on an SLG

D

The old MDS remains current – with all commands referring to this MDS – until it is concluded by a “ Next” command.

D

The PLC program sets the “ Next” command, i.e.,Bit 1 in D24, FHCom, of the WorkDB data module. All subsequent commands will refer to the next new MDS.

D If the next MDS to enter the SLG transmission range is again the old

MDS, this will be recognized by the unchanged SLG number. No command will be executed.

D If a new MDS enters the SLG transmission range and its SLG number is different, the stations’s local SLG number will be written into the system area of the MDS. This turns the new MDS into the current MDS.

1070 072 135-102 (99.11) GB

8.2

EAKO 0

EAKO - Approach/Departure Monitoring

8–3

Subsequent to receiving a command, the PBK5MIF continuously attempts to establish communications with the MDS via the connected SLG. As soon as an MDS appears within SLG transmission range, command processing commences. With this procedure, the PLC program can initiate a command at any ppoint in time. The command will be stored until it can be processed with, or by, an MDS.

In this operating mode, the “ Next” command has a decisive function. Starting the “ Next” command signifies the following:

D Processing of the old/current MDS has concluded.

D

A new command can be initiated immediately following the “ Next” command. However, this command will be processed only once a new MDS has arrived.

If the old MDS reenters the SLG transmission range, the new command will not be executed.

Initiation of the “ Next” command is always permitted.

This operating mode provides a contiguous MDS flow control.

In the event that a new MDS enters the SLG transmission range before the old/current MDS was concluded with the “ Next” command, the procedural sequence will be as follows:

D

If a command other than “ Next” is initiated, an error message will be returned.

D If the “ Next” command is initiated, the old MDS will be concluded, and the new MDS will become the current MDS. All subsequent commands will be executed with this current MDS until processing is terminated with another “ Next” command.

D

If the current MDS again exits the SLG transmission range without having processed a command, an error condition will result. The error message is returned only once a command has been initiated.

1070 072 135-102 (99.11) GB

8–4

EAKO - Approach/Departure Monitoring

8.3

EAKO 1

In this operating mode, the PLC program a part of the MDS flow control.

When a command is initiated, the PLC program must ensure that an MDS is positioned within the SLG transmission range. The command is executed immediately. If there is no MDS in the SLG transmission range, an error message will be returned.

This operating mode can be utilized in all situations where the PLC program is able to detect the precence of an MDS, e.g., by means of position switches.

The “ Next” command can be used but is not mandatory.

8.4

EAKO 4

This operating mode does not provide any means of manipulating the MDS flow control with the PBK5MIF software module. The entire MDS flow control must be handled by the PLC program, e.g., with the use of position switches.

A command will be stored until an MDS enters the SLG transmission range.

The “ Next” command can be used but is not mandatory.

1070 072 135-102 (99.11) GB

Error Messages

9–1

9

Error Messages

The PBK5MIF enters error messages in D7, Typ, and D8, ErrCode, of the

WorkDB data module. The messages will be valid only if Bit 7 in parameter

P3, Status, of the PBK5MIF is HIGH.

A distinction is made between two types of errors:

D Typ 0 Error messages originating in PBK5MIF or PBK.

D

Typ 1 Error messages generated by the MOBY I/F.

Some Type 1 error messages are also indicated by the red Error LED on the front panel of the MOBY I/F channel module. Here, the error type is determined by the number of flashing pulses separated by an intervening pause.

.

In the standard operating mode, a flashing error indicator may be safely ignored, provided that the system continues to operate correctly.

Flashing pulses/ErrCode

11

12

13

14

15

8

9

10

5

6

7

Flashing pulses

3

4

1

2

1

1

1

1

1

1

Type

1

1

1

1

1

1

1

1

1

ErrCode

D001

C006

B001

C002

C007

C008

C009

C010

C011

C012

C013

C014

C015

C016

C017

1070 072 135-102 (99.11) GB

9–2

Error Messages

9.1

Error type 0

Error messages originating in PBK5MIF or PBK.

9.1.1

P PBK5MIF parameter error

P001

The PBK cannot be contacted at the address defined in parameter P2

PBKAdr.

Check the settings of the S1 DIP and positions of jumpers JP1/JP2 on the

PBK, refer to Section 3.2, Module Calls and Parameters.

P002

The BefDB data module specified in the WorkDB data module via data words D2, BefDBNr, BefDBNr and D4, BefOff, has not been programmed, or has been programmed with excessive size.

P003

Unknown command type in BefDB data module.

P004

Unknown command code in BefDB data module.

P005

Either the data module number specified in the BefDB data module for a

“Write”, “Read”, or “Dir” command, or the DBOffset has not been programmed, or has been programmed with excessive size.

P007

A value other than 1 or 0 was found in WorkDB data module, data word

D6, Chk.

1070 072 135-102 (99.11) GB

Error Messages

9–3

9.1.2

D Request-specific errors

D001

MOBY I/F transmits a message with an unknown error code.

D002

The received part block does not correspond to the requested part block.

D003

The full data complement received with the “Read” command does not fit into the specified destination data module. The data is being written up to the end of the data module; the remaining data will be lost.

Increase the size of the data module.

D004

Due to a preceding error occurrence, Type 1 MOBY I/F are no longer processed. The only command being processed is the “Reset” command in Bit 0 of data word D24 FHCom in the WorkDB data module.

Initiate “Reset” command.

D005

The MDS system area requested with the “Move” command does not fit into the data field area intended for the subject system area.

Check the Offset for the “Move” command in the BefDB data module.

1070 072 135-102 (99.11) GB

9–4

Error Messages

9.1.3

> System Errors reported by the PBK hardware module

>001

Checkbyte D6 Chk in WorkDB data module is enabled, and an error was detected.

The error may have been caused by unauthorized instances of read/write access to the PBK start address.

>002

MOBY I/F is not connected or is defective.

>003 internal error

>004 internal error

>005 internal error

>006 internal error

>007

Parameter error in BefDB data module.

9.1.4

> System Error reproted by PBK5MIF FB

Fxxxx

A fatal system fault has occurred.

Example: Application program has overwritten internal FB data areas.

Both PBK and FB are completely reinitialized. Active requests that may still be present will be lost.

1070 072 135-102 (99.11) GB

Error Messages

9–5

9.2

Error Type 1

MOBY I/F error messages

9.2.1

A Protocol Errors

A006

Unknown error

A011

The message control parameters are not being received in the correct order.

A015

Checkbyte D6, Chk, in WorkDB data module is HIGH. The check byte generated by the PBK5MIF does not match the command message.

A016

MOBY I/F currently occupied by the STG 4F Service and Testing unit. Command processing will be delayed until the STG 4F has completed its task.

If necessary, reinitiate the command.

1070 072 135-102 (99.11) GB

9–6

Error Messages

9.2.2

B SLG Errors

B001

B002

Flashing red Error LED on MOBY I/F: 3 flashing pulses.

Errors in the connection to the SLG.

D

Check the cable between MOBY I/F and SLG.

D Missing 24 V power supply.

D

Defective MOBY I/F or SLG.

D EAKO : 1

A command was initiated but there is no MDS within the SLG transmission range.

D EAKO : 0

D

The old/current MDS has exited the transmission range, and the next/ new MDS has entered the SLG transmission range. The old/current

MDS was not concluded with the “Next” command.

D

A new MDS has entered the SLG transmission range and is exiting again without a command having been processed with the MDS.

9.2.3

C MDS Errors

C002

C006

Flashing red Error LED on MOBY I/F: 4 flashing pulses.

The MDS reports a memory error. The MDS was never write-accessed or has lost its memory contents due to a battery failure; not applicable to

EEPROM-equipped MDS.

D Replace MDS if Bit 1, battery monitor, Bat in D26 of FHStatus in the

WorkDB data module, has gone HIGH.

D Initialize MDS with the STG 4F

D

Format MDS with “Format” command.

Flashing red Error LED on MOBY I/F: 2 flashing pulses.

The MDS has exited the SLG transmission range during an ongoing command execution.

D

Reinitiate the command.

D MDS is positioned in the border area of the SLG transmission range.

1070 072 135-102 (99.11) GB

C007

C008

C009

C010

1070 072 135-102 (99.11) GB

Error Messages

9–7

Flashing red Error LED on MOBY I/F: 5 flashing pulses.

D The “Format” command was started with an incorrect parameter. The memory capacity onboard the MDS falls short of the specification given in the command.

D The “Read” or “Write” commands point to an address that does not exist on the MDS.

Flashing red Error LED on MOBY I/F: 6 flashing pulses.

SLG receives interference pulses from its environment.

D External noise field, the noise field can be detected by means of the inductive field indicator of the STG 4F.

D

The distance between two SLGs is too small and fails to conform to the project guidelines.

D The connecting cable between MOBY I/F and SLG is faulty, too long or fails to conform to the project guidelines.

.

For configuration guidelines, refer to the catalog published by

Siemens AG:

MOBY

Identsystem MOBY-I (MOBY-I Identification System)

E86060-K6910-A101-A2

Flashing red Error LED on MOBY I/F: 7 flashing pulses.

Too many transmission errors have occurred. After several attempts, MDS was unable to receive the complete command or data from the MOBY I/F.

D MDS is positioned in the border area of the SLG transmission range.

D

Transmission to the MDS is affected by the external noise field.

Flashing red Error LED on MOBY I/F: 8 flashing pulses.

The file handler has detected an error during data transmission.

D External noise field, the noise field can be detected by means of the inductive field indicator of the STG 4F.

D

The distance between two SLGs is too small and fails to conform to the project guidelines.

D

The connecting cable between MOBY I/F and SLG is defective, too long or fails to conform to the project guidelines.

.

For configuration guidelines, refer to the catalog published by

Siemens AG:

MOBY

Identsystem MOBY-I (MOBY-I Identification System)

E86060-K6910-A101-A2

9–8

Error Messages

C011

C012

C013

C014

C015

C016

C017

Flashing red Error LED on MOBY I/F: 9 flashing pulses.

refer to C008

Flashing red Error LED on MOBY I/F: 10 flashing pulses.

MDS is unable to execute the “Format” command. MDS is defective.

Flashing red Error LED on MOBY I/F: 11 flashing pulses.

Error with “Format” command.

D MDS is positioned in the border area of the SLG transmission range.

D

MDS is using too much electricity. MDS is defective.

Flashing red Error LED on MOBY I/F: 12 flashing pulses.

MDS cannot be write-accessed.

D The memory capacity onboard the MDS falls short of the specification given in the “Format” command. MDS of appropriate type must be newly formatted.

D MDS is defective.

D

EEPROM of the MDS has reached the end of its service life.

Flashing red Error LED on MOBY I/F: 13 flashing pulses.

MDS address range is being exceeded.

Wrong MDS type.

Flashing red Error LED on MOBY I/F: 14 flashing pulses.

An ECC error has occurred. Data on the MDS cannot be read-accessed.

D MDS data is lost, the MDS is defective.

D

MDS was not formatted with the use of the ECC driver. MDS must be reformatted.

D EEPROM onboard MDS has reached the end of its useful service life. Replace MDS.

Flashing red Error LED on MOBY I/F: 15 flashing pulses.

Filehandler is not functioning correctly.

D Check command structure or command sequence.

D

Defective MOBY I/F hardware or firmware.

1070 072 135-102 (99.11) GB

Error Messages

9–9

9.2.4

D Request-specific errors

D001

Flashing red Error LED on MOBY I/F: 1 flashing pulse.

Filehandler has not yet been initialized by means of the “Reset” command.

This condition can be terminated only through the use of the “Reset” command.

D005

D007

The “Format”, “Create”, or “Write” were transmitted with inappropriate parameter values.

D “Format” command with invalid MDS name or MDS type.

D

“Create” command with invalid file name.

D “Write” command with file size “0” (zero) 0.

The MDS system area stored in the data field is faulty.

D A valid system area has not yet been written into the datab field (“Move” command).

D The segregation of the data field is faulty, e.g., area overlap.

D

The data field is being overwritten due to a PLC program error, e.g., indirect addressing.

D009

D014

Invalid parameters (or parameter values) in “Reset” command.

Error originates in PLC program. Check PBK5MIF parameters.

D “Write” command, MDS memory is full. Therefore, only truncated data is written to the MDS.

D

“Create” command, file cannot be created onboard the MDS due to insufficient number of free blocks.

D015

The filehandler was unable to identify the MDS.

Reformat the MDS.

D018

The selected address is outside the file.

Reformat MDS.

D022

The data memory was closed with the use of the “Cover” command. A command requiring write-access (e.g., “Create” and “Format”) may not be permitted to destroy the data field, and is therefore rejected.

1070 072 135-102 (99.11) GB

9–10

Error Messages

D023

“Cover” command: The MDS name specified in the command fails to match the actual MDS name.

9.2.5

E Directory-related errors

E001

D

The MDS type which is present within the SLG transmission range does not match the selected ECC driver.

Reformat the MDS using the ECC driver.

D

MDS is not an MDS filehandler.

Reformat MDS.

E002

Free directory entry no longer available onboard this MDS. The file specified in the “Create” command cannot be created.

E003

The file name specified in the “Create” command is already in use.

E005

An error has occurred during “Read” or “Write” command execution.

Reformat MDS.

9.2.6

F File-specific errors

F001

F005

D The accessed file does not exist.

Generate the file with the use of the “Create” command.

D

The file name in the in the BefDB data module may possibly not be written in ASCII notation.

Attempted write-access by means of “Write” command to a file which is write-protected.

F007

QUEUE-READ: Specified file size smaller than actual file size.

1070 072 135-102 (99.11) GB

F008

Error Messages

9–11

QUEUE-READ: The skip calculated by the Filehandler is greater than

0FFF Hex.

1070 072 135-102 (99.11) GB

9–12

Error Messages

Notes:

1070 072 135-102 (99.11) GB

Characteristic Data

10–1

10

Characteristic Data

Characteristic Data

Module name

Module length

Parameters

Processing time

Assigned markers

Call

PBK5MIF

PBK5MIF

5345 words

4

154 m s, no-load

M230 to M255 cyclic, incl. 1st cycle

Cycle loading through PBK5MIF n = The number of user data per cycle to be processed. A maximum of

240 bytes can be read or 226 bytes written in one cycle. Larger files are distributed over several cycles.

Idle run

Read file

Write file

154 m s

(370 + n 5.7) m s

(370 + n 7.0) m s

.

The times specified for reading/writing files are valid only if the program is run without a checksum. If the program is run with a checksum, the cycle time for reading files is extended by the factor 1.3, and for writing files by the factor 1.5.

1070 072 135-102 (99.11) GB

10–2

Characteristic Data

Notes:

1070 072 135-102 (99.11) GB

A Appendix

A.1

Abbreviations

EI

EO

I

FAT

II

IO

MDS

O

PBK

PBK5MIF

Abbreviation Meaning

BefDB Command Area data module

DatDB

DM

DOS

Data Area data module

Data module

Disk Operating System

SLG

STG 4F

ZS

Extended input

Extended output

File Allocation Table

Input

Interface input

Interface output

Mobile Data Storage unit

Output

Peripheral Bus Interface Module

CL500 function module for the PBK module and the MOBY I/F channel module

Read/write unit

Service and Testing unit

Central processing unit of controller

Appendix A–1

1070 072 135-102 (99.11) GB

A–2 Appendix

A.2

Amendments

In this revised edition 102, amendments have been made to the former edition 101 on the following pages.

Chapter

3

4

5

9

5–6

5–7

5–11

9–4

9–9

4–4

4–3

4–6

4–7

Page

3–1

3–2

4–1

5–2

5–5

9–10

9–10

Change

Section 3.1

P1 WorkDBNr

Table was augmented.

Table was augmented.

Description of ’SatzNr’ variable was added.

Description of ’ABTA’ variable was added.

D26 FHStatus

Table was augmented.

Attribute

Command structure

Description of “Cover” command was added.

Command structure

Sections 9.1.3 and 9.1.4

Description of request-specific error messages were augmented by adding “D007” and “D022”.

Description of request-specific error messages was augmented by adding “D023”.

Description of file-specific error messages was augmented by adding “F007” and

“F008”.

1070 072 135-102 (99.11) GB

Appendix A–3

A.3

Index

Characters

> System error

– reported by PBK, 9–4

– reported by PBK5MIF, 9–4

Numbers

1B, 5–6, 7–6

1D, 5–10, 7–6

1G, 5–12, 7–6

1I, 5–4

1L, 5–14, 7–6

1M, 5–15, 7–6

1R, 5–9

1W, 5–8, 6–1

1Y, 5–11, 7–6

24 V power supply, 9–6

A

A Protocol Errors, 9–5

ABTA, 4–4, 4–6

Acknowledgement message, 2–7

Active, 3–4

Actual cycle time, 7–5

Address range, 3–3

Amendment, 1–6

Anlauf.P5O, 7–1, 7–4, 7–5

Anw, 4–7

Approach/departure monitoring, 4–5, 8–1

Attribut, 7–6

Attribute, 5–2, 5–7, 5–11, 5–13

– command structure, 5–11

B

B SLG Errors, 9–6

Bat, 4–7, 9–6

Battery failure, 9–6

Battery monitor, 4–7, 9–6

BefDB, 3–5, 4–2, 5–1, 5–3, 6–1, 9–2, 9–3, 9–4, 9–10

BefDBNr, 4–2, 5–1, 5–3, 7–5, 9–2

BefOff, 4–2, 5–1, 5–3, 7–3, 7–5, 9–2

Beispiel.S5S, 7–1, 7–5

Bit 7, 4–3

Block, 2–5

C

C MDS error, 9–6

Call, 10–1

Channel module

– MOBY I/F. See MOBY I/F

– module slot, 7–2, 7–4

Channel number, 3–2

Characteristic data, 10–1

Checkbyte, 9–4, 9–5

Checksum, 2–5, 2–6, 4–7, 5–13, 10–1

Checksum mechanism, 5–5

Chk, 4–2, 4–3, 7–5, 9–2, 9–4, 9–5

ChkSum, 5–12, 5–13, 7–8

CodeHigh, 7–2, 7–3

1070 072 135-102 (99.11) GB

CodeLow, 7–2, 7–3

Command, 2–3, 5–2, 8–3

– automatic initiation, 7–3

Command acknowledgement, 2–7

Command area, 3–5

Command code, 4–3, 5–2, 5–4, 5–6, 5–7, 5–8, 5–9, 5–10,

5–11, 5–12, 5–14, 5–15, 9–2

Command execution, 9–6

Command frame, 6–1

Command message, 2–7, 9–5

Command parameters, 3–5, 7–5

Command sequence, 9–8

Command structure, 9–8

Command typ, 4–3

Command type, 5–2, 5–4, 5–6, 5–7, 5–8, 5–9, 5–10, 5–11,

5–12, 5–14, 5–15, 9–2

Configuration guidelines, 9–7

Connecting cable, 9–7

Control byte, 4–3

Cover, 5–2, 5–7

Create, 5–2, 5–6, 5–8, 7–6, 9–9, 9–10

– attribute, 5–6, 5–11

– command structure, 5–6

Current MDS, 8–2

Cycle, – 1., 7–2, 7–4

Cycle load, 10–1

Cycle time, 4–3, 7–5, 10–1

D

D Request-specific errors, 9–3, 9–9

D0, 4–2

D12, 4–3

D14, 4–3

D18, 4–4

D2, 4–2, 9–2

D20, 4–5, 8–1

D21, 4–5

D22, 4–5

D23, 4–6

D24, 4–6, 9–3

D26, 4–7, 5–15, 9–6

D28, 4–8, 5–13

D4, 4–2, 9–2

D6, 4–3, 9–2, 9–4, 9–5

D7, 3–4, 4–3, 9–1

D8, 3–4, 4–3, 5–13, 9–1

Data, 2–3

– module number, 6–1

Data area, 3–5

Data channel, 2–7

Data field, 2–5, 5–14, 5–15, 9–9

Data field area, 9–3

Data module, 5–8, 9–3

Data module number, 3–2, 5–8, 5–9, 5–12, 6–1, 7–2, 7–4,

9–2

Data module size, 4–1, 9–3

Data security, 4–5

A–4 Appendix

Data storage, 2–2

See also MDS

Data traffic, 6–1

Data transmission, 4–3

Data word, 4–2

DatDB, 3–5

DatSize, 4–4, 4–8, 5–13, 7–5

DBOffset, 5–8, 5–9, 5–12, 6–1, 9–2

Delete, 5–2, 5–10, 7–6

– command structure, 5–10

Destination area, 7–5

Destination data module, 9–3

DIR, 4–5

Dir, 3–5, 3–6, 4–8, 5–2, 5–12, 6–1, 7–5, 7–6, 9–2

– command structure, 5–12

DirDaten, 3–5, 5–12

DirDB, 3–6, 6–1

Directory, 2–5, 5–2, 5–5, 5–6, 5–12

Directory entry, 9–10

Directory-related errors, 9–10

Documentation, 1–6

DOS operating system, 2–4

E

E Directory-related errors, 9–10

EAKO, 4–4, 4–5, 7–5, 8–1

– 0, 8–3, 9–6

– 1, 8–4, 9–6

– 4, 8–4

ECC, 4–4, 4–5, 4–7, 5–5, 5–16

– driver, 4–5, 9–8, 9–10

– error, 9–8

– operation, 5–5

EI, 3–3

EI/EO field, 3–3

End of the file, 4–7

EO, 3–3

ErrCode, 3–4, 4–2, 4–3, 5–13, 7–3, 7–5, 9–1

Error, 3–4

– >002, 9–4

– >003, 9–4

– >004, 9–4

– >005, 9–4

– >006, 9–4

– >007, 9–4

– 001, 9–4

– A006, 9–5

– A011, 9–5

– A015, 9–5

– A016, 9–5

– B001, 9–6

– B002, 9–6

– C002, 9–6

– C006, 9–6

– C007, 9–7

– C008, 9–7

– C009, 9–7

– C010, 9–7

– C011, 9–8

– C012, 9–8

– C013, 9–8

– C014, 9–8

– C015, 9–8

– C016, 9–8

– C017, 9–8

– D001, 9–3, 9–9

– D002, 9–3

– D003, 9–3

– D004, 9–3

– D005, 9–3, 9–9

– D007, 9–9

– D009, 9–9

– D014, 9–9

– D015, 9–9

– D018, 9–9

– D022, 9–9

– D023, 9–10

– E001, 9–10

– E002, 9–10

– E003, 9–10

– E005, 9–10

– F001, 9–10

– F005, 9–10

– F007, 9–10

– F008, 9–11

– Fxxxx, 9–4

– P001, 9–2

– P002, 9–2

– P003, 9–2

– P004, 9–2

– P005, 9–2

– P007, 9–2

Error code, 4–3, 5–13, 7–2, 7–3, 9–3

Error Correcting Code, 4–5

Error correction, 4–7

Error display, 9–1

Error indication, 9–6, 9–7, 9–8, 9–9

Error message, 9–1

Error type, 4–3, 7–2, 7–3, 9–1

– 0, 9–2

– 1, 9–5

Errors, 7–2

F

F File-specific errors, 9–10

FAT, 2–5, 4–5

FHCom, 4–4, 4–6, 5–1, 7–2, 7–5, 9–3

FHStatus, 4–4, 4–7, 5–15, 7–2, 7–5, 9–6

Field indicator, 9–7

File, 2–5, 5–6, 5–8, 9–10

– read, 10–1

– write, 10–1

File Allocation Table, 2–5

File management, 2–4

File management system, 2–2

File name, 2–4, 5–6, 5–7, 5–8, 5–9, 5–10, 5–13, 9–9, 9–10

File size, 4–8, 5–6, 5–13, 9–9

File.001, 7–1

File-specific errors, 9–10

Filehandler, 2–2, 2–4, 2–7, 4–4, 8–1, 9–8, 9–9, 9–10

Flashing pulse, 9–1, 9–6, 9–7, 9–8, 9–9

1070 072 135-102 (99.11) GB

Appendix A–5

Format, 5–2, 5–4, 7–6, 9–6, 9–7, 9–8, 9–9

– attribute, 5–4, 5–5

– command structure, 5–4 freeSpce, 5–12, 5–13, 7–8

H

Hard Reset, 4–5

I

I/O field, 3–3

Idle run, 10–1

II, 3–3

Initiating a parameterized command, 5–3

Input byte, 3–3

Input parameters, 3–2

Interference pulse, 9–7

IO, 3–3

J

JP1, 3–3

JP2, 3–3

K

Kanal1, 7–2, 7–4

KanalNr, 3–2

L

Load, 2–5, 5–2, 5–14, 7–6

– command structure, 5–14

M

Manufacturing sequence, 2–8

Markers, – assigned, 10–1

MDS, 2–1, 2–3, 2–4, 2–8, 4–2, 4–4, 4–5, 4–6, 4–7, 5–2,

5–4, 5–5, 5–6, 5–8, 5–9, 5–10, 5–12, 5–13, 8–1, 8–2,

8–3, 9–6, 9–7, 9–8, 9–9, 9–10

– address, 9–7

– address range, 9–8

– auxiliary battery, 4–7

– battery, 4–7

– capacity, 5–5

– current, 8–2, 8–3, 9–6

– directory, 3–6

– EEPROM, 9–8

– error, 9–6

– flow control, 8–1, 8–3, 8–4

– memory, 9–9

– memory capacity, 9–7

– memory error, 9–6

– name, 2–5, 5–4, 5–12, 5–13, 7–8, 9–9

– new, 8–2, 8–3

– old, 8–2, 8–3, 9–6

– storage, 2–5

– system area, 2–5, 5–14, 5–15, 5–16, 8–2, 9–3

– type, 2–5, 5–4, 5–5, 5–15, 5–16, 9–8, 9–9

Memory error, 9–6

Mobile Data Storage. See MDS

Mobile data storage, 2–2

MOBY I/F, 2–1, 2–2, 2–4, 3–2, 3–5, 4–3, 5–14, 9–1, 9–3,

9–4, 9–5, 9–6, 9–7, 9–8, 9–9

– parameters, 4–1, 4–4

MOBY(R)-I, 2–1

Modul, 4–3

Module call, 3–2

Module call instruction, 7–4

Module length, 10–1

Module name, 10–1

Module slot, 7–2, 7–4

Module type, 4–3

Move, 2–5, 5–2, 5–15, 7–6, 9–3

– command structure, 5–15

N

Namex, 5–12, 5–13, 7–8

New MDS, 8–2

Next, 4–4, 4–5, 4–6, 5–1, 7–2, 8–1, 8–3, 8–4, 9–6

No. of bytes, 5–4, 5–6, 5–7, 5–8, 5–9, 5–10, 5–11, 5–12,

5–13, 5–14, 5–15, 6–1

Noise field, 9–7

O

OB1.P5O, 7–1, 7–2, 7–5

Offset, 4–2, 5–8, 5–9, 5–14, 5–15, 9–3

Old MDS, 8–2

Operand identifier, 3–3

Operational sequence on an SLG, 8–2

Output byte, 3–3

Output parameter, 3–2

P

P PBK5MIF parameter error, 9–2

Parameter, 2–3, 5–1, 10–1

– P0, 3–2

– P1, 3–2, 3–4, 5–3

– P2, 3–3, 9–2

– P3, 3–4, 4–3, 9–1

Parameter error, 9–4

Parameters, 3–2

Payload data, 4–8, 5–5, 5–8, 5–9, 5–13

PBCom, 5–3

PBK, 2–1, 2–4, 2–7, 3–2, 3–3, 4–3, 4–7, 9–1, 9–2

– parameters, 4–1, 4–2

– start address, 3–3, 7–1, 9–4

PBK5MIF, 2–2

– active?, 7–2

– data structure, 3–5

– functions, 2–3

– module call instruction, 7–2, 7–4

– parameter error, 9–2

– parameters, 7–2, 7–4, 9–9

– status, 3–4

– status message, 7–2

PBKAdr, 3–2, 3–3, 7–2, 7–4, 9–2

PBKCom, 4–2, 5–1, 7–2, 7–3, 7–5

PBKMIF.P5O, 7–1

Peripheral bus, 2–1

Interface module. See PBK

PLC

– program, 8–4

– sample program, 7–1

Position switch, 8–1

Presence, 4–7

1070 072 135-102 (99.11) GB

A–6 Appendix

Processing time, 10–1

Program requirements, 7–1

Project guidelines, 9–7

Protocol errors, 9–5

Q

Qualified personnel, 1–1

QuellDB, 3–5, 3–6, 6–1

R

Read, 3–5, 3–6, 4–7, 4–8, 5–2, 5–9, 6–1, 7–3, 7–5, 7–6,

9–2, 9–3, 9–7, 9–10

– command structure, 5–9

Read attribute, 5–11

Read/write unit, 2–2

Ready bit, 2–7

Request-specific errors, 9–3

Reset, 4–6, 5–1, 7–2, 9–3, 9–9

ResetTyp, 4–4, 4–5, 7–5

S

S1, 3–3

Safety instructions, 1–4

Sample program, 7–1

Service and Testing Unit. See STG 4F

Size, 5–8, 5–9

Size of user data, 2–7

SLG, 2–1, 2–3, 2–4, 4–7, 8–1, 8–2, 8–3, 9–6, 9–7

– error, 9–6

– number, 2–5, 4–4, 8–2

– transmission range, 4–6, 4–7, 8–1, 8–2, 8–3, 8–4,

9–10

SLG Read/write unit. See SLG

SLGNr, 4–4, 7–5

Slot, 7–1

– M1, 7–5

Soft Reset, 4–5

Source data, 7–5

Standard operation, 1–1

Start, 7–2, 7–3

Start address, 3–3, 7–2, 7–4, 9–4

Start parameter, 7–2

Start position, 5–8, 5–9, 5–12

Start signal, 4–2, 5–1, 5–3

Status, 3–2, 3–4, 4–3, 9–1

Status bit, 2–7

Status message, 7–2

StatusK1, 7–2, 7–4

STG 4F, 2–1, 4–7, 9–5, 9–6, 9–7

STG enabled, 4–7

Sys, 4–7, 5–15

System area, 5–2, 5–5

System startup, 5–14

T

Time factor, 4–6

Time value, 4–6

Trademark, 1–6

Transmission error, 9–7

Transmission range, 9–6, 9–8

Trigger pulse, 7–4

Typ, 4–2, 4–3, 7–2, 7–3, 9–1

Typ/Code, 4–2, 4–3, 7–5

Type, 3–4

W

War1, 4–7

War2, 4–7

Work area, 3–5

WorkDB, 3–2, 3–4, 3–5, 5–1, 5–3, 5–9, 5–13, 5–15, 7–3,

8–1, 9–1, 9–2, 9–3, 9–4, 9–5, 9–6

– definitions, 7–2

WorkDB1, 7–2, 7–4

WorkDBNr, 3–2, 5–3

Working area, 3–5, 4–1

Write, 3–5, 3–6, 5–2, 5–8, 6–1, 7–5, 7–6, 9–2, 9–7, 9–9,

9–10

– command structure, 5–7, 5–8

Write attribute, 5–11

Z

ZielDB, 3–5, 3–6, 6–1

ZS, 4–3

1070 072 135-102 (99.11) GB

Bosch Automation Technology

Australia

Robert Bosch (Australia) Pty. Ltd.

Head Office

Cnr. Centre - McNaughton Roads

P.O. Box 66

AUS-3168 Clayton, Victoria

Fax (03) 95 41 77 03

Great Britain

Robert Bosch Limited

Automation Technology Division

Meridian South Meridian Business Park

GB-LE3 2WY Braunstone

Leicestershire

Fax (01 16) 28-9 28 78

Canada

Robert Bosch Corporation

Automation Technology Division

6811 Century Avenue

CAN-Mississauga, Ontario L5N 1R1

Fax (905) 5 42-42 81

USA

Robert Bosch Corporation

Automation Technology Division

Fluid Power Products

7505 Durand Avenue

USA-Racine, Wisconsin 53406

Fax (414) 5 54-81 03

Robert Bosch Corporation

Automation Technology Division

Factory Automation Products

816 East Third Street

USA-Buchanan, MI 49107

Fax (616) 6 95-53 63

Robert Bosch Corporation

Automation Technology Division

Industrial Electronic Products

40 Darling Drive

USA-Avon, CT 0 60 01-42 17

Fax (860) 4 09-70 80

We reserve the right to make technical alterations

Your concessionary

1070 072 135-102 (99.11) GB

· HB SP· AT/PLS · Printed in Germany

Robert Bosch GmbH

Geschäftsbereich

Automationstechnik

Antriebs- und Steuerungstechnik

Postfach 11 62

D-64701 Erbach

Fax +49 (0) 60 62 78-4 28