Kkula
Hello,
I'm working with step 7 v5.5 sp4 and PLCSIM for simulation.
I created a DB and I define the first word with value 20 as initial value.
My problem was when I load my program (using PLCSIM)and go online, I find that the first word of DB was 0 (as you see in attachement) and this value don't change until I force it using VAT.
So, why I can't see initial value (20) after loading DB?
It appears you're encountering a common issue with STEP V5.6 after installing newer software like Simotion Starter and SSP for S120 drives. Here's a breakdown of the problem and solutions:
STEP V5.6 has specific dependencies on the Simotion package. Installing newer Simotion Starter often doesn't automatically integrate correctly with the older STEP V5.6. This results in the "Simotion package not installed" error and the CPU 320PN not appearing in the hardware catalog.
If the issue persists, please provide your exact STEP V5.6 version (including SP level) and the versions of Simotion Starter and the S120 SSP. You can also find additional troubleshooting steps and FAQs on the Siemens Industry Support Portal. Search for keywords like "STEP V5.6 Simotion package" or "CPU not found in hardware catalog".
You want to shift a boolean bit within a 255-element array each time an encoder emits a Z pulse. Here's how you can achieve this using TIA Portal:
Example Code Snippet (Ladder Logic):
NETWORK 1: // Encoder Z Pulse Detection
IF Encoder_Z_Pulse THEN
Counter_DB.DB_Number.Counter_MW++; // Increment counter
END_IF;
NETWORK 2: // Bit Shifting Logic
DB_Number.DB_Number.Array_of_Bools[Counter_DB.DB_Number.Counter_MW MOD 255 + 1] := TRUE; // Set bit at shifted index
DB_Number.DB_Number.Array_of_Bools[Counter_DB.DB_Number.Counter_MW MOD 255] := FALSE; //Clear Previous Bit
Explanation:
Resources:
For detailed guidance and specific configurations tailored to your hardware and TIA Portal version, consult the Siemens documentation or SiePortal.
Hello Davor,
The issue of OB100 not executing after a warm restart with an IM 151-7 CPU is often related to the startup configuration and how the PLC handles OB100 execution during restarts.
Here are a few potential causes and solutions:
Important SiePortal Resources:
If the problem persists, please provide your Simatic Manager project version and a more detailed description of your OB100 code for further assistance.
Best regards,
Siemens Self Support
Hello Larry,
The issue you're experiencing with updating the CP343-1 Advanced IT firmware is a known problem often related to incomplete or corrupted previous installations. Here's a recommended approach, referencing SiePortal resources:
For detailed troubleshooting steps, please refer to the following SiePortal FAQ: CP343-1 Update fails with error message.
If the issue persists, providing the exact error message and your PG/PC specifications will help in further diagnosis.
Sincerely,
Siemens Self Support
Hi Matthew,
The structure list program displays a table with three columns during online operation. While the first column represents 'RLO' (Result of Logic), the other two columns represent:
For more detailed information, please refer to the SiePortal documentation on Structure Lists:
Siemens Support - Structure Lists in TIA PortalIf you have further questions, please don't hesitate to ask.
Regards,
Siemens Self Support
The STL (STEP 7 Ladder Logic) instructions CALL, BLD (Build Data), and END CALL are used for creating and managing function blocks (FBs) and function call blocks (FCs) within your program. They facilitate modular programming and code reuse.
Here's a breakdown:
In essence: BLD creates the FB instance, CALL executes it, and END CALL signifies completion.
For detailed information and examples, please refer to the Siemens documentation:
Siemens Support Article - CALL and BLD Instructions STEP 7: How do you use Function Blocks (FBs) and Function Call Blocks (FCs)?You are experiencing a known limitation in Step 7 V5.5 regarding the number of IO flags visible at once within a segment during online monitoring. The display is restricted to a subset (e.g., 4 out of 12) of the elements.
Workaround/Solution:
This behavior is due to display limitations within the V5.5 environment. While not a bug, it requires manual scrolling or alternative methods to view all online statuses.
Yes, it's possible to log forced values in Siemens PLCs and export the data. Here are a few methods:
Exporting to Excel: After logging the data, you can export it from the chosen method (TIA Portal trace data, SCADA system, or custom data block) to a CSV file, which can then be opened and formatted in Excel.
Further Resources:
For detailed instructions tailored to your specific PLC model and TIA Portal version, please consult the Siemens documentation on SiePortal.
You're encountering an issue with S5 time format (#0.0s) when using IEC timers in TIA Portal. Here's how to handle it:
The IEC timer expects time in seconds
or milliseconds (MS). S5 time is in seconds with decimal places. You can directly use S5 time values with IEC timers, as TIA Portal automatically handles the conversion.
Example: If your HMI input is S5#1.5s, the IEC timer will interpret it as 1.5 seconds. No explicit conversion is needed in the code.
If you need to perform a conversion within your code for clarity or specific calculations, use the TIME_TO_REAL or REAL_TO_TIME functions. However, this is generally not necessary for direct use with IEC timers.
For more detailed information, refer to the Siemens documentation: TIA Portal: Working with Time
Siemens officially does not support running STEP 7 (V5.x) on Windows Vista. While some users have reported limited functionality with workarounds, it's strongly discouraged for production environments.
There are no plans for specific add-ons or upgrades to enable full STEP 7 compatibility with Windows Vista. Siemens focuses support on currently supported operating systems, which currently includes Windows 7 (with limitations), Windows 10, and Windows 11.
Recommendation: Migrate to a supported operating system for optimal performance and Siemens support. Consider upgrading to the latest version of TIA Portal which is the successor to Step7 and provides broader OS compatibility.
For detailed compatibility information, refer to the Siemens Support website: Siemens STEP 7 Compatibility
Greetings! Siemens Self Support here, integrated with SiePortal. It appears you're experiencing problems with your PG/PC interface and program download. The missing interface prevents installation, and you're receiving an error during download.
To best assist you, we need more information. However, here are some initial troubleshooting steps and resources:
SiePortal Resources: Siemens Industry Support offers extensive FAQs, manuals, and knowledge base articles. Please search for your specific PLC and TIA Portal version.
If these steps don't resolve the issue, please provide the requested information (full error message and screenshot) so we can investigate further.
You've observed a PLC rung where the CPU is writing to input bits that aren't mapped to any physical input hardware. This is a valid, though often unconventional, technique used for several purposes:
Important Considerations:
For more information on PLC programming best practices, please refer to the Siemens documentation on TIA Portal programming guidelines.
You're on the right track! The linked FAQ demonstrates summing sampled flow values. For your application of 1-second samples over 10 seconds, followed by a shift, this principle applies – it accumulates the flow over that defined period.
To achieve the shifting effect (moving the integrated value forward), you’ll need to implement a circular buffer or similar data structure in your STL code. This allows you to discard the oldest sample and add the newest one after each integration cycle.
While there isn’t a single FAQ covering this exact scenario, consider these resources:
Yes, accumulating flow samples and then shifting the data is a common and correct practice for flow measurement and totalization, especially when dealing with data logging and analysis.
Yes, it is absolutely possible to compare the PLC time and enable an output in SIMATIC Manager STEP 7 V5.4, and to reset a counter at a specific time like 6:00 AM.
Here's how you can achieve this:
SFB13 (Read Time) to access the PLC's current time.>=, ==) to compare the current time with your target time (6:00 AM). You’ll need to represent 6:00 AM as an integer value corresponding to the time in hours, minutes, and seconds.Example: You can create a function block (FB) to encapsulate this logic for reusability.
For detailed information and examples, please refer to the following resources in SiePortal:
Please ensure you have correctly configured the PLC's time and date settings before implementing this logic.
Thank you for sharing the "Shortcuts in Step 7" document! We appreciate you contributing to making Step 7 usage faster and easier, especially for field work.
These shortcuts are indeed incredibly valuable for improving efficiency during commissioning and maintenance tasks.
For further Siemens Step 7 support resources, please visit: Siemens Industry Online Support - STEP 7
You can also access the SiePortal knowledge base through: SiePortal
Yes, simply adjusting the multiplication factor (MUL) is generally sufficient when changing encoders with different pulse counts. If you previously had 10 pulses per revolution and now have 50, multiplying your input value by 5 will scale the measurement correctly.
However, consider these points for accurate measurement:
If you encounter issues, please provide your PLC program snippet and encoder specifications for further assistance through SiePortal.
Hello! Upgrading from SIMATIC Manager V5.1 to V5.4 involves a specific procedure. Here's a breakdown, along with license considerations:
Your existing V5.1 license *should* generally be transferable, but it's best to verify this via SiePortal:
Important: Consult the official Siemens documentation and FAQs on the Support website for detailed instructions and troubleshooting.
You've highlighted a useful FAQ regarding license key issues in STEP 7, even with a valid installation. This remains relevant despite updates to the FAQ and the release of ALM 4.
The core issue revolves around potential conflicts or incorrect configurations. The FAQ likely details troubleshooting steps such as:
Please refer to the FAQ directly for detailed steps: Siemens Support - License Key Missing in STEP 7
Careful review of this FAQ is recommended as the root causes can be non-obvious.
The error code 39B4 indicates a failure to update the output image for a device, specifically related to Profibus communication. Your troubleshooting steps point to a problem localized to a single Profibus bus.
Given this is a multicomputing system with the S7-400 as a slave, the issue likely stems from configuration inconsistencies or resource conflicts within the Profibus communication settings of the master CPU and how it interacts with the slave CPU’s I/O.
Here's a breakdown of potential causes and recommendations:
Further Investigation:
For more detailed troubleshooting steps and specific configuration guidance, please refer to the following SiePortal resources:
Siemens Support Forum - Profibus Error 39B4 Siemens Support ID: 109762698 - Error 39B4Hello Smiffy,
Yes, the provided function block (FB99) can convert an array of characters to a string in your Siemens PLC. This block utilizes pointer manipulation to directly access the character data within a Data Block (DB).
Key Considerations:
DB_PTR points to the entire DB containing the character array, not just a portion of it.STR) is limited to a maximum length of 254 characters.The code uses BLKMOV to move the data from the DB to the string. The temporary variable pSRC is crucial as it dissects the ANY pointer to access the DB's contents.
For more information on using ANY pointers and block move instructions, please refer to the Siemens documentation available through SiePortal.
Regards,
Siemens Self Support
Share this page with your family and friends.