------------------------------------------------------------------------------------------
Split from Detect an Profibus error without Profibus Analyzer.

mr.adi

Have any chance that this problem caused by the PROFIBUS stations because the PROFIBUS cable is not on the good condition?

hi adi,

 this is very often the reason for Profibus-failures.

It is very hard, when it occurs once a week. check all Bus-connectors and also check if the grounding is good.

hope this helps,

regards,

Hi,

why don't look in the diagnostic buffer which I/O is affected?

if the i/o is identified then you can show what you can do to eliminate the problem.

Regards

Christoph 

Hello,

hmmm maybe some check of right termination of modules will be helpfull. I've same problem with my one old prj.

mr.adi

Thanks for your answer 

The problem is that on diagnostic buffer i can't see this information. 

Event 6 of 10:  Event ID 16# 494D

STOP due to IO error 

No relevance for user (Z2): 0000 (Z3): 0000 

Previous operating mode: RUN 

Requested operating mode: STOP (internal)

External error, Incoming event

10:23:37.383 AM  11/10/2015

Best regards 

Adi

hi Adi,

we had already a discussion about this error.

CPU 315-2DP, sometimes goes to STOP mode and turn on the SF led

is it the same CPU? and the same behavior?

regards,

Hello,

if I will be thinking about problem with connector/cable, there must be in that same time in diagnostic buffer event about loosing DP Slave probably. If not, it looks like internal bus connector backplane problem or some leaking data on DP communication???? Look again in buffer and find that events. Give us info.

mr.adi

Thanks for your answer 

Yes is the same behavior, but now my question is, have any chance that profibus cable cause this error?

Regards 

Adi

 and which module have the adress 37 which you named in the other thread?

a module in the ET200 or in the central rack?