Innovation Center

DMX-4338_9thScenario

Objective

Organize large volume of high-speed data with OT-based Information models. In high-speed production scenarios, it’s common for manufacturers the need to quickly access the entire set of operational related data (production, quality, maintenance, etc.) from various stages in the process.

Approach

Organize large volume of high-speed data with OT-based Information models. In high-speed production scenarios, it’s common for manufacturers the need to quickly access the entire set of operational related data (production, quality, maintenance, etc.) from various stages in the process.

Overview

FactoryTalk Edge Gateway software unifies data from industrial sources and control or automation systems. It integrates with a variety of cloud, IIoT, and big data applications including ThingWorx, Microsoft Azure IoT Hub, Microsoft SQL and more. This maximizes operational insights, simplifying and automating data ingestion in a single integration solution for IT applications.

With FactoryTalk Edge Gateway software user can create information models at the Operational Technology (OT) layer and efficiently map to upstream IT applications to improve performance KPIs like OEE, predictive quality and process efficiency.

With access to OT contextualized data, IT applications can help users to extract equipment insights across the enterprise. Quickly, easily, and proactively identify process and production inefficiencies and product defects. With less required data preparation time, customer can focus on using their data to detect and resolve equipment issues and improve production output.

Downloads

Please note: You will need to agree to the Terms & Conditions for each download.

Need Help?

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt.

• Simplifies and automates industrial data collection, contextualization, and organization across equipment, devices, and automation assets
• Enables IT/OT convergence
• Unlocks key industrial performance insights from OT data
• Enables high IT data integrity
• Integrates with a variety of cloud, IIoT and big data applications
• High speed, synchronous data collection
• Reduces the need for IT technical expertise

Installation Guide

Supports OT / IT collaboration by empowering control engineers -Without traditional IT skills- to identify the most appropriate data sets (Information models) and send information directly to the IT layer.

Step 1: Connect

Supports OT / IT collaboration by empowering control engineers -Without traditional IT skills- to identify the most appropriate data sets (Information models) and send information directly to the IT layer.

Step 2: Contextualize

Contextualize the data into Information Models: Allows OT engineer to organize data in context as it pertains to the OT assets, simplifies maintenance and updates.

Step 3: Map

Map the data to enterprise and cloud applications: Supports Azure IoT Hub and Azure IoT Edge, Creates SQL table needed to store data and creates objects in ThingWorx to replicate the information model.

Step 1: Connect

Step 1.1: Define Driver

Drivers enable communication between the gateway and data sources. Add drivers to configure data collection paths for data sources and FactoryTalk Smart Object instances. Go Online to add a driver. By default, an EtherNet/IP (CIP) driver is installed with FactoryTalk Edge Gateway.

Add a Driver:

1. Select Data Flow > Data Sources.
2. From Define Drivers, select Add to add a driver to the gateway.
3. From Select Driver, select the driver type to configure:
   • FactoryTalk Live Data (FTLD)
   • therNet/IP (CIP)
4. Select Next.
5. Enter the Driver Name and define the settings.
   • The name must contain only letters, numbers, and hyphens.
   • The settings differ for each driver type.
6. Select Save.

Step 1.2: Configure Data Sources

Configure data sources to populate a namespace and collect data from data tags and FactoryTalk Smart Object instances. Data tags are accessed from controllers, devices, and servers. FactoryTalk Smart Object instances require an offline Studio 5000 Logix Designer project file (.acd) to populate the namespace and an EtherNet/IP driver for data collection.

FactoryTalk Edge Gateway gathers the directory of data from the source and stores the data into a namespace. In the case of FactoryTalk Smart Object instances, the FactoryTalk Smart Object model is also discovered and replicated in Models. Use these data tags and models to configure the gateway. From Configure Data Sources, add, edit, delete, populate, clear, and filter data sources.

Use Case 1:

Smart Objects
(Add a data source from a Studio 5000 Logix Designer Project File [.acd]) + Logix Echo Controller

Add data sources from offline Studio 5000 Logix Designer controller project files to populate a namespace and collect data from data tags and FactoryTalk Smart Object instances. The supported file type is “.acd”. FactoryTalk Smart Object instances are only available from the Studio 5000 Logix Designer project file (.acd) data source type and require an EtherNet/IP (CIP) driver. The data from the “.acd” project file is later accessed from the device or server running the Studio 5000 Logix Designer project file.

FactoryTalk Edge Gateway is compatible with Logix firmware revisions 16.00 or later. FactoryTalk Smart Object instances are supported in Logix firmware revisions 28.00 or later. The Studio 5000 Logix Designer project file (.acd) data source is compatible with these drivers: FactoryTalk Live Data and EtherNet/IP (CIP).

Add a Driver:

1. Select Data Flow > Data Sources.
2. From Define Drivers, select Add to add a driver to the gateway.
3. From Select Driver, select the driver type to configure:
   • FactoryTalk Live Data (FTLD)
   • therNet/IP (CIP)
4. Select Next.
5. Enter the Driver Name and define the settings.
   • The name must contain only letters, numbers, and hyphens.
   • The settings differ for each driver type.
6. Select Save.

Use Case 2:

FactoryTalk Live Data Shortcut
Add a data source from a FactoryTalk Live Data Shortcut – CompactLogix controller and VSD

Add data sources from FactoryTalk Live Data to populate a namespace and collect data from data tags. The data source is also a shortcut to these source types: HMI TagDb, OPC DA server, OPC UA server, and FactoryTalk® Linx™ shortcut. The FactoryTalk Live Data Shortcut data source is compatible with the FactoryTalk Live Data driver.

Add a data source from a Studio 5000 Logix Designer project file (.acd)

1. Select Data Flow, Data Sources, and then from Configure Data Sources, add a data source.
   • To add the first data source, select Add Data Sources.
   • To add a subsequent data source, select Add.
2. Enter the name and then from Data Browse Path Type, select Logix Project File (ACD).
   • The name must contain only letters, numbers, and hyphens.
3. From Driver for browsing, select the FactoryTalk Live Data driver.
4. Select a network or local path and enter the browse path.
5. (optional) To automatically generate the namespace, select Auto-populate namespace.
6. Perform one of these:
   • Select Use browse path for data collection.
   • From Driver for Collection, select the FactoryTalk Live Data driver for the data collection path and enter the collection path.
7. Select Save to add the data source.

Step 2: Contextualize

Step 2.1: Define Driver

Drivers enable communication between the gateway and data sources. Add drivers to configure data collection paths for data sources and FactoryTalk Smart Object instances. Go Online to add a driver. By default, an EtherNet/IP (CIP) driver is installed with FactoryTalk Edge Gateway.

LRESULT CALLBACK WndProd(
    _In_ HWEND  hWnd,
    _In_ UINT   message,
    _In_ WPARAM wParam,
    _In_ LPARAM lParam
);

Chitra_DMX-4338_NinthScenario01

Objective

Organize large volume of high-speed data with OT-based Information models. In high-speed production scenarios, it’s common for manufacturers the need to quickly access the entire set of operational related data (production, quality, maintenance, etc.) from various stages in the process.

Approach

Organize large volume of high-speed data with OT-based Information models. In high-speed production scenarios, it’s common for manufacturers the need to quickly access the entire set of operational related data (production, quality, maintenance, etc.) from various stages in the process.

Overview

FactoryTalk Edge Gateway software unifies data from industrial sources and control or automation systems. It integrates with a variety of cloud, IIoT, and big data applications including ThingWorx, Microsoft Azure IoT Hub, Microsoft SQL and more. This maximizes operational insights, simplifying and automating data ingestion in a single integration solution for IT applications.

With FactoryTalk Edge Gateway software user can create information models at the Operational Technology (OT) layer and efficiently map to upstream IT applications to improve performance KPIs like OEE, predictive quality and process efficiency.

With access to OT contextualized data, IT applications can help users to extract equipment insights across the enterprise. Quickly, easily, and proactively identify process and production inefficiencies and product defects. With less required data preparation time, customer can focus on using their data to detect and resolve equipment issues and improve production output.

Downloads

Please note: You will need to agree to the Terms & Conditions for each download.

Need Help?

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt.

• Simplifies and automates industrial data collection, contextualization, and organization across equipment, devices, and automation assets
• Enables IT/OT convergence
• Unlocks key industrial performance insights from OT data
• Enables high IT data integrity
• Integrates with a variety of cloud, IIoT and big data applications
• High speed, synchronous data collection
• Reduces the need for IT technical expertise

Installation Guide

Supports OT / IT collaboration by empowering control engineers -Without traditional IT skills- to identify the most appropriate data sets (Information models) and send information directly to the IT layer.

Step 1: Connect

Supports OT / IT collaboration by empowering control engineers -Without traditional IT skills- to identify the most appropriate data sets (Information models) and send information directly to the IT layer.

Step 2: Contextualize

Contextualize the data into Information Models: Allows OT engineer to organize data in context as it pertains to the OT assets, simplifies maintenance and updates.

Step 3: Map

Map the data to enterprise and cloud applications: Supports Azure IoT Hub and Azure IoT Edge, Creates SQL table needed to store data and creates objects in ThingWorx to replicate the information model.

Step 1: Connect

Step 1.1: Define Driver

Drivers enable communication between the gateway and data sources. Add drivers to configure data collection paths for data sources and FactoryTalk Smart Object instances. Go Online to add a driver. By default, an EtherNet/IP (CIP) driver is installed with FactoryTalk Edge Gateway.

Add a Driver:

1. Select Data Flow > Data Sources.
2. From Define Drivers, select Add to add a driver to the gateway.
3. From Select Driver, select the driver type to configure:
   • FactoryTalk Live Data (FTLD)
   • therNet/IP (CIP)
4. Select Next.
5. Enter the Driver Name and define the settings.
   • The name must contain only letters, numbers, and hyphens.
   • The settings differ for each driver type.
6. Select Save.

Step 1.2: Configure Data Sources

Configure data sources to populate a namespace and collect data from data tags and FactoryTalk Smart Object instances. Data tags are accessed from controllers, devices, and servers. FactoryTalk Smart Object instances require an offline Studio 5000 Logix Designer project file (.acd) to populate the namespace and an EtherNet/IP driver for data collection.

FactoryTalk Edge Gateway gathers the directory of data from the source and stores the data into a namespace. In the case of FactoryTalk Smart Object instances, the FactoryTalk Smart Object model is also discovered and replicated in Models. Use these data tags and models to configure the gateway. From Configure Data Sources, add, edit, delete, populate, clear, and filter data sources.

Use Case 1:

Smart Objects
(Add a data source from a Studio 5000 Logix Designer Project File [.acd]) + Logix Echo Controller

Add data sources from offline Studio 5000 Logix Designer controller project files to populate a namespace and collect data from data tags and FactoryTalk Smart Object instances. The supported file type is “.acd”. FactoryTalk Smart Object instances are only available from the Studio 5000 Logix Designer project file (.acd) data source type and require an EtherNet/IP (CIP) driver. The data from the “.acd” project file is later accessed from the device or server running the Studio 5000 Logix Designer project file.

FactoryTalk Edge Gateway is compatible with Logix firmware revisions 16.00 or later. FactoryTalk Smart Object instances are supported in Logix firmware revisions 28.00 or later. The Studio 5000 Logix Designer project file (.acd) data source is compatible with these drivers: FactoryTalk Live Data and EtherNet/IP (CIP).

Add a Driver:

1. Select Data Flow > Data Sources.
2. From Define Drivers, select Add to add a driver to the gateway.
3. From Select Driver, select the driver type to configure:
   • FactoryTalk Live Data (FTLD)
   • therNet/IP (CIP)
4. Select Next.
5. Enter the Driver Name and define the settings.
   • The name must contain only letters, numbers, and hyphens.
   • The settings differ for each driver type.
6. Select Save.

Use Case 2:

FactoryTalk Live Data Shortcut
Add a data source from a FactoryTalk Live Data Shortcut – CompactLogix controller and VSD

Add data sources from FactoryTalk Live Data to populate a namespace and collect data from data tags. The data source is also a shortcut to these source types: HMI TagDb, OPC DA server, OPC UA server, and FactoryTalk® Linx™ shortcut. The FactoryTalk Live Data Shortcut data source is compatible with the FactoryTalk Live Data driver.

Add a data source from a Studio 5000 Logix Designer project file (.acd)

1. Select Data Flow, Data Sources, and then from Configure Data Sources, add a data source.
   • To add the first data source, select Add Data Sources.
   • To add a subsequent data source, select Add.
2. Enter the name and then from Data Browse Path Type, select Logix Project File (ACD).
   • The name must contain only letters, numbers, and hyphens.
3. From Driver for browsing, select the FactoryTalk Live Data driver.
4. Select a network or local path and enter the browse path.
5. (optional) To automatically generate the namespace, select Auto-populate namespace.
6. Perform one of these:
   • Select Use browse path for data collection.
   • From Driver for Collection, select the FactoryTalk Live Data driver for the data collection path and enter the collection path.
7. Select Save to add the data source.

Step 2: Contextualize

Step 2.1: Define Driver

Drivers enable communication between the gateway and data sources. Add drivers to configure data collection paths for data sources and FactoryTalk Smart Object instances. Go Online to add a driver. By default, an EtherNet/IP (CIP) driver is installed with FactoryTalk Edge Gateway.

LRESULT CALLBACK WndProd(
    _In_ HWEND  hWnd,
    _In_ UINT   message,
    _In_ WPARAM wParam,
    _In_ LPARAM lParam
);

Torque Calculator for Servo Motors This will help you convert motor torque feedback from percent to torque units and also calculate the Peak Torque/Force Lim parameter.

What is this for?

Simplify the calculation of the motor feedback torque in torque units for servo motors, as well as the conversion of the maximum torque from a given value in torque units to percent.

General Features

The use of the block or AOI (for Add-On Instruction) is extremely simple, just open the attached file labeled “AOI_TorqueCalculator_ForServoMotor - Application Code.ACD” and copy to your project file.

Add-On Instruction should look like this:

Limitations/Disadvantages

It can be used only with Servodrives with SERCOS network.

How can I make it work?

The AOI_TorqueCalculator_ForServoMotor automatically calculates the motor Torque Feedback in torque units. This AOI can also calculate the Peak Torque/Force Lim in percent from a desired maximum motor torque limit given in torque units.

This AOI is constituted by three sets of parameters: one set for configuration of the AOI, one set to convert Torque Feedback from % to torque units, and a set to convert the Peak Torque/Force Lim from torque units to %.

The user needs to enter only two motor parameters in the AOI: Continuous Stall Torque and Peak Stall Torque found in datasheets. All the other parameters needed in this AOI are automatically read from the drive when this AOI is enabled. This AOI continuously converts the Torque Feedback from percent to a given toque unit while enabled. The result is placed in the parameter Out_Torque_Nm. The torque unit is the same of the parameters Inp_ContStallTorque_Nm and Inp_PeakStallTorque_Nm. Meanwhile, this AOI can be used to calculate the parameter Peak Torque/Force Lim from the torque entered in the parameter Inp_DesiredTorqueLim_Nm, which corresponds to the maximum peak torque required for a particular application. The parameter Inp_DesiredTorqueLim_Nm is entered in torque units and the result for the Peak Torque/Force Lim stored in the parameter Out_ForceTorqueLim_Perc is given in percent.

This AOI must remain enabled to calculate Torque Feedback in a given torque unit.

AOI Control

Typically, the AOI_TorqueCalculator_ForServoMotor instruction can be executed when torque feedback needs to be read in torque units or when the Peak Torque/Force Lim needs to be calculated for specific torque limit as shown below.

Appendix: Parameter Definitions

Inp_Axis:
Axis (Servo_Axis_Drive data structure) that will have torque converted torque units.

Ref_MotorContStallCur:
This is a Message data type tag. This parameter is used to read the Motor Continuous Stall Current from the drive. The Motor Continuous Stall Current is parameter 111 (S:0:111) in a Kinetix drive. The Ref_MotorContStallCur tag is configured in the AOI as shown below. The Destination is the tag MTC.Inp_DriveContCur_mA.

Ref_MotorPeakStallCur:

This is a Message data type tag. This parameter is used to read the Motor Peak Stall Current from the drive. The Motor Continuous Peak Current is parameter 109 (S:0:109) in a Kinetix drive. The Ref_MotorPeakStallCur tag is configured in the AOI as shown below. The Destination is the tag MTC.Inp_MotorPeakStallCur_mA.

Ref_DriveContCur:

This is a Message data type tag. This parameter is used to read the Drive Continuous Current from the drive. The Drive Continuous Current is parameter 112 (S:0:112) in a Kinetix drive. The Ref_DriveContCur tag is configured in the AOI as shown below. The Destination is the tag MTC.Inp_DriveContCur_mA.

Ref_DrivePeakCur:

This is a Message data type tag. This parameter is used to read the Drive Peak Current from the drive. The Drive Peak Current is parameter 110 (S:0:110) in a Kinetix drive. The Ref_DrivePeakCur tag is set in the AOI as shown below. The Destination is the tag MTC.Inp_DrivePeakCur_mA.

Inp_ContStallTorque_Nm:

This is a REAL data type tag. The user uses this parameter to enter the Motor Continuous Stall Torque, which is found in the motor nameplate or in the Motion Selection Guide. This parameter is shown to be given in Nm. However, any other torque unit can be used if the Inp_PeakStallTorque_Nm be also set in the same toque unit. Thus, the torque feedback given in the Out_Torque_Nm will also be given in this same torque unit.

Inp_PeakStallTorque_Nm:

This is a REAL data type tag. The user uses this parameter to enter the Motor Peak Stall Torque, which is found in the Motion Selection Guide.

Out_Torque_Nm:

This is a REAL data type tag. This parameter shows the Torque Feedback converted from percent to the torque unit given by the parameters Inp_ContStallTorque_Nm and Inp_PeakStallTorque_Nm.

Inp_DesiredTorqueLim_Nm:

This is a REAL data type tag. This parameter is used to enter in torque units the torque limit for a particular application. The AOI converts this torque from torque units to percentage. This torque in percent is the Peak Torque/Force Lim to be manually entered in the Limits tab of the Axis Properties. The torque entered in this parameter must be in the same unit as the parameters Inp_ContStallTorque_Nm and Inp_PeakStallTorque_Nm.

Out_TorqueForceLim_Perc:

This is a REAL data type tag. This parameter returns the Peak Torque/Force Lim necessary to limit the motor torque to the value entered in the parameter Inp_DesiredTorqueLim_Nm. This parameter is given in percentage.

Sts_EN:

The Enable bit is set while the rung is on.

Sts_TLim:

This Torque Limit bit is set when the value entered in the Inp_DesiredTorqueLim_Nm parameter is higher than the torque that the motor-drive system can deliver.

Sts_ER:

The Error bit is set if same of the message instructions used to read parameters from the drive fail to communicate with the drive. This bit is reset when the AOI is enabled. When an error occurs, the error message can be read in the Message Configuration window which can be accessed by hitting the box beside the tag name as shown below.

Inp_MotorContStallCur_mA:

This is a DINT data type tag. This parameter is the Destination in the Ref_MotorContStallCur message. This parameter contains the Motor Continuous Stall Current in mA read from the drive by the Ref_MotorContStallCur message.

Inp_MotorPeakStallCur_mA:

This is a DINT data type tag. This parameter is the Destination in the Ref_MotorPeakStallCur message. This parameter contains the Motor Peak Stall Current in mA read from the drive by the Ref_MotorPeakStallCur message.

Inp_DriveContCur_mA:

This is a DINT data type tag. This parameter is the Destination in the Ref_DriveContCur message. This parameter contains the Drive Continuous Current in mA read from the drive by the Ref_DriveContCur message.

Inp_DrivePeakCur_mA:

This is a DINT data type tag. This parameter is the Destination in the Ref_DrivePeakCur message. This parameter contains the Drive Peak Current in mA read from the drive by the Ref_DrivePeakCur message.

Downloads

Please note: You will need to agree to the Terms & Conditions for each download.

Need Help?

If you need help with an application or have feedback from the Innovation Center, please contact us.

Test App Six Lorem ipsum dolor sit amet, consectetur adipiscing elit. Donec venenatis lectus quam, vitae fermentum ante pellentesque vel. In non erat in elit vestibulum venenatis sit amet vel nisl. Aliquam erat volutpat. Proin sagittis eget arcu vitae gravida.

Objective

Organize large volume of high-speed data with OT-based Information models. In high-speed production scenarios, it’s common for manufacturers the need to quickly access the entire set of operational related data (production, quality, maintenance, etc.) from various stages in the process.

Approach

Organize large volume of high-speed data with OT-based Information models. In high-speed production scenarios, it’s common for manufacturers the need to quickly access the entire set of operational related data (production, quality, maintenance, etc.) from various stages in the process.

Overview

FactoryTalk Edge Gateway software unifies data from industrial sources and control or automation systems. It integrates with a variety of cloud, IIoT, and big data applications including ThingWorx, Microsoft Azure IoT Hub, Microsoft SQL and more. This maximizes operational insights, simplifying and automating data ingestion in a single integration solution for IT applications.

With FactoryTalk Edge Gateway software user can create information models at the Operational Technology (OT) layer and efficiently map to upstream IT applications to improve performance KPIs like OEE, predictive quality and process efficiency.

With access to OT contextualized data, IT applications can help users to extract equipment insights across the enterprise. Quickly, easily, and proactively identify process and production inefficiencies and product defects. With less required data preparation time, customer can focus on using their data to detect and resolve equipment issues and improve production output.

Downloads

Please note: You will need to agree to the Terms & Conditions for each download.

Need Help?

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt.

• Simplifies and automates industrial data collection, contextualization, and organization across equipment, devices, and automation assets
• Enables IT/OT convergence
• Unlocks key industrial performance insights from OT data
• Enables high IT data integrity
• Integrates with a variety of cloud, IIoT and big data applications
• High speed, synchronous data collection
• Reduces the need for IT technical expertise

Installation Guide

Supports OT / IT collaboration by empowering control engineers -Without traditional IT skills- to identify the most appropriate data sets (Information models) and send information directly to the IT layer.

Step 1: Connect

Supports OT / IT collaboration by empowering control engineers -Without traditional IT skills- to identify the most appropriate data sets (Information models) and send information directly to the IT layer.

Step 2: Contextualize

Contextualize the data into Information Models: Allows OT engineer to organize data in context as it pertains to the OT assets, simplifies maintenance and updates.

Step 3: Map

Map the data to enterprise and cloud applications: Supports Azure IoT Hub and Azure IoT Edge, Creates SQL table needed to store data and creates objects in ThingWorx to replicate the information model.

Step 1: Connect

Step 1.1: Define Driver

Drivers enable communication between the gateway and data sources. Add drivers to configure data collection paths for data sources and FactoryTalk Smart Object instances. Go Online to add a driver. By default, an EtherNet/IP (CIP) driver is installed with FactoryTalk Edge Gateway.

Add a Driver:

1. Select Data Flow > Data Sources.
2. From Define Drivers, select Add to add a driver to the gateway.
3. From Select Driver, select the driver type to configure:
   • FactoryTalk Live Data (FTLD)
   • therNet/IP (CIP)
4. Select Next.
5. Enter the Driver Name and define the settings.
   • The name must contain only letters, numbers, and hyphens.
   • The settings differ for each driver type.
6. Select Save.

Step 1.2: Configure Data Sources

Configure data sources to populate a namespace and collect data from data tags and FactoryTalk Smart Object instances. Data tags are accessed from controllers, devices, and servers. FactoryTalk Smart Object instances require an offline Studio 5000 Logix Designer project file (.acd) to populate the namespace and an EtherNet/IP driver for data collection.

FactoryTalk Edge Gateway gathers the directory of data from the source and stores the data into a namespace. In the case of FactoryTalk Smart Object instances, the FactoryTalk Smart Object model is also discovered and replicated in Models. Use these data tags and models to configure the gateway. From Configure Data Sources, add, edit, delete, populate, clear, and filter data sources.

Use Case 1:

Smart Objects
(Add a data source from a Studio 5000 Logix Designer Project File [.acd]) + Logix Echo Controller

Add data sources from offline Studio 5000 Logix Designer controller project files to populate a namespace and collect data from data tags and FactoryTalk Smart Object instances. The supported file type is “.acd”. FactoryTalk Smart Object instances are only available from the Studio 5000 Logix Designer project file (.acd) data source type and require an EtherNet/IP (CIP) driver. The data from the “.acd” project file is later accessed from the device or server running the Studio 5000 Logix Designer project file.

FactoryTalk Edge Gateway is compatible with Logix firmware revisions 16.00 or later. FactoryTalk Smart Object instances are supported in Logix firmware revisions 28.00 or later. The Studio 5000 Logix Designer project file (.acd) data source is compatible with these drivers: FactoryTalk Live Data and EtherNet/IP (CIP).

Add a Driver:

1. Select Data Flow > Data Sources.
2. From Define Drivers, select Add to add a driver to the gateway.
3. From Select Driver, select the driver type to configure:
   • FactoryTalk Live Data (FTLD)
   • therNet/IP (CIP)
4. Select Next.
5. Enter the Driver Name and define the settings.
   • The name must contain only letters, numbers, and hyphens.
   • The settings differ for each driver type.
6. Select Save.

Use Case 2:

FactoryTalk Live Data Shortcut
Add a data source from a FactoryTalk Live Data Shortcut – CompactLogix controller and VSD

Add data sources from FactoryTalk Live Data to populate a namespace and collect data from data tags. The data source is also a shortcut to these source types: HMI TagDb, OPC DA server, OPC UA server, and FactoryTalk® Linx™ shortcut. The FactoryTalk Live Data Shortcut data source is compatible with the FactoryTalk Live Data driver.

Add a data source from a Studio 5000 Logix Designer project file (.acd)

1. Select Data Flow, Data Sources, and then from Configure Data Sources, add a data source.
   • To add the first data source, select Add Data Sources.
   • To add a subsequent data source, select Add.
2. Enter the name and then from Data Browse Path Type, select Logix Project File (ACD).
   • The name must contain only letters, numbers, and hyphens.
3. From Driver for browsing, select the FactoryTalk Live Data driver.
4. Select a network or local path and enter the browse path.
5. (optional) To automatically generate the namespace, select Auto-populate namespace.
6. Perform one of these:
   • Select Use browse path for data collection.
   • From Driver for Collection, select the FactoryTalk Live Data driver for the data collection path and enter the collection path.
7. Select Save to add the data source.

Step 2: Contextualize

Step 2.1: Define Driver

Drivers enable communication between the gateway and data sources. Add drivers to configure data collection paths for data sources and FactoryTalk Smart Object instances. Go Online to add a driver. By default, an EtherNet/IP (CIP) driver is installed with FactoryTalk Edge Gateway.

LRESULT CALLBACK WndProd(
    _In_ HWEND  hWnd,
    _In_ UINT   message,
    _In_ WPARAM wParam,
    _In_ LPARAM lParam
);

Test App Two Lorem ipsum dolor sit amet, consectetur adipiscing elit. Donec venenatis lectus quam, vitae fermentum ante pellentesque vel. In non erat in elit vestibulum venenatis sit amet vel nisl. Aliquam erat volutpat. Proin sagittis eget arcu vitae gravida.

Objective

<Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nosx ea commodo consequat.>

Approach

<Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nosx ea commodo consequat.>

Overview

<Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nosx ea commodo consequat.>

<Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nosx ea commodo consequat.>

<Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nosx ea commodo consequat.>

Downloads

Need Help?

item 1

item 2

item 3

• Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
• Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
• Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
• Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.

Installation Guide

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nosx ea commodo consequat.

Step 1

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nosx ea commodo consequat.

Step 2

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nosx ea commodo consequat.

Step 3

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nosx ea commodo consequat.

Step 1

Step 1.1

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nosx ea commodo consequat.

Steps:

• Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
• Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
• Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
• Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.

Step 1.2

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nosx ea commodo consequat.

Steps:

• Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
• Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
• Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
• Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.

Step 2

Steps:

• Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
• Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
• Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
• Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.

Step 3

Steps:

• Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
• Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
• Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
• Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.

Chitra_DMX-4338_SixthSCenario01

Downloads

Please note: You will need to agree to the Terms & Conditions for each download.

Need Help?

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt.

• Simplifies and automates industrial data collection, contextualization, and organization across equipment, devices, and automation assets
• Enables IT/OT convergence
• Unlocks key industrial performance insights from OT data
• Enables high IT data integrity
• Integrates with a variety of cloud, IIoT and big data applications
• High speed, synchronous data collection
• Reduces the need for IT technical expertise

Installation Guide

Supports OT / IT collaboration by empowering control engineers -Without traditional IT skills- to identify the most appropriate data sets (Information models) and send information directly to the IT layer.

Step 1: Connect

Supports OT / IT collaboration by empowering control engineers -Without traditional IT skills- to identify the most appropriate data sets (Information models) and send information directly to the IT layer.

Step 2: Contextualize

Contextualize the data into Information Models: Allows OT engineer to organize data in context as it pertains to the OT assets, simplifies maintenance and updates.

Step 3: Map

Map the data to enterprise and cloud applications: Supports Azure IoT Hub and Azure IoT Edge, Creates SQL table needed to store data and creates objects in ThingWorx to replicate the information model.

Step 1: Connect

Step 1.1: Define Driver

Drivers enable communication between the gateway and data sources. Add drivers to configure data collection paths for data sources and FactoryTalk Smart Object instances. Go Online to add a driver. By default, an EtherNet/IP (CIP) driver is installed with FactoryTalk Edge Gateway.

Add a Driver:

1. Select Data Flow > Data Sources.
2. From Define Drivers, select Add to add a driver to the gateway.
3. From Select Driver, select the driver type to configure:
   • FactoryTalk Live Data (FTLD)
   • therNet/IP (CIP)
4. Select Next.
5. Enter the Driver Name and define the settings.
   • The name must contain only letters, numbers, and hyphens.
   • The settings differ for each driver type.
6. Select Save.

Step 1.2: Configure Data Sources

Configure data sources to populate a namespace and collect data from data tags and FactoryTalk Smart Object instances. Data tags are accessed from controllers, devices, and servers. FactoryTalk Smart Object instances require an offline Studio 5000 Logix Designer project file (.acd) to populate the namespace and an EtherNet/IP driver for data collection.

FactoryTalk Edge Gateway gathers the directory of data from the source and stores the data into a namespace. In the case of FactoryTalk Smart Object instances, the FactoryTalk Smart Object model is also discovered and replicated in Models. Use these data tags and models to configure the gateway. From Configure Data Sources, add, edit, delete, populate, clear, and filter data sources.

Use Case 1:

Smart Objects
(Add a data source from a Studio 5000 Logix Designer Project File [.acd]) + Logix Echo Controller

Add data sources from offline Studio 5000 Logix Designer controller project files to populate a namespace and collect data from data tags and FactoryTalk Smart Object instances. The supported file type is “.acd”. FactoryTalk Smart Object instances are only available from the Studio 5000 Logix Designer project file (.acd) data source type and require an EtherNet/IP (CIP) driver. The data from the “.acd” project file is later accessed from the device or server running the Studio 5000 Logix Designer project file.

FactoryTalk Edge Gateway is compatible with Logix firmware revisions 16.00 or later. FactoryTalk Smart Object instances are supported in Logix firmware revisions 28.00 or later. The Studio 5000 Logix Designer project file (.acd) data source is compatible with these drivers: FactoryTalk Live Data and EtherNet/IP (CIP).

Add a Driver:

1. Select Data Flow > Data Sources.
2. From Define Drivers, select Add to add a driver to the gateway.
3. From Select Driver, select the driver type to configure:
   • FactoryTalk Live Data (FTLD)
   • therNet/IP (CIP)
4. Select Next.
5. Enter the Driver Name and define the settings.
   • The name must contain only letters, numbers, and hyphens.
   • The settings differ for each driver type.
6. Select Save.

Use Case 2:

FactoryTalk Live Data Shortcut
Add a data source from a FactoryTalk Live Data Shortcut – CompactLogix controller and VSD

Add data sources from FactoryTalk Live Data to populate a namespace and collect data from data tags. The data source is also a shortcut to these source types: HMI TagDb, OPC DA server, OPC UA server, and FactoryTalk® Linx™ shortcut. The FactoryTalk Live Data Shortcut data source is compatible with the FactoryTalk Live Data driver.

Add a data source from a Studio 5000 Logix Designer project file (.acd)

1. Select Data Flow, Data Sources, and then from Configure Data Sources, add a data source.
   • To add the first data source, select Add Data Sources.
   • To add a subsequent data source, select Add.
2. Enter the name and then from Data Browse Path Type, select Logix Project File (ACD).
   • The name must contain only letters, numbers, and hyphens.
3. From Driver for browsing, select the FactoryTalk Live Data driver.
4. Select a network or local path and enter the browse path.
5. (optional) To automatically generate the namespace, select Auto-populate namespace.
6. Perform one of these:
   • Select Use browse path for data collection.
   • From Driver for Collection, select the FactoryTalk Live Data driver for the data collection path and enter the collection path.
7. Select Save to add the data source.

Step 2: Contextualize

Step 2.1: Define Driver

Drivers enable communication between the gateway and data sources. Add drivers to configure data collection paths for data sources and FactoryTalk Smart Object instances. Go Online to add a driver. By default, an EtherNet/IP (CIP) driver is installed with FactoryTalk Edge Gateway.

LRESULT CALLBACK WndProd(
    _In_ HWEND  hWnd,
    _In_ UINT   message,
    _In_ WPARAM wParam,
    _In_ LPARAM lParam
);

Test App Five Lorem ipsum dolor sit amet, consectetur adipiscing elit. Donec venenatis lectus quam, vitae fermentum ante pellentesque vel. In non erat in elit vestibulum venenatis sit amet vel nisl. Aliquam erat volutpat. Proin sagittis eget arcu vitae gravida.

Objective

<Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nosx ea commodo consequat.>

Approach

<Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nosx ea commodo consequat.>

Overview

<Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nosx ea commodo consequat.>

<Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nosx ea commodo consequat.>

<Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nosx ea commodo consequat.>

Downloads

Need Help?

• Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
• Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
• Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
• Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.

Installation Guide

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nosx ea commodo consequat.

Step 1

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nosx ea commodo consequat.

Step 2

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nosx ea commodo consequat.

Step 3

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nosx ea commodo consequat.

Step 1

Step 1.1

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nosx ea commodo consequat.

Steps:

• Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
• Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
• Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
• Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.

Step 1.2

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nosx ea commodo consequat.

Steps:

• Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
• Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
• Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
• Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.

Step 2

Steps:

• Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
• Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
• Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
• Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.

Step 3

Steps:

• Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
• Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
• Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
• Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.

Test App Three Lorem ipsum dolor sit amet, consectetur adipiscing elit. Donec venenatis lectus quam, vitae fermentum ante pellentesque vel. In non erat in elit vestibulum venenatis sit amet vel nisl. Aliquam erat volutpat. Proin sagittis eget arcu vitae gravida.

Objective

<Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nosx ea commodo consequat.>

Approach

<Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nosx ea commodo consequat.>

Overview

<Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nosx ea commodo consequat.>

<Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nosx ea commodo consequat.>

<Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nosx ea commodo consequat.>

Downloads

Need Help?

• Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
• Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
• Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
• Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.

Installation Guide

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nosx ea commodo consequat.

Step 1

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nosx ea commodo consequat.

Step 2

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nosx ea commodo consequat.

Step 3

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nosx ea commodo consequat.

Step 1

Step 1.1

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nosx ea commodo consequat.

Steps:

• Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
• Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
• Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
• Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.

Step 1.2

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nosx ea commodo consequat.

Steps:

• Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
• Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
• Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
• Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.

Step 2

Steps:

• Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
• Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
• Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
• Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.

Step 3

Steps:

• Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
• Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
• Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
• Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.

DMX-6243

Objective

Organize large volume of high-speed data with OT-based Information models. In high-speed production scenarios, it’s common for manufacturers the need to quickly access the entire set of operational related data (production, quality, maintenance, etc.) from various stages in the process.

Approach

Organize large volume of high-speed data with OT-based Information models. In high-speed production scenarios, it’s common for manufacturers the need to quickly access the entire set of operational related data (production, quality, maintenance, etc.) from various stages in the process.

Overview

FactoryTalk Edge Gateway software unifies data from industrial sources and control or automation systems. It integrates with a variety of cloud, IIoT, and big data applications including ThingWorx, Microsoft Azure IoT Hub, Microsoft SQL and more. This maximizes operational insights, simplifying and automating data ingestion in a single integration solution for IT applications.

With FactoryTalk Edge Gateway software user can create information models at the Operational Technology (OT) layer and efficiently map to upstream IT applications to improve performance KPIs like OEE, predictive quality and process efficiency.

With access to OT contextualized data, IT applications can help users to extract equipment insights across the enterprise. Quickly, easily, and proactively identify process and production inefficiencies and product defects. With less required data preparation time, customer can focus on using their data to detect and resolve equipment issues and improve production output.

Downloads

Please note: You will need to agree to the Terms & Conditions for each download.

Need Help?

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt.

• Simplifies and automates industrial data collection, contextualization, and organization across equipment, devices, and automation assets
• Enables IT/OT convergence
• Unlocks key industrial performance insights from OT data
• Enables high IT data integrity
• Integrates with a variety of cloud, IIoT and big data applications
• High speed, synchronous data collection
• Reduces the need for IT technical expertise

Installation Guide

Supports OT / IT collaboration by empowering control engineers -Without traditional IT skills- to identify the most appropriate data sets (Information models) and send information directly to the IT layer.

Step 1: Connect

Supports OT / IT collaboration by empowering control engineers -Without traditional IT skills- to identify the most appropriate data sets (Information models) and send information directly to the IT layer.

Step 2: Contextualize

Contextualize the data into Information Models: Allows OT engineer to organize data in context as it pertains to the OT assets, simplifies maintenance and updates.

Step 3: Map

Map the data to enterprise and cloud applications: Supports Azure IoT Hub and Azure IoT Edge, Creates SQL table needed to store data and creates objects in ThingWorx to replicate the information model.

Step 1: Connect

Step 1.1: Define Driver

Drivers enable communication between the gateway and data sources. Add drivers to configure data collection paths for data sources and FactoryTalk Smart Object instances. Go Online to add a driver. By default, an EtherNet/IP (CIP) driver is installed with FactoryTalk Edge Gateway.

Add a Driver:

1. Select Data Flow > Data Sources.
2. From Define Drivers, select Add to add a driver to the gateway.
3. From Select Driver, select the driver type to configure:
   • FactoryTalk Live Data (FTLD)
   • therNet/IP (CIP)
4. Select Next.
5. Enter the Driver Name and define the settings.
   • The name must contain only letters, numbers, and hyphens.
   • The settings differ for each driver type.
6. Select Save.

Step 1.2: Configure Data Sources

Configure data sources to populate a namespace and collect data from data tags and FactoryTalk Smart Object instances. Data tags are accessed from controllers, devices, and servers. FactoryTalk Smart Object instances require an offline Studio 5000 Logix Designer project file (.acd) to populate the namespace and an EtherNet/IP driver for data collection.

FactoryTalk Edge Gateway gathers the directory of data from the source and stores the data into a namespace. In the case of FactoryTalk Smart Object instances, the FactoryTalk Smart Object model is also discovered and replicated in Models. Use these data tags and models to configure the gateway. From Configure Data Sources, add, edit, delete, populate, clear, and filter data sources.

Use Case 1:

Smart Objects
(Add a data source from a Studio 5000 Logix Designer Project File [.acd]) + Logix Echo Controller

Add data sources from offline Studio 5000 Logix Designer controller project files to populate a namespace and collect data from data tags and FactoryTalk Smart Object instances. The supported file type is “.acd”. FactoryTalk Smart Object instances are only available from the Studio 5000 Logix Designer project file (.acd) data source type and require an EtherNet/IP (CIP) driver. The data from the “.acd” project file is later accessed from the device or server running the Studio 5000 Logix Designer project file.

FactoryTalk Edge Gateway is compatible with Logix firmware revisions 16.00 or later. FactoryTalk Smart Object instances are supported in Logix firmware revisions 28.00 or later. The Studio 5000 Logix Designer project file (.acd) data source is compatible with these drivers: FactoryTalk Live Data and EtherNet/IP (CIP).

Add a Driver:

1. Select Data Flow > Data Sources.
2. From Define Drivers, select Add to add a driver to the gateway.
3. From Select Driver, select the driver type to configure:
   • FactoryTalk Live Data (FTLD)
   • therNet/IP (CIP)
4. Select Next.
5. Enter the Driver Name and define the settings.
   • The name must contain only letters, numbers, and hyphens.
   • The settings differ for each driver type.
6. Select Save.

Use Case 2:

FactoryTalk Live Data Shortcut
Add a data source from a FactoryTalk Live Data Shortcut – CompactLogix controller and VSD

Add data sources from FactoryTalk Live Data to populate a namespace and collect data from data tags. The data source is also a shortcut to these source types: HMI TagDb, OPC DA server, OPC UA server, and FactoryTalk® Linx™ shortcut. The FactoryTalk Live Data Shortcut data source is compatible with the FactoryTalk Live Data driver.

Add a data source from a Studio 5000 Logix Designer project file (.acd)

1. Select Data Flow, Data Sources, and then from Configure Data Sources, add a data source.
   • To add the first data source, select Add Data Sources.
   • To add a subsequent data source, select Add.
2. Enter the name and then from Data Browse Path Type, select Logix Project File (ACD).
   • The name must contain only letters, numbers, and hyphens.
3. From Driver for browsing, select the FactoryTalk Live Data driver.
4. Select a network or local path and enter the browse path.
5. (optional) To automatically generate the namespace, select Auto-populate namespace.
6. Perform one of these:
   • Select Use browse path for data collection.
   • From Driver for Collection, select the FactoryTalk Live Data driver for the data collection path and enter the collection path.
7. Select Save to add the data source.

Step 2: Contextualize

Step 2.1: Define Driver

Drivers enable communication between the gateway and data sources. Add drivers to configure data collection paths for data sources and FactoryTalk Smart Object instances. Go Online to add a driver. By default, an EtherNet/IP (CIP) driver is installed with FactoryTalk Edge Gateway.

LRESULT CALLBACK WndProd(
    _In_ HWEND  hWnd,
    _In_ UINT   message,
    _In_ WPARAM wParam,
    _In_ LPARAM lParam
);

Component

Test App One Testing changing description

Objective

<Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nosx ea commodo consequat.>

Approach

<Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nosx ea commodo consequat.>

Overview

<Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nosx ea commodo consequat.>

<Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nosx ea commodo consequat.>

<Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nosx ea commodo consequat.>

Downloads

Need Help?

• Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
• Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
• Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
• Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.

Installation Guide

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nosx ea commodo consequat.

Step 1

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nosx ea commodo consequat.

Step 2

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nosx ea commodo consequat.

Step 3

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nosx ea commodo consequat.

Step 1

Step 1.1

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nosx ea commodo consequat.

Steps:

• Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
• Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
• Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
• Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.

Step 1.2

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nosx ea commodo consequat.

Steps:

• Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
• Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
• Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
• Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.

Step 2

Steps:

• Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
• Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
• Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
• Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.

Step 3

Steps:

• Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
• Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
• Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
• Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.

Multibelt Transport System Designed to transport industry specially food and beverage, multibelt system is a storage/transport system used in many aplications where it requires movement of multiple products simultaneously from one point to another

What is this for?

The Multibelt system is a storage/transport system and consists of two or more independently driven belts. Each belt contains two or more trains (collators) that are built to carry a tray or built for a variable number of pockets. Trains vary in mechanical design. In the case of using a tray, the tray is placed inside the train in the loading position by any loading module. Products are fed from an infeed conveyor to the train at the filling position. If the feed train is full, it moves to the unloading position. If this is done, the train moves in positive rotation (recovery motion) behind the next train. This sequence guarantees a continuous flow of product in the filling area, while the other trains can be loaded with a tray and unloaded passing through the unloading position. The Multibelt equipment module can be configured with a large number of parameters, which are described in other chapters. A standardized interface for the load, supply and output module allows flexible adaptation. 

General Features

The  Multibelt System module concludes the following features:

• Multibelt storage sequence procedure for 2 axes (production mode)

• Automatic homing / reference move procedure

• Automatic synchronize move procedure

• Variable speed override adaption while production

• Jog function for each axis separately (service mode)

• Handling of multiple trains per belt

• Interface data handling to any other loading, infeed and outfeed module device

• Wide range of parameters to configure the module

Advantages:

The Mutibelt system has the advantage of being flexible and with the possibility of adaptation according to the application needs - number of collators (train).

From a software point of view, the system is relatively easy to implement using specific AddOn and Data DataTypes: Multibelt_AOI and Q_MAM_P (developed for this application, in order to reduce configuration, commissioning and startup time.

Limitations/Disadvantages

• Speed – Depends on the Drag Mechanism

• Number of mechanical elements - gears, belts

• Fixed space between cleats, if need change, mechanical change neededc

Is this useful for me?

In general, multibelt systems can be recommended to OEM manufacturers such as:

• Conveyor belt manufacturers
• Special machine manufacturers
• Palletizers manufacturers
• Packing machines manufacturers

Application areas:

Food, Manufacturing, Beverage

Benefits of applications with multibelt systems:

• Production gain and speed

• Increased dynamism in production

• 60% reduction in commissioning and startup time

• Easy of integration with devices: Robot, transfer devices

 

How can I make it work?

Requirements: Products, Tools, Previous Knowledge.

Hardware

• Kinetix 5300, Kinetix 5500, Kinetix 5700 with CIP Motion and CIP Sync
• PowerFlex 755 with Position control/ CIP Motion
• CompactLogix L18ERM or high
• Firmware revision 30 or high

Software

• Logix Design Studio 5000
• Program Multibelt_2Collators.ACD
• AddOn instructions: Multibelt_AOI, Q_MAP_P

Knowledge

Intermediate knowledge of programming and configuration in Logix Design Studio 5000 software:

• Ladder language (LD)
• Motion configuration.

Downloads

Please note: You will need to agree to the Terms & Conditions for each download.

Need Help?

If you need help with an application or have feedback from the Innovation Center, please contact us.

Installation Guide 

Additional information is in the "Multibelt.pdf" document in Downloads >> GeneralFiles.zip

Step 1:

Instructions:

1. Open program Multibelt_2Collators.ACD – This file is located inside the Generalfiles.zip package in the Downloads section.
2. Initially you can use this program with Virtual Axis for tests. After that you can couple the virtual axis with physical axis using Motion Axis Gear (MAG).

Step 2

Motion Configuration:

1. Configure the Axes Parameters Virtual (Collator_X_AV) and Physical (Collator_X_AP) . For Physical: Model of operation: Position Loop.
2. Configure the virtual axes.
3. Couple virtual axis with real – This function is already in the program example (Multibelt_2Collators.ACD) .

Step 3:

Configure Add-ons Data parameters:

1. MainTask > MainProgram > _01_Multibelt, Configure Add-on MultiBelt_AOI.

• Axis
• Axis Preceding
• Wagon Size
• Number of Wagons
• Loading Station Position
• Waiting Station Position
• Unloading Station Positions

2. MotionEventTask > Main_Motion_Rtn, configure Add-ON Q_MAM_P parameters (Setup and configure Train Data).

• Axis
• Axis Preceding
• Command Position
• Velocity
• Acceleration
• Deceleration 
• Acceleration Jerk 
• Decceleration Jerk

Step 4:

Download and commissioning

1. You can use the Emulator (Factory Talk Logix Echo)
2. For simulation, use MainTask > MainProgram > _02_Simulation program

LOTO - LockOut and TagOut How to make an efficient and safe digital electrical lock on electrical panels?

What is this for?

LOTO consists of a functionality available in Factory Talk View Studio SE and Studio 5000 that allows the safe, direct and indirect digital blocking of equipment in electrical panels, drawers and CMM, controlled by duly accredited users, increasing safety for operators and maintenance people. 

General Features

The electrical lock consists of the shutdown of the component responsible for energizing a circuit (usually a circuit breaker) and inserting a padlock into this disconnected circuit breaker, so that it cannot be reconnected by another person during the entire maintenance.

In this way, the electrical block prevents anyone from being able to access and/or maneuver this component and from energizing a certain circuit, where workers are intervening in maintenance.

Locks can be used individually or collectively, through multiplier devices, in situations where multiple teams are working on the same equipment, but on different service fronts. This way, the machine will only be energized when all team locks are removed.

After all, it is important to emphasize that the blockage in the electrical circuits must be carried out mainly in the power circuits and can be complemented with the shutdown of the control circuit. 

Next to the locking device, a signaling card is also inserted, usually containing the photo of the person responsible for the lock, its function and allocation sector, in addition to the name of the circuit or equipment that was blocked by it.

Therefore, the purpose of the signal card is to visually alert people not involved in the process that the equipment is blocked for some reason and cannot under any circumstances be energized.

Advantages:

LOTO with Factory Talk View Studio and Studio 5000 make it simple and safe to lock panels, CMM drawers, specific equipment such as valves, motors and instruments in the field.

• Time for configuration
• Request
• Authorization by the area owner
• Indication of padlock placement
• Indication of zero energy test by the area owner
• Removal of the blockade by the owner of the area
• Block outputs
• Label placement
• Label withdrawal
• Authorization by the General Manager
• Break by the maintainer
• More protection for operators and maintenance people

 

Is this useful for me?

In general, LOTO is recommended specially for automation process control where it requires the need to block equipments for maintenance and repairs.

• Cement process
• Food and Beverage process
• Chemical process
• Steel industry
• Mining Companies

Application areas:

Cement, Food and Beverage, Chemical, Steel, Mining.

Benefits of applications with LOTO systems:

• Secure digital lock management
• Treacebility
• Lock by area and equipment
• SQL Server database for record datas

 

How can I make it work?

Hardware

• Logix Controllers (ControlLogix / CompactLogix)

Software

• Factorytalk View SE Enterprise v13 or higher
• Studio 5000 Logix Desing v35 or higher
• SQL express (ou SQL Server para  FTAlarm&Event)
• FactoryTalk Logix Echo V2 (or Physical Controller)P

Knowledge

Intermediate knowledge of programming and configuration in Logix Design Studio 5000 software:

• Studio 5000 - Ladder language (LD)
• Studio 5000 - Function Block Diagram (FBD)
• Factory Talk View Studio
• Factory Talk Echo

Downloads

Please note: You will need to agree to the Terms & Conditions for each download.

Need Help?

If you need help with an application or have feedback from the Innovation Center, please contact us.

Installation Guide 

Step 1:

Studio 5000 Logix Design:

1. Download files documentation available
2. Open FILES> LOTO_Aplication Referency_en_EN.docx – Use this document as referency
3. Studio 5000 Logix Desing, Open program PController_FTEcho.ACD in Files/CS – Control Strategie
4. Import the 32Dis Card (to exemplify using the "Connection" where we can modify with the controller running without stopping)
5. Slow/Slow Program, import routine MTR_Lock_Routine_FBD.L5X.

Step 2

Factory Talk Logix Echo:

1. Open FactoryTalk Logix Echo - ControlLogix 5580 Emulator V35
2. Add the controller (ACD) PController_FTEcho.ACD
3. In Studio 5000, Who Active, Select Emulate 5580 Controller and Download the program and Run Mode.

Step 3:

Factory Talk SE:

1. Open FactoryTalk View SE Application Manager
2. Restore an Archive (menu), FILES\Backup .Apb – Distribuited Application, Select LOTO_2023_01.apb application. Check the name of your machine (Primary Host)
3. Open Application in FT View Studio (Network Distributed)
4. Import alarm configuration from Excel file. FILES\Alarms Exported > LOTO_2023_01_FTAE_AlarmExport.xls
5. Configure the communication setup
6. Add Database in System\Connections\Databases.

Step 4:

Factory Talk SE – Application:

1. Where we have a folder called LOTO, the sample screens "001_Coluna 1-8" for use in the application
2. With the "001_Coluna 1-8" screen open, see that each column contains its devices in each drawer, thus setting up according to your CCM
3. Add Engine lock MTR001 in Column 3 (ra-blk) equip lock and hold and drag the "GO_EqpLockLOTO" object to Column 3.

Step 5:

Factory Talk SE – Client Application:

1. Click on the FactoryTalk View Client file in the folder (if I need to edit to work, please click with the right and Edit). We have in the Example of the PlantPAx DCS template where it can be used.
2. Column 1-8" button opens the screen with the CCM
3. See that automatically the column we set up appears already configured
4. Type as example "RAZAO 01" and click ENTER to start Digital Lock  
5. "Request", check to follow the next step
6. Follow the steps and see that there is the possibility of checking STATUS (reason) for the following items (Autoruzar and Zero Energia)
7. In the Etiquete we have as shown the option below and in the lock /padlock icon for the execution of the job or the break of the same all recorded in the events). In the Advanced icon, check the other available settings. For modification of descriptions, it can be done via faceplate or via controller in aoi MTR001_lock 
8. After performing the job, click "Unlock" the faceplate will return to normal mode (all clean action)
9. To Check all the steps taken for blocking, users, comments, click "Events" and navigate each line for detailing

Master-Slave application using PowerFlex 755TS Master-follower system with fast parameter setup for precise and efficient synchronization in industrial applications.

What is this for?

The master-slave application using frequency drives with load variations on the motor shaft demonstrates the PowerFlex 755TS frequency drive's ability to respond to these changes with rapid response and precise speed control, as well as the adaptive control operation in response to load variations.

This system enables the synchronization of two AC motors with PowerFlex 755TS frequency drives using a master-slave scheme, along with the use of DC motors as loads. 

This demonstration includes operating in both automatic and manual modes. It offers a comprehensive solution that combines visualization tools, integration with the Logix platform, and operation to visualize the response of the frequency drives. 

General Features

The master-slave application with load variations offers the following features:

• Operating modes: Automatic and manual.
• Adjustable speed reference.
• Simulation of load variations with DC motors.
• Flexibility and adaptability to a variety of industrial applications.

Advantages

• Demonstrates the integration of monitoring and operation tools.
• Streamlines the programming time of frequency drives.
• Exhibits scalability and repeatability to adapt to various industrial environments.
• Allows agile and precise modifications according to changing needs.
• Provides versatile control that adjusts to different application scenarios.
• Optimizes performance in terms of efficiency and productivity.

Is this useful for me?

Frequency drives with Total Force technology represent an effective solution because the adaptive control of the PowerFlex 755TS can adapt to changes in motor load, fluctuations in supply voltage, and other variable operating conditions. This ensures an optimal response of the frequency drive to different operating scenarios, enhancing system stability and reducing the possibility of failures or performance issues.

This improvement in energy efficiency brings significant benefits, including reduced carbon emissions and compliance with increasingly stringent environmental regulations in the industry. Additionally, by smoothly controlling the speed and torque of the motors, mechanical wear on the equipment is reduced, extending its lifespan and lowering maintenance costs.

The master-slave application minimizes the time required to configure slave parameters, reducing the total system startup time, allowing for quicker and more efficient implementation in the workplace.

How can I make it work?

Hardware

• 2 AC Motors IDVSNM3581T-5.
• 2 DC Motors Bulletin 1325R.
• 2 PowerFlex 755TS Frequency Drives.
• 2 PowerFlex DC Frequency Drives.
• PanelView Plus 7.
• ControlLogix 5573. 

Software

• Studio5000(V35)
• FactoryTalk View(V12)
• Connected Components Workbench(CCW - V21)

Required knowledge

Knowledge of CCW, AC and DC motors, and Studio 5000.

Links of Interest:

https://www.rockwellautomation.com/es-mx/support/product/product-downloads/innovation-center/potenciometro-dancer-para-powerflex-755T.html 

https://www.rockwellautomation.com/es-mx/products/hardware/allen-bradley/new/powerflex-755ts.html

Downloads

Please note: You will need to agree to the Terms & Conditions for each download.

Need Help?

If you need help with an application or have feedback from the Innovation Center, please contact us.

Installation Guide

Step 1

Identify the applications used for implementation: CCW, Studio 5000, and FactoryTalk View.

Step 2:

Open the CCW application, click on File, Import Project, and import the .ccwarc files.

Step 3:

Access the device parameters and modify the IP to place it on the same network mask as your computer, controller, and PanelView.

Step 4:

Open the Studio 5000 application and run the project: Master_Slave.ACD, configure the assigned IP addresses, leaving the device names the same.

Step 5:

Validate the connection of each part of the system through pings in Command Prompt.

Step 6:

Open FactoryTalk View with the RA_Master_Slave.apa file, within FactoryTalk ensure that the server points to the project controller.

Step 7:

Create the runtime application of the HMI and upload it to the PanelView for project visualization.

Step 8:

The master motor's speed reference, in Hz, entered analogically, is reflected in the numeric indicator. The "START" and "STOP" buttons on the HMI serve to start and stop the rotation of the motors.

Step 9:

When pressing the "Master Trend" button, a pop-up screen allows us to monitor the current and torque variables of the master motor.

Step 10:

When pressing the "Slave Trend" button, a pop-up screen allows us to monitor the current and torque variables of the slave motor.

Solutions for enabling IT/OT convergence The Converge IT & OT application helps to simplify and automate industrial data collection through a common information model, mapping and contextualization.

What is this for?

OT/IT Convergence Solution provides the right foundation to drive edge-to-cloud integration at the enterprise level to accelerate IIoT digital transformation. It simplifies and automates collection, contextualization, and organization of industrial equipment data across machines, devices and automation assets at the plant floor while enabling high data integrity.

This is especially useful when working with operational data locked in disparate devices or siloed in systems of record. High-speed, contextualized OT data from controllers is discovered and packaged automatically in a logical, common information model that control engineers can configure. This common information model speeds setup for similar assembly lines and can be enriched with third-party data. It can be mapped to on-prem or cloud applications and easily consumed. Solution unifies data from industrial sources and control or automation systems.

It integrates with a variety of cloud, IIoT, and big data applications including ThingWorx, Microsoft Azure IoT Hub, Microsoft SQL and more. It also uses OPC-DA to access KEPServer Enterprise data for third party connectivity. With access to OT contextualized data, IT applications can help users to extract equipment insights across the enterprise: Quickly, easily and proactively identify process and production inefficiencies and product defects; allowing to focus on using the data to detect and resolve equipment issues and improve production output.

General Features

The  OT/IT convergence solution provides the following features: 

• Simplifies and automates industrial data collection, contextualization and organization across equipment, devices and automation assets.
• Unlocks key industrial performance insights from OT data.
• Enables high IT data integrity.
• Integrates with a variety of cloud, IIoT and big data applications.
• Reduces the need for IT technical expertise.
• Automatic creation of information, application content and databases.
• Organize large volume of high-speed data with OT-based information models.
• Connect disparate data sources, add application context and enable contextual data delivery.

 

Advantages

Supports OT/IT collaboration by empowering control engineers to identify the most appropriate data sets and send information directly to the IT layer.

Limitations/Disadvantages

• Licensed software required, subscription only.
• License tag counts are not additive.
• Tags are counted when information models are deployed, a tag used in multiple applications on the same gateway is counted only once.

 

Is this useful for me?

Convergence solutions are suitable for OT engineers interested in automate the contextualization of the operational data as close to the source before populating the information at the IT level for other analytical applications. Typical use case examples:

• Data collection and contextualization.
• Create organization structure aligned with intended data analysis utilization whether via information modeling alone or smart objects and information modeling combined.
• Perform intended data analysis with other analytics software.

Application areas

Food and Beverage, Automotive and Tire, Manufacturing, etc.

Benefits of applications with OT/IT convergence solutions:

• Baseline benefit comes from the information model and ability to contextualize to the asset hierarchy.
• For users that have a Rockwell Automation Integrated Architecture system, additional benefit is realized by adding Smart Objects configuration properties and achieving synchronized data collection at high resolutions.
• The data collection and organization capabilities provide value by empowering OT collaboration with IT and also provides the ability to egress contextualized data sets for big data analysis projects.
• Improve engineering efficiency for project deployment and accessibility to data.

 

How can I make it work?

Hardware

• PowerFlex 525
• CompactLogix, ControlLogix 
• Firmware revision 30 or high.

Software

• Programs: FTEGSmartObjects.ACD, ACMTR88HMI.apa
• Studio 5000 Logix Emulate v33
• Studio 5000 Logix Designer v34
• FactoryTalk Logix Echo v33.11.00
• Studio 5000 Application Code Manager v4.02.00
• FactoryTalk ViewME v12.00.00
• FactoryTalk Edge Gateway v3.00.00
• ThingWorx 9.0
• FactoryTalk Administration Console v6.30.00
• Microsoft SQL Server Management Studio v18.9.1
• SQLServer/SQLExpress
• Azure IoT Explorer Preview v15.00
• Azure IoT Hub

Knowledge

Familiarity with control theory, controller coding skills, application knowledge (Preferable OT engineer) that can relate with the intended use case and analysis once the data has reached its intended destination. Intermediate knowledge of programming and configuration in Logix Design Studio 5000 software.

Downloads

Please note: You will need to agree to the Terms & Conditions for each download.

Need Help?

If you need help with an application or have feedback from the Innovation Center, please contact us.

Installation Guide 

Step 1:

1. Identify the use cases for implementation:

1.1 Test Client Application

1.2. ThingWorx Application

1.3. SQL Server Application

1.4. Azure IoT Hub Application

Step 2

Add a driver:

1. Select Data Flow > Data Sources.

2. From Define Drivers, select Add to add a driver to the gateway.

3. From Select Driver, select the driver type to configure:

• FactoryTalk Live Data (FTLD)
• EtherNet/IP (CIP)

4. Select Next. 

5. Enter the Driver Name and define the settings.

• The name must contain only letters, numbers, and hyphens.
• The settings differ for each driver type. 

6. Select Save. 

Step 3:

Add a data source:

1. Select Data Flow > Data Sources, and then from Configure Data Sources, add a data source.

• To add the first data source, select Add Data Sources.
• To add a subsequent data source, select Add. 

2. Enter the name and then from Data Browse Path Type, select Logix Project File (FTEGSmartObjects.ACD). 

• The name must contain only letters, numbers, and hyphens. 

3. Browse for the file path and select the .acd file. 

4. (optional) To generate the namespace, select Auto-populate namespace. 

5. From Driver for Collection, select the FactoryTalk Live Data or EtherNet/IP (CIP) driver. 

6. Enter the collection path.

7. Select Save to add the data source.

Step 4

Test the application

1. Test Client. The Test Client application displays live data streaming into the gateway when Enable Data Flow is selected.

2. ThingWorx. Collect information from Rockwell Automation and third-party sources and send it to a ThingWorx Foundation server.

3. SQL Server. Provides a method to collect information from Rockwell Automation and third-party sources.

4. Azure IoT Hub.

Ease of integrating a MT IND360 weight indicators via Ethernet/IP Ease of integrating a Mettler Toledo IND360 weight indicators via Ethernet/IP using Application Code Manager

What is this for?

The Mettler Toledo IND360 product is a product for accurate weight measurement (load cell) and allows excellent integration with our controllers (ControlLogix, CompactLogix) via Ethernet/IP. The partnership between Mettler Toledo and Rockwell Automation has allowed the development of libraries such as Add-on, Faceplates (HMI), sample codes, to make integration easy and fast. With the Application Code Manager feature (code generator and screens) it is possible to integrate, generate controller application code (Studio 5000), generate HMI screens and network configurations, reducing setup time and startup of production lines and industrial machines.

https://www.mt.com/us/en/home/library/case-studies/industrial-scales/Encompass.html

 

General Features

Our Device Object Libraries allow you to easily interact with Rockwell Automation® Intelligent devices, as drives, motion, network switches, sensors, IoT, and more. The libraries contain tests, documented, and lifecycle. Managed objects that can be used with the manufacturer of machines, processes, and libraries packaged or as stand-alone components. Device Objects Include HMI Faceplates para FactoryTalk® View ME/SE e Studio 5000 View Designer® software and provide a user interface that integrates seamlessly with the goods.

HMI faceplates are standard display files that provide the average user with Interface. These are HMI pop-up screens used to display detailed information related to a specific instruction or device. On systems that follow ISA 101.1 According to design guidelines, front-facing displays are often referred to as Level 4 monitors.

Preconfigured device objects include a supplemental instruction line and a HMI front panel that offers the following benefits:

• Collect, process, and deliver data between smart devices and Application Logic
• Detailed collection and delivery of device data
• Improved device status and diagnostics
• Common control interfaces that maximize device automation flexibility Selection and reuse of application code

Device objects use cases:

• Basic device maintenance and diagnostics
• Virtual device operations for start-up and commissioning
• Operator and program control for machines and processes Applications

 

Advantages

Integration via Ethernet/IP allows for excellent ease of integration, reducing time and line start-up process. Use of Application Code Manager to generate controller code (Add-on) and general configurations and construction of HMI faceplates for integration.

 

Application Code Manager

Studio 5000® Application Code Manager is a tool that can be used with Device Object libraries to speed up the development of projects and machines. This volume Coding tool allows you to easily design and standardize functionalities with Reusable application code. Enable more efficient project development with reusable code libraries:

• Quickly create and deploy projects through our app content

 

Libraries

• Import Rockwell-sourced application content libraries for agility system development.

 

Limitations and drawbacks

Number of IND-360 devices, integrated via Ethernet/IP, depends on the limitation of CIP connections of each controller used.

 

Is this helpful for me?

Integration via Ethernet/IP allows excellent ease of integration, reducing time and start-up of lines, process and industrial machines.

 

How can I make it work?

Hardware

• PanelView™ 5500 with v8 or later firmware
• PanelView™ Plus with v10 or later firmware
• ControlLogix® 5570/5580 controller or CompactLogix™ 5370/5380
• Controller with v3.01 or later firmware

Software

• Studio 5000 Logix Designer® v31.02 or later for PAC Application Development
• Studio 5000® Application Code Manager v4.01 and later for bulk code configuration
• Studio 5000 View Designer® v8.00 and later for PanelView™ 5000 Application Development
• FactoryTalk® View Studio v10 and later for PanelView™ Plus or
• FactoryTalk® View SE Application Development

Required knowledge

• SO Windows
  
• Studio 5000 Design Studio and View Design
• FactoryTalk View Studio ME
• FactoryTalk View Studio SE
• Application Code Manager - Basic

Downloads

Please note: You will need to agree to the Terms & Conditions for each download.

Need Help?

If you need help with an application or have feedback from the Innovation Center, please contact us.

Installation Guide

To implement, check the steps below.

Step 1

Manual de Referência: DEVICE-RM905A-EN-P.pdf

 

Localizado em General_Files.zip, no caminho:

MettlerToledoDeviceLibrary_v1.00.00\Reference Manual\DEVICE-RM905A-EN-P.pdf

 

Como importar e configurar objetos de dispositivo Metter Toledo no ACM – Application Code Manager.

Step 2

How to Import and Configure Metter Toledo Device Objects in Studio 5000 Logix Design.

Step 3

How to Import and Configure Metter Toledo Device Objects in FactoryTalk View ME and SE.

Step 4

How to Import and Configure Metter Toledo Device Objects in Studio 5000 View Design.

Step 5

MT-IND360 Visualization & Operational Data - Faceplates.

MicroLink Remote Control, MicroLink MQTT Remote Control Streamline IoT in industrial environments. Unlock MQTT capabilities effortlessly through Micro800 controllers.

MicroLink MQTT is a transformative suite of User-Defined Function Blocks (UDFBs) for Micro800 controllers, enabling seamless MQTT communication with any MQTT broker. This package includes three function blocks: one for establishing connections, one for subscribing to specific topics, and one for publishing data. It offers high customizability with settings for unique MQTT IDs, broker/server IP addresses, usernames, passwords, and your chosen Quality of Service (QoS).

Target to use with PowerFlex 523 and 525 component drives from Rockwell Automation.

This code can be used with the following equipment:

• PowerFlex 523
• PowerFlex 525
• Micro850
• Micro870
• PanelView 800d

 

What is this for?

MicroLink MQTT is a UDFBs suite designed for seamless integration with Micro800 controllers from Rockwell Automation. It's meant to enhance the capabilities of these controllers by enabling MQTT communication with any MQTT broker.

This solution is especially useful for remote control use cases and in the industrial field where data exchange and communication efficiency are critical. MicroLink MQTT provides three function blocks for establishing connections, subscribing to specific topics, and publishing data.

With MicroLink MQTT, users can easily establish a connection to an MQTT broker, subscribe to the data they need, and publish data back to the broker. It offers high customization options for MQTT IDs, broker/server IP addresses, usernames, passwords, and your chosen Quality of Service (QoS), ensuring efficient and secure data communication.

Therefore, whether you're an industrial operator looking to optimize data communication or a developer who needs to integrate efficient data exchange in your applications, MicroLink MQTT can be the perfect solution.

General Features

Our package provides three core User-Defined Function Blocks:

• RA_MQTT_CONNECT_v2: Step into the future with our connection function block. It lets your Micro800 controller establish a connection with an MQTT broker, setting the stage for robust data interchange.
• RA_MQTT_SUBSCRIBE_v2: Leverage our subscription function block to stay connected with the data you need. Tailor your subscriptions to specific topics from the MQTT broker and always keep your operations data-rich and up-to-date.
• RA_MQTT_PUBLISH_v2: Take control with our publish function block. Transmit data with precision by publishing topics to the MQTT broker, making your data-driven operations a benchmark for others to follow.

Each function block is highly customizable, allowing you to specify unique MQTT IDs, broker/server IP addresses, usernames, passwords, and your preferred Quality of Service (QoS). With RA_MQTT v2, every aspect of your MQTT communications is in your hands.

Limitations / Disadvantages

• Limited to Micro820, Micro850 and Micro870
• Third-party MQTT broker dependent

 

How can I make it work?

The architecture implies using Micro820, Micro850, Micro870 hardware. And this is the required software:

• Connected Component Workbench, version 21 or higher.
• The firmware of the equipment used must be compatible with the version of Connected Component Workbench.
• User-defined Function Blocks:
  • RA_MQTT_CONNECT_v2
  • RA_MQTT_SUBSCRIBE_v2
  • RA_MQTT_PUBLISH_v2

Knowledge

A foundational understanding of ladder programming and system configuration using the Connected Components Workbench software is highly recommended. Additionally, familiarity with MQTT protocols would be beneficial.

Downloads

Please note: You will need to agree to the Terms & Conditions for each download.

Need Help?

If you need help with an application or have feedback from the Innovation Center, please contact us.

Installation Guide 

Step 1:

Establishing Connection Settings to Connect to or Disconnect from a MQTT Broker

An MQTT broker essentially serves as a server to manage MQTT messages. To connect to an MQTT broker, we must input the broker's IP address and port number into the RA_MQTT_CONNECT_v2 UDFB. The broker could be housed on your computer (in which case you would need to install and operate an MQTT broker compatible with your OS), or it could be a remote server, such as the ones previously mentioned.

1.1 Assign the IP address and port number of the MQTT broker to your RA_MQTT_CONNECT_v2 UDFB

This example is for connecting to the test.mosquitto.org broker in the cloud.  An alternative to entering the IP address directly is to enable Domain Name Service (set ‘EnableDNS’ TRUE) after entering in the MQTT broker URL into ‘MQTTBrokerName’ and the local DNS server IP address into ‘DNSIPaddr’ in rung 2.

1.2 Enter a unique ‘clientName’, as well as a ‘userID’ and ‘userPass’ if your MQTT broker requires it. (Many public MQTT brokers do not require a username and password, so these fields are optional and can be left blank if not required.)

1.3 Set ‘EnableMQTT’ to TRUE to connect to the MQTT broker.

Note:

There are a few things to keep in mind to ensure a successful connection. The MQTTsocketSts should eventually display a 9. If it shows a 7 and then reverts back to 0, it could imply that your broker is either not running or doesn't exist.

The data in resultData_Out is helpful for diagnostic troubleshooting. Typically, when you send a connect command to the server, the server responds with an acknowledgement. The acknowledgement is indicated by the 1st byte, which in this instance, is '32'.

Another frequent response you'll receive is a ping acknowledgement, denoted by '208' in the 1st byte of the returned data. The ping command is sent to the remote broker at 50-second intervals. This interval is hardcoded in the UDFB but can be modified if needed.

If the return data is something other than 32 or 208 upon connection, it could suggest that the client has subscribed to a topic that was broadcasted while it was offline. The message is retained and sent to the client when it comes back online. If you encounter this, process the message and then reinitialize the connection.

1.4 If you want to configure for LWT, you need to access these parameters in the UDFB:

322| willTopic := willTopic_In;
323| willData := willData_In;

‘willTopic_In’ is where you enter the Last Will topic for the connection.

‘willData_In’ is where you enter the testament for the connection.

The MQTT broker will publish the testament to all clients that subscribe to the Last Will topic when the client is disconnected abruptly.

1.5 If you want to disconnect gracefully from the server (without triggering LWT), set ‘disconnect_Cmd’ to TRUE.

This is a rising edge triggered bit, so you can reset it immediately.

Step 2

Subscribing to or Unsubscribing from a Topic

The MQTT protocol exchanges data through subscribe and publish methods. Clients communicate directly only with the MQTT broker. Clients subscribing to a topic will receive a message from the broker when another client publishes to that topic. Clients can be of any form as long as they have a running MQTT client application. For example, it could be software on a PC, a connector or API for the software, an app on a phone, or application code on a PLC.

2.1. Enter the name of the topic (‘topicName_input’) to subscribe to or unsubscribe from.

2.2. Set the quality of service (‘subQoS’) for the subscription. By default, use ‘0’ as it consumes the least bandwidth.

2.3. Set ‘subscribe’ or ‘unsubscribe’ to TRUE to subscribe to or unsubscribe from the topic.

2.4. These bits detect for rising edge, so you can reset them immediately.

2.5 Notice that the resultData_Out from RA_MQTT_CONNECT_v2 is also copied to respondData_In.

Note:

It is recommended to use only 1 instance of each UDFB.

Step 3:

Publishing a Topic

When a topic with data is published to an MQTT broker, the broker then forwards this topic data to all the clients subscribed to it. The client that publishes the message does not know if any remote nodes receive the topic, as that responsibility lies with the broker, depending on the QoS level. Topics can be published or subscribed to at any QoS level, but they will only be delivered at the lowest QoS level.

3.1. Enter the topic to publish into ‘pubTopic_In’.

3.2. Enter the data for the topic into ‘pubData_In’.

3.3. Set the quality of service into ‘pubQoS’. By default, use ‘0’ as it consumes the least bandwidth.

3.4. Set ‘publish’ to TRUE to publish the topic with its data. It will automatically will be set back to FALSE when ‘publishDN’ becomes TRUE.

3.5. Notice that the resultData_Out from RA_MQTT_CONNECT_v2 is also copied to respondData_In.

Step 4

Getting Messages from Subscribe Topics

The MQTT broker handles all topic subscriptions. It sends the data of any published topic to the clients that are subscribed to it. When a topic is received by the Micro800 MQTT client, it populates the 'TopicName' and 'TopicData' array variables in the RA_MQTT_CONNECT_v2 UDFB. The data is stored in a First In/First Out order, so it is crucial to process the data before it gets overwritten.

Step 5

Subscribing to an Array of Topics

MQTT_Subscriptions is an optional Structured Text program that works in conjunction with the MQTT_Client program. It enables you to subscribe to a 'Subscriptions' array of preconfigured topics. Adjust the array dimension of the global variable 'Subscriptions' to the desired size and modify the initial value of the local variable 'maxSubscriptions' to match the array size (default=10). 'Subscriptions' is a User-Defined Data Type (UDT) array that comprises the MQTT topic 'Name', the latest topic 'Data', a timestamp based on the RTC value when the latest topic 'Data' was received, and a 'Subscribed' indicator. Enter the desired topic names to subscribe to as initial values for Subscriptions[i].Name before downloading the project to the controller.

Local variable 'enableSubcriptions' must be TRUE in order to enable this functionality.

Step 6

Automatically Publishing an Array of Topics

MQTT_Publications is an optional Structured Text program that works in conjunction with the MQTT_Client program. It allows you to publish an entire 'Publications' array of preconfigured topics. Adjust the array dimension of the global variable 'Publications' to the desired size and modify the initial value of the local variable 'maxPublications' to match the size of the array (default=10). 'Publications' is a User-Defined Data Type (UDT) array that comprises the MQTT topic 'Name', the latest topic 'Value', the previous topic value 'Valueprev', and a timestamp based on the RTC value when the latest topic 'Value' was published. Enter the desired topic names to publish as initial values for Publications[i].Name before downloading the project to the controller.

Set the local variable 'ChangeOfState' to TRUE to publish any value that changes on an exception basis. Set the local variable 'Interval' to TRUE and 'intervalTime' to a non-zero value to publish all of the current values that aren't null ('') on a timed interval basis. Typically, one would choose either 'ChangeOfState' or 'Interval' as the method for publishing topic updates. For a one-time update, set the local variable 'OnDemand' to TRUE to publish all current values that aren't null (''). 'OnDemand' is set to FALSE once the entire 'Publications' array has been published. The local variable 'enablePublications' must be set to TRUE to enable this program functionality.

Easy Dashboards and Control for a Powerflex 520 This is a Connected Component Workbench development that provides basic parameters monitoring and control, either from a PanelView 800 or remotely (through VNC)

Easy Dashboards and Control for a Powerflex 520 enables you to have a ready to use code and HMI screens to apply them with PowerFlex 523 and PowerFlex 525 drives. This is a Connected Component Workbench development that provides basic parameters monitoring and control, either from a PanelView 800 or remotely (through VNC).

Target to use with PowerFlex 523 and 525 component drives from Rockwell Automation.

This code can be used with the following equipment:

• PowerFlex 523 
• PowerFlex 525
• Micro850
• Micro870
• PanelView 800

What is this for?

The main purpose is to provide visualization and basic control through principal parameters as a ready-to-use development for basic drive control. In addition, it will be possible to access the information contained in the dashboards remotely (Internet).

This can be applied to control systems that include Micro-controllers and Powerflex 520 component drives. Implicit and explicit messaging are used (the most important parameters are handled by implicit messaging).

General Features

• Basic Control parameters modification:
  • Reference Speed
  • Acceleration Time
  • Deacceleration Time
  • Position Reference

• Drives faults reset

• Visualization of the following parameters:
  • Ready
  • Active
  • Command Speed
  • Actual Speed
  • Drives fault
  • Output current
  • Output voltage
  • DC Bus voltage
  • Drive temperature
  • Consumed energy
  • Elapsed power
  • Accumulated cost savings

• Remote access to the PanelView 800 screens through FTP functionalities

 

Limitations/Disadvantages

• Limited to PowerFlex 523 and 525
  
• Limited to Micro800 and PanelView 800
• Parameters selected are fixed

 

How can I make it work?

The architecture implies the following hardware:

• PowerFlex 523, PowerFlex 525
• Micro 850, Micro 870
  
• PanelView 800

And this is the required software:

1. Connected Component Workbench, version 21 or higher.
2. The firmware of the equipment used must be compatible with the version of Connected Component Workbench.
3. User-defined Function Blocks:

• RA_PF523_VEL
• RA_PF525_VEL
• RA_PF525_POS
• RA_PFx_ENET_PAR_READ
• RA_PFx_ENET_PAR_WRITE

Knowledge

Basic knowledge of programing and configuration in Connected Component Workbench software:

• PowerFlex 523/525 and PanelView 800 configuration
• Ladder Language

Downloads

Please note: You will need to agree to the Terms & Conditions for each download.

Need Help?

If you need help with an application or have feedback from the Innovation Center, please contact us.

Installation Guide 

Step 1: Communication Settings

1.1 Configure VNC settings in PanelView 800: Go to the main configuration screen.

1.2 Press terminal settings.

1.3 Press Communication.

1.4 Press VNC Settings.

Step 2: Parameters import

2.1 Import “Parameters_52X”.

Step 3: PanelView800 configuration

3.1 Verify that all FTP Accessibility Settings are enable.

3.2 Configuration of email server and account setting to send email on PV800 (optional).

Step 4: Configuration of the PowerFlex 523/525

4.1 Create the PowerFlex as Ethernet modules (this enables implicit messaging)

4.2 PowerFlex523 communicated with EIP card (2 ports) and speed control mode.

4.3 PowerFlex525 communicated with EIP card (2 ports) and speed control mode.

4.4 PowerFlex525 communicated by ethernet Embedded IP and position control mode.

4.5 Configuration of parameters for Ethernet communication. For communication by 25-COMM-E2P card.

4.6 Configuration of parameters for Ethernet communication. For the communication of the PF525 through the embedded EIP port.

4.7 Parameter setting for control mode: Speed.

4.8 Parameter setting for control mode: Position.

Step 5: Program download and commissioning

5.1 Compile the Micro800 program.

5.2 Validate PV800 application.

5.3 Verify the right connection and IP assignment of the equipment in the Ethernet IP network.

5.4 Download program (without errors) to Micro800 controller and leave in run mode.

5.5 Download the HMI application to the PV800 and execute it.

Simple On-Off Control for First Orders and Overdamped Systems Bang-Bang Control: an easy to program and calibrate first order plant control when output of the system is on-off actuator.

What is this for?

The objective of this document is to present an easy to program and calibrate first order plant control when output of the system is on-off actuator. This algorithm is based on Bang-Bang Control which uses hysteresis to turn on and off the output of the control with an enhancement of a first order filter in an inner feedback loop to increase modulation of the output.

The type of outputs that this control may drive are:

- Solenoid Valves.

- Motorized Valves with 2 positions (Open/Close).

1. Solid State Relays (To drive heating resistors).

2. Electromechanical Contactors.

This solution has been tested in physical thermal heating and heating/cooling systems described in the tools and prerequisites section (see below) as the test equipment, and level control systems (Tested in industrial system not shown here) where we have inlet and outlet flow.

Is this useful for me?

The bang-bang principle of operation is the on/off control with hysteresis, but we have added a feedback inner loop at the on/off output through a first order filter. 

The ultimate effect of the Feedback First Order filter in the Bang-Bang Control is to compensate for the dead time it takes between from the actuator that affects the measured variable and the sensor to report actual measurement. 

With the feedback filter, the oscillation at the control output will begin earlier than if it only had the hysteresis comparator hence limiting the amount of heat deliver to the tank helping to avoid overshoot as the heated liquid arrives to the sensor.

This algorithm can replace a Proportional-Integral control loop that needs to be connected to a time proportional output, it is simpler to tune and has less parameters to setup.

Note: We suggest using this algorithm for first order systems and only critically damped and overdamped (ζ≥1) second order systems. Undamped system may produce undesirable oscillations that may have unexpected behavior.

How can I make it work?

Previous knowledge:

• Enhanced Bang-Bang Algorithm theory of operation.
• Definition of a First Order and Second Order Critically Damped or Overdamped System.

(Full document available here)

The block diagram for the enhanced Bang-Bang control algorithm is shown in Figure 1:

The bang-bang principle of operation is the on/off control with hysteresis, as the diagram shows the system will turn on when the input [e2] is greater than H but, it will hold on until [e2] is less than L. 

Normally this is all the bang-bang functionality, but we have added a feedback inner loop at the on/off output through a first order filter. This filter is implemented mathematically in the algorithm. 

This first order filter (FOF) will receive the status of the bang-bang (BB) (hysteresis) output block that is a 1 (one) or 0 (cero) depending if the output is on or off. The result will be a capacitance charge or discharge depending on the state of the Bang-Bang block output. The tendence of the FOF output will be K when the BB output is on and will tend to cero when the output is off.

The output of the FOF is subtracted of the error [e] producing a reduced [e2] that will tend to K, this means that when the error (e=SP-PV) is greater for enough time, e2 will tend to e-Kr, therefore e2 will be greater than H turning the output of the BB to on.

The final control element will stay open until the plant reaches the difference stated by e2 ≤ L the output of the BB will turn off even when the plant has not yet reached the Setpoint, but then the feedback filter will begin a discharge provoking an increase on e2. The discharge will continue until e2 reaches H that will turn again the output of BB.

The process will continue to cycle between on/off until the PV reaches SP.

Tunning the Bang-Bang

Tunning method is quite intuitive. But is best to begin with small gain in the feedback filter and few units of error to turn on the control and few units to turn off the control. It can begin centered over cero. For example, start with [H = 0.5% of the control variable] and [L=- 0.5% of the control variable]. Make K=0 to see how the system reacts to a pure bang-bang.

The sample time should be equal to the periodic function call for the Bang-Bang function. This parameter is important because it will determine the system timing for the following steps.

Check the overshoot after the system stabilizes, make [K] equal to overshoot and [Tao] equal to the dead time (t0) to estimate this time (does not have to be precise) measure the time between the output of the actuator activates and when you can see a perceivable change of 0.5% in the control variable. 

This will set up the Bang-Bang for the first pass tunning. 

By observing the system capacity, you may reduce the gap between [H] and [L] to reduce magnitude of the fluctuations around the set point [SP].

You can also reduce or increase the on/off period by modifying [Tao] on the control. This will enhance the precision of the system output but will create and increase of on/off cycles in the actuator.

Be aware that if the actuator has a mechanical operation such as a relay, contactor or solenoid valve, the life of the actuator will be inverse of the number of on/off cycles, so you will need to make a trade off among life of the actuator and precision of the control.

Cooling Bang-Bang (Actuator to decrease the control variable)

The algorithm to decrease the control variable such as cooling in a heated tank or pressure release valve in a pressure tank is very similar to the heating diagram but with some changes as shown in figure 2:

The difference in the algorithm is that the decrease output is multiplied by -1 before feeding the input of the inner loop filter. The control different parameters, now the hysteresis turns on the decrease actuator when the e2 is less than de SP at DecON point and will turn off the decrease actuator when the e2 is greater than DecOFF point.

Heating and cooling Bang-Bang

The last case for Bang-Bang is when you have both actuators for the same system, this is the case of application such as chrome plating or galvanizing where the systems need to be at a certain temperature to begin the process but once the process is in operation, the process generates more heat due to the electro plating current and hence needs to be cooled.

In this case we need to use the Bang-Bang in dual mode as shown in figure 3:

As you can see in figure 8, we have 2 hysteresis, one to drive the increase actuator and one to drive the decrease actuator. The key to tune this option is to make sure that the [DecON] parameter is always less than the [IncOn] and is preferable that the off point of both parameters does not cross each other. Is preferable that both hysteresis are set up as mutually exclusive.

Tools & prerequisites

Software:

• Studio 5000 Logix Designer v35.
• FactoryTalk View ME v12.00.00.

Hardware:

• ControlLogix Logix (1756-L83) FW v35.
• CompactLogix I/O Adapter (5069-AEN2TR).
• CompactLogix Universal Analog Input Card (5069-IY4).
• CompactLogix 16 24VDC output card (5069-OB16F).
• PanelView Plus 7 Performance 700 (2711P-T7C22A9P).

Test System Components:

• 1 Pc 8 liters aquarium.
• 1 pc RTD PT100 Temperature Sensor.
• 1 pc Solid State Relay 24 VDC input coil / 125 VAC output.
• 1 pc 400 watts heating resistor.

Files:

• BB.acd Logix Designer Addon Instruction

Inputs & Outputs for the testing system.

The input outputs used are:

• 1 PT100 RTD temperature sensor connected to Remote Compact I/O input in slot 3 input 0 (5069-IY4). Controller tag: Compact_Ethernet_Adapter:3:I.Ch00.Data.
• 2 DC output connected to 24 DC output card in Remote Compact I/O in slot 2 output 0 & 1. Compact_Ethernet_Adapter:2:O.Pt00.Data & Compact_Ethernet_Adapter:2:O.Pt01.Data.

Bang-Bang Add On Instruction (AOI).

The Bang-Bang Add On Instruction contains the instruction parameters, input variables and output variables to make the control work as well as the logic. The parameters that are input and output are shown in the faceplate made for Panelview Plus 7.

AOI Structure

The AOI instruction has a defined data type to name each control system by its unique name. In the case of this example the name of the system is “Acuarium” that has the {aoi_Bang_Bang} data type.

Enable/Disable Parameters:

Parameter List and description.

[BB_is_ON] Boolean input variable to turn the control to ON or OFF.

[Has_inc_element] Boolean input to indicate if control has variable increase actuator.

[Has_dec_element] Boolean input to indicate if control has variable decrease actuator.

Operation parameters:

[PV] Process variable: This is a real floating-point parameter. You should assign the scaled variable of the input card to this variable.

[SP] Set Point: This is a real floating-point parameter. This variable will be set in the HMI or any input device that sets the reference for the control.

Calibration parameters:

[Inc_On] Real floating-point parameter. This is part of the hysteresis of the Bang-Bang that if the input error to the hysteresis greater than this value, the output to the increase the control variable is turned on.

[Inc_Off] Real floating-point parameter. This is part of the hysteresis of the Bang-Bang that if the input error to the hysteresis is less than this value, the output to the increase the control variable is turned off.

[Dec_On] Real floating-point parameter. This is part of the hysteresis of the Bang-Bang that if the input error to the hysteresis is less than this value, the output to the decrease the control variable is turned on.

[Dec_Off] Real floating-point parameter. This is part of the hysteresis of the Bang-Bang that if the input error to the hysteresis is greater than this value, the output to the decrease the control variable is turned off.

[tsample] Real floating-point parameter. This parameter should be equal to the time defined for the scan time of the periodic task for the Bang-Bang.

[Tao] Real floating-point parameter. This is the time constant in seconds for the first order filter at the inner loop feedback.

[K] Real floating-point parameter. This is the gain that the output of the first order system will tend after long period of time (normally 7 times Tao). If K = 3, then after 7 times Tao, the filter output will be near 3.

Monitoring Parameters

[e] Real floating-point variable. This indicates the difference between the setpoint and the process variable ([e] = [SP] – [PV]).

[e2] Real floating-point variable. Is the difference between the error [e] and the output of the first order filter [FB_Filter_Out].

[FB_Filter_In] Real floating-point variable. Is the input to the feedback filter which is the result of adding [INC_OUT] – [DEC_OUT] output parameters. These parameters are the actual outputs to actuator elements. Because [INC_OUT] and [DEC_OUT] parameters are Boolean, to add these parameters is required to use integer variables before assigning to the Filter input.

[FB_Filter_Out] Real floating-point variable. Is the output of the feedback filter which is the result of the digitalization of the transfer function of a first order system. For simplification purposes, the first order differential equation is transformed to digital sampling with Euler method.

The filter equation is as follows:

Output Parameters

[INC_OUT] Boolean Output Parameter. This is the output that must be connected to the output card to drive the Increase control variable actuator.

[DEC_OUT] Boolean Output Parameter. This is the output that must be connected to the output card to drive the decrease control variable actuator.

AOI internal variables

The Add On Instruction has other internal variables required to execute the instruction such as conversion from Boolean to Integer. We will not describe each of these variables in this document as the AOI instruction is open for reviewing and editing.

Panelview plus 7 screens

Panelview 7 machine edition screen is provided as face plate for the Bang-Bang Control.

The face plate is provided as a sample for a system and is included in the documentation package.

Previous Knowledge

Definition of a First Order and Second Order Critically Damped or Overdamped System. You can find the complete document here.

Downloads

Please note: You will need to agree to the Terms & Conditions for each download.

Need Help?

If you need help with an application or have feedback from the Innovation Center, please contact us.

Installation Guide 

To implement the Add On Instruction check the following steps.

Studio 5000 AOI

Step 1:

Extract files from BB.ZIP into your working directory

Step 2:

Open file BB.acd into Studio 5000

Step 3:

Open the project where you want to use the Bang-Bang (it is assumed that the I/O mapping of your project is already done).

Step 4:

Highlight Select the aoi_Bang_Bang instruction under Assets menu in the controller organizer section of the Logix Designer.

Step 5:

Right click the mouse and select Copy as shown if Figure.

Step 6:

Go to the program you want to use the Bang-Bang and under Assets, highlight select the folder Add-On Instructions.

Step 7:

Verify that your target program has the new pasted AOI and under data type you should also have a new structure under Add-On-Defined.

Step 8:

Create a periodic task where you want to use the Bang-Bang Control or copy and paste the sample task from the BB.acd program. If you choose to copy the periodic task it must be done in 2 steps:

a. Select the Bang_Bang (10ms) Task, right click the mouse button and select copy.

b. Go to your target program and under Task folder right click select paste. The periodic task will be created in the target program.

c. From the BB.acd program under Bang_Bang (10ms) task right click select the BB_Logic routine and select copy.

d. In the target program select Bang_Bang (10ms) and right click to paste the logic.

Step 9:

Under Controller Tags define a new variable “Acuarium” (because this is the name of the system in the BB_Logic routine.

Step 10:

In the BB_Logic routine in the program named {IOAssignments_n_Scaling}, change the I/O Analog Input Address to match your project. Also change the Digital output to the Control Actuators to match your project.

Step 11:

Your Bang-Bang should be ready to work in your target program.

View Studio ME

To use the template for PanelView Plus 7 Performance, you will need to recover the project from the .mer file into the Studio 5000 View ME. 

Step 12:

From the zip file unzip the file named PV7P_BB.mer (Remember this file is in version 12 for ViewME).

Step 13:

Use Factory Talk ViewME Application Manager from the tools menu within the FactoryTalk ViewME application.  

Step 14:

Select “Restore runtime application.”

Step 15:

Select the file BB.mer file.

Step 16:

Select Open application and the application should be restored.

You can also find many videos on how to restore a .mer application to recover

MQTT Data Exchange: Real-Time Dashboard & Historical Data Guide on MQTT for data exchange between applications, focusing on real-time visualization and historical data, with setup steps for deployment.

What is this for?

Demo MQTT is an example consisting of two projects: Field Application and Data Aggregator Application. The objective of this demo is to simply show an example of communication via MQTT protocol between a hypothetical application running on a machine/plant (Field Application) and an application that collects the data sent by the machine, showing them in the form of a dashboard (Data Aggregator Application). Usually, it would be done only with the visualization of historical data (cold data) but in this project, we also wanted to show an example of receiving live data.

Use MQTT for real-time data visualization and communication between applications, emphasizing safety and practical implementation using FT Optix.

General Features

MQTT for real-time communication between field and data aggregator applications, with a focus on practical setup and safety. 

Limitations/Disadvantages

The example is provided as-is and can be a useful reference for building your application. The example as its cannot be used on a real machine but must be adapted for the purpose, respecting the highest safety standards required. A public and open source MQTT broker is used in the project for demonstration purposes only, it is not secured, and its uptime can’t be guaranteed. We strongly encourage you to change the topic and server names using your provider before deploying the final application.

How to start the project?

To setup the Field Application and/or to solve compiling issues/missed references please read the MQTT_Field documentation.

Please note:

This application works paired with the Field Application, showing data received via MQTT protocol in form of a control dashboard. This app you can find in the Innovation Center under the following tittle: Real-Time Data Implementation and Visualization with MQTT in Optix.

Downloads

Please note: You will need to agree to the Terms & Conditions for each download.

Need Help?

If you need help with an application or have feedback from the Innovation Center, please contact us.

Guía de implementación

Paso 1

Start the Field Application.

Paso 2:

After that, open this project on another FT Optix window and run the application with FT Optix Emulator.

Paso 3:

If the connection with the Field Application is working, the “Live Data” LED will be green.

Detailed information

The data exchange is based on a Runtime Netlogic which can be found in the Netlogic folder. The Netlogic MQTTBrokerLogic is present on both applications but is configured differently.

Field application

Here the Runtime Netlogic acts as Publisher, in this way it publishes data on certain topics, addressed to an MQTT broker.

Data aggregator application

Here the Runtime Netlogic works as Subscriber: subscribing to the topics on which the Field Application publishes, it shows all data in the form of a dashboard.

MQTT BrokerLogic

Server MQTT

Debe activarse (TRUE) solo si desea utilizar su aplicación Uniqo como Broker (por lo tanto, no usar un broker MQTT existente, en este ejemplo test.mosquitto.org).

Parameters:

• IPAddress: IP address where the Broker will be instantiated.
• Port: number of the port on which the broker is listening
• UseSSL: enables the use of certificates.
• Certificate
• CertificatePassword
• AutoStart LEAVE TRUE
• UserAuthentication: if true only the specified users can access
• AuthorizedUsers
• IsRunning: Server status
• IsDebuggingMode NOT USED
• MaxNumberOfConnections: maximum number of clients that can connect to the Broker
• NumberOfConnections: number of active connections

MQTT Client

It must always be active (TRUE) because it is the connection with the Broker to which you publish or to which you subscribe. If you want to connect two applications, you need to set the same broker and the same port on both projects. Instead, the ClientID parameter must be different (unique) on each application.

Parameters:

• IPAddress: broker address (test.mosquitto.org) could be external like in this case, or internal if the application work as a broker (e.g., MQTTBrokerLogic.MQTTServer.IPAddress)
• Port: broker port (1883 for test.mosquitto.org)
• UseSSL: Switch to TRUE if the broker requires certificates
  • CaCertificate
  • ClientCertificate
  • ClientCertificatePassword
  • AllowUntrustedCertificates
• UserAuthentication: Switch to TRUE if the broker requires authorized users.
  • AuthorizedUsers: String array which contains Uniqo users (User1; User2; User […]);
• IsRunning NOT USED
• IsDebuggingMode NOT USED
• ClientId: this is the unique Id, different for each application that wants to participate in the data sharing/exchange
• Connected: connection status to the broker
• SentPackages STATS
• ReceivedPackages STATS

Subscriber

It must be active (TRUE) if your application needs to receive data published on the broker.

Parameters:

• LiveTags: TRUE = receive LIVE DATA
  • LiveTagsFolder: this folder/Node contains a copy of the Publisher LiveTagsFolder parameter, on which the Netlogic will copy the values read from the broker.
  • LiveTagsTopic: on this parameter needs to be specified the topic on which you are subscribed, and you want to receive live variables/tags values.
  • LastPackageTimestamp: Timestamp of the last published packet
• StoreTables: TRUE = receive HISTORICAL DATA
  • Store: DataStore on which we are saving received data. The store’s tables must be renamed with the “TablesPrefix” parameter, plus the name of the publisher application tables. Below is an example:
    • Publisher application DataStore table names: Datalogger, AlarmsEventLogger
    • Publisher “TablesPrefix” parameter: Station1
    • Subscriber application DataStore table names: Station1_DataLogger, Station1_EventLogger Verify to have the same columns you have on the Publisher application.
  • StoreTablesTopic: on this parameter needs to be specified the topic on which you are subscribed, and you want to receive historical variables/tags values.
• CustomPayload: Custom message without pre-defined format
  • CustomPayloadMessage: Custom text message from the CustomPayloadTopic
  • CustomPayloadTopic: On this parameter the topic on which you are subscribed, and you want to receive custom messages needs to be specified.

Publisher

It must be active (TRUE) if your application needs to publish data to the broker.

Parameters:

• LiveTags: TRUE = publish LIVE DATA
  • LiveTagsPeriod: Sending frequency (if 0000:00:00.000 send data on value change).
  • LiveTagsFolder: folder (or node) that contains data to be sended
  • LiveTagsTopic: /UniqoFieldHmiLiveTopic is the topic on which we are sending/publishing data
  • QoS: MQTT Quality of Service (0,1,2)
  • Retain: Retain message on the topic even after read
• StoreTables: TRUE = publish HISTORICAL DATA
  • Store: DataStore on which we are saving our data
  • TableNames: Store tables to be sended
    • Table1: Datalogger
    • Table2: AlarmsEventLogger
    • Table (…) could be added or removed
  • PreserveData NOT USED
  • MaximumItemsPerPacket: define how many rows per packet to send
  • MaximumPublishTime: Maximum waiting time before publishing data even if it does not reach the MaximumItemsPerPacket value.
  • MinimumPublishTime: Minimum waiting time before publishing data when the MaximumItemsPerPacket value is reached.
  • StoreTablesTopic : /UniqoFieldHmiDataLoggerTopic is the topic on which we are sending/publishing data
  • QoS: MQTT Quality of Service (0,1,2)
  • Retain: Retain message on the topic even after read
  • TablesPrefix: A model variable containing the hypothetical name of different production sites, in this case, will be “Station1”. Into the sent packet will appear the table sent with the unique prefix corresponding to the right machine/site from which the packet arrives (Station1_AlarmsEventLogger). This is useful when we have more than one of the same machine models/more than one of the same plant configurations and we need to distinguish from which machine/plant data arrives.
• AllRows: When it is TRUE, publish all the data already present in the Store Tables. Set on FALSE to publish only the data stored after the implementation of the MQTTBrokerLogic.
• CustomPayload: Custom message without pre-defined format
  • CustomPayloadMessage: Custom text message published to the CustomPayloadTopic
  • CustomPayloadTopic: The topic on which the message will be published.
  • CustomPayloadPeriod: Sending frequency of the custom message (if 0000:00:00.000 send data on value change)
  • QoS: MQTT Quality of Service (0,1,2)
  • Retain: Retain message on the topic even after read

Boiler Efficiency Library A library to measure the efficiency of a boiler in real time using existing instrumentation in an Allen Bradley control system.

What is this for?

The objective of creating a standard Boiler Efficiency library is to gather knowledge from experience and applications utilizing the best approaches to provide features that will be selected based on the detailed requirements of the project scope.  Control, process design, and the configuration approach will utilize a PlantPAx based control system that will be used with standard Boiler Efficiency applications.  It is also desired for the controller to be flexible and allow integration of custom requirements and expansion as future technological developments are realized through industries.

The vision is to allow the user to select specific requirements and procedures, including and configuration capabilities, to meet the needs of the required mixing application. 

Is this useful for me?

Currently, there is no way to calculate Boiler Efficiency in a standardized way. A standard library with flexibility allows for the same basic building blocks to be utilized.

By standardizing the Boiler Efficiency library, it may be used for multiple industries (F&B, Chem, Life Science, Home & Personal Care) across the globe.  This standard will also be able to assist in cost benefit to the organization by lowering the engineer labor to create basic functionality.

Capturing of industry specific knowledge. Future go-to-market features for sales of Plant Pax application. Financial and labor savings are unknown currently.  However, reduced development time is expected due to the ability of tool to create basic functionality.

How can I make it work?

User will enter Boiler system inputs based on standard instrumentation typically used in Boilers.

This first version allows you to have real time efficiency in a Rockwell Automation control system, just import and configure the AOI and the Display, add it in your application and that's it.

System requirements of app:

Item	Requirement	Version
1	Tool will be built using Steam properties libraries of PlantPAx	4.x – 5.x
2	FactoryTalk View SE/ME	12.00
3	Studio 5000	21 and above

Process variables will need to be able to be configured including input signal, scaling, and units.

Item	Instrumentation
Temperature (Steam and Water)	Type: Resistance - RTD with common ranges configurable (PT100, PT1000, etc.) with configurable units: degK, degC, degF mV - Thermocouple with all types for temperature ranges (Type J, Type K, etc.) with configurable and units: degK, degC, degF Analog - analog input signal, with scalable engineering units, with configurable units: degK, degC, degF Digital - networked device, ethernet I/P, profibus, ASi, etc. with configurable units: degK, degC, degFTool will be built using Steam properties libraries of PlantPAx
Flow (Steam, Water, Fuel)	Type: Analog - analog input signal, with scalable engineering units, with configurable units: gpm, gpm, lpm, lph, m3h, kgh, etc. Digital - networked device, ethernet I/P, profibus, ASi, etc. with configurable units: gpm, gpm, lpm, lph, m3h, kgh, etc.
Pressure (Steam, Water)	Type: Analog - analog input signal, with scalable engineering units, with configurable units PSI, MPa, etc. Digital - networked device, Ethernet I/P, Profibus, ASi, etc with configurable units: PSI, MPa, etc.

Knowledge required

Basic knowledge of programming and configuration in Studio 5000 Logix Designer® software and FactoryTalk® View Site Edition Studio.

Downloads

Please note: You will need to agree to the Terms & Conditions for each download.

Need Help?

If you need help with an application or have feedback from the Innovation Center, please contact us.

Installation Guide 

Step 1:

1. Import file L5X for routine according with the programing language to use:

• Calc_Boiler_Efficiency_FB_Routine_FBD. L5X for Function Block.
• Calc_Boiler_Efficiency_LD_Routine_RLL.L5X for Ladder.

Note: Please read the instructions in the program comments

Step 2

Import the Global Object in FTView SE Application.

• Boiler efficiency.ggfx.