$MODE
The mode word of 4 ASCII characters must be written by the SSP on receipt of one of the commands listed in COMMANDS_UNDERSTOOD_BY_ALL_SSPS. The mode words listed below have been defined so far:
------------------------------------------------------------------ ASCII Mode word ASCII command read written by SSP from $COMMAND ------------------------------------------------------------------ INIM denotes receipt of INIT STAM " " STAR BSPM " " BSPI EVNM " " EVNT ESPM " " ESPI PAUM " " PAUS CONM " " CONT GOIN denotes that a command has been received, SSP has started. KRAP denotes that an unrecognised command has been received
The mode word "GOIN" is usually quickly overwritten by one of the other mode words, but is useful for debugging purposes.
The return code from the subroutines is written into this location. It consists of 4 ASCII characters. The return codes defined so far are as follows:
o SUCC The subroutine has executed successfully. The next command can be issued. All the subroutines defined in COMMANDS_UNDERSTOOD_BY_ALL_SSPS must be able to return this code.
o FAIL The subroutine has failed for some reason. The FAIL return code is considered a fatal error, and
the reason for the failure must be investigated and corrected before continuing. More information on the reason for failure can be found in $MORE_INFO. All the subroutines defined in COMMANDS_UNDERSTOOD_BY_ALL_SSPS must be able to return this code.
o DFUL This return code must be returned by EVENT if the data buffer becomes full. It is not considered a fatal error. The condition can be corrected by sending a BEGIN_SPILL command, which resets the data and address buffer pointers. In some implementations, other subroutines may return this code if desired.
o AFUL This return code must be returned by EVENT if the address buffer becomes full It is not considered a fatal error. The condition can be corrected by sending a BEGIN_SPILL command, which resets the data and address buffer pointers. In some implementations, other subroutines may return this code if desired.
A unique ID of 4 ASCII characters should be assigned to every SSP program that will be loaded into one of the SSPs in the BNL787 experiment. (It is likely that every SSP will be loaded with a different program). This program ID should be loaded into the location $PROGID after the command GO is given, so that the master can easily check which code has been loaded into any particular SSP.
No SSP program IDs have yet been assigned. It would be appreciated if SSP programmers would assign IDs to their own programs, and communicate them to the author (SUZ@TRIUMFCL) to ensure that they remain unique.
Converted from .HLP to .HTML by HLPTOHTML.