Difference between revisions of "42Q-MES0184-IIoT Configuration"
Line 12: | Line 12: | ||
| | ||
− | = <span class="mw-headline" id="Introduction">Introduction</span> = | + | = <span class="mw-headline" id="Introduction"><span class="mw-headline" id="Introduction">Introduction</span></span> = |
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). | 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). | ||
Line 20: | Line 20: | ||
| | ||
− | = Prerequisites = | + | = <span class="mw-headline" id="Prerequisites">Prerequisites</span> = |
*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). | *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). | ||
Line 28: | Line 28: | ||
**Java Runtime Environment (JRE) version 8 or greater (included in the installation script). | **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). | **Python version 3.8 for functions that use the Python 3.8 runtime (included in the installation script). | ||
− | *Network requirements:<br/> 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: | + | *Network requirements:<br/> 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: |
− | **[https://www.amazontrust.com/repository/AmazonRootCA1.pem]. | + | **[https://www.amazontrust.com/repository/AmazonRootCA1.pem [1]]. |
− | **[https://d2s8p88vqu9w66.cloudfront.net/releases/greengrass-2.6.0.zip]. | + | **[https://d2s8p88vqu9w66.cloudfront.net/releases/greengrass-2.6.0.zip [2]]. |
**greengrass-ats.iot.us-east-1.amazonaws.com. '''Ports:''' 8443, 443. | **greengrass-ats.iot.us-east-1.amazonaws.com. '''Ports:''' 8443, 443. | ||
***.iot.us-east-1.amazonaws.com. '''Ports:''' 8883, 8443, 443. | ***.iot.us-east-1.amazonaws.com. '''Ports:''' 8883, 8443, 443. | ||
− | ***.credentials.iot.us-east-1.amazonaws.com. '''Ports:''' 443 | + | ***.credentials.iot.us-east-1.amazonaws.com. '''Ports:''' 443 |
| | ||
Line 39: | Line 39: | ||
| | ||
− | = Functional Description = | + | = <span class="mw-headline" id="Functional_Description">Functional Description</span> = |
There are three different functional components: CloudPrinting, MachineInterface, and DataIngestion.<br/> To access the Edge Devices portlet, navigate to: Shop Floor Control > Configuration > IIoT Configuration > Edge Devices. | There are three different functional components: CloudPrinting, MachineInterface, and DataIngestion.<br/> To access the Edge Devices portlet, navigate to: Shop Floor Control > Configuration > IIoT Configuration > Edge Devices. | ||
Line 63: | Line 63: | ||
| | ||
− | = Install 42Q Edge Software = | + | = <span class="mw-headline" id="Install_42Q_Edge_Software">Install 42Q Edge Software</span> = |
− | == CloudPrinting == | + | == <span class="mw-headline" id="CloudPrinting">CloudPrinting</span> == |
Please follow the steps below to create a 42Q Cloud Printing Edge Device in 42Q: | Please follow the steps below to create a 42Q Cloud Printing Edge Device in 42Q: | ||
Line 136: | Line 136: | ||
| | ||
− | === Testing Label Printing Function Using Label Engine Screens === | + | === <span class="mw-headline" id="Testing_Label_Printing_Function_Using_Label_Engine_Screens">Testing Label Printing Function Using Label Engine Screens</span> === |
#Navigate to: Administration > Label Engine Admin > Printer. | #Navigate to: Administration > Label Engine Admin > Printer. | ||
Line 176: | Line 176: | ||
| | ||
− | <br/> | + | Select the Printer Name previously created.<br/> Enter a value in the Entry field.<br/> Select Test Print. |
+ | |||
+ | Figure 11: Entering Test Print Data<br/> |
Revision as of 17:50, 13 March 2023
42Q Home > IIoT > Device Self Service
Contents
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:
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
- Users can query the list of all devices by Edge Device Name or Group Name.
- Users can create a new edge device.
- Users can view the details of the edge device.
- Users can download the software of the edge device.
- Users can upgrade this edge device with more features.
- Users can get all functional components through this button when no functional components are deployed on their local core device.
- 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:
- Navigate to: Shop Floor Control > Configuration > IIoT Configuration > Edge Devices.
- Select CREATE EDGE DEVICE to create a new Green Grass Core.
Figure 3: CREATE EDGE DEVICE Button
- 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 (-).
- 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
- Select the checkbox next to the desired Edge Device.
- Select the Download icon to download the Edge Device ZIP file.
Figure 5: Downloading The Files
- Right-click on the ZIP file.
- Select Extract Here to unzip the file.
- Open the Terminal.
- Enter the command: sudo su, and then press Enter.
- 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
- 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
- Navigate to: Administration > Label Engine Admin > Printer.
- Select Add.
Figure 8: Add Printer Button
- Enter the Printer Name.
- Select the Resolution from the drop-down list.
- 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.
- Navigate to: Production > Label Engine Labels > LE Labels.
- Search for the label called “entry”, which will print whatever "Entry" value is passed.
- Select the checkbox next to the printer name.
- Select Print.
Figure 10: Print Button
Select the Printer Name previously created.
Enter a value in the Entry field.
Select Test Print.
Figure 11: Entering Test Print Data