I am using a Red Lion G310 display with the latest version of Crimson 3.0. I would like to use one display to represent multiple zones being controlled. Each zone has an AB Micrologix for its controller. Rather than making multiple duplicate screens, I want to replace the data source for the items on the screen on the fly. If you're familiar with how Parameter files work in AB FactoryTalk View Studio, that's what I'm trying to replicate. I thought I could do the following for the data source for display.Tag1:
switch (internal.zone)
{
case 1:
return zone1.Tag1;
break;
case 2:
return zone2.Tag1;
break;
case 3:
return zone3.Tag1;
break;
etc...
}
This works if all of the PLCs are enabled and communicating. If any of the PLCs are disabled or not communicating the code doesn't execute. There is no "run anyway" when using complex code as a data source.
Has anyone ever tried this? Is there a best practice way to do this other than copying every screen x times for the x zones of control?
switch (internal.zone)
{
case 1:
return zone1.Tag1;
break;
case 2:
return zone2.Tag1;
break;
case 3:
return zone3.Tag1;
break;
etc...
}
This works if all of the PLCs are enabled and communicating. If any of the PLCs are disabled or not communicating the code doesn't execute. There is no "run anyway" when using complex code as a data source.
Has anyone ever tried this? Is there a best practice way to do this other than copying every screen x times for the x zones of control?