FC8x - SIEB & MEYER · :Protocol Description FC8x Profibus Communication 3 1 Protocol Description...

Title

FC8xProfibus Communication

SIEB & MEYER AGAuf dem Schmaarkamp 21 * D-21339 Lüneburg * (Germany)

Telephone: +49 - 4131 - 203 - 0 * Telefax: +49 - 4131 - 203 - 2000Email: [email protected]: http://www.sieb-meyer.com

FC8x Profibus Communication

http://www.sieb-meyer.com

http://www.sieb-meyer.com

Copyright

Translation of the original instructions. Copyright © 2012 SIEB & MEYER AG.All rights reserved.

This manual or extracts thereof may only be copied with the explicit authorization by SIEB & MEYER AG.

Trademarks

All product, font and company names mentioned in this manual may be trademarks or registered trademarksof their respective companies.

Identification Key

FC8x_BED_Profibuskommunikation/R02-SM-EN-km/uhSeptember 18, 2012

Profibus Communication FC8x

1 Protocol Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31.1 Communication with Higher-ranking Controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31.2 Prompt Telegram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31.2.1 CMD_SBYTE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41.2.2 CMD_BYTE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41.2.3 CMD_PAR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41.3 Reply telegram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41.3.1 SFU_SB0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51.3.2 SFU_SB1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61.3.3 SFU_SB2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61.3.4 SFU_SB3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61.3.5 SFU_PAR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61.4 Handshake between Master and Slave . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.5 Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81.5.1 Command 1, Delete Error (ERR_RES) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81.5.2 Command 5, Traverse Speed (MOVE). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81.5.3 Command 32, Controller Off (REG_OFF) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91.5.4 Command 33, Controller On (REG_ON) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

2 Configuration of the PLC (S7) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112.1 Setup of the Anybus GSD-File.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112.2 Configuration of an Anybus Participant. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

3 Anybus Communicator by HMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133.1 Connectors, Switches and Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133.2 Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143.2.1 Accessories Checklist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143.2.2 Installation and Startup Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153.2.3 Technical Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153.3 Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

FC8x Profibus Communication 1

Inhalt

2 Profibus Communication FC8x

Protocol Description

1 Protocol Description

1.1 Communication with Higher-ranking Controls

The SIEB & MEYER DNC61 protocol is used to connect an FC8x to a higher-rankingcontrol (Master). The physical connection of the slave to the master is supported bythe following bus systems:

Profibus DP

The Communication between masters and CNC modules is always carried out by themaster-slave method, i.e. a CNC-module becomes only active after being requestedby the master.

Data is exchanged cyclically in data telegrams. The prompt telegram is applied fromthe master to the CNC module and the reply telegram from the CNC module to themaster.

The cycle time of the data exchange arises from the number of bus participants andthe transfer rate of the bus system.During the communication an individual bus address, which is derived from the mod-ule address, is allocated to each CNC module. In the INTERBUS-S this is made upof the order in the connector.

1.2 Prompt Telegram

The master and slave communicate in a cyclic interchange of firmly defined promptand reply telegrams.

Range: 8 Bytes, data received from the FC module

Exchange of request and reply telegrams

Byte# Name Meaning0 CMD_SBYTE Control byte for the command transmission

Bit number Name Meaning0 CMD_VALID Start command123456 CMD_HBEAT Heartbeat-Bit7

1 CMD_BYTE Command byte, contains the command number23

4 to 7 CMD_PAR Double word (4 bytes) for the parameter transmission to the FC module



1.2.1 CMD_SBYTE

The master transmits the control bits to the frequency converter via the commandcontrol byte. Among other things, the handshake between master and frequencyconverter is realized by the command control byte.

CMD_VALID If this bit is toggled, another command will be initiated. At this time,CMD_BYTE and CMD_PAR must contain valid data.

CMD_HBEATThe heartbeat bit CMD_HBEAT can be used for the mutual monitoring of mas-ter and slave (frequency converter). For this, the master toggles the bitCMD_HBEAT and monitors whether the frequency converter has adapted thebit SFU_HBEAT after a defined time.

1.2.2 CMD_BYTE

Via the CMD_BYTE, the master selects the respective command stored in the fre-quency converter. The selection is made by unambiguous command numbers.

In the CMD_PAR, a 32 bit parameter can be transmitted with every command.

1.2.3 CMD_PAR

In the CMD_PAR, a 32 bit parameter can be transmitted with every command fromthe master to the frequency converter.

1.3 Reply telegram

The master and the slave communicate in a cyclic interchange of firmly definedprompt and reply telegrams.

Range: 8 bytes, data transmitted from the FC module to the master

Exchange of request and reply telegrams



1.3.1 SFU_SB0

The status byte SFU_SB0 informs the master about the status of the frequency con-verter via separate status bits.

SFU_DONEBy adapting the bit SFU_DONE to the bit CMD_VALID the master is informedthat the execution of a command is finished.

SFU_ACKNBy adapting the bit SFU_ACKN to the bit CMD_VALID the master is informedthat the command has been received and that it will be executed.

SFU_ERRThe bit indicates whether a command error or a malfunction of the unit oc-curred. The bit SFU_ERR must only be evaluated after the command hasbeen finished.Then SFU_DONE and SFU_ACKN are adapted to CMD_VALID. In this case,the byte SFU_SB2 contains the error code.

SFU_HBEATThe heartbeat bit SFU_HBEAT can be used for monitoring the frequency con-verter. For this, the master toggles the bit CMD_HBEAT and monitors whetherthe frequency converter has adapted the bit SFU_HBEAT after a defined time.

Byte# Name Meaning0 SFU_SB0 Status byte 0

Bit number Name Meaning0 SFU_DONE Command finished, toggle1 SFU_ACKN Command received, toggle2 SFU_ERR Error message3456 SFU_HBEAT Heartbeat-Bit7

1 SFU_SB1 Status byte 1Bit number Name Meaning

01 SFU_RUN Ready for operation2 SFU_ON Controller activated34 SFU_V_ZERO Ramp generator = Zero56 SFU_V_OK Ramp generator = reference value7 SFU_I_LIMIT Peak current

2 SFU_SB2 Status byte 2, error and message codes3 SFU_SB3 Status byte 3, state of the digital outputs 1 to 8 (bit 0 to 7)

4 to 7 SFU_PAR Command return value



1.3.2 SFU_SB1

The status byte SFU_SB1 informs the master about the status of the frequency con-verter via separate status bits.

SFU_RUNThis bit will be set if the frequency converter is in the operational mode AUTO-MATIC.

SFU_ONThe bit indicates whether the output stage is activated (SFU_ON = 1) or deac-tivated (SFU_ON = 0).

SFU_V_ZEROIf SFU_V_ZERO = 1, the ramp generator has the value 0.

SFU_V_OKThe bit SFU_V_OK indicates that the ramp generator has reached the refer-ence value.

SFU_I_LIMITThe bit SFU_I_LIMIT will be set when the frequency converter is within the cur-rent limitation.

1.3.3 SFU_SB2

If bit SFU_ERR is set, SFU_SB2 contains an error code. If bit SFU_ERR is not set,SFU_SB2 contains a message code. An error code always overwrites a messagecode.

1.3.4 SFU_SB3

This status byte transmits messages back to the master (see table).

1.3.5 SFU_PAR

After request by respective commands, the frequency converter transmits a 32 bitparameter to the master. The parameter is only valid, when SFU_ACKN is equal toSFU_DONE.



1.4 Handshake between Master and Slave

The handshake between master and frequency converter is generated by trackingthe bits SFU_ACKN and SFU_DONE to the master bit CMD_VALID. The followingdiagram shows the time dependent cycle of a sequence of commands.

Command cycle

Command 1:[1] The master toggles the CMD_VALID bit after creating a command in the

CMD_BYTE bit. Both can also be done in the same prompt telegram.[2] After adapting SFU_DONE the frequency converter provides current re-

turn values in the double word SFU_PAR.[3] If the command has been finished, the frequency converter will adapt

SFU_DONE to CNC_VALID. Thus, the master will get the informationabout the finished command. If an error occurs in the frequency convert-er during this time, SFU_DONE will be adapted to CMD_VALID. Thenthe error code will be transmitted to the master by SFU_SB1.SFU_ERRand SFU_SB1 do not contain valid data until SFU_DONE is adapted toCMD_VALID.



1.5 Commands

1.5.1 Command 1, Delete Error (ERR_RES)

By means of this command error codes can be deleted. The frequency converterdoes not execute any drive functions before an error has been acknowledged. Whenthe error is still current during the execution of the command, the error code is setagain. Error codes can only be deleted after the corresponding cause of error hasbeen eliminated. By no means the error may be reset automatically. Commandsused to remove an error status can be executed despite of the set error code.

The command will only be executed when:the operating mode of the FC is set to AUTOMATIC (SFU_RUN = 1)

Command numberCMD_BYTE = 1

Condition of callSFU_RUN = 1

Return value after the command is finished:SFU_ERR = 1 -> error

SFU_SB2 = SFU_ERR

1.5.2 Command 5, Traverse Speed (MOVE)

This command can move the drive with a preset speed.

The command will only be executed when:SFU_RUN = 1the output stage is activated (SFU_ON=1)there is no interferences (SFU_ERR=0)

The command will only be finished whenan interferences occurredor the command has been canceled (CMD_Byte unequal to 5 or the bitCMD_VALID has been toggled)



SFU_ON = 1

SFU_ERR = 0

Parameters of callCMD_PAR = reference speed in rpm / 10



Return value during the execution

Return value after the command is finishedSFU_V_ZERO = 1, when actual speed = Null

SFU_PAR =

SFU_ERR = 1 -> error

SFU_SB2 = CNC_ERR = 1 -> error code

1.5.3 Command 32, Controller Off (REG_OFF)

By means of this command the output stage will be deactivated.The command will only be executed when:

SFU_RUN = 1



Return value after the command is finishedSFU_ERR = last state

SFU_SB2 = last error code

SFU_ON = 0

Actual current value A/100 Actual speed value 1/min/10



1.5.4 Command 33, Controller On (REG_ON)

By means of this command the output stage will be switched on. The position refer-ence value will be set to the actual position value that was valid when switching on.The command will also be carried out when there is an error code. The drive will notbe moved.

The command will only be executed when:SFU_RUN = 1

The command will only be finished whenan interferences occurredthe output stage is switched on.



Parameters of callSFU_INIT = 0

Return value after the command is finishedSFU_ERR = 1 -> error

SFU_SB2 = CNC_ERR = 1 -> error code, CNC_ERR = 0 -> message code


Configuration of the PLC (S7)

2 Configuration of the PLC (S7)

2.1 Setup of the Anybus GSD-File.

Please refer to the SIMATIC documentation for information on the integration ofGSD-files.

2.2 Configuration of an Anybus Participant.

Start the hardware configuration (HW Config) of the SIMATIC software. You find the entry ANYBUS-C PDP in the hardware catalog below AdditionalField Devices General. Move the entry ANYBUS-C PDP to your fieldbus and define the number of theProfibus.

Move the universal module using the „drag and drop“ method in the module listto configure the data. Doubleclick on the universal module to open the configuration so that you candefine the data width and direction.


Configuration of the PLC (S7)

Set the parameters of the universal module as follows:

Confirm the selection by click on OK.

The participant is configured now. After the download of the configura-tion into the PLC, it can be employed.

Parameters Value that must be setI/O type Out- InputAddress Depends on your configurationLength 8Unit ByteConsistent over Total length


Anybus Communicator by HMS

3 Anybus Communicator by HMS

Detailed information on Anybus Communicator is to find in the HMS user manual(www.anybus.com).

3.1 Connectors, Switches and Indicators

LED indicators

Configuration switches A, BSet the Profibus node address by using the switches as follows: Node address = (switch B × 10) + (switch A × 1)

LED no Status Meaning1 - Online Green Online

Off Not online2 - Offline Red Offline

Off Not offline3 - Not used – –4 - Fieldbus Diagnos-tics

Off No diagnostics presentRed, flashing 1 Hz Error in configurationRed, flashing 2 Hz Error in user parameter dataRed, flashing 4 Hz Error in initialization

5 - Subnet Status Flashing green Running, but one or more transaction errorsGreen RunningRed Transaction error/timeout or subnet stopped

6 - Device Status Off Power offAlternating red/green

Invalid or missing configuration

Green InitializationFlashing green RunningRed Boot loader modeFlashing red Note the flash sequence pattern and contact the HMS support

department.


http://www.anybus.com/


Profibus connector

Power connector

Notes Use 60/75 or 75 °C copper (Cu) wire only.The terminal tightening torque must be between 5…7 lbs-in (0.5…0.8 Nm).

PC connector (RJ11)

Subnetwork connector

3.2 Setup

3.2.1 Accessories Checklist

The following items are required for installation:Anybus Communicator (ABC) for ProfibusAnybus Communicator Resource CD (includes configuration software, manuals,GSD file and application notes)

Female submin D connector

Pin Description

Housing Cable shield1 –2 –3 B-line4 RTS5 GND bus6 +5 V bus out7 –8 A-line9 –

Connector Pin Description1 + 24 V DC2 GND

RJ11 male connector Pin Description1 GND2 GND3 RS232 Rx4 RS232 Tx

Female submin D connector

Pin Description

Housing Cable shield1 +5 V output (max. 100 mA)2 RS232 Rx3 RS232 Tx4 –5 GND Signal6 RS422 Rx+7 RS422 Rx-8 RS485+ / RS422 Tx+9 RS485- / RS422 Tx-



RS232 configuration cableSubnetwork connectorProfibus network cable and connector (not included)

3.2.2 Installation and Startup Summary

Mount the Anybus Communicator on the DIN rail.Connect the Communicator to the Profibus network.Connect the module to the subnetwork.Turn on the module (+24 V DC).Connect the configuration cable between the module and the PC containing the"Anybus Configuration Manager" software.Configure the module using "Anybus Configuration Manager".Include the Anybus Communicator GSD file in the Profibus configuration tool.Configure and start the Profibus network.

3.2.3 Technical Specification

Mechanical propertiesHousing Plastic housing with snap-on connection for DIN-rail

IP Code IP20Dimensions (L × B × H) 120 × 75 × 27 mm

Electrical characteristicsPower supply 24 V DC ±10 %Power consumption max. 280 mA at 24 V (typically around 100 mA)

Environmental characteristicsRelative humidity 5 – 95 % non-condensingTemperature Operating: 0 to + 55 °C

Non operating: -25 to +85 °C



3.3 Functional Description

Anybus Communicator for Profibus is a Profibus-DP slave module. The gateway isdesigned to exchange data between a serial subnetwork and a higher level network.It supports all common baud rates up to 12 Mbit (detected automatically). The I/Odata size can be up to 244 bytes in each direction, max. 416 bytes total.

In the following example, a temperature regulator on the subnetwork exchanges in-formation with a PLC on the higher level network, via the internal memory buffers inthe Anybus Communicator.


FC8x - SIEB & MEYER · :Protocol Description FC8x Profibus Communication 3 1 Protocol Description...

Documents

Transcript of FC8x - SIEB & MEYER · :Protocol Description FC8x Profibus Communication 3 1 Protocol Description...