Skip to Content

Register Login

Default Header

(header konnte nicht geladen werden)

Navigation

SDB download problems for S7-400

Created by: khorkhordin at: 3/7/2012 4:00 PM (5 Replies)

Rating (0)

Thanks 3

6 Entries

3/7/2012 4:00 PM	Rate (0)
khorkhordin Posts: 10 Rating: (0)	Hi all, I ran into wierd problem with a project written in Step7 v5.4 for S7-414H. At some point complete project download to CPU started to fail with error message: (D20D) SDB cannot be interpreted (for example, unknown number) What is the possible remedy? Any ideas are appreciated.
khorkhordin Posts: 10 Rating: (0)
Suggestion To thank Quote Answer

3/10/2012 5:37 AM	Rate (0)
khorkhordin Posts: 10 Rating: (0)	The message also says 'Cannot load SDB 305'. Any ideas, folks? Attachment SDB error.jpg (475 Downloads)
khorkhordin Posts: 10 Rating: (0)
Suggestion To thank Quote Answer

3/11/2012 8:08 AM	Rate (0)
umencho Diamond Member Joined: 3/21/2006 Last visit: 3/30/2025 Posts: 10239 Rating: (1183)	Hello, Is this a new project or an old one in which you are trying to make some changes? SDB305 is related to Configuring symbol-related messages. Check Configuring chronological messaging or http://support.automation.siemens.com/WW/view/en/22979182 Best regards, Hristo Mihalev

Suggestion To thank Quote Answer
This contribution was helpful to 1 thankful Users khorkhordin

3/11/2012 5:02 PM	Rate (0)
khorkhordin Posts: 10 Rating: (0)	Hristo, Thank you for the reply. The project is new, and the idea of SDB problem originating from message generation looks promising. I will try that direction... Yuriy
khorkhordin Posts: 10 Rating: (0)
Suggestion To thank Quote Answer

3/11/2012 7:45 PM	Rate (0)
Late Platinum Expert Joined: 1/7/2006 Last visit: 5/11/2025 Posts: 2705 Rating: (321)	Hi, You could see it directly in the symbolic, if you place the colums for communication also in the view. Normally these messages are coming from PDIAG or S7-Graph where ALARM_S messages are programmed. If no ALARM_S messages are used then delete the SDB-bag from the block-container and compile the hardware new, then look if the SDB305 is coming back, if not then compile Netpro and look again.
	I hope that the answer will help, if you have still questions, don't hesitate to ask me. All the best, Late Never say never, think in solutions, not in trouble......
Suggestion To thank Quote Answer
This contribution was helpful to 1 thankful Users khorkhordin

3/13/2012 11:27 AM	Rate (0)
khorkhordin Posts: 10 Rating: (0)	Thank you guys again. In my Symbol table I had an input generating a message (I was experimenting earlier). Once I removed the message and re-genereated SDBs, the problem disappeared! Case isclosed!
khorkhordin Posts: 10 Rating: (0)
Suggestion To thank Quote Answer
This contribution was helpful to 1 thankful Users umencho

|

Share this page:

Share this page on...

Follow us on