Hello;

At first glance,I have no idea what the error could be linked to, there is too much information missing.

But the diagnostic buffer does have an idea, you should interrogate it: use the Help on Event button on the diagnostic buffer screen to retrieve additional info on that specific line in the buffer.

However, there seems to be a lot of lines with similar messages. The best way to study the contents of the buffer is to use the Save As button, which redirects all logged messages to a text file that you can save and attach to a post here. This way we can all have a look for missing information on your system and work on understanding your problem.

One more way to help us would be to open the HWConfig editor in Online mode (with the glasses icon), this will show all the Profibus slaves that present faults with a failure symbol. If you can post that screenshot here this will give us an idea of the overall functioning of your network, and identify the slave node in fault.

See the screenshot below as an example of the Online view of the HWConfig, taken from this link that should interest you:

Diagnostics tools for commissioning the PROFIBUS DP network

.https://support.industry.siemens.com/cs/ww/en/view/19378851

Hope this helps,

Daniel Chartier

65535 = -1 as a signed Integer and I suspect a loop problem in the logic somewhere that leads to this.

If production allows, remove OB121 from the online program which will lead to a CPU stop.

When the CPU Stop happens, the diagnostic buffer will tell you what Block caused it which will allow you to check the logic and hopefully determine what is going on (or wrong).

hi,

it is an addressing error.

The one thing, that is clear is, that the CPU can´t reach a peripherial address. It also seams that the modbus blocks are involved.

Check the blocks that you use. FB 641 seams to trigger this event.check for error and status, like in the following FAQ:

How do you evaluate the status of system blocks in STEP 7 (TIA Portal)?

Have a look into the TIA-help of the block to get information about the error or ask us again if you need further help.

hope this help,

regards,

Hi AutoGen_5934520

based on your pic, you assigned "only" DB11 to "DATA_PTR" INOUT of FB 641.

While "DATA_PTR" is an ANY Parameter and allows this, you should instead assign something like P#DB11.DBX0.0 BYTE 170 to it (assuming you want to store the received 85 WORDS as of Byte 0 in DB11).

If this by itself doesn't fix it (and the 1SI ET200SP module are "fun" to use), do check the status info you get out FB641 as advised by MopS04. 

Hi Varadharajan.S

love to be able to fully fix up all issues in your program, but there's more than one issue and I unfortunately neither have the time nor hardware to test and best advice I can give is as followed:

1.) You program still still has "only" DB11 assigned to "DATA_PTR" INOUT of FB 641 and you seemed to have ignored previous advice.

2.) You assigned W#16#200 (=512 decimal) to the "PORT" Parameter of FB640.

Problem is that none of the 8 CM PtP cards that you have across your 4 ET200SP stations has this address. Use W#16#100 (=256 decimal) if you are testing the first CM PtP in the first rack as that is it Laddr (logical I/O address)

3.) If you don't already have it, grab the manual from HERE and study it please as there is possibly more wrong (and check the error codes that the blocks provide you).