Leak Test
A
uto-InflateStart Pressure: 3 user presets can be set and saved
E
ach adjustable
: 50-300mmHg
Elapsed Time: 3 user presets can be set and saved Each adjustable 20-120 seconds
H
igh Resolution Manometer:
0
.0 to 400.0 mmHg
Over-Pressure
A
utomatically tests operation of the monitor's relief valve
Pop-Off Pressure range: 10 to 400 mmHg
Instantaneous Pressure: 0 to 400 mmHg
Autosequences
User can utilize autosequences to test NIBP monitors with a specific series of AccuPulse
N
IBP performance tests.
Also a special user sequence is added with the optional User Defined mode
C
uff Support for Adult cuffs is the AccuPulse case for portability and ease of use.
Neonate mandrel also supplied
• Neonate (1.25" OD,2.25" width)
Adapter Hoses
Adapter Hoses insert between the NIBP device, cuff and analyzer. These adapters are
compatible with oscillometric NIBP monitors.
• Male/Female Luer
• Male/Female Clippard (GEMedical, Draeger/Siemens)
• Colder/CPC (GEMedical, Protocol Systems)
• OBAC Quick Release (Philips Medical)
• Universal 5/32" I.D. Hose
Self Test Accessories
• Pressure Bulb Assembly (tees into any Cuff Adapter)
• Self system leak test hose (plugged at distal end)
Communication Port
1 USB mini Port
Display Non-Glare Graphic LED Backlight
Resolution: 128 x 64
Power
External: 100-240 VAC, 50 watts, 50-60 Hz, Desktop Switcher
Output: 24VDC @ 2.1A, 6 foot cable
Safety Agency Approvals: UL, CE, TUV
Internal Battery: Lithium Ion (LiOn)
Voltage: 16.5V Capacity: 2.5A-Hr, typically 150 NIBP Simulations
Charge Time: 3.5 Hours
Weight 1.9 pounds with internal battery
Dimensions 4.25" Wide x 2" High x 10" Long
Standard Accessories
• External Power Supply & Cord
• Neonate Cuff Support
• Adult Cuff Support (built-in)
• Five Adapter Hose set
• Operation Manual on CD
• Internal Pump
• Internal Battery
Optional Accessories
• Carry Case
• CalTables software module
• User Defined software module
•
Motion sof
tware module
• Arrhythmia software module
Section 7. Remote Control
Overview:
This remote control tries to adhere as closely as possible to the remote control spec of
t
he legacy SmartArm and AccuPulse remote control commands. That is, typically,
commands and command feedback are accompanied by similar syntax.
This section explains the commands in detail. A less detailed short form listing of the
m
ost commonly used commands is presented at the end which can be used for fast
reference.
Set up / protocol – Before developing a software communications driver for use
in your AccuPulse application, it is
r
ecommended that the developers familiarize themselves with the communications
protocol using a dumb terminal or a PC operating as a dumb terminal.
NOTE: Windows VISTA and Windows 7 do not include a terminal program. Free / Open
Source terminal applications such as TerraTerm can be easily downloaded. Another
solution is to copy Hypertrm.exe and Hypertrm.dll from Windows XP (no install is
required, just keep them in the same folder).
Baud Rate: 921600 bps
Data Bits: 8
Stop Bits: 1
Parity: None
ANSI emulation
No Flow Control
Local Echo and CR-> CR/LF are helpful when entering commands by hand.
Terms and Syntax:
All commands must be sent in upper case as shown. Lower case will not be recognized.
The syntax and action of most commands reflects their development with a terminal
program. To support legacy syntax, the terminal interactivity remains.
<CR> = carriage return = character 13
The remote control syntax is that of an HTML-style tag wrapping each command name
and a carriage return:
< COMMAND_NAME > <CR>
In order that differing terminal protocols may be supported, <LF>s (character code 10
decimal) are filtered out of the stream for most commands.
The prompt returned by the
ApHandheld is:
>
There are, furthermore, several return codes that may precede the prompt.
COMMAND RESPONSES: (delimited from the prompt by a <CR>)
• ‘>’ – Ready Prompt
• ‘=’ – multichar command executed successfully
.
• ‘#’ – data or parameters were out-of-range for the given command.
• ‘*’ – command not usable in the current mode. Set-preset command only operates
in BpT
est mode, for instance. Some commands require a purchased upgrade, etc.
• ‘?’ – COMMAND_NAME is not recognized as a valid command.
• ‘$’ – checksum error in data that was sent.
• ‘@’ – data has overflowed (data was truncated to prevent a memory leak).
•'!' - command has no cur
rent context, not usable in this mode or at this time.
• ‘~’ – Busy
• ‘^’ – Time out
The sof
tware that drives an ApHandheld must process all these return characters.
16
To Next Page
Loading...