Kkula
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?
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:
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.
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:
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.
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.
Please provide the specific encoder model and S7 CPU type for more tailored guidance.
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:
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.
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:
Important Considerations:
If you still encounter issues, ensure your hardware and software are up-to-date and consult the ET 200S System Manual for more specifics.
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:
Recommendation: Use FB126 "PNIODiag" for a more robust and user-friendly diagnostic experience. Refer to the SiePortal for detailed documentation and examples:
FB126 DocumentationEstablishing 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):
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.
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 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
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.
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.
For detailed configuration assistance and troubleshooting, please provide your TIA Portal project version and the exact model number of your Pepperl+Fuchs module.
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 projectThis 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
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:
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
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:
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.
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
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:
I hope this helps! Let me know if you have further questions.
Sincerely,
Siemens Self Support
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:
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
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:
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.
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:
For detailed information, refer to the ET 200ECO PN hardware configuration manual and application examples on Siemens Support.
Yes, printing is possible using the 6ES7 138-4DF01-0AB0 communication module (RS232 interface) with an Epson printer and an ET 200S PLC.
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.
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:
PUT/GET communication instructions (e.g., PUT_COM, GET_COM) within your STEP 7 program to send data to the printer.Disclaimer: Implementation details will depend on your specific setup and programming skills. Consult Siemens documentation and Epson resources for accurate information.
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.
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.
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.
HART_Create_Connection to establish a connection to a specific HART device on a channel.HART_Read_Data, specifying the channel number (0 or 1), the record number, and the desired data length.HART_Write_Data similarly, providing the channel, record number, data to write, and data length.HART_Disconnect when communication is no longer needed.Important: The specific record numbers and data interpretations are device-specific. Always refer to the HART device's DD for correct configuration.
Share this page with your family and friends.