In today’s industrial automation landscape, efficient network communication with PLCs is crucial, with data collection errors costing industries millions annually. You are facing challenges with data collection from multiple PLCs connected to your PC using Ns-Runtime. The complexity of configuring network settings and mapping PLCs can be daunting, especially when choosing between Toolbus and Sysmac Way. To address these issues, you need a robust solution that ensures seamless data access. By employing a PLC master, configuring correct network settings, and utilizing Ethernet or RS422 communication, you can streamline data collection. Mapping PLCs in Ns-Runtime and using Function Blocks or SEND/RECV functions will facilitate efficient data retrieval. This approach not only resolves your current difficulties but also enhances your system’s overall performance and reliability.
In particolar modo vedremo:
Quick Solution: Solve the Problem Quickly
Utilize a PLC Master for Efficient Data Reading
To efficiently read data from multiple PLCs, you should employ a PLC master, such as the CP1L-EM Ethernet model. This PLC master will act as an intermediary, facilitating data collection from the connected PLCs and then communicating with Ns-Runtime. The PLC master should be configured to read data from the PLCs using Ethernet or RS422, depending on your network setup.
Ensure that the PLC master is properly connected to the network and that its IP address is correctly configured. This will allow it to communicate with the other PLCs and aggregate the data for Ns-Runtime. The PLC master should be set up to use Function Blocks (FB) or SEND/RECV functions to collect data from the PLCs.
Configure Network Settings for Seamless Communication
Correctly configuring the network settings is crucial for seamless communication between the PLCs and the PC. Start by setting the Node Number in the Host-link port settings of each PLC. This ensures that each PLC is correctly identified on the network. If using Ethernet, ensure that the PLCs are visible in CX-Programmer and that their IP addresses are correctly configured.
If using RS422 communication, ensure that the converter (e.g., Omron SCU02 R232-422-485) is properly connected and configured. Verify that the baud rate, parity, and data bits settings match across all devices. This will prevent communication errors and ensure that data is transmitted accurately.
Verify PLC Mapping and Data Collection in Ns-Runtime
In Ns-Runtime, configure the serial ports to match the settings of your PLCs and converter. Ensure that the PLCs are correctly mapped in Ns-Runtime. If using Ethernet, verify that the PLCs are visible and accessible. Use the mapping feature in Ns-Runtime to assign specific PLCs to the appropriate ports and IP addresses.
Once the mapping is complete, verify the data collection by reading data from specific PLCs, such as DM 100 of PLC 3. Check that the data is being collected correctly and that there are no errors or discrepancies. If issues persist, review the network settings and PLC configurations to ensure everything is correctly set up.
Setting Up PLC Master for Ethernet Data Collection
Configuring the PLC Master for Ethernet Communication
To configure the PLC master for Ethernet communication, you must first ensure that the PLC master is compatible with your network setup. The CP1L-EM Ethernet model is a suitable choice, as it supports Ethernet communication and can act as an intermediary between the PLCs and Ns-Runtime. Begin by connecting the PLC master to your network and configuring its IP address. This will allow it to communicate with the other PLCs and aggregate the data for Ns-Runtime.
Next, configure the PLC master to use Function Blocks (FB) or SEND/RECV functions to collect data from the PLCs. This can be done through the PLC master’s configuration software, where you can set up the data collection parameters and specify the PLCs to be read. Ensure that the PLC master is set to communicate with the PLCs using Ethernet, as this will provide a more stable and efficient data transfer compared to RS422.
Establishing Correct Network Settings for PLCs
Correctly establishing network settings for the PLCs is crucial for seamless communication. Start by setting the Node Number in the Host-link port settings of each PLC. This ensures that each PLC is correctly identified on the network. If using Ethernet, ensure that the PLCs are visible in CX-Programmer and that their IP addresses are correctly configured. This will allow the PLC master to communicate with the PLCs and collect data efficiently.
If using RS422 communication, ensure that the converter (e.g., Omron SCU02 R232-422-485) is properly connected and configured. Verify that the baud rate, parity, and data bits settings match across all devices. This will prevent communication errors and ensure that data is transmitted accurately. Additionally, ensure that the PLCs are correctly mapped in Ns-Runtime, and that the serial ports are configured to match the settings of your PLCs and converter.
Implementing Data Collection with Ns-Runtime
Once the PLC master is configured and the network settings are established, you can implement data collection with Ns-Runtime. In Ns-Runtime, configure the serial ports to match the settings of your PLCs and converter. Ensure that the PLCs are correctly mapped in Ns-Runtime. If using Ethernet, verify that the PLCs are visible and accessible. Use the mapping feature in Ns-Runtime to assign specific PLCs to the appropriate ports and IP addresses.
After mapping the PLCs, verify the data collection by reading data from specific PLCs, such as DM 100 of PLC 3. Check that the data is being collected correctly and that there are no errors or discrepancies. If issues persist, review the network settings and PLC configurations to ensure everything is correctly set up. By following these steps, you should be able to establish a functional communication network between the PLCs and the PC using Ns-Runtime.
Configuring Network Settings for PLC Communication
Establishing Network Communication with PLCs via Ns-Runtime
To establish a robust network communication with your PLCs using Ns-Runtime, it is essential to first understand the communication protocols available. Ns-Runtime supports both Toolbus and Sysmac Way for PLC communication. Toolbus is a high-speed communication protocol suitable for large-scale networks, while Sysmac Way is a more traditional method that is easier to implement in smaller systems. Depending on your network size and complexity, you may choose one over the other. For instance, if you have a large network with many PLCs, Toolbus might be more appropriate due to its speed and efficiency.
Ensure that your Ns-Runtime version is compatible with the communication protocol you choose. For example, Ns-Runtime version 5.0 and above supports Toolbus, while earlier versions may only support Sysmac Way. Always refer to the latest version compatibility information provided by the manufacturer to avoid potential issues.
Setting Up PLC Network Parameters for Effective Data Collection
Configuring the network settings correctly is crucial for effective data collection. Start by setting the correct Node Number in the Host-link port settings of each PLC. This unique identifier ensures that each PLC is correctly recognized on the network. If using Ethernet, verify that the PLCs are visible in CX-Programmer and that their IP addresses are correctly configured. This step is vital for seamless communication between the PLCs and the PC.
If you are using RS422 communication, ensure that the converter (e.g., Omron SCU02 R232-422-485) is properly connected and configured. Verify that the baud rate, parity, and data bits settings match across all devices. For example, a common configuration is a baud rate of 9600, parity set to ‘None’, and 8 data bits. These settings are crucial for preventing communication errors and ensuring accurate data transmission.
Implementing Standards for Seamless PLC-PC Communication
Implementing industry standards such as IEC 61131-3 and ISO 9506-1 can significantly enhance the reliability and efficiency of your PLC-PC communication. These standards provide guidelines for programming, communication protocols, and data exchange, ensuring that your system operates within accepted parameters. For instance, IEC 61131-3 defines the programming languages and communication protocols for industrial automation, while ISO 9506-1 specifies the communication profile for manufacturing message specification (MMS).
When configuring your network, adhere to these standards to ensure compatibility and interoperability. For example, using the correct communication profile as defined by ISO 9506-1 can prevent data loss and ensure that all devices on the network can communicate effectively. Additionally, following the programming guidelines in IEC 61131-3 can help you create robust and reliable PLC programs.
Comparing Ethernet and RS422 Communication Methods
Ethernet vs RS422: Choosing the Right Communication Standard
When selecting a communication standard for your PLCs, you must consider the specific requirements of your industrial automation setup. Ethernet and RS422 are two commonly used protocols, each with distinct advantages and limitations. Ethernet is a high-speed, reliable, and scalable solution suitable for large-scale networks, offering data transfer rates up to 100 Mbps. It is ideal for applications requiring real-time data exchange and high bandwidth, such as video surveillance or high-speed data logging.
On the other hand, RS422 is a serial communication standard that is more cost-effective and easier to implement in smaller systems. It provides reliable data transmission over longer distances (up to 4000 feet) and is resistant to electromagnetic interference. RS422 is suitable for applications where high-speed data transfer is not critical, such as simple sensor networks or legacy systems. The choice between Ethernet and RS422 should be based on factors such as network size, data transfer requirements, and budget constraints.
Configuring Network Parameters for Effective PLC Communication
Configuring the network parameters correctly is crucial for effective PLC communication. Start by setting the correct Node Number in the Host-link port settings of each PLC. This unique identifier ensures that each PLC is correctly recognized on the network. If using Ethernet, verify that the PLCs are visible in CX-Programmer and that their IP addresses are correctly configured. This step is vital for seamless communication between the PLCs and the PC.
If you are using RS422 communication, ensure that the converter (e.g., Omron SCU02 R232-422-485) is properly connected and configured. Verify that the baud rate, parity, and data bits settings match across all devices. For example, a common configuration is a baud rate of 9600, parity set to ‘None’, and 8 data bits. These settings are crucial for preventing communication errors and ensuring accurate data transmission.
Implementing Data Collection with Ns-Runtime and PLC Networks
To implement data collection with Ns-Runtime and your PLC networks, you should use a PLC master (e.g., CP1L-EM Ethernet) to read data from other PLCs. This PLC master will then communicate with Ns-Runtime. Ensure that the PLC master is configured to use Function Blocks (FB) or SEND/RECV functions to collect data from the PLCs. The PLC master will aggregate the data and make it available for Ns-Runtime.
In Ns-Runtime, configure the serial ports to match the settings of your PLCs and converter. Ensure that the PLCs are correctly mapped in Ns-Runtime. If using Ethernet, verify that the PLCs are visible and accessible. Use the mapping feature in Ns-Runtime to assign specific PLCs to the appropriate ports and IP addresses. After mapping the PLCs, verify the data collection by reading data from specific PLCs, such as DM 100 of PLC 3. Check that the data is being collected correctly and that there are no errors or discrepancies.
Ensure compatibility and interoperability by adhering to industry standards such as IEC 61131-3 and ISO 9506-1. These standards provide guidelines for programming, communication protocols, and data exchange, ensuring that your system operates within accepted parameters.
Implementing Data Collection with Function Blocks
Establishing a PLC Master for Data Collection
To effectively collect data from multiple PLCs, you must establish a PLC master, such as the CP1L-EM Ethernet model, which will serve as an intermediary between the PLCs and Ns-Runtime. The PLC master should be configured to communicate using Ethernet or RS422, depending on your network setup. This master will read data from the connected PLCs and aggregate it for Ns-Runtime. It is essential to ensure that the PLC master is properly connected to the network and that its IP address is correctly configured to facilitate seamless communication.
In configuring the PLC master, you can use Function Blocks (FB) or SEND/RECV functions to collect data. The CP1L-EM Ethernet model supports these methods, enabling efficient data aggregation. For Ns-Runtime version 5.0 and above, Toolbus is supported for high-speed communication, whereas earlier versions may only support Sysmac Way. Always ensure compatibility with the chosen communication protocol.
Configuring Network Settings for Seamless Communication
Properly configuring the network settings is crucial for seamless communication between the PLCs and the PC. Begin by setting the Node Number in the Host-link port settings of each PLC. This ensures that each PLC is correctly identified on the network. If using Ethernet, verify that the PLCs are visible in CX-Programmer and that their IP addresses are correctly configured. For RS422 communication, ensure that the converter (e.g., Omron SCU02 R232-422-485) is properly connected and configured with matching baud rate, parity, and data bits settings across all devices.
Adhering to industry standards such as IEC 61131-3 and ISO 9506-1 enhances the reliability and efficiency of your PLC-PC communication. These standards provide guidelines for programming, communication protocols, and data exchange, ensuring that your system operates within accepted parameters. For instance, IEC 61131-3 defines the programming languages and communication protocols for industrial automation, while ISO 9506-1 specifies the communication profile for manufacturing message specification (MMS).
Implementing Data Collection with Function Blocks
To implement data collection using Function Blocks (FB), you should configure the PLC master to use these blocks or SEND/RECV functions to gather data from the PLCs. The PLC master will then aggregate this data and make it available for Ns-Runtime. In Ns-Runtime, configure the serial ports to match the settings of your PLCs and converter. Ensure that the PLCs are correctly mapped in Ns-Runtime. If using Ethernet, verify that the PLCs are visible and accessible. Use the mapping feature in Ns-Runtime to assign specific PLCs to the appropriate ports and IP addresses.
After mapping the PLCs, verify the data collection by reading data from specific PLCs, such as DM 100 of PLC 3. Check that the data is being collected correctly and that there are no errors or discrepancies. If issues persist, review the network settings and PLC configurations to ensure everything is correctly set up. By following these steps, you should be able to establish a functional communication network between the PLCs and the PC using Ns-Runtime.
Mapping PLCs in Ns-Runtime for Effective Data Access
Establishing a PLC Master for Data Collection
To facilitate data collection from multiple PLCs connected to a PC using Ns-Runtime, it is crucial to establish a PLC master, such as the CP1L-EM Ethernet model. This PLC master acts as an intermediary, aggregating data from the connected PLCs and communicating with Ns-Runtime. Configure the PLC master to use Ethernet or RS422 communication, depending on your network setup. Ensure that the PLC master is properly connected to the network and that its IP address is correctly configured to enable seamless communication.
Using Function Blocks (FB) or SEND/RECV functions for data collection is recommended. The CP1L-EM Ethernet model supports these methods, ensuring efficient data aggregation. For Ns-Runtime version 5.0 and above, Toolbus is supported for high-speed communication, whereas earlier versions may only support Sysmac Way. Always ensure compatibility with the chosen communication protocol to avoid potential issues.
Configuring Network Settings for Seamless Communication
Properly configuring the network settings is essential for seamless communication between the PLCs and the PC. Begin by setting the Node Number in the Host-link port settings of each PLC. This unique identifier ensures that each PLC is correctly recognized on the network. If using Ethernet, verify that the PLCs are visible in CX-Programmer and that their IP addresses are correctly configured. For RS422 communication, ensure that the converter (e.g., Omron SCU02 R232-422-485) is properly connected and configured with matching baud rate, parity, and data bits settings across all devices.
Adhering to industry standards such as IEC 61131-3 and ISO 9506-1 enhances the reliability and efficiency of your PLC-PC communication. These standards provide guidelines for programming, communication protocols, and data exchange, ensuring that your system operates within accepted parameters. For instance, IEC 61131-3 defines the programming languages and communication protocols for industrial automation, while ISO 9506-1 specifies the communication profile for manufacturing message specification (MMS).
Implementing Effective Data Mapping in Ns-Runtime
To implement effective data mapping in Ns-Runtime, configure the serial ports to match the settings of your PLCs and converter. Ensure that the PLCs are correctly mapped in Ns-Runtime. If using Ethernet, verify that the PLCs are visible and accessible. Use the mapping feature in Ns-Runtime to assign specific PLCs to the appropriate ports and IP addresses. This ensures that data can be accurately read from specific PLCs, such as DM 100 of PLC 3.
After mapping the PLCs, verify the data collection by reading data from specific PLCs. Check that the data is being collected correctly and that there are no errors or discrepancies. If issues persist, review the network settings and PLC configurations to ensure everything is correctly set up. By following these steps, you should be able to establish a functional communication network between the PLCs and the PC using Ns-Runtime.
Ensure compatibility and interoperability by adhering to industry standards such as IEC 61131-3 and ISO 9506-1. These standards provide guidelines for programming, communication protocols, and data exchange, ensuring that your system operates within accepted parameters.
Frequently Asked Questions (FAQ)
Question
How do I select the appropriate PLC master for my network setup?
To select the appropriate PLC master, consider the type of communication you plan to use. For Ethernet communication, a CP1L-EM Ethernet PLC master is suitable. If you are using RS422 communication, ensure that your PLC master supports this protocol. The PLC master should be capable of aggregating data from the connected PLCs and communicating with Ns-Runtime.
Question
What steps should I follow to configure the Node Number in the Host-link port settings of each PLC?
To configure the Node Number, access the Host-link port settings of each PLC. Ensure that each PLC has a unique Node Number within the network. This is crucial for proper communication and data collection. Typically, you can set the Node Number in the PLC’s configuration software, such as CX-Programmer. Verify that the Node Numbers do not conflict with each other.
Question
Can I use both Ethernet and RS422 communication in the same network setup?
Yes, it is possible to use both Ethernet and RS422 communication in the same network setup. However, you will need to ensure that the appropriate converters and communication protocols are used. For instance, use Ethernet for direct communication between PLCs and the PLC master, and RS422 for connecting PLCs that do not support Ethernet. Proper configuration of both communication types is essential for seamless data collection.
Question
How do I collect data from specific PLCs using Ns-Runtime?
To collect data from specific PLCs using Ns-Runtime, you can use Function Blocks (FB) or SEND/RECV functions. Configure the PLC master to aggregate data from the connected PLCs. In Ns-Runtime, map the PLCs and set up the data collection process. Ensure that the PLCs are correctly mapped and that the data paths are correctly defined. This will allow you to read data from specific PLCs, such as DM 100 of PLC 3.
Question
What should I do if the PLCs are not visible in Ns-Runtime when using Ethernet communication?
If the PLCs are not visible in Ns-Runtime, first ensure that the PLCs are correctly configured in CX-Programmer and that the Ethernet network settings are properly set up. Verify that the PLCs are connected to the same network segment as the PC running Ns-Runtime. Check the network cables and switches for any connectivity issues. If the problem persists, restart the PLCs and the PC, and ensure that the PLCs are powered on and in RUN mode.
Question
How can I troubleshoot issues with RS422 communication between the PLCs and the converter?
To troubleshoot issues with RS422 communication, first check the physical connections between the PLCs and the converter. Ensure that the cables are properly connected and that there are no loose connections. Verify that the converter is configured correctly for RS422 communication. Check the baud rate, parity, and data bits settings to ensure they match the PLCs’ settings. If the issue persists, test the converter with another device to rule out hardware failure.
Common Troubleshooting
Issue: Difficulty Establishing Network Communication
Symptoms:
The user is unable to establish a connection between the PC and the PLCs. The PLCs do not appear in Ns-Runtime, and data collection is not possible.
Solution:
Ensure that the network settings are correctly configured. Verify that the Node Number is set correctly in the Host-link port settings of each PLC. Check that the converter is properly connected and functioning. Ensure that the PLCs are powered on and operational. If using Ethernet, confirm that the PLCs are visible in CX-Programmer.
Issue: Incorrect Data Collection
Symptoms:
The user is able to establish a connection, but the data collected from the PLCs is incorrect or incomplete.
Solution:
Verify that the Function Blocks (FB) or SEND/RECV functions are correctly configured in the PLCs. Ensure that the PLC master is properly aggregating the data. Check the mapping of PLCs in Ns-Runtime to ensure that the correct data is being collected from the right PLCs.
Issue: PLCs Not Visible in Ns-Runtime
Symptoms:
The PLCs are connected and operational, but they do not appear in the Ns-Runtime interface.
Solution:
If using Ethernet communication, ensure that the PLCs are correctly configured in CX-Programmer and that the network settings are properly set up. If using RS422, verify that the serial ports are correctly configured in Ns-Runtime and that the PLCs are properly mapped. Check the converter settings and ensure that all cables are securely connected.
Issue: Communication Protocol Confusion
Symptoms:
The user is unsure whether to use Toolbus or Sysmac Way for communication and is experiencing difficulties in configuring the network.
Solution:
Use the appropriate communication protocol based on the setup. If using Ethernet, Sysmac Way is typically the preferred protocol. If using RS422, ensure that the correct protocol is selected in the PLC and Ns-Runtime settings. Consult the user manual or technical documentation for the specific communication protocol requirements.
Issue: Mapping Issues
Symptoms:
The user is having trouble mapping the PLCs in Ns-Runtime, leading to difficulties in data collection.
Solution:
In Ns-Runtime, carefully configure the serial ports and map the PLCs according to their Node Numbers. Ensure that the PLCs are correctly identified and mapped in the software. Double-check the mapping settings to ensure that data is being collected from the intended PLCs. If necessary, restart Ns-Runtime and reconfigure the settings.
Conclusion
In conclusion, establishing effective communication between PLCs and a PC using Ns-Runtime involves several critical steps. You should use a PLC master to read data from other PLCs, configure the network settings correctly, and choose the appropriate communication method—Ethernet or RS422. By mapping the PLCs in Ns-Runtime and utilizing Function Blocks or SEND/RECV functions, you can successfully collect and access data from your PLCs. Following these steps will help you achieve a seamless and efficient data access system.
Want to deepen your PLC programming skills? Join our specialized courses to turn theory into practical skills for your industrial projects.
“Semplifica, automatizza, sorridi: il mantra del programmatore zen.”
Dott. Strongoli Alessandro
Programmatore
CEO IO PROGRAMMO srl
