VPC3+C User Manual Revision 1.04

VPC3+C

User Manual

Revision 1.04

Th e Cl e ve r Al t e r n a t i ve

Liability Exclusion

We have tested the contents of this document regarding agreement with the hardware and software described.

Nevertheless, there may be deviations and we do not guarantee complete agreement. The data in the document is tested periodically, however. Required corrections are included in subsequent versions. We gratefully accept suggestions for improvements.

Copyright

Copyright © profichip GmbH 2004-2007.

All Rights Reserved.

Unless permission has been expressly granted, passing on this document or copying it, or using and sharing its content are not allowed. Offenders will be held liable. All rights reserved, in the event a patent is granted or a utility model or design is registered.

This document is subject to technical changes.

Copyright © profichip GmbH, 2004-2007

Table of Contents

1

Introduction .................................................................5

2

Functional Description ...............................................7

2.1

Overview ......................................................................................7

3

Pin Description............................................................9

3.1

Pin Assignment ............................................................................9

3.2

Pinout .........................................................................................11

4

Memory Organization ...............................................13

4.1

Overview ....................................................................................13

4.2

Control Parameters (Latches/Registers) ....................................15

4.3

Organizational Parameters (RAM) .............................................17

5

ASIC Interface............................................................19

5.1

Mode Registers ..........................................................................19

5.1.1

Mode Register 0 .............................................................19

5.1.2

Mode Register 1 .............................................................21

5.1.3

Mode Register 2 .............................................................23

5.2

Status Register...........................................................................25

5.3

Interrupt Controller .....................................................................27

5.3.1

Interrupt Request Register..............................................28

5.3.2

Interrupt Acknowledge / Mask Register ..........................31

5.4

Watchdog Timer .........................................................................31

5.4.1

Automatic Baud Rate Identification.................................32

5.4.2

Baud Rate Monitoring .....................................................32

5.4.3

Response Time Monitoring.............................................32

6

PROFIBUS DP Interface............................................35

6.1

DP Buffer Structure ....................................................................35

6.2

Description of the DP Services...................................................38

6.2.1

Set_Slave_Add (SAP 55) ...............................................38

6.2.2

Set _Prm (SAP 61) .........................................................39

6.2.3

Chk_Cfg (SAP 62) ..........................................................43

6.2.4

Slave_Diag (SAP 60)......................................................44

6.2.5

Write_Read_Data / Data_Exchange (Default_SAP).......46

6.2.6

Global_Control (SAP 58) ................................................50

6.2.7

RD_Input (SAP 56) .........................................................51

6.2.8

RD_Output (SAP 57) ......................................................51

6.2.9

Get_Cfg (SAP 59)...........................................................52

VPC3+C User Manual


Revision 1.04 3

Table of Contents

7

PROFIBUS DP Extensions .......................................53

7.1

Set_(Ext_)Prm (SAP 53 / SAP 61) .............................................53

7.2

PROFIBUS DP-V1 .....................................................................54

7.2.1

Acyclic Communication Relationships ............................54

7.2.2

Diagnosis Model .............................................................57

7.3

PROFIBUS DP-V2 .....................................................................58

7.3.1

DXB (Data eXchange Broadcast) ...................................58

7.3.2

IsoM (Isochron Mode).....................................................64

8

Hardware Interface....................................................69

8.1

Universal Processor Bus Interface .............................................69

8.1.1

Overview.........................................................................69

8.1.2

Bus Interface Unit ...........................................................69

8.1.3

Application Examples (Principles) ..................................73

8.1.4

Application with 80C32 (2K Byte RAM Mode) ................75

8.1.5

Application with 80C32 (4K Byte RAM Mode) ................76

8.1.6

Application with 80C165 .................................................77

8.2

Dual Port RAM Controller...........................................................77

8.3

UART..........................................................................................78

8.4

ASIC Test ...................................................................................78

9

PROFIBUS Interface..................................................79

9.1

Pin Assignment ..........................................................................79

9.2

Example for the RS485 Interface ...............................................80

10

Operational Specifications.......................................81

10.1

Absolute Maximum Ratings........................................................81

10.2

Recommended Operating Conditions ........................................81

10.3

General DC Characteristics........................................................81

10.4

Ratings for the Output Drivers....................................................82

10.5

DC Electrical Characteristics Specification for 5V Operation .....82

10.6

DC Electrical Characteristics Specification for 3.3V Operation ..83

10.7

Timing Characteristics................................................................84

10.7.1

System Bus Interface......................................................84

10.7.2

Timing in the Synchronous Intel Mode ...........................85

10.7.3

Timing in the Asynchronous Intel Mode..........................87

10.7.4

Timing in the Synchronous Motorola Mode ....................89

10.7.5

Timing in the Asynchronous Motorola Mode ..................91

10.8

Package .....................................................................................94

10.9

Processing Instructions ..............................................................96

10.10

Ordering Information ..................................................................96


Introduction

1

1 Introduction

Profichip’s VPC3+C is a communication chip with processor interface for intelligent PROFIBUS DP-Slave applications. It’s an enhancement of the

VPC3+B

in terms of protocol functions and power consumption.

The VPC3+C handles the message and address identification, the data security sequences and the protocol processing for PROFIBUS DP. In addition the acyclic communication and alarm messages, described in

DPV1 extension, are supported. Furthermore the slave-to-slave communication Data eXchange Broadcast (DXB) and the Isochronous Bus

Mode (IsoM), described in DPV2 extension, are also provided.

Automatic recognition and support of data transmissions rates up to 12

Mbit/s, the integration of the complete PROFIBUS DP protocol, 4K Byte communication RAM and the configurable processor interface are features to create high-performance PROFIBUS DP-Slave applications. The device can be operated with either 3.3V or 5V single supply voltage. For 3.3V operation the inputs are 5V tolerant.

Profichip’s VPC3+ is the predecessor of VPC3+C and VPC3+B. The chip offers 2 kByte communication RAM and PROFIBUS DP functionality only and is therefore suited for DP-Slave applications which do not require

DP-V1 or DP-V2 functions. The device can be operated with 5V single supply only.

VPC3+

and VPC3+C are pin-compatible. Therefore VPC3+ can be replaced by VPC3+C in existing applications without any restrictions or SWmodifications. However, downgrading from VPC3+C to VPC3+ is only possible, if the additional features of VPC3+C (4K Byte RAM, DP-V1- or

DP-V2-functionality, 3.3V supply) are not used.

As there are also simple devices in the automation engineering area, such as switches or thermoelements, that do not require a microcontroller for data preprocessing, profichip offers a DP-Slave ASIC with 32 direct input/output bits. The VPCLS2 handles the entire data traffic independently.

No additional microprocessor or firmware is necessary. The VPCLS2 is compatible to existing chips.

Further information about our products or current and future projects is available on our web page: http://www.profichip.com

.



Revision 1.04 5

1 Introduction

Notes:


Functional Description

2

2 Functional Description

2.1 Overview

The VPC3+C makes a cost optimized design of intelligent PROFIBUS DP-

Slave applications possible.

The processor interface supports the following processor series:

Intel: 80X86

Motorola: HC11-, HC16-, and HC916 types

The VPC3+C handles the physical layer 1 and the data link layer 2 of the

ISO/OSI-reference-model excluding the analog RS485 drivers.

The integrated 4K Byte Dual-Port-RAM serves as an interface between the VPC3+C and the software/application. In case of using 2K Byte the entire memory is divided into 256 segments, with 8 bytes each. Otherwise in the 4K Byte mode the segment base addresses starts at multiple of 16.

Addressing by the user is done directly, however, the internal Micro

Sequencer (MS) addresses the RAM by means of the so-called basepointer. The base-pointer can be positioned at the beginning of a segment in the memory. Therefore, all buffers must be located at the beginning of a segment.

If the VPC3+C carries out a DP communication it automatically sets up all

DP-SAPs. The various telegram information are made available to the user in separate data buffers (for example, parameter and configuration data).

Three buffers are provided for data communication (three for output data and three for input data). As one buffer is always available for communication no resource problems can occur. For optimal diagnosis support, the

VPC3+C offers two Diagnosis-Buffers. The user enters the updated diagnosis data into these buffers. One Diagnosis-Buffer is always assigned to the VPC3+C.

The Bus Interface Unit is a parameterizable synchronous/asynchronous 8- bit interface for various Intel and Motorola microcontrollers/processors. The user can directly access the internal 2K/4K Byte RAM or the parameter latches and control registers via the 11/12-bit address bus.

Procedure-specific parameters (Station_Address, control bits, etc.) must be transferred to the Parameter Registers and to the Mode Registers after power-on.

The MAC status can be observed at any time in the Status Register.

Various events (e.g. various indications, error events, etc.) are entered in the Interrupt Controller. These events can be individually enabled via a mask register. Acknowledgement takes place by means of the acknowledge register. The VPC3+C has a common interrupt output.

Revision 1.04 7



2 Functional Description

The integrated Watchdog Timer is operated in three different states:

BAUD_SEARCH, BAUD_CONTROL and DP_CONTROL.

The Micro Sequencer (MS) controls the entire process. It contains the DP-

Slave state machine (DP_SM).

The integrated 4K Byte RAM that operates as a Dual-Port-RAM contains procedure-specific parameters (buffer pointer, buffer lengths,

Station_Address, etc.) and the data buffers.

In the UART, the parallel data flow is converted into the serial data flow and vice-versa. The VPC3+C is capable of automatically identifying the baud rates (9.6 Kbit/s - 12 Mbit/s).

The Idle Timer directly controls the bus times on the serial bus line.


Pin Description

3

3 Pin Description

3.1 Pin Assignment

Pin Signal Name In/Out Description Source / Destination

1

2

4

5

6

7

24

AB11

XWR / E_CLOCK

AB11

3 DIVIDER

XRD / R_W

CLK

VSS

CLKOUT2/4

8 XINT/MOT

9 X/INT

10 AB10

11 DB0

12 DB1

13

XDATAEXCH

SYNC

14 XREADY/XDTACK

15 DB2

16 DB3

17

VSS

18

VDD

19 DB4

20 DB5

21 DB6

22 DB7

23 MODE

ALE / AS

AB11

25 AB9

26 TXD

27 RTS

28

VSS

29 AB8

CS-Signal

CPU (80C165)

Address Bus 11 (C32-Mode; 4K Byte RAM)

Write Signal / E_Clock for Motorola

I(C) CPU

Address Bus 11 (Asynchronous Motorola Mode; 4K Byte RAM)

I(C)

Setting the scaling factor for CLKOUT2/4

‘0’ = CLK divided by 4

’1’ = CLK divided by 2

I(C) Read Signal / Read _Write for Motorola

I(TS) System Clock Input, 48 MHz

O Clock Output (System Clock divided by 2 or 4)

I(C)

‘0’ = Intel Interface

’1’ = Motorola Interface

Configuration Pin

CPU

System

System, CPU

Configuration Pin

O Interrupt

C32 mode: ‘0’

C165 mode: Address Bus

CPU; Interrupt-

Controller

C32 Mode: ‘0’

C165 Mode: Address Bus

System, CPU

I(C)/O

I(C)/O

Data Bus

O

C32 Mode: Data/Address Bus multiplexed

C165 Mode: Data/Address Bus separated

Indicates DATA-EXCH state for PROFIBUS DP

Synchronization Signal for Isochron Mode (see section 8.3.2)

CPU, Memory

LED

CPU

System, CPU O Ready for external CPU

I(C)/O

I(C)/O

Data Bus

C32 mode: Data /Address Bus multiplexed

C165 mode: Data/Address Bus separate

CPU, Memory

I(C)/O

I(C)/O

I(C)/O

Data Bus

I(C)/O

I

I(C)

C32 mode: Data/Address Bus multiplexed

C165 mode: Data/Address Bus separate

‘0’ = 80C166 Data/Address Bus separated; Ready Signal

’1’ = 80C32 Data/Address Bus multiplexed, fixed Timing

Address Latch

Enable

C32 mode: ALE

C165 mode: ‘0’ (2K Byte RAM)

Address Bus 11 (Asynchronous Intel and

Synchronous Motorola Mode; 4K Byte RAM)

C32 Mode:

<log>0

C165 Mode: Address Bus

O

O Request to Send

CPU, Memory

Configuration Pin

CPU

CPU, Memory

PROFIBUS Interface

CPU, Memory

9



Revision 1.04


Pin Signal Name

30 RXD

31 AB7

32 AB6

33 XCTS

34 XTEST0

35 XTEST1

36 RESET

37 AB4

38

VSS

39

VDD

40 AB3

41 AB2

42 AB5

43 AB1

44 AB0

In/Out Description

I(C) Serial Receive Port

I(C)

I(C)

Address Bus

I(C) Clear to Send: ‘0’ = send enable

I(C) Pin must be connected to VDD.

I(C) Pin must be connected to VDD.

I(CS) Connect Reset Input with CPU’s port pin.

I(C) Address Bus

I(C)

I(C)

I(C)

Address Bus

I(C)

I(C)

Source / Destination

PROFIBUS Interface

CPU, Memory

FSK Modem

CPU, Memory

CPU, Memory

Figure 3-1: Pin Assignment

Notes:

All signals that begin with X.. are LOW active.

C32-Mode means ‘Synchronous Intel Mode’ and

C165-Mode means ‘Asynchronous Intel Mode’.

VDD = +5 V

VSS = 0 V

Input Levels:

I ( C ) :

I ( CS ) :

CMOS

CMOS, Schmitt-Trigger

I (CPD ) : CMOS, pulldown

I (TS ) : TTL, Schmitt-Trigger

4K Byte RAM extension

Beginning with Step B of the VPC3+ the communication RAM has been extended to 4K Byte, whereas Step A only has 2K Byte. To access the entire 4K Byte RAM in VPC3+C an additional address signal AB11 is required. Which pin is assigned to A11 depends on the Processor Interface

Mode used (see Figure 3-2). Due to compatibility reasons the pin which is now assigned to A11 was unused in Step A for the certain Interface Mode.

Processor Interface Mode Pin Signal Name

Synchronous Intel Mode

Asynchronous Intel Mode

Asynchronous Motorola Mode

Synchronous Motorola Mode

1

24

2

24

XCS

ALE/AS

XWR/E_CLOCK

ALE/AS

Figure 3-2 : Pin assignment for AB11

The 4K Byte RAM extension must be enabled in Mode Register 2 (see

section 5.1.3). By default the 4K Byte mode is disabled.


Pin Description 3

3.2 Pinout

VPC3+C has a 44-pin PQFP housing with the following pinout:

XTEST0

XTEST1

RESET

AB4

VSS

VDD

AB3

AB2

AB5

AB1

AB0

34

33

44

1

23

22

11

12

DB7

DB6

DB5

DB4

VDD

VSS

DB3

DB2

XREADY/XDTACK

XDATAEXCH/SYNC

DB1

Figure 3-3: VPC3+C Pinout

For details about package outline and dimensions see section 10.8.



Revision 1.04 11


Notes:


Memory Organization

4

4 Memory Organization

4.1 Overview

The internal Control Parameters are located in the first 21 addresses. The latches/registers either come from the internal controller or influence the controller. Certain cells are read- or write-only. The internal working cells, which are not accessible by the user, are located in RAM at the same address locations.

The Organizational Parameters are located in RAM beginning with address

16H. The entire buffer structure (for the DP-SAPs) is based on these parameters. In addition, general parameter data (Station_Address,

Ident_Number, etc.) and status information (Global_Control command, etc.) are also stored in these cells.

Corresponding to the parameter setting of the Organizational Parameters, the user-generated buffers are located beginning with address 40H. All buffers or lists must begin at segment addresses (8 bytes segmentation for

2K Byte mode, 16 bytes segmentation for 4K Byte mode).

Address Function

000H

:

015H

016H

:

03FH

Control Parameters

(latches/registers) (21 bytes)

Organizational Parameters (42 bytes)

Internal working cells

040H

:

7FFH (FFFH)

DP-buffers: Data in (3)*

Data out (3)**

Diagnosis

Parameter data (1)

Configuration data (2)

Auxiliary

(1)

(1)

Indication / Response buffers ***

DP-V2-buffer: DXB

(2)

(1)

Figure 4-1: Memory Table

* Data in means input data from DP-Slave to DP-Master

** Data out means output data from DP-Master to DP-Slave

*** number of buffers depends on the entries in the SAP-List

**** DXB out means input data from another DP-Slave (slave-to-slave communication)

13



Revision 1.04


Segment 0

Segment 1

Internal VPC3+C RAM (2K/4K Byte)

Segment 2

8/16 bit segment addresses

(pointer to the buffers)

Segment 254

Segment 255

Building of the physical buffer address:

2K Byte Mode:

7 0

Segment address bit)

0 0 0 Offset

+

10 0

Physical

4K Byte Mode:

7 0

Segment address bit)

0 0 0 Offset

+

11 0

Physical


Memory Organization 4

4.2 Control Parameters (Latches/Registers)

These cells can be either read-only or write-only. In the Motorola Mode the

VPC3+C carries out ‘address swapping’ for an access to the address locations 00H - 07H (word registers). That is, the VPC3+C internally generates an even address from an odd address and vice-versa.

Address

Interrupt Controller Register

02H 03H

−Reg 7..0

03H 02H

−Reg 15..8

Status-Reg 7..0

Status Register

Status-Reg 15..8

7..0

15..8

Mode Register 0

08H Din_Buffer_SM

0AH Dout_Buffer_SM

0CH Diag_Buffer_SM

The user positively acknowledges the user parameter setting data of a

Set_(Ext_)Prm telegram.

The user negatively acknowledges the user parameter setting data of a

Set_(Ext_)Prm telegram.

The user positively acknowledges the configuration data of a Chk_Cfg telegram.

The user negatively acknowledges the configuration data of a Chk_Cfg telegram.

12H

13H

14H SSA_Buffer_Free_Cmd

15H Mode-Reg 1 7..0

The user has fetched the data from the SSA_Buf and enables the buffer again.

Figure 4-2: Assignment of the Internal Parameter-Latches for READ



Revision 1.04 15


Address

01H

02H

03H

04H

05H

00H Int-Req_Reg

7..0

15..8

03H Int-Ack-Reg

02H Int-Ack-Reg

7..0

15..8

Interrupt-Controller-Register

05H Int

−Mask-Reg 7..0

04H

Int

−Mask-Reg 15..8

06H

07H

07H Mode-Reg0

06H Mode-Reg0

7..0

15..8

Setting parameters for individual bits

08H

09H

0DH

Mode-Reg1-S 7..0

Mode-Reg1-R 7..0

0AH WD_BAUD_CONTROL_Val

Square-root value for baud rate monitoring

0BH

0CH minT

SDR

_Val 7..0

Sync_PW_Reg 7..0 Sync Pulse Width Register

0EH

0FH

10H

11H

12H

13H

14H

15H

Reserved

Figure 4-3: Assignment of the Internal Parameter-Latches for WRITE


Memory Organization 4

4.3 Organizational Parameters (RAM)

The user stores the organizational parameters in the RAM under the specified addresses. These parameters can be written and read.

Address

16H R_TS_Adr

18H

19H

17H SAP_List_Ptr

Pointer to a RAM address which is preset with FFh or to SAP-List

19H R_User_WD_Value 7..0

In DP_Mode an internal 16-bit watchdog

18H R_User_WD_Value 15..8

1AH R_Len_Dout_Buf

1BH R_Dout_Buf_Ptr1

1CH

1DH

1EH

1FH

R_Dout_Buf_Ptr2

R_Dout_Buf_Ptr3

R_Len_Din_Buf

R_Din_Buf_Ptr1

2AH R_Aux_Buf_Sel

2BH

2CH

R_Aux_Buf_Ptr1

R_Aux_Buf_Ptr2

2DH R_Len_SSA_Data

2EH R_SSA_Buf_Ptr

2FH R_Len_Prm_Data

Length of the 3 Dout_Buf

Segment base address of Dout_Buf 1



Length of the 3 Din_Buf

Segment base address of Din_Buf 1

20H

21H

R_Din_Buf_Ptr2

R_Din_Buf_Ptr3



22H R_Len_DXBout_Buf Length of the 3 DXBout_Buf

23H R_DXBout_Buf_Ptr1 Segment

24H

25H

26H

R_Len Diag_Buf1

R_Len Diag_Buf2

R_Diag_Buf_Ptr1

Length of Diag_Buf 1

Length of Diag_Buf 2

Segment base address of Diag_Buf 1

27H R_Diag_Buf_Ptr2

28H R_Len_Cntrl_Buf1

29H R_Len_Cntrl_Buf2

Segment base address of Diag_Buf 2

Length of Aux_Buf 1 and the corresponding control buffer, for example

SSA_Buf, Prm_Buf, Cfg_Buf,

Read_Cfg_Buf

Length of Aux_Buf 2 and the corresponding control buffer, for example

SSA_Buf, Prm_Buf, Cfg_Buf,

Read_Cfg_Buf

Bit array; defines the assignment of the

Aux_Buf 1 and 2 to the control buffers

SSA_Buf, Prm_Buf, Cfg_Buf

Segment base address of Aux_Buf 1

Segment base address of Aux_Buf 2

Length of the input data in the

Set_Slave_Address_Buf

Segment base address of the

Set_Slave_Address_Buf

Length of the input data in the Prm_Buf



Revision 1.04 17


Address

30H R_Prm_Buf_Ptr

31H R_Len_Cfg_Data

32H R_Cfg_Buf_Ptr

Segment base address of the Prm_Buf

33H

R_Len_Read_Cfg_Data

34H R_Read_Cfg_Buf_Ptr

Length of the input data in the

Read_Cfg_Buf


Read_Cfg_Buf

35H R_Len_DXB_Link_Buf Length of the DXB_Linktable

36H R_DXB_Link_Buf_Ptr


DXB_Link_Buf

37H R_Len_DXB_Status_Buf Length of the DXB_Status

38H R_DXB_Status_Buf_Ptr


DXB_Status_Buf

This parameter specifies whether the

Station_Address may be changed again later.

3AH R_Ident_Low

3BH R_Ident_High

3CH R_GC_Command

3DH R_Len_Spec_Prm_Buf

The user sets the parameters for the

Ident_Number_Low value.

The user sets the parameters for the

Ident_Number_High value.

The Control_Command of Global_Control last received

If parameters are set for the

Spec_Prm_Buffer_Mode (see Mode

Register 0), this cell defines the length of the Prm_Buf.

3EH R_DXBout_Buf_Ptr2 Segment

3FH R_DXBout_Buf_Ptr3 Segment

Figure 4-4: Assignment of the Organizational Parameters


ASIC Interface

5

5 ASIC Interface

5.1 Mode Registers

In the VPC3+C parameter bits that access the controller directly or which the controller directly sets are combined in three Mode Registers (0, 1 and

2).

5.1.1 Mode Register 0

Setting parameters for Mode Register 0 may take place in the Offline state only

(for example, after power-on). The VPC3+C may not exit the

Offline state until Mode Register 0, all Control and Organizational Parameters are loaded (START_VPC3 = 1 in Mode Register 1).

Address

7 6 5

Bit Position

4 3 2 1 0

Designation

06H

(Intel)

Mode Reg 0

7 .. 0

See below for coding

Address

15 14

Bit Position

13 12 11 10 9 8

Designation

07H

(Intel)

Mode Reg 0

15 .. 8


*) If Spec_Clear_Mode = 1 (Fail Safe Mode) the VPC3+C will accept Data_Exchange telegrams without any output data (data unit length = 0) in the state DATA-EXCH. The reaction to the outputs can be parameterized in the parameterization telegram.

**) When a large number of parameters have to be transmitted from the DP-Master to the

DP-Slave, the Aux-Buffer 1/2 must have the same length as the Parameter-Buffer.

Sometimes this could reach the limit of the available memory in the VPC3+C. When

Spec_Prm_Buf_Mode = 1 the parameterization data are processed directly in this special buffer and the Aux-Buffers can be held compact.

19



Revision 1.04


bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0

Mode Register 0, Low-Byte, Address 06H (Intel):

Freeze_Supported

: Freeze_Mode support

0 = Freeze_Mode is not supported.

1 = Freeze_Mode is supported

Sync_Supported:

Sync_Mode support

0 = Sync_Mode is not supported.

1 = Sync_Mode is supported.

Early_Rdy

: Early Ready

0 = Normal Ready: Ready is generated when data is valid (write) or when data has been accepted (read).

1 = Ready is generated one clock pulse earlier

INT_Pol:

Interrupt Polarity

0 = The interrupt output is low-active.

1 = The interrupt output is high-active.

minT

SDR

:

Default setting for the minT

SDR

after reset for DP operation or combi operation.

0 = Pure DP operation (default configuration!)

1 = Combi operation

WD_Base:

Watchdog Time Base

0 = Watchdog time base is 10 ms (default state)

1 = Watchdog time base is 1 ms

Dis_Stop_Control:

Disable Stopbit Control

0 = Stop bit monitoring is enabled.

1 = Stop bit monitoring is switched off

Set_Prm telegram overwrites this memory cell in the DP_Mode. (Refer to the user specific data.)

Dis_Start_Control:

Disable Startbit Control

0 = Monitoring the following start bit is enabled.

1 = Monitoring the following start bit is switched off

Set_Prm telegram overwrites this memory cell in the DP_Mode. (Refer to the user specific data.)

Figure 5-1: Coding of Mode Register 0, Low-Byte


ASIC Interface 5


Mode Register 0, High-Byte, Address 07H (Intel):

Reserved

PrmCmd_Supported

: PrmCmd support for redundancy

0 = PrmCmd is not supported.

1 = PrmCmd is supported

Spec_Clear_Mode:

Special Clear Mode (Fail Safe Mode)

0 = No special clear mode.

1 = Special clear mode. VPC3+C will accept data telegrams with data unit = 0

Spec_Prm_Buf_Mode:

Special-Parameter-Buffer Mode

0 = No Special-Parameter-Buffer.

1 = Special-Parameter-Buffer mode. Parameterization data will be stored directly in the Special-Parameter-Buffer.

Set_Ext_Prm_Supported:

Set_Ext_Prm telegram support

0 = SAP 53 is deactivated

1 = SAP 53 is activated

User_Time_Base:

Timebase of the cyclical User_Time_Clock-Interrupt

0 = The User_Time_Clock-Interrupt occurs every 1 ms.

1 = The User_Time_Clock-Interrupt occurs every 10 ms.

EOI_Time_Base:

End-of-Interrupt Timebase

0 = The interrupt inactive time is at least 1 µs long.

1 = The interrupt inactive time is at least 1 ms long

DP_Mode:

DP_Mode enable

0 = DP_Mode is disabled.

1 = DP_Mode is enabled. VPC3+C sets up all DP_SAPs (default configuration!)

Figure 5-2: Coding of Mode Register 0, High-Byte


Some control bits must be changed during operation. These control bits are combined in Mode Register 1 and can be set independently of each other

(Mode-Reg_1_S) or can be reset independently of each other (Mode-

Reg_1_R). Separate addresses are used for setting and resetting. A logical

‘1’ must be written to the bit position to be set or reset.

For example, to set START_VPC3 write a '1' to address 08H, in order to reset this bit, write a '1' to address 09H.



Revision 1.04 21


Address

7

08H

6 5

Bit Position

4 3 2 1 0

Designation

Mode-Reg_1_S

7..0

09H Mode-Reg_1_R

7..0

See below for coding bit 7 bit 6 bit 5 bit 4

Mode Register 1, Set, Address 08H:

Reserved

Reserved

Res_User_WD:

Resetting the User_WD_Timer

1 = VPC3+C sets the User_WD_Timer to the parameterized value

User_WD_Value. After this action, VPC3+C sets Res_User_WD to ’0'.

En_Change_Cfg_Buffer:

Enabling buffer exchange (Config-Buffer for

Read_Config-Buffer)

0 = With User_Cfg_Data_Okay_Cmd, the Config-Buffer may not be exchanged for the Read_Config-Buffer.

1 = With User_Cfg_Data_Okay_Cmd, the Config-Buffer must be exchanged for bit 3 bit 2 bit 1 bit 0

User_LEAVE-MASTER.

Request to the DP_SM to go to WAIT-PRM.

1 = The user causes the DP_SM to go to WAIT-PRM.

After this action, VPC3+ sets User_LEAVE-MASTER to ’0’ again.

Go_Offline:

Going into the Offline state

1 = After the current request ends, VPC3+C goes to the Offline state and sets

Go_Offline to ’0’ again.

EOI:

End-of-Interrupt

1 = VPC3+C disables the interrupt output and sets EOI to ’0‘ again.

Start_VPC3:

Exiting the Offline state

1 = VPC3+C exits offline and goes to Passive_Idle

In addition the Idle Timer and Watchdog Timer are started and

‘Go_Offline = 0’ is set

Figure 5-3: Coding of Mode Register 1




Setting parameters for Mode Register 2 may take place in the Offline

State only (like Mode Register 0).

Address

7 6 5

Bit Position

4 3 2 1 0

Designation

0CH Mode Reg 2

7 .. 0



Revision 1.04 23


bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1

Mode Register 2, Address 0CH:

4KB_Mode:

size of internal RAM

0 = 2K Byte RAM (default).

1 = 4K Byte RAM

No_Check_Prm_Reserved:

disables checking of the reserved bits in

DPV1_Status_2/3 of Set_Prm telegram

0 = reserved bits of a Set_Prm telegram are checked (default).

1 = reserved bits of a Set_Prm telegram are not checked.

SYNC_Pol:

polarity of SYNC pulse (for Isochron Mode only)

0 = negative polarity of SYNC pulse (default)

1 = positive polarity of SYNC pulse

SYNC_Ena:

enables generation of SYNC pulse (for Isochron Mode only)

0 = SYNC pulse generation is disabled (default)

1 = SYNC pulse generation is enabled

DX_Int_Port:

Port mode for DX_Out interrupt (ignored if SYNC_Ena set)

0 = DX_Out interrupt is not assigned to port DATAEXCH (default).

1 = DX_Out Interrupt (synchronized to SYNCH telegram) is assigned to port

DATAEXCH.

DX_Int_Mode:

Mode of DX_out interrupt

0 = DX_Out interrupt is only generated, if Len_Dout_Buf is unequal 0 (default).

1 = DX_Out interrupt is generated after every Data_Exchange telegram

No_Check_GC_Reserved:

Disables checking of the reserved bits in

Global_Control telegram

0 = reserved bits of a Global_Control telegram are checked (default).

1 = reserved bits of a Global_Control telegram are not checked. bit 0

GC_Int_Mode:

Controls generation of New_GC_Command interrupt

0 = New_GC_Command interrupt is only generated, if a changed

Global_Control telegram is received

1 = New_GC_Command interrupt is generated after every Global_Control

telegram (default)

Figure 5-4: Coding of Mode Register 2



5.2 Status Register

The Status Register shows the current VPC3+C status and can be read only.

Bit Position

Address Designation

7 6 5 4 3 2 1 0

04H

(Intel)

WD_State DP_State

1 0 1 0 Reserv

Status-Reg

7..0


Address

15 14 13

Bit Position

12 11 10 9 8

Designation

05H

(Intel)

VPC3+ Release Baud Rate

Status-Reg

15..8

See below

Status Register,Low-Byte, Address 04H (Intel):

bit 7,6

WD_State 1..0:

State of the Watchdog State Machine

00 = BAUD_SEARCH state

01 = BAUD_CONTROL state

10 = DP_CONTROL state

11 = Not possible bit 5,4

DP_State 1..0:

State of the DP State Machine

00 = WAIT-PRM state

01 = WAIT-CFG state

10 = DATA-EXCH state

11 = Not possible bit 3 bit 2

Reserved

Diag_Flag:

Status of the Diagnosis-Buffer

0 = The Diagnosis-Buffer had been fetched by the DP-Master.

1 = The Diagnosis-Buffer had not been fetched by the DP-Master yet. bit 1 bit 0

Reserved

Offline/Passive-Idle:

Offline-/Passive_Idle state

0 = VPC3+C is in Offline.

1 = VPC3+C is in Passive_Idle.

Figure 5-5: Status Register, Low-Byte



Revision 1.04 25


Status Register, High-Byte, Address 05H (Intel):

bit 15-12 VPC3+-Release 3..0 : Release number for VPC3+

0000 = Step A

1011 = Step B

1100 = Step C

1101 = Step D

Rest = Not possible bit 11-8

Baud Rate 3..0 :

The baud rate found by VPC3+D

0000 = 12,00 Mbit/s

0001 = 6,00 Mbit/s

0010 = 3,00 Mbit/s

0011 = 1,50 Mbit/s

0100 = 500,00 Kbit/s

0101 = 187,50 Kbit/s

0110 = 93,75 Kbit/s

0111 = 45,45 Kbit/s

1000 = 19,20 Kbit/s

1001 = 9,60 Kbit/s

1111 = after reset and during baud rate search not

Figure 5-6: Status Register, High-Byte



5.3 Interrupt Controller

The processor is informed about indication messages and various error events via the interrupt controller. Up to a total of 16 events are stored in the interrupt controller. The events are summed up to a common interrupt output. The controller does not have a prioritization level and does not provide an interrupt vector (not 8259A compatible!).

The controller consists of an Interrupt Request Register (IRR), an Interrupt

Mask Register (IMR), an Interrupt Register (IR) and an Interrupt Acknowledge Register (IAR).

µP µP µP

VPC3+

µP

S

R

IRR IMR

S

R

IR

Σ

X/INT

µP

IAR

INT_POL

Figure 5-7: Block Diagram of Interrupt Controller

Each event is stored in the IRR. Individual events can be suppressed via the IMR. The input in the IRR is independent of the interrupt masks. Events that are not masked in the IMR set the corresponding IR bit and generate the X/INT interrupt via a sum network. The user can set each event in the

IRR for debugging.

Each interrupt event that was processed by the microcontroller must be deleted via the IAR (except for New_(Ext_)Prm_Data and New_Cfg_Data).

A logical ‘1’ must be written on the specific bit position. If a new event and an acknowledge from the previous event are present at the IRR at the same time, the event remains stored. If the microcontroller enables a mask subsequently, it must be ensured that no prior IRR input is present. To be on the safe side, the position in the IRR must be deleted prior to the enabling of the mask.

Before leaving the interrupt routine, the microprocessor must set the ‘end of interrupt bit' (EOI = 1) in Mode Register 1. The interrupt output is switched to inactive with this edge change. If another event occurs, the interrupt output is not activated again until the interrupt inactive time of at least 1 µs or 1 ms expires. This interrupt inactive time can be set via EOI_Time_Base in Mode Register 0. This makes it possible to enter the interrupt routine again when an edge-triggered interrupt input is used.



Revision 1.04 27


The polarity of the interrupt output is parameterized via the Int_Pol bit in

Mode Register 0. After hardware reset, the output is low-active.

5.3.1 Interrupt Request Register

Address

7 6 5

00H

(Intel)

Bit Position

4 3 2 1 0

Designation

Int-Req-Reg

7 .. 0


Address

15

01H

(Intel)

14

Bit Position

13 12 11 10 9 8

Designation

Int-Req-Reg

15 .. 8





Interrupt-Request-Register, Low-Byte, Address 00H (Intel):

DXB_Out:

VPC3+C has received a DXB telegram and made the new output data available in the ‘N’ buffer.

New_Ext_Prm_Data:

The VPC3+C has received a Set_Ext_Prm telegram and made the data available in the Parameter-Buffer.

DXB_Link_Error:

The Watchdog cycle is elapsed and at least one Publisher-Subscriber connection breaks down.

User_Timer_Clock:

The time base for the User_Timer_Clocks is run out (1 / 10ms).

WD_DP_CONTROL_Timeout:

The watchdog timer expired in the DP_CONTROL state.

Baud_Rate_Detect:

The VPC3+C has left the BAUD_SEARCH state and found a baud rate.

Go/Leave_DATA-EXCH:

The DP_SM has entered or exited the DATA-EXCH state.

MAC_Reset:

After processing the current request, the VPC3+C has entered the Offline state

(by setting the Go_Offline bit).

Figure 5-8: Interrupt-Request-Register, Low-Byte



Revision 1.04 29



Interrupt Request Register 0, High-Byte, Address 01H (Intel):

FDL_Ind:

The VPC3+C has received an acyclic service request and made the data available in an Indication-Buffer.

Poll_End_Ind:

The VPC3+C have send the response to an acyclic service.

DX_Out:

The VPC3+C have received a Data_Exchange telegram and made the new output data available in the ‘N’ buffer.

Diag_Buffer_Changed:

Due to the request made by New_Diag_Cmd, the VPC3+C exchanged the

Diagnosis-Buffers and made the old buffer available to the user again.

New_Prm_Data:

The VPC3+C have received a Set_Prm telegram and made the data available in the Parameter-Buffer.

New_Cfg_Data:

The VPC3+C have received a Chk_Cfg telegram and made the data available in the Config-Buffer.

New_SSA_Data:

The VPC3+C have received a Set_Slave_Add telegram and made the data available in the Set_Slave_Add-Buffer.

New_GC_Command:

The VPC3+C have received a Global_Control telegram and stored the

Control_Command in the R_GC_Command RAM cell.

Figure 5-9: Interrupt Request Register, High-Byte



5.3.2 Interrupt Acknowledge / Mask Register

The other interrupt controller registers are assigned in the bit positions like the Interrupt Request Register.

Address Register Reset state Assignment

02H / 03H Interrupt

Register (IR)

Readable only All bits cleared

04H / 05H Interrupt

Mask

Register

(IMR)

Writeable, can be changed during operation

All bits set

02H / 03H Interrupt

Acknowledge

Register

(IAR)

Writeable, can be changed during operation

All bits cleared

1 = Mask is set and the interrupt is disabled

0 = Mask is cleared and the interrupt is enabled

1 = Interrupt is acknowledged and the IRR bit is cleared

0 = IRR bit remains unchanged

Figure 5-10: Interrupt Acknowledge / Mask Register

The New_(Ext_)Prm_Data, New_Cfg_Data interrupts cannot be acknowledged via the Interrupt Acknowledge Register. The relevant state machines clear these interrupts through the user acknowledgements (for example, User_Prm_Data_Okay etc.).

5.4 Watchdog Timer

The VPC3+C is able to identify the baud rate automatically. The state machine is in the BAUD_SEARCH state after each RESET and also after the

Watchdog (WD) Timer has expired in the BAUD_CONTROL state.

BAUD_SEARCH

WD_Timeout baudrate detected

BAUD_CONTROL

WD_On = 0 or

WD_DP_CONTROL_Timeout

WD_On = 1

DP_CONTROL

Figure 5-11: Watchdog State Machine (WD_SM)



Revision 1.04 31


5.4.1 Automatic Baud Rate Identification

The VPC3+C starts searching for the transmission rate using the highest baud rate. If no SD1 telegram, SD2 telegram, or SD3 telegram was received completely and without errors during the monitoring time, the search continues using the next lower baud rate.

After identifying the correct baud rate, the VPC3+C switches to the

BAUD_CONTROL state and observes the baud rate. The monitoring time can be parameterized (WD_BAUD_CONTROL_Val). The watchdog uses a clock of 100 Hz (10 ms). Each telegram to its own Station_Address received with no errors resets the Watchdog. If the timer expires, the

VPC3+C switches to the BAUD_SEARCH state again.

5.4.2 Baud Rate Monitoring

The detected baud rate is permanently monitored in BAUD_CONTROL.

The Watchdog is triggered by each error-free telegram to its own

Station_Address. The monitoring time results from multiplying twice

WD_BAUD_CONTROL_Val (user sets this parameter) by the time base (10 ms). If the timer expires, WD_SM again goes to BAUD_SEARCH. If the user uses the DP protocol (DP_Mode = 1, see Mode Register 0), the watchdog is used for the DP_CONTROL state, after a Set_Prm telegram was received with an enabled response time monitoring (WD_On = 1). The watchdog timer remains in the baud rate monitoring state when the master monitoring is disabled (WD_On = 0). The DP_SM is not reset when the timer expires in the state BAUD_CONTROL. That is, the DP-Slave remains in the DATA-EXCH state, for example.

5.4.3 Response Time Monitoring

The DP_CONTROL state serves as the response time monitoring of the

DP-Master (Diag_Master_Add). The used monitoring time results from multiplying both watchdog factors and then multiplying this result with the time base (1 ms or 10 ms):

T

WD

= WD_Base * WD_Fact_1 * WD_Fact_2

(See byte 7 of the Set_Prm telegram.)

The user can load the two watchdog factors (WD_Fact_1 and WD_Fact_2) and the time base that represents a measurement for the monitoring time via the Set_Prm telegram with any value between 1 and 255.

EXCEPTION:

The WD_Fact_1 = WD_Fact_2 = 1 setting is not allowed. The circuit does not check this setting.

A monitoring time between 2 ms and 650 s - independent of the baud rate - can be implemented with the allowed watchdog factors.



If the monitoring time expires, the VPC3+C goes to BAUD_CONTROL state again and generates the WD_DP_CONTROL_Timeout interrupt. In addition, the DP State Machine is reset, that is, it generates the reset states of the buffer management. This operation mode is recommended for the most applications.

If another DP-Master takes over the VPC3+C, the Watchdog State Machine either branches to BAUD_CONTROL (WD_On = 0) or to DP_CONTROL

(WD_On = 1).



Revision 1.04 33


Notes:


PROFIBUS DP Interface

6

6 PROFIBUS DP Interface

6.1 DP Buffer Structure

The DP_Mode is enabled in the VPC3+C with ‘DP_Mode = 1’ (see Mode

Register 0). In this mode, the following SAPs are permanently reserved:

Default SAP: Write and Read data (Data_Exchange)

SAP 53: Sending extended parameter setting data (Set_Ext_Prm)

SAP 55:

SAP 56:

Changing the Station_Address (Set_Slave_Add)

Reading the inputs (RD_Input)

SAP 57:

SAP 58:

SAP 59:

SAP 60:

Reading the outputs (RD_Output)

Control commands to the DP-Slave (Global_Control)

Reading configuration data (Get_Cfg)

Reading diagnosis information (Slave_Diag)

SAP 61:

SAP 62:

Sending parameter setting data (Set_Prm)

Checking configuration data (Chk_Cfg)

The DP-Slave protocol is completely integrated in the VPC3+C and is handled independently. The user must correspondingly parameterize the

ASIC and process and acknowledge received messages. All SAPs are always enabled except the Default SAP, SAP 56, SAP 57 and SAP 58. The remaining SAPs are not enabled until the DP_SM goes into the DATA-

EXCH state. The user can disable SAP 55 to not permit changing the

Station_Address. The corresponding buffer pointer R_SSA_Buf_Ptr must be set to ‘00H’ for this purpose.

The DP_SAP Buffer Structure is shown in Figure 6-1. The user configures

all buffers (length and buffer start) in the Offline state. During operation, the buffer configuration must not be changed, except for the length of the Dout-

/Din-Buffers.

The user may still adapt these buffers in the WAIT-CFG state after the configuration telegram (Chk_Cfg). Only the same configuration may be accepted in the DATA-EXCH state.

The buffer structure is divided into the data buffers, Diagnosis-Buffers and the control buffers. Both the output data and the input data have three buffers available with the same length. These buffers are working as changing buffers. One buffer is assigned to the ‘D’ data transfer and one buffer is assigned to the ‘U’ user. The third buffer is either in a next state 'N' or a free state ‘F’. One of the two states is always unoccupied.

For diagnosis two Diagnosis-Buffers, that can have different lengths, are available. One Diagnosis-Buffer (D) is always assigned to the VPC3+C for sending. The other Diagnosis-Buffer (U) belongs to the user for preprocessing new diagnosis data.

35



Revision 1.04


D N U

Dout-Buffer

D-N changed by VPC3+

N-U changed by User

D N U

Din-Buffer

D U

Diagnosis-

Buffer

Read_Config-

Buffer changed by User

UART

Config-Buffer

Aux

1/2

Set-Slave-

Address-Buffer

Aux

1/2

Parameter-

Buffer

Figure 6-1: DP_SAP Buffer Structure

The VPC3+C first stores the parameter telegrams (Set_Slave_Add and

Set_(Ext_)Prm) and the configuration telegram (Chk_Cfg) in Aux-Buffer 1 or Aux-Buffer 2. If the telegrams are error-free, data is exchanged with the corresponding target buffer (Set_Slave_Add-Buffer, Parameter-Buffer and

Config-Buffer). Each of the buffers to be exchanged must have the same

length. In the R_Aux_Buf_Sel parameter cell (see Figure 6-2) the user

defines which Aux_buffers are to be used for the telegrams mentioned


PROFIBUS DP Interface 6

above. The Aux-Buffer 1 must always be available, Aux-Buffer 2 is optional.

If the data profiles of these DP telegrams are very different (for example the length of the Set_Prm telegram is significantly larger than the length of the other telegrams) it is suggested to make an Aux-Buffer 2 available

(R_Aux_Buf_Sel: Set_Prm = 1) for this telegram. The other telegrams are then read via Aux-Buffer 1 (R_Aux_Buf_Sel: Set_Slave_Adr = 0, Chk_Cfg

= 0). If the buffers are too small, the VPC3+C responds with “no resources”

(RR)!

Bit Position


7 6 5 4 3 2 1 0

2AH R_Aux_Buf_Sel


R_Aux_Buf_Sel, Address 2AH:

bit 7-3

Don’t Care:

Read as ‘0’ bit 2 bit 1 bit 0

Set_Slave_Adr:

Set Slave Address

0 = Aux-Buffer 1

1 = Aux-Buffer 2

Chk_Cfg:

Check Configuration

0 = Aux-Buffer 1

1 = Aux-Buffer 2

Set_Prm:

Set (Extended) Parameter

0 = Aux-Buffer 1

1 = Aux-Buffer 2

Figure 6-2: Aux-Buffer Management

The user makes the configuration data (Get_Cfg) available in the

Read_Config-Buffer for reading. The Read_Config-Buffer must have the same length as the Config-Buffer.

The RD_Input telegram is serviced from the Din-buffer in the ‘D’ state and the RD_Output telegram is serviced from the Dout-Buffer in the ‘U’ state.

All buffer pointers are 8-bit segment addresses, because the VPC3+C have only 8-bit address registers internally. For a RAM access, VPC3+C adds an

8-bit offset address to the segment address shifted by 4 bits (result: 12-bit physical address) in case of 4K Byte RAM or shifted by 3 bits (result: 11- bit physical address) in case of 2K Byte RAM. With regard to the buffer start addresses, this specification results either in a 16-byte or in an 8-byte granularity.



Revision 1.04 37


6.2 Description of the DP Services

6.2.1 Set_Slave_Add (SAP 55)

Sequence for the Set_Slave_Add service

The user can disable this service by setting ‘R_SSA_Puf_Ptr = 00H’. The

Station_Address must then be determined, for example, by reading a DIPswitch or an EEPROM and writing the address in the RAM cell R_TS_Adr.

There must be a non-volatile memory available (for example an external

EEPROM) to support this service. It must be possible to store the

Station_Address and the Real_No_Add_Change (‘True’ = FFH) parameter in this EEPROM. After each restart caused by a power failure, the user must read these values from the EEPROM again and write them to the

R_TS_Adr und R_Real_No_Add_Change RAM registers.

If SAP55 is enabled and the Set_Slave_Add telegram is received correctly, the VPC3+C enters the pure data in the Aux-Buffer 1/2, exchanges the

Aux-Buffer 1/2 for the Set_Slave_Add-Buffer, stores the entered data length in R_Len_SSA_Data, generates the New_SSA_Data interrupt and internally stores the New_Slave_Add as Station_Address and the

No_Add_Chg as Real_No_Add_Chg. The user does not need to transfer this changed parameter to the VPC3+C again. After reading the buffer, the user generates the SSA_Buffer_Free_Cmd (read operation on address

14H). This makes the VPC3+C ready again to receive another

Set_Slave_Add telegram (for example, from a different DP-Master).

The VPC3+C reacts automatically to errors.

Bit Position


7 6 5 4 3 2 1 0

SSA_Buf_Free_Cmd, Address 14H:

bit 7-0

Don’t care:

Read as ‘0’

Figure 6-3: Coding of SSA_Buffer_Free_Command



Structure of the Set_Slave_Add Telegram

The net data are stored as follows in the SSA buffer:

Bit Position

Byte

7 6 5 4 3 2 1 0

Designation

4

:

243

Figure 6-4: Structure of the Set_Slave_Add Telegram

6.2.2 Set _Prm (SAP 61)

Rem_Slave_Data additional application specific data

Parameter Data Structure

The VPC3+C evaluates the first seven data bytes (without

User_Prm_Data), or the first eight data bytes (with User_Prm_Data). The first seven bytes are specified according to the standard. The eighth byte is available to the application.

If a PROFIBUS DP extension shall be used, the bytes 7-9 are called

DPV1_Status and must be coded as described in section 7,

“PROFIBUS DP Extensions”. Generally it is recommended to start the

User_Prm_Data first with byte 10.



Revision 1.04 39


Byte

7 6 5

Bit Position

4 3 2 1 0

0

Designation

Station Status

3 minT

SDR

7 0 0

Spec_User_Prm_Byte

/DPV1_Status_1

10

:

243

Figure 6-5: Format of the Set_Prm Telegram

User_Prm_Data



bit 7

Spec_User_Prm_Byte / DPV1_Status_1:

DPV1_Enable:

0 = DP-V1 extensions disabled (default)

1 = DP-V1 extensions enabled bit 6

Fail_Safe:

0 = Fail Safe mode disabled (default)

1 = Fail Safe mode enabled bit 5 bit 4-3

Reserved:

To be parameterized with ‘0’ bit 2

WD_Base:

Watchdog Time Base

0 = Watchdog time base is 10 ms (default)

1 = Watchdog time base is 1 ms bit 1

Publisher_Enable:

0 = Publisher function disabled (default)

1 = Publisher function enabled bit 0

Dis_Stop_Control:

Disable Stop bit Control

0 = Stop bit monitoring in the receiver is enabled (default)

1 = Stop bit monitoring in the receiver is disabled

Dis_Start_Control:

Disable Start bit Control

0 = Start bit monitoring in the receiver is enabled (default)

1 = Start bit monitoring in the receiver is disabled

Figure 6-6: Spec_User_Prm_Byte / DPV1_Status_1

It is recommended not to use the DPV1_Status bytes (bytes 7-9) for user parameter data.



Revision 1.04 41


Parameter Data Processing Sequence

In the case of a positive validation of more than seven data bytes, the

VPC3+C carries out the following reaction:

The VPC3+C exchanges Aux-Buffer 1/2 (all data bytes are entered here) for the Parameter-Buffer, stores the input data length in R_Len_Prm_Data and triggers the New_Prm_Data interrupt. The user must then check the

User_Prm_Data and either reply with User_Prm_Data_Okay_Cmd or with

User_Prm_Data_Not_Okay_Cmd. The entire telegram is entered in this buffer. The user parameter data are stored beginning with data byte 8, or with byte 10 if DPV1_Status bytes used.

The user response (User_Prm_Data_Okay_Cmd or

User_Prm_Data_Not_Okay_Cmd) clears the New_Prm_Data interrupt.

The user cannot acknowledge the New_Prm_Data interrupt in the IAR register.

With the User_Prm_Data_Not_Okay_Cmd message, relevant diagnosis bits are set and the DP_SM branches to WAIT-PRM.

The User_Prm_Data_Okay and User_Prm_Data_Not_Okay acknowledgements are read accesses to defined registers with the relevant signals:

• User_Prm_Finished: No additional parameter telegram is present.

• Prm_Conflict: An additional parameter telegram is present, processing again

• Not_Allowed: Access not permitted in the current bus state

Bit Position


7 6 5 4 3 2 1 0

0EH

⇓ ⇓

User_Prm_

Data_Okay



Address

7 6 5

Bit Position

4 3 2 1

0FH

⇓

Designation

0

⇓

User_Prm_

Data_Not_Okay

Figure 6-7: Coding of User_Prm_(Not)_Okay_Cmd

If another Set_Prm telegram is supposed to be received in the meantime, the signal Prm_Conflict is returned for the positive or negative acknowledgement of the first Set_Prm telegram. Then the user must repeat the validation because the VPC3+C has made a new Parameter-Buffer available.

6.2.3 Chk_Cfg (SAP 62)

The user checks the correctness of the configuration data. After receiving an error-free Chk_Cfg telegram, the VPC3+C exchanges the Aux-Buffer 1/2

(all data bytes are entered here) for the Config-Buffer, stores the input data length in R_Len_Cfg_Data and generates the New_Cfg_Data interrupt.

Then the user has to check the User_Config_Data and either respond with

User_Cfg_Data_Okay_Cmd or with User_Cfg_Data_Not_Okay_Cmd. The pure data is entered in the buffer in the format of the standard.

The user response (User_Cfg_Data_Okay_Cmd or the

User_Cfg_Data_Not_Okay_Cmd response) clears the New_Cfg_Data interrupt. The user cannot acknowledge the New_Cfg_Data in the IAR register.

If an incorrect configuration is reported, several diagnosis bits are changed and the VPC3+C branches to state WAIT-PRM.

For a correct configuration, the transition to DATA-EXCH takes place immediately, if trigger counters for the parameter telegrams and configuration telegrams are at 0. When entering into DATA-EXCH, the

VPC3+C also generates the Go/Leave_DATA-EXCH Interrupt.

If the received configuration data from the Config-Buffer is supposed to result in a change to the Read_Config-Buffer (contains the data for the

Get_Cfg telegram), the user have to make the new Read_Config data available in the Read_Config-Buffer before the User_Cfg_Data_Okay_Cmd acknowledgement, that is the user has to copy the new configuration data into the Read_Config-Buffer.

During acknowledgement, the user receives information about whether there is a conflict or not. If another Chk_Cfg telegram was supposed to be



Revision 1.04 43


received in the meantime, the user receives the Cfg_Conflict signal during the positive or negative acknowledgement of the first Chk_Cfg telegram.

Then the user must repeat the validation, because the VPC3+C have made a new Config-Buffer available.

The User_Cfg_Data_Okay_Cmd and User_Cfg_Data_Not_Okay_Cmd acknowledgements are read accesses to defined memory cells with the relevant Not_Allowed, User_Cfg_Finished, or Cfg_Conflict signals.

If the New_Prm_Data and New_Cfg_Data are supposed to be present simultaneously during start-up, the user must maintain the Set_Prm and then the Chk_Cfg acknowledgement sequence.

Bit Position


7 6 5 4 3 2 1 0

10H

⇓ ⇓

User_Cfg_

Data_Okay

Address

7 6 5

Bit Position

4 3 2 1

11H

⇓

Designation

0

⇓

User_Cfg_

Data_Not_Okay

Figure 6-8: Coding of User_Cfg_(Not)_Okay_Cmd

6.2.4 Slave_Diag (SAP 60)

Diagnosis Processing Sequence

Two buffers are available for diagnosis. These two buffers can have different lengths. One Diagnosis-Buffer, which is sent on a diagnosis request, is always assigned to the VPC3+C. The user can pre-process new diagnosis data in the other buffer parallel. If the new diagnosis data are to be sent, the user issues the New_Diag_Cmd to make the request to exchange the Diagnosis-Buffers. The user receives confirmation of the buffer exchange with the Diag_Buffer_Changed interrupt.

When the buffers are exchanged, the internal Diag_Flag is also set. For an activated Diag_Flag, the VPC3+C responds during the next



Data_Exchange with high-priority response data. That signals the DP-

Master that new diagnosis data are present at the DP-Slave. The DP-

Master then fetches the new diagnosis data with a Slave_Diag telegram.

Then the Diag_Flag is cleared again. However, if the user signals

‘Diag.Stat_Diag = 1’ (that is static diagnosis, see the structure of the

Diagnosis-Buffer), the Diag_Flag still remains activated after the relevant

DP-Master has fetched the diagnosis. The user can poll the Diag_Flag in the Status Register to find out whether the DP-Master has already fetched the diagnosis data before the old data is exchanged for the new data.

According to IEC 61158, Static Diagnosis should only be used during start-up.

Status coding for the diagnosis buffers is stored in the Diag_Buffer_SM control parameter. The user can read this cell with the possible codings for both buffers: User, VPC3+, or VPC3+_Send_Mode.

Bit Position


7 6 5 4 3 2 1 0

Diag_Buffer_SM, Address 0CH:

bit 7-4

Don’t care:

Read as ‘0’ bit 3-2

Diag_Buf2:

Assignment of Diagnosis Buffer 2

00 = Nil

01 = User

10 = VPC3+

11 = VPC3_Send_Mode bit 1-0

Diag_Buf1:

Assignment of Diagnosis Buffer 1

00 = Nil

01 = User

10 = VPC3+

11 = VPC3_Send_Mode

Figure 6-9: Diagnosis Buffer Assignment

The New_Diag_Cmd is also a read access to a defined control parameter indicating which Diagnosis-Buffer belongs to the user after the exchange or whether both buffers are currently assigned to the VPC3+C (No_Buffer,

Diag_Buf1, Diag_Buf2).



Revision 1.04 45


Address

7 6 5

Bit Position

4 3 2 1

0DH

⇓

Designation

0

⇓

New_Diag_

Buffer_Cmd

Figure 6-10: Coding of New_Diag_Cmd

Byte

7 6 5

Bit Position

4 3 2 1 0

0

Designation

4

5

6

: n

1

2

3 user input

Ext_Diag_Data

(n = max. 243)

Figure 6-11: Format of the Diagnosis-Buffer

The Ext_Diag_Data must be entered into the buffers after the VPC3+C internal diagnosis data. Three different formats are possible here: devicerelated, ID-related and port-related. If PROFIBUS DP extensions shall be used, the device-related diagnosis is substituted by alarm and status messages. In addition to the Ext_Diag_Data, the buffer length also includes the VPC3+C diagnosis bytes (R_Len_Diag_Buf 1, R_Len_Diag_Buf 2).

6.2.5 Write_Read_Data / Data_Exchange (Default_SAP)

Writing Outputs

The VPC3+C writes the received output data in the 'D' buffer. After an error-free receipt, the VPC3+C shifts the newly filled buffer from ‘D’ to ‘N'.

In addition, the DX_Out interrupt is generated. The user now fetches the current output data from ‘N’. The buffer changes from ‘N’ to ‘U’ with the

Next_Dout_Buffer_Cmd, so that the current data can be transmitted to the application by a RD_Output request from a DP-Master.



If the user’s evaluation cycle time is shorter than the bus cycle time, the user does not find any new buffers with the next Next_Dout_Buffer_Cmd in

‘N'. Therefore, the buffer exchange is omitted. At a 12 Mbit/s baud rate, it is more likely, however, that the user’s evaluation cycle time is larger than the bus cycle time. This makes new output data available in ‘N’ several times before the user fetches the next buffer. It is guaranteed, however, that the user receives the data last received.

For power-on, LEAVE-MASTER and the Global_Control telegram with

‘Clear_Data = 1’, the VPC3+C deletes the ‘D’ buffer and then shifts it to ‘N'.

This also takes place during power-up (entering the WAIT-PRM state). If the user fetches this buffer, he receives U_Buffer_Cleared during the

Next_Dout_Buffer_Cmd. If the user is supposed to enlarge the output data buffer after the Chk_Cfg telegram, the user must delete this deviation in the

'N' buffer himself (possible only during the start-up phase in the WAIT-CFG state).

If ‘Diag.Sync_Mode = 1’, the ‘D’ buffer is filled but not exchanged with the

Data_Exchange telegram. It is exchanged at the next Sync or Unsync command sent by Global_Control telegram.

Bit Position


7 6 5 4 3 2 1 0

D Dout_Buffer_SM 0AH F U

Dout_Buffer_SM, Address 0AH:

bit 7-6

F:

Assignment of the F-Buffer

00 = Nil

01 = Dout_Buf_Ptr1

10 = Dout_Buf_Ptr2

11 = Dout_Buf_Ptr3

N bit 5-4

U:

Assignment of the U-Buffer

00 = Nil

01 = Dout_Buf_Ptr1

10 = Dout_Buf_Ptr2

11 = Dout_Buf_Ptr3 bit 3-2

N:

Assignment of the N-Buffer

00 = Nil

01 = Dout_Buf_Ptr1

10 = Dout_Buf_Ptr2

11 = Dout_Buf_Ptr3 bit 1-0

D:

Assignment of the D-Buffer

00 = Nil

01 = Dout_Buf_Ptr1

10 = Dout_Buf_Ptr2

11 = Dout_Buf_Ptr3

Figure 6-12: Dout-Buffer Management



Revision 1.04 47


When reading the Next_Dout_Buffer_Cmd the user gets the information which buffer (‘U’ buffer) belongs to the user after the change, or whether a change has taken place at all.

Bit Position


7 6 5 4 3 2 1 0

Next_Dout_

Buf_Cmd

See coding below

Next_Dout_Buf_Cmd, Address 0BH:

bit 7-4

Don’t care:

Read as ‘0’ bit 3 bit 2

U_Buffer_Cleared:

User-Buffer-Cleared Flag

0 = U buffer contains data

1 = U buffer is cleared

State_U_Buffer:

State of the User-Buffer

0 = no new U buffer

1 = new U buffer bit 1-0

Ind_U_Buffer:

Indicated User-Buffer

01 = Dout_Buf_Ptr1

10 = Dout_Buf_Ptr2

11 = Dout_Buf_Ptr3

Figure 6-13: Coding of Next_Dout_Buf_Cmd

The user must clear the ‘U’ buffer during initialization so that defined

(cleared) data can be sent for a RD_Output telegram before the first data cycle.

Reading Inputs

The VPC3+C sends the input data from the ‘D’ buffer. Prior to sending, the

VPC3+C fetches the Din-Buffer from ‘N’ to ‘D'. If no new buffer is present in

‘N', there is no change.

The user makes the new data available in ‘U’. With the

New_Din_Buffer_Cmd, the buffer changes from ‘U’ to ‘N’. If the user’s preparation cycle time is shorter than the bus cycle time, not all new input data are sent, but just the most current. At a 12 Mbit/s baud rate, it is more likely, however, that the user’s preparation cycle time is larger than the bus cycle time. Then the VPC3+C sends the same data several times in succession.



During start-up, the VPC3+C does not go to DATA-EXCH before all parameter telegrams and configuration telegrams have been acknowledged.

If ‘Diag.Freeze_Mode = 1’, there is no buffer change prior to sending.

The user can read the status of the state machine cell with the following codings for the four states: Nil, Dout_Buf_Ptr1, Dout_Buf_Ptr2 and

Dout_Buf_Ptr3. The pointer for the current data is in the 'N' state.

Bit Position


7 6 5 4 3 2 1 0

08H F U N D Din_Buffer_SM

Din_Buffer_SM, Address 08H:

bit 7-6

F:


00 = Nil

01 = Din_Buf_Ptr1

10 = Din_Buf_Ptr2

11 = Din_Buf_Ptr3 bit 5-4

U:


00 = Nil

01 = Din_Buf_Ptr1

10 = Din_Buf_Ptr2


N:


00 = Nil

01 = Din_Buf_Ptr1

10 = Din_Buf_Ptr2


D:


00 = Nil

01 = Din_Buf_Ptr1

10 = Din_Buf_Ptr2

11 = Din_Buf_Ptr3

Figure 6-14: Din-Buffer Management



Revision 1.04 49


Bit Position

Address

7 6 5 4 3 2 1

09H

⇓

Designation

0

⇓

New_Din_Buf_Cmd

Figure 6-15: Coding of New_Din_Buf_Cmd

User_Watchdog_Timer

After start-up (DATA-EXCH state), it is possible that the VPC3+C continually answers Data_Exchange telegrams without the user fetching the received Dout-Buffers or making new Din-Buffers available. If the user processor ‘hangs up' the DP-Master would not receive this information.

Therefore, a User_Watchdog_Timer is implemented in the VPC3+C.

This User_WD_Timer is an internal 16-bit RAM cell that is started from a user parameterized value R_User_WD_Value and is decremented by the

VPC3+C with each received Data_Exchange telegram. If the timer reaches the value 0000H, the VPC3+C goes to the WAIT-PRM state and the

DP_SM carries out a LEAVE-MASTER. The user must cyclically set this timer to its start value. Therefore, ‘Res_User_WD = 1’ must be set in Mode

Register 1. Upon receipt of the next Data_Exchange telegram, the VPC3+C again loads the User_WD_Timer to the parameterized value

R_User_WD_Value and sets ‘Res_User_WD = 0’ (Mode Register 1).

During power-up, the user must also set ‘Res_User_WD = 1’, so that the

User_WD_Timer is set to its parameterized value.

6.2.6 Global_Control (SAP 58)

The VPC3+C processes the Global_Control telegrams like already described.

The first byte of a valid Global_Control is stored in the R_GC_Command

RAM cell. The second telegram byte (Group_Select) is processed internally.

The interrupt behavior regarding to the reception of a Global_Control telegram can be configured via bit 8 of Mode Register 2. The VPC3+C either generates the New_GC_Control interrupt after each receipt of a

Global_Control telegram (default) or just in case if the Global_Control differs from the previous one.

The R_GC_Command RAM cell is not initialized by the VPC3+C. Therefore the cell has to be preset with 00H during power-up. The user can read and evaluate this cell.



In order to use Sync and Freeze, these functions must be enabled in the

Mode Register 0.

Bit Position


7 6 5 4 3 2 1 0

3CH R_GC_

Command


R_GC_Command, Address 3CH:

bit 7-6

Reserved

bit 5 bit 4 bit 3 bit 2 bit 1

Sync:

The output data transferred with a Data_Exchange telegram is changed from ‘D’ to ‘N’. The following transferred output data is kept in ‘D’ until the next Sync command is given.

Unsync:

The Unsync command cancels the Sync command.

Freeze:

The input data is fetched from ‘N’ to ‘D’ and „frozen“. New input data is not fetched again until the DP-Master sends the next Freeze command.

Unfreeze:

The Unfreeze command cancels the Freeze command.

Clear_Data:

With this command, the output data is deleted in ‘D’ and is changed to ‘N’. bit 0

Reserved

Figure 6-16: Format of the Global_Control Telegram

6.2.7 RD_Input (SAP 56)

The VPC3+C fetches the input data like it does for the Data_Exchange telegram. Prior to sending, ‘N’ is shifted to ‘D', if new input data are available in ‘N'. For ‘Diag.Freeze_Mode = 1', there is no buffer change.

6.2.8 RD_Output (SAP 57)

The VPC3+C fetches the output data from the Dout_Buffer in ‘U’. The user must preset the output data with ‘0’ during start-up so that no invalid data can be sent here. If there is a buffer change from ‘N’ to ‘U’ (through the



Revision 1.04 51


Next_Dout_Buffer_Cmd) between the first call-up and the repetition, the new output data is sent during the repetition.

6.2.9 Get_Cfg (SAP 59)

The user makes the configuration data available in the Read_Config-Buffer.

For a change in the configuration after the Chk_Cfg telegram, the user writes the changed data in the Config-Buffer, sets

‘En_Change_Cfg_buffer = 1’ (see Mode Register 1) and the VPC3+C then exchanges the Config-Buffer for the Read_Config-Buffer. If there is a change in the configuration data during operation (for example, for a modular DP systems), the user must return with Go_Offline command (see

Mode Register 1) to WAIT-PRM.


PROFIBUS DP Extensions

7

7 PROFIBUS DP Extensions

7.1 Set_(Ext_)Prm (SAP 53 / SAP 61)

The PROFIBUS DP extensions require three bytes to implement the new parameterization function. The bits of the Spec_User_Prm_Byte are included.

Bit Position

Byte Designation

7 6 5 4 3 2 1 0

0

:

6

7 DPV1_Status_1

8 0 DPV1_Status_2

9 0 0 Alarm_Mode DPV1_Status_3

10

:

243

User_Prm_Data

Figure 7-1: Set_Prm with DPV1_Status bytes

If the extensions are used, the bit Spec_Clear_Mode in Mode

Register 0 serves as Fail_Safe_required. Therefore it is used for a comparison with the bit Fail_Safe in parameter telegram. Whether the

DP-Master support the Fail_Safe mode or not is indicated by the telegram bit. If the DP-Slave requires Fail_Safe but the DP-Master doesn’t the Prm_Fault bit is set.

If the VPC3+C should be used for DXB, IsoM or redundancy mode, the parameterization data must be packed in a Structured_Prm_Data block to distinguish between the User_Prm_Data. The bit Prm_Structure indicates this.

If redundancy should be supported, the PrmCmd_Supported bit in Mode

Register 0 must be set.



Revision 1.04 53


Byte

0

7 6 5

Bit Position

4 3 2 1 0

Designation

Structured_Length

3

4

:

243

Reserved

User_Prm_Data

Figure 7-2 : Format of the Structured_Prm_Data block

Additional to the Set_Prm telegram (SAP 61) a Set_Ext_Prm (SAP 53) telegram can be used for parameterization. This service is only available in state WAIT-CFG after the reception of a Set_Prm telegram and before the reception of a Chk_Cfg telegram. The new Set_Ext_Prm telegram simply consists of Structured_Prm_Data blocks.

The new service uses the same buffer handling as described by Set_Prm.

By means of the New_Ext_Prm_Data interrupt the user can recognize which kind of telegram is entered in the Parameter-Buffer. Additional the

SAP 53 must be activated by Set_Ext_Prm_Supported bit in Mode Register

0.

The Aux-Buffer for the Set_Ext_Prm is the same as the one for

Set_Prm and have to be different from the Chk_Cfg Aux-Buffer.

Furthermore the Spec_Prm_Buf_Mode in Mode Register 0 must not be used together with SAP 53.

7.2 PROFIBUS DP-V1

7.2.1 Acyclic Communication Relationships

The VPC3+C supports acyclic communication as described in the DP-V1 specification. Therefore a memory area is required which contains all SAPs needed for the communication. The user must do the initialization of this area (SAP-List) in Offline state. Each entry in the SAP-List consists of 7 bytes. The pointer at address 17H contains the segment base address of the first element of the SAP-List. The last element in the list is always indicated with FFH. If the SAP-List shall not be used, the first entry must be

FFH, so the pointer at address 17H must point to a segment base address location that contains FFH.

The new communication features are enabled with DPV1_Enable in the

Set_Prm telegram.


PROFIBUS DP Extensions 7

Byte

7 6 5

Bit Position

4 3 2 1 0

0

1

2

3

Designation

SAP_Number SAP_Number

Request_SA

Request_SSAP

Service_Supported

SAP-List entry:

Byte 0

Response_Sent:

Response-Buffer sent

0 = no Response sent

1 = Response sent

SAP_Number:

0 – 51

Byte 1

Request_SA:

The source address of a request is compared with this value. At differences, the VPC3+C response with “no service activated” (RS). The default value for this entry is 7FH.

Byte 2

Request_SSAP:

The source SAP of a request is compared with this value. At differences, the VPC3+C response with “no service activated” (RS). The default value for this entry is 7FH.

Byte 3

Service_Supported:

Indicates the permitted FDL service.

00 = all FDL services allowed

Byte 4

Ind_Buf_Ptr[0]:

pointer to Indication-Buffer 0

Byte 5

Ind_Buf_Ptr[1]:

pointer to Indication-Buffer 1

Byte 6

Resp_Buf_Ptr:

pointer to Response-Buffer

Figure 7-3: SAP-List entry

In addition an Indication- and Response-Buffer are needed. Each buffer consists of a 4-byte header for the buffer management and a data block of configurable length.



Revision 1.04 55


Byte

7 6 5

Bit Position

4 3 2 1 0

0

Designation

Control

SAP-List entry:

Byte 0

Control:

bits for buffer management

USER buffer assigned to user

INUSE buffer assigned to VPC3+C

Byte 1

Max_Length:

length of buffer

Byte 2

Length:

length of data included in buffer

Byte 3

Function Code:

function code of the telegram

Figure 7-4: Buffer Header

Processing Sequence

A received telegram is compared with the values in the SAP-List. If this check is positive, the telegram is stored in an Indication-Buffer with the

INUSE bit set. In case of any deviations the VPC3+C responses with “no service activated” (RS) or if no free buffer is available with “no resource”

(RR). After finishing the processing of the incoming telegram, the INUSE bit is reset and the bits USER and IND are set by VPC3+C. Now the FDL_Ind interrupt is generated. Polling telegrams do not produce interrupts. The

RESP bit indicates response data, provided by the user in the Response-

Buffer. The Poll_End_Ind interrupt is set after the Response-Buffer is sent.

Also bits RESP and USER are cleared.



DP-Master PROFIBUS DP-Slave

Request to acyclic SAP -> fill

Indication-Buffer

<- short acknowledgement (SC)

Polling telegram to acyclic SAP ->

<- short acknowledgement (SC) process data

:

: update Response-

Buffer

Polling telegram to acyclic SAP ->

<- Response from acyclic

Figure 7-5: acyclic communication sequence

VPC3+C Firmware

set Request_SA / Request_SSA set INUSE in Control of Ind_Buf write data in Ind_Buf clear INUSE and set USER and IND in Control of Ind_Buf set FDL_Ind interrupt clear FDL_Ind interrupt search for Ind_Buf with IND = 1 read Ind_Buf clear IND in Control of Ind_Buf write Response in Resp_Buf set RESP in Control of Resp_Buf check on RESP = 1 read Resp_Buf clear RESP and USER in Control of Resp_Buf set Response_Sent set Poll_End_Ind interrupt clear Poll_End_Ind interrupt search for SAP with Response_Sent = 1 clear Response_Sent

Figure 7-6: FDL-Interface of VPC3+C (e.g. same Buffer for Indication and Response)

7.2.2 Diagnosis Model

The format of the device related diagnosis data depends on the GSD keyword DPV1_Slave in the GSD. If 'DPV1_Slave = 1', alarm and status messages are used in diagnosis telegrams. Status messages are required by the Data eXchange Broadcast service, for example. Alarm_Ack is used as the other acyclic services.



Revision 1.04 57


7.3 PROFIBUS DP-V2

7.3.1 DXB (Data eXchange Broadcast)

The DXB mechanism enables a fast slave-to-slave communication. A DP-

Slave that holds input data significant for other DP-Slaves, works as a

Publisher. The Publisher can handle a special kind of Data_Exchange request from the DP-Master and sends its answer as a broadcast telegram.

Other DP-Slaves that are parameterized as Subscribers can monitor this telegram. A link is opened to the Publisher if the address of the Publisher is registered in the linktable of the Subscriber. If the link have been established correctly, the Subscriber can fetch the input data from the

Publisher.

DP-Master (Class1)

Request (FC=7)

Dout Din

Response (DA=127)

Data Exchange with

DP-Master (Class 1)

Data Exchange with

DP-Master (Class 1) filtered

Broadcast (Input) Data from Publisher

Dout Din

DP-Slave (Publisher)

Dout Din DXBout

DP-Slave (Subscriber)

Link

Figure 7-7 : Overview DXB

The VPC3+C can handle a maximum of 29 links simultaneously.

Publisher

A Publisher is activated with 'Publisher_Enable = 1' in DPV1_Status_1. The time minT

SDR

must be set to 'T

ID1

= 37 t bit

+ 2 T

SET

+ T

QUI

'.

All Data_Exchange telegrams containing the function code 7 (Send and

Request Data Multicast) are responded with destination address 127. If

Publisher mode is not enabled, these requests are ignored.



Subscriber

A Subscriber requires information about the links to its Publishers. These settings are contained in a DXB Linktable or DXB Subscribertable and transferred via the Structured_Prm_Data in a Set_Prm or Set_Ext_Prm telegram. Each Structured_Prm_Data is treated like the User_Prm_Data and therefore evaluated by the user. From the received data the user must generate DXB_Link_Buf and DXB_Status_Buf entries. The watchdog must be enabled to make use of the monitoring mechanism. The user must check this.

Bit Position


7 6 5 4 3 2 1 0

0 Structured_Length

5

6

7

8

9

:

120

Publisher_Addr

Publisher_Length

Sample_Offset

Sample_Length further link entries

Figure 7-8: Format of the Structured_Prm_Data with DXB Linktable

(specific link is grey scaled)



Revision 1.04 59


Byte

0

7 6 5

Bit Position

4 3 2 1 0

Designation

Structured_Length

5

6

7

8

9

10

11

:

120

Publisher_Addr

Publisher_Length

Sample_Offset

Dest_Slot_Number

Offset_Data_Area

Sample_Length further link entries

Figure 7-9: Format of the Structured_Prm_Data with DXB Subscribertable

(specific link is grey scaled)

The user must copy the link entries of DXB Linktable or DXB

Subscribertable, without Dest_Slot_Number and Offset_Data_Area, in the

DXB_Link_Buf and set R_Len_DXB_Link_Buf. Also the user must enter the default status message in DXB_Status_Buf with the received links and write the appropriate values to R_Len_DXB_Status_Buf. After that, the parameterization interrupt can be acknowledged.



Byte

7 6 5

0 0 0

Bit Position

4 3 2 1

Block_Length

0

Designation

Header_Byte

4

5

6

:

61 bit 7

Link_

Status

Link_

Error

0 bit 6 bit 0

0 0 0 0

Publisher_Addr

Data_

Exist

Link_Status

Link_Status:

Link_Status :

1 = active, valid data receipt during last monitoring period

0 = not active, no valid data receipt during last monitoring period (DEFAULT)

Link_Error:

0 = no faulty Broadcast data receipt (DEFAULT)

1 = wrong length, error occurred by reception

Data_Exist:

0 = no correct Broadcast data receipt during current monitoring period

(DEFAULT)

1 = error free reception of Broadcast data during current monitoring period

Figure 7-10: DXB_Link_Status_Buf (specific link is grey scaled)

Processing Sequence

The VPC3+C processes DXBout-Buffers like the Dout-Buffers. The only difference is that the DXBout-Buffers are not cleared by the VPC3+C.

The VPC3+C writes the received and filtered broadcast data in the 'D' buffer. The buffer contains also the Publisher_Address and the

Sample_Length. After error-free receipt, the VPC3+C shifts the newly filled buffer from 'D' to 'N'. In addition, the DXBout interrupt is generated. The user now fetches the current output data from 'N'. The buffer changes from

'N' to 'U' with the Next_DXBout_Buffer_Cmd.



Revision 1.04 61


Byte

7 6 5

Bit Position

4 3 2 1 0

Designation

2

:

246

Sample_Data

Figure 7-11: DXBout-Buffer

When reading the Next_DXBout_buffer_Cmd the user gets the information which buffer ('U' buffer) is assigned to the user after the change, or whether a change has taken place at all.

Bit Position


7 6 5 4 3 2 1 0

D DXBout_Buffer_SM 12H F U N

DXBout_Buffer_SM, Address 0AH:

bit 7-6

F:


00 = Nil

01 = DXBout_Buf_Ptr1


11 = DXBout_Buf_Ptr3 bit 5-4

U:


00 = Nil




N:


00 = Nil




D:


00 = Nil




Figure 7-12: DXBout-Buffer Management



Address

7 6 5

Bit Position

4 3 2 1 0

Designation

Next_DXBout_

Buf_Cmd

See coding below

Next_DXBout_Buf_Cmd, Address 0BH:

bit 7-3

Don’t care:

Read as ‘0’ bit 2

State_U_Buffer:

State of the User-Buffer

0 = no new U buffer

1 = new U buffer bit 1-0

Ind_U_Buffer:

Indicated User-Buffer




Figure 7-13: Coding of Next_DXBout_Buf_Cmd

Monitoring

After receiving the DXB data the Link_Status in DXB_Status_Buf of the concerning Publisher is updated. In case of an error the bit Link_Error is set. If the processing is finished without errors, the bit Data_Exist is set.

In state DATA-EXCH the links are monitored in intervals defined by the parameterized watchdog time. After the monitoring time runs out, the

VPC3+C evaluates the Link_Status of each Publisher and updates the bit

Link_Status. The timer restarts again automatically.

Link_ Link_ Data_

Event

Status Error Exist

valid DXB data receipt 0 1 faulty DXB data receipt

WD_Time elapsed AND Data_Exist = 1

WD_Time elapsed AND Link_Error = 1

0

1

0

1

0

0

0

0

0

Figure 7-14: Link_Status handling

To enable the monitoring of Publisher-Subscriber links the watchdog timer must be enabled in the Set_Prm telegram. The user must check this.



Revision 1.04 63


7.3.2 IsoM (Isochron Mode)

The IsoM synchronizes DP-Master, DP-Slave and DP-Cycle. The isochron cycle time starts with the transmission of the SYNCH telegram by the IsoM master. If the VPC3+C supports the IsoM, a synchronization signal at Pin

13 (XDATAEXCH/SYNC) is generated by each reception of a SYNCH telegram. The SYNCH telegram is a special coded Global_Control request.

SYNCH mesage

Cyclic

Service

. . .

Cyclic

Service

Acyclic

Service

. . .

Acyclic

Service

Token

Spare

Time

SYNCH mesage

Cyclic

Part

Acyclic

Part

Cycle Time (T

DP

)

Figure 7-15: Telegram sequences in IsoM with one DP-Master (Class 1)

Two operation modes for cyclic synchronization are available in the

VPC3+C:

1. Isochron Mode: Each SYNCH telegram causes an impulse on the

SYNC output and a New_GC_Command interrupt.

2. Simple Sync Mode: A Data_Exchange telegram no longer causes a

DX_Out interrupt immediately, rather the event is stored in a flag. By a following SYNCH message reception, the DX_Out interrupt and a synchronization signal are generated at the same time. Additionally a

New_GC_Command interrupt is produced, as the SYNCH telegram behaves like a regular Global_Control telegram to the DP state machine. If no Data_Exchange telegram precedes the SYNCH telegram, only the New_GC_Command interrupt is generated.

Byte

7 6 5

Bit Position

4 3 2 1 0

Designation

1

Group_8

= 1

Group_Select

Figure 7-16: IsoM SYNCH telegram

Each Global_Control is compared with the values that can be adjusted in

Control_Command_Reg (0Eh) and Group_Select_Reg (0Fh). If the values are equal a SYNCH telegram will be detected.



Data_Ex SYNCH SYNCH

Data_Ex

GC SYNCH telegrams

IsoM

SYNC

DX_Out*

New_GC_Command*

Simple Sync Mode

SYNC

DX_Out*

New_GC_Command*

Figure 7-17: SYNC-signal and interrupts for synchronization modes (picture only shows the effects by reception of telegrams; time between telegrams is not equal)

Isochron Mode

To enable the Isochron Mode in the VPC3+C, bit SYNC_Ena in Mode

Register 2 must be set. Additionally the Spec_Clear_Mode in Mode

Register 0 must be set. The polarity of the SYNC signal can be adjusted with the SYNC_Pol bit. The register Sync_PW contains a multiplicator with the base of 1/12

μs to adjust the SYNC pulse width. Settings in the

Set_Prm telegram are shown below.

The Structured_Prm_Data block IsoM (Structure_Type = 4) is also required for the application. If it is sent by Set_Prm telegram the bit

Prm_Structure must be set.



Revision 1.04 65


Byte

7 6 5

Bit Position

4 3 2 1 0

Designation

0 Station_Status

3 minT

SDR

6 Group_Ident

7 DPV1_Status_1

9 DPV1_Status_3

10

:

246

Figure 7-18: Format of Set_Prm telegram for IsoM

User_Prm_Data



DP-Slave in a IsoM network

To enable cyclic synchronization via the ‘Simple Sync Mode', the bit

DX_Int_Port in Mode Register 2 have to be set. Bit SYNC_Ena must not be set. The settings of the pulse polarity are adjusted like described in the

IsoM.

For the parameterization telegram the DP format is used. Though the

DPV1_Status bytes 1-3 could be used as User_Prm_Data, it is generally recommended starting the User_Prm_Data at byte 10.

Bit Position


7 6 5 4 3 2 1 0

0 Station_Status

6 minT

SDR

Group_Ident

10

:

246

User_Prm_Data

Figure 7-19: Format of Set_Prm for DP-Slave using isochrones cycles

In opposite to IsoM the DX_Out interrupt is generated first after the receipt of a SYNCH telegram. If no Data_Exchange telegram had been received before a SYNCH occurred, no synchronization signal is generated.

For this mechanism the interrupt controller ist used. Hence no signal will be generated, if the mask for DX_Out in the IMR is set. Since the synchronization signal is now the DX_Out interrupt, it remains until the interrupt acknowledge.



Revision 1.04 67


Notes:


Hardware Interface

8

8 Hardware Interface

8.1 Universal Processor Bus Interface

8.1.1 Overview

The VPC3+C has a parallel 8-bit interface with an 11-bit address bus. The

VPC3+C supports all 8-bit processors and microcontrollers based on the

80C51/52 (80C32) from Intel, the Motorola HC11 family, as well as 8- /16bit processors or microcontrollers from the Siemens 80C166 family, X86 from Intel and the HC16 and HC916 family from Motorola. Because the data formats from Intel and Motorola are not compatible, VPC3+C automatically carries out ‘byte swapping’ for accesses to the following 16bit registers (Interrupt Register, Status Register and Mode Register 0) and the 16-bit RAM cell (R_User_WD_Value). This makes it possible for a

Motorola processor to read the 16-bit value correctly. Reading or writing takes place, as usual, through two accesses (8-bit data bus).

The Bus Interface Unit (BIU) and the Dual Port RAM Controller (DPC) that controls accesses to the internal RAM belong to the processor interface of the VPC3+C.

The VPC3+C is supplied with a clock pulse rate of 48MHz. In addition, a clock divider is integrated. The clock pulse is divided by 2 (Pin: DIVIDER =

'1') or 4 (Pin: DIVIDER = '0') and applied to the pin CLKOUT 2/4. This allows the connection of a slower controller without additional expenditures in a low-cost application.

8.1.2 Bus Interface Unit

The Bus Interface Unit (BIU) is the interface to the connected processor/microcontroller. This is a synchronous or asynchronous 8-bit interface with an 11-bit (12-bit in 4K Byte mode) address bus. The interface is configurable via 2 pins (XINT/MOT, MODE). The connected processor family (bus control signals such as XWR, XRD, or R_W and the data format) is specified with the XINT/MOT pin. Synchronous or asynchronous bus timing is specified with the MODE pin.

XINT/MOT MODE Processor Interface Mode

0 1 Synchronous Intel mode

0 0 Asynchronous Intel mode

1

1

0

1

Asynchronous Motorola mode

Synchronous Motorola mode

Figure 8-1: Configuration of the Processor Interface

Examples of various Intel system configurations are given in subsequent sections. The internal address latch and the integrated decoder must be

Revision 1.04 69




used in the synchronous Intel mode. One figure shows the minimum configuration of a system with the VPC3+C, where the chip is connected to an

EPROM version of the controller. Only a clock generator is necessary as an additional device in this configuration. If a controller is to be used without an integrated program memory, the addresses must be latched for the external memory.

Notes:

If the VPC3+C is connected to an 80286 or similar processor, it must be taken into consideration that the processor carries out word accesses. That is, either a ‘swapper’ is necessary that switches the characters out of the

VPC3+C at the correct byte position of the 16-bit data bus during reading or the least significant address bit is not connected and the 80286 must read word accesses and evaluate only the lower byte.

Name

Input/

Output

Type Comments

AB(10..0) I

MODE I

XWR/E_CLOCK

AB11

AB(10) has a pull down resistor.

Intel: Write Sync. Motorola: E-Clk

AB11 (Asynchronous Motorola Mode)

XCS

AB11

ALE/AS

AB11

DIVIDER I

Chip Select

AB11 (Synchronous Intel Mode)

AB11 (Async. Intel / Sync. Motorola Mode)

Scaling factor 2/4 for CLKOUT 2/4

XRDY/XDTACK O Push/Pull * Intel/Motorola: Ready-Signal

CLK I

RESET I Schmitt-Trigger Minimum of 4 clock cycles

Figure 8-2: Microprocessor Bus Signals

* Due to compatibility reasons to existing competitive chips the XRDY/XDTACK output of the

VPC3+C has push/pull characteristic (no tristate!).


Hardware Interface 8

Synchronous Intel Mode

In this mode Intel CPUs like 80C51/52/32 and compatible processor series from several manufacturers can be used.

Synchronous bus timing without evaluation of the XREADY signal

8-bit multiplexed bus: ADB7..0

The lower address bits AB7..0 are stored with the ALE signal in an internal address latch.

The internal CS decoder is activated. VPC3+C generates its own CS signal from the address lines AB10..3. The VPC3+C selects the relevant address window from the AB2..0 signals.

A11 from the microcontroller must be connected to XCS (pin 1) in 4K

Byte mode as this is the additional address bus signal in this mode. In

2K Byte mode this pin is not used and should be pulled to VDD.

Asynchronous Intel Mode

In this mode various 16-/8-bit microcontroller series like Intel’s x86,

Siemens 80C16x or compatible series from other manufacturers can be used.

Asynchronous bus timing with evaluation of the XREADY signal

8-bit non-multiplexed bus: DB7..0, AB10..0 (AB11..0 in 4K Byte mode)

The internal VPC3+C address decoder is disabled, the XCS input is used instead.

External address decoding is always necessary.

External chip select logic is necessary if not present in the microcontroller

A11 from the microcontroller must be connected to ALE/AS (pin 24) in

4K Byte mode as this is the additional address bus signal in this mode.

In 2K Byte mode this pin is not used and should be pulled to GND.

Asynchronous Motorola Mode

Motorola microcontrollers like the HC16 and HC916 can be used in this mode. When using HC11 types with a multiplexed bus the address signals

AB7..0 must be generated from the DB7..0 signals externally.

Asynchronous bus timing with evaluation of the XREADY signal

8-bit non-multiplexed bus: DB7..0, (AB11..0 in 4K Byte mode)


Chip select logic is available and programmable in all microcontrollers mentioned above.

AB11 must be connected to XWR/E_CLOCK (pin 2) in 4K Byte mode as this is the additional address bus signal in this mode. In 2K Byte mode this pin is not used and should be pulled to GND.



Revision 1.04 71


Synchronous Motorola Mode

Motorola microcontrollers like the HC11 types K, N, M, F1 or the HC16- and

HC916 types with programmable E_Clock timing can be used in this mode.

When using HC11 types with a multiplexed bus the address signals AB7..0 must be generated from the DB7..0 signals externally.

Synchronous bus timing without evaluation of the XREADY signal

8-bit non-multiplexed bus: DB7..0, AB10..0 (AB11..0 in 4K Byte mode)


For microcontrollers with chip select logic (K, F1, HC16 and HC916), the chip select signals are programmable regarding address range, priority, polarity and window width in the write cycle or read cycle.

For microcontrollers without chip select logic (N and M) and others, an external chip select logic is required. This means additional hardware and a fixed assignment.

If the CPU is clocked by the VPC3+C, the output clock pulse (CLKOUT

2/4) must be 4 times larger than the E_Clock. That is, a clock pulse signal must be present at the CLK input that is at least 10 times larger than the desired system clock pulse (E_Clock). The Divider-Pin must be connected to ‘0’ (divider 4). This results in an E_Clock of 3 MHz.

AB11 must be connected to ALE/AS (pin 24) in 4K Byte mode as this is the additional address bus signal in this mode. In 2K Byte mode this pin is not used and should be pulled to GND.



8.1.3 Application Examples (Principles)

CLK

WR

RD

INT 0

80C 32/

C501

Por t 0

ALE

Por t 2

A / D 7 ...0

AB 1 5...8

(0000 0XXX)

Clock-Generator

48MHz

DIVIDE R

XW R

XRD

X/INT

Clockdivider

RT S

TxD

DB 7..0

Data

DB 7..0

Address-Latch

Rx D

XC TS

AB 7 ..0

Decoder

VPC3+

1K

GND

AB8

AB9

AB10

Mode

VPC3+

Reset

Reset

1K 1K 1K

GND

3K 3

VDD

Figure 8-3: Low Cost System with 80C32

CLK

WR

RD

INT0

80C 32

20/16 MHz

ALE

PSEN

Address-

Latch

Clock-Generator

48 MHz

DIVIDER

XW R

XRD

X/INT

Clockdivider

RT S

TxD

DB 7..0

Data

DB 7..0

Address-Latch

Rx D

XC TS

VPC3+

1K

GND

Po rt 0

A/D 7..0

Por t 2

AB 15..8

(0000 0XXX)

Reset

AB 15..0

EPROM

64kB

RAM

32kB

RD W R

Address-

Decoder

Figure 8-4: 80C32 System with External Memory

1K 1K 1K

AB8

AB9

AB10

Mode

3K 3

VPC3+

Reset

GND VDD



Revision 1.04 73


CLK

WR

RD

INT R

80286

+

Buscontr.

(82288) +

82244

Readylogic

DB

DB 15..0

AB

Reset

DB 7..0

AB 23..0

RD WR

AB 12..1

driver, control logic

EPROM

64kB

RAM

32kB

CSRAM

CSEPROM address decoder

CS

12/24 MHz

Clockgenerator

48 MHz

DIVIDER

XWR

XRD

X/INT clockdivider

RTS

TxD

XREADY

RxD

XCTS

DB(7..0)

VPC3+

1K

AB(10..0)

GND

XCS Mode

VPC3+

Reset

3K3

GND

Figure 8-5: 80286 System (X86 Mode)



8.1.4 Application with 80C32 (2K Byte RAM Mode)

VPC3+

5

48 MHz

CLK

GND

1K

µC

VDD

VDD

3K3

3K3

µC

µC

µC

XWR

XRD

AB(15..8)

µC

VDD 3K3

VDD 3K3 connect to

VDD or GND

AB8

AB9

AB10

AB11

AB12

AB13

AB14

AB15

1

GND

1K

1K

1K

AB5

AB6

AB7

AB8

AB9

AB10

AB0

AB1

AB2

AB3

AB4

40

37

42

32

44

43

41

31

29

25

10

2

4

23

24

8

36

1

34

35

3

XINT/MOT

RESET

XCS

MODE

ALE

XWR

XRD

XTEST0

XTEST1

DIVIDER

CLK2

XDATAEX

XREADY

7

13

14

X/INT

9

XCTS

33

RXD

RTS

TXD

30

27

26

DB0

DB1

DB2

DB3

DB4

DB5

DB6

DB7

19

20

21

22

11

12

15

16

LED for Data_Exchange

1K

ADB0

ADB1

ADB2

ADB3

ADB4

ADB5

ADB6

ADB7

µC

GND

RS485

RS485

RS485

µC

DB(7..0)

Figure 8-6: 80C32 Application in 2K Byte mode

The internal chipselect is activated when the address inputs AB[10..3] of the VPC3+C are set to '0'.

In the example above the start address of the VPC3+C is set to 1000H.

Processor VPC3+ B

ALE

ALE

AD[7..0]

AB[10..8]

8

3

DB[7..0]

AB[2..0] address latch

8

11 internal address

4.0 KB

RAM

AB[15..11]

5

3

AB[7..3]

AB[10..8]

8 all bits zero

CS decoder

1 internal chip select

Figure 8-7: Internal Chipselect Generation in Synchronous Intel Mode, 2K Byte RAM



Revision 1.04 75


8.1.5 Application with 80C32 (4K Byte RAM Mode)

VPC3+

5

48 MHz

CLK

µC

GND

1K

8

36

XINT/MOT

RESET

CLK2

XDATAEX

XREADY

7

13

14

VDD

3K3

µC

µC

µC

XWR

XRD

VDD 3K3

VDD 3K3 connect to VDD or GND

AB8

AB9

AB10

AB11

AB12

AB13

AB14

AB15

1

AB(15..8)

µC

GND

1K

1K

1K

1K

MODE

ALE

XWR

XRD

XTEST0

XTEST1

DIVIDER

AB3

AB4

AB5

AB6

AB7

AB0

AB1

AB2

XCS/AB11

AB8

AB9

AB10

23

24

2

4

34

35

3

44

43

41

1

40

37

42

32

31

29

25

10

X/INT

9

XCTS

33

RXD

RTS

TXD

30

27

26

DB4

DB5

DB6

DB7

DB0

DB1

DB2

DB3

16

19

20

21

22

11

12

15


1K

ADB0

ADB1

ADB2

ADB3

ADB4

ADB5

ADB6

ADB7

µC

GND

RS485

RS485

RS485

µC

DB(7..0)

Figure 8-8: 80C32 Application in 4K Byte mode

The internal chipselect is activated when the address inputs AB[10..3] of the VPC3+C are set to '0'.

In the example above the start address of the VPC3+C is set to 2000H.

Processor VPC3+ B

ALE

ALE

AD[7..0]

AB[10..8]

AB[11]

AB[15..12]

8

3

4

4

DB[7..0]

AB[2..0]

XCS/A11

AB[6..3]

AB[10..7] address latch

8

12 internal address

8 all bits zero

CS decoder

1 internal chip select

4.0 KB

RAM

Figure 8-9 : Internal Chipselect Generation in Synchronous Intel Mode, 4K Byte RAM



8.1.6 Application with 80C165

GND

1K

µC

µC

GND

µC

µC

GND

XWRL

XRD

1K

1K

VDD 3K3

VDD 3K3 connect to

VDD or GND

AB0

AB1

AB2

AB3

AB4

AB5

AB6

AB7

AB8

AB9

AB10

48 MHz

VPC3+

5

CLK

AB0

AB1

AB2

AB3

AB4

AB5

AB6

AB7

AB8

AB9

AB10

37

42

32

44

43

41

40

31

29

25

10

24

2

4

8

36

1

23

34

35

3

XINT/MOT

RESET

XCS

MODE

ALE

XWR

XRD

XTEST0

XTEST1

DIVIDER

µC

AB(10..0)

Figure 8-10: 80C165 Application

CLK2

XDATAEX

XREADY

7

13

14

X/INT

9

XCTS

33

RXD

RTS

TXD

30

27

26

DB0

DB1

DB2

DB3

DB4

DB5

DB6

DB7

16

19

20

21

22

11

12

15


µC

µC

1K

DB0

DB1

DB2

DB3

DB4

DB5

DB6

DB7

GND

RS485

RS485

RS485

µC

DB(7..0)

8.2 Dual Port RAM Controller

The internal 4K Byte RAM of the VPC3+C is a single-port RAM. An integrated Dual-Port RAM controller, however, permits an almost simultaneous access of both ports (bus interface and microsequencer interface). When there is a simultaneous access of both ports, the bus interface has priority. This guarantees the shortest possible access time. If the VPC3+C is connected to a microcontroller with an asynchronous interface, the controller can evaluate the Ready signal.



Revision 1.04 77


8.3 UART

The transmitter converts the parallel data structure into a serial data flow.

Signal Request-to-Send (RTS) is generated before the first character. The

XCTS input is available for connecting a modem. After RTS active, the transmitter must hold back the first telegram character until the modem activates XCTS. XCTS is checked again after each character.

The receiver converts the serial data flow into the parallel data structure and scans the serial data flow with the four-fold transmission speed. Stop bit testing can be switched off for test purposes ('Dis_Stop_Control = 1' in

Mode Register 0 or Set_Prm telegram for DP). One requirement of the

PROFIBUS protocol is that no rest states are permitted between the telegram characters. The VPC3+C transmitter ensures that this specification is maintained.

The synchronization of the receiver starts with the falling edge of the start bit. The start bit is checked again in the middle of the bit-time for low level.

The data bits, the parity and the stop bit are also scanned in the middle of the bit-time. To compensate for the synchronization error, a repeater generates a

±25% distortion of the stop bit at a four-fold scan rate. In this case the VPC3+ should be parameterized with 'Dis_Start_Control = 1' (in Mode

Register 0 or Set_Prm telegram for DP) in order to increase the permissible distortion of the stop bit.

8.4 ASIC Test

All output pins and I/O pins can be switched to the high-resistance state via the XTEST0 test pin. An additional XTEST1 input is provided to test the chip on automatic test devices (not in the target hardware environment!).

Pin Name Value Function

VSS (GND) All outputs high-resistance

34 XTEST0

VDD Normal VPC3+ function

VSS (GND) Various test modes

35 XTEST1

VDD Normal VPC3+ function

Figure 8-11: Test Ports


PROFIBUS Interface

9

9 PROFIBUS Interface

9.1 Pin Assignment

The data transmission is performed in RS485 operating mode (i.e., physical

RS485). The VPC3+C is connected via the following signals to the galvanically isolated interface drivers.

Signal Name Input/Output Function

RTS Output Request to send

Figure 9-1: PROFIBUS Signals

The PROFIBUS interface is a 9-way, sub D, plug connector with the following pin assignment.

Pin 1 - Free

Pin 2 - Free

Pin 3 - B line

Pin 4 - Request to send (RTS)

Pin 5 - Ground 5V (M 5 )

Pin 6 - Potential 5V (floating P5 )

Pin 7 - Free

Pin 8 - A line

Pin 9 - Free

The cable shield must be connected to the plug connector housing.

The free pins are described as optional in IEC 61158-2.

CAUTION:

The pin names A and B on the plug connector refer to the signal names in the RS485 standard and not the pin names of driver ICs.

Keep the wires from driver to connector as short as possible.



Revision 1.04 79

9 PROFIBUS Interface

9.2 Example for the RS485 Interface

To minimize the capacity of the bus lines the user should avoid additional capacities. The typical capacity of a bus station should be 15...25 pF.

1

R4 100K

2 1

R3 100K

2

5 3

1

1

2

2

2 1

1 2

R RE

1 2

7 6

1

R9 22K

2

NC VO

Figure 9-2: Example for the RS485 Interface


Operational Specifications

10

10 Operational Specifications

10.1 Absolute Maximum Ratings

Parameter

DC supply voltage

Input voltage

Output voltage

DC output current

Storage temperature

Symbol Limits

VDD

V

I

V

O

-0.3 to 6.0

-0.3 to VDD +0.3

-0.3 to VDD +0.3

T

I

O

See

store

-40 to +125

Figure 10-1: Absolute Maximum Ratings

Unit

V

V

V mA

°C

10.2 Recommended Operating Conditions

Parameter Symbol MIN MAX Unit

DC supply voltage

Static supply current

Circuit ground

Input voltage

Input voltage (HIGH level)

Input voltage (LOW level)

V

DD

3.00 5.50

I

DD

100

1)

µA

V

SS

V

I

0 5.50

V

IH

V

IL

Output voltage

Ambient temperature

V

O

0 V

DD

V

T

A

-40 +85

1)

: Static I

DD

current is exclusively of input/output drive requirements and is measured with the clock stopped and all inputs tied to V

DD

or V

SS

.

Figure 10-2: Recommended Operating Conditions

10.3 General DC Characteristics

Parameter

Input LOW current

Input HIGH current

Tri-state leakage current

Current consumption (3.3V)

Current consumption (5V)

Input capacitance

Output capacitance

Bi-directional buffer capacitance

Symbol MIN TYP MAX Unit

I

IL

-1

I

IH

-1

I

OZ

-10

I

A

45 mA

I

A

90 mA

C

IN

5

C

OUT

5 pF pF

C

BID

5 pF

Figure 10-3: General DC Characteristics

81



Revision 1.04


10.4 Ratings for the Output Drivers

Signal

DB 0-7

Direction

I/O

Driver

Type

Tristate

Driver Strength

8mA

Max. Cap.

Load

100pF

XREADY/XDTACK O Push/Pull 4mA 50pF

XDATAEXCH O 8mA 50pF

Figure 10-4: Ratings for the Output Drivers

10.5 DC Electrical Characteristics Specification for 5V Operation

Parameter

DC supply voltage

CMOS input voltage LOW level

CMOS input voltage HIGH level

Output voltage LOW level

Output voltage HIGH level

CMOS Schmitt Trigger negative going threshold voltage

CMOS Schmitt Trigger positive going threshold voltage

TTL Schmitt Trigger negative going threshold voltage

TTL Schmitt Trigger positive going threshold voltage

Input LOW current

Input HIGH current


Output current LOW level, 4mA cell

Output current HIGH level, 4mA cell




V

CC

4.50 5.00 5.50 V

V

ILC

V

IHC

0.7 V

DD

V

V

OL

0.4 V

V

OH

3.5 V

V

T-

1.5 1.8 V

V

T+

V

T-

0.9 1.1 V

V

T+

1.9

I

IL

-1 +1 µA

I

IH

-1 +1 µA

I

OZ

-10 ±1 +10 µA

I

OL

4.0 mA

I

OH

-4.0 mA

I

OL

8.0 mA

I

OH

-8.0 mA

Figure 10-5: DC Specification of I/O Drivers for 5V Operation


Operational Specifications 10

10.6 DC Electrical Characteristics Specification for 3.3V Operation

Parameter

DC supply voltage

CMOS input voltage LOW level

CMOS input voltage HIGH level

Output voltage LOW level

Output voltage HIGH level

CMOS Schmitt Trigger negative going threshold voltage

CMOS Schmitt Trigger positive going threshold voltage

TTL Schmitt Trigger negative going threshold voltage

TTL Schmitt Trigger positive going threshold voltage

Input LOW current

Input HIGH current







V

CC

3.00 3.30 3.60 V

V

ILC

V

IHC

0.7 5.50 V

V

OL

0.4 V

V

OH

2.4 V

V

T-

0.8 V

V

T+

2.7 V

V

T-

0.6 V

V

T+

1.7 V

I

IL

-1 +1 µA

I

IH

-1 +1 µA

I

OZ

-10 ±1 +10 µA

I

OL

+2.8 mA

I

OH

-2.8 mA

I

OL

+5.6 mA

I

OH

-5.6 mA

Figure 10-6: DC Specification of I/O Drivers for 3.3V Operation

Notes:

For 3.3V operation the VPC3+C is equipped with 5V tolerant inputs except for the clock pin CLK. When using 3.3V supply voltage the clock input needs to be 3.3V level.

For 3.3V operation the guaranteed minimum output current is 70% of that for 5V operation mode.



Revision 1.04 83


10.7 Timing Characteristics

All signals beginning with ‘X’ are ‘low active’. All timing values are based on the capacitive loads specified in the table above.

10.7.1 System Bus Interface

Clock

Clock frequency is 48 MHz. Distortion of the clock signal is permissible up to a ratio of 30:70 at the threshold levels 0.9 V and 2.1 V.

Parameter Symbol MIN MAX Unit

Clock period

Clock high time

Clock low time

Clock rise time

Clock fall time

T 20.83 20.83

T

CH

T

CL

6.25

T

CR

4

T

CF

4

Figure 10-7: Clock Timing

Note:

For 3.3V operation the VPC3+C is equipped with 5V tolerant inputs except for the clock pin CLK. When using 3.3V supply voltage the clock input needs to be 3.3V level.

Interrupt:

After acknowledging an interrupt with EOI, the interrupt output of the

VPC3+C is deactivated for at least 1 us or 1 ms depending on the bit

EOI_Time_Base in Mode Register 0.

Parameter MIN MAX Unit

Interrupt inactive time EOI_Timebase = ‘0’

Interrupt inactive time EOI_Timebase = ‘1’

1

1

1

1

µs ms

Figure 10-8: End-of-Interrupt Timing

Reset:

VPC3+C requires a minimum reset phase of 100 ns at power-on.



10.7.2 Timing in the Synchronous Intel Mode

In the synchronous Intel mode, the VPC3+C latches the least significant addresses with the falling edge of ALE. At the same time, the VPC3+C expects the most significant address bits on the address bus. An internal chipselect signal is generated from the most significant address bits. The request for an access to the VPC3+C is generated from the falling edge of the read signal (XRD) and from the rising edge of the write signal (XWR).

1 7

ALE 5

AB10..0

DB7..0

3 valid

4 address

2 data valid

9

8 valid address

XRD

6

ALE

AB10..0

DB7..0

XWR

Figure 10-9: Synchronous Intel Mode, READ (XWR = 1)

1

10

14

11

3 valid

15 address

12 data valid

13

15

8

10

Figure 10-10: Synchronous Intel Mode, WRITE (XRD = 1)

valid address



Revision 1.04 85


No. Parameter

V

DD

= 3.3 V

MIN MAX

2 ALE

↓ to XRD ↓

3

Address to ALE

↓ setuptime

4 Address holdtime after ALE

↓

5 XRD

↓ to data valid

7

XRD

↑ to ALE ↑

8 address (AB7..0) holdtime after XRD/XWR

↑

9 data holdtime after XRD

↑

10 XRD / XWR cycletime

11 ALE

↓ to XWR ↓

155

13 data setuptime to XWR

↑

14

XWR

↑ to ALE ↑

15 data holdtime after XWR

↑

Figure 10-11: Timing, Synchronous Intel Mode

V

DD

= 5 V

MIN MAX

Unit

155 ns



10.7.3 Timing in the Asynchronous Intel Mode

In the asynchronous Intel mode, the VPC3+C acts like a memory with ready logic. The access time depends on the type of access. The request for an access to the VPC3+C is generated from the falling edge of the read signal (XRD) or the rising edge of the write signal (XWR).

The VPC3+C generates the Ready signal synchronously to the system clock. The Ready signal gets inactive when the read or the write signal is deactivated. The data bus is switched to Tristate with XRD = '1'.

AB10..0

valid

16

23

DB7..0

data valid

17

24

XRD

18 25

19

XCS

26

XREADY

(normal)

XREADY

(early)

21

20

22

Figure 10-12: Asynchronous Intel Mode, READ (XWR = 1)

27



Revision 1.04 87


AB10..0

valid

16

DB7..0

23 data valid

28 30

XWR

29 25

19

XCS

26

XREADY

(normal)

21

20

XREADY

(early)

27

22

Figure 10-13: Asynchronous Intel Mode, WRITE (XRD = 1)

VDD = 3.3 V

MIN MAX No. Parameter

16 address-setuptime to XRD / XWR

↓

17

XRD

↓ to data valid

VDD = 5 V

MIN MAX Unit

19 XCS

↓ setuptime to XRD / XWR ↓

20

XRD

↓ to XREADY ↓ (Normal-Ready)

21 XRD

↓ to XREADY ↓ (Early-Ready)

22 XRD / XWR cycletime

23 address holdtime after XRD / XWR

↑

24 data holdtime after XRD

↑

25 read/write inactive time

26 XCS holdtime after XRD / XWR

↑

27 XREADY holdtime after XRD / XWR

28 data setuptime to XWR

↑

125

10

6

30 data holdtime after XWR

↑

Figure 10-14: Timing, Asynchronous Intel Mode

21

125

10

5 16 ns ns ns



10.7.4 Timing in the Synchronous Motorola Mode

If the CPU is clocked by the VPC3+C, the output clock pulse (CLKOUT 2/4) must be 4 times larger than the E_Clock. That is, a clock pulse signal must be present at the CLK input that is at least 10 times larger than the desired system clock pulse (E_Clock). The Divider-Pin must be connected to ‘0’

(divider 4). This results in an E_Clock of 3 MHz.

The request for a read access to the VPC3+C is derived from the rising edge of the E_Clock (in addition: XCS = 0, R_W = 1). The request for a write access is derived from the falling edge of the E_Clock (in addition:

XCS = 0, R_W = 0).

31

E_CLOCK

33

32 37

AB10..0

valid

38

DB7..0

data valid

R_W

39

35

XCS

36

Figure 10-15: Synchronous Motorola-Mode, READ (AS = 1)

40



Revision 1.04 89


31

E_CLOCK

AB10..0

33 valid

37

DB7..0

41 data valid

42

R_W

39

35

XCS

36 40

No.

Figure 10-16: Synchronous Motorola-Mode, WRITE (AS = 1)

Parameter

VDD = 3.3 V

MIN MAX

136.7

VDD = 5 V

MIN MAX

136.7 31 E_Clock pulse width

33

Address setuptime (A10..0) to E_Clock

↑

37 Address holdtime after E_Clock

↓

32 E_Clock

↑ to Data valid

38

Data holdtime after E_Clock

↓

35

R_W setuptime to E_Clock

↑

39 R_W holdtime after E_Clock

↓

36

XCS setuptime to E_Clock

↑

40

XCS holdtime after E_Clock

↓

41 Data setuptime to E_Clock

↓

42 Data holdtime after E_Clock

↓

Figure 10-17: Timing, Synchronous Motorola Mode

Unit

ns



10.7.5 Timing in the Asynchronous Motorola Mode

In the asynchronous Motorola mode, the VPC3+C acts like a memory with

Ready logic, whereby the access times depend on the type of access.

The request for an access of the VPC3+C is generated from the falling edge of the AS signal (in addition: XCS = '0', R_W = '1'). The request for a write access is generated from the rising edge of the AS signal (in addition:

XCS = '0', R_W = '0').

AB10..0

valid

43 52

DB7..0

data valid

44

53

AS

45 54

R_W

46 55

XCS

47 56

XDTACK

(normal)

48

49

XDTACK

(early)

57

50

51

Figure 10-18: Asynchronous Motorola Mode, READ (E_CLOCK = 0)



Revision 1.04 91


AB10..0

valid

43

DB7..0

AS

59

R_W

46 data valid

58

XCS

47

XDTACK

(normal)

49

48

XDTACK

(early)

50

51

Figure 10-19: Asynchronous Motorola Mode (WRITE)

56

55

57

52

60

54



No. Parameter

43 address setuptime to AS

↓

44 AS

↓ to data valid

45 AS pulsewidth (read access)

46 R_W

↓ setuptime to AS ↓

47 XCS

↓ setuptime to AS ↓

48

AS

↓ to XDTACK ↓ (Normal-Ready)

49

AS

↓ to XDTACK ↓ (Early-Ready)

50 last AS

↓ to XCS ↓

VDD = 3.3 V

MIN MAX

115

52 address holdtime after AS

↑

53 Data holdtime after AS

↑

54 AS inactive time

55

R_W holdtime after AS

↑

56

XCS holdtime after AS

↑

57 XDTACK holdtime after AS

↑

58 Data setuptime to AS

↑

59 AS pulsewidth (write access)

60 Data holdtime after AS

↑

10

83

Figure 10-20: Timing, Asynchronous Motorola Mode

VDD = 5 V

MIN MAX

Unit

115

10

83 ns ns ns



Revision 1.04 93


10.8 Package

Figure 10-21: Package Drawing



SYMBOL

MILLIMETER INCH

MIN NOM MAX MIN NOM MAX

A ─── ─── 2.45 ─── ─── 0.096

A1 0.15 0.25 0.35 0.006 0.010 0.014

A2 1.95 2.05 2.10 0.077 0.081 0.083

D

D1

E

E1

13.90 BASIC

10.00 BASIC

13.90 BASIC

10.00 BASIC

0.547 BASIC

0.394 BASIC

0.547 BASIC

0.394 BASIC

R1 0.13 ─── 0.005 ─── ───

Θ 0° 3.5° 7° 0° 3.5° 7°

Θ1 0° ─── 0° ─── ───

Θ2

Θ3

10° REF

7° REF

10° REF

7° REF c 0.11 0.15 0.23 0.004 0.006 0.009

L 0.73 0.88 1.03 0.029 0.035 0.041

L1 1.95 REF 0.077 REF

S 0.40 ─── 0.016 ─── ─── b 0.22 0.30 0.38 0.009 0.012 0.015 e 0.80 BSC. 0.031 BSC.

D2 8.0 0.315

E2 8.0

Tolerances of Form and Position

0.315 aaa 0.25 bbb 0.20

0.010

0.008 ccc 0.20 0.008

Figure 10-22 : Package Dimensions and Tolerances

Notes:

1. Dimensions D1 and E1 do not include mold protrusion. Allowable protrusion is 0.25 mm per side. Dimensions D1 and E1 do not include mold mismatch and are determined at datum plane ─H─.

2. Dimension b does not include dambar protrusion. Allowable dambar protrusion shall be 0.08 mm total in excess of the b dimension at maximum material condition. Dambar cannot be located on the lower radius of the lead foot.



Revision 1.04 95


10.9 Processing Instructions

Generally, ESD protective measures must be maintained for all electronic components. The VPC3+C is a cracking-endangered component that must be properly handled.

A drying process must be carried out before the VPC3+C is processed. The component must be dried for 24 hours at 125°C and then processed within

48 hours. Due to the solderability of the component this drying process may be carried out once only.

10.10 Ordering Information

Order Code Package Operation Range

PA002003 PQFP44 Industrial

(-40°C to +85°C)

PALF2003 PQFP44 Industrial

(-40°C to +85°C)

Notes

End of Lifetime

RoHS compliant


Revision History

Version Date Page Remarks

V1.00 10.05.2004 First

V1.01 18.07.2004 Re-formatting and correction of typing errors

V1.02 22.09.2004

V1.03 12.01.2006

54

80

85

Some minor corrections

Consecutive paging

Additional figures for FDL-Interface

Figure 9-2 updated

Figure 10-10 revised

V1.04 19.03.2007 62

63

96

Figure 7-12 revised

Figure 7-13 revised

Ordering Information added



Revision 1.04 97

profichip GmbH

Einsteinstrasse 6

91074 Herzogenaurach

Germany

Phone : +49.9132.744-200

Fax: +49.9132.744-204 www.profichip.com

Th e Cl e ve r Al t e r n a t i ve

VPC3+C User Manual Revision 1.04

VPC3+C

User Manual

Table of Contents

Introduction

Notes:

Functional Description

2.1 Overview

Pin Description

3.1 Pin Assignment

4K Byte RAM extension

3.2 Pinout

Notes:

Memory Organization

4.1 Overview

4.2 Control Parameters (Latches/Registers)

4.3 Organizational Parameters (RAM)

ASIC Interface

5.1 Mode Registers

5.1.1 Mode Register 0

5.1.2 Mode Register 1

5.1.3 Mode Register 2

5.2 Status Register

5.3 Interrupt Controller

Σ

5.3.1 Interrupt Request Register

5.3.2 Interrupt Acknowledge / Mask Register

5.4 Watchdog Timer

5.4.1 Automatic Baud Rate Identification

5.4.2 Baud Rate Monitoring

5.4.3 Response Time Monitoring

Notes:

PROFIBUS DP Interface

6.1 DP Buffer Structure

6.2 Description of the DP Services

6.2.1 Set_Slave_Add (SAP 55)

Sequence for the Set_Slave_Add service

Structure of the Set_Slave_Add Telegram

6.2.2 Set _Prm (SAP 61)

Parameter Data Structure

Parameter Data Processing Sequence

6.2.3 Chk_Cfg (SAP 62)

6.2.4 Slave_Diag (SAP 60)

Diagnosis Processing Sequence

6.2.5 Write_Read_Data / Data_Exchange (Default_SAP)

Writing Outputs

Reading Inputs

User_Watchdog_Timer

6.2.6 Global_Control (SAP 58)

6.2.7 RD_Input (SAP 56)

6.2.8 RD_Output (SAP 57)

6.2.9 Get_Cfg (SAP 59)

PROFIBUS DP Extensions

7.1 Set_(Ext_)Prm (SAP 53 / SAP 61)

7.2 PROFIBUS DP-V1

7.2.1 Acyclic Communication Relationships

Processing Sequence

7.2.2 Diagnosis Model

7.3 PROFIBUS DP-V2

7.3.1 DXB (Data eXchange Broadcast)

Publisher

Subscriber

Processing Sequence

Monitoring

7.3.2 IsoM (Isochron Mode)

Isochron Mode

DP-Slave in a IsoM network

Notes:

Hardware Interface

8.1 Universal Processor Bus Interface

8.1.1 Overview

8.1.2 Bus Interface Unit

Synchronous Intel Mode

Asynchronous Intel Mode

Asynchronous Motorola Mode

Synchronous Motorola Mode

8.1.3 Application Examples (Principles)

8.1.4 Application with 80C32 (2K Byte RAM Mode)

8.1.5 Application with 80C32 (4K Byte RAM Mode)

8.1.6 Application with 80C165