This application note documents the required procedure for integrating the Digi One IAP serial server with a DeltaV Virtual IO Module with Generic EtherNet/IP firmware (IOD-4104). Reference manuals for both the Digi One IAP and the DeltaV Virtual IO Module firmware IOD-4104 are provided in the beginning section of the application note.
The network schematic below should serve as a guideline for the network configuration used for this application. Some components of this application place constraints on the network design (e.g. - DeltaV) and should be taken into account during network setup.
There may be instances during the procedure where it is beneficial to consult the documentation for the products used in this application. Links to the manuals for the products are given below:
Digi One IAP - PDF
Virtual IO Module IOD-4104 - Web Help
1 - Configure Digi One IAP Network Address
Insert the "Software & Documentation" CD that came with the Digi One IAP into the computer's CD drive. Navigate to the CD drive using Windows Explorer, then run "setup.exe" from the CD root.
A splash screen will appear. If the device setup wizard does not launch automatically, click "Setup" to launch the device setup wizard manually.
The device setup wizard will detect Digi devices on the computer's network and provide configuration options for each of these devices. Select the device you wish to configure, then select the settings you wish to apply to each port on that device. The Digi configuration wizard may fail to apply the port configuration(s) to the device, however, the ports can also be configured using the web interface (outlined in section 2). The only critical configuration parameter for the Digi One IAP is the IP Address - as long as the IP Address is successfully assigned using the wizard, the remaining configuration can be completed through the web interface.
2 - Configuring the EtherNet and Serial Ports on the Digi One IAP
Open a web browser and enter into the address bar the IP Address assigned to the Digi One IAP in the previous step. If the connection attempt is successful, the device will require user credentials to access the web configuration utility. If these user credentials have not yet been configured, use the factory default credentials, as shown below:
From the "Network" tab under "Configuration," the network settings of the Digi One IAP can be modified if necessary.
From the "Industrial Automation" tab under "Applications," the Serial Slaves can be configured. To configure a port, select the protocol that will be used for IO communications with the slave device attached to that port, then click "Add." (Note that the green 9-pin terminal block connector on the Digi One IAP is "Port 1" and the 9-pin RS-232 port is "Port 2.")
To configure the Network Masters, click on "Network Masters" under "Industrial Automation" in the main window. Select the protocol(s) you wish to enable for the Network Masters, then click "Apply."
After all of the necessary settings have been configured, from the "Reboot" tab under "Administration," click the "Reboot" button to reboot the Digi One IAP and apply all of the configured settings. The Digi One IAP serial server is now ready for IO communications.
3 - Configuring the Digi One IAP in VIMNet Explorer
Open VIMNet Explorer.
Right-click on "Physical Network" and select "Properties."
Select the NIC that has access to the subnet which contains the IP Address of the Digi One IAP by clicking on the IP Address in the "Used Addresses" listbox. If the desired IP Address does not appear in the "Used Addresses" listbox, click the "Refresh" button next to the "Available NIC" drop-down menu. Select the correct NIC IP Address, then click "Add" to add that address to the listbox below.
Right-click on "Decommissioned VIMs" and select "Refresh List." This will find all Vitual IO Modules that can be reached on the configured Physical Network (note that it may take up to 30 seconds of scanning to find all VIMs on the network).
Right-click on "I/O Net"and select "New Controller."
Assign the new controller a name, then click "OK." (The controller in this example is named "DIGI_ONE_DV.")
Right-click on the newly created controller and select "New IO VIM."
Configure the parameters on the prompt window as outlined in the table below:
||I/O VIM - Generic Ethernet IP 4.x|
|Virtual Cards||(Depends on DeltaV configuration - This example uses 57-60)|
DeltaV version 10.x or earlier or M-series IO
||(Depends on DeltaV controller hardware and software version)|
||(User's choice - ensure the selected IP Address is not in use and that the VIM is on the same subnet as the Digi One IAP)|
After all of the parameters have been configured, click "OK."
Expand the newly created Virtual IO Module, then expand "C57." Right-click "P01"and select "Add Device."
When the prompt window appears, click "Add" next to the "IP Address" list box.
The IP Address entered here is the configured IP Address of the Digi One IAP serial server. Leave all of the other parameters as the defaults (shown above), then click "OK."
Leave all of the other parameters in the main prompt window as the defaults (shown above), then click "OK."
If no available connection definitions exist, a dialog will appear asking to create a new connection definition. Select "Yes" to continue.
A prompt window will appear with several configurable parameters. However, only a few of these parameters need to be modified. Configure the following parameters as outlined in the table below:
||UCMM, with "DF1" checked|
||Type: 16-bit unsigned integer, Input|
* See Appendix for more info on Base DataSet Types to configure connection definitions for other Modbus register types.
After these parameters have been configured, click the "Msg Parameters" button in the "EtipBuffer" panel.
A new prompt will appear with several configurable message parameters. Configure these parameters as outlined in the table below:
||Binary File Type [B]|
Register offset (Dec)
||(User's choice, depending on the range of Modbus registers they wish to read from/write to)|
||(User's choice, depending on the number of Mobus registers they wish to read from/write to)|
||Checked (Period value is user's choice)|
* See Appendix for more info on File Types and File Numbers to configure connection definitions for other Modbus register types.
After all of the parameters have been configured, click "OK," then when returned to the first prompt window, click "OK" to save the connection definition.
After the connection definition is created, VIMNet Explorer will prompt the user for a description - this is not required, but the user may input a description if they wish. Click "OK" to add the connection definition to the device in the VIMNet Explorer hierarchy.
Expand the device and the newly created connection definition to reveal a new Dataset. This Dataset contains all of the configuration information necessary for creating this connection definition's Dataset in DeltaV Explorer. When creating a new connection definition, use the settings generated by VIMNet Explorer to create and configure its corresponding Dataset in DeltaV Explorer.
Once all of the connection definitions have been added to the device, right-click on the Virtual IO Module placeholder and select "Commission."
Select the decommissioned VIM from the list of devices displayed in the prompt window, then click "OK."
After the VIM is commissioned, a blue arrow will appear next to the VIM placeholder. This indicates that the VIMNet explorer still needs to be uploaded to the physical VIM. To do this, right-click on the VIM placeholder and select "Upload Configuration to VIM." When prompted to save the VIMNet Explorer configuration file, select "Yes." A warning prompt will appear asking for confirmation to begin the upload - select "Yes" to begin the upload. After the upload is complete, the blue arrow will disappear. The VIM is now ready for communications to the Digi One IAP serial server.
4 - Configuring the VIM Cards in DeltaV Explorer
Open DeltaV Explorer.
Expand "Physical Network," then right-click on "Control Network" and select "New > Controller."
The newly created controller will appear in the main window of DeltaV Explorer. The user may choose to name the new controller if they wish.
Expand the newly created controller, then right-click on "I/O" and select "Auto-sense I/O cards."
After a few minutes, a dialog window will appear indicating that cards were inserted into slots 57-60 (or 61-64 if the VIM was configured for those cards instead of 57-60).
Expand "C57," then right-click "P01" and select "Properties."
In the "Ports" tab, check the "Enabled" checkbox. Leave all of the other settings as their defaults, then click "OK."
Right-click "P01" and select "New Serial Device."
Set the "Device Address" parameter to "1." The user may enter a description of the device if they wish. Click "OK" when all of the parameters are configured.
Right-click "DEV01" and select "New Dataset."
Configure the parameters in each of the tabs as shown above (The parameters for each of these tabs are also outlined in VIMNet Explorer - see section 2 for more information). All of the parameters for this device's Dataset can be found by viewing the dataset under the same device's connection definition in VIMNet Explorer.
After all of the necessary devices and Datasets have been configured, right-click on the controller placeholder and select "Download > Controller."
A warning prompt will appear asking to confirm the download. Check the "Verify the configuration" checkbox and select "Yes" to begin the download.
A progress window will appear that contains a log of all of the download events currently executing. Once the download is finished, click "Close."
5 - Conclusion
The Digi One IAP serial server is now ready for DeltaV IO communications. Our testing of the Digi One IAP confirmed that multiple Modbus slaves can be supported in this configuration using a RS-232/485 half-duplex bus. In this demonstration, only one connection definition was created - that connection definition simulates the Modbus function 01 (Read Coils). For implementing other Modbus functions to work with other register types and ranges, refer to the instructions on creating connection definitions in section 3, as well as the Appendix for the necessary parameter configuration information.
Depending on the Modbus function used to access device registers with the Digi One IAP, the parameter values for the Base DataSet Type, File Type, File Number in the VIM's connection defintion will need to change. Each Modbus function should have its own connection definition in the VIM configuration. Below is a table of parameter values required for these Modbus functions' connection definitions.
Base DataSet Type
|01 - Read Coils||16-bit unsigned int, input||Boolean File [B]||10|
|02 - Read Discrete Inputs (Status)||16-bit unsigned int, input||Boolean File [B]||250|
|03 - Read Holding Registers||16-bit unsigned int, input||Integer File [N]||10|
|04 - Read Input Registers||16-bit unsigned int, input||Integer File [N]||250|
|05 - Write Single Coil||Boolean, output w/ readback||Boolean File [B]||10|
|06 - Write Single Holding Register||16-bit unsigned int, output w/ readback||Integer File [N]||10|
|15 - Write Multiple Coils||16-bit unsigned int, output w/ readback||Boolean File [B]||10|
|16 - Write Multiple Holding Registers||16-bit unsigned int, output w/ readback||Integer File [N]||10|
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.