zenerdiode

MrPLC Member
  • Content count

    3
  • Joined

  • Last visited

Community Reputation

0 Neutral

About zenerdiode

  • Rank
    Hi, I am New!

Profile Information

  • Country Pakistan
  1. Issue with Allen Bradley PLC Modbus TCP IP

    @kaiser_will Thanks alot for your help. We disabled "Supervisor Mode" in the Ethernet Card settings and now the behaviour of the system is normal, the lights of the switches are blinking and the Instrument Air Compressor which was not pinging before, is pinging and giving data on Modbus TCP/IP. 
  2. Issue with Allen Bradley PLC Modbus TCP IP

    @kaiser_will Please if you can, go through the dropbox link, I have uploaded the architecture drawing of Over Head Compressor which contains complete information of the PLC and Cards used. And also the IP scheme of the complete network. We have already verified, there is not duplication of IPs in the network. We are also following up with the Vendor and have raised exactly the same concern. Maybe they would review their configurations in PLC for modbus. Analysing the Wire Shark capture, it clearly shows that the AB PLC is actually flooding the network with its packets.
  3. Dear Forum, I am working at a Gas Processing Plant which is running Emerson Delta Distributed Control System (DCS). The Control System is communicating with over 24 3rd party Packages in the field over Modbus TCP/IP using its VIM Module. We have implemented redundant communication with most of the packages so we have a primary switch and a secondary switch. We are facing a communication issue regarding an Over Head Compressor (using Rockwell Allen Bradley PLC) and Instrument Air Compressor by CAPS Australia running XE Controller (Dedicated Controller). The issue is that when the Over Head Compressor is plugged into the VIM Network (Network in which all 24 3rd Party Packages are plugged), the Instrument Air Compressor **stops communicating**. We can't even ping the compressor. At times the Instrument Air Compressor does reply but with TTL of over 30ms. When OVHD Compressor is plugged out, Instrument Air Compressor resumes communication. I have attached wire shark capture of the network with and without over head compressor. When the OVHD Compressor is plugged in, the capture shows heavy traffic being generated by its PLC (IP address 192.168.1.60). Another physical observation is that before the OVHD Compressor is plugged in the VIM Network, the NTRON Switch (Ethernet Switch) in OVHD Compressor panel shows static lights, unlike lights of a normal healthy network. When the OVHD Compressor is plugged into the VIM Network, all the lights of switches in VIM Network which were blinking previously also become static. Do the static lights mean that the network is being choked due to heavy traffic? Below are links for the Capture, IP Scheme and Architecture of Over Head Compressor. https://www.dropbox.com/sh/ar7ss8zzoo96g37/AAADguRpUDtdOnmN3xQX-Wlpa?dl=0 Please also note that OVHD Compressor is using following IPs 192.168.1.59  PLC (Internal PLC IP) 192.168.1.60  PLC (Internal PLC IP) 192.168.1.61  HMI (Internal PLC IP) 192.168.1.62  RedLion device for DCS Communication I would really appreciate if anyone would help me trouble shoot this issue.