In OB86 I have code storing the values of EV_Class, FLT_ID, MDL_ADDR and Z23...

When I have issues(profilbus)  I get

EV_Class = B#16#39

FLT_ID =B#16#C4

MDL_ADDR =W#16#1FFF

Z23 =W#16#0001

if I am reading the documentation right, does that mean I have a fault on the Profibus device #1?

Hello LandLord;

Yes basically, this is what comes out of the code in OB86:

- A incoming event

- a failure of a DP slave

- DP slave address 1

- Master system logical address 8191

The attached screenshot is taken from the System and Standard functions manual,

Ch. 1: Organization Blocks.

Hope this helps,

Daniel Chartier

dchartier

Hello LandLord;

Yes basically, this is what comes out of the code in OB86:

- A incoming event

- a failure of a DP slave

- DP slave address 1

- Master system logical address 8191

The attached screenshot is taken from the System and Standard functions manual,

Ch. 1: Organization Blocks.

Hope this helps,

Daniel Chartier

 I get all that, however i dont have a device with an id of 1 on my network?

the Master.. 8191 is ID2

Hello LandLord;

It is difficult for us to understand your statements without more information.

I suggest you show us a screenshot of your network configuration, along with the contents of your diagnostic buffer. That would allow us to examine your situation more clearly.

Hope this helps,

Daniel Chartier 

Hello LandLord;

The DB you have posted is not very useful at this time, although it represents a good effort. It always stores incomming and outgoing faults for the same Profibus master system ID and the same slave address (# 1), which you state does not exist.

It would really be better if we had a look at the contents of the diagnostic buffer, preferably as a text file (there is a "Save As.." button on the diagnostic buffer screen that you can use to produce a text file of all the stored messages in the buffer, those genertaed from OB86 and all the other diagnostic OBs, with a useful timestamp.

Please provide this file so we can help you more thoroughly.

Hope this helps,

Daniel Chartier

I'll be back at that facility on Monday.  Hard to look at the diagnostic log as there are other issues, looks like remote IO had been removed and not the code.  So, the buffer is full of that.  If i get a chance i will clean that up for them on Monday too. 

As far as the DB goes, i was under the assumption that coding it like that would capture the DP station having an issue.

The other thing i was confused on, on their network, is that it looks like there are 3 masters on the network, and also 2 repeaters.  One of the repeaters being right off the PLC (317). 

Monday we'll be able to put it apart and put a sniffer on the network.  Didn't trust the sniffer results last week, due to the repeaters, and this facility does not know how the network is laid out(all of which I hope to resolve Monday).

Any expert advice on documenting and troubleshooting an unknown network like this, beside the hand over hand method.