I am proud to announce the release of the Next Generation OPC UA IIoT Wall. This document will provide the steps to ensure a successful rollout. I'd like to thank Ranga Vadlamudi, from the IoT Central team for his late night and weekend support. I'd like to thank Hans Gschoßmann for his insights to the OPC UA integration. A final thank you to Ali Mazaheri and Chad Gronbach for their time and leadership while I struggled to rebuild the OPC UA wall into an impactful demo and showcase for our customers.

I want to add a special thank to Brad Murphy for his support and persistance! I wouldn't have been able to get this done without his support.

Please Note: The OPC UA Wall is an evolving solution and will continue to be improved through the coming weeks and months. I'll be posting a list of roadmap features and showcases that you can leverage for your customer events. If you would like to assist, I'm looking for volunteers. Reach out to me directly.

Kevin Orbaker

The HP gateway installed on the OPC wall must be installed/upgraded with the latest version of Windows 10 IoT Enterprise LTS. You must do a clean installation. Do not install any unnecessary software.

During the installation, you will need to enter a License Key. You can get the key from either Brad Murphy or Kevin Orbaker for the Windows IoT Enterprise Key.

Once you have done an installation, make sure all updates are completed prior to proceeding with the installation.

Note: You might have to run Windows Update multiple times to get all the updates.

After all Windows Updates are applied, run Disk Cleanup on the C: drive (include system files) to free up space.

This is a critical step as it must be done prior to the next steps.

The HP Gateway comes with two ethernet ports. Both ports are connected to the same switch, and by default, they both grab an IP Address from whatever DHCP server your wall is connected to.

A static IP address must be assigned to one of the ports to ensure it can communicate with the IoT devices that are plugged into the IoT Wall.

• From Windows, press Windows + R. From the Run dialog enter control panel and click OK

• From Control Panel select Network and Internet and then select Network and Sharing Center.

• From there you should see two ethernet connections. Names for these might vary (mine was labeled Ethernet and Ethernet 3). Select the first connection.

• From the Ethernet x Status Dialog, click Properties

• From the Properties Dialog, click Internet Protocol Version 4(TCP/IPv4) and click Properties

• From the Internet Protocol Version 4 dialog, click Use the following IP address: and enter the following:

  • IP address: 192.168.30.10
  • Subnet mask: 255.255.255.0

Note: Leave all other values blank.

• Click OK then Close

To confirm that you have successfully changed the IP address, make sure you can PING 192.168.30.11. If you cannot PING that IP address. You will need to validate your IP configuration, or you might have an issue with your IoT wall. Please reach out for assistance if you can't PING 192.168.30.11.

EFLOW (Edge for Linux on Windows) let's you run Auzure IoT Edge in a Linux container on Windows.

Please note that you may have a number of prompts during the installation process that will have to agree to the Microsoft EULA.

1. In an elevated PowerShell session, run each of the following commands to download IoT Edge for Linux on Windows.

   Set-ExecutionPolicy -ExecutionPolicy AllSigned -Force
   $msiPath = $([io.Path]::Combine($env:TEMP, 'AzureIoTEdge.msi'))
   $ProgressPreference = 'SilentlyContinue'
   Invoke-WebRequest "https://aka.ms/AzEflowMSI" -OutFile $msiPath
   

2. Install IoT Edge for Linux on Windows on your device.

   Start-Process -Wait msiexec -ArgumentList "/i","$([io.Path]::Combine($env:TEMP, 'AzureIoTEdge.msi'))","/qn"
   

3. Create the IoT Edge for Linux on Windows deployment. The deployment creates your Linux VM and installs the IoT Edge runtime for you.

   Deploy-Eflow -cpuCount 2 -memoryInMB 4096 -vmDiskSize 20 
   

Note: You will likely need to execute the above command two times. Durnig the first execution, you might need to restart, and then execute the above statement again.

The OPC UA IIoT Wall is hosted on IoT Central in the EXP tenant. To onboard your wall, you will need to do the following.

• Login to the OPC UA IIoT Portal with your Manager, Product Development - Engineering persona. For example: In Irvine, it is Aamil Shammas. Find the Persona for your Location here

• Select your location from the list.

• From the Device screen, select Connect in the upper left corner of the display. You will need the ID Scope, Device ID and Primary Key, to onboard your Wall during the IoT Edge runtime installation in the next step.

  

• Use the ID scope, Device ID and the Primary Key you made a note of previously

  Provision-EflowVm -provisioningType DpsSymmetricKey -scopeId <ID_SCOPE_HERE> -registrationId <DEVCIE_ID_HERE> -symmKey <PRIMARY_KEY_HERE>
  

Once you have successfully deployed EFLOW on your gateway device, it will take a few minutes for IoT Central to push down all the updates.

It should look similar to below.

Your OPC UA IIoT wall has been deployed and is ready for use. You should see Beckhoff Telemetry being sent to your wall.

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.

When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.

This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft trademarks or logos is subject to and must follow Microsoft's Trademark & Brand Guidelines. Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. Any use of third-party trademarks or logos are subject to those third-party's policies.