# BASEstartm Classic DAS
for OMNItm Software
Installation and User's Guide

Previous | Contents | Index

# Appendix B
Logged Messages

The messages in the following sections are logged to the BASEstar Classic history file by the DAS for OMNI software. These messages are logged to provide more detailed diagnostic information than what is supplied by the returned status values.

Messages logged to the history file for DAS for OMNI software use event class 21 and event type 32.

To view all messages logged by this DAS use the following syntax:

    $ BSTAR
    BSTAR> SHOW HISTORY/EVENT=21.32.*

OMNI software returns status results in an I/O status block consisting of three status fields, General, Provider and Network. The DAS logs each of these error statuses (if present) when logging status results.

# B.1 NI Logged Messages

The following messages are logged by the Network Interface (NI).

Unable to initialize OMNI.
Explanation: Error. The call to omni_initialize failed.
User Action: Check the status returned and take action based on the status.

# B.2 PE Logged Messages

The following messages are logged by the Protocol Emulator (PE).

Error calling omni_abort ().
Explanation: Error. The call to omni_abort failed.
User Action: Check the status returned and take action based on the status.

Device !AD connected.
Explanation: Informational. The DAS has successfully connected to the device.
User Action: None.

Device !AD connection aborted.
Explanation: Informational. The connection to the device has been successfully aborted.
User Action: None.

Device !AD association concluded by the presentation layer.
Explanation: Informational. The DAS has successfully accepted a request to conclude the association. The DAS submits a request to Device Connection Management to abort the connection and to transition the device to not connected and not reachable.
User Action: None.

Device !AD association concluded by the device.
Explanation: Informational. The DAS has received a conclude indication. The DAS submits a request to Device Connection Management to abort the connection and to transition the device to not connected and not reachable.
User Action: None.

Device !AD association aborted.
Explanation: Informational. The DAS has received an abort indication. The DAS submits a request to Device Connection Management to abort the connection and to transition the device to not connected and not reachable.
User Action: None.

Error creating local VMD.
Explanation: Error. An error occurred when attempting to create the local VMD using the OMNI API.
User Action: Examine the error message returned and take action based on the error found.

Error creating remote VMD.
Explanation: Error. An error occurred when attempting to create the remote VMD using the OMNI API.
User Action: Examine the error message returned and take action based on the error found.

Error calling omni_connect ().
Explanation: Error. An error occurred when attempting to connect to the remote VMD using the OMNI omni_connect service.
User Action: Examine the error message returned and take action based on the error found. Check local and remote ODS configurations. Check physical and network connections to the device.

Error creating simple OMNI type !AD for point !AD.
Explanation: Error. An error occurred when attempting to create the given data type. The DAS attempts to create named types for all "simple" (i.e. not a structure or array) data types.
User Action: Examine the error message returned and take action based on the error found.

Error creating structure OMNI type !AD for point !AD.
Explanation: Error. An error occurred when attempting to create the given data type. The data type name is formed from the fields in the structure so that the same structure definition can be used for multiple physical points.
User Action: Examine the error message returned and take action based on the error found.

Error creating array OMNI type !AD for point !AD.
Explanation: Error. An error occurred when attempting to create the given data type. The data type name is formed using the number of elements in the array so that the same array definition can be used for multiple physical points.
User Action: Examine the error message returned and take action based on the error found.

Error creating domain !AD for point !AD.
Explanation: Error. An error occurred when attempting to create a domain for a physical point that has a domain name embedded in it.
User Action: Examine the error message returned and take action based on the error found.

Error creating named variable for point !AD.
Explanation: Error. An error occurred when attempting to create a named variable for the physical point. The name of the named variable is taken from the address field of the physical point.
User Action: Examine the error message returned and take action based on the error found.

Error creating unnamed variable for point !AD.
Explanation: Error. An error occurred when attempting to create an unnamed variable for the physical point.
User Action: Examine the error message returned and take action based on the error found.

Error creating a message for point !AD.
Explanation: Error. (SINEC-AP devices only.) An error occurred when attempting to create a message for the physical point. The message object is used to transfer messages to and from the device.
User Action: Examine the error message returned and take action based on the error found.

Error compiling BASEstar logical point !AD.
Explanation: Error. An error occurred when calling BCC$COMPILE_POINT_NAME for the given logical point. The logical point name is contained in the unsolicited ID of the physical point being configured for unsolicited data collection.
User Action: Examine the error message returned and take action based on the error found.

Error getting physical status attribute.
Explanation: Error. An error occurred when calling omni_get_attribute with an attribute of omni_c_attr_physical_status. This call is made to decode the results of an omni_get_remote_attributes call or of an unsolicited status indication.
User Action: Examine the error message returned and take action based on the error found.

Error getting logical status attribute.
Explanation: Error. An error occurred when calling omni_get_attribute with an attribute of omni_c_attr_logical_status. This call is made to decode the results of an omni_get_remote_attributes call or of an unsolicited status indication.
User Action: Examine the error message returned and take action based on the error found.

Error getting vendor name attribute.
Explanation: Error. An error occurred when calling omni_get_attribute with an attribute of omni_c_attr_vendor. This call is made to decode the results of an omni_get_remote_attributes call.
User Action: Examine the error message returned and take action based on the error found.

Error getting model name attribute.
Explanation: Error. An error occurred when calling omni_get_attribute with an attribute of omni_c_attr_model. This call is made to decode the results of an omni_get_remote_attributes call.
User Action: Examine the error message returned and take action based on the error found.

Error getting revision number attribute.
Explanation: Error. An error occurred when calling omni_get_attribute with an attribute of omni_c_attr_revision. This call is made to decode the results of an omni_get_remote_attributes call.
User Action: Examine the error message returned and take action based on the error found.

Error getting local detail attribute.
Explanation: Error. An error occurred when calling omni_get_attribute with an attribute of omni_c_attr_local_detail. This call is made to decode the results of an omni_get_remote_attributes call or of an unsolicited status indication.
User Action: Examine the error message returned and take action based on the error found.

Error calling omni_get_remote_attributes ().
Explanation: Error. An error occurred when calling omni_get_remote_attributes. This routine is called when a "READ STATUS" command is done from the BASEstar Device Connection Management CLI.
User Action: Examine the error message returned and take action based on the error found.

Error writing value for point = !AD.
Explanation: Error. An error occurred when calling omni_put_value for the given physical point. (This error can also be logged when calling omni_exchange_data or omni_send_value.) The most likely cause for this error is that the variable does not exist in the remote VMD or that the data types do not match.
User Action: Examine the error message returned and take action based on the error found.

Error reading value for point = !AD.
Explanation: Error. An error occurred when calling omni_get_value for the given physical point. (This error can also be logged when calling omni_exchange_data.) The most likely cause for this error is that the variable does not exist in the remote VMD or that the data types do not match.
User Action: Examine the error message returned and take action based on the error found.

Read not allowed from unacknowledged write point !AD.
Explanation: Error. An attempt was made to read a physical point that has an address of "MW\YYY" where "YYY" is the name of the message. "MW" physical points are message physical points that can be written to only.
User Action: Redefine the physical point to allow both reads and writes or do not attempt to read from the physical point. If the physical point is connected to a logical point, use SHOW POINT/VALUE=LAST to show the last value written to the logical point. If the physical point is redefined, Device Connection Management may need to be restarted for the change to take effect.

Solicited read not allowed from unsolicited point !AD.
Explanation: Error. Solicited reads of unsolicited physical points are allowed only for write indication (W\) or information report indication (I\) physical points. Read indication physical points (R\) are defined on the local VMD and not on the remote VMD, so a read cannot be attempted since the variable does not exist.
User Action: Do not attempt to read from the physical point. If the physical point is connected to a logical point, use SHOW POINT/VALUE=LAST to show the last value written to the logical point.

Write not allowed, no indication pending for point !AD.
Explanation: Error. An attempt was made to write to an unsolicited physical point that does not have a read indication pending. Solicited writes of unsolicited physical points are allowed only for write indication (W\) or information report indication (I\) physical points. Read indication physical points (R\) are defined on the local VMD and not on the remote VMD, so a write cannot be attempted unless a read indication is pending since the variable does not exist on the remote VMD.
User Action: Wait for a read indication trigger to occur before writing to the physical point.

Buffer too small for the message for point !AD.
Explanation: Error. The length of the message (as specified in the first word of the message) is too large for the buffer that has been allocated for it. The size of the buffer is the size of the physical point that is defined for the message.
User Action: Modify the first word of the message so that the size is less than or equal to the buffer that has been allocated.

Write required to message exchange point !AD before reading.
Explanation: Error. An attempt was made to read from a message exchange physical point before writing to it. Reading from a message exchange physical point is what triggers the message exchange, but if the physical point hasn't been written to, there is no data in the buffer to exchange with the device.
User Action: Write to the exchange physical point before attempting to read from it.

Error getting PI name attribute.
Explanation: Error. An error occurred when calling omni_get_attribute with an attribute of omni_c_attr_name. omni_get_attribute is called after successfully calling omni_get_remote_attributes using a class of omni_c_cls_pi.
User Action: Examine the error message returned and take action based on the error found.

Error getting Domain name attribute.
Explanation: Error. An error occurred when calling omni_get_attribute with an attribute of omni_c_attr_name. omni_get_attribute is called after successfully calling omni_get_remote_attributes using a class of omni_c_cls_dom.
User Action: Examine the error message returned and take action based on the error found.

Error getting Named Variable name attribute.
Explanation: Error. An error occurred when calling omni_get_attribute with an attribute of omni_c_attr_name. omni_get_attribute is called after successfully calling omni_get_remote_attributes using a class of omni_c_cls_named_var.
User Action: Examine the error message returned and take action based on the error found.

Error downloading file.
Explanation: Error. An error occurred when calling omni_download.
User Action: Examine the error message returned and take action based on the error found.

Error uploading file.
Explanation: Error. An error occurred when calling omni_upload.
User Action: Examine the error message returned and take action based on the error found.

A domain must be specified in the /DEVICE_FILE qualifier.
Explanation: Error. When attempting to do an upload or download, no domain name was specified in the /DEVICE_FILE=XXX qualifier.
User Action: Specify the domain name you would like to upload or download in the /DEVICE_FILE qualifier of the upload or download command.

Error creating domain !AD for file !AD.
Explanation: Error. An error occurred when creating the domain specified in the /DEVICE_FILE qualifier of the upload or download command.
User Action: Examine the error message returned and take action based on the error found.

PI start/reset/delete error for PI !AD.
Explanation: Error. An error occurred when attempting to start or stop (reset/delete) the given program invocation (PI).
User Action: Examine the error message returned and take action based on the error found.

Start/stop option !AD syntax error.
Explanation: Error. The option specified in the START or STOP command was not specified correctly or is not supported.
User Action: Check the DAS documentation for valid options and syntax for the START or STOP command.

Error calling omni_get_value () for pollset !AD.
Explanation: Error. An error occurred when calling omni_get_value for a group of variables. The DAS uses omni_group_variables to group members of a pollset.
User Action: Examine the error message returned and take action based on the error found.

Polling collision - pollset !AD in use.
Explanation: Error. A new poll request has occurred before the previous one has completed.
User Action: Increase the polling interval of the pollset.

No variable handle for point !AD in pollset !AD.
Explanation: Error. A variable handle was not found for the given physical point. The variable handle is created as part of enabling the device.
User Action: If the problem persists, disable and reenable the device.

Error calling omni_group_variables () for point !AD in pollset !AD.
Explanation: Error. An error occurred when attempting to group variables in a scattered pollset.
User Action: Examine the error message returned and take action based on the error found.

Device !AD!/Physical status: !AD!/Logical status: !AD.
Explanation: Informational. The device has delivered an unsolicited status indication to the DAS. The DAS logs the status to the history file.
User Action: None.

Local detail: !AD.
Explanation: Informational. The device has delivered an unsolicited status indication to the DAS. The DAS logs (as a bit string), the information in the local detail portion of the status.
User Action: None.

!AD indication received.
Explanation: Error. An error occurred when receiving an indication from the device. The type of indication received is logged.
User Action: Examine the error message returned and take action based on the error found.

!AD indication received. No unsolicited point found.
Explanation: Error. An indication was received for a variable that is not defined. The indication is rejected.
User Action: Determine the variable that the indication is for (by examining programmable controller logic) and create an unsolicited physical point that matches the variable that is being requested.

!AD ind rejected. Error calling BCC$GET_VALUE (), logical point = !AD.
Explanation: Error. A read indication was received and a matching physical point was found, but the call to get the current value of the logical point failed. The indication is rejected.
User Action: Examine the error message returned and take action based on the error found. If the logical point exists then it may be necessary to force recompiling of the logical point name by stopping BASEstar software, deleting the ILAN$_SECTION.DAT file and restarting BASEstar software.

!AD ind rejected. Error in point status for logical point !AD.
Explanation: Error. A read indication was received, a matching physical point was found and the call to BCC$GET_VALUE succeeded, but the status of the logical point is bad. The indication is rejected.
User Action: Examine the error message returned and take action based on the error found.

Read ind rejected. Previous read ind pending for point !AD.
Explanation: Error. A logical point was not specified from which to get the data to return to the requestor, so the DAS is waiting for a write request to the physical point (after generating a trigger update) and the write had not yet occurred when another read indication was received. The indication is rejected.
User Action: Write to the given physical point to satisfy the previous read indication.

Read ind rejected. No trigger point and no logical point for point !AD.
Explanation: Error. A read indication was received and a matching variable was found, but the physical point did not specify a logical point and a matching trigger physical point was not found. The indication is rejected.
User Action: Modify the physical point to add a logical point name in the unsolicited ID, if automatic replies to the read indication is desired, or create a matching trigger physical point, if automatic notification of the indication is desired, but a manual response to the read indication is required.

Unexpected !AD indication received.
Explanation: Error. An indication type was received that the DAS is not designed to process. The indication is ignored, but since the indication is not responded to, virtual memory may be consumed and not properly released.
User Action: Modify the programming in the programmable controller to stop sending this type of indication.

Index | Contents