rstech
Member
Hi everyone,
I have a problem with a new machine I programmed about a month ago. It is up and running but every day or two the PanelView decides to stop communicating with the PLC. When I've gone on-site I've found that I also cannot communicate very well with my laptop. What I mean by that is, I can see the processor in RSLinx but I can't go online (it times out), and when I ping from a command prompt my replies range from 200ms to 800ms to time outs. So there is some form of communication there, just not a good connection. If I cycle power to the PLC everything is back to normal. I can go online without any problem, the PanelView communicates and when I ping the response is <1ms every time.
Here are the hardware details. CompactLogix L32E with firmware 19.11, PanelViewPlus700 with firmware 5.10.06 and another integrator has a GuardLogix system that we are exchanging 5 words with (producer/consumer). Everything is going to a non-managed switch and the other integrator also has a PanelViewPlus and a Point I/O assembly.
While the equipment is running there doesn't appear to be a hold up in communication between my CompactLogix and the other integrator's GuardLogix. The machine runs as normal but on my PanelView we get the error bar at the top and the objects get the error messages and question marks in them. The problem seems to get progressively worse as time passes. When I leave the site everything is fine, the next day they start to notice the buttons acting really slow on the PanelView (15 seconds sometimes to actuate a button), and then several hours later it will periodically lose communication for several minutes at a time sometimes not recovering. Although I am getting some conflicting reports from the customer it sounds like the problem is usually cleared after cycling power.
I tried replacing the PanelView logic module and it made no difference. A week ago I replaced the CompactLogix processor and it made no difference. When I've been on-site and the PanelView has not communicated I have isolated everything else off the network and had just my laptop and PLC on the network and I still can't communicate with the PLC; not until I cycle the power. I even connected directly to the PLC to rule out the switch and cables. I contacted Rockwell Tech Support and they said to upgrade the firmware in the PanelView to the latest which I did this morning. So it went from 5.10.01 to 5.10.06. I'm skeptical about that solution which is why I'm posting here and hoping someone has some ideas.
A few other notes. The PLC and PanelView programs are not very big. There is plenty of memory available in both the PLC and PanelView. The temperature inside the panel does not seem to be a factor, doesn't feel unusually warm (plant is air conditioned). I've never set up produced/consumed tags before so I don't know if this is a factor. Seemed pretty straight forward and as I mentioned this part always seems to be working. I've worked extensively with Logix and PanelViewPlus systems and I've never seen an issue like this. Does anyone have an ideas or things I might try? Thanks.
I have a problem with a new machine I programmed about a month ago. It is up and running but every day or two the PanelView decides to stop communicating with the PLC. When I've gone on-site I've found that I also cannot communicate very well with my laptop. What I mean by that is, I can see the processor in RSLinx but I can't go online (it times out), and when I ping from a command prompt my replies range from 200ms to 800ms to time outs. So there is some form of communication there, just not a good connection. If I cycle power to the PLC everything is back to normal. I can go online without any problem, the PanelView communicates and when I ping the response is <1ms every time.
Here are the hardware details. CompactLogix L32E with firmware 19.11, PanelViewPlus700 with firmware 5.10.06 and another integrator has a GuardLogix system that we are exchanging 5 words with (producer/consumer). Everything is going to a non-managed switch and the other integrator also has a PanelViewPlus and a Point I/O assembly.
While the equipment is running there doesn't appear to be a hold up in communication between my CompactLogix and the other integrator's GuardLogix. The machine runs as normal but on my PanelView we get the error bar at the top and the objects get the error messages and question marks in them. The problem seems to get progressively worse as time passes. When I leave the site everything is fine, the next day they start to notice the buttons acting really slow on the PanelView (15 seconds sometimes to actuate a button), and then several hours later it will periodically lose communication for several minutes at a time sometimes not recovering. Although I am getting some conflicting reports from the customer it sounds like the problem is usually cleared after cycling power.
I tried replacing the PanelView logic module and it made no difference. A week ago I replaced the CompactLogix processor and it made no difference. When I've been on-site and the PanelView has not communicated I have isolated everything else off the network and had just my laptop and PLC on the network and I still can't communicate with the PLC; not until I cycle the power. I even connected directly to the PLC to rule out the switch and cables. I contacted Rockwell Tech Support and they said to upgrade the firmware in the PanelView to the latest which I did this morning. So it went from 5.10.01 to 5.10.06. I'm skeptical about that solution which is why I'm posting here and hoping someone has some ideas.
A few other notes. The PLC and PanelView programs are not very big. There is plenty of memory available in both the PLC and PanelView. The temperature inside the panel does not seem to be a factor, doesn't feel unusually warm (plant is air conditioned). I've never set up produced/consumed tags before so I don't know if this is a factor. Seemed pretty straight forward and as I mentioned this part always seems to be working. I've worked extensively with Logix and PanelViewPlus systems and I've never seen an issue like this. Does anyone have an ideas or things I might try? Thanks.