853 profibus manual

7/28/2019 853 Profibus Manual

1/50

May 2005


2/50

Safety Information in this Manual

Danger, Warning, and Caution symbols are used throughout the manual to help identify andavoid hazardous situations. Examples of each symbol are shown and explained below.

DANGER

Indicates an imminently hazardous situation that, if not avoided, will result indeath or serious injury. This signal word is to be limited to the most extremesituations. It may also be used to alert against unsafe practices. (Color: red)

WARNINGIndicates a potentially hazardous situation that, if not avoided, could result indeath or serious injury. It may also be used to alert against unsafe practices orcause product failure. (Color: orange)

Caution

Indicates a potentially hazardous situation that, if not avoided, may result inminor or moderate injury. It may also be used to alert against unsafepractices. (Color: yellow)


3/50

i

Table of Contents

Chapter 1............................................................................... 1-1Description ...................................................................................... 1-1

Technical Specifications ...............................................................1-2Chapter 2............................................................................... 2-1

Hardware ........................................................................................ 2-1Mounting....................................................................................... 2-1Wiring............................................................................................ 2-1Network Connector ....................................................................... 2-2Module and Network Status LEDs................................................2-3

Chapter 3............................................................................... 3-1Network Configuration.....................................................................3-1

Local Assignment of PROFIBUS Address .................................... 3-2Assignment of Network Data Rate................................................3-4

Chapter 4............................................................................... 4-1PROFIBUS GSD File ...................................................................... 4-1

853 Three Phase Power Controller GSD File ............................... 4-2Chapter 5............................................................................... 5-1

PKW and PZD Data Capability .......................................................5-1Parameter Process data Object ....................................................5-1Data Exchange using PPOs .........................................................5-3

PZD Output Data...................................................................................5-3PZD Input Data .....................................................................................5-4

Using the PKW Structure for Single Parameter Requests ............ 5-5Error Response............................................................................. 5-7Modifying the Assignment of PZD Data ........................................ 5-9

PZD Output Map ...................................................................................5-9PZD Input Map....................................................................................5-11

Chapter 6............................................................................... 6-1Configuration Example....................................................................6-1

Hardware Configuration................................................................6-1Software Configuration .................................................................6-4Sample Code ................................................................................ 6-9

Chapter 7............................................................................... 7-1Troubleshooting .............................................................................. 7-1


4/50

ii

PROFIBUS Interface LED Indicators ............................................ 7-2Troubleshooting Guide..................................................................7-3

Glossary .................................................................................... i


5/50

iii

List of Figures

Figure 1-1 PROFIBUS Connectivity .............................................................................1-1Figure 2-1 850 Series PROFIBUS Interface Card........................................................2-1

Figure 2-2 PROFIBUS Interface Connector .................................................................2-2Figure 2-3 Location of status LEDs ..............................................................................2-3Figure 6-1 GSD file installation.....................................................................................6-1Figure 6-2 Hardware configuration of test system........................................................6-3Figure 6-3 FC100: Receive data from the 853 .............................................................6-4Figure 6-4 FC101: Send data to the 853 ......................................................................6-5Figure 6-5 S7DEMO_853 block summary....................................................................6-6Figure 6-6 DB100: Input data received from the 853 ...................................................6-7Figure 6-7 DB100: Output data sent to the 853............................................................6-8Figure 6-8 853Ctrl: Allows user to read and write variables in real time..... ..................6-9Figure 7-1 PROFIBUS Interface Board........................................................................7-2

List of Tables

Table 1-1 Technical Specifications...............................................................................1-2Table 1-2 Transmission Medium Specifications...........................................................1-3Table 2-1 PROFIBUS Connector Pinout ......................................................................2-2Table 2-2 PROFIBUS Interface Status LEDs...............................................................2-3Table 5-1 PPO Data Exchange Message Format ........................................................5-2Table 5-2 Master's PZD Output Data ...........................................................................5-3

Table 5-3 853 PZD Input Data .....................................................................................5-4Table 6-1 853 Output and Input Words........................................................................6-2Table 7-1 PROFIBUS Interface Status LEDs...............................................................7-2Table 7-2 PROFIBUS Troubleshooting ........................................................................7-3


6/50


7/50

1-1

Chapter 1

Description

Caution

The Spang 850 Series Controller can be controlled remotely when connected to aPROFIBUS network. In order to enable the remote control, the Remote/Localdigital input must be shorted.

PROFIBUS is a vendor-independent, low-level network standard that defines the connection andcommunication between industrial devices. PROFIBUS has two primary functions:

Control of connected industrial devices

Monitoring link for connected industrial devices

The Spang 850 Series PROFIBUS Interface products support the PROFIBUS-DP variant of thePROFIBUS protocol, which is a multimaster, master-slave, token passing protocol designed especially forcommunication between automatic control systems and distributed I/O at the device level. The opennature of the network allows equipment from different manufacturers to coexist on the same bus.

The Spang 850 Series PROFIBUS Interface products are 'slave' devices; that is, they do not initiatecommunication. A master device on the network must establish a connection with the 850 SeriesPROFIBUS interface, in order for data to be exchanged.

The PROFIBUS-DP network standard follows a high speed version of the RS485 standard, permittingbaud rates of up to 12Mbaud. A maximum of 32 PROFIBUS-DP stations (nodes) may be contained

within a single network segment. Use of RS485 repeaters allows a total of up to 127 stations.

Figure 1-1 PROFIBUS Connectivity


8/50

Descript ion May 2005

1-2

Technical Specifications

Table 1-1 Technical Specifications

Network Topology Linear bus terminated at both ends

Medium Shielded twisted pair

Line Length 1200 m max, depending on data rate

Network Supply Voltage 5VDC +/- 5%

Network Data Rate 9.6 Kbaud to 12Mbaud, step-wise

Network Nodes 32 per segment, 127 with repeaters

Station (node) types Masters (active), with bus-accesscontrol; Slaves (passive) have no busaccess control

Bus Connector 9 pin D-sub; T-type is recommendedfor quick network configuration

Bus access Hybrid; token-passing ring betweenmaster stations; master-slave betweenmaster and slave stations

Signalling NRZ bit encoding combined withRS485 signaling

Encoding Half-duplex, asynchronous, no bitstuffing

Terminating Resistors 250 or 150 ohm at each end of the bus,depending on cable type


9/50

May 2005 Descript ion

1-3

Table 1-2 Transmission Medium Specifications

Transmission Rate Segment Length (cable type A) Segment Length (cable type B)

9.6 Kbits/sec 1200 meters 1200 meters

19.2 1200 1200

45.45 1200 1200

93.75 1200 1200

187.5 1000 600

500 400 200

1500 200 70

3000, 6000, 12000 100

Cable Type A Impedance: 135 165 ohm; f = 3 20 MHzCapacity: < 30 pF/mLoop resistance: 110 ohm/kmWire diameter: 0.64 mmCore cross section: > 0.34 mm

2(22 AWG)

Cable Type B Impedance: 100 130 ohm; f > 100 KHzCapacity: < 60 pF/mLoop resistance: naWire diameter: 0.64 mm

Core cross section: > 0.22 mm2

(24 AWG)


10/50

Descript ion May 2005

1-4


11/50

2-1

Chapter 2

Hardware

Mounting

The 850 Series PROFIBUS Interface card is mounted on the main control board inside the 850 SeriesController. The actual card mounted in the controller (850 chassis version) is shown below.

Figure 2-1 850 Series PROFIBUS Interface Card

Wiring

Each station on the PROFIBUS network is connected to the medium via a 9-pin D-sub connector. Thefemale side of the connector is located in the station (850 series Interface), while the male side ismounted on the bus cable.

The bus cable (type A and type B) must be terminated at both ends by a termination resistor. Thetermination resistor is 220 ohms (type A cable) or 150 ohms (type B), accompanied by 390 ohm pullupand pulldown resistors.

Typical PROFIBUS T connectors offer a selectable termination option. It is important to note thatstations located between the terminated ends of a cable run must not be resistor-terminated.


12/50

Hardware May 2005

2-2

Network Connector

The 850 series PROFIBUS Interface connector is afemale (socket) DB9 type. The PROFIBUS cableconnector is specified as a DB9 male (plug) type.Cable (plug end) connectors generally includeselectable terminating resistors. Terminatingresistance MUST be applied at the end stations onthe network.

Figure 2-2 PROFIBUS Interface Connector

Each station on the PROFIBUS network must ensure that it provides 5 volts and GND to pins 5 and 6 ofthe connector. These signals are necessary for bus termination. VP (pin 5) must be capable of driving

10mA for the terminating resistors.

Table 2-1 PROFIBUS Connector Pinout

Pin number RS 485 Reference Signal Descripti on

1 SHIELD(2)

Shield, protectiveground

2 - 24 V(2)

-24V output voltage

3 B/B' RxD/TxD - P Receive/Transmit

Data N

4 CNTR P(2)

Control P

5 C/C' DGND Data ground

6 VP(1)

Voltage - plus

7 + 24 V(2)

+24V output voltage

8 A/A' RxD/TxD - N Receive/TransmitData - N

9 CNTR N(2)

Control N

(1) Signal is only necessary at the end node (station at the end of the bus)

(2) These signals are optional.


13/50

May 2005 Hardware

2-3

Module and Network Status LEDs

Figure 2-3 Location of status LEDs

The interface card uses three LEDs to describe Module and Network status. The LEDs flash duringpower up as a self-test. Status is summarized in the following table.

Table 2-2 PROFIBUS Interface Status LEDs

LED State DescriptionD6 (green), D3 (green),

D5 (red)Off There is no power applied

D5 On Interface board is notcommunicating with control board

D5, D3 Flashing No network activity

D3 Flashing Configuration incomplete

D6, D3 On Interface is configured andexchanging data with its master


14/50

Hardware May 2005

2-4


15/50

3-1

Chapter 3

Network Configuration

DANGEROnly qualified electrical personnel familiar with the construction and operation of thisequipment and the hazards involved should install, operate, and/or service thisequipment. Read and understand this manual and other applicable manuals in theirentirety before proceeding. Failure to observe this precaution could result in severebodily injury or loss of life.

Caution

The 850 Series Controller is configured using the programmable settings.

Programming the settings incorrectly can cause the controller to exhibit intermittent orfull output conditions.

In order to communicate across PROFIBUS, the 850 Series controller must be configured as a node(station) on the PROFIBUS network.

Each station on the network must have a unique address in the range 0 - 126. The default slave addressis 126; however, address 126 is NOT a valid slave address for IO data exchange.

There are two methods available for setting the address of the 850 Series controller: 1) by a masterstation over the network (refer to the Communication chapter); or 2) locally, using the Configuration Tool

supplied with the 850 Series controller. In either case, it is imperative that the station address remainunique on the network throughout the configuration process.


16/50

Network Configuration May 2005

3-2

Local Assignment of PROFIBUS Address

Note: The 850 Series Controller must be under Local control (i.e, the Remote/Local input is open) toenable write capability from the Configuration Tool. Refer to the specific 850 Series product manual(SPE-AM 851, SPE-AM 853, etc) for detailed information on the Configuration Tool.

Establish on-line communication between the 850 Series Controller and the accompanying ConfigurationTool. Open the settings window, and select the Network Tab. Set the Network Type for PROFIBUS.


17/50

May 2005 Network Configuration

3-3

Set the Network Address. It is the user's responsibility to assign a station address which is UNIQUE onthe network. There is no address arbitration procedure on the PROFIBUS network; duplicate stationaddresses will result in undefined network behavior.


18/50

Network Configuration May 2005

3-4

Set the Network Loss Option for desired operation.

This setting defines 850 Controller behavior in the event that communication over the network is lost.

FAULT and STOP The 850 Controller will indicate a fault and the output will be shut off.

IGNORE and RUN There is no indication of network loss, and the 850 Controller continues normaloperation.

ALARM and RUN The 850 Controller will indicate an alarm and continue normal operation.

Assignment of Network Data Rate

The 850 series PROFIBUS interface is an AUTOBAUD device. When the interface is added to the

PROFIBUS network, it senses the network baud rate, and sets its own baud rate accordingly.


19/50

4-1

Chapter 4

PROFIBUS GSD File

The PROFIBUS specification requires that an electronic device description accompany each PROFIBUSinterface product. The electronic data sheet is an ASCII text file referred to as a 'GSD' file. The GSD filecontains information about the product manufacturer, communication rates and timing, product options,and device parameters. Availability of GSD files enables the user to configure a PROFIBUS networkusing any of several vendor-independent, network configuration tools.

The GSD file (SPE0773e.gsd) of the 853 Three Phase Power Controller follows the format defined byPROFIBUS International. The filename corresponds to the product 'Ident Number' assigned byPROFIBUS International.


20/50

PROFIBUS GSD May 2005

4-2

853 Three Phase Power Cont roll er GSD File

; Device Data File for 853 Three Phase Power Controller; Copyright (c) 2004, Spang Power Electronics

; GSD Rev 3.0

#PROFIBUS_DPGSD_Revision = 2

Vendor_Name = "Spang Power Electronics"Model_Name = "853 Three Phase Power Control"Revision = "Rev 8.x"Ident_Number= 0x0773Protocol_Ident = 0Station_Type = 0FMS_Supp = 0Hardware_Release = "Rev B"Software_Release = "8.00x"

; Supported baudrates9.6_supp = 119.2_supp = 193.75_supp = 1187.5_supp = 1500_supp = 11.5M_supp = 13M_supp = 16M_supp = 112M_supp = 1

; Maximum responder time for supported baud rates

MaxTsdr_9.6 = 60MaxTsdr_19.2 = 60MaxTsdr_93.75 = 60MaxTsdr_187.5 = 60MaxTsdr_500 = 100MaxTsdr_1.5M = 100MaxTsdr_3M = 200MaxTsdr_6M = 200MaxTsdr_12M = 200

; Supported hardware featuresRedundancy = 0

Repeater_Ctrl_Sig = 224V_Pins = 0

; Slave Specific

Freeze_Mode_Supp = 0Sync_Mode_Supp = 0

Auto_Baud_Supp = 1

The 853 is an 'autobaud'device; it supports all of the

baudrates defined for Profibusnetworks.

'Max_Tsdr' is the maximumtime allowed to pass beforethe slave responds to themaster. It is specified in

'Tbits', a time equal to theinverse of the baud rate. One

Tbit at 12M = 83nsec

The 853 will configure itself tothe existing network baud rate

upon powerup.The network address of the

853 is set by the masterthrough SAP 55.


21/50

May 2005 PROFIBUS GSD

4-3

Set_Slave_Add_Supp = 1

; Maximum length of user parameter dataUser_Prm_Data_Len = 0

; Default user parameter string; noneSlave_Family = 0@SpangMin_Slave_Intervall = 2Modular_Station = 1Max_Module = 3Max_Input_Len = 32Max_Output_Len = 32Max_Data_Len = 56Max_Diag_Data_len = 8

Module = "5WOut 10WIn - config follows" 0xCD, 0xC4, 0xC9, 68, 17, 54, 75, 72, 30, 63, 74, 119, 11, 50,13, 65 ; 5w out, 10w in, data follows1EndModule

Module = "PKW + 5Out 10In - config follows" 0xCD, 0xC8, 0xCD, 68, 17, 54, 75, 72, 30, 63, 74, 119, 11,50, 13, 65 ; PKW + PZD, 5w out, 10w in, data follows2EndModule

Module = "PKW + 5Out 10In - config saved" 0xC0, 0xC8, 0xCD ; PKW + PZD, 5w out, 10w in, no datafollows3EndModule

; Spang 853 Configuration specific parameters; Spang_Icon_File = "SP850.ico"

Each 'Module' mirrors a PPO type defined for the 850 series. Module 1 corresponds to PPO 1,Module 2 is the same as PPO 2, and so on.

Modules 1 and 2 define the output and input data lengths, and include the 850 setting numbersassigned to the output and input data.

Module 3 defines the output and input data lengths, but does not include setting numbers; theassignment (configuration) stored in the 850 will be used.


22/50

PROFIBUS GSD May 2005

4-4


23/50

5-1

Chapter 5

PKW and PZD Data Capability

The 850 series power control products utilize a PROFIBUS communication structure similar to thatdefined in the PROFIDRIVE profile published by the PNO (PROFIBUS User Organization). ThePROFIDRIVE profile describes the structure of the cyclic data telegram as a combination of parameterdata and process data. The structure is referred to as a PPO (Parameter Process data Object) type.

Parameter Process data Object

The Parameter Process data Object (PPO) consists of a parameter segment (PKW) and a processdata segment (PZD). The PKW segment is used to transfer a single parameter request from the masterto the slave, and for the slave to provide a response to the masters request. The request is handled asacyclic communication. The slave response to the PKW request may not be ready in the immediateresponse telegram. The PZD segment is the cyclic portion of the telegram. The slaves cyclic responseinformation will always be present in the PZD segment of its response.

The following table describes the PPO types available for 850 series communication. They are definedas modules in the 850 series gsd file. The desired configuration is assigned by the master in theconfiguration telegram. Note that not all PPO types contain a PKW message segment. If purely cycliccommunication is desired, the 850 series product can be configured as such.


24/50

Parameter Process data Object (PPO) May 2005

5-2

Table 5-1 PPO Data Exchange Message Format

PKW PZD

PKE IND PWE PZD1 PZD2 PZD3 PZDn

Type 1: Octet String (20 max) 5 words out, 10 words in

Type 2: Octet String (28 max)

PZD1CTWSTW

PZD2 PZD3 PZDn

PKW: Parameter ID / Value

PZD: Process Data; cyclically transmitted

PKE: Parameter ID (octets 1-2)

IND: Sub-index (octets 3-4)

PWE: Parameter Value (octets 5-8)

CTW: Control Word (request)

STW: Status Word (response)


25/50

May 2005 Parameter Process data Object (PPO)

5-3

Type 1 communication does not include a PKW segment. Type 1 is defined as 5 words of PZD (process)data out (from the master), and 10 words of PZD data in (to the master). Type 2 communication includesthe 8-byte PKW (parameter) segment, 5 words of process data out, and 10 words of process data in.

The default PPO type for the 853 is PPO 1, described as 5 words of output data (control information fromthe master), and 10 words of input data (status information sent to the master). There is no PKWsegment in the 853 default configuration.

Data Exchange using PPOs

The slave's diagnostic response indicates satisfactory configuration, and whether or not it has a master(4th byte of diagnostic response). When the master detects the satisfactory configuration of its slave (byrepeated requests for diagnostics), the master and slave enter the Data Exchange mode. The DataExchange mode is marked by the transfer of process data between the master and slave in a query-response, or polled, arrangement. The master sends output data to the slave and receives input data inresponse. The master's output data is written to the 853. Input data is data read from the controller andsent to the master. If the slave has been configured for data transfer involving PKW (parameter) data, thePKW portion of the message will be handled apart from the PZD (process) data.

PZD Output Data

The PZD output data (from master to 853 slave) is summarized below. The first two bytes of PZDoutput data are ALWAYS the Control Word (setting 93). No other 853 setting may be mapped tothis output.

Table 5-2 Master's PZD Output Data

PZD Byte Contents Default Mapping

0,1 Output 1 data Setting 93 Control Word (ALWAYS)

2,3 Output 2 data Setting 68 Power Output Setpoint

4,5 Output 3 data Setting 17 Voltage Output Setpoint

6,7 Output 4 data Setting 54 Current Output Setpoin t

8,9 Output 5 data Setting 75 Duty Cycle Setpoin t


26/50


5-4

PZD Input Data

The PZD input data (from 853 Controller to master) is summarized in the following table. The first twobytes of the PZD input data are ALWAYS the Status Word (setting 94). No other 853 setting maybe mapped to this input. Input data is READ-ONLY and cannot be altered by the master.

Table 5-3 853 PZD Input Data

PZD Byte Contents Default Mapping

0,1 Input 1 data Setting 94 Status Word (ALWAYS)

2,3 Input 2 data Setting 72 Power Output

4,5 Input 3 data Setting 30 Voltage Output

6,7 Input 4 data Setting 63 Current Output

8,9 Input 5 data Setting 74 Duty Cycle Out

10,11 Input 6 data Setting 119 Fault Code

12,13 Input 7 data Setting 11 Voltage In

14,15 Input 8 data Setting 50 Current In

16,17 Input 9 data Setting 13 Frequency (actual)

18,19 Input 10 data Setting 65 KVA In


27/50


5-5

Using the PKW Structure for Single Parameter Requests

The PKW is an 8 byte segment at the front of the data exchange message. The PKW is used by themaster to issue a single parameter request. The slave processes the request and formulates theresponse to it. It is important to note that the slaves PKW response may not be ready to be included inthe immediate cyclic response telegram. The slave will include its PKW response in a subsequent cyclicresponse after it has processed the request. The slave is unable to respond to a new parameter requestuntil the current request has been completed. It is the responsibility of the master to maintain the orderand timing of parameter requests within the cyclic message.

The 8-byte PKW segment is interpreted as follows:

PKW PZD


PKE: Parameter ID (octets 1-2)

IND: Sub-index (octets 3-4)

PWE: Parameter Value (octets 5-8)

The PKE (Parameter ID) is a 16 bit value which contains the request/response code and parameternumber. Bits 0 10 identify the 853 parameter number. Bit 11 is unused. Bits 12 15 identify therequest/response.

Parameter ID (PKE)

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

Identif ier (ID) Parameter Number (PNU)

REQUEST

0 = no request

1 = read

2 = write

RESPONSE

0 = no response

1 = transfer resp

7 = error resp

8 = no master

PNU numbers 1 119 correspond to850 series settings

PNU numbers 150 164 correspond toprocess data settings

The IND (index) is currently reserved for future use. The PWE is a 16 bit value transferred high byte first.For a parameter read request, the PWE contents are undefined. Likewise in a parameter write response,the PWE contents are undefined.


28/50


5-6

As an example, the PKW read request of 853 setting number 95 (Ramp Up Time) is as follows:

PKW PZD


10 5FH 00 00 00 00 00 00

PKE: Read request, Parameter number 95

IND: Not used

PWE: Not used for Parameter Read

The PKE is determined as follows:

Parameter ID (PKE)

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

Identif ier (ID) Parameter Number (PNU)

1 = read reques t 95 (x5F) = Ramp Up Time

0 0 0 1 0 0 0 0 0 1 0 1 1 1 1 1

The master continues to issue the same PKW request in the cyclic message exchange until a PKWresponse is received. Only one PKW task is processed at any one time.

The slave will issue a no response in the PKW segment of its cyclic response until the PKW request hasbeen processed.

PKW PZD


00 5FH 00 00 00 00 00 00

PKE: No response, setting number 95

IND: Not used

PWE: Not used for No response


29/50


5-7

When the slave has processed the PKW request, it will issue a transfer response or an error response.

PKW PZD


10 5FH 00 00 00 00 00 0AH

PKE: Transfer response, setting number 95

IND: Not used

PWE: Current value of setti ng num ber 95 (eg, 10 seconds)

The slave continues to provide the last response PKW until the master formulates a new request. A PKWread response always provides the current value.

Error Response

If the slave cannot process the PKW request, it issues an error response. If the error identifier in theslave response is 8, it means the master does not have control of the slave for PKW processing. Theslaves configuration is probably incorrect.

If the error identifier in the slave response is 7, the error is described in the PNU field.

Parameter ID (PKE)

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

Error Identifier Error Codes

7 = error resp

8 = no master

0 = illegal parameter number

1 = Parameter value cannot bechanged

17 = request cannot be processed dueto operating state

18 = unspecified error


30/50


5-8

As an example, a request to write a new value to a read-only setting, such as status, will return an error.

Request:

PKW PZD


20 5EH 00 00 00 00 AA 55H

PKE: Write request, setting number 94 (Status)

IND: Not used

PWE: Desired value of setting number 94

Response:

PKW PZD


70 5EH 00 00 00 00 00 11H

PKE: Error response, setting number 94 (Status)

IND: Not used

PWE: Error 17, request cannot be processed due to operatingstate

Important Note

The PKW message segment cannot be used to modify an 853 setting that is mapped to a PZDoutput. As an example, the control word (setting 93) is mapped to PZD output one. This means that aPKW request to write the control word w ill generate an error response.


31/50


5-9

Modifying the Assignment of PZD Data

The data telegram is used for the cyclic transfer of data between master and slave. PPO capabilitybreaks the data telegram into an acyclic PKW (parameter) segment and a cyclic PZD (process) segment.The process data are applied to settings assigned by the information sent from the master to the slaveduring configuration. It is possible to modify the settings referenced in the data telegram by using thePKW segment of the data telegram. Note that the first output word must always remain the contro lword, and the first input word will always be the status word .

The PZD data is defined as 16 bit values transferred as bytes, high byte first. Each word of datacorresponds to an 853 setting. Output data is written to the setting; input data is read from the setting.The list of settings addressed in the PZD data is an array that can be accessed as parameter numbers150 164. The mapping of PZD position to parameter is illustrated below.

PZD Output Map

PZD Offset Parameter Number Description / Default Mapping

0 150 Output 1 data / Setting 93 Control Word (ALWAYS)

2 151 Outpu t 2 data / Setting 68 Power Setpoin t

4 152 Outpu t 3 data / Setting 17 Voltage Setpoin t

6 153 Outpu t 4 data / Setting 54 Current Setpoin t

8 154 Outpu t 5 data / Setting 75 Duty Cycle Setpoin t

Any 853 setting that can be modified is a valid output parameter. For example, to change Output 2 fromsetting 68 (Power Setpoint) to setting 17 (Voltage Setpoint) the PKW message segment would look likethe following:


32/50


5-10

PKW Request:

PKW PZD


20 97H 00 00 00 00 00 11H

PKE: Write request, Parameter number 151d = 97H

IND: Not used

PWE: New 853 setting number 17d = 11H

Changes to the PZD output map should be made with the 850 unit output OFF. It is the usersresponsibility to ensure proper values are set in the PZD output data before turning the unit output on.

The PKW response:

PKW PZD


10 97H 00 00 00 00 00 00

PKE: Transfer response, Parameter number 151d = 97H

IND: Not used

PWE: Not used


33/50


5-11

PZD Input Map

PZD Offset Parameter Number Description / Default Mapping

0 156 Input 1 data / Setting 94 Status Word (ALWAYS)

2 157 Input 2 data / Setting 72 Power Outpu t

4 158 Input 3 data / Setting 30 Voltage Outpu t

6 159 Input 4 data / Setting 63 Current Outpu t

8 160 Input 5 data / Setting 74 Duty Cycle Out

10 161 Input 6 data / Setting 119 Fault Code

12 162 Input 7 data / Setting 11 Voltage In

14 163 Input 8 data / Setting 50 Current In

16 164 Input 9 data / Setting 13 Frequenc y (actual)

18 165 Input 10 data / Setting 65 KVA In

Any 853 setting is a valid input parameter. To change Input 6 from setting 119 (Fault Code) to setting102 (Product Code) the PKW message segment would look like the following:

PKW PZD


20 A1H 00 00 00 00 00 66H

PKE: Write request, Parameter number 161d = A1H

IND: Not used

PWE: New 853 setting number 102d = 66H

The PKW response:

PKW PZD


10 A1H 00 00 00 00 00 00

PKE: Transfer response, Parameter number 161

IND: Not used

PWE: Not used


34/50


35/50

6-1

Chapter 6

Configuration Example

This chapter describes the setup and operation of an 853 Three Phase Power Controller as a slavedevice on a PROFIBUS network. The Siemens S7 400 PLC is the master. The Simatic Step 7 v5.2configuration software was used in this example.

Hardware Configuration

The hardware configuration consists of a nine-slot rack; Siemens power supply PS407 4A; mainprocessor CPU 412-5; extended communication processor CP 443-5; and a Spang Power Electronics853 Three Phase Power Controller.

In the Step 7 project, add the Siemens hardware and install the 853. To install the 853 into the Step 7device database, add its GSD file. From the Step 7 hardware configuration window, select Options >Install new GSD.

Browse for the 853 GSD file, labeled SPE_0773.gsd, and add it to the device library. After the GSD filehas been added to the device database, the 853 will appear in the device list under Addi tional FieldDevices > General > Spang . Double click the device to add it to the HW configuration.

Figure 6-1 GSD file installation


36/50

Configuration Example May 2005

6-2

Several input/output modules are defined in the 853 GSD. This example uses module 1, 5 Words Out,10 Words In config follows, defined as 5 words of output data and 10 words of input data. The moduledescribes the information passed between the S7 400 PLC master and the 853 slave in Data Exchangemode. The information is described below.

Table 6-1 853 Output and Input Words

Output Input

Word 1 Control Word (93) Status Word (94)

Word 2 Power Output Setpoint (68) Power Output (72)

Word 3 Voltage Output Setpoint (17) Voltage Output (30)

Word 4 Current Output Setpoint (54) Current Output (63)

Word 5 Duty Cycle Setpoin t (75) Duty Cycle Output (74)

Word 6 Fault Code (119)

Word 7 Voltage Input (11)

Word 8 Current Input (50)

Word 9 Frequency (13)

Word 10 KVA In (65)


37/50

May 2005 Configuration Example

6-3

The hardware configuration is shown below.

Figure 6-2 Hardware configuration of test system


38/50


6-4

Software Configuration

Transfer instructions in the Siemens S7 400 PLC are limited to a max of 4 bytes of consistent data. Sincethe data between the PLC and the 853 has a maximum of 14 words, two System Function calls are usedto read and write data. The System Function calls are SFC14 (read consistent data of DP standardslave), and SFC15 (write consistent data to a DP standard slave). The use of system function callsensures the consistency of data over the length of the data exchange. The S7 demo project has twoUser Function Calls which utilize SFC14 and SFC15, and are illustrated in the following figures.

Figure 6-3 FC100: Receive data from the 853


39/50


6-5

Figure 6-4 FC101: Send data to the 853

The SFC14 and SFC15 connect to the PROFIBUS DP standard slave by the word assigned to the

LADDR input. The word must be the same as defined in the hardware configuration of the selected I/Omodule, which was I address (512D or 200H) and Q address (512D or 200H).

The user function calls, FC100 and FC101, are in the main program block (OB1) of the Siemens S7 400PLC. Additional organizational blocks are needed to handle error and fault conditions. A list of theorganizational blocks used in the S7DEMO_853 program is shown on the following page.


40/50


6-6

Figure 6-5 S7DEMO_853 block summary

Data is transferred from the system function calls to a custom data block DB100. The data block maps

the data to memory by assigning tags matching the definition of the selected I/O module. The data blockmust be the exact length of the configured data exchange. Control word bits and status bits are assignedindividually, and are easy to see/access. Note that the word storage in the Siemens S7-400 PLC has thehigh and low bytes switched. The data block accommodates this structure. The data block definition isillustrated in the following figures.


41/50


6-7

Figure 6-6 DB100: Input data received f rom the 853


42/50


6-8

Figure 6-7 DB100: Output data sent to the 853

The variable table 853Ctrl was created to use for testing. The variable table is accessible online and

allows the user to change variables while the Siemens S7-400 PLC is running. The definition of thevariable table is shown below.


43/50


6-9

Figure 6-8 853Ctrl: A llows user to read and wr ite variables in real time.

Sample Code

Thesample code using SIMATIC Step 7 v5.2 software has been tested and is available by request.


44/50


45/50

7-1

Chapter 7

Troubleshooting

DANGEROnly qualified electrical personnel familiar with the construction and operation of thisequipment and the hazards involved should install, operate, and/or service thisequipment. Read and understand this manual and other applicable manuals in theirentirety before proceeding. Failure to observe this precaution could result in severebodily injury or loss of life.

DANGER

The user is responsible for conforming with all applicable local, national, and

international codes; wiring practices, grounding, disconnects, and overcurrentprotection are of particular importance. Failure to observe this precaution could resultin severe bodily injury or loss of life.

DANGER

This equipment is at line voltage when AC power is connected. Disconnect and lockout all ungrounded conductors of the AC power line. Failure to observe theseprecautions could result in severe bodily injury or loss of life.

DANGER

Power must be applied to the 850 Series Controller with the cover removed to performcertain troubleshooting procedures. Voltages on many components are at incomingline potential. To avoid electric shock hazard or damage to equipment, do not touchany component other than those specified in the manual. Failure to observe theseprecautions could result in severe injury or loss of life.


46/50

Troubleshooting May 2005

7-2

PROFIBUS Interface LED Indicators

The following figure illustrates the location of module and network status LEDs on the PROFIBUSinterface card.

Figure 7-1 PROFIBUS Interface Board

The interface card uses three LEDs to describe Module and Network status. The LEDs flash duringpower up as a self-test.

Table 7-1 PROFIBUS Interface Status LEDs

LED State DescriptionD6 (green), D3 (green),

D5 (red)Off There is no power applied

D5 On Interface board is notcommunicating with control board

D5, D3 Flashing No network activity

D3 Flashing Configuration incomplete

D6, D3 On Interface is configured andexchanging data with its master


47/50

May 2005 Troubleshoot ing

7-3

Troubleshooting Guide

Table 7-2 PROFIBUS Troubleshooting

Condition Possible Cause Corrective Action

Check for control power

Check that jumper JP1 is removedbefore applying power

Control BoardHeartbeat LED off

DSP on main control PCBfailed

Replace main control PCB

No Control Power Insure the 850 Series Controller hasseparate control power

Power Supply connectionopen

Check Power Supply connections tomain control PCB

Interface PCB connectionopen

Check connection between thePROFIBUS Interface PCB and the maincontrol PCB.

PROFIBUS StatusLEDs of f

Power Supply failed Replace Power Supply

Verify PROFIBUS Interface flashesLEDs on power up

Verify Heartbeat LED on main PCB

D5 (red) LED on The PROFIBUS Interface isnot communicating with the

main control board

Replace main control PCB

Verify PROFIBUS Interface flashesLEDs on power up

Verify presence and operation ofPROFIBUS network

D5 (red), D3 (green)flashing

The PROFIBUS Interfacedetects no network activity

Replace PROFIBUS Interface PCB

Check Network Address setting (use850 Series Configuration Tool orPROFIBUS configuration tool)

D3 (green) flashing Configuration incomplete

Use PROFIBUS configuration tool tocheck master's configuration data


48/50

Troubleshooting May 2005

7-4


49/50

i

Glossary

Glossary of common terms and abbreviations used in SCR Power Controllers and their applications

Term or Acronym Description

ASCII American Standard Code for Information Interchange

Autobaud The ability of a device on a network to sense the network baud rate

GSD PROFIBUS Electronic Device Description

I/O Input/Output

LED Light emitting diode

NC Normally closed contact

NO Normally open contact

NEC National Electric Code

NEMA National Electrical Manufacturers Association

PCB Printed Circuit Board

PCMCIA Personal Computer Memory Card International Association

PKW Parameter segment of a PPO-style cyclic PROFIBUS message

PLC Programmable Logic Controller

PPO Parameter Process data Object

PROFIBUS A vendor-independent, low-level, industrial network standard

PROFIBUS-DP A master-slave, token-passing protocol designed specifically forautomated control and device-level IO. A variant of the PROFIBUSprotocol.

PZD Process-data segment of a PPO-style cyclic PROFIBUS message

RMS Root Mean Squared

Rx Receive

SCR Silicon Controlled Rectifier

Setpoint Reference for PID control

Tx Transmit


50/50

Glossary May 2005

Term or Acronym Description

VAC Volts Alternating Current

VDC Volts Direct Current

VRMS Volts Root Mean Squared

853 profibus manual

Documents