Configure Set Pressure (SetP):
While in SetP Mode, this sets the target inflation pressure.
Send: <SETP_CFG> <CR>
[50...400] <CR>
Recv: ‘=’ – success
‘#’ – out of range.
To begin the test Send:
<BUTTON>
F3
Manometer Output
The 2 manometer outputs use the format: -300 .. 4000 for –30.0 mmHg to 400.0
mmHg.
-429 or 4051 may be returned which are the extreme limits and may indicate an out of
range value.
For readings less than 100.0 mmHg (less than 4 significant digits) leading zeros are
suppressed.
Manometer Sample
Delivers one current manometer sample.
Send:
<MAN_SMP> <CR>
Recv:
xxxx
‘=’ – success
Streaming Manometer
Turns on or off the outputting of one manometer sample every 250 mSecs.
Send:
<MAN_STR> <CR>
[ON/OFF] <CR>
Recv:
‘=’ – success
‘#’ – bad command parameter was given (not ON or OFF)
Getting and setting device information
Get Serial Number
Send:
<GET_SERIAL_NUM> <CR>
Recv:
HH12080006
Get Software Information
Send:
<I> <CR>
Recv:
AP_Handheld Rev.B 2_0_9 12:12:11 Oct 21 2009
Get Features
Primarily a troubleshooting aid for factory support.
Returns a HEX value which reflects the configuration and software options loaded.
Send:
<GET_FEATURES> <CR>
Recv:
Features = 6008 Hex
Set Device ID
Note: This command is given for convenience to the end-user. There exists a utility,
distributed for free by FtdiChip.com that allows the USB chip inside the APHandheld device
to be programmed with a custom device id. Programmers using FTDI’s API may use this to
identify devices. This is simpler than opening the port and then querying the device. The
user does not even have to open the port if it’s not the device they are looking for.
This allows users to set their device ID so that a group of them may be controlled
remotely. Software configured to control a group of devices can requisition each device
for its informal name (or a more formal ID, such as “Factory1”, for instance) . This way,
it does not matter which USB port is used to communicate with a device, even if it is on
a Radio-linked USB hub; it just matters that we know which device ID we are talking to.
Some users will prefer to ask for the serial number to determine which device is which.
Send:
<SET_DEVICE_ID> <CR>
Sparky <CR>
“Sparky” is listed here as an example name
Recv:
‘=’ on success
‘@’ on overflow.
Get Device ID
Send:
<GET_DEVICE_ID> <CR>
Recv:
“Sparky” – if device id has been set
“*” – if device id has not been set
Screenshot Support
These were to support Clinical Dynamics' proprietary software for internal use. Those
applications assemble this data into pictures automatically and provide output files as
needed. This command is exposed in case customers wish to display pictures of
screenshots in their software packages.
Hex Screenshot:
Output hex screenshot data.
• Data is in format first byte first, last byte last and is in hexadecimal format.
• Every 8th hexadecimal BYTE is followed by a <CR> for readability when in hyperterm.
• If a byte is < 16, the number is “ n”, not “0n”.
• A screen is 1024 bytes arranged 128 bytes per row for 8 rows. (8 vertical pixels per byte).
Send:
<HEX_SCREENSHOT> <CR>
Recv:
0 0 1 1 1 1 0 0 <CR>
ffab 1 1 1 1baff <CR>
…
0 1 1 1 1 0 0 <CR>
Binary Screenshot:
Upload binary screenshot data.
• Data is in format first byte first, last byte last and is in binary format.
• If a byte is < 16, the number is “ n”, not “0n”.
• A screen is 1024 bytes RAW BINARY DATA
Send:
<BIN_SCREENSHOT> <CR>
Recv:
1024 binary bytes
NOTE: a variation of these screen dumps are available when appropriate for bench top
products that have a larger display format.
<QVGA_BIN_SCREENSHOT>
19