Where is my panelview plus?

Patrick · May 24, 2007

Hi

When I run RSLinx AB_ETH-1, I can read everthing that is on Ethernet except for panelview plus. All the addresses will show including panelview plus at first, Then a red X will appear for panelview plus. I have RSStudio-ME But can not communicate from my desktop. With the laptop everything works fine. At the machine I'm plugging in thru a HUB.

This is the log from RSLinx on my desktop.

05/24/07 16:41:14 172.30.110.186 Attempting first connection, protocol = CSPv4
05/24/07 16:41:35 172.30.110.186 Unable to establish TCP connection to the Ethernet Interface
05/24/07 16:41:35 172.30.110.186 [10060] Connection timed out
05/24/07 16:41:35 172.30.110.186 CSPv4 connection lost; timed out on socket write

From the desktop I can communicate with the controller and 5 Frequency drives. But no Communications with the panelview.

Thank You

Ken Roach · May 24, 2007

Establish IP and Ethernet connectivity first

Since one computer works correctly and another one doesn't, the problem is either rudimentary IP addressing or firewalling.

First, establish that you have correctly configured the PanelView's IP address and subnet mask. Check those out on the PV+ terminal itself. Obviously it should be 172.30.110.186 as you have shown above. The subnet mask matters too.

Next use a Command window, type "IPCONFIG /ALL" to get the IP addressing of your computer. Post the results.

Next PING the address of the PanelView Plus terminal. Post the results.

Patrick · May 24, 2007

When i ping IPCONFIG /ALL. I get a ton of info but no addresses. This is a company network with all kinds of safe guards. When I ping 172.30.110.186. I get REquest time out. 4 times. When I ping the frequncy drive I get TTL expired in transit. When I ping the controller I get, Replys from Controllers address.

OZEE · May 24, 2007

You haven't answered all of Ken's questions. He's asked you some important questions in helping you to solve your problem. You've only answered his third question...

Since you're getting no response from the PVP, that indicates a network issue. Like Ken said, are you absolutely certain that the PVP has that IP address? How did you configure it (e.g., bootp)?

If your computer's IP and the PVP's IP aren't in the same subnet, they won't be able to communicate. So you're going to have to know your computer's IP. What kind of info are you getting from the ipconfig?

Ken Roach · May 24, 2007

By the way, Patrick, I'm the Rockwell Automation network and controller specialist who covers your area. Walt Brunner at Columbia Electric in Pasco is your local PLC guy from our distributor and is very good at this sort of thing.

If you'd like, give Walt a call or drop me an e-mail and we'll walk through this thing directly.

tomalbright · May 25, 2007

You might also try using the ETH-IP driver as well. I have found it makes a difference.

It does sound as if there is an IP config problem on your source computer, though.

Patrick · May 25, 2007

Morning

Ken we met a few years ago at an automation fair in Bellevue, WA. And Walt knows me quit well. I fact he blames part of his baldness on me.

I went out to the panelview plus to get the Ethernet info. The I.P. address that I enter was wrong. I had 172.30.110.180 instead of 172.30.110.186. This brings up a new question. How was it able to communicate with the CompactLogix if the address was wrong?

I should clarify that this machine was programmed at the factory and installed by their technician. The controller, frequency drives and panelview was all set up by them. After they left I changed the I.P. addresses so I could get some info for the scada system. This was the first time I ever worked with the CompactLogix and panelview plus. First time I worked with Ethernet. Walt set up a ControlLogix so I could change Ethernet to DH+.

I modified the panelview program for upstream and down stream info. So if all this time it had the wrong I.P. how did the panelview communicate with the controller?

This machine has been running like this since February. No complains from the operators about the panelview not working.

OZEE · May 25, 2007

As I read your OP, your question was related to not being able to get to the PVP from your PC. It sounds like everything else works amongst themselves, but not your PC.

To help you solve that problem, we still need you to provide us with some information about YOUR computer. You said you can't ping the PVP -- that indicates either a networking or a config problem. We can't help you fix that until you answer the questions both Ken and I have asked of you...

Although now that you know the real address of the PVP, can you ping it??

Patrick · May 25, 2007

Morning OZEE As stated in the last post by me I had the I.P. address set wrong. This I have corrected and I am able to ping the panelview and see it in RSLinx. My Question now is how did the panelview comunicate with the compactlogix if it had a wrong I.P. address all this time?

dmroeder · May 25, 2007

Patrick said:
Morning OZEE As stated in the last post by me I had the I.P. address set wrong. This I have corrected and I am able to ping the panelview and see it in RSLinx. My Question now is how did the panelview comunicate with the compactlogix if it had a wrong I.P. address all this time?

Because the panelview only cares what the IP of the CompactLotix is. As long as the panelview has an address in the same subnet (I think that's the right term), then it just looks for the tags at the Compact Logix address.

OZEE · May 25, 2007

In the PVP, you define the destination address in the communication. If the source (PVP) IP address was in the same subnet as the destination (PLC) address, then it doesn't matter what the actual addresses are.

The .180 and .186 addresses you gave are in the same subnet range. If the subnet itself was 255.255.255.0, then any 172.30.110.xxx could have successfully reached the PLC.

curlyandshemp · May 25, 2007

Patrick said:
Morning OZEE As stated in the last post by me I had the I.P. address set wrong. This I have corrected and I am able to ping the panelview and see it in RSLinx. My Question now is how did the panelview comunicate with the compactlogix if it had a wrong I.P. address all this time?

The PV+ and the PLC were on the same subnet, so as long as the PV+ had the correct PLC IP address, the PV+ would have no issue with communications. Your PC and the PV+ are on the same subnet, put your IP adress for the PV+ was wrong, that is why your PC could not ping the PV+

Ian

Ken Roach · May 25, 2007

The CompactLogix only responds to PV+ commands, and the "return address" is part of the packet, and the CompactLogix doesn't need to be configured to "know" the IP address of the PV+.

Patrick · May 25, 2007

Thank you for the insight on the interworkings of I.P addressing. I see i still have a lot of reading to do. The new addressing of compactlogix was easy to learn as compared to the understanding of the internet. Once again thank you. OH yes the subnet is set to 255.255.255.0

TonyShell · May 25, 2007

Can't see PV+?

Hi,

Maybe this will help. I had the same problem a while back. It drove me nuts! I was using RSLinx and couldn't see the PV+. As it turns out, RSLinx CAN'T see a PV+. According to Tech Support, only RSLinx Enterprise can see them. You have to do it in RSView Studio in the Communication Setup by browsing the Ethernet driver in the Local tab (I think). I hate to say this, but why? Why the poop did they make RSLinx so it could see everything BUT a PV+? Crazy, man! Are you using regular RSLinx Classic to try to see it? Not gonna happen. What were they thinking? Anyway, hope this helps.

Tony

Where is my panelview plus?

Patrick

Lifetime Supporting Member

Ken Roach

Lifetime Supporting Member + Moderator

Patrick

Lifetime Supporting Member

OZEE

Member

Ken Roach

Lifetime Supporting Member + Moderator

tomalbright

Member

Patrick

Lifetime Supporting Member

OZEE

Member

Patrick

Lifetime Supporting Member

dmroeder

Lifetime Supporting Member

OZEE

Member

curlyandshemp

Lifetime Supporting Member

Ken Roach

Lifetime Supporting Member + Moderator

Patrick

Lifetime Supporting Member

TonyShell

Member

Similar Topics