Acyclic Data Configuration Menu

Name

Name of the selectable configuration in virtual station mapping.

Max size

This value will be manually set until it is mapped to a virtual station. This value makes sure that the configuration fits within the selected instances in mapping. The value is calculated from the required number of instances, according data record size.

First channel or bolt offset

Address of the first channel or bolt offset. This defines the size of the common area.

Bolt or channel template size

Size of the bolt or channel.

Select channel by

Bolt or Channel. This value defines if the Identifier of each result configuration item is bolt or channel.

Data layout

Select between:

• Compact data layout - If the channel or bolt selected in the acyclic configuration does not exist in the current Sync Mode or system run, then that specific data will not be written on the fieldbus. Instead, the next channel/bolt that is present in the Sync Mode will be written in that space in the fieldbus data and will impact the offsets of all of the following bolts/channels. This only applies to whole bolts/channels and not to individual items or values inside a configured bolt/channel.

• Fixed data layout - The entire configured acyclic data will be written on the fieldbus regardless of how the current Sync Mode, Tightening Program, or system is configured. If no data can be found for an item, then the Non existing values will be written instead. This can be the case for entire bolts/channels. Reasons as to why there is no data written could be that the bolt does not exist in the current Sync Mode, the channel is inhibited, no restriction/monitor has been chosen in the Tightening Program, or the step selected does not have a restriction/monitor.

Add header

Select the check box to indicate that a header must to be added to the acyclic configuration result. When the checkbox is marked, the offset will be updated with 6 bytes lower or higher, depending on the usage. This is also visible graphically. The header can only be added if there is space available. If items are added in the common area and there is no space for the header, it is disabled.

If the Compact data layout is chosen, it is strongly recommended to use the header in order to know the length of the acyclic data payload.

Non existing values

Non existing values for different data types are used if the configuration wants data that is not present in the tightening result or in the multistage configuration.

When a new acyclic fieldbus is created, the values will be set automatically from the controller.