7034 12 PDF

Configuring a Profibus DP
Segment Commander SE
EMERSON Process Management Educational Services Copyrighted Material / Duplication Prohibited

EMERSON Process Management Educational Services Course 7034 - Rev 6 - 3/15/04 Copyrighted Material / Duplication Prohibited
16-2
Objectives
Upon completion of this training module you will be able to
y Add and connect Profibus DP interface card
y Add a Profibus DP device to the Library
y Add a Profibus DP device slot and modules
y Use diagnostics
y Configure a control module for the Profibus device.
y Verify operation of Profibus device and control module using On-Line
16-3
Profibus DP Interface Card
LED's:
Green On powered and self tests are good.
Red Failed and/or not communicating to the controller.
Yellow (top port 1)
Off Not enabled, not communicating or
no configuration for this port.
Blinking - Communication problem exists.
On Good communications and at least one
device is configured on the port
Yellow (bottom port 2) Reserved
1 2 3 4 5 6 7 8
A1 G B1 A2 G B2
16-4
Adding a New Profibus DP Card
DeltaV_System System Configuration Physical Network
Control Network CTLR IO New Card
A maximum of 16 Profibus cards may be connected

to one controller.
16-5
Enabling a Profibus DP Port
16-6
Using DeltaV Explorer
A Profibus DP card has one port available. Enter the following characteristics when the
General Properties dialog box appears:
y Enable Checking this box enables the port to be the master on the network.
y Description Up to 40 characters for a description to appear in Explorer.
y Action in event of controller failure:
Stop scanning When scanning is stopped the slave devices will use their
failsafe settings depending on their Watchdog Timer setting.
Continue scanning The Profibus DP card continues to update the slave
devices with their last settings.
y Baud rate Select the appropriate baud rate. It must be valid for all slave
devices.
y Address 1..125 Note: The preference is 1
16-7
16-8
Enter the following characteristics when the Advanced Properties dialog box appears:
y Repeater on segment ? Checking this box confirms that there are repeaters on
the network. This is necessary for Profibus to perform internal calculations for
communications activity.
y FMS device on segment This is reserved for future use. Therefore, DO NOT
CHECK this box.
y All other boxes DO NOT CHECK or CHANGE the values of these boxes.
These fields do not have a restore limits function. Their values should only be
changed based on a recommendation from Emerson Process Management.
16-9
Adding Profibus Devices in the Library
Library (right mouse) Profibus Devices Add Device Definition Look in
select the location for the new devices GSD files
16-10
16-11
Adding a Profibus Device to a Port
Select PO1 and right click the New Profibus Device menu option. Browse the I/O
selection in the Profibus Library for vendor name, the device added to the port, and the
devices revision information as illustrated below.
16-12
Vendor name
Device added
to the port
Device revision
information
16-13
Adding a Profibus Device
16-14
The new devices default name is PDT?. You may rename the device at this time or
rename it later. Enter the following characteristics when the Properties dialog box
appears:
y Enable Checking this box enables the device to communicate with the master
following download.
y Address 1..125 (must match the devices hardware address)
y Watchdog Timer
Enabled Check this box to set a time to reset the protocol state and
invoke any device failure in the event of a communications failure.
Time Enter a time following a communication failure that a device
failure action occurs.
16-15
Adding a Profibus Slot
Selected Module
16-16
Selecting the Profibus device and right clicking the New Profibus Slot or module menu
option displays the New Profibus Slot dialog box.
The New Profibus Slot or module dialog box displays a list of Profibus modules
available for this device. Listed are Profibus modules that are currently installed or will
be installed in the future. Add a Profibus module to a slot by selecting the module and
clicking the OK button.
The Commander SE displays a list of Profibus modules to select from. The module to
configure is the Cyc=3W, NCyc=Mode 1, full cons for the example system.
The Commander SE Profibus-DP interface automatically detects the required data
format when the master initializes the network.
Three Cyclic Words with Mode 1 Non-Cyclic data (with or without consistency) is the
data format used for the example system.
16-17
Adding a New Profibus Input Signal
Diagnostic channel
Signal Tag
if available on device
Signal direction Byte offset

Data type
16-18
Adding a New Profibus Input Signal
Selecting the Profibus slot and right clicking the New Profibus Signal menu option
displays the New Profibus Signal dialog box containing the following options:
y Description A description containing a maximum of 40 characters
y Use diagnostic channel Check this box to associate a channel with this signal
for diagnostics if supported by the device, Commander SE does not support this.
y Signal Tag Enter the Signal Tag you want to associate with this channel. Click
Browse to see the available tags.
y Data Mapping:
Standard Network byte order Check this if the device reads data starting
with the most significant byte.
Signal direction Select whether it is an input or an output signal
Byte offset Select the starting input or output byte location. Refer to the
device documentation for this information.
Data type Select from floating point, Boolean or integer values. Refer to
vendor documentation for this information.
16-19
Commander SE in Word Data Format
16 BIT WORD
BYTE 1 BYTE 0
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
NON CYCLIC DATA WORD 0
BYTE 3 BYTE 2
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
STATUS WORD WORD 1
BYTE 5 BYTE 4
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
POST RAMP SPEED WORD 2
BYTE 7 BYTE 6
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
MOTOR LOAD WORD 3
16-20
Commander SE Status Word
BIT DESCRIPTION DRIVE STOP DRIVE RUN DRIVE RUN BINARY

FREQ =0 FREQ =0 FREQ > 0 VALUE
0 DRIVE HEALTHY 1 1 1 1
1 DRIVE RUNNING 0 1 1 2
2 ZERO SPEED 1 1 0 4
3 RUNNING AT OR BELOW 0 1 0 8
SPEED
4 BELOW SPEED 0 0 0 16
5 AT SPEED 0 1 1 32
6 ABOVE SET SPEED 0 0 0 64
7 LOAD REACHED 0 0 0 128
BINARY WEIGHT 5 47 35
16-21
Adding a New Profibus Output Signal
16-22
Adding a New Profibus Output Signal
for diagnostics if supported by the device, Commander SE does not support this.
y Signal Tag Enter the Signal Tag you want to associate with this channel.
Click Browse to see the available tags.
y Data Mapping:
Standard Network byte order Check this if the device reads data starting
with the most significant byte.
Data type Select from floating point, Boolean or integer values. Refer to
vendor documentation for this information.
16-23
Commander SE Outword Data Format
16 BIT WORD
BYTE 1 BYTE 0
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
NON CYCLIC DATA WORD 0
BYTE 3 BYTE 2
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
CONTROL WORD WORD 1
BYTE 5 BYTE 4
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
DIGITAL SPEED REF WORD 2
BYTE 7 BYTE 6
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
NOT MAPPED WORD 3
16-24
Commander SE Control Word
BYTE 3 BYTE 2
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
NOT USED
RESET MASK ENABLE

RUN
FORWARD
y BIT O Enable must be set to 1 to put Commander in the Ready mode

y BIT 1 Set to 1 with Enable set to 1 in order to run the motor in the forward
direction
y BIT 4 Set bit to 1 to allow Profibus DP to control the drive
y BIT 6 Set bit to 1 to reset the Commander from a trip condition
16-25
Profibus DP Diagnostics
16-26
Using DeltaV Diagnostics
Selecting the Profibus device and right clicking the Display Device Information menu
option displays the Profibus Device Information dialog box. This dialog box contains
nine tabs for device-specific information. If the device supports extended diagnostics,
such as the ET 200S and all or some of the available diagnostic parameters have been
enabled, this information will appear.
y General tab A check is placed adjacent to the fault detected by the device.
y Device, Slot and Signal tabs Display the detected faults enabled at the time of
configuration. These tabs are advanced diagnostics that are device-specific.
Refer to device documentation for specific information.
y Diag Msg, Input, Output, Config and Param tabs are a moment in time
capture. By using the update button available, these parameters can be refreshed
at the time of viewing. Intended for advanced Profibus users, refer to device
documentation for specific information.
Note: Extended Diagnostics are not available on the Commander SE device.
16-27

Selecting the device slot will display the
y Signal names
y Value on signal
y overall integrity
y status
y DST
16-28
16-29
Workshop
Verify communications
Step 1. Connect the Commander SE VFD to the Profibus DP Interface card in slot 7
using the purple cable supplied in the simulator.
Step 2. Add the Profibus card using DeltaV Explorer.
Step 3. Enable Port 1 and download the the Profibus Card.
Step 4. Add a Profibus (slave) device using the Commander SE module from the
Profibus Library. Rename to Device.
Step 5. Right mouse click, properties. Check the enable box, select address 5.
Step 6. Add a Profibus slot matching the existing hardware. Cyc=3, Ncyc=Mode 1,
full cons.
Step 7. Add New Profibus Signal. Signal Tag-STAT_IN, Signal direction-Input, Byte
Offset-2, Data Type-16 bit unsigned integer. Re-name Signal001 to STATUS.
16-30
Workshop
Step 8. Add New Profibus Signal. Signal Tag-CONTROL_OUT, Signal direction-
Output, Byte Offset-2, Data Type-16 bit unsigned integer. Re-name Signal002
to CONTROL.
Step 9. Add New Profibus Signal. Signal Tag-SPEED_REF, Signal direction-Output,
Byte Offset-4, Data Type-16 bit unsigned integer. Re-name Signal003 to
Speed.
Step 10. Download Profibus PO1.
Step 11. Verify the configuration by using the DeltaV Diagnostics and make use of the
Profibus Device information that all statuses are good. The front display of the
Commander SE VFD should read rd in the left hand window and 0.0 in the
right hand window.
16-31
n
Workshop
n External Reference DST/CTLR/Speed_Ref/out

o External Reference DST/CTLR/Control_Out/Out
p External Reference DST/CTLR//Stat_IN/field_val
16-32
Workshop
Adding a Profibus Module
Step 1. Add a module Profibus as shown above.
a. Drag and drop the module template named Commander SE from the
Module Library. The path is Module Template Communications-Busses
Commander SE.
b. Rename module Commander
c. Open Commander using Control Studio
Step 2. Select parameter name SPEED, edit object, parameter type-External Reference
and browse for parameter path DST CTLR SPEED-REF OUT.
Step 3. Select parameter name CNTRL_WORD, edit object, parameter type-External
Reference and browse parameter path DST CTLR CONTROL-OUT
OUT.
16-33
Workshop
Adding Profibus Module
Step 4. Select parameter name STATUS, edit object, parameter type External Reference
and browse for parameter path DST CTLR STAT_IN FIELD_VAL.
Step 5. Select parameter name Enable, edit object and select True.
Step 6. Select parameter name Mask, edit object and select True.
Step 7. Assign module properties, assign to controller, save and download.
16-34
Workshop
Verifying Control Module and Device operation
Step 1. Select the Control Module Commander and OPEN it using Control Studio
On-Line.
Note: If the Commander module is already OPEN go on-line in the studio application.
Step 2. Select the DC1 function block and double click SP_D in the parameter window.
Select Start from the Named Set drop down menu.
Step 3. Double click the parameter name FREQ and enter a value from 0 to 60. Verify
that the Commander SE VFD is displaying FR in the left window and the
Frequency Value is displayed in the right window.
Note: If the Commander SE does not START, set SP_D to STOP then toggle parameters
mask and enable from TRUE to FALSE and back to TRUE again. Double click SP_D and
select START from the drop down window.
16-35
Workshop
Verifying Control Module and Device operation
Step 4. Optional Add the Commander SE module to the DeltaV Operate display.
Step 5. Optional Verify operations from DeltaV Operate display.
Hint: Use the Dynamo set FRSModules to START and STOP the drive. Place Data Links
on the display for Frequency and other parameters you would like to interface with.
16-36
Considerations for Writing Output Signals
If you are writing output signals to a Profibus, DeviceNet or AS-Interface device that
has been configured for failsafe action, be sure your control module is configured to
track the failsafe action in the device should it occur. For example, if communication
between the DeltaV system and the device is disrupted the device itself may drive its
outputs to a failsafe state. The DeltaV system must know this has occurred and take
appropriate action so that outputs are not driven to the last good state by the DeltaV
system when communication with the device is restored. Configure your control module
so that this happens, because the Profibus, DeviceNet, and AS_Interface standards do
not support readback of output values.
Profibus DP, DeviceNet and AS-Interface output signals should be written in control
modules by means of an external reference parameter, which writes the value to the I/O
card even when signal status is Bad. If you use a Profibus DP, DeviceNet or AS-
Interface DST reference in function blocks such as AO, DO, PID, and DC the value is
not written when signal status is Bad. It is important for the control module to be able to
write the failsafe value to the I/O card when the Profibus DP, DeviceNet or AS-Interface
device is in the failsafe state, to prevent a bump when the failsafe state has cleared.
16-37
If your Profibus DP, DeviceNet or AS-Interface device goes to a failsafe state due to a
failure in the device or a loss of communication with the DeltaV system, the status of its
DSTs in the DeltaV system is Bad. The figure above shows a technique for analog
outputs using a DeltaV PID function block. A condition function block detects Bad
status in the output DST and after the failsafe time duration, causes the PID block output
to track the failsafe value in the device. After the failsafe state in the device clears, the
PID block initializes from the failsafe value.
16-38
The figure above shows a similar technique for a discrete output using the Device
Control function block. The condition block is used in the same way as in the figure. In
this case the DC block becomes interlocked to the 0 (passive) state when the device goes
to failsafe state. When the failsafe state clears, SP_D and CAS_IN_D are in the passive
state, and can be written to the active state at the appropriate time.
16-39
The figure above illustrates using the condition block when you are writing the discrete
output with Boolean or expression logic. Whether the output is maintained or pulsed, the
idea is to be sure the output is the device failsafe value when the device is in the failsafe
state.
16-40
Configuring a Profibus DP
Segment Siemens I/O
EMERSON Process Management Educational Services Copyrighted Material / Duplication Prohibited

16-42
Objectives
Upon completion of this training module you will be able to
y Add and connect Profibus DP interface card
y Add a Profibus DP device to the Library
y Add a Profibus DP device slot and modules
y Use diagnostics
16-43
Profibus DP Interface Card
LED's:
Green On powered and self tests are good.
Red Failed and/or not communicating to the controller.
Yellow (top port 1)
Off Not enabled, not communicating or
no configuration for this port.
Blinking - Communication problem exists.
On Good communications and at least one
device is configured on the port
Yellow (bottom port 2) Reserved
1 2 3 4 5 6 7 8
A1 G B1 A2 G B2
16-44
Adding a New Profibus DP Card
DeltaV_System System Configuration Physical Network
Control Network CTLR IO New Card
A maximum of 16 Profibus cards may be connected

to one controller.
16-45
16-46
A Profibus DP card has one port available. Enter the following characteristics when the
General Properties dialog box appears:
y Enable Checking this box enables the port to be the master on the network.
y Action in event of controller failure:
Stop scanning When scanning is stopped the slave devices will use their
failsafe settings depending on their Watchdog Timer setting.
Continue scanning The Profibus DP card continues to update the slave
devices with their last settings.
y Baud rate Select the appropriate baud rate. It must be valid for all slave
devices.
y Address 1..125 Note: The preference is 1
16-47
16-48
Enter the following characteristics when the Advanced Properties dialog box appears:
y Repeater on segment ? Checking this box confirms that there are repeaters on
the network. This is necessary for Profibus to perform internal calculations for
communications activity.
y FMS device on segment This is reserved for future use. Therefore,
DO NOT CHECK this box.
y All other boxes DO NOT CHECK/CHANGE the values of these boxes. These
fields do not have a restore limits function. Their values should only be changed
based on a recommendation from Emerson Process Management.
16-49
Adding Profibus Devices in the Library
Library (right mouse) Profibus Devices Add Device Definition Look in
select the location for the new devices GSD files
16-50
16-51
Select PO1 and right click the New Profibus Device menu option. Browse the I/O
selection in the Profibus Library for vendor name, the device added to the port, and the
devices revision information as illustrated below.
16-52
Vendor name
Device added
to the port
Device revision
information
16-53
16-54
The new devices default name is PDT?. You may rename the device at this time or
rename it later. Enter the following characteristics when the Properties dialog box
appears:
y Enable Checking this box enables the device to communicate with the master
following download
y Address 1..125 (must match device hardware address)
y Watchdog Timer
Enabled Check this box to set a time to reset the protocol state and
invoke any device failure in the event of a communication failure.
Time Enter a time following a communication failure that a device
failure action occurs
16-55
Enabling Device-specific Parameters
16-56
Enabling Device-specific Parameters
Depending on the Profibus device type and vendor, there may be parameters available
for identifying device-specific behavior and diagnostics. Refer to specific device
vendors documentation for such information.
For our example, Siemens ET 200S remote I/O devices have two parameters that can be
enabled for determining device behavior:
y Start-up preset<>actual config
y Module change during operation
By selecting and enabling these two parameters you can add, delete/remove and replace
I/O modules during operation of the device without affecting other I/O modules
operation.
16-57
Selected Card
16-58
Selecting the Profibus device and right clicking the New Profibus Slot menu option
displays the New Profibus Slot dialog box.
The New Profibus Slot dialog box displays a list of Profibus modules available for this
device. Listed are Profibus modules that are currently installed or will be installed in the
future. Add a Profibus module to a slot by selecting the module and clicking the OK
button.
The ET 200S displays a list of Profibus modules to select from. The first slot to
configure is the power module GES7 138-4CB00-AB0 PM-E AC230 for the example
system.
16-59
Enabled for display in

DeltaV Diagnostics
16-60
The ET 200S Profibus devices power card offers two diagnostic parameters:
y Diag Missing load voltage L+
y Diagnosis Fuse blown
By selecting and enabling these parameters, extended diagnostics will be displayed in
the DeltaV diagnostics application.
Note: Not all devices support extended diagnostics. Refer to the venders specifications
for detailed information regarding device diagnostic parameters.
16-61
16-62
The New Profibus Slot dialog boxs Configuration Summary tracks how your selections
affect the available bytes, slot space and configuration space for this device. Shown
above is the summary for the ET 200S device. It displays the Used, Remaining and
Maximum allowed information for
y Input, Output and Total bytes
y Number of slots
y Parameter bytes
y Config size
The above elements are dynamic and will change as you add slots to, or delete slots
from, the device. According to the illustration above, the device has a maximum Config
size of 244 bytes.
This dialog box is totally device-type dependant; selections change depending on the
specific device type. This windows choices must match the Profibus device hardware in
the field.
16-63
16-64
Select the I/O module from the list that matches the I/O module installed in Slot 2. In the
example above, the I/O module is a GES7 132BBOO-OABO 2DO DC24V.
16-65
Enabled for display in

DeltaV Diagnostics
16-66
y Behavior at CPU-STOP Choose either Hold last value or Switch substitute
value. This selection is I/O module and device specific.
y Substitute value 00 If the Switch substitute value parameter is selected, you
may enter either a 0 or 1 value to be substituted for this output in case of CPU-
STOP. This is available for both channels of this I/O module.
y Diagnosis Wire break 00 This Diagnostic parameter can be enabled or
disabled for both output channels. However, it must be ENABLED to be
displayed in DeltaV diagnostics that supports the devices extended diagnostics.
y Diag Short circuit to M 00 This Diagnostic parameter can be enabled or
disabled for both output channels. However, it must be ENABLED to be
16-67
Only select cards without an asterisk *
16-68
Select the I/O module from the list that matches the I/O module installed in Slot 3. In the
example above, the I/O module is a GES7 131-4BB00-0AB0 2DI DC24V.
16-69
Enabled for display in DeltaV Diagnostics

16-70
y Input delay An I/O module parameter with choices in milliseconds of
1ms, 3ms and 15ms. Refer to device manufacturers documentation for details.
y Diag Short circuit to GND This Diagnostic parameter can be enabled or
disabled for both input channels. However, it must be ENABLED to be
Note: Select cards without an asterisk *. The asterisk indicates a special data
compression which DeltaV does not currently support.
16-71
Adding a New Profibus Signal
16-72
for diagnostics if supported by the device
y Signal Tag Enter the Signal Tag you want to associate with this channel.
Click Browse to see the available tags.
y Data Mapping:
Standard Network byte order Check this if the device reads data
starting with the most significant byte.
Data type Select from floating point, Boolean or integer values. Refer
to vendor documentation for this information.
16-73
Use diagnostic channel and First bit used must match to enable the DeltaV Diagnostics.
16-74
y Use Scaling Check this box to scale the values 0% and 100% scale for
the DeltaV System.
y Bit pattern Specify the first bit for DeltaV to read from or write to. This bit
must match the diagnostic channel, for example channel 0 and bit 0, or channel 1
and bit 1. Refer to device documentation for specific information.
y Number of used bits Specify the number of bits that the DeltaV system reads
from or writes to for this signal. Refer to the device documentation for this
information.
16-75
16-76
Selecting the Profibus device and right clicking the Display Device Information menu
option displays the Profibus Device Information dialog box. This dialog box contains
nine tabs for device-specific information. If the device supports extended diagnostics,
such as the ET 200S and all or some of the available diagnostic parameters have been
enabled, this information will appear.
y General tab A check is placed adjacent to the fault detected by the device.
y Device, Slot and Signal tabs Display the detected faults enabled at the time of
configuration. These tabs are advanced diagnostics that are device-specific.
Refer to device documentation for specific information.
y Diag Msg, Input, Output, Config and Param tabs are a moment in time
capture. By using the update button available, these parameters can be refreshed
at the time of viewing. Intended for advanced Profibus users, refer to device
documentation for specific information.
16-77
16-78
16-79
16-80
16-81
16-82
16-83
Workshop
Step 1. Add the Profibus DP Interface card in slot 7 using the DeltaV Explorer.
Step 2. Enable Port 1 and download the Card 7.
Step 3. Add a Profibus (slave) device using the V1.5 (ET 200S). Set the address at 3
and check the enabled box.
Step 4. Add three Profibus slots matching the existing hardware. Enable the
diagnostics for the slots.
Step 5. Add all Profibus Module Signals.
Profibus Device information.
16-84
Workshop
16-85
Workshop
Verify configuration
Step 1. Add a control module for Profibus Siemens I/O as shown above.
Step 2. Verify the configuration by setting one or both DO function blocks value to 1.
Step 3. Disconnect one of the wires between DO and DI.
Profibus Device information and Extended Diagnostics.
Step 5. Optional for the user to add the Siemens I/O control module to the DeltaV
Operate display.
Step 6. Optional for the user to verify operations from the DeltaV Operate display by
adding data links to the display to represent DO and DI values.
16-86
If you are writing output signals to a Profibus, DeviceNet or AS-Interface device that
has been configured for failsafe action, be sure your control module is configured to
track the failsafe action in the device should it occur. For example, if communication
between the DeltaV system and the device is disrupted the device itself may drive its
outputs to a failsafe state. The DeltaV system must know this has occurred and take
appropriate action so that outputs are not driven to the last good state by the DeltaV
system when communication with the device is restored. Configure your control module
so that this happens, because the Profibus, DeviceNet, and AS_Interface standards do
not support readback of output values.
Profibus DP, DeviceNet and AS-Interface output signals should be written in control
modules by means of an external reference parameter, which writes the value to the I/O
card even when signal status is Bad. If you use a Profibus DP, DeviceNet or AS-
Interface DST reference in function blocks such as AO, DO, PID, and DC the value is
not written when signal status is Bad. It is important for the control module to be able to
write the failsafe value to the I/O card when the Profibus DP, DeviceNet or AS-Interface
device is in the failsafe state, to prevent a bump when the failsafe state has cleared.
16-87
If your Profibus DP, DeviceNet or AS-Interface device goes to a failsafe state due to a
failure in the device or a loss of communication with the DeltaV system, the status of its
DSTs in the DeltaV system is Bad. The figure above shows a technique for analog
outputs using a DeltaV PID function block. A condition function block detects Bad
status in the output DST and after the failsafe time duration, causes the PID block output
to track the failsafe value in the device. After the failsafe state in the device clears, the
PID block initializes from the failsafe value.
16-88
The figure above shows a similar technique for a discrete output using the Device
Control function block. The condition block is used in the same way as in the figure. In
this case the DC block becomes interlocked to the 0 (passive) state when the device goes
to failsafe state. When the failsafe state clears, SP_D and CAS_IN_D are in the passive
state, and can be written to the active state at the appropriate time.
16-89
The figure above illustrates using the condition block when you are writing the discrete
output with Boolean or expression logic. Whether the output is maintained or pulsed, the
idea is to be sure the output is the device failsafe value when the device is in the failsafe
state.
16-90

7034 12 PDF

Uploaded by

Copyright:

Available Formats

7034 12 PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

7034 12 PDF

Uploaded by

Copyright:

Available Formats

How do you add and configure a Profibus DP interface card?

How do you add and configure a Profibus DP interface card?

What are some considerations when writing output signals to a Profibus DP device?

What are some considerations when writing output signals to a Profibus DP device?

Configuring a Profibus DP

EMERSON Process Management Educational Services Copyrighted Material / Duplication Prohibited

A maximum of 16 Profibus cards may be connected

Signal direction Byte offset

BIT DESCRIPTION DRIVE STOP DRIVE RUN DRIVE RUN BINARY

6 ABOVE SET SPEED 0 0 0 64

7 LOAD REACHED 0 0 0 128

RESET MASK ENABLE

y BIT O Enable must be set to 1 to put Commander in the Ready mode

Using DeltaV Diagnostics

n External Reference DST/CTLR/Speed_Ref/out

EMERSON Process Management Educational Services Copyrighted Material / Duplication Prohibited

A maximum of 16 Profibus cards may be connected

Enabled for display in

Enabled for display in

Only select cards without an asterisk *

Enabled for display in DeltaV Diagnostics

You might also like