This technical note describes the recommended settings for integrating the PAC8000 Ethernet Bus Interface Module (EBIM) with a Modbus TCP Virtual IO Module 2 (VIM2). The EBIM is a rugged, field-mountable platform intended for remote I/O mounting in harsh and hazardous process applications. The PAC8000 GE Intelligent Platform configures both PAC8000 controllers and EBIMs.
1. Connecting the PAC8000 EBIM System to DeltaV
The DeltaV VIM2 provides a native DeltaV I/O interface to the PAC8000 Ethernet BIM via an open plant Ethernet network and Modbus TCP (RTU TCP) protocol. DeltaV controllers can read and write signals to the EBIMs residing on this Ethernet network. As such, the VIM2 exists as a Network Gateway between DeltaV controllers and the external EBIM nodes. This connectivity is illustrated below:
2. Installing and Starting the Software
Install the DeltaV software suite on the DeltaV PCs. Please consult Emerson Process Management if assistance is required with DeltaV installation and setup. After DeltaV is properly installed and licensed, proceed to install PAC8000 Control Center and VIMNet Explorer on the desired machine(s) residing on the open Ethernet network. The VIMNet Explorer utility used to configure the VIM2 can be located on the www.mynah.com licensing site page associated with the purchased firmware.
3. Assembling the Simplex Ethernet BIM Node
For this application note, a simplex EBIM was assembled with four IO modules. Two separate carriers are required; one carrier to host the EBIM and a second to host the IO modules. 12V DC Power is applied both to the EBIM carrier to supply power to IO modules and directly to the EBIM itself. The PAC8000 8913 AC-DC power supply was used as a source to both of these connections. Optionally, a power monitor module may be used in the left-most slot of the EBIM carrier. Please consult product datasheets for additional specification and requirements.
4. Configuring the EBIM System Using PAC8000 Control Center
Launch Workbench and start a new project. Assign a project name, select a save location and press "Apply."
Right-click on the Project folder and select "New Controller…" Assign a controller name, select "EBIM" and the appropriate firmware version, then press "Apply."
Configure the attributes tab with desired network settings, startup mode, carrier type, and other desired parameters. The Master IP Address is the IP address used by all external devices to communicate with the node and will only be answered by the current running master. The Direct A IP address is the IP Address to processor A. The Direct B IP address is the IP Address to processor B. All three IP addresses must always be assigned, even when a simplex node is used.
Right-click the EBIM in the tree and select "New Module." Create a Module corresponding to the Type on the carrier. Repeat for every module on the IO carrier.
Change the EBIM to Manual or Auto in order to download the configuration. Navigate to "Configuration->Download Controller."
Pending a mismatch in the IO, the modules should now all be in a running state. Modules Dynamic Data and Channel Dynamic Data can now be observed and Channel Attributes can be configured.
At this time, exit the 8000 IO Configurator. Tags can now be created and assigned to IO channels of the modules. Double-click "Controller Modules" under the EBIM on the Project Explorer tree to launch the tag assignment utility.
Proceed to create new tags for every signal. Repeat until a Tag is applied to every desired channel.
Once every Tag is created and assigned, proceed to Compile IO by right-clicking on the EBIM and select "Compile IO." Now, right-click on the EBIM and navigate to "Map Data->Build Register Mapping Table." Internal Modbus registers associated with the Tags are now visible in the *Map External Registers Table for EBIM on the Available Tags list located on the right-hand side of the window.
*Note: internal Modbus registers can be mapped to an external mapping table. However, a download of the EBIM is required to generate the table.
Furthermore, by selecting the "Launch 8000 IO Configurator" button, IO Tags can now be observed and assigned to each channel of the running modules.
The device is now configured as a remote IO node in the field residing on the device LAN. The internal Modbus addresses can now be read from and written to.
5. Configuring a VIM in VIMNet Explorer
Open VIMNet Explorer. Expand VIMNet and Physical Network until I/O Net is displayed, as in the image below. Right-click on I/O Net and select "New Controller."
A prompt will appear asking for a controller name. The name of the controller used in this example is shown below:
Expand I/O Net until the new controller (labeled “EBIM” in this example) is displayed. Right-click on the controller and select "New IO VIM."
A prompt will appear requesting specific configuration information about the new I/O VIM. For configuring the VIM to work with the EBIM node, enter a valid IP address on the device network and select the appropriate parameters based on the VIM type.
Expand the controller and the newly created I/O VIM, then expand C57 to show the two ports attached to Card 57. Right-click on P01 and select "Add Device."
Set the "Device Address" to the node address and the IP Address to the IP Address of the EBIM. If the IP Address is not displayed, click "Add" to create an IP Address - the value for this IP Address should match the one on the Direct A IP. After the IP Address is set, click "OK."
A new device should now appear under the first port of Card 57. This device is the Modbus TCP EBIM. VIMNet Explorer simply configures the VIM to map a DeltaV Device Address to an IP address in the field.
Right-click on the VIM placeholder under the EBIM controller node and select "Commission."
Select the VIM connected to the backplane containing the DeltaV controller and click "OK."
A blue arrow will appear next the VIM placeholder after it has been successfully commissioned. The arrow indicates that an upload is required to the VIM do to the difference between the VIMNet Explorer configuration and the running configuration in the VIM. Right-click on the VIM placeholder and select "Upload Configuration to VIM." After the upload is complete VIMNet should indicate a successful upload and the blue arrow should disappear.
VIMNet Explorer is now fully configured and the VIM can now map a DeltaV device to a field IP address.
6. Configuring a DeltaV Controller to Communicate to the EBIM
Launch DeltaV Explorer. Expand System Configuration, then expand Physical Network. Right-click on Control Network and select "New->Controller."
Give the controller a name, then right-click the controller and select "Commission." Select the controller from the decommissioned nodes list. If the controller does not appear on the decommissioned nodes list, please investigate the DeltaV network.
When prompted Auto-sense the I/O cards. The I/O card may be auto-sensed because we have already configured in the VIM in the previous section. If the DeltaV is configured before VIMNet the cards will need to be manually added or auto-sense later.
Expand C57, then right-click on P01 and select "Properties."
Check the Enable box for the port, then click "OK."
Right-click on P01 under C57 and select "New Serial Device."
Ensure that the "Device Address" parameter is set to the same node address assigned to the device in VIMNet Explorer.
Right-click DEV01 under P01 and select "New Dataset." A dataset will be created for each physical module IO module on the 8000 IO Module Carrier. DS01: DO1-DO8, DS02: DI1-DI8, DS03: AI1-AI8, DS04: AO1-AO8.
The following instructions are for configuring each of the datasets:
DS01 Properties Tabs:
DS02 Properties Tabs:
DS03 Properties Tabs:
DS04 Properties Tabs:
For more information on configuring a DeltaV dataset with Modbus TCP mappings, please consult the VIMNet Explorer Help Topics.
In this example, two modules are assigned to the DeltaV controller. The first landing module will read the input module channels, while the second module will write data to the output module channels. Landing modules should be created based on the standards of the DeltaV end-user.
Finally, right-click on the DeltaV controller and select "Download"; choose to download the whole controller.
DeltaV is now ready to communicate to the EBIM in the field. The IO has now been fully migrated from the channels on the modules to the EBIM across the Ethernet network via Modbus TCP to the MYNAH VIM card and presented to the DeltaV serial dataset channels.
390 South Woods Mill Road, Suite 100
Chesterfield, MO 63017 USA
+1 636 728 2000 (voice)
+1 636 728 2001 (fax)
MYNAH Technologies LLC
390 South Woods Mill Road, Suite 100
Chesterfield, MO 63017 USA
© MYNAH Technologies 2012 - 2020. All rights reserved.
Designs are marks of MYNAH Technologies, Emerson Process Management, DeltaV, and the DeltaV design are marks of one of the Emerson Process Management of companies. All other marks are property of their respective owners. The contents of this publication are presented for informational purposes only, and while every effort has been made to ensure their accuracy, they are not to be construed as warrantees or guarantees, expressed or implied, regarding the products or services described herein or their use or applicability. All sales are governed by our terms and conditions, which are available on request. We reserve the right to modify or improve the design or specification of such products at any time without notice.
While this information is presented in good faith and believed to be accurate, Mynah Technologies does not guarantee satisfactory results from reliance upon such information. Nothing contained herein is to be construed as a warranty or guarantee, express or implied, regarding the performance, merchantability, fitness or any other matter with respect to the products, nor as a recommendation to use any product or process in conflict with any patent. Mynah Technologies reserves the right, without notice, to alter or improve the designs or specifications of the products described herein.