# Virtual Station Mapping Configuration

A virtual station in a controller and the fieldbus master communicate by exchanging a fieldbus map between each other.

One or more fieldbus maps are combined into a Process Data Frame, which is sent on the physical communication link between the controller and the fieldbus master.

Fieldbus Virtual Station Mapping Configuration
Column | Function
--- | ---
Check box | Select or deselect a mapping.
Virtual station | Name of virtual station.
Fieldbus configuration | The fieldbus map.
To/From controller offset | Starting point of the fieldbus map within the Process Data Frame.

Acyclic Virtual Station Mapping Configuration
Column | Function
--- | ---
Check box | Select or deselect a mapping.
Virtual station | Name of virtual station.
Acyclic configuration | The acyclic data map.
Start Instance | First instance number of the acyclic data. Default/minimum instance number: 2048.
End Instance | Last instance number of the acyclic data. Maximum instance number: 65535. The maximum size of the instance varies between the different fieldbus types.
No of Instances | Number of instances that are required to send the acyclic data. For example, if the Data instance size is set as 64 and the Start Instance is 2048 and the End Instance is 2060, then the No of instances are 13 and the maximum size for the acyclic configuration will be 832 bytes . The No of instances are generated automatically based on the Start Instance and End Instance.
Size in Bytes | Maximum size of the acyclic configuration based on the selected Data instance size, Start Instance and the End Instance.

The total size of the acyclic data should not exceed 65536 bytes.

A virtual station can only have one acyclic fieldbus configuration mapped, but an acyclic fieldbus configuration can be mapped to many virtual stations.

Relevant Information

- Pushing Configurations to a Controller

In this Section

- Adding a Fieldbus Mapping
- Adding an Acyclic Fieldbus Mapping
- Viewing a Fieldbus Map assigned to a Virtual Station