General Automation Discussion

[slac_guy]

Hello I am using Compactlogix L32E processor major revision 17.

I made a display using the the factory talk iew ME, and it runs successfully on the development PC, and updates all the tags from the PLC. I then created a .mer file and transferred it to the touchscreen, and tried running it from there. It is not able to update any of the tags on the touchscreen.

Is it my communication setup which is causing this to happen ? Also do I need a license for RSlinx Enterprise software for getting this to run on my touchscreen ?

Thanks,

slac_guy

[Ken_Roach]

You're on the right track.

In FTView Studio, when you browse for online tags or test-run a single Display, you are using the "Design(Local)" shortcut definition in RSLinx Enterprise.

When you perform a "Test Runtime" (the little running-man icon) or actually run FTView ME Runtime on your PC, you are using the Runtime(Target) shortcut definition.

It is very common to have the same route to the controller both online and offline, especially when you are using Ethernet both on your development PC and on the PanelView Plus terminal.   In those cases, just use the "Copy from Design to Runtime" button in RSLinx Enterprise to set up the Runtime(Target) shortcut.

When you download the *.MER file and run it on the PV+ terminal, the terminal will prompt you to replace the terminal's onboard RSLinx Enterprise communication configuration with the one in the *.MER.    Respond "Yes";  you want the configuration you just did in FTView Studio to be used by the PV+ terminal.

The FTView ME Runtime and RSLinx Enterprise licenses included in the PV+ hardware;  you never need to perform any licensing actions on the PV+ terminal.    You only need licenses when you use this software on a Windows computer instead of a PV+ terminal.

[slac_guy]

Hi Ken, 

Thanks a lot for your answer. The Ethernet Driver is working now. The tag values are getting updatedon the PV+ terminal from the PLC.

I also wanted to try the Serial driver. I configured the RSLinx Enterprise on my PC, and added a serial driver to it. When I run it on the PC, the tag values get updated. When I download it to the PV+ terminal, then it gives me an error saying that it cannot auto configure the COM1 port. It also gives me an error 2040101 [ CIP connection (0) open rejected.]

These errors werenot present when I ran it from the development PC.

Any ideas?

Thanks,

Slac_guy

[Ken_Roach]

Here's one important thing to check;  the RS-232 port on the PanelView Plus is a "DCE" type port, while all personal computers and all A-B controllers have "DTE" type ports.

To connect a DTE <-> DTE, you use a "null modem" cable.   The 1747-CP3 or 1756-CP3 or 1761-CBL-PM02 are all this type of cable.

To connect a DTE <-> DCE, you use a "straight through" cable.   Any general-purpose cable can be used.

So, if you are using the same cable to the PLC from the PV+ as you used on your computer, switch to a straight-through cable or add a Null-Modem Adapter.

[slac_guy · Accepted solution]

Hello Ken,

Thanks a lot. It never occured to me that it might be a straight cable instead of the null modem cable.

Thank you,

slac_guy

[slac_guy]

Hi Ken,

That woked. The tags are being updated serially now, from the PLC.

Thanks for your help.

slac_guy

[susi]

I think everyone really contribute very well to know about the runtime configuration. It helps me a lot to make it my job more easier about it. Thanks for providing with the full details.