Integrating 1783-MS10T Switch into I/O Tree: Does It Work with L16-ER Controller?

Subject: Configuring Stratix 8000/8300/5700 in RSLogix 5000 I/O Setup Access Level: TechConnect When it comes to adding the Stratix 8000, 8300, or 5700 series switches to your RSLogix 5000 I/O configuration, consider this as an official confirmation for your inquiry (Reference Number: 493693). The integrated web interface known as "Device Manager" is significantly more effective for switch configuration than Logix 5000 or Logix Designer, despite its frustratingly slow page updates and transitions. Incorporating the switch into your setup is advantageous, especially if you intend to utilize its predefined faceplate for a Human-Machine Interface (HMI) application. Today, I plan to integrate a faceplate into a project that has been under commissioning all week. With our Stratix 8000 featuring a full expansion capability of up to 26 ports, having a quick visual diagnostics interface on the HMI is incredibly valuable for monitoring that many ports. If I were in your position, I would always recommend including spare Ethernet nodes to accommodate future expansion. However, I fully understand the limitations posed by project size and budget. Given that you mentioned the possibility of upgrading to a higher-level controller, this option would certainly influence my decision-making process for an application of this nature. Best Regards, George

• 21-03-2025
• Geospark

Hello George, thank you for reaching out. Unfortunately, I do not have access to techConnect. When you refer to the faceplate, I assume you mean for FTV SE applications? My Human-Machine Interface (HMI) is powered by Ignition SCADA, complete with a web browser module. As a result, I can directly display the Stratix Device Manager, which is secured with user level access and password protection.

• 21-03-2025
• the_msp

The technical note is concise yet effective—something I often find challenging to achieve. A Stratix switch appliance functions seamlessly within a Logix-based integrated architecture without needing to be included in any existing controller's I/O Configuration. This option provides an auxiliary and practical approach for users to access both diagnostic and configuration data easily. Right out of the box, these switches operate immediately in an unmanaged mode, requiring no additions to I/O Configuration or even basic settings like Express Setup. Interestingly, they don't require an IP address, as they run on Cisco IOS firmware, which is inherently designed for data propagation and routing capabilities. It is through configuration that these switches become "managed," improving their efficiency in handling end device data by customizing features such as port roles. The faceplate is compatible with FactoryTalk View ME or SE. To access the necessary data, you would employ an Add-On Instruction (AOI) that manages standard messaging to the switch. For third-party Human-Machine Interfaces (HMIs), you can also utilize the AOI to populate tag data for display; however, the "Requested Packet Interval" (RPI) of the AOI is relatively slow, as it is tailored to work with the faceplate that updates less frequently. You have the option to modify the AOI or, by integrating the switch into the I/O Configuration, you can tap into the higher RPI module-defined (I/O) tag data for the switch. This approach may be more effective if you prefer to avoid granting access to the Device Manager switch configuration through the Ignition web module. Best regards, George

• 21-03-2025
• Geospark

Incorporating the switch is beneficial for utilizing its predefined faceplate in Human-Machine Interface (HMI) applications. However, it's important to note that the V10 Faceplate Add-On Instruction (AOI) does not necessitate the switch being included in the I/O configuration. The “Requested Packet Interval” (RPI) for the AOI is set to a slower rate since it syncs with the faceplate, which refreshes less frequently. Modifying the AOI's update rate can lead to potential overloads of the CIP Object associated with the switch. For better performance and display purposes, you can access the higher RPI module-defined I/O tag data externally. It's essential to recognize that the information available within the module-defined tags is quite limited, whereas the AOI can extract a significantly more comprehensive dataset. Additionally, some of the data retrieved by the AOI is dependent on the current display to minimize the messaging load on the switch. If you plan to utilize the AOI across various displays, be sure to review the specific conditions within the AOI logic. Notably, these switches can start functioning immediately without any additional I/O configuration or even a basic setup, such as the Express Setup, although they will operate in an unmanaged mode. However, it is highly advisable to complete the Express Setup as it is a crucial step for establishing at least a minimum configuration.

• 21-03-2025
• Contr_Conn