Emerson Exchange 365

• Not Answered

Profibus DP Siemens s7-300 deltav

The problem I have now is that although achievement set the Profibus DP communicationbetween DCS DeltaV emerson and plc S7-300 either by the integrated dp or the CP342-5, I can not get data from any party Please I need to know how to handle within the S7 andthe DeltaV digital inputs and both analog outputs as they are in the gsd files. in the case ofthe CPU with integrated dp configure Slots accomplishment but do not get data. but in the case of the CP342-5 as a slave as not configure virtual slot. finally here-S7 ConnectionDeltaV apparently is a common question but I have not seen in the support files a sample program for this type of connection if you have one that meets this requirement please do me directions.

PROFIBUS DEVICE SUMMARY - 19:11 Friday, April 11, 2014

Device Name      LO

------ ----      --

Vendor Name      SIEMENS

Model Name       CP 342-5

----- ----       -- -----

Revision         V1.0

 

General

-------

                 Station Non-Existent                                    NO

                 Station Not Ready                                       NO

                 Configuration Fault                                     NO

                 Master Lock                                             NO

                 Parameter Fault                                         NO

                 Invalid Slave Response                                  NO

                 Not Supported                                           NO

                 Extended Diagnostics                                    NO

                 Deactivated                                             NO

                 Sync Mode                                               NO

                 Freeze Mode                                             NO

                 Watchdog On                                             YES           1000ms

                 Slave                                                   YES

                 Static Diagnostics                                      NO

                 Parameterize Request                                    NO

                 Extended Diagnostics Overflow                           NO

                 Device Ident                                            0x80d6

                 Device State                                            Online

                 Master Address                                          1

Device

------

Slot

Signal

------

                 Signal                                 Error

Diagnostic Message Detail

---------- ------- ------

                 Variable                               Value

Diag Msg

---- ---

                 Station Status 1: 0x00

                 Station Status 2: 0x0c

                 Station Status 3: 0x00

                 Device Master Address: 0x01

                 High Byte Of Identifier: 0x80

                 Low Byte Of Identifier: 0xd6

                 No Extended Diagnostic Data

Input

-----

                 

Output

------

                 

Config

------

                 

Param

-----

                 Status Byte To Slave: 0x88

                 Watchdog Factor 1 To Slave: 0x64

                 Watchdog Factor 2 To Slave: 0x01

                 Response Delay Time (tbit) To Slave: 0x0b

                 High Byte ID Value To Slave: 0x80

                 Low Byte ID Value To Slave 0xd6

                 Group ID To Slave 0x00

                 User Parameters:

                 Byte 001 - 003: 0x40  0x00  0x00 

ot configure virtual slot. finally here-S7 ConnectionDeltaV apparently is a common question but I have not seen in the support files a sample program for this type of connection if you have one that meets this requirement please do me directions.

• Profibus

ojven

• 13 Apr 2014 6:56 PM
• Cancel

1 Reply

• Niklas Flykt

  

  • 14 Apr 2014 12:23 PM

  Hi,

  Could you give some more data e.g. some screen shots from both sides settings?

  Do you have blinking LED:s bus fault?

  You could recheck the siemens side by reading: support.automation.siemens.com/.../llisapi.dll

  It is really important that you have the lengt of the communication right, there can´t be any differences on either sides.

  also see: www.youtube.com/watch

  Here are some information borrowed from other instances:

  Configuration Parameters
  
  Slot Configuration
  
  In DeltaV first 3 slots are to be created for 1st, 2nd and 3rd general ID and are reserved. These 3 slots with no I/O signals are required to be configured in DeltaV for housekeeping purposes. These slots are not configured in the PLC. DeltaV user data slots start at slot 4. PLC user data definition starts from slot 1. The slots assignments for the user data in DeltaV and the PLC must match.
  
  Tables 3.1 and 3.2 describe the various slot types that can be configured. The slot definition comprises of 3 parts: part 1 defines the direction of data transfer, I stands for Input and Q stands for Output, part 2 defines the slot length and part 3 defines the data format. E.g. Slot definition Master_I Slave_Q 4 B tot lgth means this is Input to Master and Output(Q) from Slave and has 4 Bytes of total length.

  Slot configuration limiting values
  
  In DeltaV maximum of 32 slots per PLC for user data exchange can be configured starting from Slot 4 to Slot 35. These Slots can be freely mixed. However the same sequence and slot type should be available on the PLC for communication to be established and these are numbered from 1 to 32. Following table lists the maximum data exchange for a PLC over Profibus.

  In the PLC configuration 32 slots can defined for user data exchange and they need to match DeltaV configuration. The Type I stands for Input and Q stands for Output. Output from DeltaV is Input to PLC and vice-versa. While assigning Master Addresses continuous addressing is to be defined for Inputs and Outputs. These addresses are not significant for DeltaV as there are no Address areas in the DeltaV.
  
  Note : When the CPU of the PLC goes to STOP mode, data in the CPU intermediate memory are overwritten with “0” that is, DeltaV reads its inputs as “0”. However when the Profibus communication stops the CPU intermediate memory is maintained and the CPU uses the stale data. Therefore it is advised to have a life signal in the communication which takes care of this issue.

  Configuration Rules
  
  The following rules apply:

  1. It is mandatory to ensure the PLC and DeltaV slot configurations are identical (see section 3.1)
  2. Integer and floating point signals held in PLC data blocks must start on an even number byte offset. Values held in byte oriented memory can start on any byte.
  3. It is not necessary to configure all signals in DeltaV.

  
  
  Configuring DeltaV
  
  The following steps are required to configure an instance of a PLC in the DeltaV I/O database:
  

  1. Select the GSD file corresponding to the S7 hardware model from the Siemens internet site (see section 2.3)
  2. Add the S7 device to the DeltaV Profibus library
  3. Create an instance of a device on a Profibus I/O port
  4. Add slots to the device to match the PLC slot configuration
  5. Add the required signals to the slots.

  Error reporting and recovery
  
  In case of communication failure the status of the DST is set to BADNOCOM and it can be used in the Control Module for interlocking.
  
  Recovery of communication with the PLC is automatic.

  there is a document on the E-net : http://www.plctalk.net/qanda/attachment.php?s=282fe718226fa5e7abbf8e2b3a8ae42a&attachmentid=5655&d=1156136099 but you first have to register

  Niklas Flykt 

  Klinkmann Oy
  

  Key Account Manager safety products

  nikfly@gmail.com

  • Cancel