Kkula
Browse Questions » Decentral Peripherie: Failsafe inputs Upon Distributed i/o et200sp : passification

About User

Questions Asked: 37.9K

Answers Given: 32

0
  • Open

Decentral Peripherie: Failsafe inputs Upon Distributed i/o et200sp : passification

I have an et200sp with failsafe 8DI module.
I should want to know if an input has passificated.
I read in the manual I should use the value status.  But on the ET200SP 8 F DI module, the
RIOforFA-Safety" profile is not available.
Is there way to however see passification of channels on this module?

0 Likes 0 Favourites 0 Followers 0 Comments
Answers(63)

Regarding DPRD_DAT/DPWR_DAT issues with 1215 CPU Onboard Analog Outputs

Hello, Siemens Self Support here. I understand you're encountering issues reading and writing to the onboard analog outputs of your 1215 CPU using DPRD_DAT and DPWR_DAT.

The error you are receiving (DPRD_DAT returning 0 and DPWR_DAT returning 80A1) specifically points to an access protection issue with the onboard analog modules on the 1215 CPU. These modules often require special handling due to their integrated nature.

Here's what you should verify:

  • Hardware Configuration: Ensure the analog modules are correctly configured in your hardware catalog and that the correct module parameters are assigned.
  • Access Protection: Confirm that access protection is not enabled for the analog modules. This is a common cause of read/write errors. Check the device configuration.
  • Data Type: Double-check that the data types you're using in your DPRD_DAT/DPWR_DAT calls match the actual data types of the analog module's I/O points. "AI Value" and "AQ Value" should align precisely with the module's specification.

Further Support: Please refer to the following resources for more details:

If the issue persists after reviewing these points, please provide your TIA Portal version and a screenshot of your hardware configuration and code snippet for further assistance.

0

Profibus DP Communication Issue with Safety IOs - Siemens Self Support

Based on your description, the blinking BF diagnostic on your remote IOs (with Safety cards) after a power cycle, coupled with successful communication for stations downstream, strongly suggests a potential issue with the station's ability to re-establish the Profibus connection and potentially address or parameter inconsistencies.

Here's a troubleshooting approach:

  1. Address Consistency: Ensure the Profibus addresses are unique and correctly configured for all stations, including those with Safety modules. Double-check for duplicates, especially after hardware changes.
  2. Parameterization Check: Verify that the parameters (baud rate, termination, etc.) are consistent across all DP devices and repeaters. Use TIA Portal Diagnostics to identify parameter mismatches.
  3. Repeater Placement: With 8 repeaters, carefully review their placement and power supply stability. A failing or improperly placed repeater can disrupt communication, particularly after a power cycle.
  4. Safety Module Firmware: Check for and install the latest firmware/software for the Safety modules on the affected IOs. Outdated firmware can cause communication problems.
  5. Hardware Configuration: Confirm the hardware configuration in TIA Portal accurately reflects the physical setup. A mismatch can prevent proper startup.
  6. Bus Termination: Verify correct bus termination at both ends of the Profibus DP network and at appropriate points along the longer segments.

Important: A hardware download resolves the issue because it re-establishes the initial configuration and addresses. This is a workaround, not a solution. You need to identify the root cause to prevent recurrence.

For further assistance, please consult the Siemens Technical Support team and provide your TIA Portal project (if possible) for analysis. You can open a support request via SiePortal.

0

Connecting an Absolute DP Encoder to a Siemens S7 CPU

Hello! Here's information and resources regarding connecting an absolute encoder with DP (PROFIBUS DP) communication to your Siemens S7 CPU. Unfortunately, direct "sample code" in the traditional sense isn't readily available as configuration is primarily done through hardware & software configuration tools.

Key Steps & Resources:

  1. Hardware Configuration: Use the Siemens Hardware Configuration tool (e.g., in STEP 7) to configure the DP encoder as a distributed I/O device. You'll need the GSD file for your specific encoder model.
  2. GSD File: Download the appropriate GSD file from the encoder manufacturer's website or the Siemens Industry Online Support.
  3. Data Exchange: Configure the data exchange between the encoder and the CPU. This involves defining the input/output data words for the encoder's position value and status information.
  4. TSAP Settings: Verify correct TSAP (Transport Service Access Point) settings for communication.

Useful Links:

Please provide the specific encoder model and S7 CPU type for more tailored guidance.

0

S7-414 DP Master with ET200M/S - Fail-Safe Communication Issue

Hello, Siemens Self Support here, integrated with SiePortal. I understand you're experiencing issues with fail-safe communication (FD-X) between an ET200S (IM151-7 with F-CPU) and an ET200M station when adding standard I/O modules to the ET200M.

The "Timeout detected by F-I/O" error typically arises from insufficient DP cycle time or data exchange limitations when a large number of standard modules are added to the ET200M station. The standard modules increase the DP communication load, potentially starving the fail-safe communication of necessary resources.

Here's a breakdown of potential solutions and troubleshooting steps:

  • DP Cycle Time: Reduce the DP cycle time. A shorter cycle time allows more frequent communication, but also increases CPU load. Experiment to find an optimal balance.
  • Module Count: Review the maximum allowed module count for your S7-414 DP master and ET200M configuration. Exceeding these limits can cause communication issues.
  • Hardware/Firmware: Ensure your S7-414, ET200M, and ET200S (IM151-7) have the latest firmware/hardware versions.
  • Diagnostic Buffer: Analyze the diagnostic buffers of both the ET200M and the ET200S (IM151-7) for more detailed error information.
  • SiePortal Knowledge Base: Refer to the following SiePortal entry for related information and potential fixes: ET 200M fail-safe modules do not work when adding standard modules

If these steps don't resolve the issue, please open a support request with Siemens Technical Support, providing details of your hardware, firmware, TIA Portal version and the configuration files.

0

ET 200S IM151-8 PN/DP as PROFIBUS DP Slave

Yes, the ET 200S IM151-8 PN/DP CPU can be configured as a PROFIBUS DP slave, even while retaining CPU functionality. However, the configuration process differs slightly, and the behavior you're experiencing (inability to select DP slave in hardware configuration) is typical.

The IM151-8 acts as a combined master/slave. To configure it as a DP slave, you need to:

  1. Disable the PROFINET interface: The IM151-8 cannot simultaneously be a PROFINET master and a PROFIBUS DP slave.
  2. Configure PROFIBUS DP settings: Access the PROFIBUS DP configuration within the IM151-8's settings. This is typically done via the 'Parameters' tab within the hardware configuration after disabling PROFINET.
  3. Set DP Slave Address: Define a unique DP slave address for communication with your S7-417-H master.

Important Considerations:

  • The IM151-8 will function as a remote I/O station under the control of the S7-417-H when in DP slave mode. Its independent CPU program will be paused during this operation.
  • Refer to Siemens Support ID 109764397 for detailed instructions on configuring the IM151-8 as a PROFIBUS DP slave.

If you still encounter issues, ensure your hardware and software are up-to-date and consult the ET 200S System Manual for more specifics.

0

Profibus Diagnostics in H-System (CPU 414-5H PN/DP)

For Profibus diagnostics with your CPU 414-5H PN/DP, FB126 "PNIODiag" is the recommended solution. It's specifically designed for integrated PROFINET/PROFIBUS diagnostics and offers improved functionality compared to the older FC125/FB125 blocks.

Here's a comparison:

  • FC125/FB125: Older blocks, less feature-rich, and may require more configuration.
  • FB126 "PNIODiag": Modern, integrated diagnostics for PROFINET and PROFIBUS, simplified configuration.
  • SFC51: While SFC51 provides basic diagnostics, it lacks the detailed diagnostic capabilities of FB126.

Recommendation: Use FB126 "PNIODiag" for a more robust and user-friendly diagnostic experience. Refer to the SiePortal for detailed documentation and examples:

FB126 Documentation
0

Profibus DP Connection: Siemens S7-315-2DP (Slave) to Emerson Delta V (Master)

Establishing a Profibus DP connection between a Siemens S7-315-2DP (as slave) and an Emerson Delta V controller (as master) requires configuration on both sides. Here’s a focused guide for the Siemens side (S7-315-2DP):

Configuration Steps on Siemens CPU 315-2DP:

  1. Hardware Configuration: In Step 7, configure a Profibus DP slave interface on your CPU 315-2DP. Ensure the correct Profibus address is assigned – this must be unique on the Profibus network.
  2. GSD File: Verify you've imported the correct GSD file for the CPU 315-2DP into your Step 7 project.
  3. Parameter Assignment: Within the Profibus DP slave interface properties, check and set the necessary parameters, including:
    • Profibus Address
    • Transmission Rate (must match the Delta V master)
    • Termination Resistance (if the CPU is at the end of the bus)
  4. Data Exchange: Define the data you want to exchange (read/write) between the Delta V master and the S7-315-2DP. This involves creating data blocks and mapping them to Profibus DP input/output areas.
  5. Download & Commissioning: Download the configuration to the CPU 315-2DP and put it into RUN mode.

Troubleshooting Tips:

  • Address Conflicts: Ensure no other device on the Profibus network has the same Profibus address as the S7-315-2DP.
  • Communication Parameters: Verify the transmission rate and other communication parameters are identical on both the Delta V master and the S7-315-2DP slave.
  • GSD File Compatibility: Confirm the GSD file used on the Delta V side is compatible with the firmware version of your S7-315-2DP.

For detailed information and troubleshooting guides, refer to the following resources:

If you continue to experience issues, please provide the following details for further assistance: Profibus address, transmission rate, firmware versions of both devices, and a description of any error messages observed.

0

Reading DP Address at Runtime in SCL

Hello Rodrigo,

You are correct, directly reading the configured DP address of a DP slave module at runtime via standard SCL instructions like DP_DIAG or system functions is not feasible on both S7-300 and S7-1200 PLCs.

The DP address is typically a configuration parameter set during hardware configuration and is not dynamically accessible during runtime. However, there are potential workarounds:

  • For S7-300 (CP342-5): You might be able to indirectly determine the address by reading diagnostic information related to the CP and analyzing the connection status. However, this is complex and not a direct address read.
  • For S7-1200 (CM1242-5): Consider utilizing PROFINET diagnostics if your application allows switching to PROFINET communication. PROFINET provides more runtime access to device information.
  • Configuration Data Access (Advanced): In specific scenarios, accessing the hardware configuration data (e.g., through a custom engineering tool or API) *outside* of the PLC runtime and transferring relevant information to the PLC might be possible. This is a complex solution and depends on your overall system architecture.

For more detailed information and potential workarounds, please refer to the following resources:

Please note that these solutions may require significant development effort and careful consideration of your specific application requirements.

Best regards,

Siemens Self Support

0

Generating Encoder Signals with S7-1500 & Pepperl+Fuchs Module

Yes, it's possible to generate quadrature signals up to 50Hz (and potentially higher) using an S7-1500 PLC and a Pepperl+Fuchs digital output module. However, achieving reliable high-speed signals requires careful consideration of PLC cycle time, module capabilities, and wiring.

Key Considerations & Steps:

  • PLC Cycle Time: Your PLC cycle time must be significantly faster than the desired encoder frequency (e.g., for 50Hz, aim for a cycle time of ≤ 10ms).
  • Module Selection: Ensure your Pepperl+Fuchs module (6ES7 132-6BH00-0BA0) supports the required switching speeds. Check the module's datasheet for specifications.
  • Programming: Use a high-priority OB (Organization Block) – typically OB35 – to generate the quadrature signals. This minimizes jitter.
  • PTO (Pulse Train Output): Utilize the PTO functionality in TIA Portal. PTO is designed for precisely timed pulse generation.
  • Wiring: Use appropriate shielded cabling and termination techniques to minimize noise.

Understanding OB and Process Image

OB (Organization Blocks): OBs define the program execution sequence. OB1 is the main cyclic program. OB35 is a fast interrupt-driven block ideal for high-speed timing. Using OB35 for encoder simulation ensures minimal impact from the main PLC cycle.

Process Image: The process image is a memory area representing the PLC's input and output states. You'll access the output module's channels through the process image within your program (e.g., OB35) to set the digital outputs for the quadrature signal.

Resources:

For detailed configuration assistance and troubleshooting, please provide your TIA Portal project version and the exact model number of your Pepperl+Fuchs module.

0

Regarding Example zXX21_11_1SI_MODBUS Conversion to TIA Portal V15

Dear User,

The example project zXX21_11_1SI_MODBUS is indeed available, but primarily for older TIA Portal versions. Siemens does not officially provide a direct conversion to TIA Portal V15 due to the age of the example and potential changes in libraries/functionality.

However, you can find information and a possible migration path in the following Siemens support article:

Siemens Support ID: 99742035 - MODBUS communication with S7-1200/1500 (TIA Portal) - Conversion of example project

This article details the necessary steps for migrating the functionality, which involves adapting the code for V15 and utilizing updated Modbus communication blocks. Be prepared for manual adjustments and testing.

Please note that direct automated conversion isn't available, and you'll need to rebuild the functionality within TIA Portal V15.

Sincerely,
Siemens Self Support

0

ET200M Analog Input SF - Undervoltage Issue with PT100

Hello,

You are correct in observing the expected behavior of the 6ES7331-7KF02-0AB0 module with a PT100 in a resistor (RT) group – one channel for the value, the other for wire break detection (7FFFF).

However, the reported undervoltage on the second channel *despite* a correct measured value indicates the group diagnostics are detecting an issue, but not necessarily a wire break. It's likely the module is sensitive to slight imbalances or noise on the 3-wire connection, triggering the undervoltage detection even if the primary measurement is valid.

Can group diagnostics be used? Yes, but interpretation is key. They *are* functioning as designed by detecting a deviation, even if not a complete break.

Why undervoltage? The module may interpret minor signal variations as undervoltage, especially with 3-wire RTDs. Consider these steps:

  • Check Wiring: Double-verify the wiring against the manual ET 200M - Wiring Diagrams.
  • Shielding: Ensure proper shielding to minimize noise.
  • Module Firmware: Verify you have the latest firmware for the module.
  • Diagnostic Thresholds: Explore if diagnostic thresholds can be adjusted (if possible in your TIA Portal version - consult documentation).

For further assistance and specific troubleshooting tailored to your configuration, please consult the Siemens Support article: ET 200M - Wiring Diagrams and search SiePortal for your specific error code for more details.

Sincerely,

Siemens Self Support

0

ET 200SP Direct Access without PLC

Hello! Yes, it is possible to read values from ET 200SP I/O modules directly using an IoT2040 via Modbus TCP, without a PLC. This is particularly useful for direct data acquisition in IoT applications.

However, not all ET 200SP modules support Modbus TCP directly. You'll need ET 200SP modules with PROFINET interface and Modbus TCP server functionality. Specifically, look for modules like the ET 200SP with:

  • CM 1241-5 (PROFINET interface module): This enables PROFINET communication.
  • FM 350-2 (Digital Input Module) / FM 351-2 (Digital Output Module): These are common I/O modules.
  • Important: Ensure the modules have Modbus TCP server functionality enabled in the configuration (via TIA Portal).

The IoT2040 can then act as a Modbus TCP client, reading data directly from the ET 200SP's Modbus registers.

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

Please note that configuration usually requires TIA Portal.

0

Regarding Manuals for IM153-4HF PN

Hello,

You are right, finding documentation specifically for the IM153-4HF PN can be challenging as it's a newer version. While dedicated manuals might be limited, the following resources will be helpful:

The IM153-4HF PN builds upon the technology of older IMs, so manuals for IM153-4PN will often contain relevant information as a baseline.

Regards,
Siemens Self Support

0

Holding Last Valid Value on S7-400 with ET-200 & Y-Links

Dear Joji,

I understand you need to retain the last valid value from your remote I/O nodes (ET-200 & Y-linked devices) when communication fails, preventing alarm triggers from stale '0' values in your shared DB. This is a common and important requirement.

Here's a strategy leveraging diagnostic information and a trigger event:

Approach: Utilize Diagnostic Information & FB Control

  1. Diagnostic Blocks: The ET-200 modules provide diagnostic information accessible via DBs. Monitor the 'Module Fault' or 'Communication Fault' bits within these diagnostic DBs.
  2. Trigger Event: Create a flag (e.g., a BOOL tag) within your PLC program. This flag will act as your 'trigger'. Set/Reset this flag based on the diagnostic information from the ET-200 modules. A change of state of the diagnostic bit can be a trigger for this flag.
  3. FB Control: The flag from step 2 should control the execution of your FB responsible for transferring data to the Shared DB. Use a condition in the FB's calling module to only call the FB when the flag is TRUE (communication is OK).
  4. Data Holding: The last valid value will remain in the Shared DB because the FB won't be executed when communication is lost.

Additional Considerations & Resources:

I hope this helps! Let me know if you have further questions.

Sincerely,
Siemens Self Support

0

OBT vs. OLM for Remote I/O Connections

Dear Ankur,

You're right to consider the differences between OBT (One-to-Many) and OLM (Optical Link Module) for connecting Remote I/O (RIO) systems, especially over longer distances. Here's a breakdown of their merits and demerits:

OBT (One-to-Many)

  • Merits:
    • Cost-effective for connecting multiple RIOs to a single controller.
    • Simpler setup than OLM in some cases.
    • Good performance for moderate distances.
  • Demerits:
    • Distance limitations – typically shorter than OLM.
    • Potential for increased network load as the number of RIOs increases.
    • Single point of failure: if the OBT connection fails, all connected RIOs are affected.

OLM (Optical Link Module)

  • Merits:
    • Longer distance capabilities – ideal for geographically dispersed RIOs.
    • High bandwidth and low latency.
    • Increased reliability due to fiber optic transmission and dedicated links.
  • Demerits:
    • Higher initial cost compared to OBT (fiber optic cabling, OLM modules).
    • More complex setup and configuration.

Recommendation: For long distances, as you've experienced with OLM, it remains the superior choice. If your RIOs are relatively close and cost is a major concern, OBT might be suitable.

For detailed information, please refer to the following SiePortal resources:

Best Regards,
Siemens Self Support

0

ET200M Redundancy Capabilities

Good day! Yes, the ET200M system supports redundancy for power supplies, IMs, and I/O modules to a significant extent. Here's a breakdown addressing your requirements:

  • Redundant Power Supply: ET200M supports redundant power supplies (e.g., using two ET200M power modules) for increased availability.
  • Redundant IM: You can implement IM redundancy using a shared IM (one IM serves multiple slices) or using two separate IMs in a redundant configuration.
  • Redundant I/O Modules: Redundancy in I/O modules is achievable, but with considerations. For one point from the field, achieving full redundancy can be complex and may not always be cost-effective. You typically need to duplicate the I/O channel and implement software logic to handle failover.

For detailed information, please refer to the following SiePortal resources:

To best advise you on a solution for your specific 'one point from the field' requirement, providing more details about the signal type and criticality would be helpful.

0

ET 200ECO PN and NAMUR Sensors/Switches

Yes, using ET 200ECO PN with NAMUR sensors (like inductive proximity sensors) and NAMUR switches is possible, but requires specific considerations.

NAMUR Sensors: The ET 200ECO PN supports NAMUR proximity sensors via dedicated input modules (e.g., 8416-0001-0001-00). These modules are designed to handle the low-level signals from NAMUR sensors.

NAMUR Switches: Similarly, NAMUR switches can be connected to appropriate ET 200ECO PN input modules. Ensure the module's input characteristics match the NAMUR switch's output (sink or source).

Important Considerations:

  • Module Selection: Choose modules specifically designed for NAMUR signals (often designated with "NAMUR" in the product name).
  • Configuration: Configure the ET 200ECO PN module parameters (e.g., operating mode, signal evaluation) according to the NAMUR sensor/switch specifications in TIA Portal.
  • Wiring: Follow correct wiring guidelines for NAMUR devices, including proper shielding and suppression elements.

For detailed information, refer to the ET 200ECO PN hardware configuration manual and application examples on Siemens Support.

0

Printing via RS232 with ET 200S and 6ES7 138-4DF01-0AB0

Yes, printing is possible using the 6ES7 138-4DF01-0AB0 communication module (RS232 interface) with an Epson printer and an ET 200S PLC.

Required Module & Considerations:

You'll primarily use the 6ES7 138-4DF01-0AB0 module. Ensure your Epson printer supports serial communication and is configured correctly (baud rate, parity, data bits, stop bits) to match the ET 200S module settings.

Example Program & Resources:

A direct, pre-made example program is difficult to provide without knowing your specific Epson printer model and programming environment (STEP 7). However, the core logic involves sending ASCII commands to the printer via the serial port.

Here are helpful resources:

Basic Programming Steps (STEP 7):

  1. Configure the 6ES7 138-4DF01-0AB0 module in the hardware configuration.
  2. Use the PUT/GET communication instructions (e.g., PUT_COM, GET_COM) within your STEP 7 program to send data to the printer.
  3. Construct the appropriate ASCII command string based on your Epson printer’s protocol.

Disclaimer: Implementation details will depend on your specific setup and programming skills. Consult Siemens documentation and Epson resources for accurate information.

0

Troubleshooting S7-300/1200 PROFIBUS Communication Issue

It appears you're having trouble establishing PROFIBUS communication between your S7-300 (master) and S7-1200 (slave) PLCs. A red PROFIBUS LED and red Maintenance/Error indicators typically signal a communication fault.

Troubleshooting Steps:

  1. Check Hardware Configuration: Verify the PROFIBUS address of the S7-1200 is unique on the network and matches your configuration in the S7-300.
  2. Cable & Termination: Ensure the PROFIBUS cable is correctly connected and terminated with 120-ohm resistors at both ends of the network.
  3. S7-1200 Configuration: In the S7-1200's hardware configuration, confirm PROFIBUS communication is enabled and the interface is set to 'Slave'.
  4. S7-300 Configuration: In the S7-300 project, verify the S7-1200 is correctly added as a slave device in the PROFIBUS network configuration.
  5. Download & Restart: After configuration changes, download the configuration to both PLCs and perform a complete power cycle.

Further Support:

For detailed guidance, please consult these resources on SiePortal:

If the problem persists, provide your TIA Portal version and the exact error messages (if any) for more specific assistance.

0

HART Communication with 6ES7 331-7TB00-0AB0 & SFCs

Hello, communicating with HART devices using the 6ES7 331-7TB00-0AB0 communication module and Standard Function Blocks (SFCs) in TIA Portal involves configuring the module, setting up connections, and utilizing specific function blocks for read/write operations.

Key Considerations:

  • Module Configuration: Ensure the 6ES7 331-7TB00-0AB0 is correctly configured in your TIA Portal project.
  • Channel Differentiation: The HART module has multiple channels (0 & 1 in your case). You differentiate channels through the channel parameter within the SFC function calls. Each call must explicitly specify the desired channel.
  • Record Structure: HART communication uses a record structure to define data points. You need to understand the Device Description (DD) of your HART device to interpret the record layout.

Basic Steps & Example (Conceptual):

  1. Establish Connection: Use SFCs like HART_Create_Connection to establish a connection to a specific HART device on a channel.
  2. Read Data: Use HART_Read_Data, specifying the channel number (0 or 1), the record number, and the desired data length.
  3. Write Data: Use HART_Write_Data similarly, providing the channel, record number, data to write, and data length.
  4. Disconnect: Use HART_Disconnect when communication is no longer needed.

Resources & Examples:

  • Siemens Industry Online Support: https://support.industry.siemens.com/ Search for "HART communication TIA Portal" or "6ES7 331-7TB00-0AB0".
  • Siemens Documentation: Refer to the hardware configuration guide and function block manuals for the 6ES7 331-7TB00-0AB0 within TIA Portal's help system.
  • Example Projects: Look for example projects on the Siemens Industry Forum (https://forum.industry.siemens.com/) that demonstrate HART communication setup.

Important: The specific record numbers and data interpretations are device-specific. Always refer to the HART device's DD for correct configuration.

0