---
alias: user-guide-automation-controller-workflow-setup
tags:
- connect iot
description: "Configure a setup workflow for drivers to enable automation controller functionality and communication initialization"
---

# Create the Setup Workflow

For the automation controller to work properly, it is required to configure a setup workflow for each of the drivers used.

If you wish to perform that action, choose **Views** and **Workflow**, as seen below.

![WFlow1][WFlow1]

A Setup page is created automatically and some changes should be done. Each of the driver's blocks is highlighted in a color previously specified at the Automation Controller/Driver Definitions' creation step. See [Create Automation Controller](create_automation_controller.md).

![WFlow2][WFlow2]

## Settings

Some settings can be changed in each of the drivers. These settings are protocol-specific and can be different in another driver.

To change the settings, tick the *Setup* case and choose **Settings**.

![Settings1][Settings1]

A new pop-up window will be displayed in the first page, where some settings can be changed.

* Name - the name of the block.
* Description - the description of the block.
* Reconnect interval - the time to wait to try to reconnect to the equipment after the connection is lost or has failed.
* Reconnect max attempts - maximum number of tries before it changes to idle state. After this, a manual action must be done to restart the communication.
* Require buffering - active or inactive.

![Settings2][Settings2]

In the second page of the settings, the protocol-specific settings can be changed, a list will appear in the left side of the page and when an item is selected, the value can be changed.

![Settings3][Settings3]

## Workflow

For each Driver, some connections must be performed to allow the driver to successfully start the communication's initialization.  See the next image as an example.

* Connect the onInitialize output (1) to the connect input (2) of the 'OnEquipment Setup' block; this will result in the driver trying to connect to the defined equipment.
* Connect the onSetup output (3) of the 'OnEquipment Setup' to the success input of the 'Equipment Setup Result'; after the communications are established the driver will do whatever it is necessary for the protocol initialization; it is protocol dependant and is different for each protocol.
* It is allowed to perform some customized tasks between these two blocks, however, after all is done, it is mandatory that the success input is invoked.

![WFlow3][WFlow3]

[Settings1]: images/workflow_automation_controller_settings_1.png
[Settings2]: images/workflow_automation_controller_settings_2.png
[Settings3]: images/workflow_automation_controller_settings_3.png
[WFlow1]: images/create_setup_workflow.png
[WFlow2]: images/automation_controller_settings_1.png
[WFlow3]: images/workflow_automation_controller_3.png