ORTEC DSPEC - 6.3. Dollar Response Records; 6.4. Command Catalog

DSPEC
®
Digital Gamma-Ray Spectrometer
24
%131135083<CR>
Command not allowed while acquisition in progress.
%131136084<CR>
Command not allowed in current mode of operation.
%131137085<CR>
Hardware failure detected while processing command.
6.3. Dollar Response Records
SHOW and STEP commands respond with a single dollar response record followed immediately
by a percent response record. All valid dollar response records for each command are listed in
the command dictionary.
The following list provides the general form of each dollar response record for an MCB. In this
list, lower case letters represent numeric values. The letters “
ccc
” always represent an 8-bit
unsigned checksum of all characters on the record up to but not including the checksum
characters, and
<CR>
represents the ASCII carriage return character.
$Axxxccc<CR>
xxx is a single 8-bit unsigned number.
$Cxxxxxccc<CR>
xxxxx is a single 16-bit unsigned number.
$Dxxxxxyyyyyccc<CR>
xxxxx and yyyyy are 16-bit unsigned numbers.
$Exxxxxccc<CR>
xxxxx is a single 16-bit alarm mask.
$Fssss...<CR>
ssss... is a variable length ASCII character sequence (no checksum
is sent with this record).
$Gxxxxxxxxxxccc<CR>
xxxxxxxxxx is a single 32-bit unsigned number.
$IT<CR>
True response to a SHOW command (no checksum).
$IF<CR>
False response to a SHOW command (no checksum).
$Jxxxxxyyyyy...ccc<CR>
Response to SHOW_CONFIGURATION command.
$Mxxxxxxxxxx...ccc<CR>
Response to SHOW_STATUS command.
$Nxxxyyyzzzccc<CR>
xxx, yyy, and zzz are 8-bit unsigned numbers.
6.4. Command Catalog
This section lists each command with a description of its operation. The descriptions include a
list of any unusual responses that may result. As described in previous sections, the usual
response from a command is a
%000000069<CR>
response, which represents a macro error
code of 0 and a micro error code of 0 (no errors).
All execution error responses, if any, are listed for each command. Though syntax and
communication error responses may result from any command, in practice, these error responses
rarely occur on systems with reliable communication hardware running debugged software.
Refer to Section 6.2 for information about error responses.