Phoenix Contact USA

MrPLC Member
  • Content count

  • Joined

  • Last visited

Everything posted by Phoenix Contact USA

  1. Wirelss Modbus

    Homer, it is perfectly reasonable to convert this from a wired Modbus RTU to a wireless solution. To further Dan’s point it is important to consider two questions when exploring wireless: 1. How fast must the pulling rates be for Modbus (wireless will be slower than a wired configuration)? 2. What is the distance between the PLC’s (as this would determine what wireless technology to use)? Each wireless technology is suited for different data rates and distances. For example, WLAN is for a fast speed covering shorter distances. Trusted wireless is a 900MHz solution that is ideal for scada speeds at longer distances (3-20 miles).
  2. Industrial networks attacked by a custom-made virus

    In light of the recent Duqu worm ( ) I thought I would comment on this thread. In addition to the 8 security enhancers mentioned by Camel, a 9th point would be to implement sifts monitoring into your control system. Sifts monitoring will help detect any changes to the programs on Windows or Linux based devices. Unlike a virus or antivirus, it isn’t signature based therefore you don’t need to do daily updates to get new signature files. You can monitor multiple devices from a single security appliance. To find out more about how this could help prevent a Stuxnet variant account check out:
  3. Wireless programing

    Although this forum is from 2007, I ran across it and thought it would beneficial to expand on Chris’ point. Although Dlink works great, it is more of a residential wireless Ethernet device. It would be much more reliable to use an industrial rated radio like WLAN for such an application. There are several WLAN radios made for varying speeds and distances. In this particular situation, one radio should be configured as a client (“slave”) in the control cabinet and should be connected to a switch. An additional radio should be connected back to the main network and configured as an access point. In this configuration you can access your panels via a computer hardwired into your network or a laptop connected wirelessly to the access point. With this setup a user can download programs and get updates wirelessly to and from the PLC. Phoenix Contact offers several industrial WLAN products:
  4. Micrologix 1000 Modes

    As mentioned by Bob and Carlton, and in light of the recent duqu worm, it is extremely important to consider security when extablishing a system. A secure industrial router/industrial firewall is a must to protect your Industrial Ethernet network from unwanted and potentially dangerous traffic. MGuard is an ideal solution for higher level remote site security. To find out more about how this could help prevent a Stuxnet variant account check out:
  5. FUS060 HART -> Modbus converter

    Although this post is from 2010, I thought it would be beneficial to comment just in case anyone else had the same inquiry. AJ, I understand that you are looking for a HART gateway that converts to Modbus. Phoenix Contact does not offer this, however Endress+Hausers fieldgate seems to fit what you are looking for. In contrast, if you are looking for a wireless solution, Phoenix Contact does offer a solution using an adaptor and gateway. By adding a WirelessHART adaptor, the data can be sent over a WirelessHART network. A gateway can then be used to convert the WirelessHART to Modbus.
  6. Panel items organization tips

    Greg's comments were spot on. It is good to keep analog signals segregated from other devices because of noise. To add to his point, if you are looking for a simple and clean way to organize our system, it would be good to use system cabling with a ribbon cable to clean up your cabinet.
  7. Text Message from PLC

    Although texting and emailing are both reliable options, it is truly just a matter of preference as to which technology you use. After further exploring this application, it seems as though there are three reliable options: 1. Create a stand alone solution (no need for a PLC) by connecting an SMS relay directly to the sensor/device. A set point can be created in the SMS relay and if over the given value a text will be sent. 2. If a PLC is already implemented, the sensor/device can be connected to the PLC. When a signal is sent to the PLC the ouput will be sent to the input of the SMS relay. The input (SMS relay) will then send text messages based on the on/off of the relay. The SMS relay can also receive commands. As long as there is cell coverage, these are both very reliable options. 3. If looking to send notifications via email. A GSM modem can be used instead. A GSM modem, however will need a PLC in order to operate) For more information on these products visit:
  8. Redundancy causing network disruptions?

    Paul... Just came across this topic. You are reading it correctly and you are not alone. We have enhanced RST with a solution called “fast ring”. In the event that faster recovery is required, Phoenix Contact has optimized our managed switch line to better recover in just the scenario that you have described. "Fast Ring" allows us to recover both unicast traffic and multicast groups in approximately 200 ms or less even with extremely large topologies. Our solution also works in more than just a simple ring topology. For example, partial and full mesh, interlocking rings, etc. Phoenix Contact switches running fast ring can also interconnect with other STP capable switches on the IT side such as Cisco. For more technical details you can check out our product page: or call our free tech support at 800 322-3225.
  9. Ethernet through slip rings

    Something like the DX80 would be a solution if you were transmitting I/O, however, if you wanted to communicate ethernet data, you would have to use something like an industrial WLAN radio. It is important to consider a few things prior to choosing either solution: 1. How fast must the wireless be (since a wireless solution will be slower than a wired solution)? 2. What is the distance that must be covered by the wireless network? (as this would determine what wireless technology to use) For this application in particular, Bluetooth or Ethernet could be considered. Bluetooth is usually less expensive than Ethernet and runs at the same frequency. Bluetooth is also much faster. Phoenix Contact offers either solution. For more information please visit: or call our free tech support at 800 322-3225.
  10. Junction Box I/O Sequence (Best Practices)

    There really is no set standard when creating a junction box. It is important to do what makes the most logical sense for your particular application and shops. However, as Poovs said, with longer runs with analog you must be conscious of noise. If you have the opportunity a shielded cable should be used. It is important to consider how long your cable is run. Although voltage drop may be an issue, it is recommended that you don't go over a certain length of cable with analog signals.
  11. Interbus S Communication with Wonderware

    The RS232 port is a diagnostics port, however we would need to know a make and model number to determine if communications with Wonderware is possible using our OPC server.
  12. M23 19pos wiring

    Although this is an older post, I just came across it and thought I'd post the answer for anyone with a similar inquiry: Slot/position = pin = conductor color 1 / 4 (A) = 15 = WH 1 / 2 (B) = 7 = GY/PK 2 / 4 (A) = 5 = GN 2 / 2 (B) = 4 = RD/BU 3 / 4 (A) = 16 = YE 3 / 2 (B) = 8 = WH/GN 4 / 4 (A) = 3 = GY 4 / 2 (B) = 14 = BN/GN 5 / 4 (A) = 17 = PK 5 / 2 (B) = 9 = WH/YE 6 / 4 (A) = 2 = RD 6 / 2 (B) = 13 = YE/BN 7 / 4 (A) = 11 = BK 7 / 2 (B) = 10 = WH/GY 8 / 4 (A) = 1 = VT 8 / 2 (B) = 18 = GY/BN 1-8 / 1 (+ 120 V) = 19 = BN 1-8 / 3 (0 V) = 6 = BU 1-8 / 5 (PE) = 12 = GN/YE This may not be the industry standard, but this is what Phoenix Contact uses.
  13. Multiple Analog Signals

    When you say reduce the wiring, do you mean the wiring in a control cabinet or the wiring that goes out to a remote location? If you are looking to reduce the wiring out to a remote location, is there any existing infrastructure such as buried phone lines? For each of these instances there is a different solution that might be applicable (i.e, wireless or remote I/O).