Signals that an SDTI serial connection has closed.
Trigger: Sent after SDTI has received a valid BIOS_SDTI_IN or BIOS_SDTI_OUT and the resulting connection has closed for one of the reasons described below.
Target: The link number that sent the BIOS_SDTI_IN or BIOS_SDTI_OUT call.
link_message(integer sender_num, integer [ident]
, string "BIOS_SDTI_CLOSE", key [status]
)
• integer | [ident] |
• key | [status] |
Parameter | Description |
---|---|
[ident] |
Integer. The [ident] sent with BIOS_SDTI_IN or BIOS_SDTI_OUT when the connection was created. |
[status] |
String. The result of the connection as one of the following strings. |
[status] |
Description |
---|---|
"ok" | The data was sent successfully. |
"cancel" | The connection was cancelled by BIOS_SDTI_CANCEL. |
"not enough memory" | There was not enough memory in the receiving object to send the specified data. No data was transferred. |
"serial error" | An unrecoverable communications error in the simulator occurred. Some data may have been transferred, but the SDTI cannot verify that it transferred all data. The SDTI automatically detects if one packet has dropped or is sent in the incorrect order and corrects the data. However, if multiple packets are sent out of order in sequence, the SDTI will return this error. Software may reattempt the connection if desired. |
"timeout" | Either the outputting object did not send BIOS_SDTI_OUT within 60 seconds, or there was a communications failure for at least 10 seconds. Some data may have been transferred, but the SDTI cannot verify that it transferred all data. The SDTI automatically attempts to reestablish the connection during this timeout period, so if a timeout occurs, it is generally safe to assume that the other object has been deleted and the connection should not be automatically reattempted. |
Any BIOS_RAM_RESP [status] |
The specified memory error occurred. Some data may have been transferred, but the SDTI cannot verify that it transferred all data. Software may reattempt the connection if desired. |