Connected Factory April 2019

Microsoft has released the April 2019 update of the Connected Factory solution accelerator.

This update comprises the following changes:

• Replace Proxy with OPC Twin for browsing, accessing (read, write, call) and publishing server nodes
• Add IoT edge Gateway page
• Update endpoint list page
• Update several NuGet packages because of reported vulnerability
• Update WebApp project to .NET 4.6.1

Connected Factory October 2018 patch 1

This patch removes changes how docker is installed into the VM. It has been earlier installed via the ARM template and is now installed at runtime via the initialization shell script.

Connected Factory October 2018

Microsoft has released the October 2018 update of the Connected Factory solution accelerator.

This update comprises the following changes:

• Increase resilience of the browsing page in the Dashboard if the browsed OPC Server reports errors
• Update OPC UA stack NuGet package because of reported vulnerability
• Add missing dependency in ARM template
• Various text and hyperlink updates in resources and comments

Connected factory August 2018 patch 2

This patch fixes a deployment problem on www.azureiotsolutions.com.

Connected factory August 2018 patch 1

This patch fixes a few regressions in the August 2018 release:

• The map is now shown also for subscriptions with an Bing Maps license
• The KPI and OEE values are now shown correct
• TSI links for certain alerts are now working

Connected factory August 2018 release

Microsoft has released the August 2018 update of the Connected factory solution accelerator.

This update comprises the following changes:

• Use Azure Maps instead of Bing Maps
• Fix an issue which caused indefinite certification validation loop when connecting to an OPC UA server using an IP address
• Fix an issue which prevented to publish/unpublish nodes when connected to an OPC UA server using an IP address
• Fix an issue which prevented that new nodes of new OPC UA servers where showing up in the dashboard
• Fix an issue which prevented that TSI data of new OPC UA servers where shown correct
• Fix a couple of typos
• Update to newer version of jquery and bootstrap

Connected factory April 2018 patch 1

There is the following change in this patch:

• change the ARM template to adjust the MSIDeploy RP API version

Connected factory April 2018 release

Microsoft has released the April 2018 update of the Connected factory preconfigured solution.

This update comprises of the following:

• Update the OPC packages to the latest versions
• Update to the latest version of proxy, which fixes a endless loop in certain conditions
• Adds a workaround for a bug in the Azure ARM deployment

Connected factory January 2018 release

Microsoft has released the January 2018 update of the Connected factory preconfigured solution.

This update comprises of the following:

• Update resource files with latest translations.
• Adjust to Azure PowerShell 5.x, update PSCX and Posh-SSH cmdlets.
• Use iot-edge-opc-publisher 2.1.4 and update readme.
• Add pushpin functionality for images
• Add verification steps to readme.md
• Shutdown tasks on application shutdown.
• Cleanup obsolete topology relevance tags
• Change App plan instance count default to 1.
• Fix msbuild call to allow spaces in path.
• Fix scrolling reset on signalR refresh
• Simplify adm mode by compilation.
• Update world static image to new dark theme

Connected factory November 2017 release

Microsoft has released the November update of the Connected factory preconfigured solution.

This update comprises of the following:

• Update the UX design to align with UX design of PCSv2 solutions
• Enable showing the last value of telemetry in the dashboard

Notes:
With Connected factory 1711 release the most recent value of a node value is shown in the dashboard. If you are deploying just the 1711 WebApp (in contrast of deploying the whole Cf solution), you need to make a couple of changes in your existing deployment:

• Add an additional consumer group to your IoTHub
  In the Azure portal go to the IoTHub of your deployment. Under ‘Endpoints’ select the endpoint ‘Events’ and add a new consumer group ‘telemetrycg’ (beside the $Default consumer group there is till now one other consumer group with name ‘rdxcg’)
  Please also copy the ‘Event Hub-compatible name’ and the ‘Event Hub-compatible endpoint’ shown in the ‘Device-to-cloud settings’ blade (this is where you added the consumer group), since you need it in the next step.

• Add additional App settings to your AppService
  In the Azure portal go to the App Service of your deployment. Under ‘Application Settings’ in the ‘AppSettings’ section add the following new variables:

  • IotHubTelemetryConsumerGroup
    The value of this variable should be set to ‘telemetrycg’.
  • IotHubEventHubName
    The value of this variable should be set to the ‘Event Hub-compatible name’ of the ‘Events’ endpoint of your IoTHub you saved in the step before.
  • IotHubEventHubEndpointIotHubOwnerConnectionString
    The value of this variable should be set to the ‘Event Hub-compatible endpoint’ of the ‘Events’ endpoint of your IoTHub you saved in the step before.

The WebApp reads the telemetry shown as the last value directly from the telemetrycg consumer group of IoTHub and saves its checkpoint information in the telemetrycheckpoints blob of the storage account. By deleting the files in this blob, the dashboard will show telemetry values starting at the time of the app start, otherwise it will start showing values starting from the last checkpoint.