Skip to Content

Register Login

Industry Online Support

Technical Forum

Navigation

Diagnostics event ID 16#39B1 - Reading DW within CP 343-1

Created by: JoKuhl at: 1/30/2008 8:40 AM (12 Replies)

Rating (0)

Thanks 0

Result pages:: |; 1 | 2; |

13 Entries

Entries per page: 10 | all

1/30/2008 8:40 AM	Rate (0)
JoKuhl Experienced Member Joined: 10/3/2007 Last visit: 2/10/2022 Posts: 43 Rating: (0)	Hi, I've got the same diagnostic event: Event 33 of 100: Event ID 16# 2942 I/O access error, reading P area, double-word access, Access address: 372 Requested OB: I/O access error OB (OB122) Priority class: 1 External error, Incoming event 11:56:07:197 pm 01/27/08 But access address 372 is in the area of an CP 343: RACK 0, SLOT 11, "6GK7 343-1EX11-0XE0" "V2.0", "CP 343-1(1)" LOCAL_IN_ADDRESSES ADDRESS 368, 0, 16, 0, 1, 0 LOCAL_OUT_ADDRESSES ADDRESS 368, 0, 16, 0, 1, 0 How can I get information about the actual source of the error, or am I mixing up here some things? greets JK
	Last edited by: CS Moderator at: 30.01.2008 12:45 new subject after splitting
Suggestion To thank Quote Answer

1/30/2008 12:55 PM	Rate (0)
J_Bell Posts: 5822 Rating: (412)	Dear JK, I wonder myself... what is trying to access the CP’s I/O? A usual call of FC 5 / 6 or any other FC that is useable for the CP would not do this. Could you figure this out? Best regards J_Bell
J_Bell Posts: 5822 Rating: (412)
Suggestion To thank Quote Answer

1/30/2008 2:14 PM	Rate (0)
JoKuhl Experienced Member Joined: 10/3/2007 Last visit: 2/10/2022 Posts: 43 Rating: (0)	FC101/102 are used for communication: for example: CALL "AG_RECV" ID :=1 LADDR :=W#16#170 RECV :=P#DB92.DBX 0.0 WORD 64 NDR :="DB_Rec_Real CL2".DONE ERROR :="DB_Rec_Real CL2".ERROR STATUS:="DB_Rec_Real CL2".STATUS LEN :="DB_Rec_Real CL2".LEN ...does that help anything? I will attach the config.cfg for the station where the error stops the CPU and the print of the NetPro configuration, if that helps something. thx Attachment config.zip (460 Downloads)
	Last edited by: JoKuhl at: 30.01.2008 14:17
Suggestion To thank Quote Answer

1/30/2008 2:39 PM	Rate (0)
J_Bell Posts: 5822 Rating: (412)	Hello, I just wonder myself, which version and family these AG_RECV Functions have you use? If they are S7-300 I think this is OK. Is the Program you use the same as the one on the CPU 315-2 the Config file was from? I would recommend changing the ANY Pointer at the Receive area from Word 64 to Byte 128, this is always recommendable with AG_SEND / AG_RECV. Best regards J_Bell
J_Bell Posts: 5822 Rating: (412)
Suggestion To thank Quote Answer

1/30/2008 3:21 PM	Rate (0)
JoKuhl Experienced Member Joined: 10/3/2007 Last visit: 2/10/2022 Posts: 43 Rating: (0)	OK I will try the word-byte change. the FC100/101 state they are CP_300 Family and have Version Header 4.1 and FC 100 calls SFC 58/59 FC 101 only SFC 59 They are WR_REC and RD_REC and from the IO_FUNCT family greets Johannes
	Last edited by: JoKuhl at: 30.01.2008 15:27
Suggestion To thank Quote Answer

1/30/2008 3:44 PM	Rate (0)
J_Bell Posts: 5822 Rating: (412)	Dear Johnnes, I see that the latest versions of AG_SEND / AG_RECV are as following: AG_SEND CP_300 V 4.2 AG_RECV CP_300 V 4.7 Maybe you think about updating your SIMATIC NET Library. Best regards J_Bell
J_Bell Posts: 5822 Rating: (412)
Suggestion To thank Quote Answer

1/30/2008 3:53 PM	Rate (0)
JoKuhl Experienced Member Joined: 10/3/2007 Last visit: 2/10/2022 Posts: 43 Rating: (0)	Thanks, I will try that. But to think of that, have i to update the fc on the other cpu's also? There are some CPU's in that system that are not owned by my concern. greets Johannes. PS: Schöne Gruesse in meine alte Heimat Deutschland ;)
	Last edited by: JoKuhl at: 30.01.2008 16:03
Suggestion To thank Quote Answer

1/30/2008 4:12 PM	Rate (0)
J_Bell Posts: 5822 Rating: (412)	Hallo Johannes.... ... und ich wundere mich schon. ... and write your name the wrong way... Keine Sorge wegen der anderen Steuerungen, die gehen auch mit den alten FCs weiter. Es kann nur sein das für die neueren CPUen fixes in den Bausteinen gemacht wurden die dann für einen besseren Ablauf sorgen. Best regards J_Bell
J_Bell Posts: 5822 Rating: (412)
Suggestion To thank Quote Answer

1/30/2008 4:21 PM	Rate (0)
JoKuhl Experienced Member Joined: 10/3/2007 Last visit: 2/10/2022 Posts: 43 Rating: (0)	Hehe, Dann werde ich Morgen testen ob es mit dem Update und dem Ändern von Word nach Byte endlich klappt. Leider tritt der Fehler sehr sporadisch auf, also dauert der Test etwas. Vielen Dank Gruss Johannes :)

Suggestion To thank Quote Answer

2/5/2008 8:24 AM	Rate (0)
JoKuhl Experienced Member Joined: 10/3/2007 Last visit: 2/10/2022 Posts: 43 Rating: (0)	Since it is an english forum I will write in english, maybe somebody is intrested. I made the updates of FC5/FC6 and changed the send and receive communication to BYTE instead of WORD, as suggested. But the error occurs after a while. But the CP343-1 is acting a bit strange, the RUN and STOP LED are sometimes shining constant, and in the manual there are only possibilities like, one constant the other flashing described. So my conclusion is, the CP must be broken. I will exchange it today or tomorrow, depending on when the part arrives. I have also a question to the send and receive call with BYTE. I am working here with a multi-project, and I am wondering if I have to change the Send and Receive routin also to BYTE in the other parts of the project? I rather don't, since they are working fine and I don't want to add another source of error to them, me :) best regards Johannes
	Last edited by: JoKuhl at: 05.02.2008 08:26
Suggestion To thank Quote Answer

|

Share this page:

Share this page on...

Follow us on