42Q-MES0184-IIoT Configuration

42Q Home > IIoT > Device Self Service

 

 

 

IIoT Device Self Service Version MES 15.76 Revision B1  

 

 

 

Introduction

The concept of GGC stands for “Green Grass Computer”, the word: “Computer” also refers to any kind of device. This document will teach users how to configure, install, and deploy a GGC, as well as create and set up an Edge Device for the purpose of establishing a connection between the computer (device) and the 42Q portal to send data (payloads).

 

 

Prerequisites

• Only Linux is supported for the computer or device to install the Green Grass Core. The related shell scripts and test code only work on Linux systems (Windows is not currently supported).
• Python 3.8 or higher must be installed and configured to run the test code.
• Operating System and  Software requirements:
  • Linux kernel version 4.4 or later (Ubuntu 20.04 and CentOS 8.5).
  • Java Runtime Environment (JRE) version 8 or greater (included in the installation script).
  • Python version 3.8 for functions that use the Python 3.8 runtime (included in the installation script).
• Network requirements:
  A Region is an AWS region that hosts 42Q portal APIs. The Green Grass Core hardware needs to be able to access the following endpoints through specific ports:
  • [1].
  • [2].
  • greengrass-ats.iot.us-east-1.amazonaws.com. Ports:   8443, 443.
    • .iot.us-east-1.amazonaws.com. Ports:  8883, 8443, 443.
    • .credentials.iot.us-east-1.amazonaws.com. Ports: 443

 

 

Functional Description

There are three different functional components: CloudPrinting, MachineInterface, and DataIngestion.
To access the Edge Devices portlet, navigate to: Shop Floor Control > Configuration > IIoT Configuration > Edge Devices.

Figure 1: Accessing Edge Devices

 

Figure 2: Edge Devices Functions

800px

 

1. Users can query the list of all devices by Edge Device Name or Group Name.
2. Users can create a new edge device.
3. Users can view the details of the edge device.
4. Users can download the software of the edge device.
5. Users can upgrade this edge device with more features.
6. Users can get all functional components through this button when no functional components are deployed on their local core device.
7. Users can delete the edge device.

 

 

Install 42Q Edge Software

CloudPrinting

Please follow the steps below to create a 42Q Cloud Printing Edge Device in 42Q:

1. Navigate to: Shop Floor Control > Configuration > IIoT Configuration > Edge Devices.
2. Select CREATE EDGE DEVICE to create a new Green Grass Core.

 

Figure 3: CREATE EDGE DEVICE Button

800px

 

3. Enter the Edge Device Name of the Green Grass Core. The name can be up to 128 characters. Valid characters are: a-z, A-Z, 0-9, colon (:), underscore (_), and hyphen (-).
4. Select the Group Name as CloudPrintingGroup.

Note: After selecting the Group Name, the Group Version will automatically be selected.

 

Figure 4: Create Edge Device Form

 

5. Select the checkbox next to the desired Edge Device.
6. Select the Download icon to download the Edge Device ZIP file.

 

 

Figure 5: Downloading The Files

 

7. Right-click on the ZIP file.
8. Select Extract Here to unzip the file.
9. Open the Terminal.
10. Enter the command: sudo su, and then press Enter.
11. Enter the root user’s password, and then press Enter.

Note: If the word: root@ appears before the computer’s username as in the image below, it means that you are logged in as a root user.

 

Figure 6: User Logged In as a Root User

 

12. Enter the next command: sh ggcV2.sh, and then press Enter.

Note: After the script is installed successfully, users can navigate to the local device’s path: /greengrass/v2 to check the installed folder; logs are contained in the path: /greengrass/v2/logs.

 

Figure 7: Edge Device Folder

 

Testing Label Printing Function Using Label Engine Screens

1. Navigate to: Administration > Label Engine Admin > Printer.
2. Select Add.

 

Figure 8: Add Printer Button

 

3. Enter the Printer Name.
4. Select the Resolution from the drop-down list.
5. Select the Connectivity Type as Edge Device.

 

Figure 9: Entering The Printer Details

 

Note: The TCP IP Address should be the address of the printer or start a TCP Server as a simulator by executing the next command in the Terminal: python3 tcpServer.py.

 

6. Navigate to: Production > Label Engine Labels > LE Labels.
7. Search for the label called “entry”, which will print whatever "Entry" value is passed.
8. Select the checkbox next to the printer name.
9. Select Print.

 

Figure 10: Print Button

 

10. Select the Printer Name previously created.
11. Enter a value in the Entry field.
12. Select Test Print.

 

 

Figure 11: Entering Test Print Data

 

13. Open the Terminal.
14. Navigate to the local device’s path: /greengrass/v2/logs.
15. Enter the next command: tail -f {envide}_CloudPrinting.log. After that, a message will be received to confirm the successful testing.

 

 

Figure 12: Successful Testing Message

 

MachineInterface

This function is used for sending commands to machines from the cloud.
Below there is an example for stopping a machine when the server finds MSD material expired.

 

 

Figure 13: Server Stopping A Machine Due To Material Expired Diagram

800px
 

The diagram above is divided into three steps:

1. Install an Edge Device on a server in the plant.
2. The plant creates a new local application which can communicate with the Edge Device by TCP and also can send commands to machines.
3. The Cloud application will send commands to the Edge Device, then the Edge Device will forward the message to the local application through TCP/IP.

Please follow the steps below to create a 42Q Cloud Machine Interface Edge Device in 42Q:

1. Navigate to: Shop Floor Control > Configuration > IIoT Configuration > Edge Devices.
2. Select CREATE EDGE DEVICE to create a new Green Grass Core.
3. Enter the Edge Device Name of the Green Grass Core. The name can be up to 128 characters. Valid characters are: a-z, A-Z, 0-9, colon (:), underscore (_), and hyphen (-).
4. Select the Group Name as MachineInterfaceGroup.

Note: After selecting the Group Name, the Group Version will automatically be selected.

 

5. Select the checkbox next to the desired Edge Device.
6. Select the Download icon to download the ZIP file.
7. Right-click on the ZIP file.
8. Select Extract Here to unzip the file.
9. Open the Terminal.
10. Enter the command: sudo su, and then press Enter.
11. Enter the root user’s password, and then press Enter.
12. Navigate to the extract folder by using the command: cd {folder path}.
13. Enter the next command: sh ggcV2.sh, and then press Enter.

Note: After the script is installed successfully, users can navigate to the computer’s path: 
/greengrass/v2 to check the installed folder; logs are contained in the path: /greengrass/v2/logs.

 

14. Open Postman to test its functionality.
15. Select POST as HTTP Method.
16. Enter the URL.
17. Enter the Topic.
18. Enter the Output.
19. Enter the Error.

 

Data nomenclature:
URL: https://portal-sqa.42-q.com/mes-api/[SiteName]/greengrass/v2/publish
Topic: [Envide]/machine-interface/[Envide]_[Edge device name]
Output: [Envide]/machine-interface/results
Error: [Envide]/machine-interface/errors

 

Figure 14: Sending The Payload Using Postman

800px
 

21. Navigate to the local device’s path: /greengrass/v2/log to view the logs.

 

 

Figure 15: Successful Payload Sending Logs

 

Note: If the message from the previous image is printed in your local log, the function has succeeded.
Adding the corresponding configuration for PTS allows PTS to send messages to Edge Device.

 

DataIngestion

Please follow the steps below to create a 42Q Cloud Data Ingestion Edge Device in 42Q:

1. Navigate to: Shop Floor Control > Configuration > IIoT Configuration > Edge Devices.
2. Select CREATE EDGE DEVICE to create a new Green Grass Core.
3. Enter the Edge Device Name of the Green Grass Core. The name can be up to 128 characters. Valid characters are: a-z, A-Z, 0-9, colon (:), underscore (_), and hyphen (-).
4. Select the Group Name as DataIngestionGroup.

Note: After selecting the Group Name, the Group Version will automatically be selected.

 

5. Select the checkbox next to the desired Edge Device.
6. Select the Download icon to download the ZIP file.
7. Right-click on the ZIP file.
8. Select Extract Here to unzip the file.
9. Open the Terminal.
10. Enter the command: sudo su, and then press Enter.
11. Enter the root user’s password, and then press Enter.
12. Enter the next command: sh ggcV2.sh, and then press Enter.

Note: After the script is installed successfully, users can navigate to the computer’s path: /greengrass/v2 to check the installed folder; logs are contained in the path: /greengrass/v2/logs.

 

13. When the status of this Edge Device is "Healthy", select the Edit button to enter the Edge Device information.

 

Figure 16: Edit Button

 

14. Select the CLIENT DEVICES tab.
15. Select CREATE CLIENT DEVICES.

 

Figure 17: CLIENT DEVICES TAB

 

16. Enter the name of the Client Device to be created.

Note: The name can be up to 128 characters. Valid characters: a-z, A-Z, 0-9, colon (:), underscore (_), and hyphen (-).

17. Select ASSOCIATE.

 

 

Figure 18: Creating a Client Device

 

18. Select the Download icon to download the Client Device ZIP file.
19. Right-click on the ZIP file.
20. Select Extract Here to unzip the file.

 

Figure 19: Client Device Folder

800px

 

21. Open the MqttTest.py file.
22. Find the line that contains: ‘# Change This’.
23. Modify the data information to be sent; users may see an example below (user’s will be different).

 

Figure 20: Data To Be Modified

800px

24. Open the Terminal.
25. Enter the next command: python MqttTest.py, and then press Enter. The result should be similar to the image below:

 

Figure 21: Result Of Executing The MqttTest.py File

 

26. Navigate to the local device’s path: /greengrass/v2/log to view the logs.

 

 

Figure 22: Successful MqttTest.py Running Logs

 

Note: If the message from the previous image is printed in your local log, the function has succeeded.

 

1. Navigate to: Shop Floor Control > Configuration > IIoT Configuration > Things.

 

Figure 23: Things Portlet

 

28. If the “Thing ID” is the same as the “id” configured in MqttTest.py file, it means that AWS Cloud has already stored the data uploaded.

 

 

Figure 24: Thing ID

 

29. Navigate to: Reporting > IIoT Dashboard.
30. Select the + icon to create a new widget.

 

 

Figure 25: Add (+) Icon

 

31. Enter the Widget Name.
32. Select the THINGS tab.
33. Select the "id" value previously configured in the MqttTest.py file.
34. Select the SAVE button located at the end of the Add Widget Form.

 

Figure 26: Creating a Widget

 

35. Select the show/hide icon to view the values of the widget created.

 

Figure 27: Show/Hide Icon

Note: Users can check the payload sent through either of the following:

• IIoT widget.