Emerson Exchange 365

VIM2 Field Device Setup - Switches and Adapters

I'm looking for input on the pros and cons of using unmanaged vs. managed switches in the VIM network. I have a VIM2 setup as a master and communication is ModbusTCP for all devices connected. For this application I currently have one switchconnected to the application station, VIM2, and a SignalFire wireless Gateway. I am looking to bring in two more devices to this VIM2 for which I need a second switch; a 4B Watchdog SuperElite and (3)Rosemount 5708 solid scanners running through a Chiyu BF-430 converter. These two additional devices are located in close proximity to each other next to a fiber patch panel where I have several spare fibers that will give me a direct shot down to the VIM2. Question is, would it be better to have the second switch as unmanaged, managed, or does it matter?

Also has anyone used or used something similar to ANYBUS X-gateway with communication protocols ModbusTCP client/EthernetIP adapter? I would like to test VFDs in our instrumentation shop using Ethernet/IP on a VIM2 that is loaded with Modbus driver; and was thinking of exploring this option.  

DV13.3

Thanks in advance

 

• network
• switch
• VIM
• VIM2
• converter
• adapter

csbenne

• 13 Aug 2017 4:31 AM
• Cancel

3 Replies

• fairchdm

  

  • 16 Aug 2017 1:38 PM

  I've had my VIM card installed for about six years now, currently running DV 13.3. I am communicating with Ethernet IP to several VFDs. I originally installed the VIM network with a Cisco 2960, but have tried different configurations with a Linksys unmanaged switch. I went back to the 2960 due to criticality of my VIM network. The Linksys worked fine but I like using the Cisco. I haven't "stacked" switches as you plan, but it shouldn't make much difference due to how Ethernet transfers data. As long as you do not create a "Loop" that might cause conflicts there shouldn't be an issue. The best thing you get with the managed switch is the ease of access and configuration options. The unmanaged switch is Plug and Play, but then you have to play by their rules. Best of Luck.

  • Cancel
• dave_marshall

  

  • 16 Aug 2017 2:40 PM

  I have several clients with VIM networks that stretch far across their facility. In almost all cases we have used unmanaged switches with great success. For older installations we have used the Cisco switches in an unmanaged state. For newer or retrofitted facilities, we use the Hirschmann MACH-102's because of the moderate cost and redundant power supplies.
  
  If I had one point that I would stress with you, it is to acquire a switch with dual power supplies. It really stinks when you have your VIM network drop because a power supply failed. If you do not like Hirschmann or if they are too pricey, there are a few other vendors who make dual power supply switches for a lower cost.
  
  I have had two scenarios when we configured our VIM switches to a managed mode. In one case, a customer wanted to subdivide the VIM network into VLANs. In the other case, we were connecting two networks together: one was a star topology and one was a ring topology. We had to enable STP to not crash the whole thing.
  
  If your network is a simple star or star type hybrid, I would go with unmanaged. Unless necessary, there is no need to make it complicated.
  
  To your second question, I have not used the Anybus adaptor series. Is there a way to get a MODBUS TCP option card for your VFD's instead? It is not helpful to have complexity added if you can help it.

  • Cancel
• csbenne

  

  • 24 Sep 2017 3:44 AM

  In reply to dave_marshall:

  Some time has passed now but just in case anyone comes across this thread; I had no issues at all stacking unmanaged switches on the VIM network. My facility is undergoing a migration right now to convert existing PLCs over to DeltaV. Older PLC5s are getting converted to Charms while a few ControlLogix will remain in place and simply be taken over with I/O mapped into DeltaV through VIM cards. As we move forward and the number of VIMs increase we will be using a VLAN as you mentioned to get back to our Application Station server, so thanks for the heads up on the spanning tree.

  • Cancel