1. Manuals
  2. Brands
  3. Emerson Manuals
  4. Industrial Equipment
  5. PACEdge
  6. User manual

Emerson PACEdge User Manual

Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
PACEdge User Manual
GFK-3178B
Nov 2020
PACEdge™
USER MANUAL

Advertisement

Table of Contents
loading

Related Manuals for Emerson PACEdge

Summary of Contents for Emerson PACEdge

  • Page 1 PACEdge User Manual GFK-3178B Nov 2020 PACEdge™ USER MANUAL...

  • Page 2: Table Of Contents

    5.1.1 Necessary Platform Components .............. 9 5.1.2 Administration Components ..............9 5.1.3 Application Development Components ........... 10 PACEdge Communication and Data Flow ............11 5.2.1 Internal Communication Between PACEdge Applications ......12 Data Storage and Backup ................... 12 Section 6: PACEdge Usage Examples ........13 Earthquake Monitor ...................
  • Page 3 PACEdge Software Recovery Procedure ............. 27 PACEdge Software Backup Procedure ..............29 Section 10: Troubleshooting ..........30 10.1 Difficulties accessing PACEdge components, erratic behavior ......30 10.2 PACEdge Files ....................30 10.2.1 Installation Test ..................30 10.3 Docker Commands .................... 31 10.4 docker-compose up -d ..................
  • Page 4 Changes, modifications, and/or improvements to equipment and specifications are made periodically and these changes may or may not be reflected herein. It is understood that Emerson may make changes, modifications, or improvements to the equipment referenced herein or to the document itself at any time. This document is intended for trained personnel familiar with the Emerson products referenced herein.

  • Page 5: Introduction

    Introduction PACEdge processing maximizes the value of your data by improving operational reliability, safety, and energy. PACEdge provides all aspects of edge processing and simplifies your IIoT application development, deployment, and administration. All components necessary in the IIoT application lifecycle are brought together in one package to provide a unified interface to decrease your development time and increase your deployable footprint.

  • Page 6: Pacedge Software

    Note: PACEdge software comes pre-installed on Emerson Industrial PCs. PACEdge Usage Model PACEdge software is designed to run on the Industrial PC which is operating in a headless mode, with the user accessing it remotely via Ethernet using the web interface.

  • Page 7: First Login

    The first time you connect a warning message stating that the identity of the device could not be confirmed will be shown. Please click on Advanced and Accept to proceed. (This is due to your browser not recognizing the self-signed certificate of PACEdge. If you trust the device, it is safe to proceed. ) Please read and accept the Emerson End User License Agreement.

  • Page 8: Physical Connections And Configuration Settings

    3.1.1 Network, Keyboard, Display PACEdge is designed to primarily operate on a headless compute device using web interfaces, however, if desired, a monitor and keyboard can be attached. To use web interfaces, the user must know the IP address assigned to the Ethernet port. If using a keyboard and local display, the IP address assignment can be easily checked using Linux commands.

  • Page 9: Pacedge Access And Configuration Options

    PACEdge Access and Configuration Options To fully experience the PACEdge product you must use a web browser. However, users can also access PACEdge with an SSH client or with an attached keyboard. The table below illustrates the steps needed for each approach.

  • Page 10: Login Credentials

    PACEdge is Linux based software but designed to be user friendly with a graphical user interface (Cockpit) for all basic configuration tasks. To access Cockpit, open browser, and type in the IP address of PACEdge. This will bring you to the home page, where you can click on the Cockpit icon. 4.2.1...
  • Page 11 PACEdge User Manual Section 4 GFK-3178B Nov 2020 Figure 4: Cockpit Screen For further Cockpit details and documentation please consult online resources. Quick Start Guide...

  • Page 12: Pacedge Architecture Details

    (internal) (external) PACEdge was designed using Docker architecture, in which each application is running in its own Docker container (Figure 6). Given that containers are designed to be easily replaceable they do not retain an internal state between reboots unless specifically designed to do so. With PACEdge, selected containers will map some of their data to data volumes on the host Linux system so that Node-RED, Grafana, and database changes can be saved between Container restarts and updates.

  • Page 13: Necessary Platform Components

    5.1.2.1 Cockpit Description PACEdge is designed to offer the user a GUI experience. Even though it is based on a Linux operating system, all main system management tasks can be done via GUI and Cockpit is a tool that makes it happen. Cockpit provides system status and health information, resource (CPU,...

  • Page 14: Application Development Components

    5.1.3.1 Node-RED Node-RED is the logic engine of the PACEdge. It provides a graphical way to wire together different APIs and services, enabling event-driven logic implementations. Node-RED is well known for its broad adoption in the software community and has a large number of freely available nodes that can be easily installed.

  • Page 15: Pacedge Communication And Data Flow

    Nov 2020 PACEdge Communication and Data Flow Considering that most of the services in PACEdge are implemented using Docker Containers main communication between them is implemented using network interfaces. For security reasons and traffic segregation PACEdge is using an internal user-defined bridge network, with IP subdomain address 172.18.0.0/16.

  • Page 16: Internal Communication Between Pacedge Applications

    5.2.1 Internal Communication Between PACEdge Applications To access InfluxDB and MySQL from within the PACEdge, say from Node-RED flows, certain communication parameters, and authorization data needs to be specified. Assuming that passwords are default and have not yet been changed by the user, this data is as follows InfluxDB Access Parameters: •...

  • Page 17: Pacedge Usage Examples

    PACEdge User Manual Section 6 GFK-3178B Nov 2020 Section 6: PACEdge Usage Examples Earthquake Monitor 6.1.1 Example Description This example shows how to create a Node-RED flow that periodically connects to the Internet, gets the latest earthquake reports, extracts location and magnitude values, stores data in InfluxDB, and also displays it via Node-RED Dashboard.

  • Page 18: Example Walk Through

    PACEdge User Manual Section 6 GFK-3178B Nov 2020 6.1.4 Example Walk Through 1. To store and activate example click on the Deploy button. 2. To be able to store data in InfluxDB, access to the database needs to be authorized. Double click on InfluxDB icon 3.
  • Page 19 PACEdge User Manual Section 6 GFK-3178B Nov 2020 Figure 10: Dashboard 11. The way this flow works is as follows: For each node, you can get embedded description and help by clicking on the help button on the right side and then clicking on a specific node The Start button icon triggers the flow every minute.

  • Page 20: Using The Influxdb Database

    PACEdge User Manual Section 6 GFK-3178B Nov 2020 Using the InfluxDB Database 6.2.1 Example Description This example shows how to access the InfluxDB database within the Node-RED flow. It shows how to create a new database, write to it, and read from it.

  • Page 21: Example Walk Through

    PACEdge User Manual Section 6 GFK-3178B Nov 2020 6.2.4 Example Walk Through 1. To be able to store data in InfluxDB, access to the database needs to be authorized. Double click on the InfluxDB icon 2. Click on the pencil icon to edit Server details.

  • Page 22: Example Walk Through

    Port: 1883 Note: the internal MQTT communication is designed to be used internally between PACEdge components, while external MQTT Broker can be accessed from other devices via Ethernet 2. Once flows are deployed they will start publishing messages to both internal and external MQTT brokers and the specified Topic once a second.

  • Page 23: Using Mysql Database

    PACEdge User Manual Section 6 GFK-3178B Nov 2020 Using MySQL Database 6.4.1 Example Description This example shows how to use internal and external MQTT brokers and communication. 6.4.2 Prerequisites If new to Node-RED, completion of the Earthquake Monitor example is highly recommended, as it shows some Node-RED usage basics and tips.

  • Page 24: Grafana Use Example

    Prerequisites Requires running InfluxDB Example, as described in Section 6.2. 6.5.3 Example Installation Open Grafana by using a shortcut from the PACEdge Home page. 6.5.4 Example Walk Through 1. Within Grafana, go to Configuration, then Data Sources. 2. Click on Add Data Source and select InfluxDB.
  • Page 25 PACEdge User Manual Section 6 GFK-3178B Nov 2020 Figure 14: Configuration Screen for InfluxDB 4. Click on Save & Test on the bottom, you should get the message Data source is working with green background 5. Click on Explore (on the left sidebar) 6.

  • Page 26: Pacedge Performance Indication

    OPC UA Performance Indication OPC UA Performance test was done by using two PACEdge devices: one configured to act as OPC UA Server and the other one as OPC UA Client. The server was setup to generate a large number of variables and to have them updated at the specified rate.

  • Page 27: Node Red Dashboard Performance Indication

    Grafana Node RED Dashboard Performance Indication Test Description: PACEdge with OPC UA Client reads variables, stores them in InfluxDB and finally displays the data in 20 Node RED Dashboard graphs, which are updated every second. In parallel, the Cockpit is being exercised to check utilization.
  • Page 28 PACEdge User Manual Section 7 GFK-3178B Nov 2020 Figure 16: Dashboard Update Rate Performing PACEdge Updates...

  • Page 29: Saving And Restoring User Data

    • Select either current flow or all flows option. • Click on the Download button. • Select the location (on your client system, not PACEdge) where to store the flow.json file. 8.1.2 Import Flow While in Node-RED application: • Click on the menu icon on the right side of the screen •...

  • Page 30: Exporting And Importing Views In Grafana

    • Click on the Share Dashboard icon • Click on Export. • Click on Save to file and select the location to store it on your client system (not PACEdge). 8.2.2 Import Flow While in Grafana application: • Navigate to Create icon on the left side and select the Import option.

  • Page 31: Pacedge Software Recovery

    Procedure: 1. Backup all important data from your current PACEdge system onto a USB stick or another device on the network. 2. Obtain a USB stick (minimum 8GB large) and delete all files and directories. To reduce potential issues with different partitions on the disc, which might not be visible in Windows PC, it is highly recommended to use a brand new USB stick.
  • Page 32 Figure 18: Install PACEdge Screen 7. Next, you will be asked to confirm on which disk this PACEdge needs to be reinstalled. It should be the first entry /dev/sda. Mark it with the space bar and hit enter to proceed.

  • Page 33: Pacedge Software Backup Procedure

    To proceed, please start with the same steps as in PACEdge Software Restore Procedure, but in step 6, instead of “Install …”, please select “Backup …”...

  • Page 34: Section 10: Troubleshooting

    (/home/admin/PackEdgeSoftwareInstall.<Version>). These files can be used by expert users to adapt and modify the PACEdge Docker environment to their needs and to stop and start the PACEdge system via the docker-compose command (see below). Normally there is no need to use these files.

  • Page 35: Docker Commands

    10.3 Docker Commands PACEdge is heavily based on Docker and Docker application images. Docker is a kind of lightweight virtualization allowing to group applications together in a protected self-contained environment within the Linux operating system. Setting up and configuring such a set of applications is a complex task whose description is beyond the scope of this document.

  • Page 36: Docker-Compose Up -D

    “docker-compose.yml” file, are created, configured, started, and connected. Normally there is no need to use this command, as the PACEdge environment is automatically started during system start. But it is used whenever the configuration has changed or PACEdge has been shut down by the following command: 10.5...

  • Page 37: General Contact Information

    Note: If the product is purchased through an Authorized Channel Partner, please contact the seller directly for any support. Emerson reserves the right to modify or improve the designs or specifications of the products mentioned in this manual at any time without notice. Emerson does not assume responsibility for the selection, use, or maintenance of any product.

Table of Contents