How To Check Your RSLinx Enterprise Shortcut on a PanelView Plus

TAS_Banner_PVP_A



PanelView Plus 400 and 600So you're on the plant floor with your new PanelView Plus runtime file (.MER) freshly downloaded and your screen is showing the tell tale signs that theirs no communication.

If you like many people, sometime during the development cycle you learn how to disable the “information” pop-up window.

Unfortunately, that same window you disabled in testing would be really handy right now as it would likely tell you exactly what was going wrong.

However, it's a good be your RSLinx Enterprise Target tab configuration is incorrect, or your shortcut hasn't been applied to the PLC in your Target tab. To find out if that's the case, follow these steps:

1) Start by accessing the PanelView Plus Configuration Mode menu (for more information about this, check our this blog article HERE.)

2) With your application loaded (very important) select Application Settings:

PanelView Plus 6 600 Configuration Mode

3) Now select Device Shortcuts and press Enter:

PanelView Plus Application Settings

5) Highlight your PLC shortcut and press Enter. Hopefully you see your shortcut here – if you do not, then you either didn't load it or didn't create it in RSLinx Enterprise.

PanelView Plus Shortcuts

6) Now if your shortcut is setup correctly you will see your PLC Device highlighted as my SLC is below. If no device is highlighted, then you have not “applied” your shortcut to your PLC device in the Target tab in RSLinx Enterprise. If that is the case, you should be able to use the up/down arrow keys here to select the PLC Device, and press OK to assign it:

PanelView Plus Shortcut Config

I hope you've found this article about checking your PanelView Plus shortcut settings helpful. If you have any questions, comments, suggestions, or corrections, please don't hesitate to leave them by using the “post a comment or question” link below.

Sincerely,

Shawn Tierney
Automation Blogger and Trainer
If you enjoyed my article, you may like my affordable courses at TheAutomationSchool.com




Old Comment:

  1. Would this be the case if the shortcut appeared to work when testing on a laptop but not working when going to runtime?

  2. Good morning Steve,

    In short, yes.

    The most common reason for ViewME runtimes not communicating even though testing in ViewStudio does communicate is simply forgetting to setup the Target Tab config in RSLinx Enterprise. And in most of these cases you can just copy the Local Tab config to the Target Tab.

    Other reasons include not selecting the “replace communications” checkbox when transferring the file.

    In both the above situations you wouldn’t see a shortcut in step 6 above.

    For videos of setting up RSLinx Enterprise check out my flashback series currently running at http://www.TheAutomationMinute.com.

    Hope this helps,

    Shawn Tierney

    If you enjoyed reading my article you may also like my affordable training courses at TheAutomationSchool.com