Unsolicited data involves a device sending data to a physical point in BASEstar Classic device connection management BASEstar Classic device connection management requesting it. BASEstar Classic device connection management can accept unsolicited values from any device, as long as the device is defined as unsolicited and physical points are defined with unsolicited information.

All unsolicited data is sent over the unsolicited TSAP which is defined by specifying the name of the unsolicited TSAP in the /NETADDR definition of the Siemens device.

Siemens devices are capable of sending unsolicited messages to the host. The DAS for Siemens H1 Protocol allows you to define BASEstar Classic device connection management physical points for collecting unsolicited data. If the device sends an unsolicited message, the DAS forwards the message to BASEstar Classic device connection management.

An unsolicited message consists of a message header followed by the unsolicited data. The message header must have the following format:

• First longword : any positive integer value
• Second longword : 0

To define a physical point having an unsolicited ID, use the following qualifier: /UNSOLICITED=xxxx

Where xxxx is any positive integer value that fits in a longword and that will uniquely identify an unsolicited message.

The /ADDRESS qualifier of an unsolicited physical point can contain any valid point address (See Section 3.2.4).

Unsolicited messages are received in the DAS by posting an unsolicited read on the unsolicited TSAP. When the device sends an unsolicited message over this TSAP, the read is completed and sent to BASEstar Classic device connection management.

If the first longword of the received message matches a physical point unsolicited ID and if the second longword of the received message has been set to 0, then the BASEstar Classic device connection management will be updated with the data part of the message.

3.3.2 Pollsets

BASEstar Classic device connection management physical points may be grouped together into pollsets to optimize data collection.

Data can be polled on the read TSAP or on the unsolicited TSAP.

Pollsets created for the Siemens devices have the following limitations:

• Physical points of differing data types cannot be part of the same pollset.
  For example, a physical point of type WORD and a physical point of type BYTE cannot be members of the same pollset. Physical points of the same data type with varying element counts can reside in the same pollset.
• A pollset used with the unsolicited TSAP can only contain one physical point.
• Physical points with different block types cannot be part of the same pollset.
• Physical points with different block numbers cannot be part of the same pollset.

For more information on physical points, see the BASEstar Classic Command Line Interface User's Guide.