Archestra could not resolve reference

Adam Bullen

Member
Join Date
May 2012
Location
Taupo
Posts
11
Hi Guys;


I am getting this error when I try to reference anything in my template with a different reference then the name of the IO attribute.


I am talking via the ABCIP driver to a ControlLogix PLC. This is an existing plant with an existing InTouch application that we are going to migrate to Archestra Graphics. I am working on a test platform; one issue I have is that a reference with a different IO name doesn't work.


e.g. Archestra won't resolve attribute "MotorAlarm" as <iodevice>.$Motor.InAlarm since "InAlarm" is a reserved field; this is an issue for me. There are a few motors in the plant where an alarm not in the motor UDDT will cause the motor to be "InAlarm" this is handled in the PLC.



I decided to test this further we have a basic AlarmStd UDDT with Alarm; Ack; Delay and SP.


Archestra will resolve just fine if the attribute is called Delay.ACC -> "<IOdevice>.$AlarmStd.Delay.ACC"; but if I change the name to Elapsed with the same IO path it doesn't work any more.


Can someone help me out here as to why this is.
 

Similar Topics

Using: Wonderware System Plataform 3.0 SP2; Intouch 10 SP2. I used the Archestra to create objects using a script to automatically assign object...
Replies
0
Views
8,148
Dear All, We are designing a solution with 1756-L74 and Archestra. We need to use SOE to show on HMI. Please mention any solution if someone did...
Replies
0
Views
125
So I'm trying to enable history for a tag that is being used to display PPH on InTouch. I was able to locate the tagPath by finding the display...
Replies
2
Views
628
Got myself into a bit of a jam this AM. Somehow the graphic editor hiccupped and when I went back into my graphic, everything was gone. I...
Replies
1
Views
1,040
It's a while since I had used this that I forget where the setting to enable/disable object security is. There are some devices (pumps/valves)...
Replies
1
Views
835
Back
Top Bottom