You are not registered yet. Please click here to register!


 
 
plc storereviewsdownloads
This board is for PLC Related Q&A ONLY. Please DON'T use it for advertising, etc.
 
Try our online PLC Simulator- FREE.  Click here now to try it.

---------->>>>>Get FREE PLC Programming Tips

New Here? Please read this important info!!!


Go Back   PLCS.net - Interactive Q & A > PLCS.net - Interactive Q & A > LIVE PLC Questions And Answers

PLC training tools sale

Reply
 
Thread Tools Display Modes
Old August 16th, 2008, 07:24 AM   #1
gh_ounie
Member
Syria

gh_ounie is offline
 
Join Date: Dec 2007
Location: aleppo
Posts: 73
profibus problem

Dear all , good day



Our system is S7315-2DP, and the DP is define as DP Slave, connected to DCS system from another company we transfer the data between two (master and slave) through Profibus MS protocol (slot 4,5,6)
And the system is working fine without any problem for more than three years.
Now, we need to send more information from PLC to DCS, so we add a new MS slot (slot 7), , and then I download it to PLC


The PLC after that is still working in Run mode but the BF and SF LED are ON, and all the data communication between DCS and PLC was lost.
  Reply With Quote
Old August 17th, 2008, 09:19 AM   #2
JesperMP
Lifetime Supporting Member + Moderator
Denmark

JesperMP is offline
 
JesperMP's Avatar
 
Join Date: Feb 2003
Location: Copenhagen.
Posts: 14,193
gh ounie.

1st, I think you should post the diagnostic buffer in this thread.
The PM you sent me contained 2 links, one to some kind of program that I dont want to open, and the other to a RAR file with probably the diagnostics buffer. Unfortunately I cannot open RAR files, so I think you should just post it as a ZIP file.

Now is this problem with the same PLC and DCS as the other thread ?
If so, then I am genuinly confused, because in that thread you talk about a Yokogawa DCS and an S7 PLC connected together as master-to-master via a DP coupler (each partner sees the other partner as a slave).

If this is another project, and it is really an S7 setup as a DP slave, then my best guess at the moment is that only one side is correctly setup.
The full diagnostics buffer will probably tell us more.
__________________
Jesper
See my profile interests for Q&A
  Reply With Quote
Old August 17th, 2008, 09:40 AM   #3
gh_ounie
Member
Syria

gh_ounie is offline
 
Join Date: Dec 2007
Location: aleppo
Posts: 73
i'm so sorry to confused you and i'm realy appreciate your helping this is a new project and this is the

Diagnostic buffer of module CPU 315-2 DP -part 1

Order No./ Description Component Version

6ES7 315-2AG10-0AB0 Hardware 3

- - - Firmware V 2.0.8

rack: 0

Slot: 2

Event 1 of 10: Event ID 16# 4302

Mode transition from STARTUP to RUN

Startup information:

- Startup with modified system configuration

- Difference between setpoint and actual configuration

- Time for time stamp at the last backed up power on

- Single processor operation

Current/last startup type:

- Warm restart triggered via MPI; last power on backed up

Permissibility of certain startup types:

- Manual warm restart permitted

- Automatic warm restart permitted

Last valid operation or setting of automatic startup type at power on:

- Warm restart triggered via MPI; last power on backed up

Previous operating mode: STARTUP (warm restart)

Requested operating mode: RUN

Incoming event

03:45:55:271 am 09/30/97

Event 2 of 10: Event ID 16# 1381

Request for manual warm restart

STOP due to: STOP caused by PG stop operation or by SFB 20 "STOP"

Startup information:

- Startup with modified system configuration

- Difference between setpoint and actual configuration

- Time for time stamp at the last backed up power on

- Single processor operation

Current/last startup type:

- Warm restart triggered via MPI; last power on backed up

Permissibility of certain startup types:

- Manual warm restart permitted

- Automatic warm restart permitted

Last valid operation or setting of automatic startup type at power on:

- Warm restart triggered via MPI; last power on backed up

Requested OB: Startup OB (OB100)

Priority class: 27

Incoming event
03:45:55:269 am 09/30/97
Event 3 of 10: Event ID 16# 4301

Mode transition from STOP to STARTUP

STOP due to: STOP caused by PG stop operation or by SFB 20 "STOP"

Startup information:

- Startup with modified system configuration

- Difference between setpoint and actual configuration

- Time for time stamp at the last backed up power on

- Single processor operation

Current/last startup type:

- Warm restart triggered via MPI; last power on backed up

Permissibility of certain startup types:

- Manual warm restart permitted

- Automatic warm restart permitted

Last valid operation or setting of the automatic startup type at power on:

- Warm restart triggered via MPI; last power on backed up

Previous operating mode: STOP (internal)

Requested operating mode: STARTUP (warm restart)

Incoming event

03:45:54:591 am 09/30/97

Event 4 of 10: Event ID 16# 5371

Distributed I/Os: end of the synchronization with a DP master

Slot of the DP master: 2

Number of distributed stations: 0

Incoming event

03:45:43:055 am 09/30/97

Event 5 of 10: Event ID 16# 4304

STOP caused by PG stop operation or by SFB 20 "STOP"

Previous operating mode: RUN

Requested operating mode: STOP (internal)

Incoming event

03:45:15:396 am 09/30/97



So:
  • What is the problem?
  • There are any things to do or modify in our PLC or user program or any SFC or DB,Ö
Iím waiting your reply with best regards.
  Reply With Quote
Old August 17th, 2008, 09:40 AM   #4
gh_ounie
Member
Syria

gh_ounie is offline
 
Join Date: Dec 2007
Location: aleppo
Posts: 73
and this is a part 2

Event 6 of 10: Event ID 16# 4302

Mode transition from STARTUP to RUN

Startup information:

- Startup with modified system configuration

- Difference between setpoint and actual configuration

- Time for time stamp at the last backed up power on

- Single processor operation

Current/last startup type:

- Warm restart triggered via MPI; last power on backed up

Permissibility of certain startup types:

- Manual warm restart permitted

- Automatic warm restart permitted

Last valid operation or setting of automatic startup type at power on:

- Warm restart triggered via MPI; last power on backed up

Previous operating mode: STARTUP (warm restart)

Requested operating mode: RUN

Incoming event

03:40:15:270 am 09/30/97





Event 7 of 10: Event ID 16# 1381

Request for manual warm restart

STOP due to: STOP caused by PG stop operation or by SFB 20 "STOP"

Startup information:

- Startup with modified system configuration

- Difference between setpoint and actual configuration

- Time for time stamp at the last backed up power on

- Single processor operation

Current/last startup type:

- Warm restart triggered via MPI; last power on backed up

Permissibility of certain startup types:

- Manual warm restart permitted

- Automatic warm restart permitted

Last valid operation or setting of automatic startup type at power on:

- Warm restart triggered via MPI; last power on backed up

Requested OB: Startup OB (OB100)

Priority class: 27

Incoming event

03:40:15:268 am 09/30/97





Event 8 of 10: Event ID 16# 4301

Mode transition from STOP to STARTUP

STOP due to: STOP caused by PG stop operation or by SFB 20 "STOP"

Startup information:

- Startup with modified system configuration

- Difference between setpoint and actual configuration

- Time for time stamp at the last backed up power on

- Single processor operation

Current/last startup type:

- Warm restart triggered via MPI; last power on backed up

Permissibility of certain startup types:

- Manual warm restart permitted

- Automatic warm restart permitted

Last valid operation or setting of the automatic startup type at power on:

- Warm restart triggered via MPI; last power on backed up

Previous operating mode: STOP (internal)

Requested operating mode: STARTUP (warm restart)

Incoming event

03:40:14:587 am 09/30/97





Event 9 of 10: Event ID 16# 5371

Distributed I/Os: end of the synchronization with a DP master

Slot of the DP master: 2

Number of distributed stations: 0

Incoming event

03:40:03:011 am 09/30/97





Event 10 of 10: Event ID 16# 4304

STOP caused by PG stop operation or by SFB 20 "STOP"

Previous operating mode: RUN

Requested operating mode: STOP (internal)

Incoming event

03:39:37:314 am 09/30/97
Event 6 of 10: Event ID 16# 4302

Mode transition from STARTUP to RUN

Startup information:

- Startup with modified system configuration

- Difference between setpoint and actual configuration

- Time for time stamp at the last backed up power on

- Single processor operation

Current/last startup type:

- Warm restart triggered via MPI; last power on backed up

Permissibility of certain startup types:

- Manual warm restart permitted

- Automatic warm restart permitted

Last valid operation or setting of automatic startup type at power on:

- Warm restart triggered via MPI; last power on backed up

Previous operating mode: STARTUP (warm restart)

Requested operating mode: RUN

Incoming event

03:40:15:270 am 09/30/97





Event 7 of 10: Event ID 16# 1381

Request for manual warm restart

STOP due to: STOP caused by PG stop operation or by SFB 20 "STOP"

Startup information:

- Startup with modified system configuration

- Difference between setpoint and actual configuration

- Time for time stamp at the last backed up power on

- Single processor operation

Current/last startup type:

- Warm restart triggered via MPI; last power on backed up

Permissibility of certain startup types:

- Manual warm restart permitted

- Automatic warm restart permitted

Last valid operation or setting of automatic startup type at power on:

- Warm restart triggered via MPI; last power on backed up

Requested OB: Startup OB (OB100)

Priority class: 27

Incoming event

03:40:15:268 am 09/30/97





Event 8 of 10: Event ID 16# 4301

Mode transition from STOP to STARTUP

STOP due to: STOP caused by PG stop operation or by SFB 20 "STOP"

Startup information:

- Startup with modified system configuration

- Difference between setpoint and actual configuration

- Time for time stamp at the last backed up power on

- Single processor operation

Current/last startup type:

- Warm restart triggered via MPI; last power on backed up

Permissibility of certain startup types:

- Manual warm restart permitted

- Automatic warm restart permitted

Last valid operation or setting of the automatic startup type at power on:

- Warm restart triggered via MPI; last power on backed up

Previous operating mode: STOP (internal)

Requested operating mode: STARTUP (warm restart)

Incoming event

03:40:14:587 am 09/30/97





Event 9 of 10: Event ID 16# 5371

Distributed I/Os: end of the synchronization with a DP master

Slot of the DP master: 2

Number of distributed stations: 0

Incoming event

03:40:03:011 am 09/30/97





Event 10 of 10: Event ID 16# 4304

STOP caused by PG stop operation or by SFB 20 "STOP"

Previous operating mode: RUN

Requested operating mode: STOP (internal)

Incoming event

03:39:37:314 am 09/30/97

Last edited by gh_ounie; August 17th, 2008 at 10:00 AM.
  Reply With Quote
Old August 17th, 2008, 09:49 AM   #5
JesperMP
Lifetime Supporting Member + Moderator
Denmark

JesperMP is offline
 
JesperMP's Avatar
 
Join Date: Feb 2003
Location: Copenhagen.
Posts: 14,193
Is this the same as the other thread, or is it a different problem ?

Did you update the DCS partner in the same way as the S7 PLC ?

The diagnostics buffer does not say so much.
Only one I can see is the "difference between setpoint and actual configuration".
Maybe it means that the partner isnt configured in the same way.
Try to get "help for event".

In entry 9 it says:
Distributed I/Os: end of the synchronization with a DP master
Slot of the DP master: 2

Number of distributed stations: 0
This also interesting. Try get "help for event".
__________________
Jesper
See my profile interests for Q&A
  Reply With Quote
Old August 17th, 2008, 10:14 AM   #6
gh_ounie
Member
Syria

gh_ounie is offline
 
Join Date: Dec 2007
Location: aleppo
Posts: 73
Hi Jesper MP
it's another task
and we are just trying to configure the slave and then we have had this problem
Imag of my configuration





Last edited by gh_ounie; August 17th, 2008 at 10:36 AM.
  Reply With Quote
Old August 17th, 2008, 01:13 PM   #7
JesperMP
Lifetime Supporting Member + Moderator
Denmark

JesperMP is offline
 
JesperMP's Avatar
 
Join Date: Feb 2003
Location: Copenhagen.
Posts: 14,193
Did you setup the partner so that the changes are mirrored ?
__________________
Jesper
See my profile interests for Q&A
  Reply With Quote
Old August 17th, 2008, 01:29 PM   #8
gh_ounie
Member
Syria

gh_ounie is offline
 
Join Date: Dec 2007
Location: aleppo
Posts: 73
of course i did asyou told me other thread virtule out put in plc become virtule input in Dcs

regarding to event 9 this what i found "help of event"
This event indicates the end of the start-up synchronization of the DP master. If this event does not occur within the monitoring time you have set for the module ready message, the CPU forces the end of the DP master start-up synchronization. The detailed information shows the number of stations that have indicated that they are ready
  Reply With Quote
Old August 17th, 2008, 01:33 PM   #9
JesperMP
Lifetime Supporting Member + Moderator
Denmark

JesperMP is offline
 
JesperMP's Avatar
 
Join Date: Feb 2003
Location: Copenhagen.
Posts: 14,193
Try to investigate the help for event for the "difference between setpoint and actual configuration" entries.
__________________
Jesper
See my profile interests for Q&A
  Reply With Quote
Old August 18th, 2008, 03:25 AM   #10
gh_ounie
Member
Syria

gh_ounie is offline
 
Join Date: Dec 2007
Location: aleppo
Posts: 73
Many thanks Jesper for your time

This is what i found

The event is only generated if stations are missing at the end of the startup synchronization of the DP master and a setpoint/actual difference is not permitted.

The number of existing stations is always registered as zero in the event.

Last edited by gh_ounie; August 18th, 2008 at 03:28 AM.
  Reply With Quote
Old August 18th, 2008, 03:31 AM   #11
JesperMP
Lifetime Supporting Member + Moderator
Denmark

JesperMP is offline
 
JesperMP's Avatar
 
Join Date: Feb 2003
Location: Copenhagen.
Posts: 14,193
I dont know the particular error message, so it is mostly guesssing.

The wording sounds to me that the DP port is setup to be a master, but according to your description, the S7 PLC is a slave to the DCS.

Maybe you can post the archived S7 project (.zip file !).
__________________
Jesper
See my profile interests for Q&A
  Reply With Quote
Reply
Jump to Live PLC Question and Answer Forum

Bookmarks


Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 
Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Topics
Thread Thread Starter Forum Replies Last Post
Problem with Profibus carlos57 LIVE PLC Questions And Answers 38 July 30th, 2010 09:41 PM
Profibus Citect com problem pacak LIVE PLC Questions And Answers 1 March 4th, 2008 07:00 AM
Profibus PA problem (E+H Flowmeter) owenmaher LIVE PLC Questions And Answers 2 September 4th, 2006 02:09 AM
Electronic shaft Simovert & Profibus Prince LIVE PLC Questions And Answers 11 August 31st, 2005 01:04 AM
Ab Plc5 Rio Problem. fernandes LIVE PLC Questions And Answers 5 March 7th, 2004 01:25 PM


All times are GMT -5. The time now is 06:56 AM.


.