Anybus-IC PROFIBUS: Fieldbus Appendix
Anybus-IC PROFIBUS: Fieldbus Appendix
Anybus-IC PROFIBUS: Fieldbus Appendix
Anybus-IC PROFIBUS
Doc.ID. SCM-1200-022
Rev 2.00
Connecting DevicesTM
+$/067$'&+,&$*2.$5/658+(72.<2%(,-,1*0,/$1208/+286(&29(175<381(&23(1+$*(1
Liability
Every care has been taken in the preparation of this manual. Please inform HMS Industrial Networks AB of any
inaccuracies or omissions. The data and illustrations found in this document are not binding. We, HMS Industrial
Networks AB, reserve the right to modify our products in line with our policy of continuous product development.
The information in this document is subject to change without notice and should not be considered as a commit-
ment by HMS Industrial Networks AB. HMS Industrial Networks AB assumes no responsibility for any errors that
may appear in this document.
There are many application of this product. Those responsible for the use of this device must ensure that all the
necessary steps have been taken to verify that the application meets all performance and safety requirements in-
cluding any applicable laws, regulations, codes, and standards
HMS Industrial Networks AB will under no circumstances assume liability or responsibility for any problems that
may arise as a result from the use of undocumented features, timing, or functional side effects found outside the
documented scope of this product. The effects caused by any direct or indirect use of such aspects of the product
are undefined, and may include e.g. compatibility issues and stability issues.
The examples and illustrations in this document are included solely for illustrative purposes. Because of the many
variables and requirements associated with any particular implementation, HMS Industrial Networks AB cannot
assume responsibility for actual use based on these examples and illustrations.
HMS Industrial Networks AB has intellectual property rights relating to technology embodied in the product de-
scribed in this document. These intellectual property rights may include patents and pending patent applications
in the US and other countries.
Trademark Acknowledgements
Anybus ® is a registered trademark of HMS Industrial Networks AB. All other trademarks are the property of their
respective holders.
Warning: This is a class A product. in a domestic environment this product may cause radio interference in
which case the user may be required to take adequate measures.
ESD Note: This product contains ESD (Electrostatic Discharge) sensitive parts that may be damaged if ESD
control procedures are not followed. Static control precautions are required when handling the prod-
uct. Failure to observe this may cause damage to the product.
Table of Contents
Related Documents
Document name Author
Anybus-IC Design Guide HMS
Digital Communications IEC61158 Type 3 (PROFIBUS) IEC
Document History
Change Page(s)
New format -
Updated frontpage information -
Updates sales and support information 7
Miscellaneous corrections -
Revision List
Anybus-IC PROFIBUS
Doc.Rev. 2.00 Doc.Id. SCM-1200-022
About This Document 6
Anybus-IC PROFIBUS
Doc.Rev. 2.00 Doc.Id. SCM-1200-022
About This Document 7
Anybus-IC PROFIBUS
Doc.Rev. 2.00 Doc.Id. SCM-1200-022
Chapter 1
General
The Anybus-IC PROFIBUS communication module provides instant PROFIBUS slave connectivity
through the generic Anybus-IC application interface. Any device that supports this standard can take
advantage of the features provided by the module, allowing seamless network integration regardless of
network type.
Features
• Galvanically isolated bus electronics
• Up to 144 bytes of fieldbus I/O in each direction
• Automatically detects the PROFIBUS baud rate
• User parametrization data support
• Extended diagnostic support
• Set Slave Address support
• Device identity customization
• Generic GSD file provided
Any deviations from what is stated above will require changes in the GSD file and thus also recertifica-
tion of the end product. For further information, please contact HMS.
Anybus-IC PROFIBUS
Doc.Rev. 2.00 Doc.Id. SCM-1200-022
Chapter 2
Basic Operation
General Information
Software Requirements
Generally, no network specific support code needs to be written in order to support the Anybus-IC
PROFIBUS. However, due to natural reasons, advanced fieldbus specific features may require the use
of PROFIBUS specific parameters.
For general information about the Anybus-IC software interface, consult the Anybus-IC Design Guide.
See also...
• “Fieldbus Specific Parameters” on page 18
GSD-files
On PROFIBUS, the characteristics of a device is stored in an ASCII data file with the suffix ‘GSD’. This
file is used by the PROFIBUS configuration tool when setting up the network.
HMS provides a generic GSD file, which corresponds to the default settings in the module. However,
due to the flexible nature of the Anybus concept, it is possible to alter the behavior of the product in
ways that invalidates the generic GSD file.
See also...
• “Fieldbus Conformance Notes” on page 8
Identity Information
On the PROFIBUS network, the module identifies itself as follows:
See also...
• “PROFIBUS ID Number Config (Parameter #107)” on page 23
• “PROFIBUS ID Number Actual (Parameter #108)” on page 24
Data Exchange
The module supports up to 144 bytes of fieldbus I/O in each direction.
All fieldbus I/O data is exchanged as cyclical I/O on PROFIBUS.
Anybus-IC PROFIBUS
Doc.Rev. 2.00 Doc.Id. SCM-1200-022
Basic Operation 10
Communication Settings
Baud Rate
See also...
• “PROFIBUS Baud Rate Actual (Parameter #106)” on page 23
Node Address
feature is supported by the generic GSD file, and is FBNA bit set?
Yes
enabled when any of the following conditions are true: No
1. The node address source is specified by the ‘NA’ bit in parameter #8 (‘Configuration Bits’)
Anybus-IC PROFIBUS
Doc.Rev. 2.00 Doc.Id. SCM-1200-022
Basic Operation 11
The fieldbus specific input is used for fieldbus specific configuration settings and supports two types of
switches/coding.
• BCD-coded Switches
This type of switches allows the PROFIBUS node address to be set in the range 0... 99.
• Binary Switches
This type of switches allows the node address to be set in the range 0... 126 as follows:
b7 b6 b5 b4 b3 b2 b1 b0 Node Address
- 0 0 0 0 0 0 0 0
- 0 0 0 0 0 0 1 1
- 0 0 0 0 0 1 0 2
- 0 0 0 0 0 1 1 3
... ... ... ... ... ... ... ... ...
- 1 1 1 1 1 0 1 125
- 1 1 1 1 1 1 0 126 (reserved for SSA)
- 1 1 1 1 1 1 1 (invalid on PROFIBUS)
Note: The type of switch used is specified in parameter #9 (‘Switch Coding’). On PROFIBUS, the de-
fault value for this parameter is 00h (BCD Switches). However, since this is fieldbus dependent, there is
no guarantee that the same type of switch is used by default on other networks.
See also...
• Anybus-IC Design Guide (parameter #9 ‘Switch Coding’)
• “Communication Settings” on page 10
The fieldbus specific output is used for fieldbus specific status indications as follows:
See also...
• Anybus-IC Design Guide (parameter #7 ‘LED State’)
Anybus-IC PROFIBUS
Doc.Rev. 2.00 Doc.Id. SCM-1200-022
Basic Operation 12
PROFIBUS Implementation
Global Control
The master identifies itself with the slaves by sending parametrization data, specifying how the slave shall
operate (i.e. Master address, PNO-ID, Sync/Freeze capabilities etc.).
The parametrization data consists of two parts:
As seen in the table above, support for additional (i.e. > 1 byte) user parametrization data can optionally
be implemented by supporting the corresponding parameters in the application. Note however that this
invalidates the generic GSD file supplied by HMS.
If enabled, the user parametrization data has to be acknowledged by the application.
See also...
• “Fieldbus Conformance Notes” on page 8
• “Identity Information” on page 9
• “FB Init (Parameter #101)” on page 20
• “User Parametrization Data Length (Parameter #111)” on page 24
• “User Parametrization Data (Parameter #117)” on page 27
Anybus-IC PROFIBUS
Doc.Rev. 2.00 Doc.Id. SCM-1200-022
Basic Operation 13
Extended Diagnostics
In addition to the 6 mandatory diagnostic data bytes, the module supports up to 200 bytes of extended
diagnostic data. This data can be used e.g. to notify the PROFIBUS master of a fault that has occurred
in the application.
The PROFIBUS specification specifies three different types of extended diagnostic data:
• Device related
• Identifier related
• Channel related
The application is responsible for setting up the correct diagnostics prior to sending it to the master.
Consult the PROFIBUS specification for further information about the different diagnostic settings.
Extended diagnostics is not supported by default, but can optionally be supported by implementing sup-
port for the corresponding parameters in the application. Note however that this invalidates the generic
GSD file supplied by HMS.
See also...
• “Fieldbus Conformance Notes” on page 8
• “Identity Information” on page 9
• “FB Init (Parameter #101)” on page 20
• “Extended Diagnostic Length (Parameter #112)” on page 25
• “Extended Diagnostics (Parameter #118)” on page 28
Configuration Data
The Anybus module is a modular slave, which means that the input/output block size is flexible and not
tied to a specific block length. The input/output blocks are specified by so-called identifier bytes, which
defines the input- and/or output data length as well as data consistency. The identifier bytes are defined
in the GSD file and are automatically extracted by the configuration tool when adding modules to the
configuration.
During network startup, the master sends its actual configuration to the Anybus module for validation.
By default, the Anybus module adopts its configuration data from the master (i.e. a mismatch is not pos-
sible, unless the configuration is bigger than the data sizes specified during initialization).
Optionally, the configuration data can be acknowledged by the application (fieldbus specific mode).
See also...
• “Fieldbus Conformance Notes” on page 8
• “Identity Information” on page 9
• “FB Init (Parameter #101)” on page 20
• “Default Config Data Length (Parameter #109)” on page 24
• “Config Data Length (Parameter #110)” on page 24
• “Default Config Data (Parameter #115)” on page 27
• “Config Data (Parameter #116)” on page 27
Anybus-IC PROFIBUS
Doc.Rev. 2.00 Doc.Id. SCM-1200-022
Basic Operation 14
Bus Offline
When the fieldbus is offline, the outputs can behave in different ways depending on the parameter #10
(“Offline Action”) setting.
See also...
• Anybus-IC Design Guide, parameter #10 (‘Offline Action’)
When the fieldbus master issues the global control telegram ‘Clear’, the outputs can behave in different
ways depending on the parameter #11 (“Idle Action”) setting.
Note that input data can be read by the master even if the module is in ‘Clear’-mode.
See also...
• Anybus-IC Design Guide, parameter #11 (‘Idle Action’)
• “Global Control” on page 12
Anybus-IC PROFIBUS
Doc.Rev. 2.00 Doc.Id. SCM-1200-022
Chapter 3
Fieldbus Interface
General Considerations
Make sure to keep the length of the stub lines (i.e. the distance between the PROFIBUS connector and
the Anybus module) as short as possible. If these stub lines are too long, communication problems may
arise when operating at higher bus speeds (>=1.5 Mbps). According to the PROFIBUS Test Specifica-
tion, the max. allowed total length of all stub lines on a bus segment is 80 cm @ 12 Mbps. Over a full
bus segment of 32 nodes, this equals 25 mm.
The recommended connector for PROFIBUS is a 9-pin female DSUB-connector (DB9F). Other con-
nectors are also permitted, as long as all mandatory signals are present.
+5 V BUS and GND BUS are normally used for bus termination, and may be used to power external
devices such as e.g. optical transceivers (RS485 to fibre optics). In any case, such devices may not con-
sume more than 100 mA of current. Also note that these power outputs are not short circuit protected.
Note: Due to the individual requirements (i.e. differences in cable shield filters, max. stub line length
etc.) for each networking system, special care has to be taken if compatibility with several networking
systems is required. It is therefore generally recommended to also study the design examples in the field-
bus appendices for Anybus-IC DeviceNet and Anybus-IC Ethernet/IT/IP.
See also...
• “Fieldbus Conformance Notes” on page 8
• “DB9F Pinout” on page 16
IMPORTANT: The recommendations regarding PE and cable shield filters etc. have been changed slightly compared
to those of older revisions of this document. The module is however fully backwards compatible with the old recommenda-
tions.
Anybus-IC PROFIBUS
Doc.Rev. 2.00 Doc.Id. SCM-1200-022
Fieldbus Interface 16
Typical Implementation
PROFIBUS requires a cable shield filter as shown below. If multiple networks are to be supported using
the same application PCB, this has to be accounted for when routing the board, since other networking
systems may use a different shielding approach.
Max. 25mm
RTS
4 15
+5V BUS
6 20
A Line
8 13
B Line
3 14
GND BUS
5 19
Shield
VCC
1+9
1M GND
24 + 32
Note: To ensure proper EMC behavior, the metal housing DB9F-connector must be connected to Pro-
tective Earth (PE) as illustrated above.
DB9F Pinout
When using a DB9F connector, A-Line, B-Line, +5 V BUS, GND BUS and Shield are mandatory.
When using other connectors, only A-Line, B-Line and Shield are required.
4 RTS 15 FB3
5 GND BUS (isolated) 19 FB5
9 6
6 +5 V BUS (output, isolated, 100 mA max.) 20 FB6
7 - - -
8 A-Line 13 FB1
9 - - -
Housingb Shield - -
See also...
• “Fieldbus Conformance Notes” on page 8
Anybus-IC PROFIBUS
Doc.Rev. 2.00 Doc.Id. SCM-1200-022
Fieldbus Interface 17
Termination Example
It is generally recommended to use PROFIBUS connectors with built-in termination. If this is not pos-
sible, termination can be implemented on-board as illustrated below.
L
A Line Switchable
Bus In Termination
L
B Line +5V BUS
R2 20
L
B Line B Line
R1 14
Bus Out
L
A Line A Line
13
R2
RTS GND BUS VCC
19 1+9
1M
Ref. Description
R1 220 R ± 5%
R2 390 R ± 5%
L 110 nH ± 20%
Anybus-IC PROFIBUS
Doc.Rev. 2.00 Doc.Id. SCM-1200-022
Chapter 4
Note: Byte sized parameter values are placed in the least significant byte of the word.
Anybus-IC PROFIBUS
Doc.Rev. 2.00 Doc.Id. SCM-1200-022
Fieldbus Specific Parameters 19
Bit Layout
• PRM1
This bit indicates if a Set_Prm telegram has been received from the PROFIBUS master.
1: Set_Prm telegram has been received from the PROFIBUS master. The application should
check the received user parametrization data in parameter #117 (“User Parametrization
Data”) and respond by setting/clearing bit 0 of parameter #101 (“FB Init”).
0: Set_Prm telegram has not been received from the PROFIBUS master.
• CFG1
This bit indicates if a Chk_Cfg telegram has been received from the PROFIBUS master.
1: Chk_Cfg telegram has been received from the PROFIBUS master. The application should
check the received configuration data in parameter #116 (“Config Data”) and respond by
setting/clearing bit 1 of parameter #101 (“FB Init”).
0: Chk_Cfg telegram has not been received from the PROFIBUS master.
• BUS
1: Node is online
0: Node is offline
• IDLE
1: Node is in clear mode
0: Node is not in clear mode
1. These bits are only valid when using the fieldbus specific initialization option. For more information, see
“Fieldbus Specific Initialization” on page 30 .
Anybus-IC PROFIBUS
Doc.Rev. 2.00 Doc.Id. SCM-1200-022
Fieldbus Specific Parameters 20
This parameter is used to acknowledge user parametrization data and configuration data received from
the PROFIBUS master when using the fieldbus specific initialization option. For more information, see
“Fieldbus Specific Initialization” on page 30 .
Bit Layout
b7 b6 b5 b4 b3 b2 b1 b0
- - - - - - CFG PRM
• PRM1
This bit is used to accept / reject the user parametrization data found in parameter #117 (“User
Parametrization Data”) when the module has received a Set_Prm telegram from the PROFIBUS
master.
The application should set this bit accordingly after checking the received parametrization data.
1: Accept user parametrization data
0: Reject user parametrization data
• CFG1
This bit is used to accept / reject the configuration data found in parameter #116 (“Config Da-
ta”) when the module has received a Chk_Cfg telegram from the PROFIBUS master.
The application should set this bit accordingly after checking the received configuration.
1: Accept configuration data
0: Reject configuration data
1. These bits are only valid when using the fieldbus specific initialization option. For more information, see
“Fieldbus Specific Initialization” on page 30 .
Anybus-IC PROFIBUS
Doc.Rev. 2.00 Doc.Id. SCM-1200-022
Fieldbus Specific Parameters 21
This parameter grants write access to the following parameters provided that a valid password is sup-
plied:
• “PROFIBUS ID Number Config (Parameter #107)” on page 23
• “Firmware Revision (Parameter #119)” on page 29
• “Serial Number (Parameter #120)” on page 29
(The password can be obtained by contacting HMS)
This parameter holds the manually configured PROFIBUS node address. Note that in order for this val-
ue to be valid, bit 4 of parameter #8 (“Configuration Bits”) must be set. Valid node address settings
range from 0 to 126.
Note: This parameter is read once during startup, i.e. any changes requires a reset in order to have effect.
Anybus-IC PROFIBUS
Doc.Rev. 2.00 Doc.Id. SCM-1200-022
Fieldbus Specific Parameters 22
This parameter holds the automatically configured fieldbus node address from the SSC interface. Note
that in order for this value to be valid, bit 4 of parameter #8 (“Configuration Bits”) must be cleared.
If the SSC node address is larger than allowed by the fieldbus, the default value of parameter #103 (“FB
Node Address Config”) will be used as the actual node address.
Note: This parameter is read once during startup, i.e. any changes requires a reset in order to have effect.
After initialization, this parameter holds the actual fieldbus node address. Prior to module initialization,
the value of this parameter is not defined.
Anybus-IC PROFIBUS
Doc.Rev. 2.00 Doc.Id. SCM-1200-022
Fieldbus Specific Parameters 23
This parameter holds the actual fieldbus baud rate after the Anybus-IC is online. Before the Anybus-IC
is online, the value of this parameter is not defined.
• Value
00h: 12 Mbps 05h: 187.5 kbps
01h: 6 Mbps 06h: 93.75 kbps
02h: 3 Mbps 07h: 45.45 kbps
03h: 1.5 Mbps 08h: 19.2 kbps
04h: 500 kbps 09h: 9.6 kbps
This parameter holds the configured PROFIBUS ID number for the Anybus-IC. The “set default” com-
mand in parameter #1 (“Module mode”) does not affect this parameter if the password is not entered
before the set default is executed. If the parameter is unlocked with the password, and the module is
restarted, the parameter is locked again.
Note: This parameter is password protected. To change its value, a valid password must first be supplied
through parameter #102 (“FB Password”).
Anybus-IC PROFIBUS
Doc.Rev. 2.00 Doc.Id. SCM-1200-022
Fieldbus Specific Parameters 24
This parameter holds the actual PROFIBUS ID number after the Anybus-IC has been initialized. Before
the Anybus-IC is initialized, the value of this parameter is not defined.
This parameter holds the length of the default configuration data sent to the master when a Get_Cfg
telegram is received from the master. The default configuration is entered in parameter #115 (“Default
Config Data”). This register should be updated before the module is initialized in order to have effect.
This parameter holds the configuration data length when the Chk_Cfg telegram is received from the
PROFIBUS master. The data is found in parameter #116 (“Config Data”). Before the Chk_Cfg tele-
gram is received from the PROFIBUS master, the length of the Anybus-IC calculated configuration data
is present here.
This parameter holds the user parametrization data length when the Set_Prm telegram is received from
the PROFIBUS master. The data can be found in parameter #117 (“User Parametrization Data”).
Anybus-IC PROFIBUS
Doc.Rev. 2.00 Doc.Id. SCM-1200-022
Fieldbus Specific Parameters 25
This parameter holds the length (in bytes) of the extended diagnostic data entered in parameter #118
(“Extended Diagnostics”). Note that the indication word (see “Indication Word” on page 28 ) is not
included in this value.
Anybus-IC PROFIBUS
Doc.Rev. 2.00 Doc.Id. SCM-1200-022
Fieldbus Specific Parameters 26
This parameter makes it possible to disable the support for the Set_Slave_Address telegram (SSA).
Note: This functionality is only implemented in firmware revision 1.14 or higher.
• Value
00h: Disable SSA support
(SSA telegrams will be rejected with the error code RS (No resource). The FBNA bit in pa-
rameter #8 will be ignored.)
01h: Enable SSA support
(SSA telegrams will be accepted, and the node address will be stored in parameter #114)
This parameter holds the node address received from the fieldbus via the Set_Slave_Address telegram.
Note: This functionality is only implemented in firmware revision 1.14 or higher.
Anybus-IC PROFIBUS
Doc.Rev. 2.00 Doc.Id. SCM-1200-022
Fieldbus Specific Parameters 27
This parameter holds the default configuration data sent to the master when a Get_Cfg telegram is re-
ceived from the master. The length of the default configuration data is entered in parameter #109 (“De-
fault Config Data Length”).
If no default configuration data is specified in this register, the module will calculate the configuration
data based on the initialized I/O lengths.
This register should be updated before the module is initialized in order to have effect.
This parameter holds the configuration data when the Chk_Cfg telegram is received from the PROFI-
BUS master. The length is found in parameter #110 (“Config Data Length”). Before the Chk_Cfg tel-
egram is received from the PROFIBUS master, the Anybus-IC calculated configuration data is present
here.
This parameter holds the user parametrization data when the Set_Prm telegram is received from the
PROFIBUS master. The length can be found in parameter #111 (“User Parametrization Data Length”).
The first byte of the user parametrization data is reserved for the PROFIBUS ASIC and should always
be left at 0 by the user.
Anybus-IC PROFIBUS
Doc.Rev. 2.00 Doc.Id. SCM-1200-022
Fieldbus Specific Parameters 28
The application can send user specific diagnostics a.k.a. extended diagnostics to the PROFIBUS master.
(See “Extended Diagnostic Data (Slave_Diag)” on page 1 for more information).
The length of the actual extended diagnostic data is specified in parameter #112 (“Extended Diagnostic
Length”).
The first word in the extended diagnostic data field specifies the type of diagnostic data. The data is sent
when this word has been updated, which means that the actual diagnostic data must be written before
this word is updated.
Indication Word
• EXT
1: Extended diagnostic is indicated to the PROFIBUS master.
0: Status diagnostic is indicated to the PROFIBUS master.
• STA
1: Static diagnostic is indicated to the PROFIBUS master.
• OFL
1: Diagnostic overflow is indicated to the PROFIBUS master.
Anybus-IC PROFIBUS
Doc.Rev. 2.00 Doc.Id. SCM-1200-022
Fieldbus Specific Parameters 29
Anybus-IC PROFIBUS
Doc.Rev. 2.00 Doc.Id. SCM-1200-022
Chapter 5
General Information
By default, the application does not need to acknowledge any telegrams from the PROFIBUS master;
all handshaking etc. is handled automatically by the module.
Optionally, the module can be initialized in fieldbus specific mode, offering greater control over user
parametrization data and configuration data. To start the module in this mode, the fieldbus specific in-
itialization option in parameter #1 (“Module Mode”) is used.
#1 Module mode =
0002h
NAK
(#101 FB_Init Bit 0&1=0)
STATE 1
Waiting for parameter
data NAK
NAK (#101 FB_Init Bit 0&1=0)
NAK
(#101 FB_Init Bit 0=0) (#101 FB_Init Bit 0=0)
Set_Prm received
(#100 FB_Status Bit 0=1)
Evaluate User
Parameter Data
#111 Usr Prm Data Len
#117 User Param Data
Set_Prm received
(#100 FB_Status Bit 0=1)
ACK
(#101 FB_Init Bit 0=1)
STATE 2
Waiting for config data
Chk_Cfg received
(#100 FB_Status Bit 1=1)
Evaluate
Configuration Data
#110 Cfg Data Len
#116 Config
ACK ACK
#101 FB_Init Bit 0=1 ACK (#101 FB_Init Bit 1=1) Check config data
(#101 FB_Init Bit 1=1)
#110 Cfg Data Len
#116 Config
Check parameter data
#111 Usr Prm Data Len
#117 User Param Data
STATE 3
Chk_Cfg received
(#100 FB_Status Bit 1=1)
Set_Prm received
(#100 FB_Status Bit 0=1)
Anybus-IC PROFIBUS
Doc.Rev. 2.00 Doc.Id. SCM-1200-022
Fieldbus Specific Initialization 31
The module awaits the parametrization data from the PROFIBUS master. When received (indicated by
bit #0 of parameter #100 (‘Fieldbus Status’)), the application must evaluate the user parametrization
data by checking parameters #111 (‘Usr Prm Data Len’) and #117 (‘User Param Data’).
• If the user parametrization data is ok, the application shall accept the telegram by setting bit 0 of
parameter #101 (“FB Init”). The application shall then enter STATE 2.
• If the user parametrization data is not ok, the application shall reject the telegram by clearing bit
0 of parameter #101 (“FB Init”). The application shall then remain in STATE 1.
STATE 2
The module awaits configuration data from the PROFIBUS master. When received (indicated by bit #1
of parameter #100 (‘Fieldbus Status’)), the application must evaluate the configuration data by checking
parameters #110 (‘Cfg Data Len’) and #116 (‘Config Data’).
• If the configuration data is ok, the application shall accept the telegram by setting bit 1 of param-
eter #101 (“FB Init”). The application shall then enter STATE 3.
• If the configuration data is not ok, the application shall reject the telegram by clearing bits 0 and
1 of parameter #101 (“FB Init”). The application shall then return to STATE 1 and expect a new
initialization sequence.
STATE 3
This state handles all PROFIBUS telegrams received after the initialization is finished and is also the
‘normal’ runtime state. The bus is online and exchanging I/O data in this state.
• If a ‘SET_PRM’-telegram is received, the application must evaluate the user parametrization da-
ta. If the user parametrization data is ok, the application shall remain in STATE 3.
If the user parametrization data is not ok, the application shall return to STATE 1 and expect a
new initialization sequence.
• If a ‘CHK_CFG’-telegram is received, the application must evaluate the configuration data. If
the configuration data is ok, the application shall remain in STATE 3.
If the configuration data is not ok, the application shall return to STATE 1 and expect a new
initialization sequence.
Note: If the fieldbus goes offline and then back to online (e.g. if the fieldbus connector is temporarily discon-
nected and then reconnected again), the initialization sequence must restart from STATE 1 again.
Note: If both the ‘SET_PRM’- and ‘CHK_CFG’-telegrams are received, and the application accepts both tel-
egrams, it is possible to acknowledge both simultaneously by writing 03h to parameter #101 (‘FB Init’).
This is only allowed when both telegrams shall be acknowledged. If any of the telegrams shall be reject-
ed, it must be made one at a time in the order described in the flowchart on the previous page.
Note: If the CHK_CFG telegram shall be rejected, both bits (#0 and #1) of parameter #101 (‘FB Init’) must
be cleared.
Anybus-IC PROFIBUS
Doc.Rev. 2.00 Doc.Id. SCM-1200-022
Appendix A
Technical Specification
Electrical Specification
Power Supply
Supply Voltage
The module requires a regulated 5 V ± 5% DC power supply as specified in the Anybus-IC Design
Guide.
Power Consumption
The maximum power consumption is 150 mA.
Environmental Specification
• Temperature
Test performed according to IEC-68-2-1 and IEC 68-2-2.
Operating: -40 to +85 °C (-40 to +185 °F).
Storage: -40 to +85 °C (-40 to +185 °F).
• Humidity
The product is designed for a relative humidity of 5 to 95% noncondensing.
Test performed according to IEC 68-2-30.
• Emission: EN 61000-6-4
Tested perEN 55016-2-3
• Immunity: EN 61000-6-2
Tested perEN 61000-4-2
EN 61000-4-3
EN 61000-4-4
EN 61000-4-5
EN 61000-4-6
Anybus-IC PROFIBUS
Doc.Rev. 2.00 Doc.Id. SCM-1200-022