| View previous topic :: View next topic |
| Author |
Message |
sandy201684
Junior
Joined: 16 Nov 2016
Posts: 14
|
 Posted: 24/12/2016 09:43 Post subject: Siemens S7-300 -dp slave not ready for data exchange yet |
 |
|
Hi experts,
I have a problem in site...PLC panel was working perfectly for one year after that there was a short circuit in the next cabinet of PLC . then PLC and IM rack showing SF and BF fault
now we have downloaded the original backup to PLC and still showing the error we have tried the following methods
1.changed profibus cable
2.changed dp connector
while online it is showing "dp slave not ready for data exchange yet" |
|
| Back to top |
|
 |
go
Member
Joined: 26 Mar 2015
Posts: 147
|
| Posted: 24/12/2016 10:52 Post subject: Re: Siemens S7-300 -dp slave not ready for data exchange yet |
|
|
| sandy201684 wrote: | Hi experts,
I have a problem in site...PLC panel was working perfectly for one year after that there was a short circuit in the next cabinet of PLC . then PLC and IM rack showing SF and BF fault
now we have downloaded the autentic backup to PLC and still showing the error we have tried the following methods
1.changed profibus cable
2.changed dp connector
while online it is showing "dp slave not ready for data exchange yet" |
What do you read on Diagnostic Buffer of CPU S7-300.
What is your configuration exactly ..you are connected from the CPU to IM or have a Communication processor.
What is the state of LEDs on CPU(CP) and IM.
Put exactly your configuration as in NetPro and see... |
|
| Back to top |
|
|
sandy201684
Junior
Joined: 16 Nov 2016
Posts: 14
|
| Posted: 24/12/2016 13:14 Post subject: dp slave not ready |
|
|
HI,
This is the diag buffer message
vent 1 of 10: Event ID 16# 2942
I/O access error, reading
P area, word access, Access address: 302
Requested OB: I/O access error OB (OB122)
Priority class: 1
External error, Incoming event
11:13:07.452 PM 12/23/2016
(Coding: 16# 2942 017A 0020 012E 0000 0000)
central rack-CPU-3152DP+1 AI module
IM station (1nos)-ET200+3DI+3DO+2AI
Dcoupler with IM station for another plc access
LED status-CPU =SF+BFflashing, IM=SF+BF flashing
as I have no option to attach files please check the above config |
|
| Back to top |
|
|
go
Member
Joined: 26 Mar 2015
Posts: 147
|
| Posted: 24/12/2016 17:59 Post subject: Re: dp slave not ready |
|
|
| sandy201684 wrote: | HI,
This is the diag buffer message
vent 1 of 10: Event ID 16# 2942
I/O access error, reading
P area, word access, Access address: 302
Requested OB: I/O access error OB (OB122)
Priority class: 1
External error, Incoming event
11:13:07.452 PM 12/23/2016
(Coding: 16# 2942 017A 0020 012E 0000 0000)
central rack-CPU-3152DP+1 AI module
IM station (1nos)-ET200+3DI+3DO+2AI
Dcoupler with IM station for another plc access
LED status-CPU =SF+BFflashing, IM=SF+BF flashing
as I have no option to attach files please check the above config |
Read carefully the PROFIBUS Manual and proceed:
http://profibus.felser.ch/en/index.html?codierung_der_diagnose.htm
This is the Diagnostic telegram:
Byte1 Byte2 Byte3 Byte4 Byte5 Byte6 Byte7 Byte8 Byte9 Byte10 Byte11 Byte12
29 ..... 42 ..... 01 .... 7A ... 00 .... 20 .... 01 ..... 2E ..... 00 ..... 00 ..... 00 ..... 00
This is the buffer diagnostic you provide Coding: 16# 2942 017A 0020 012E 0000 0000
Status1
nHEX-> BIN
---------------7654 3210---Bits in Byte
Byte1=29->0010 1001
Bit0=1 means:Station_Non_Existent:
Station does not exist. This bit is always set to zero by a slave. Here a master notices that this slave is not responding.
Bit3=1 means:Ext_Diag:
An extended diagnosis follows in the telegram. This bit indicates that further diagnostic blocks follow starting from byte 7.
Bit5=1 means:Invalid_Slave_Response:
Invalid response from slave. This bit is always set to zero by a slave. Here a master notices that a slave gives invalid responses.
STATUS2
--------------7654 3210---Bits in Byte
Byte2=42->0100 0010
Bit1=1 means:Stat_Diag:
Status diagnostics. If the DP slave sets this bit, the DP master must continue fetching diagnostic data until this bit is deleted again. The DP slave sets this bit when, for example, it is not able to provide any valid user data.
Bit6=1 means: Reserved
STATUS3
---------------7654 3210---Bits in Byte
Byte3=01->0000 0001
Master Adress 0x7A=122
--------------7654 3210---Bits in Byte
Byte4=7A->0111 1010
If the slave does not have any valid parameters, it sets this value to 255. As soon as valid parameters have been received with a lock from a class 1 master, the address of that master will be entered. It is therefore possible to identify here which master exercises cyclic control over a slave.
Diagnostic bytes 5 and 6 ...In these two bytes the slave declares its own Ident_Number.
Ident H
---------------7654 3210---Bits in Byte
Byte5=00->0000 0000
http://profibus.felser.ch/en/index.html?gsd_dateien.htm
Ident L
---------------7654 3210---Bits in Byte
Byte6=20->0010 0000
http://profibus.felser.ch/en/index.html?gsd_dateien.htm
these bytes are Diagnostic blocks
http://profibus.felser.ch/en/index.html?codierung_der_diagnose.htm.
Block1
---------------7654 3210---Bits in Byte
Byte7=01->0000 0001 means you have Identifier-based
diagnostics:
Identifier-based diagnostics concerns the position of the module in the configuration telegram. Events on the relevant module are signalled by a set bit.
Block2
---------------7654 3210---Bits in Byte
Byte8=2E->0010 1110
Conclusion:
As long as your Master signaling Station_Non_Existent that means you have problems with:
Check Cables
Check Connectors
Check PINOUT correspondence
LEDs indicated there is no communications due to mistaken in cabling or try to replace IM ...to check if there are not problems on this.
Good luck!!!! |
|
| Back to top |
|
|
sandy201684
Junior
Joined: 16 Nov 2016
Posts: 14
|
| Posted: 25/12/2016 17:31 Post subject: issue resolved |
|
|
Hello,
I have resolved the issue ..The problem was 3 modules were faulty in the expansion rack
I have done the following method to troubleshoot the issue
Created new project with new hardware configuration
removed all modules from expansion rack
configured with one by one modules and found 3modules faulty from the rack and replaced with spare modules and now the system is running with no errors
Thanks guys  |
|
| Back to top |
|
|
go
Member
Joined: 26 Mar 2015
Posts: 147
|
| Posted: 29/12/2016 14:21 Post subject: Re: issue resolved |
|
|
| sandy201684 wrote: | Hello,
I have resolved the issue ..The problem was 3 modules were faulty in the expansion rack
I have done the following method to troubleshoot the issue
Created new project with new hardware configuration
removed all modules from expansion rack
configured with one by one modules and found 3modules faulty from the rack and replaced with spare modules and now the system is running with no errors
Thanks guys |
Glad you solve the problem.
Anyway, for later use, put bit for extended diagnostic to 1 and use this method. |
|
| Back to top |
|
|
sandy201684
Junior
Joined: 16 Nov 2016
Posts: 14
|
| Posted: 29/12/2016 15:20 Post subject: |
|
|
| hi even though the issue is solved why when a module is faulty complete station goes into faulty?.. I have all the OB blocks in the program |
|
| Back to top |
|
|
go
Member
Joined: 26 Mar 2015
Posts: 147
|
| Posted: 29/12/2016 21:03 Post subject: |
|
|
| sandy201684 wrote: | | hi even though the issue is solved why when a module is faulty complete station goes into faulty?.. I have all the OB blocks in the program |
What IM do you exactly use 151 or 152 ...put Siemens code |
|
| Back to top |
|
|
sandy201684
Junior
Joined: 16 Nov 2016
Posts: 14
|
| Posted: 30/12/2016 19:23 Post subject: |
|
|
| Its 153-2 exact part number needs to check |
|
| Back to top |
|
|
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
