Hi!

I have the same problem but in my case the "Enable put/get" check is checked. In fact, the put funcition is working fine, the problem is only with the get function and the error is the same:

 2 = "Negative acknowledgement from the partner device. The function cannot be executed"

Any idea?

Thanks and regards,

------------------------------------------------------------------------------------------
Split from Trouble with PUT/GET communication from S7-400 to S7-1200.

 Hello.

Duris_I

Hello,

maybe... DB11 with proper styructure exists really on both CPUs? Check this again carefully, better in Online. Show that internal structures of DBs. Zip screenshots, attach here.

To aid your contribution and additional to your notes.
Some hints for the S7-1200 in the attached picture.

BR

It was not a problem about the user program... The s7-400 is programmed with PCS7 v8.2. I have solved the problem after donwload a backup from monday, copy and paste again the same blocks that were not running today, and compile and download again the program. So, I suppose that the problem was about the compilation (and I can do nothing about it). 

I will see if after future changes and compilations in the program, everything remains ok...

Thanks to all!

Bingo!

I have changed the pointer from 2 bytes to 90 bytes (same data types in both DBs and in both CPUs) and communication errors again...

Thank you for your support. Please find attached de zip file with many screenshots.

I have made a lot of tests. Sometimes the put works, sometimes the get works, sometimes none works and sometimes both works; and I am only changing the number of bytes, compiling the PLC project and downloading it (remember that it is PCS7 with a S7-410-5H). No changes in the user DBs, no changes in the netpro.

At this moment, the get is working with 4 bytes and the put with 2 bytes. If I increase the number of bytes it does not work. An the question is that on monday we could communicate up to 132 bytes.

Regards,

P.S.: I said "Bingo" because I was expecting this kind of funny errors