toddp65 said:
...WARNING: Device deletion detected. Shortcut name = "filler". Description: The system has detected that a device that was referenced by the noted shortcut has been deleted from the configuration...
Is your 1769-L32E controller still under the "EtherNet, Ethernet" driver on the Runtime (Target) tab? As you know, this is what your "filler" Shortcut should be assigned to...
...When I open the config and go to the runtime side, the right side already drills down to the actual L32E controller before I even click on the 'filler' shortcut so it appears if it's already points to the controller...
Don't just go by what is displayed when you open this tab. Remember I explained earlier how to quickly identify which device, if any, is assigned to a Shortcut? With the driver expanded as far as your controller, click on the driver instance (EtherNet, Ethernet) on the right side, not the controller. Then click on the Shortcut and the controller should automatically be highlighted (Blue) on the right side, "if" the Shortcut is currently assigned to the controller. If not, then tell us what, if anything, does highlight when you select the Shortcut? I mean tell us "exactly" what highlights, and not just "the controller" is highlighted, please. It is very important.
Also, use the Verify button to open the Shortcut Verifier window and see what it describes for the Runtime path. It should probably say something similar to the "deleted" warning, or at minimum that it is currently assigned no path. Again, be specific if describing it.
By the way, did you delete the PanelView Plus terminal instance under the
EtherNet, Ethernet driver?
If you find, one way or another, that the controller instance does not appear to be assigned to your Shortcut, then follow the steps we went over previously. Highlight the controller instance precisely, and not anything under it. Then highlight the Shortcut, and click "Apply". Use Verify again to check the Runtime path has now been assigned to a [Logix Device]. Then OK, close Communications Setup, save and attempt to compile once more.
I'm not going to get into what your screenshot of the current Shortcut configuration on the terminal shows, but it does somewhat indicate that what was configured in the application was as some point applied to the terminal by having selected replace communications.
If we get the application Shortcut sorted, and
do use replace communications, then it will overwrite all this on the terminal, so no need to zone in on it, for now.
It's a little frustrating, as 5 minutes in front of all this would most likely get it sorted, as opposed to all this typing. But alas, this is where we are, and it will do you no harm learning these things the "hard way".
Regards,
George