Examples
  • 10 Oct 2022
  • 2 Minutes to read
  • PDF

Examples

  • PDF

Article summary

Connecting to an ABB inverter using Aurora Client

In this example, the data will be obtained from an ABB inverter.

Below you can find a file containing a couple of template examples for both an inverter and a junction box respectively. These templates will make it much easier for users to get started using the module and creating a model in no-time, with minimal adjustments. 


  • Step 1: Create a new module: (Config => Modules => New module)

Figure 7. Create a new module


  • Step 2: Provide a name for the module (in this example, AuroraClienthas been used) and set the module type to AuroraClient in Module Type. 

Figure 8. Configure the module


  • Step 3: Configure the Logger and API for this module. In this example, the default configuration has been left unchanged since, in most cases, this is a valid configuration.
  • Step 4: Create a new channel (Config => Modules => AuroraClient => Model => New Channel).

Figure 9. Create a new Channel


  • Step 5: Configure the connection as shown in the below image.

Figure 10. Configure the channel

For this example, the following fields have been configured:

  • Connection
    • Type: TCP.
  • Config
    • Host: 10.101.3.211, which is the device's IP address. 
    • TCP port: By default, port 4001 is used.
  • Step 6: Create a new device (Config => Modules => AuroraClient => Model => Channel01 => New Device).

Figure 11. Create a new device


  • Step 7: Configure the device and give it a name. In this case, the device's name is Device01.

Figure 12. Configure the device


At this point, the connection is ready and we can now move on to creating new tags using the templates provided above.

  • Step 8: Import the templates.

Figure 13. Import Templates


  • Step 9: Create a new instance for the template Aurora_ABB_Inverter.

Figure 18- Create a new groupFigure 14. Create a new instance


In the below image, you can see the created instance with all the different subgroups and parameters contained within it.

Figure 19- Instance parametersFigure 15. Instance properties


  • Step 10: Adapt the imported template for your specific application. 

Users can modify, add, or remove Custom properties for the template according to their needs. 

  • Custom properties
    • Device: This property must follow the Channel_name/Device_name format. In this case, Channel01/Device01 is used. 
    • Module: Enter the name of the module you created previously. In this case, AuroraClient.
    • Rate: Select the appropriate rate, in this example 15,000.

Figure 20- Configure custom propertiesFigure 16. Configure the custom properties


You should also adjust the source section of every tag according to your needs. The most straightforward way to do this is by exporting the template configuration to a CSV file, modifying it, and uploading it again, which will overwrite the previous configuration. 

Figure 21- Tag source sectionFigure 17. Configure the tag source section


In this example, the following configuration is used:

  • Source
    • Enabled: Yes.
    • Module type: AuroraClient.
    • Module name: Custom property.
    • Config
      • Device: Custom property.
      • Scan rate: Custom property.
      • Group: 78: Cumulated energy.
      • Variable: Daily energy.

  • Step 11: Navigate to the Real-Time section and check that everything is working properly.

Figure 22- Real time ValuesFigure 18. Real-Time values



Was this article helpful?

What's Next