engineering pushed a naming standard this week so the palletizer controller went from Palletizer to L3_PAL_01. 1769 L33ER, studio 5000 v32. i did the rename offline, downloaded it on the day shift, plc runs fine.
problem is the panelview plus 7 on that machine. every screen has the red x tag error boxes, numeric displays blank, buttons do nothing, and before the rename it was fine for years.
so i power cycled the terminal twice, nothing, then checked it can still ping the L33 at 192.168.10.21 and it can. opened the mer in view studio me v12 on the laptop after that and the tags all still say {::[PAL]Program:Main.Run_Cmd} style, so nothing changed there either.
do i have to re import every tag with the new controller name? theres a few hundred of them. any pointers before i start, id rather not do that on nights lol
Don't re-import anything.
Communication Setup in the project. What does the PAL shortcut point at on the Design tab, and on the Runtime tab? Is it browsed by the controller's name, or by the slot?
design tab shortcut PAL points at 192.168.10.21, backplane, 0, Palletizer. runtime tab same. the old name is still sat in the path, its greyed out in the tree though
The greyed out bit is the answer. The shortcut was saved with the browsed path ending in the old controller name. After the rename that hop is stale, so every tag under PAL fails. The tags reference the shortcut, the shortcut references the path. Only the name changed, so only the path needs fixing. In Communication Setup, Design tab, select PAL, browse to the L33ER again, it now shows as L3_PAL_01, click it, Apply. Do the same on the Runtime tab or use Copy from Design to Runtime. Then Create Runtime Application and load the new MER. No tag edits.
Someone did a decent article on how the shortcut sits between tags and the controller: https://plctr.com/introduction-to-hmi-human-machine-interface-in-plc-systems/
repointed on the design tab, test application on the laptop works now. rebuilt the mer, loaded it, terminal still all red x. not sure what i missed
You said you'd do the Runtime tab too. Did you?
Test Application uses Design, the terminal uses Runtime. I think that's all it is. Copy from Design to Runtime, Verify, then rebuild the MER again.
yep, missed the runtime tab. copied design to runtime, new mer, loaded it at 05:30 before days came in. every screen back.
so the whole thing was the shortcut path still ending in the old controller name. repointed it on both tabs, new mer, and not one tag edited, which i wasnt expecting when i posted.
thing i still dont get is why the path browses the L33 by name at all when the ip and slot are sitting right there. anyway.
thanks hannah and priya87
Glad it was only the path. Loading at 05:30 is dedication.