Systemdiagnostics
Error 8083 on PN device diagnostics V5.
Thread Starter: pimpim32 Started: 11/25/2010 12:39 PM Replies: 3

11/25/2010, 12:39 PM
|
Joined 3/6/2008
Last visit: 1/23/2013
Posts: 35
Rating:
(0)
|
(0)
|
Hi,
I am trying to set-up the PN Device Diagnostics V5 but seems he cannot read the modules. He is getting Error 8083 .
What I am doing wrong? I have used exactly your example. Export cfg file, transfer tags by AS/OS transfer, used DB35 with CPU_OK... etc
Thank you Marian
Hardware : CPU 414-2DP 6ES7 414-2XK05-0AB0 / V5.3 CP 443-1 6GL7 443-12X20-0XE0 / V2.1 X204-2 6GK5 204-2BB10-2AA3 / V4.2 IM153-4PN 6ES7 153-4AA01-0XB0 / V2.0 CP1623 6GK1 162-3AA00 /V7.1 Software Step7 V5.5 Simatic NET 2008 + SP2 WinCC 7.0 PN IO Device Diagnostics V5
|
|
|
|

1/3/2011, 10:56 AM
|
Joined 10/3/2008
Last visit: 5/2/2013
Posts: 522
Rating:
(52)
|
(0)
|
Hi, this is a problem with this new CPU. The system state lists are changed. Try the diagnosis with the block parameters EXT_DP = FALSE und PNIO = FALSE.
Wüstenräuber
|
|
|
|

2/22/2011, 10:44 AM
|
Joined 2/22/2011
Last visit: 11/21/2012
Posts: 1
Rating:
(0)
|
(0)
|
Hi Mr. Wüstenräuber ,
Sorry for the late reply, I have not been around for a while.
I have tried as you said , however still same error. In demo we have a FB12 activated in OB33 As test I have created a FB1730 activated in OB1 In WinCC I have tested both variants (FB12 and FB1730) After that I have played with configuration parameters EXT_DP and PNIO, however in all cases just on main view some nodes goes from barred to error, but deep diagnose is never performed (error 0x8083) I am attaching the last pictures.
However what is curious is that if I am changing first parameter Master_Nr from 100 to 64, communication stays OK, error 0x8083 If I am putting Master_Nr under 64 I get error 0x30a.
So this is really strange. Anyway this new CPU combined with my inexperience in parameterizing diagnose block is getting wrong result.
Please tell me what are the chances for a test from your side with above hardware setup?
Best regard Marian
|
|
|
|

2/22/2011, 2:12 PM
|
Joined 10/6/2008
Last visit: 1/10/2012
Posts: 8
Rating:
(0)
|
(0)
|
Hello Marian,
the screenshots are not providing enough information to make a detailed diagnostics. It would be good when you save a trace and send it to IT4Industry Hotline for further research.
With this post you find a PDF file that explains how to create a trace output. This file you should send to "it4.industry@siemens.com" with reference SR7048. We then can check the content and hopefully give you a better answer what is wrong.
Important for creating the trace output is that you start the trace tool before you open the WinCC picture with the diagnostics control.
Regards, Bernhard
|
|
|
|
Actions