8/18/2008 9:40 AM | |
Joined: 9/28/2005 Last visit: 8/27/2024 Posts: 2957 Rating:
|
Hello, I think you must check new configuration on DCS side. Is everything ok there? Adding new slot to Profibus MS protocol isn't a big deal, but it must be correct at both sides. By the way, maybe you can attach configuration at Siemens side? |
Best regards, |
|
8/18/2008 9:45 AM | |
Posts: 5 Rating:
|
here is my HW configuration at siemens side |
Last edited by: bashar662 at: 8/18/2008 9:47 AMLast edited by: bashar662 at: 8/18/2008 9:47 AM |
|
8/18/2008 9:53 AM | |
Joined: 9/28/2005 Last visit: 8/27/2024 Posts: 2957 Rating:
|
Please, send config where I can see these MS slots |
Best regards, |
|
8/18/2008 10:01 AM | |
Posts: 5 Rating:
|
Pls reffer to atachment |
8/18/2008 10:21 AM | |
Joined: 9/28/2005 Last visit: 8/27/2024 Posts: 2957 Rating:
|
Its seems everythg ok. Amount of data is ok. Are you sure everything is ok at DCS side ? Maybe it can't support such amount of data? I'm sure everything would be okif you use other Siemens PLC as your third party DCS system with the same config. I suggest you to check DCS side. |
Best regards, |
|
8/18/2008 10:39 AM | |
Posts: 5 Rating:
|
Below is the copy of the diagnostic error. Hope some one can guide us to solve this error. Event 1 of 10: Event ID 16# 4302Mode 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 operationCurrent/last startup type:- Warm restart triggered via MPI; last power on backed upPermissibility of certain startup types:- Manual warm restart permitted- Automatic warm restart permittedLast 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: RUNIncoming event03:45:55:271 am 09/30/97Event 2 of 10: Event ID 16# 1381Request 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 operationCurrent/last startup type: - Warm restart triggered via MPI; last power on backed upPermissibility of certain startup types: - Manual warm restart permitted- Automatic warm restart permittedLast 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: 27Incoming event03:45:55:269 am 09/30/97Event 3 of 10: Event ID 16# 4301Mode 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 operationCurrent/last startup type:- Warm restart triggered via MPI; last power on backed upPermissibility of certain startup types:- Manual warm restart permitted- Automatic warm restart permittedLast 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 event03:45:54:591 am 09/30/97Event 4 of 10: Event ID 16# 5371Distributed I/Os: end of the synchronization with a DP master Slot of the DP master: 2 Number of distributed stations: 0Incoming event03:45:43:055 am 09/30/97Event 5 of 10: Event ID 16# 4304STOP caused by PG stop operation or by SFB 20 "STOP" Previous operating mode: RUN Requested operating mode: STOP (internal)Incoming event03:45:15:396 am 09/30/97Event 6 of 10: Event ID 16# 4302Mode 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 operationCurrent/last startup type:- Warm restart triggered via MPI; last power on backed upPermissibility of certain startup types:- Manual warm restart permitted- Automatic warm restart permittedLast 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: RUNIncoming event03:40:15:270 am 09/30/97Event 7 of 10: Event ID 16# 1381Request 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 operationCurrent/last startup type: - Warm restart triggered via MPI; last power on backed upPermissibility of certain startup types: - Manual warm restart permitted- Automatic warm restart permittedLast 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: 27Incoming event03:40:15:268 am 09/30/97Event 8 of 10: Event ID 16# 4301Mode 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 operationCurrent/last startup type:- Warm restart triggered via MPI; last power on backed upPermissibility of certain startup types:- Manual warm restart permitted- Automatic warm restart permittedLast 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 event03:40:14:587 am 09/30/97Event 9 of 10: Event ID 16# 5371Distributed I/Os: end of the synchronization with a DP master Slot of the DP master: 2 Number of distributed stations: 0Incoming event03:40:03:011 am 09/30/97Event 10 of 10: Event ID 16# 4304STOP caused by PG stop operation or by SFB 20 "STOP" Previous operating mode: RUN Requested operating mode: STOP (internal)Incoming event03:39:37:314 am 09/30/97 So:
I’m waiting your reply with best regards. |
Last edited by: bashar662 at: 8/18/2008 10:45 AM |
|
8/18/2008 10:44 AM | |
Joined: 9/28/2005 Last visit: 8/27/2024 Posts: 2957 Rating:
|
How do you read/write ? Do you use PIW/PQW or some SFC ? |
Best regards, |
|
8/18/2008 10:52 AM | |
Posts: 5 Rating:
|
Thanks Darius I use PIW/PQW with code L IB T QB |
8/18/2008 1:17 PM | |
Joined: 9/28/2005 Last visit: 8/27/2024 Posts: 2957 Rating:
|
Thats strange then. The diagnostic says that something's wrong with system configuration. How do you transfered new HW config ? From START mode or in STOP mode? Maybe you should try to reload HW configuration in STOP mode and then try to set it in RUN mode and then send diagnostic data here again. |
Best regards, |
|
Follow us on