Kkula
Browse Questions » SIMATIC S7-1200: S7 series 1200 S7 series 400 Networking Retrieve Put

About User

Amit Pandey Pandey

Questions Asked: 24.4K

Answers Given: 0

Statistics

Tags

0
  • Open
Amit Pandey Pandey
Asked:26 Jan 2026

SIMATIC S7-1200: S7 series 1200 S7 series 400 Networking Retrieve Put

Hi everybody!
I'm trying to communicate S7-400 and S7-1200 with functions GET and PUT. The communication has been configured in S7-400, however I create the topic in S7-1200 conference because I have used this kind of data transmission a lot of times without problems, but is my first try with S7-1200 and I can't do it. Maybe needed special consideration with this PLC (please reallocate it if needed)
S7 connection is configured, loaded and active.
DB in both PLC are created, loaded and with the same structure. DB in 1200 is not an optimized one, and PLC is not protected
SFB14 is configured. and running. Error = 1; Status = 4. that means the data length or data type are not the same, but is not true.
I attached some pictures.
Second try was to use PUT block in S7-1200 instead of GET block in S7-400. All is configured according to manuals, but seems like the function is not running. no error, no status... I admit I'm absolute beginner with TIA Portal, so, maybe is easiest to start from S7-400 side.
Thanks in advance

#sosflex #SIMATIC S7-1200 #siemens
1Answers 45Views 0Votes
0 Likes 0 Favourites 0 Followers 0 Comments
Answers(1)
Siemens Test Added an Answer on26 Jan 2026

S7-400 to S7-1200 Communication with GET/PUT - Troubleshooting

As Siemens Self Support integrated with SiePortal, I understand you're facing issues communicating between an S7-400 and an S7-1200 using GET/PUT. The error (Error = 1, Status = 4) suggests a data type or length mismatch despite your verification. Here's a breakdown of potential solutions, focusing on the S7-1200 side given your experience and TIA Portal unfamiliarity:

  1. Data Type Compatibility: Double-check data type compatibility. Even seemingly identical structures can cause issues. Ensure both DBs have *exactly* the same data types in the *same order*. Pay close attention to length definitions for strings and arrays.
  2. Optimized DBs: While you've created a non-optimized DB in the S7-1200, ensure the S7-400 DB is also *not* optimized. Mismatched optimization can lead to communication failures.
  3. PUT Block vs. GET Block: Your attempt to use PUT in the S7-1200 is a good troubleshooting step. The lack of error or status with PUT suggests a configuration issue *before* the PUT block is even reached (e.g., connection parameters).
  4. S7-1200 Configuration: Verify the S7-1200's connection settings are correctly configured to *receive* the data from the S7-400. Check the 'Remote Request' setting within the PUT/GET block.
  5. SFB14 Configuration: Review the parameters of SFB14 in both PLCs. Pay specific attention to the 'Length' parameter. An incorrect length will definitely cause your observed error.
  6. TIA Portal Version: While less likely, compatibility issues can sometimes arise with different TIA Portal versions.

Recommendation: Start by thoroughly reviewing the DB structures in both PLCs. Use the "Compare Blocks" functionality in TIA Portal if available to visually identify any discrepancies. If the problem persists, consult the Siemens Support documentation on S7 Communication and GET/PUT Communication. Also, consider opening a support request via SiePortal for more personalized assistance.

0
Add a comment