Emerson Exchange 365

Update: Network Device Command Center - It does NOT need a module prebuilt

Update: Went ahead and commissioned the switches and the "wizard" creates the modules.

I'm ready to commission a switch using the "Network Device Command Center" in DeltaV 13.3, and it's prompting me for a "switch name" - name to be assigned to the switch module . . . must be a valid DeltaV module name.

I just wanted to confirm - I don't need to pre-build a module that this switch will point to, the command center "builds" it when the switch is commissioned. It just needs a valid module name. (A default or a suggestion would be helpful here).

(You don't . . . )

Thanks,

John

John Rezabek

• 11 Apr 2016 4:03 PM
• Cancel

5 Replies

• Matt Stoner

  

  • 11 Apr 2016 4:11 PM

  That is correct John (At least it was in v12, I haven't tested v13 but it should work the same)

  • Cancel
• Andre Dicaire

  

  • 11 Apr 2016 5:12 PM

  In reply to Matt Stoner:

  It is the same in v13. In v12, the application was called Smart Switch Command Center, and only supported Smart Switches on the DeltaV network.
  
  In v13, it is rebranded as the Network Command Center, and supports Smart Switches and the Perimeter Firewall connected to the multiple networks, including Remote Networks, Thin Client Networks and the 2.5 plant information network.
  
  When you commission a new switch, a new Switch Module will be created from the class modules provided with DeltaV. The name field appends the _$X suffix, with the complete name limited to 16 Characters. That gives you 13 characters to uniquely name the Switch. The module cannot exist in the database.

  Andre Dicaire

  • Cancel
• ryanscofield

  

  • 31 Jan 2018 8:28 PM

  In reply to Andre Dicaire:

  Can you clarify your comment that the module cannot exist in the database? Can it be exposed through the OPC server to pull the data into PI? Is the _$X suffix meaningful?

  • Cancel
• Alexandre Peixoto

  

  • 1 Feb 2018 1:11 PM

  In reply to ryanscofield:

  The Network Device Command Center will create modules in the DeltaV database, so you don't have to create them first. We don't support name duplicates in the system, but based on the "_$X" suffix is unlikely the match will occur, but the warning is valid (just in case). Once created, the module is accessible throughout the system as a standard DeltaV control module, so yes you can pull data into PI using OPC as an example.

  • Cancel
• Brent Hamilton

  

  • 13 Sep 2019 2:57 PM

  In reply to ryanscofield:

  I believe Andre's comment that "the module cannot exist in the database" was saying that you need a unique name for the switch since it will reside in the database as a Control Module once it's created.

  • Cancel