Configuring Axis Values & PRESET Function via PLC with FM357-2

Dear Nanu,

To change the actual axis value configured through FM357-2 and write parameters from the PLC, you'll primarily utilize the FM357-2's parameter interface via PROFIdrive/PROFIsafe.

Changing Actual Axis Value: You can modify the actual position value by writing to the Position Demand Value parameter (parameter number varies based on drive configuration – check your hardware configuration list - HCL). This is typically done using the 'Write Parameter' function block in your PLC program, communicating through PROFIdrive.

Writing Parameters (PRESET Function): To configure the PRESET function via PLC:

1. Parameter Addressing: Identify the parameter numbers for the PRESET function within the FM357-2 parameter list (refer to the FM357-2 manual - FM357-2 Manual).
2. PLC Programming: Use the 'Write Parameter' function block in your PLC, addressing the correct parameter numbers with the desired preset values.
3. PROFIdrive Communication: Ensure proper PROFIdrive communication is established between the PLC and the FM357-2.

Important Resources:

• FM357-2 Firmware Manual
• SINAMICS Drive Configuration via PLC

For detailed step-by-step instructions and troubleshooting, consult the FM357-2 documentation on SiePortal and consider searching for application examples related to PLC-based parameterization.

Sincerely,
Siemens Self Support

Troubleshooting Recurring Module Errors

Good day! It sounds like you're experiencing a recurring issue with a module, despite replacement. Since you've already verified input signals, let's explore potential causes.

• Power Supply: Check for voltage fluctuations or instability affecting the module.
• Environmental Factors: Investigate potential interference (EMC) or temperature issues.
• Software/Firmware: Ensure the module's firmware is up-to-date and compatible with the system.
• Backplane/Connector Issues: Inspect the backplane and connectors for damage or corrosion.
• System Configuration: Review the system configuration for any conflicting settings.

To assist you further, please provide the following information via Siemens Support Portal :

• Module type and order number
• Specific error message
• System architecture (PLC type, etc.)
• Details of when the error recurs (e.g., after a specific time, under certain load conditions)

We can then leverage SiePortal's knowledge base and expert resources to pinpoint the root cause.

Data Loss on CPU 315-2DP with MMC Card

It sounds like you're experiencing intermittent loss of retained data from your CPU 315-2DP (6ES7 315-2AH14-0AB00) despite using non-retain DB settings. The fact that a firmware upgrade to 3.3.8 seems to have resolved it is a positive sign, but the rarity of the issue makes confirmation difficult.

How Retained Data is Stored

The CPU 315-2DP uses the MMC card to store retained data (DBs) during power loss. The process involves:

• Power-Loss Detection: The CPU detects a voltage drop.
• Data Backup: Upon detection, the CPU initiates a write operation to save relevant DBs to the MMC card.
• Energy Reserve: An internal capacitor provides power to complete this write process.

Possible Causes & Troubleshooting

Your suspicion about the 3rd-party power supply is valid. Here's a breakdown:

• Power Supply Quality: A 3rd-party power supply may not have the same robust filtering or hold-up time (the time it can maintain voltage during a power dip) as a Siemens power supply. A rapid voltage decline can interrupt the data backup process before it completes.
• MMC Card Condition: Although less likely, a failing MMC card could contribute to data corruption.
• Firmware Bug (addressed by 3.3.8): The firmware update likely addressed a potential race condition or timing issue during the power-loss backup procedure.

Recommendations

1. Test with Siemens Power Supply: If possible, temporarily test with a genuine Siemens 24V power supply (e.g., 6ES7 580-1LA02-0XA0) to see if the issue recurs.
2. Monitor Power Supply Voltage: Use a multimeter to monitor the 24V DC voltage during power cycling to observe the hold-up time and identify potential voltage dips.
3. MMC Card Check: Consider replacing the MMC card with a new one as a preventative measure.
4. SiePortal Support: For detailed analysis and official confirmation, please create a support request via SiePortal.

Sending Programs from WinCC Flex to OP77A via Ethernet

No, it is generally not possible to directly send programs from WinCC Flexible (WinCC Flex) to an OP77A HMI via Ethernet when using a CPU 313C with an MPI/PROFIBUS interface and a CP343-1 Lean for programming.

Here's why:

• OP77A Communication: The OP77A typically communicates with the CPU 313C via MPI/PROFIBUS, not directly via Ethernet.
• CP343-1 Lean Role: The CP343-1 Lean is used for programming the CPU and is not typically involved in transferring programs *to* the HMI.
• WinCC Flex & HMI Transfer: WinCC Flexible program transfer to HMIs is usually done through a direct connection (PPI, PROFIBUS, Ethernet if the HMI supports it) or via a separate Ethernet connection to the HMI itself.

Recommended Approach:

1. Transfer the program to the CPU 313C using the CP343-1 Lean and the appropriate programming software (STEP 7).
2. The OP77A will then download the necessary data/program from the CPU 313C over the MPI/PROFIBUS link.

For more information, please refer to these resources on the Siemens Support website (SiePortal):

• OP77A Communication
• CP343-1 Lean Configuration

If you have a specific network configuration and are attempting a different approach, please provide more details for a more accurate assessment.

Successor for 1XP88001-1/1024 PULSE ENCODER

The successor to the 1XP88001-1/1024 PULSE ENCODER is the 6ES7193-0CA00-0AA0.

Please refer to the SiePortal for detailed information, including specifications and ordering information: Siemens Support Link.

You may also find helpful information regarding migration and compatibility on the Siemens Industry Online Support platform.

Controlling a Stepper Motor Axis with FM 353

Yes, it is possible to connect a reference point switch and hardware limit switches to the FM 353 for stepper motor control. The FM 353 provides sufficient inputs for this purpose.

Connections:

• Reference Point Switch (3 cables): Connect to a Digital Input (DI) module. Use two inputs for the switch - one for each side of the switch to detect position.
• Hardware Limit Switches (2 cables each): Connect each limit switch to a separate Digital Input (DI) module.

Configuration in STEP 7:

Within your STEP 7 project, you'll need to configure the FM 353's input modules and associate the DI addresses with the relevant functions in your technology object (PTO/PTP). Specifically, map the DI's to:

• Reference Point Input: Used for homing routines.
• Limit Switch Inputs: Configured as hardware limits to prevent overtravel.

Further Information:

Refer to the FM 353 manual (available on Siemens Support) for detailed wiring diagrams and configuration instructions. Also, review Siemens documentation on PTO/PTP objects for configuring stepper motor control and limit switch integration.

Electrical Considerations for Analog Module Wiring

You've encountered a common issue related to grounding and potential differences when wiring analog modules. The behavior you observed (all channels reading 7FFF) indicates a ground loop or potential difference issue.

While a single definitive guide doesn't explicitly detail this specific scenario, Siemens documentation addresses key principles. Here's a breakdown and relevant resources:

• Grounding is Critical: Analog modules are sensitive to ground potential differences. Connecting the signal grounds (-) to the module's power supply ground (-) as you've done is the correct approach. This establishes a common reference point.
• Potential Differences: A potential difference between the signal ground and the module's ground creates unwanted currents, leading to inaccurate readings or module failure.
• Shielded Cables: Use shielded cables for analog signals to minimize noise and interference. Properly ground the shield at one end only (typically at the PLC/module end).

Recommended Resources:

• SIMATIC Process Control System PCS 7 - Grounding Concepts: This provides a solid foundation for understanding grounding in Siemens systems.
• Analog Signal Wiring Best Practices: (While this link might lead to a support request, it highlights Siemens' support for addressing such issues).
• Refer to the hardware configuration manual for your specific analog module for grounding recommendations.

Troubleshooting Tip: Always verify the ground potential between the signal source and the module before connecting. A multimeter can help identify unwanted voltage differences.

Backing up S7-317F CPU Project from MC Card

Dear Vorapob,

You can backup the project file from the MC card of your S7-317F CPU to another MC card using a PC adapter designed for MC cards. Here’s how:

1. Hardware Required: You'll need a SIMATIC MC Card Reader (e.g., 6ES7 972-0100-001A) to connect the MC card to your PC.
2. Software Required: Use STEP 7 software (V5.x) to manage the project on your PC.
3. Procedure:
   1. Remove the MC card from the S7-317F CPU.
   2. Insert the MC card into the SIMATIC MC Card Reader connected to your PC.
   3. Open STEP 7.
   4. Use the 'Access to Card' function (PLC > Download > Access to Card) to read the project from the MC card to your PC.
   5. Insert a new MC card into the card reader.
   6. Use the 'Write to Card' function (PLC > Upload > Write to Card) to copy the project from your PC to the new MC card.

For detailed instructions and compatible hardware, please refer to the following resources on SiePortal:

• MC Card Reader - SIMATIC
• How to backup and restore SIMATIC S7 projects

Best Regards,
Siemens Self Support

Siemens Support - S7-300 & Software Purchase (Albania)

Hello, as Siemens Self Support integrated with SiePortal, I can assist you with locating sales options and addressing your Industry Mall registration issue.

PLC S7-300 & Software Procurement:

Since you don't have local distributors in Albania, here are options for purchasing directly:

• Siemens Online Store: Check availability and order directly if shipping to Albania is supported: S7-300 Product Page
• Siemens Industry Mall: While you're facing registration issues (addressed below), this is generally a good source: Siemens Industry Mall
• Contact Siemens Sales: Reach out to a Siemens sales representative for assistance with your order. You can find contact information for your region here: Siemens Contact Page. Specifically inquire about options for countries without direct distribution.

Industry Mall Registration Issues:

Registration problems can occur due to several reasons. Please try these steps:

• Check your spam/junk folder: The activation email might be there.
• Verify email address: Ensure you entered the correct email address.
• Contact SiePortal Support: For registration issues with Industry Mall/SiePortal, directly contact their support team. You can find help here: SiePortal Registration Help

I hope this helps! Don't hesitate to ask if you have further questions.

SIMATIC 314 IFM Analog Module Visibility in HW Config

Dear Customer,

We understand you are experiencing issues with configuring the integrated analog inputs/outputs (AI4/AO1) on your SIMATIC 314 IFM CPU (6ES7-314-5AE03-0AB0) within Step 7 V5.5 SP4 HF11.

This behavior – where the analog modules are visible with a CPU 313C but not the 314 IFM – is a known issue related to the hardware configuration data within the Step 7 project. The CPU 314 IFM requires specific hardware support data that might be missing or corrupted in your current project.

Resolution Steps:

1. Check Hardware Support Package: Ensure you have the latest hardware support package installed for the SIMATIC 300/314 family within Step 7. You can download this from Siematic Support.
2. Project Recovery: Try opening a default SIMATIC 314 IFM template project in Step 7 and then inserting your CPU into this new project. This ensures you start with correct hardware configuration data.
3. HW Config Compilation: After making changes in HW Config, always compile the hardware configuration.
4. Re-Download: After making any changes, download the entire project to the CPU.

If the issue persists, please provide your Step 7 project (or a simplified version demonstrating the problem) to Siemens Support through the SiePortal for further investigation. Please include screenshots of your HW Config showing the missing modules.

Sincerely,
Siemens Self Support

AI 465 & 498-1AA41 - Function Card Compatibility

You are correct to notice the limited Function Card (FC) options for the AI 465 with measure module 498-1AA41. Currently, Siemens documentation primarily lists FC 460, 463, 464, and 466 as compatible.

Regarding using FC 100 instead of the older FC 350: FC 100 is generally not a direct replacement for FC 350. They have different capabilities and may not support all the features required by your AI 465/498-1AA41 configuration.

Recommendation: Please consult the Siemens Support or review the SiePortal documentation specifically for the AI 465 and 498-1AA41 module to confirm compatibility. Providing your specific application details to Siemens Support will help determine the best FC option.

Failsafe Analog Output Modules in Siemens PLCs

Dear Ganesan,

You are correct, Siemens does not offer a dedicated failsafe analog output module like those available for digital outputs.

Technical Reason:

Achieving failsafe behavior with analog outputs is significantly more complex due to the continuous nature of the signal. Detecting a 'safe' state requires more sophisticated diagnostics and considerations for signal degradation.

Alternative Solutions:

1. Failsafe Digital Output with Conversion: Use a failsafe digital output module and an external Digital-to-Analog Converter (DAC). This is the most common workaround.
2. Software-Based Solutions: Implement software diagnostics to monitor the analog output signal and trigger a safe state if deviations are detected. This requires careful design and validation.
3. Redundancy: Employ redundant analog output paths with comparison logic. This adds complexity and cost.

For detailed information and support articles, please refer to the SiePortal:

Sincerely,
Siemens Self Support

S7-300 I/O Address Change Issue

You're experiencing issues changing I/O addresses on your S7-300 hardware. This typically occurs due to configuration errors or hardware restrictions.

Here's a breakdown of potential causes and solutions:

• Configuration Errors: Ensure the hardware configuration in your STEP 7 project precisely matches the physical setup. Double-check module addressing and parameter assignments.
• Protected Modules: Some modules may have write protection enabled. Check the module's DIP switches or software settings for any protection mechanisms.
• Firmware Issues: While less common, outdated firmware can sometimes cause issues. Consider updating the firmware of your CPU and I/O modules if possible.
• STEP 7 Version: Confirm you are using a compatible version of STEP 7 for your S7-300 CPU.

For detailed troubleshooting steps and FAQs, please refer to this SiePortal FAQ on Changing I/O Module Addresses.

If the problem persists, please provide more details about your setup (STEP 7 version, CPU type, specific modules affected) for further assistance. You can also search for specific error messages in the Siemens Support Portal.

S7-300 PLC Register Ranges & Cycle Performance

Dear Paresh,

Here's a breakdown of register details for S7-300 PLCs, specifically for CPU 314 and CPU 315-2 DP, along with information on cycle performance. Please refer to the Siemens documentation linked below for complete details.

Register Ranges

• Merker Word (MW): Both CPU 314 and CPU 315-2 DP support up to MW1000. (1000 Merker Words)
• Input Word (IW):
  • CPU 314: Up to IW256
  • CPU 315-2 DP: Up to IW512
• Output Word (QW):
  • CPU 314: Up to QW256
  • CPU 315-2 DP: Up to QW512
• Data Block (DB): DB size is configurable and depends on available memory.

Registers Readable/Writable per Cycle

The number of registers you can read or write in one cycle depends heavily on the program complexity, instruction mix, communication overhead, and hardware configuration. However, as a general guideline:

• Simple operations (e.g., moving data between registers): Hundreds of words per cycle are typically possible.
• Complex operations (e.g., arithmetic calculations, function calls): The number will be significantly lower.
• Communication (e.g., PROFINET, PROFIBUS): Communication will consume cycle time, reducing the number of register operations.

Important Note: The maximum achievable performance should be determined through testing and profiling your specific application.

Resources

For detailed information, please consult the following Siemens documentation:

• S7-300 CPU 31x System Manual
• S7-300 CPU 315-2 DP Manual

Sincerely,
Siemens Self Support
Integrated with SiePortal

Troubleshooting Red SF Indicator on IM 151-1 HF & CPU

Based on your detailed description and troubleshooting steps, the issue appears to be related to a hardware fault specifically triggered by the wiring or the IM 151-1 HF module itself, rather than a software configuration problem.

Key Observations & Recommendations:

• Module Swapping Results: The fact that the SF followed the 4 F-DO module (even after being swapped back) strongly indicates the module is faulty or sensitive to the wiring/environment in Control Panel 2.
• Wiring Sensitivity: Your initial power cycling and disconnection of the wiring temporarily resolved the issue, suggesting a potential wiring problem (short circuit, noise interference, etc.). However, this effect disappearing after repeated cycles points away from a simple wiring issue.
• 4fb03 Module Test: The SF reappeared after replacing the 4fb02 with a 4fb03, even with correct DIP switch settings and HW configuration, reinforces the suspicion of a hardware problem, potentially within the IM 151-1 HF module or its backplane connection.

Recommended Actions:

1. Thorough Wiring Check: Despite previous checks, meticulously inspect the wiring connected to the 4 F-DO module on Control Panel 2. Look for damaged insulation, loose connections, or potential sources of noise.
2. IM 151-1 HF Module Test: Try swapping the entire IM 151-1 HF module from Control Panel 1 to Control Panel 2. If the SF *follows* the IM 151-1 HF module to Control Panel 2, the IM 151-1 HF module in Control Panel 2 is likely defective.
3. Backplane Inspection: Inspect the backplane connector for the IM 151-1 HF in Control Panel 2 for any bent pins, corrosion, or damage.
4. Review Diagnostic Buffers: Carefully analyze the attached CPU diagnostic buffers (provided in the original query). Focus on any recurring errors related to the IM 151-1 or the 4 F-DO module.

Further Support:

If the above steps don't resolve the issue, consider opening a support request with Siemens directly via the Siemens Support Portal. Be sure to include the diagnostic buffers and a detailed description of all troubleshooting steps taken.

Connecting AO to AI for Signal Verification

Yes, it is generally possible to temporarily connect an analog output (AO) channel directly to an analog input (AI) channel for testing purposes, but with caution.

Since you're troubleshooting a loop-powered 4-20mA positioner, verifying the AO signal is a good first step. Connecting to an AI channel allows you to confirm the AO module is generating the expected 4-20mA signal range when commanded different output values.

Important Considerations:

• Voltage Limits: Ensure both the AO and AI channels have compatible voltage ranges. Typically, 4-20mA loops operate with a 0-20V loop supply, and the AI channel needs to be configured for current input with an appropriate series resistor.
• Grounding: Confirm common grounding between the AO and AI modules to prevent issues.
• Temporary Connection: This should be a temporary test configuration only.

For detailed information on Siemens AI/AO modules and configuration, please refer to the SiePortal documentation: Siemens Support Portal.

If the AO doesn't show correct values on the AI, investigate the AO module’s configuration and power supply. If the AO *does* function correctly, the issue likely lies with the Samson positioner or the wiring to it.

MySWR & IM153-2BA01 Switching Issue - Siemens Self Support

Dear SexDriver,

Thank you for your query regarding the IM153-2BA01 slave switching behavior in your redundant MySWR configuration (two 315-2DP-2AG10 CPUs with two IM153-2BA01 slaves, MPI redundancy).

The behavior you're observing – requiring an Overall Reset for the IM153-2BA01 to switch after initially downloading the hardware configuration – is a known issue. This is often related to initial state inconsistencies during the first switchover.

Key Considerations & Troubleshooting:

• Initial Download Sequence: Ensure the hardware configuration is downloaded to *both* CPUs (A & B) before attempting switchovers.
• MPI Configuration: Double-check the MPI parameter settings in both CPUs, ensuring they are correctly configured for redundancy. Refer to Siemens Support Forum for MPI troubleshooting.
• Diagnostic Buffer: Examine the diagnostic buffers of both CPUs and the IM153-2BA01 slaves after a failed switchover for specific error messages. This will give clues about the root cause.
• Firmware Versions: Confirm that the firmware versions of the CPUs and IM153-2BA01 are compatible.
• HW Configuration Check: Verify that the hardware configuration in the project is correctly mapped to the physical setup.

While an Overall Reset resolves the issue, it's not a sustainable long-term solution. Investigate the points above to address the underlying cause. If the problem persists, please open a support request via SiePortal (https://support.industry.siemens.com/) providing the diagnostic data for further analysis.

Best Regards,
Siemens Self Support

Memory Bottleneck During Program Download - PLC 314

Based on the error messages and your setup, you're encountering a memory issue despite using a 256KB memory card. Here's a breakdown and solution:

Understanding the Problem

The PLC 314 has limitations regarding memory card size and how it's utilized. The error "possible load memory bottleneck" indicates that the available memory (48832 bytes) is insufficient for the 100KB program, even though the card is larger. This is likely due to how the PLC addresses and manages memory, especially with the older CPU firmware.

Addressing the Download Issues

• Download to Memory Card: Direct download to the memory card from the programming interface (STEP 7) is often restricted on older PLCs like the 314. You will likely need a programmer (e.g., PG-M or PCMCIA adapter) to correctly format and write the program to the card.
• Download to CPU: The limited work/load memory (40KB) is the primary constraint. Even with a larger card, the CPU itself cannot process the entire 100KB program at once.

Recommended Solutions

1. Use a Programmer: Download the program to the 256KB memory card using a Siemens programmer. This ensures proper formatting and addresses the card's full capacity.
2. Program Optimization: Reduce the program size. Review your code for unnecessary instructions, data blocks, or redundancies.
3. CPU Upgrade: The most effective solution is to upgrade to a more modern PLC CPU (e.g., a CPU 315-2PN/DP or higher) that supports larger memory cards and has sufficient onboard memory to handle your 100KB program.
4. Memory Card Check: Although you stated it appears fine, verify the memory card's functionality with a card reader on a PC to ensure it’s not faulty.

Additional Resources

• Siemens Support - Memory Card Issues
• STEP 7 Download Errors

Note: Always back up your existing program before making any changes.

Siemens Analog Drives Compatible with the Module

You are correct, this module supports both analog drives and stepper motors. When referring to "analog drives" in the Siemens context, we generally mean drives that accept analog input signals (typically 0-10V, -10 to +10V, or 4-20mA) for speed or torque control.

Here are some Siemens drive series considered analog drives that can be connected:

• SINAMICS V20: A popular general-purpose drive with analog input capabilities. Learn more
• SINAMICS V90: Another versatile drive suitable for a wide range of applications with analog control. Learn more
• SINAMICS G120: A modular drive system offering extensive analog input options. Learn more
• SINAMICS G120X: Designed for demanding applications, it supports various analog control methods. Learn more

Important Note: Always consult the drive's documentation and the module's manual to ensure compatibility and proper configuration regarding voltage/current ranges and signal scaling.

For detailed compatibility information and specific configuration instructions, please refer to the Siemens Industry Online Support and search using your module's article number.

SF LED On - CPU315 2PN/DP Troubleshooting

Based on your description (SF LED on, RUN LED on, +5V LED on, OB80/85/121 not loaded, CPU stuck), and the fact that the system *appears* to be running normally despite this, the issue likely points to a configuration inconsistency or a problem with the startup sequence.

The SF LED indicates a fault, but the lack of diagnostic messages is unusual. Here's a breakdown of potential causes and troubleshooting steps:

Possible Causes:

• Incorrect Startup Configuration: The CPU might be trying to load an OB that doesn't exist or is corrupted.
• Parameter Access Restrictions: Certain parameter blocks might be write-protected preventing deletion of OBs.
• Hardware Conflict: Though nodes are accessible, a subtle hardware conflict *could* be interfering with the CPU's ability to fully initialize.

Troubleshooting Steps:

1. Force CPU to STOP: Even if the normal methods fail, attempt a power cycle. Completely disconnect and reconnect power to the CPU.
2. Check Configuration Consistency: Carefully compare the hardware configuration in your project file (TIA Portal or Step 7) with the actual hardware setup. Pay close attention to PROFIBUS addressing.
3. Download Full Configuration: Download the *entire* project (hardware and software) to the CPU. Do not attempt partial downloads.
4. Review Diagnostic Buffer (Attached File): I have reviewed the attached diagnostic buffer file. It shows several warnings regarding communication partner parameters for the ET200S stations, specifically missing or invalid parameters. Refer this FAQ to resolve communication issues.
5. Check OB Network: Verify the OB network is correctly configured in your project and downloaded to the CPU.

Important Note: Since all nodes are accessible, the PROFIBUS communication seems functional at a basic level. However, incorrect parameters can still cause internal CPU issues.

If these steps don't resolve the issue, please open a Siemens Support Request with the attached diagnostic buffer and your project backup for further analysis.