Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA™ Communication Drivers

TABLE OF CONTENTS

S7 trace messages

Save PDF
Save selected topicSave selected topic and subtopicsSave all topics
Share
Share to emailCopy topic URL
  • Last UpdatedAug 29, 2024
  • 8 minute read

The SIDirect Communication Driver provides five types of trace messages as follows:

  • Connection Trace

  • Poll Trace

  • Cyclic Trace

  • Block Trace

  • Alarms and Events Trace

    The following table lists the trace messages produced by the Communication Driver. For more information about trace messages, see SIDirect Communication Driver logger flags.

    Logger Message

    Explanation

    Probable Cause

    Solution

    CONNECTION_TRACE Messages

    (%d):s7_initiate_req [0]

    There is an error establishing a connection.
    The server cannot send the Connect Request to the PLC. The first parameter is the error code of the function call (-1 = Message Blocked, -2 = Message Failed) from the PLC.
    The parameters inside the square bracket is 0.

    The credit is not available to send this request.

    If after some time the problem still exists, restart the server.

    Can't connect

    There is an error establishing a connection. The server cannot send the Connect Request to the PLC.

    The credit is not available to send this request.

    If after some time the problem still exists, restart the server.

    Close connection (con=%s): (cpd=%d,cref=%d)

    INFO: The Communication Driver closes the connection with the PLC. The parameters associated with the PLC connection are listed.

    N/A

    N/A

    Connection (con=%s) was not successful

    The server connection attempts to the PLC fails.

    The PLC is in a faulty condition or the connection is broken.

    Check the PLC or check the cable connection.

    Connection (con=%s) was successful

    INFO: The server connects with the PLC successfully.

    N/A

    N/A

    Internal Error: %s Set state of connection to %d

    The connection with the PLC cannot be established.

    This is an unknown error.

    Check the PLC or cable connection, or restart the server.

    Open connection (con=%s)

    INFO: The socket connect call to the PLC is successful but the connection negotiation is still not completed

    N/A

    N/A

    s7_abort = OK

    INFO: The SIDirect Communication Driver closes the connection with the PLC successfully.

    The connection is closed by either the server or the PLC

    N/A

    s7_get_initiate_cnf cnf amq called: %d

    INFO: PLC agrees on this parameter with the Communication Driver. (cnf_amq_called)

    N/A

    N/A

    s7_get_initiate_cnf cnf amq calling: %d

    INFO: PLC agrees on this parameter with the Communication Driver. (cnf_amq_calling)

    N/A

    N/A

    s7_get_initiate_cnf cnf pdu size: %d

    INFO: PLC agrees on this parameter with the Communication Driver. (cnf_pdu_size). The PDU size is returned.

    N/A

    N/A

    s7_get_initiate_cnf ind amq called: %d

    INFO: This is the Communication Driver side negotiation parameter with the PLC. (ind_amq_called)

    N/A

    N/A

    s7_get_initiate_cnf ind amq calling: %d

    INFO: This is the Communication Driver side negotiation parameter with the PLC (ind_amq_calling).

    N/A

    N/A

    s7_get_initiate_cnf ind pdu size: %d

    INFO: This is the Communication Driver side negotiation parameter with the PLC. (ind_pdu_size) The PDU size of the PLC is requested.

    N/A

    N/A

    s7_initiate_req = OK

    The server sends the Connect Request to the PLC successfully.

    N/A

    N/A

    %s Set state of connection to CLOSED

    The SIDirect Communication Driver closes the connection to the PLC.

    The connection is closed by the server or by the PLC.

    If the cable is not disconnected, check the PLC configuration and see if you have specified the Keep-Alive parameter. The Keep-Alive parameter causes the closing of connection if there are no activities for some specified amount of time.

    %s Set state of connection to ERROR

    The connection with the PLC cannot be established.

    The server cannot connect to the PLC at all.

    Check the PLC or cable connection, or restart the server.

    %s Set state of connection to OPEN

    INFO: The server opens a connection with the PLC.

    N/A

    N/A

    %s Set state of connection to PENDING

    INFO: The server is awaiting the response from the PLC for the Connection Request.

    N/A

    N/A

    %s Set state of connection to SLOW POLL MODE

    The server is going into the Slow Poll mode.

    The connection with the PLC is bad.

    Check the PLC or check the cable connection.

    POLL_TRACE Messages

    %s dumping s7 objects (containing %d items)

    INFO: Dumping the information about the S7Info in the logger.

    N/A

    N/A

    (1): s7_multiple_read_req (orderid=%d) [0]

    INFO: The multiple read request message cannot be sent to the PLC because the server runs out of credit.

    N/A

    N/A

    (2): s7_multiple_read_req (orderid=%d) [0]

    The multiple read request message cannot be sent to the PLC because of unknown reasons.

    N/A

    If the problem persists, restart the server.

    add pItem (%s) to S7Info (pS7Info=0x%08X, addr: %d range: %d)

    INFO: The server adds item to the S7Info while building the Poll message.

    N/A

    N/A

    Build message (%s msg=0x%08X) for topic %s

    INFO: The server builds a POLL message for the topic.

    N/A

    N/A

    Delete message (%s msg=0x%08X) for topic %s

    INFO: Destructor for the POLL message gets called.

    N/A

    N/A

    dumping read values

    INFO: Dumping the read values received from the PLC in the logger.

    N/A

    N/A

    Got orderid:%d for message (%s msg=0x%08X,con=%s) [number of orderids=%d]

    INFO: The server assigns the order ID for the POLL message.

    N/A

    N/A

    Release orderid:%d for message (%s msg=0x%08X,con=%s) [number of orderids=%d]

    INFO: Release the order ID from the message.

    N/A

    N/A

    remove pItem (%s) from S7Info (pInfo=0x%08X)

    INFO: The server removes the item from the S7Info.

    N/A

    N/A

    s7_multiple_read_req = OK (orderid=%d)

    INFO: The multiple read request message is sent to the PLC successfully.

    N/A

    N/A

    S7Info=%s:result=%d var_length=%d value (in HEX ASCII):

    INFO: The server logs the information about the read value received from the PLC in the logger.

    N/A

    N/A

    POKE_TRACE Messages

    %s dumping s7 objects (containing %d items)

    INFO: Dumping the information about the S7Infos in the logger.

    N/A

    N/A

    %s: result=%d var_length=%d value (in HEX ASCII)

    INFO: Logging the Result received from the PLC for the write request.

    N/A

    N/A

    (1): s7_multiple_write_req (orderid=%d) [(%d) %s]

    INFO: The multiple write request message cannot be sent to the PLC because running out of credit.

    N/A

    N/A

    (2): s7_multiple_write_req (orderid=%d) [(%d) %s]

    The multiple write request message cannot be sent to the PLC because of unknown reasons.

    N/A

    If problem persists, restart the Server or check the PLC.

    add pItem (%s) to S7Info (pS7Info=0x%08X, addr: %d range: %d)

    INFO: Server adding item to the S7Info while building the Poke Message.

    N/A

    N/A

    Build message (%s msg=0x%08X) for topic %s

    INFO: Server building a Poke message for the topic.

    N/A

    N/A

    Delete message (%s msg=0x%08X) for topic %s

    INFO: Destructor for the Poke message gets called.

    N/A

    N/A

    Got orderid:%d for message (%s msg=0x%08X,con=%s) [number of orderids=%d]

    INFO: Server assigns the order id for the Poke Message.

    N/A

    N/A

    Release orderid:%d for message (%s msg=0x%08X,con=%s) [number of orderids=%d]

    INFO: Release the order ID from the poke message.

    N/A

    N/A

    remove pItem (%s) from S7Info (pInfo=0x%08X)

    INFO: Server removing the item from the S7Info.

    N/A

    N/A

    s7_multiple_write_req = OK (orderid=%d)

    INFO: The multiple write request message sent to the PLC successfully.

    N/A

    N/A

    S7PokeMessage::AddPokeItem (Item=%s)

    INFO: Server adding item to the Poke Message.

    N/A

    N/A

    TREAL item %s high clamped to 9990s

    INFO: The value of TREAL item is clamped at high value.

    N/A

    N/A

    TREAL item %s low clamped to 0ms

    INFO: The value of TREAL item is clamped at low value.

    N/A

    N/A

    CYCLIC_TRACE Messages

    %s dumping s7 objects (containing %d items)

    INFO: Dumping the information about the S7Infos in the logger.

    N/A

    N/A

    (-1):s7_cycl_read (orderid=%d) [(%d) %s]

    The server could not send the cyclic read request to the PLC. Temporary error.

    N/A

    N/A

    (1): s7_cycl_read_delete_req (orderid=%d): [0]

    The server could not send the cyclic read delete request to the PLC because of running out of credit.

    N/A

    N/A

    (1): s7_cycl_read_start_req (orderid=%d): [0]

    The server could not send the cyclic read start request to the PLC because of running out of credit.

    N/A

    N/A

    (2): s7_cycl_read_delete_req (orderid=%d): [0]

    The server could not send the cyclic read delete request to the PLC because of Unknown reason.

    N/A

    N/A

    add pItem (%s) to S7Info (pS7Info=0x%08X, addr: %d range: %d)

    INFO: Server adding item to the S7Info while building the cyclic Message.

    N/A

    N/A

    Build message (%s msg=0x%08X) for topic %s

    INFO: Server building a cyclic message for the topic.

    N/A

    N/A

    Delete message (%s msg=0x%08X) for topic %s

    INFO: Destructor for the cyclic message gets called.

    N/A

    N/A

    Got orderid:%d for message (%s msg=0x%08X,con=%s) [number of orderids=%d]

    INFO: Server assigns the order id for the cyclic Message.

    N/A

    N/A

    Release orderid:%d for message (%s msg=0x%08X,con=%s) [number of orderids=%d]

    INFO: Release the order ID from the cyclic message.

    N/A

    N/A

    remove pItem (%s) from S7Info (pInfo=0x%08X)

    INFO: Server removing the item from the S7Info.

    N/A

    N/A

    s7_cycl_read = OK (orderid=%d)

    INFO: The server successfully sends the cyclic read request to the PLC.

    N/A

    N/A

    s7_cycl_read_delete_req = OK (orderid=%d)

    INFO: The server successfully sends the cyclic read delete request to the PLC.

    N/A

    N/A

    s7_cycl_read_start_req = OK (orderid=%d)

    INFO: The server successfully sends the cyclic read start request to the PLC.

    N/A

    N/A

    s7_get_cycl_read_init_cnf (cpd=%d,m_cref=%d,orderid=%d) Build Poll Messages: [(%d) %s]

    INFO: The server gets the confirmation from the PLC for the Cyclic read request.

    N/A

    N/A

    S7Info=%s:result=%d var_length=%d value (in HEX ASCII)

    INFO: Logging the value received from the PLC for the cyclic message

    N/A

    N/A

    BLOCK_TRACE Messages

    (0): s7_brcv_init (r_id=%d) [0]

    INFO: The block receive initiation request is successful.

    N/A

    N/A

    add item (%s) to S7BlockMessage (%s msg=0x%08X)

    INFO: Adding items to the block message.

    N/A

    N/A

    Build message (%s msg=0x%08X) for topic %s

    INFO: Server building a Block message for the topic.

    N/A

    N/A

    Delete message (%s msg=0x%08X) for topic %s

    INFO: Destructor for the block message gets called.

    N/A

    N/A

    Release blockid:%d for message (%s msg=0x%08X,con=%s) [number of blockids=%d]

    INFO: Release block id for the block message.

    N/A

    N/A

    remove item (%s) from S7BlockMessage (%s msg=0x%08X)

    INFO: Remove item from the block message.

    N/A

    N/A

    s7_brcv_init = OK (r_id=%d)

    INFO: The block receive initiation request is successful.

    N/A

    N/A

    s7_brcv_stop = OK (r_id=%d)

    INFO: The block receive stop request is successful.

    N/A

    N/A

    ALARMS_AND_EVENTS_TRACE Messages

    %s: ack_state=%d

    INFO: Update the alarm or event with the acknowledgement state information.

    N/A

    N/A

    %s: event_state=%d

    INFO: Update the alarm or event with the event state information.

    N/A

    N/A

    %s: no_add_value=%d

    INFO: Update the alarm or event with the number of additional value information.

    N/A

    N/A

    %s: state=%d

    INFO: Update the alarm or event with the state information.

    N/A

    N/A

    %s: time_stamp=%s

    INFO: Update the alarm or event with the time stamp information.

    N/A

    N/A

    (%d): s7_msg_abort_req (orderid=%d) for %s [0]

    The alarm abort request to the PLC failed.

    N/A

    N/A

    add item (%s) to S7Event (msg=0x%08X)

    INFO: Add item to the event message.

    N/A

    N/A

    Build alarm object (0x%08X) for connection %s

    INFO: Server builds the alarm object that are going to receive the alarms and events.

    N/A

    N/A

    Build scan object (0x%08X) for connection %s

    INFO: Server builds the scan object.

    N/A

    N/A

    Delete alarm object (0x%08X) for connection %s

    INFO: The destructor of the alarm object gets called.

    N/A

    N/A

    Release eventid:%d (con=%s) [number of eventids=%d]

    INFO: Release order id from the event message.

    N/A

    N/A

    remove item (%s) from S7Event (0x%08X)

    INFO: Remove item from the event message.

    N/A

    N/A

    s7_msg_abort_req = OK (orderid=%d) for %s

    INFO: The server sends the alarm abort request to the PLC successfully.

    N/A

    N/A

    s7_msg_initiate_req = OK (orderid=%d) for %s

    INFO: The server sends the alarm registration request to the PLC successfully.

    N/A

    N/A

TitleResults for “How to create a CRG?”Also Available in