jfd7851
Member
Hello everyone,
I am using a Control Logix L73 controller, with a motor that runs on Ethernet IP protocol.
I currently have an AOI for a motor that is in structured text. The manufacturer of the motor allows you to download a data type off of their own software where the initial IP Address and settings are configured. The data type is limiting, as you have to choose what parameters to include on the data type and their are limited spaces.
To get more useful information out of this motor, I have been investigating using the MSG instructions (Get Attribute Single, CIP Generic) to pull the other data that wasn't included on the data type. I have been successful at doing this when the message is triggered and defined in a ladder logic sequence. My goal is to define the MSG instruction within a structured text environment so that after some development time it could be added into an AOI.
I understand that I can call a MSG instruction in structured text as MSG(Message Control Tag). I do not understand where within the MESSAGE datatype that the destination tag is defined (other than the configuration tab on the Ladder Logic instruction).
So far I have read the 'General Instructions Reference' multiple times, I've tried some 'hacky' methods to see if I could either :
a.) create the message instruction in a ladder logic script so that everything is defined and then delete the Ladder logic and call it from a structured text script.
b.) tried setting MSG(message control) = another tag in the environment and that did not work either.
I am using a Control Logix L73 controller, with a motor that runs on Ethernet IP protocol.
I currently have an AOI for a motor that is in structured text. The manufacturer of the motor allows you to download a data type off of their own software where the initial IP Address and settings are configured. The data type is limiting, as you have to choose what parameters to include on the data type and their are limited spaces.
To get more useful information out of this motor, I have been investigating using the MSG instructions (Get Attribute Single, CIP Generic) to pull the other data that wasn't included on the data type. I have been successful at doing this when the message is triggered and defined in a ladder logic sequence. My goal is to define the MSG instruction within a structured text environment so that after some development time it could be added into an AOI.
I understand that I can call a MSG instruction in structured text as MSG(Message Control Tag). I do not understand where within the MESSAGE datatype that the destination tag is defined (other than the configuration tab on the Ladder Logic instruction).
So far I have read the 'General Instructions Reference' multiple times, I've tried some 'hacky' methods to see if I could either :
a.) create the message instruction in a ladder logic script so that everything is defined and then delete the Ladder logic and call it from a structured text script.
b.) tried setting MSG(message control) = another tag in the environment and that did not work either.