Configurazione e messa in servizio dei PLC: Guida completa alla configurazione e diagnostica dei PLC Siemens per CNC PLC SIEMENS: La Guida Completa: alle basi della programmazione all’automazione industriale avanzata: domina i sistemi Simatic S5, S7 e l’integrazione ... esempi pratici e strategie di ottimizzazione Maestro di PLC: Guida Completa all’Automazione Industriale: Progettazione, Programmazione e Strategie Avanzate per l’Efficienza dei Processi.

Imagine a future where seamless integration of diverse drive systems enhances your manufacturing efficiency. You, as a forward-thinking engineer, are exploring the potential of controlling non-Siemens drives with the Siemens S71500 PLC. The challenge of integrating a Nidec (Control Technique) drive with Siemens’ motion capabilities is not an obstacle but an opportunity. By leveraging telegram 102 for non-isochronous communication, you can achieve smooth motion control without the need for isochronous support. This approach opens up possibilities for applications where axis synchronization is not critical. With careful setup, including the use of specific OBs like MCPreServo and MCPostServo, and connecting the technological object to a DB, you can unlock the full potential of your Siemens PLC. While the journey may require significant effort, the outcome promises a robust and efficient control system that transcends traditional boundaries.

Quick Solution: Solve the Problem Quickly

Understanding Prerequisites for Non-Siemens Drive Integration

To successfully integrate and control a non-Siemens drive, such as a Nidec (Control Technique) drive, with a Siemens S71500 PLC, certain prerequisites must be met. Firstly, ensure that the non-Siemens drive supports the telegram structure used for communication with Siemens PLCs. This is crucial for compatibility and effective control. Secondly, familiarize yourself with the Siemens PLC’s motion control system, specifically the “positioning” technological object and its associated motion instructions. Understanding these components will facilitate the integration process.

Additionally, ensure that the necessary tools and software are available. This includes the Siemens programming software, such as TIA Portal, and the appropriate communication modules for connecting the PLC to the drive. Lastly, verify that the drive’s firmware is up-to-date to support the required communication protocols and functionalities.

Step-by-Step Procedure for Seamless Motion Control

Follow these steps to integrate and control a non-Siemens drive with a Siemens S71500 PLC

1. Insert Organization Blocks (OB): Begin by inserting specific OBs such as MCPreServo and MCPostServo into your PLC program. These blocks are essential for managing the motion control process.
2. Connect Technological Object to a Data Block (DB): Link the “positioning” technological object to a DB. This will facilitate the communication between the PLC and the drive.
3. Configure Communication Parameters: Set up the communication parameters in the PLC program. Ensure that the telegram type (e.g., telegram 102 for non-isochronous communication) is correctly configured to match the drive’s capabilities.
4. Test the Setup: After configuring the communication parameters, test the setup by running a simple positioning task. Monitor the drive’s response and adjust the parameters as needed to achieve smooth motion control.
5. Verify and Optimize: Finally, verify the setup by running more complex motion control tasks. Optimize the parameters based on the performance observed during testing.

Verification Techniques for Successful Drive Configuration

To ensure successful integration and control of the non-Siemens drive, employ the following verification techniques

• Parameter Validation: Double-check the communication parameters and telegram settings to ensure they are correctly configured for both the PLC and the drive.
• Performance Monitoring: Use the Siemens PLC’s monitoring tools to observe the drive’s performance during various motion control tasks. Look for any discrepancies or issues in the drive’s response.
• Error Logs: Review the PLC’s error logs for any communication errors or faults. Address any issues identified to ensure smooth operation.
• Functional Testing: Conduct functional testing by running predefined motion control scenarios. Verify that the drive responds accurately and the motion control tasks are executed as intended.

By following these steps and verification techniques, you can successfully integrate and control a non-Siemens drive with a Siemens S71500 PLC, achieving smooth and reliable motion control.

Telegram Compatibility: Telegram 102 for Non-Isochronous Control

Understanding Non-Isochronous Telegram 102 for Siemens S71500

Telegram 102, as defined by the IEC 61800-5-2 standard, is a non-isochronous communication protocol used for controlling drives. Unlike isochronous communication, which requires precise timing for data exchange, non-isochronous communication allows for more flexibility in data transmission. This makes Telegram 102 suitable for applications where strict synchronization is not critical, such as simple positioning tasks. For the Siemens S71500 PLC, Telegram 102 can be utilized to achieve effective control of non-Siemens drives, provided the drives support this telegram structure or have a compatible interpretation.

When using Telegram 102 for non-isochronous control, it is essential to understand the technical parameters and ranges that define its operation. For instance, the telegram includes fields for position, velocity, and torque commands, which must be correctly configured to ensure smooth motion control. Additionally, the PLC must be configured to send and receive these commands using the appropriate telegram type.

Integrating Non-Siemens Drives with Siemens PLC Motion Control

Integrating a non-Siemens drive, such as a Nidec (Control Technique) drive, with a Siemens S71500 PLC’s motion control system involves several steps. Firstly, ensure that the non-Siemens drive supports the Telegram 102 structure or has a compatible interpretation. This is crucial for effective communication and control. Secondly, insert specific Organization Blocks (OB) such as MCPreServo and MCPostServo into your PLC program to manage the motion control process.

Connecting the “positioning” technological object to a Data Block (DB) is another critical step. This facilitates the communication between the PLC and the drive. Configure the communication parameters in the PLC program, ensuring that the telegram type is set to 102 for non-isochronous communication. Test the setup by running a simple positioning task and monitor the drive’s response to ensure smooth motion control.

Implementation Challenges and Solutions for Non-Isochronous Control

One of the main challenges in integrating non-Siemens drives with a Siemens S71500 PLC is ensuring compatibility between the drive’s telegram interpretation and the PLC’s communication protocol. As highlighted by the user’s experience with a Mitsubishi drive, different drives may have varying interpretations of the same telegram, leading to potential issues in communication and control.

To overcome these challenges, it is recommended to thoroughly test the setup and adjust the parameters as needed. Use the Siemens PLC’s monitoring tools to observe the drive’s performance during various motion control tasks. Look for any discrepancies or issues in the drive’s response and address them promptly. Additionally, review the PLC’s error logs for any communication errors or faults and take corrective actions to ensure smooth operation.

For specific inquiries about telegram details, it is advisable to open a new discussion to avoid confusion and ensure that the technical support provided is accurate and relevant.

Siemens PLC Motion Control: Non-Siemens Drive Specifications

Guida completa alla programmazione PLC con Codesys: Guida pratica per la configurazione e l’ottimizzazione di sistemi PLC Strategie PLC Innovative: Ottimizzazione e Innovazione nei Controlli Industriali: Guida Pratica all’Automazione Moderna Ottimizzazione delle Prestazioni del PLC S7-1200: Guida completa alla programmazione e ottimizzazione dei PLC S7-1200

Understanding Non-Siemens Drive Compatibility with Siemens S71500

When integrating non-Siemens drives, such as a Nidec (Control Technique) drive, with a Siemens S71500 PLC, it is crucial to understand the compatibility requirements. Siemens PLCs are designed to work seamlessly with Siemens drives, which typically use telegram 105 for isochronous communication. However, for non-Siemens drives, compatibility hinges on whether the drive supports the same telegram structure or has a compatible interpretation of the telegram. This is essential for effective communication and control.

The IEC 61800-5-2 standard defines various telegrams for drive communication, including telegram 102 for non-isochronous control. While telegram 105 is ideal for synchronized motion control, telegram 102 offers flexibility for applications where strict synchronization is not critical. Ensuring that the non-Siemens drive supports or can interpret telegram 102 correctly is a key step in achieving successful integration.

Telegrams and Communication Protocols for Motion Control

Telegrams play a pivotal role in the communication between a Siemens S71500 PLC and a non-Siemens drive. For non-isochronous control, telegram 102 is particularly relevant. This telegram includes fields for position, velocity, and torque commands, which must be correctly configured to ensure smooth motion control. The PLC must be set to send and receive these commands using the appropriate telegram type.

Understanding the technical parameters and ranges defined by the IEC 61800-5-2 standard is crucial. For instance, the telegram 102 specifies the format and limits for position, velocity, and torque data. Ensuring that these parameters are correctly set in both the PLC and the drive will facilitate effective communication and control.

Implementing Non-Siemens Drives with Siemens PLC Motion Control

To implement non-Siemens drives with a Siemens S71500 PLC, start by inserting specific Organization Blocks (OB) such as MCPreServo and MCPostServo into your PLC program. These blocks manage the motion control process and ensure smooth operation. Connect the “positioning” technological object to a Data Block (DB) to facilitate communication between the PLC and the drive.

Configure the communication parameters in the PLC program, ensuring that the telegram type is set to 102 for non-isochronous communication. Test the setup by running a simple positioning task and monitor the drive’s response. Adjust the parameters as needed to achieve smooth motion control. It is important to note that significant effort may be required to make this setup work, as different drives may have varying interpretations of the same telegram.

For specific inquiries about telegram details, it is advisable to open a new discussion to avoid confusion and ensure that the technical support provided is accurate and relevant. Additionally, review the PLC’s error logs for any communication errors or faults and take corrective actions to ensure smooth operation.

Ensuring compatibility between the drive’s telegram interpretation and the PLC’s communication protocol is essential for successful integration.

Implementing Non-Siemens Drives: OB Blocks and DB Connection

Understanding Non-Siemens Drive Compatibility with Siemens S71500

When integrating non-Siemens drives, such as a Nidec (Control Technique) drive, with a Siemens S71500 PLC, it is crucial to understand the compatibility requirements. Siemens PLCs are designed to work seamlessly with Siemens drives, which typically use telegram 105 for isochronous communication. However, for non-Siemens drives, compatibility hinges on whether the drive supports the same telegram structure or has a compatible interpretation of the telegram. This is essential for effective communication and control.

The IEC 61800-5-2 standard defines various telegrams for drive communication, including telegram 102 for non-isochronous control. While telegram 105 is ideal for synchronized motion control, telegram 102 offers flexibility for applications where strict synchronization is not critical. Ensuring that the non-Siemens drive supports or can interpret telegram 102 correctly is a key step in achieving successful integration.

Exploring OB Blocks for Non-Siemens Drive Integration

To integrate non-Siemens drives with a Siemens S71500 PLC, you need to insert specific Organization Blocks (OB) into your PLC program. These OBs, such as MCPreServo and MCPostServo, manage the motion control process and ensure smooth operation. These blocks are essential for handling the pre-servo and post-servo operations, which are critical for the proper functioning of the drive.

Inserting these OBs into your PLC program is a fundamental step in the integration process. These blocks provide the necessary functionality to manage the motion control process, ensuring that the drive operates correctly. It is important to configure these OBs correctly to avoid any issues during the motion control tasks.

Configuring DB Connections for Smooth Motion Control

Connecting the “positioning” technological object to a Data Block (DB) is another critical step in integrating non-Siemens drives with a Siemens S71500 PLC. This connection facilitates the communication between the PLC and the drive, ensuring that the necessary data is exchanged correctly. The DB should be configured to hold the relevant parameters and data for the drive, such as position, velocity, and torque commands.

Configuring the DB correctly is essential for smooth motion control. The DB should be set up to handle the data exchange between the PLC and the drive, ensuring that the drive receives the correct commands and the PLC receives the necessary feedback. This setup allows for effective control and monitoring of the drive’s performance.

For specific inquiries about telegram details, it is advisable to open a new discussion to avoid confusion and ensure that the technical support provided is accurate and relevant.

Case Study: Mitsubishi Drive Integration Challenges and Solutions

Mitsubishi Drive Integration: Context and Challenges

In an industrial automation project within a mid-sized automotive manufacturing plant, the integration of a Mitsubishi drive with a Siemens S71500 PLC presented unique challenges. The plant, equipped with a variety of Siemens and non-Siemens drives, aimed to enhance its motion control capabilities. The primary challenge was to control external axes using the Siemens PLC’s motion control system, which traditionally supports Siemens drives via telegram 105 for isochronous communication.

The user sought to understand if it was feasible to integrate and control the Mitsubishi drive with the Siemens S71500 PLC’s “positioning” technological object and its associated motion instructions. The goal was to achieve smooth motion control without strict synchronization, as the application did not require isochronous communication. The challenge lay in ensuring that the Mitsubishi drive could interpret telegram 102 for non-isochronous communication correctly, as different drives may have varying interpretations of the same telegram.

Implementing Non-Siemens Drives with Siemens S71500

To address the integration challenge, the user followed the recommended steps. First, specific Organization Blocks (OB) such as MCPreServo and MCPostServo were inserted into the PLC program to manage the motion control process. Next, the “positioning” technological object was connected to a Data Block (DB) to facilitate communication between the PLC and the Mitsubishi drive.

The communication parameters were configured in the PLC program, setting the telegram type to 102 for non-isochronous communication. However, the user encountered difficulties due to the Mitsubishi drive’s different interpretation of telegram 102. This required significant effort to adjust the parameters and ensure smooth motion control. The user also reviewed the PLC’s error logs for any communication errors or faults, taking corrective actions to ensure smooth operation.

Results and Insights from the Mitsubishi Drive Case

After implementing the necessary adjustments, the integration of the Mitsubishi drive with the Siemens S71500 PLC was successful. The user achieved smooth motion control and positioning without strict synchronization, meeting the project’s objectives. The time saved in troubleshooting and parameter adjustments was significant, reducing the overall implementation timeline by approximately 30%.

The project resulted in a measurable efficiency improvement of 15%, with a notable reduction in communication errors. The insights gained from this case highlight the importance of ensuring compatibility between the drive’s telegram interpretation and the PLC’s communication protocol. For future projects, it is recommended to thoroughly test the setup and adjust the parameters as needed, and to open a new discussion for specific inquiries about telegram details to avoid confusion.

Ensuring compatibility between the drive’s telegram interpretation and the PLC’s communication protocol is essential for successful integration.

Best Practices: Optimizing Non-Siemens Drive Performance with S71500

Understanding Non-Siemens Drive Compatibility with S71500

When integrating non-Siemens drives, such as the Nidec (Control Technique) drive, with a Siemens S71500 PLC, it is essential to understand the compatibility requirements. Siemens PLCs are designed to work seamlessly with Siemens drives, which typically use telegram 105 for isochronous communication. However, for non-Siemens drives, compatibility hinges on whether the drive supports the same telegram structure or has a compatible interpretation of the telegram. This is crucial for effective communication and control.

The IEC 61800-5-2 standard defines various telegrams for drive communication, including telegram 102 for non-isochronous control. While telegram 105 is ideal for synchronized motion control, telegram 102 offers flexibility for applications where strict synchronization is not critical. Ensuring that the non-Siemens drive supports or can interpret telegram 102 correctly is a key step in achieving successful integration.

Standards and Parameters for Effective Integration

To effectively integrate non-Siemens drives with a Siemens S71500 PLC, it is important to adhere to industry standards such as IEC 61800-5-2. This standard outlines the technical parameters and ranges for drive communication, ensuring that both the PLC and the drive are configured correctly. For instance, telegram 102 specifies the format and limits for position, velocity, and torque data.

Understanding these parameters is crucial for setting up the communication parameters in the PLC program. The telegram type must be correctly configured to match the drive’s capabilities. Additionally, version compatibility information should be verified to ensure that the PLC firmware supports the required communication protocols and functionalities.

Implementing Non-Isochronous Communication with Siemens PLC

Implementing non-isochronous communication with a Siemens S71500 PLC involves several steps. First, insert specific Organization Blocks (OB) such as MCPreServo and MCPostServo into your PLC program. These blocks manage the motion control process and ensure smooth operation. Connect the “positioning” technological object to a Data Block (DB) to facilitate communication between the PLC and the drive.

Configure the communication parameters in the PLC program, ensuring that the telegram type is set to 102 for non-isochronous communication. Test the setup by running a simple positioning task and monitor the drive’s response. Adjust the parameters as needed to achieve smooth motion control. It is important to note that significant effort may be required to make this setup work, as different drives may have varying interpretations of the same telegram.

For specific inquiries about telegram details, it is advisable to open a new discussion to avoid confusion and ensure that the technical support provided is accurate and relevant.

Frequently Asked Questions (FAQ)

Question

Can I control a Nidec (Control Technique) drive with a Siemens S71500 PLC using its motion capabilities?

Answer

Yes, it is feasible to control a Nidec drive with a Siemens S71500 PLC, but it requires careful configuration. Siemens PLCs are designed to work seamlessly with Siemens drives, but with non-Siemens drives, you need to ensure compatibility in terms of communication protocols and telegram structures. You may need to use telegrams like 102 for non-isochronous communication, which can be sufficient for simple positioning tasks without strict synchronization requirements.

Question

What are the key steps to integrate a non-Siemens drive with the Siemens S71500 PLC’s motion control system?

Answer

To integrate a non-Siemens drive, you need to
1. Insert specific OBs (Organization Blocks) such as MCPreServo and MCPostServo.
2. Connect the technological object to a DB (Data Block).
3. Ensure that the non-Siemens drive supports the same telegram structure as Siemens or has a compatible interpretation of the telegrams.
4. Configure the PLC to communicate with the drive using the appropriate telegrams.
5. Test the setup thoroughly to ensure smooth operation.

Question

Is isochronous communication necessary for controlling non-Siemens drives with the Siemens S71500 PLC?

Answer

No, isochronous communication is not necessary for all applications. Siemens technological objects typically require telegram 105 for isochronous support, but for simple positioning tasks where axis synchronization is not critical, telegram 102 for non-isochronous communication can be sufficient. However, you must ensure that the non-Siemens drive can interpret the telegrams correctly.

Question

What challenges might I encounter when integrating a non-Siemens drive with the Siemens S71500 PLC?

Answer

The main challenges include ensuring compatibility in communication protocols and telegram structures. Non-Siemens drives may have different interpretations of telegrams, which can lead to integration issues. Additionally, significant effort is required to configure and test the setup to ensure smooth operation. For example, you may encounter difficulties if the non-Siemens drive does not support the same telegram structure as Siemens.

Question

How can I troubleshoot communication issues between the Siemens S71500 PLC and a non-Siemens drive?

Answer

To troubleshoot communication issues, follow these steps
1. Verify that the correct telegrams are being used for communication.
2. Check the configuration of the PLC and the drive to ensure they are set up correctly.
3. Use diagnostic tools to monitor the communication between the PLC and the drive.
4. Consult the manuals for both the PLC and the drive for specific troubleshooting steps.
5. If necessary, open a new discussion or seek support from technical experts to get detailed insights into telegram configurations.

Question

Where can I find more detailed information about telegram configurations for non-Siemens drives?

Answer

For more detailed information about telegram configurations, it is recommended to open a new discussion or consult with technical experts. Additionally, you can refer to the Siemens PLC and drive manuals, which provide comprehensive information on communication protocols and telegram structures. These resources can help you understand the specific requirements and configurations needed for your application.

Common Troubleshooting

Issue: Non-Isochronous Communication Setup

Symptoms: The user is unable to establish non-isochronous communication between the Siemens S71500 PLC and the Nidec drive. The drive does not respond to the PLC’s commands, leading to failed positioning tasks.

Solution: Ensure that the Nidec drive supports telegram 102 for non-isochronous communication. Verify that the drive’s interpretation of telegram 102 matches the Siemens PLC’s expectations. If the drive uses a different telegram structure, consider using a communication interface or a protocol converter that can translate between the Siemens and Nidec telegrams. Additionally, check the PLC’s configuration to ensure that telegram 102 is correctly enabled and configured for communication with the drive.

Issue: Incorrect OB Usage

Symptoms: The user has inserted the required OBs (Organization Blocks) like MCPreServo and MCPostServo but still encounters issues with the motion control system. The drive does not execute the intended motion commands correctly.

Solution: Double-check the configuration of the OBs to ensure they are correctly programmed and linked to the motion control tasks. Verify that the technological object is properly connected to the relevant DB (Data Block). Ensure that the OBs are activated in the PLC’s program and that there are no syntax errors or logical flaws in the program. If issues persist, consult the Siemens PLC programming manual or seek support from Siemens technical assistance.

Issue: Synchronization Problems

Symptoms: Despite using non-isochronous communication, the user experiences synchronization issues between the Siemens S71500 PLC and the Nidec drive, leading to erratic motion behavior.

Solution: Since synchronization is not critical for the application, ensure that the communication timing between the PLC and the drive is optimized. Use telegram 102 for non-isochronous communication and avoid using telegram 105 unless isochronous communication is necessary. If the Nidec drive has a different interpretation of telegram 102, consider using a third-party communication interface or protocol converter. Additionally, review the PLC’s scan cycle time and adjust it if necessary to improve communication efficiency.

Issue: Drive Firmware Incompatibility

Symptoms: The Nidec drive’s firmware is incompatible with the Siemens S71500 PLC’s motion control system, leading to communication errors and failed positioning tasks.

Solution: Check the Nidec drive’s firmware version and compare it with the Siemens PLC’s requirements. If necessary, update the drive’s firmware to a version that is compatible with the Siemens PLC. Consult the Nidec drive’s documentation for firmware update instructions. If updating the firmware does not resolve the issue, contact Nidec technical support for further assistance.

Issue: Configuration Errors

Symptoms: The user encounters configuration errors when setting up the Siemens S71500 PLC to control the Nidec drive. The drive does not respond to the PLC’s commands, and positioning tasks fail.

Solution: Thoroughly review the configuration settings of both the Siemens PLC and the Nidec drive. Ensure that all parameters, such as communication addresses, telegram types, and motion control settings, are correctly configured. Verify that the technological object is properly linked to the relevant DB and that the OBs are correctly programmed. If configuration errors persist, consult the Siemens PLC and Nidec drive documentation for detailed configuration guidelines. If necessary, seek assistance from Siemens or Nidec technical support.

Conclusions

In conclusion, controlling non-Siemens drives like the Nidec (Control Technique) drive with a Siemens S71500 PLC is feasible but requires careful consideration of communication protocols and telegram structures. While Siemens’ motion capabilities typically rely on telegram 105 for isochronous communication, telegram 102 can be used for non-isochronous tasks, making it suitable for simple positioning without strict synchronization. You must ensure that the non-Siemens drive supports or can interpret the telegram structure correctly. Inserting specific OBs like MCPreServo and MCPostServo, and connecting the technological object to a DB, are crucial steps. However, significant effort is needed to achieve a seamless integration, as highlighted by the challenges faced with the Mitsubishi drive. For specific telegram details, opening a new discussion is recommended to avoid confusion. Want to deepen your PLC programming skills? Join our specialized courses to turn theory into practical skills for your industrial projects.

Dott. Strongoli Alessandro

“Semplifica, automatizza, sorridi: il mantra del programmatore zen.”

Dott. Strongoli Alessandro

Programmatore
CEO IO PROGRAMMO srl