Skip to Content

Register Login

Industry Online Support

Technical Forum

Navigation

No connection to CPU

Created by: Import-User-1 at: 10/6/2008 12:50 PM (9 Replies)

Rating (0)

Thanks 0

10 Entries

10/6/2008 12:50 PM	Rate (0)
Import-User-1 Posts: 3609 Rating: (28)	I use Profibus Systemdiagnostics V4. The connection from OCX to CPU doesn't work. The communication between WinCC and CPU is okay, but the OCX shows "No connection to CPU". What can be the reason?
Import-User-1 Posts: 3609 Rating: (28)
Suggestion To thank Quote Answer

10/6/2008 1:36 PM	Rate (0)
Wüstenräuber Gold Member Joined: 10/3/2008 Last visit: 11/17/2023 Posts: 947 Rating: (122)	It could be multiple causes: the masternumber in the projection of theOCX isn't correct the exported HW-config-file (*.cfg)or the mapped tagname isn't ornot correct projectedin the OCX the FB DPDIAG is inserted ina OB, which is too fast or too slow (500ms are recommended) Wüstenräuber

Suggestion To thank Quote Answer

10/16/2008 3:44 PM	Rate (0)
Sam. Posts: 63 Rating: (0)	Wüstenräuber the FB DPDIAG is inserted ina OB, which is too fast or too slow (500ms are recommended) Wüstenräuber I am using System diagnostics v5... for HCPU_DIAG -- connection is OK always...but for DP_DIAG, initially takes time for communication and, communication fluctuates whereas for CPU it is healthy constantly.... I have tried MainCycle and OB35(500ms) but still facing problem.... now what do i do ? any suggestions....
Sam. Posts: 63 Rating: (0)
Suggestion To thank Quote Answer

10/20/2008 7:41 AM	Rate (0)
Wüstenräuber Gold Member Joined: 10/3/2008 Last visit: 11/17/2023 Posts: 947 Rating: (122)	Hello Sam., do you use the correct DP_DIAG block? There are 2 DP_DIAG blocks in the library: one for single profibus and one for redundant profibus. What is the size of the block, which you use? The single profibus block should be 10472 bytes and the redundant profibus block should be 12760 bytes (in V5). If the wrong block is used, the described behaviour could be shown. Please let me know, if you use the correct block and the behaviour is shown still. I'm thinking about another reason... Wüstenräuber

Suggestion To thank Quote Answer

10/20/2008 12:01 PM	Rate (0)
Sam. Posts: 63 Rating: (0)	Wüstenräuber Please let me know, if you use the correct block and the behaviour is shown still. I'm thinking about another reason... Wüstenräuber thanks for reply Wüstenräuber Yes I am using the correct one only..size for that DP_DIAG block is 12760 bytes (plz check the jpeg file attached here)....and no change in behaviour... apart from previous problems also i have find other bugs as ... 1.even if i remove the profibus from cpu still dp diagnoctics show the healthy master system 2.both master system goes unhealthy together..never a case i have find in which either of master bus is healthy and other not. i got a feeling that its operation are not consistent and not providing the correct diagnostics.... if any, can suggest the alternative for this diagnostics... ? Attachment UsedBlocks.JPG (143 Downloads)
Sam. Posts: 63 Rating: (0)
Suggestion To thank Quote Answer

10/20/2008 1:28 PM	Rate (0)
Wüstenräuber Gold Member Joined: 10/3/2008 Last visit: 11/17/2023 Posts: 947 Rating: (122)	Hello Sam., I assume it's a parameterization problem. Check the entry for the tagname and the cfg-file in the ocx and check the parameterization on the DP_DIAG block (entries of both mastersystemnumber on inputs). Wüstenräuber

Suggestion To thank Quote Answer

10/21/2008 8:50 AM	Rate (0)
Sam. Posts: 63 Rating: (0)	Hi Wüstenräuber, I have put the proper tagname and .cfg file for ocx, in hardware profibus master are 1 & 2. And parameterization is correct also as per existing system, but you can check it in attachment and comment changes if required. thanks. Attachment New.JPG (114 Downloads)
Sam. Posts: 63 Rating: (0)
Suggestion To thank Quote Answer

10/21/2008 9:20 AM	Rate (0)
Wüstenräuber Gold Member Joined: 10/3/2008 Last visit: 11/17/2023 Posts: 947 Rating: (122)	Hi Sam., okay, then in HW config the mastersystem numbers should 1 and 2 and in OCX the mastersystemnumbers should 1 and 2 as well. The input parameter EXT_DP is set to FALSE, so the mastersystem "hangs" on the internal profibus interface. You don't use an external Profibus-CP, it's correct? Attach the exported cfg-file and the wincc picture, then I can check this. Wüsternräuber

Suggestion To thank Quote Answer

1/10/2012 2:35 PM	Rate (0)
MS1981 Silver Member Joined: 4/14/2010 Last visit: 12/11/2023 Posts: 518 Rating: (11)	the masternumber in the projection of theOCX isn't correct the exported HW-config-file (*.cfg)or the mapped tagname isn't ornot correct projectedin the OCX the FB DPDIAG is inserted ina OB, which is too fast or too slow (500ms are recommended) Greeting, Could you help us please regardig discussed issue i have perform above task but have still problem which tagname i can use for DP_DIAG see attached Thanks, Regard, Attachment 3.zip (99 Downloads)
	Last edited by: Sarfraz Bhatti at: 1/10/2012 2:38 PM MS
Suggestion To thank Quote Answer

5/30/2017 2:45 PM	Rate (0)
Mtn.Ansari Experienced Member Joined: 3/2/2010 Last visit: 12/11/2023 Posts: 1 Rating: (0)	Sarfraz Bhatti the masternumber in the projection of theOCX isn't correct the exported HW-config-file (*.cfg)or the mapped tagname isn't ornot correct projectedin the OCX the FB DPDIAG is inserted ina OB, which is too fast or too slow (500ms are recommended) Greeting, Could you help us please regardig discussed issue i have perform above task but have still problem which tagname i can use for DP_DIAG see attached Thanks, Regard, Dear Sir Where can I download System diagnostics v5? unknown user

Suggestion To thank Quote Answer

|

Share this page:

Share this page on...

Related topics by keywords:

WinCC Communication (OPC, S7, OtherSystem)

Follow us on