Nice to meet you! I am new here and currently working on converting STL code from an S7-400 to SCL for an S7-1500 PLC. When running the STL on the S7-1500, the values transferred to #DB_number_1 are random, causing network issues. Can someone assist me in converting this STL to SCL? The code snippet includes TAR1T, TAR2T, Block 1L, Block 2L, and Block 3L with corresponding instructions for data manipulation. Let's work together to fix this issue and ensure a smooth transition to SCL.
Share the original S7-400 code with the block interface included for reference.
What steps should be taken to optimize the block's performance? It may be more beneficial to approach the problem with optimization in mind, possibly leading to a solution that requires restructuring the data.
I apologize for the lengthy code. This is the original source code I used to send data using a Multiplexer for BSend Communications. It worked flawlessly on an S7-400, but encountered issues on an S7-1500.
To optimize your programming workflow in Simatic Manager, it is recommended to establish a library and transfer the necessary reduced block(s) into it. After archiving the library, attach it to a post. Currently, the issue of DB_Number_1 being overwritten by the direct access to temporary data is apparent.
PeterGotta mentioned that he used a section of code to send data through a Multiplexer for BSend Communications. While it worked flawlessly on the S7-400, it encountered issues on the S7-1500. Provide a detailed explanation of the code's intended functionality before transitioning to a new, streamlined SCL code. Disregard the previously used STL code.
Welcome to the forum! While I'm not an expert at converting from STL to SCL, I do have some experience with Siemens systems. Have you checked if the DBs in your SCL code are correctly declared and the instructions used are permissible in SCL? The random values could stem from these issues. Also, keep an eye on any errors that might crop up during the compiling process as they often indicate where things are going wrong. Remember to double-check the bit operations, especially in converting between TAR1T, TAR2T structures and Block 1L to 3L. Siemens provides some helpful documentation on STL-to-SCL conversion, I'll see if I can find it and provide a link in a follow-up post.
Welcome to the forum! It sounds like a challenging task converting STL to SCL, especially with the issues you're facing. I recommend starting by breaking down your STL code line by line and translating each instruction into its SCL equivalent, ensuring that you maintain the logic flow. Pay close attention to data types and structure when manipulating values; sometimes endianess or array indexing can lead to unexpected results. If you can share specific lines of your code, Iād be happy to help with more targeted advice!
ā Work Order Management
ā Asset Tracking
ā Preventive Maintenance
ā Inspection Report
We have received your information. We will share Schedule Demo details on your Mail Id.
Answer: Answer: To convert STL code to SCL, you can manually rewrite the logic or use conversion tools provided by Siemens. Ensure proper mapping of instructions and data types during the conversion process.
Answer: Answer: Random values in DB_number_1 could indicate issues with data handling or incorrect mapping of variables during the conversion process. Check for inconsistencies in variable declarations and data manipulation instructions.
Answer: Answer: To troubleshoot network issues, validate the data transfer process, check for data integrity, review network configurations, and ensure proper communication settings between the PLCs.
Answer: Answer: Seek guidance from experienced programmers or Siemens support resources to understand the equivalent SCL instructions for TAR1T, TAR2T, and other specific STL instructions during the conversion process.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.