Produced And Consumed Tags. Configuring Produced and Consumed Tags in RSLogix/Studio 5000 Implementing a Produced/Consumed data transfer between two controllers requires the creation of the relevant Data Type tags and the addition of both 'connected' CPUs within the 'IO Tree' of the 'corresponding' one. You will notice a few more options available for selection in this menu
Configuring Produced and Consumed Tags in RSLogix/Studio 5000 from www.solisplc.com
Produced/Consumed tags provide a mechanism for a processor to provide data to one or more other processors To create a Produced tag, create a new Controller Tag, give it a name and set the data type to.
Configuring Produced and Consumed Tags in RSLogix/Studio 5000
The Inter-Processor Communications analysis dashboard provides an overview of the produced and consumed tags in the project The Inter-Processor Communications analysis dashboard provides an overview of the produced and consumed tags in the project This method of using produced and consumed tags is considered a best practice for moving data between any of the Logix series controllers and is superior to the Messaging technique that was heavily used in the past
Data exchange between 2 Controllogix using produced and consumed tags. Getting the CIP Path correct can be tricky when you're using a version of RSLogix 5000 that doesn't know about modern built-in Ethernet ports. Only the tag names, data types, and CIP Path matter in Produced/Consumed Tags
Data exchange between 2 Controllogix using produced and consumed tags. In my opinion, Studio 5000 shouldn't even ask the model or firmware revision, because it doesn't use them for keying In the "producer drop-down menu," choose the PLC that will supply the produced tag created earlier