Skip to content
Azure IoT Edge modules for remote monitoring and predictive maintenance ABB ACS electric drive solution
C#
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
AbbEdge
Docs
iot-edge-modbus
AbbEdge.code-workspace
README.md
abbDriveProfile.sln

README.md

SmartHive.AbbEdge is an IoT Edge device gateway, remote monitoring and predictive maintenance modules for ABB ACS drive managed electric motors

Video

Architecture pieces

Architecture diagram

How to deploy

  • Install '>FENA module and configure ModBus TCP support to collect ABB drive telemetry from IoT Edge gateway over Ethernet network
  • Deploy Azure remote monitoring solution accelerator into your Azure subscription via www.azureiotsuite.com or manually
  • Find resource group with deployed Remote monitoring solution in your Azure subscription and open IoT Hub Azure Service instance. Use it in future steps.
  • Deploy Azure IoT Edge runtime on some IoT Gateway devices. Connect this deices into the same Ethernet network as ACS Drive FENA adapter. Assign correct IP address and make sure your IoT Gatewy devices can ping ABB FENA adpater.
  • Deploy and configure IoT Edge modules
    1. On the Azure portal, go to your IoT hub.
    2. Go to IoT Edge and click on your IoT Edge device.
    3. Select Set modules.
    4. Click Add and select IoT Edge module.
    5. Add modbus module as described here
    6. Add abbDriveProfile module as describedhere
    7. Add abbRemoteMonitoringGateway module as describedhere
    8. Select Next.
    9. In the Specify Routes step, copy the following JSON into the text box.

      "routes": {
      	"modbusToAbbAcsEdgeProfile": "FROM /messages/modules/modbus/outputs/modbusOutput INTO BrokeredEndpoint(\"/modules/abbDriveProfile/inputs/driveProfileInput\")",
      	"abbDriveProfileToRemoteMonitoringGateway": "FROM /messages/modules/abbDriveProfile/outputs/driveProfileOutput INTO BrokeredEndpoint(\"/modules/abbRemoteMonitoringGateway/inputs/gatewayInput\")",          
      	"abbRemoteMonitoringGatewayToIoTHub": "FROM /messages/modules/abbRemoteMonitoringGateway/outputs/* INTO $upstream"
      }
      		
      • Route "modbusToAbbAcsEdgeProfile" sends all messages collected by the Modbus module to abbDriveProfile module for actual parameters calculation. In this route, ''modbusOutput'' is the endpoint that Modbus module use to output data, and driveProfileInput is the endpoint that abbDriveProfile use for reading data and calculate actual parameter values based on modbus register values
      • Route "abbDriveProfileToRemoteMonitoringGateway" sends all actual parameters calculated by abbDriveProfile to abbRemoteMonitoringGateway for transforming data into format required for Azure remote monitoring solution accelerator. In this route, ''driveProfileOutput'' is the endpoint that abbDriveProfile module use to output data, and gatewayInput is the endpoint that abbRemoteMonitoringGateway use for reading data and tarasofrm data to Azure remote monitoring solution telemetry format.
      • Route ''abbRemoteMonitoringGatewayToIoTHub''ends all telemetry messages formatted by "abbRemoteMonitoringGateway" module to output data, and ''upstream'' is a special destination that tells Edge Hub to send messages to IoT Hub.

      • Select Next.

      • In the Review Deployment step, select Submit.
      • Return to the device details page and select Refresh. You should see the new modbus module running along with the IoT Edge runtime.
  • Use IoT Hub Device Explorer to trace messages from ACS drive to IoT Hub
  • Check your Azure remote monitoring solution web portal graphs for telemetry
You can’t perform that action at this time.