User Manual

Bazefield Asset Control

INNHOLDSFORTEGNELSE

• 1    HOW IT WORKS
• 2    ASSET CONTROL THROUGH THE API
  • 2.1    SEND COMMAND

1    HOW IT WORKS

In Bazefield there is a separate service that executes all commands sent from the portal and through the API.
 This service is called Bazefield Asset Control Service. The service runs on the master server and connects to the DataEngine on each buffer to write commands over the IO protocol used. The service has plugins for different turbine vendors to handle vendor specific logic for control.

2    ASSET CONTROL THROUGH THE API

In the Bazefield API there is endpoint to send command and list out the history of the commands. See the Bazefield API documentation on how to use the API.

2.1    SEND COMMAND

To send commands one would use the SendCommand endpoint, this can be found on the following url “turbines/{TurbineKey}/commands/{Id}/send”. The enpoint support The parametes that needs to be replaced are:

• TurbineKey – is the id or name of the turbine
• Id – is the id of the command to send

There is also a possibility to send a value with the command if the command supports it. Then the url would be “/turbines/{TurbineKey}/commands/{Id}/send/{Value}”. Here you also need to replace Value with the value you want to send.

There is also a possibility to add a comment to the command, this can either be sent on the query string as “?Comment={comment_here}”.

This request will return the command log entry created for this command.