3/2/2021 7:52 AM | |
Joined: 4/6/2018 Last visit: 5/12/2024 Posts: 33 Rating: (0) |
Good day. We have communication problems between WinCC (7.4 SP1) and S7-300. Profibus communication. Sometimes the error appears: SIMATIC_S7_Protocol_Suite_01.LOG 2020-12-14 17:14:14,645 ERROR Connectionerror 1 "AGZS": Errorcode 0xFFDF 410E! 2020-12-21 05:58:05,779 ERROR Connectionerror 2 "AGZS": Errorcode 0xFFDF 410E! 2020-12-21 09:40:46,971 ERROR Connectionerror 3 "AGZS": Errorcode 0xFFDF 410E! 2020-12-22 17:29:03,212 ERROR Connectionerror 4 "AGZS": Errorcode 0xFFDF 410E! 2021-01-06 19:29:28,454 ERROR Connectionerror 5 "AGZS": Errorcode 0xFFDF 410E! 2021-01-20 23:28:25,137 ERROR Connectionerror 6 "AGZS": Errorcode 0xFFDF 410E! 2021-01-29 02:08:51,124 ERROR Connectionerror 7 "AGZS": Errorcode 0xFFDF 410E! 2021-02-02 04:39:11,933 ERROR Connectionerror 8 "AGZS": Errorcode 0xFFDF 410E! 2021-02-11 03:45:24,103 ERROR Connectionerror 9 "AGZS": Errorcode 0xFFDF 410E! 2021-02-14 03:59:33,488 ERROR Connectionerror 10 "AGZS": Errorcode 0xFFDF 410E! WinCC_Sys01.log 2303,19.11.2020,20:19:13:563,1000204,4,,SSG2,DataManager Runtime,AGZS Connection 'AGZS' disconnected,MSG_STATE_COME 2303,14.12.2020,17:14:14:645,1000204,4,,SSG2,DataManager Runtime,AGZS Connection 'AGZS' disconnected,MSG_STATE_COME 2303,14.12.2020,17:14:45:846,1000204,4,,SSG2,DataManager Runtime,AGZS Connection 'AGZS' connected,MSG_STATE_GO 2303,14.12.2020,17:14:45:846,1000205,4,,SSG2,DataManager Runtime,AGZS Connection 'AGZS' connected,MSG_STATE_COME 2303,21.12.2020,05:58:05:780,1000204,4,,SSG2,DataManager Runtime,AGZS Connection 'AGZS' disconnected,MSG_STATE_COME 2303,21.12.2020,05:58:10:409,1000204,4,,SSG2,DataManager Runtime,AGZS Connection 'AGZS' connected,MSG_STATE_GO 2303,21.12.2020,05:58:10:409,1000205,4,,SSG2,DataManager Runtime,AGZS Connection 'AGZS' connected,MSG_STATE_COME 2303,21.12.2020,09:40:46:971,1000204,4,,SSG2,DataManager Runtime,AGZS Connection 'AGZS' disconnected,MSG_STATE_COME 2303,21.12.2020,09:41:17:799,1000204,4,,SSG2,DataManager Runtime,AGZS Connection 'AGZS' connected,MSG_STATE_GO 2303,21.12.2020,09:41:17:799,1000205,4,,SSG2,DataManager Runtime,AGZS Connection 'AGZS' connected,MSG_STATE_COME 2303,22.12.2020,17:29:03:212,1000204,4,,SSG2,DataManager Runtime,AGZS Connection 'AGZS' disconnected,MSG_STATE_COME 2303,22.12.2020,17:29:07:816,1000204,4,,SSG2,DataManager Runtime,AGZS Connection 'AGZS' connected,MSG_STATE_GO 2303,22.12.2020,17:29:07:816,1000205,4,,SSG2,DataManager Runtime,AGZS Connection 'AGZS' connected,MSG_STATE_COME 2303,06.01.2021,19:29:28:455,1000204,4,,SSG2,DataManager Runtime,AGZS Connection 'AGZS' disconnected,MSG_STATE_COME 2303,06.01.2021,19:29:32:764,1000204,4,,SSG2,DataManager Runtime,AGZS Connection 'AGZS' connected,MSG_STATE_GO 2303,06.01.2021,19:29:32:764,1000205,4,,SSG2,DataManager Runtime,AGZS Connection 'AGZS' connected,MSG_STATE_COME 2303,20.01.2021,23:28:25:137,1000204,4,,SSG2,DataManager Runtime,AGZS Connection 'AGZS' disconnected,MSG_STATE_COME 2303,20.01.2021,23:28:29:642,1000204,4,,SSG2,DataManager Runtime,AGZS Connection 'AGZS' connected,MSG_STATE_GO 2303,20.01.2021,23:28:29:642,1000205,4,,SSG2,DataManager Runtime,AGZS Connection 'AGZS' connected,MSG_STATE_COME 2303,29.01.2021,02:08:51:125,1000204,4,,SSG2,DataManager Runtime,AGZS Connection 'AGZS' disconnected,MSG_STATE_COME 2303,29.01.2021,02:08:55:754,1000204,4,,SSG2,DataManager Runtime,AGZS Connection 'AGZS' connected,MSG_STATE_GO 2303,29.01.2021,02:08:55:754,1000205,4,,SSG2,DataManager Runtime,AGZS Connection 'AGZS' connected,MSG_STATE_COME 2303,02.02.2021,04:39:11:933,1000204,4,,SSG2,DataManager Runtime,AGZS Connection 'AGZS' disconnected,MSG_STATE_COME 2303,02.02.2021,04:39:16:166,1000204,4,,SSG2,DataManager Runtime,AGZS Connection 'AGZS' connected,MSG_STATE_GO 2303,02.02.2021,04:39:16:166,1000205,4,,SSG2,DataManager Runtime,AGZS Connection 'AGZS' connected,MSG_STATE_COME 2303,11.02.2021,03:45:24:103,1000204,4,,SSG2,DataManager Runtime,AGZS Connection 'AGZS' disconnected,MSG_STATE_COME 2303,11.02.2021,03:45:28:797,1000204,4,,SSG2,DataManager Runtime,AGZS Connection 'AGZS' connected,MSG_STATE_GO 2303,11.02.2021,03:45:28:797,1000205,4,,SSG2,DataManager Runtime,AGZS Connection 'AGZS' connected,MSG_STATE_COME 2303,14.02.2021,03:59:33:489,1000204,4,,SSG2,DataManager Runtime,AGZS Connection 'AGZS' disconnected,MSG_STATE_COME 2303,14.02.2021,03:59:38:623,1000204,4,,SSG2,DataManager Runtime,AGZS Connection 'AGZS' connected,MSG_STATE_GO 2303,14.02.2021,03:59:38:623,1000205,4,,SSG2,DataManager Runtime,AGZS Connection 'AGZS' connected,MSG_STATE_COME S7-300 build version, about 2005 release. Because of what these messages, did anyone come across? The archive folder diagnostic Attachmentdiagnose.zip (63 Downloads) |
3/2/2021 8:37 AM | |
Joined: 5/16/2014 Last visit: 9/12/2022 Posts: 7298 Rating: (2164)
|
Hello AutoGen_3646402, the Error 410E means: The third point is a lack of communication ressources in the PLC. See FAQ: https://support.industry.siemens.com/cs/ww/en/view/97649464 Regards Georg Berghof |
PS: If this post did really help you, you may use the Rate-button |
|
3/4/2021 6:27 PM | |
Joined: 4/6/2018 Last visit: 5/12/2024 Posts: 33 Rating: (0) |
I tried changing the parameters of the Profibus-System Parameters driver from 60 to 90 and 30 to 45. This did not solve the problem, the error was repeated. I also checked the distribution of resources - it seems to me that there should be no problems either. Initially, I gave the information incorrectly - WinCC is connected to the CP342-5 communication module. Attached are photos of our settings. What other options are possible? Could there be a reason for the logical connection name "CP5622.Profibus.1"? At other stations we have the name "CP_L2_1". AttachmentSetup_foto.zip (65 Downloads) |
Follow us on