Emerson PACSystems User manual

User Guide
GFK -3019G
Oct 2019
PACSystemsTM
FIELD AGENT MACHINE ADAPTER
USER GUIDE

User Guide Contents
GFK-3019G Oct 2019
Contents i
Contents
Chapter 1: Introduction.....................................................1
1.1 Revisions in this Manual............................................................................... 1
1.2 Related Documentation .............................................................................. 1
1.2.1 Product Landing Pages ...................................................................... 1
1.3 Other Documentation ................................................................................. 2
Chapter 2: Overview..........................................................3
2.1 Machine Adapter Definition......................................................................... 3
2.2 Minimum Requirements to Get Started ....................................................... 3
2.3 Common Deployment Method.................................................................... 3
2.3.1 Configuration Template .................................................................... 4
2.3.2 Application Template ........................................................................ 5
Chapter 3: EGD Machine Adapter.......................................6
3.1 EGD Machine Adapter Architecture ............................................................. 6
3.1.1 Features and Compatibility ............................................................... 6
3.2 Obtaining the EGD Machine Adapter ........................................................... 6
3.3 Deployment Options ................................................................................... 6
3.4 Configuring the EGD Machine Adapter ........................................................ 7
3.4.1 Modifying the Configuration Files...................................................... 7
3.4.2 Field Agent Configuration Tool........................................................ 11
3.5 Performance ............................................................................................. 11
3.6 Troubleshooting........................................................................................ 12
3.6.1 The EGD debug webpage ................................................................ 12
Configuring and Accessing the Webpage................................................... 12
Elements of the EGD Debug Webpage....................................................... 13
3.6.2 No EGD Data in the EGD Machine Adapter....................................... 13
3.6.3 No EGD Data in the Cloud................................................................ 14
3.6.4 EGD Data with Incorrect Time ......................................................... 14
Chapter 4: Modbus RTU Machine Adapter........................ 15
4.1 Modbus RTU Machine Adapter Architecture .............................................. 15
4.1.1 Features and Compatibility ............................................................. 15
4.2 Obtaining the Modbus RTU Machine Adapter ............................................ 15
4.3 Deployment Options ................................................................................. 15

User Guide Contents
GFK-3019G Oct 2019
Contents ii
4.4 Configuring the Modbus RTU Machine Adapter ......................................... 17
4.4.1 Modifying the Configuration Files Manually ..................................... 17
4.4.2 Field Agent Configuration Tool........................................................ 20
4.4.3 Deploying the Modbus RTU Machine Adapter.................................. 22
4.5 Performance ............................................................................................. 22
4.6 Troubleshooting........................................................................................ 22
4.6.1 RS-232 Cable Disconnected between Field Agent and Modbus Slave23
4.6.2 Incorrect Register Address .............................................................. 23
4.6.3 Invalid Register Address .................................................................. 23
4.6.4 Invalid Data Type............................................................................. 24
4.6.5 Invalid Register Bit Index ................................................................. 24
4.6.6 Null Register Name ......................................................................... 24
4.6.7 Invalid Register Type ....................................................................... 24
Chapter 5: OSI PI Machine Adapter .................................. 26
5.1 OSI PI Machine Adapter Architecture ......................................................... 26
5.1.1 Features and Compatibility ............................................................. 26
5.1.2 Supported Value Type ..................................................................... 26
5.2 Obtaining the OSI PI Machine Adapter ....................................................... 26
5.3 Deployment Options ................................................................................. 27
5.4 Configuring the OSI PI Machine Adapter .................................................... 28
5.4.1 Modifying the Configuration Files Manually ..................................... 28
5.4.2 Field Agent Configuration Tool........................................................ 30
5.5 Deploying the OSI PI Machine Adapter....................................................... 30
5.6 Performance ............................................................................................. 30
5.7 Troubleshooting........................................................................................ 30
5.7.1 Invalid PI Server IP Address .............................................................. 31
5.7.2 Invalid PI Server Port Number .......................................................... 31
5.7.3 Invalid Proxy Host............................................................................ 31
5.7.4 Invalid Proxy Port ............................................................................ 31
5.7.5 Invalid Data Node Name.................................................................. 32
5.7.6 Invalid PI Point Name....................................................................... 32
5.7.7 Invalid PI Point Name Format........................................................... 32
5.7.8 Invalid PI Point Name....................................................................... 33
5.7.9 Null PI Point Name........................................................................... 33
5.7.10Invalid PI Server Username .............................................................. 33
5.7.11Invalid PI Server Password ............................................................... 33

User Guide Contents
GFK-3019G Oct 2019
Contents iii
5.7.12Null Timeseries Tag Name ............................................................... 34
Chapter 6: EtherNet/IP Machine Adapter ......................... 35
6.1 EtherNet/IP Machine Adapter Architecture ................................................ 35
6.1.1 Features and Compatibility ............................................................. 35
6.1.2 Supported File Types ....................................................................... 35
Supported file types when sending PCCC commands................................. 35
Supported data types when sending CIP messages .................................... 36
6.2 Obtaining the EtherNet/IP Machine Adapter .............................................. 36
6.3 Deployment Options ................................................................................. 36
6.4 Configuring the EtherNet/IP Machine Adapter ........................................... 37
6.4.1 Modifying the Configuration Files Manually ..................................... 38
6.4.2 Field Agent Configuration Tool........................................................ 39
6.4.3 Deploying the EtherNet/IP Machine Adapter ................................... 39
6.5 Performance ............................................................................................. 39
6.6 Troubleshooting........................................................................................ 40
6.6.1 Invalid XML file path ........................................................................ 40
6.6.2 Null PLC Port Number...................................................................... 40
6.6.3 Null IP Address ................................................................................ 40
6.6.4 Invalid IP Address ............................................................................ 40
6.6.5 PLC Not reachable or cable disconnected ........................................ 41
6.6.6 Null Time series Tag Name .............................................................. 41
6.6.7 Unsupported tag or Invalid format (PCCC Protocol)......................... 41
6.6.8 Incomplete tag (PCCC Protocol) ...................................................... 41
6.6.9 Memory does not exist (PCCC Protocol) .......................................... 41
6.6.10Tag does not exist (CIP Protocol) ..................................................... 42
6.6.11Null Subscription Name................................................................... 42

User Guide Chapter 1
GFK-3019G Oct 2019
Introduction 1
Chapter 1: Introduction
1.1 Revisions in this Manual
Rev
Date
Description
F
Oct 2019
Following Emerson’s acquisition of this product, changes have been
made to apply appropriate branding and registration of the product
with required certification agencies. No changes to material, process,
form, fit or functionality.
E
Dec-2017
Formatting changes.
Updated Contact Info.
D
Jul-2017
Added EtherNet/IP Machine Adapter.
Added performance data for EGD, Modbus RTU, and OSI PI Machine
Adapters.
C
Oct-2016
Added OSI PI Machine Adapter.
B
Jul-2016
Inserted Common Deployment Option.
Revised the deployment for the EGD Machine Adapter.
A
Oct-2015
Added Modbus RTU Machine Adapter.
Jul-2015
Initial document release.
1.2 Related Documentation
1.2.1 Product Landing Pages
Product
URL
Mini Field Agent
https://www.emerson.com/Industrial-Automation-Controls/support
CPE400 with
Embedded Field
Agent
Virtual Field
Agent
Field Agent
Machine Adapters

User Guide Chapter 1
GFK-3019G Oct 2019
Introduction 2
1.3 Other Documentation
Document ID
Document Title
GFK-2993
Field Agents User Guide
GFK-3009
Field Agents Secure Deployment Guide
GFK-3017
Mini Field Agent Upgrade Guide
GFK-3018
Field Agents Registration Guide
GFK-2830
PACSystems* RXi, RX3i, and RX7i Controllers Secure Deployment
Guide
GFK-2222
PACSystems CPU Reference Manual
GFK-2314
PACSystems RX3i System Manual
GFK-2224
TCP/IP Ethernet Communications for PACSystems User’s Manual
GFK-2225
TCP/IP Ethernet Communications for PACSystems Station Manager
Manual
GFK-2571
PACSystems RX3i PROFINET Controller Manual
GFK-2572
PACSystems RX3i PROFINET Controller Command Line Interface
Manual
GFK-2904
PROFINET IO Devices Secure Deployment Guide

User Guide Chapter 2
GFK-3019G Oct 2019
Overview 3
Chapter 2: Overview
2.1 Machine Adapter Definition
In the Predix Machine platform, Machine Adapters are application plugins that enable
protocol support for industrial data sources like PLCs and HMIs. Machine Adapters are
configured to ingest this data to make it available to Predix Machine for local analytics and
for transmission to the Predix Cloud where it can be used for visualization and cloud
analytics.
The Predix Machine platform ships with Machine Adapters that are suitable in production
for OPC UA and Modbus® TCP. These Machine Adapters have been validated on the various
Field Agent hardware platforms provided by Emerson business. Additionally, Automation
& Controls provides additional Machine Adapters to support the additional industrial
protocols of EGD, Modbus RTU, OSI PI, and EtherNet/IP™. This document describes how
each A&C Machine Adapter is configured and used.
Documentation for the Machine Adapters included with Predix Machine can be found by
searching for “OPC-UA Machine Adapter” or “Modbus Machine Adapter” in
https://docs.predix.io.
2.2 Minimum Requirements to Get Started
The following are the minimum steps required to start using the machine adapter with the
field agents. For more detailed instructions for each step, refer to the section “Getting
Started with the Field Agent” in the Field Agents User Guide, GFK-2993.
1. Register the Field Agent.
2. Power up the Field Agent.
3. Log into the Predix Machine Web Console.
4. Identify and configure the network of the producer(s) and consumer(s).
5. Ensure the Field Agent is running a compatible Predix Machine version (e.g.
17.1.2).
6. Log into EdgeManager.
2.3 Common Deployment Method
There are multiple ways to deploy the machine adapters with your current Predix Machine.
This section describes the most common method for deploying the machine adapters by
utilizing the EdgeManager and Field Agent Configuration Tool, it is not necessarily the only
way to deploy it. For more information on other deployment methods for each machine
adapter, go to the specific section for that machine adapter. Figure 1 illustrates the general
process for deploying the machine adapters using EdgeManager.

User Guide Chapter 2
GFK-3019G Oct 2019
Overview 4
Note: As of this document revision, the Field Agent Configuration Tool only supports configurations for
the Modbus-RTU. You cannot use the Field Agent Configuration Tool for other machine adapters.
For more updated information on supported machine adapters, please visit Emerson support site
and search for Field Agent Configuration Tool.
Figure 1: Flow process for deploying the machine adapters with EdgeManager
Be sure to follow the steps in Sections 2.3.1 and 2.3.2 sequentially for the configuration
template and then the application template.
2.3.1 Configuration Template
1. Obtain the configuration template:
a. If the configuration is for Modbus RTU:
i. Open the Field Agent Configuration Tool.
ii. Configure the machine adapter accordingly. Refer to the specific
machine adapter section for more information on inputs.
iii. Click on “Validate” to ensure all the information entered is correct.
iv. Save the configuration in the Field Agent Configuration Tool.
v. Click on “Create Configuration Bundle”.
b. If the configuration is not for Modbus RTU, i.e. EGD, OSI PI, etc.:
i. Download the configuration template for the machine adapter from
Salesforce: https://www.emerson.com/Industrial-Automation-
Controls/support.

User Guide Chapter 2
GFK-3019G Oct 2019
Overview 5
ii. Open the configuration files (in the /configuration/machine
directory) to edit. Refer to the specific machine adapter section for
more information on how to edit the configuration files.
iii. Save the configuration files edited in the previous step. Re-zip
configuration folder.
2. Go to EdgeManager and login with your credentials.
3. Click on “Repository” and “Select Action” > “Upload” to upload the configuration
template.
4. Click on “Device Manager”, search for your field agent and click on it.
5. Go to the “Configuration” tab and click on “Deploy Configuration” and select the
configuration template that you just uploaded and select “Deploy”.
2.3.2 Application Template
6. Download the configuration template for the machine adapter from Salesforce:
https://www.emerson.com/Industrial-Automation-Controls/support.
7. Go to EdgeManager and login with your credentials.
8. Click on “Repository” and “Select Action” > “Upload” to upload the application
template.
9. Click on “Device Manager”, search for your field agent and click on it.
10. Go to the “Software” tab and click on “Deploy Software” and select the application
template that you just uploaded and select “Deploy”.

User Guide Chapter 3
GFK-3019G Oct 2019
EGD Machine Adapter 6
Chapter 3: EGD Machine Adapter
3.1 EGD Machine Adapter Architecture
Ethernet Global Data (EGD) is a proprietary protocol used by Emerson to communicate
between industrial data sources. EGD enables a producer (e.g. a CPU) to share a portion of
its internal reference memory with consumers (e.g. one or more other CPUs). The EGD
Machine Adapter enables Field Agents to consume EGD exchanges to make this industrial
data available to the Predix Machine platform and Predix Cloud. The EGD Machine Adapter
will run on Mini Field Agents (MFA), Embedded Field Agents (EFA) and Virtual Field Agents
(VFA).
3.1.1 Features and Compatibility
This table lists the EGD Machine Adapter features and compatibility.
Features
EGD Machine Adapter 1.0.0
Reading
Yes
Writing
No
Broadcast
Yes
Unicast
Yes
Multi-cast
Yes
Predix Machine Version
17.1
3.2 Obtaining the EGD Machine Adapter
The EGD Machine Adapter is a free add-on application for the field agents. The EGD Machine
Adapter configuration and application files can be obtained from the following location:
https://www.emerson.com/Industrial-Automation-Controls/support.
3.3 Deployment Options
The Configuration Template and Application Template can be deployed to the Field Agent
from EdgeManager. Refer to Section 2.3, Common Deployment Method for the general
process flow of deploying. Once you understand the deployment process, then proceed to
Section 3.4.1, Modifying the Configuration Files, for more information on how to manually
edit the configuration files.
Note: There are two different templates that need to be updated - the Configuration Template and the
Application Template. Download the appropriate templates for the target platform (MFA, EFA or VFA)
and version of Predix Machine, and add the EGD Machine Adapter configuration and application files
to them respectively. The .config and .xml files will go into the Configuration Template while the .jar
file will go into the Application Template. Section 3.4.1, Modifying the Configuration Files, describes
how to configure the .config and .xml files and how to deploy them along with the .jar file.

User Guide Chapter 3
GFK-3019G Oct 2019
EGD Machine Adapter 7
3.4 Configuring the EGD Machine Adapter
Many Predix Machine bundles use configuration files to specify their behavior. These
configuration files can be managed both from EdgeManager across multiple Field Agents
and, under limited circumstances, from the Predix Machine Web Console for an individual
Field Agent. In both cases, a default set of configuration files must be obtained as a starting
place for making modifications and additions.
3.4.1 Modifying the Configuration Files
The following is a complete list of relevant configuration files (some may not require
modification):
File
Source
Deployment
Destination
Modification
com.ge.ac.machine
adapter.egd.config
com.ge.ac.machineadapt
er.egd-1.0.0-
cfg\configuration\machin
e
<Configuration
Template>\configura
tion\machine
Required
com.ge.ac.machine
adapter.egd.xml
com.ge.ac.machineadapt
er.egd-1.0.0-
cfg\configuration\machin
e
<Configuration
Template>\configura
tion\machine
Required
com.ge.ac.machine
adapter-egd-
1.0.0.jar
com.ge.ac.machineadapt
er.egd-1.0.0-
app\machine\bundle
<Application
Template>\machine\
bundles
Required
ProducedData-
Px.x.x.x.xml
If dynamic binding is
supported, then it will
automatically be
uploaded. If not,
commission engineer
must obtain the file
associated with the
controller and download it
to the field agent.
<Configuration
Template>\configura
tion\machine
Required
machinegateway.in
<Predix Machine
Application Template
Directory>\machine\bin\v
ms
<Predix Machine
Application Template
Directory>\machine\
bin\vms
Required
com.ge.dspmicro.h
oover.spillway-
0.config
<Predix Machine
Configuration Template
Directory>\configuration\
machine
<Predix Machine
Configuration
Template
Directory>\configura
tion\machine
Required for
sending data to
the cloud

User Guide Chapter 3
GFK-3019G Oct 2019
EGD Machine Adapter 8
File
Source
Deployment
Destination
Modification
com.ge.dspmicro.w
ebsocketriver.send-
0.config
<Predix Machine
Configuration Template
Directory>\configuration\
machine
<Predix Machine
Configuration
Template
Directory>\configura
tion\machine
Required for
sending data to
the cloud
org.ops4j.pax.loggi
ng.cfg
<Predix Machine
Configuration Template
Directory>\configuration\
machine
<Predix Machine
Configuration
Template
Directory>\configura
tion\machine
Optional for
debugging
Note: There is a distinction between the <Predix Machine Application/Configuration Template Directory>
and the <Application/Configuration Template>. The <Application/Configuration Template> refers to
the application and configuration that you will deploy to EdgeManager. The <Predix Machine
Application/Configuration Template Directory> refers to the actual application and configuration
directory in your Predix Machine (modifiable through EdgeManager).
You can revise multiple files via EdgeManager and then schedule the deployment at once.
The steps to configure the EGD Machine Adapter are:
com.ge.ac.machineadapter.egd.config
1. Open the file com.ge.ac.machineadapter.egd.config for editing.
2. Note that the file is divided into three sections:
•LIKELY TO CHANGE –configurations that require modifications.
—network-interface could be a range of IP addresses in the following
format: x.x.* where x is any integer number between 0 and 255 or a
specific IP address. The * indicates that the subset of the network x.x that
is allowed. The Machine Adapter will go through all the network
interfaces defined on the Field Agent and listen to the first network
interface that it finds that matches this configuration, i.e. if the input is
172.16.*, then it will listen on UDP (101) or the PDH (201).
—subscriptionName is the name of the subscription provided by the EGD
Machine Adapter. Please note that this name must match the value in
com.ge.dspmicro.hoover.spillway-0.config under
com.ge.dspmicro.hoover.spillway.dataSubscriptions. Renaming this
variable will require a restart or reboot of the Field Agent. The default
value is “EGDSub1”.
•MAY HAVE TO CHANGE –configurations that may require modification,
but likely do not.
—name is the name of this Machine Adapter.
—description is the description of this Machine Adapter.

User Guide Chapter 3
GFK-3019G Oct 2019
EGD Machine Adapter 9
—bind-address is the IP address to bind when listening for EGD messages.
This configuration item is only supported in the Windows® operating
system, and is hence not supported on Automation & Controls Field
Agents.
—multicast-group is the multicast group to join before listening for EGD
messages. Multicast is a group IP address. Unicast is a single device IP
address. Broadcast is listening to all devices on the LAN. Multiple
addresses can be listed by separating each IP address with a comma, e.g.
"224.1.2.3, 224.0.7.1".
—listen-port is the port number to use to listen for EGD messages. The
default port value is “18246”.
Note: Only change the string in between the quotations “ ”. For example, when changing
com.ge.ac.machineadapter.egd.listen-port=I"18246", only change 18246 and do not replace the
entire I“18246”.
•UNLIKELY TO CHANGE –configurations that only require modification to
improve performance.
—threadpool.coresize is the thread pool size to handle subscriptions.
—threadpool.maxsize is the thread pool maximum size to handle
subscriptions.
—maxqueue.size is the subscription queue size to handle subscriptions.
—udp-recvbuff.size is the UDP/IP receive buffer size to use when listening
to EGD messages.
3. Change the configurations as needed. The description of what each configuration
item does is included in the file.
4. Remove the comment hashtag “#” in front of the line of configuration (not in front
of the comments) to use a given configuration. The
com.ge.ac.machineadapter.egd.config file comes with default configurations.
Other configurations, particularly the ones listed as “UNLIKELY TO CHANGE”, are
commented out.
5. Save and close
com.ge.ac.machineadapter.egd.config.com.ge.ac.machineadapter.egd.xml
1. Open the file com.ge.ac.machineadapter.egd.xml for editing.
2. Edit the data contained within the NameRules element:
•AutoVarnameRule is the name that will display for the data labels in the
cloud. It does not need to include “SiteName”, but is recommended to
help ensure all customer’s variables are unique.
i. “{%ProducerName}” and “{%VarName}” are also optional. When
used, they will be populated with the actual value defined for them,
i.e. {%ProducerName} will be populated with the <Producer Name>
element and {%VarName} will be populated with the <Var Name>

User Guide Chapter 3
GFK-3019G Oct 2019
EGD Machine Adapter 10
element. If the <Var Name> element is not defined, then <Var EgdId>
value will populate {%VarName}.
3. Edit the data contained within the Producer element:
•Name is the name of the producer. Valid characters: A-Z, a-z, 0-9 and
underscores (_). The name must start with a letter. This name must match
the name of the producer.
•ProducerID is a unique value that identifies the producer. No two
producers can share the same Producer ID. The default value of the
ProducerID is the IP address of the producer.
•Address is the IP address of the producer in dotted decimal format (x.x.x.x,
where x is any integer number between 0 and 255).
•VarGroup is the name of the variables/tags that will be received and
stored/sent to the Hoover Spillway. It must match the VarGroup Name
element (in step 4). If there are multiple producers that contain the same
variables, a single VarGroup can be defined and referenced for each
producer, rather than duplicating the variable list.
•EgdHttp is a Boolean value (true/false) that defines if the producer has
dynamic binding/loading capabilities for its EGD configurations.
4. Edit the attributes contained within the VarGroup Var element:
•Name is what will be given to the Hoover Spillway (i.e. what will be
published in the time series). This name is optional and can be changed or
removed as needed.
•EgdId is the EGD name of the variable in the ProducedDatax.x.x.x.xml file.
It must match the controller’s variable name.
5. Remove the lines marked with “REMOVE THIS LINE TO USE” completely in order to
use the elements edited above. Delete any unneeded Producer and/or VarGroup
elements.
6. Save and close com.ge.ac.machineadapter.egd.xml.

User Guide Chapter 3
GFK-3019G Oct 2019
EGD Machine Adapter 11
Note: The port in the Field Agent firewall will need to be opened to enable the EGD Machine Adapter to hear
the EGD exchanges. Refer to the section “How to Open Ports on a Field Agent” in the Field Agents
User Guide, GFK-2993, to learn how to open ports in the Field Agent firewall.
machinegateway.ini
1. Open the file machinegateway.ini file in <Predix Machine Application
Template>/machine/bin/vms for editing.
2. Add the following block of code under the <section> element with
<name>Section_7_Start</name>:
<bundle>
<name>com.ge.ac.machineadapter-egd-1.0.0.jar</name>
</bundle>
3. Save and close machinegateway.ini.
Note: If the Field Agent does not support dynamic binding, copy ProducedData-Px.x.x.x.xml (where x is any
integer number between 0 and 255) into the <Configuration Template>/configuration/machine
directory.
3.4.2 Field Agent Configuration Tool
Currently the Field Agent Configuration Tool does not support configurations for the EGD
machine adapter. For more updated information on the Field Agent Configuration Tool,
please visit:https://www.emerson.com/Industrial-Automation-Controls/support.
3.5 Performance
EGD data throughput to Time Series Database (TSDB) is dependent on the number of EGD
exchanges processed, as well as network bandwidth of both EGD and cloud networks. Each
EGD exchange results in one subscription message forwarded to TSDB: the MFA can send
one subscription message per second, and the VFA is capable of sending about four
subscription messages per second.
To maximize data throughput to the cloud given these limits, it is best to fully populate each
EGD exchange with data. The chart below illustrates the maximum number of 4-byte REAL
variables that can be published to TSDB by the EGD Machine Adapter.

User Guide Chapter 3
GFK-3019G Oct 2019
EGD Machine Adapter 12
Supported Configurations for EGD Machine Adapter (EGD interval update 480 ms)
Publish Interval
(ms)
MFA Max Configured and
Published 4-Byte Variables
VFA Max Configured and Published
4-Byte Variables
1000-1999
350 (one exchange) 1
1050 (three exchanges) 1
2000-2999
700 (two exchanges) 1
2450 (seven exchanges) 1
3000-3999
1050 (three exchanges) 1
3850 (eleven exchanges) 1
≥4000
1400 (four exchanges) 1
5250 (fifteen exchanges) 1
3.6 Troubleshooting
Before attempting some of these possible solutions, be sure to check that the string for each
of the configurations in the .config and .xml files are valid and not empty. For example, the
IP address should follow the correct format and should exactly match the intended IP
address.
3.6.1 The EGD debug webpage
Configuring and Accessing the Webpage
The EGD Debug Webpage is intended to aid in debugging EGD configuration issues. It can
be accessed using a web browser while the EGD Machine Adapter is running. It provides
information on the configurations, statistics of the messages, details of EGD packets, and
logging messages.
Before accessing the webpage, the following configuration modifications are needed:
1. Open the file org.ops4j.pax.logging.cfg for editing inside in
<Configuration Template>/configuration/machine.
2. Add the following lines at the end of the file:
log4j.category.com.ge.ac.pmAdapter=DEBUG
log4j.category.com.ge.ac.pmEgd=DEBUG
log4j.category.com.ge.ac.egd=DEBUG
3. Save and close org.ops4j.pax.logging.cfg.
After deploying the updated configurations above, access the webpage using the following
URL:
https://<Field Agent IP address>:8443/egd/startup
If running the EGD locally on a PC instead of a Field Agent appliance, access the webpage
using the following URL:
1
Exchanges are fully populated.

User Guide Chapter 3
GFK-3019G Oct 2019
EGD Machine Adapter 13
https://localhost:8443/egd/startup
Elements of the EGD Debug Webpage
The webpage has the following elements:
•Startup Messages: messages from the EGD machine adapter starting up, indicating
configurations of the machine adapter.
•Configuration: configurations that the EGD machine adapter is utilizing, including the
data subscription name, EGD xml config file name and the Predix machine home
directory.
•Statistics: statistics of the processed EGD messages including missed EGD messages.
•Packets: detailed information on each EGD packet received.
•Files: configuration files that are utilized for the EGD machine adapter.
•Log: log messages from the Predix machine. It is filtered by the following categories:
“All”, “Info”, “Warn”, “Debug” and “Error”.
3.6.2 No EGD Data in the EGD Machine Adapter
If the EGD Machine Adapter is not initializing or running, follow the steps below to
troubleshoot and resolve the issue:
1. Check the machinegateway.ini file in <Predix Machine Application
Template>/machine/bin/vms.
Verify the following block of code is present:
<bundle>
<name>com.ge.ac.machineadapter-egd-1.0.0.jar</name>
</bundle>
2. Verify the com.ge.ac.machineadapter.egd.xml and
com.ge.ac.machineadapter.egd.config files:
a. Verify that both configuration files are in the Configuration Template.
i. In EdgeManager, select the Field Agent device in the Device Manager.
ii. Under the “Configurations” tab, select the most recent deployed
configuration.
iii. Verify the deployed configuration contains both expected
configuration files.
b. Verify the contents of both files are correctly configured. If the EGD Debug
Webpage is configured, verify the contents through the EGD Debug Webpage
> Files > Egd Config File / Egd Xml File.
3. Verify the com.ge.ac.machineadapter-egd-1.0.0.jar is in the Application Template.
a. In the EdgeManager Repository, search for the most recent deployed
Application Template.

User Guide Chapter 3
GFK-3019G Oct 2019
EGD Machine Adapter 14
b. Select the template and click on “Select Action” > “Download”.
c. Unzip the zip directory.
d. Open the file and verify the .jar file is present in the <Zip Folder Directory
Path>\machine\bundles directory.
4. Verify that the port is open in the Field Agent firewall. Refer to the section “How to
Open Ports on a Field Agent” in the Field Agents User Guide, GFK-2993, to learn
how to open ports in the Field Agent firewall. You may need to reboot the field
agent once you have made changes to the port in order for those changes to take
effect.
3.6.3 No EGD Data in the Cloud
If the Field Agent is not consuming EGD exchanges, follow the steps below:
1. Open the com.ge.dspmicro.hoover.spillway-0.config file and verify that under
com.ge.dspmicro.hoover.spillway.dataSubscriptions, there is an item in the list
that matches the subscriptionName from the
com.ge.ac.machineadapter.egd.config file. The default value is “EGDSub1”.
2. Open the com.ge.dspmicro.websocketriver.send-0.config file and verify that the
following configurations are filled out correctly:
a. com.ge.dspmicro.websocketriver.send.river.name should match
com.ge.dspmicro.hoover.spillway.destination in the
com.ge.dspmicro.hoover.spillway-0.config file.
b. com.ge.dspmicro.websocketriver.send.destination.url
c. com.ge.dspmicro.websocketriver.send.header.zone.value
3.6.4 EGD Data with Incorrect Time
If the timestamp on the data sent to the cloud is too old, then the Predix Cloud will throw
the data away. However, the EGD machine adapter currently uses the time when the data is
received by the field agent, not the time that was sent in the exchange. To ensure that the
data has the correct time, use the Time Synchronization page in the Predix Machine Web
Console to set the time on the Field Agent.

User Guide Chapter 4
GFK-3019G Oct 2019
Modbus RTU Machine Adapter 15
Chapter 4: Modbus RTU Machine Adapter
4.1 Modbus RTU Machine Adapter Architecture
Modbus RTU is an open, industry standard serial protocol used by many industrial devices
to communicate. Modbus RTU enables a Modbus Slave to share a portion of its internal
reference memory with one or more Modbus Masters. The Modbus RTU Machine Adapter
enables a Mini Field Agent to act as a Modbus Master to read data from a Modbus Slave
connected by a RS-232 serial cable and make this industrial data available to the Predix
Machine platform and Predix Cloud.
4.1.1 Features and Compatibility
This table lists the Modbus RTU Machine Adapter features and compatibility.
Features
Modbus RTU Machine Adapter 170102.1.0
Modbus Read
Yes
Modbus Write
No
Predix Machine Version
17.1
4.2 Obtaining the Modbus RTU Machine Adapter
The Modbus RTU Machine Adapter must be purchased for each Field Agent where it will be
installed. It can then be downloaded from the following location:
https://www.emerson.com/Industrial-Automation-Controls/support.
After downloading the zip file containing the Modbus RTU Machine Adapter, verify the file
integrity by calculating a SHA-256 sum of the zip file and compare it to the expected SHA-
256 sum posted on the download page.
4.3 Deployment Options
The Modbus RTU Machine Adapter is packaged as a single zip file containing two separate
components:
1. An inner zip file containing the Modbus RTU Machine Adapter binaries (.jar, .so).
•Customers that want to deploy the non-configured Modbus RTU Machine
Adapter into a running system can directly upload the zip to EdgeManager as an
Application and deploy it.
•Customers that want to add these binaries to an existing Application Template
can do so using the instructions below.
2. An inner zip file containing the Modbus RTU Machine Adapter configuration files
(.config, .xml).

User Guide Chapter 4
GFK-3019G Oct 2019
Modbus RTU Machine Adapter 16
•Customers that want to use the Field Agent Configuration Tool to generate
Modbus RTU configuration files can ignore the files in this zip.
•Customers that want to add these configuration files to an existing Configuration
Template can do so using the instructions below.
As a result, the possible deployment options for the Modbus RTU Machine Adapter are:
1. Deployment Option 1: Modbus RTU Machine Adapter Application + Field Agent
Configuration Tool output
a. Deploy the Modbus RTU Machine Adapter Application zip (from the
package downloaded) as an EdgeManager Application.
b. Use the Field Agent Configuration Tool to generate configuration files for
the Modbus RTU Machine Adapter.
c. Deploy the output of the Field Agent Configuration Tool as an
EdgeManager Configuration.
2. Deployment Option 2: Modbus RTU Machine Adapter Application + Configuration
Template
a. Deploy the Modbus RTU Machine Adapter Application zip (from the
package downloaded) as an EdgeManager Application.
b. Add the Modbus RTU Machine Adapter configuration files (manually
copied from the package downloaded) to an existing Configuration
Template, like the MFA Configuration Template for Predix Machine 17.1.2.
c. Deploy a Configuration Template including the Modbus RTU Machine
Adapter configuration files as an EdgeManager Configuration.
3. Deployment Option 3: Application Template + Configuration Template
a. Add the Modbus RTU Machine Adapter binaries (manually copied from the
package downloaded) to an existing Application Template, like the MFA
Application Template for Predix Machine 17.1.2.
b. Deploy the Application Template including the Modbus RTU Machine
Adapter binaries as an EdgeManager Application.
c. Add the Modbus RTU Machine Adapter configuration files (manually
copied from the package downloaded) to an existing Configuration
Template, like the MFA Configuration Template for Predix Machine
17.1.2.
d. Deploy a Configuration Template including the Modbus RTU Machine
Adapter configuration files as an EdgeManager Configuration.
In order to extend an existing Application or Configuration Template to include the
Modbus RTU Machine Adapter, manually copy the following source files into the specified
destination directories in the respective template.