APPLICATION NOTE
INFUTEST
Series C & Series D
AN-17.2004: Page 1 of 4
1-800-667-6557
www.datrend.com
©
Datrend Systems Inc.
Interface With medTester
1. INTRODUCTION
The
medTester 5000B
is part of an equipment
management data base and testing system available
from DNI Nevada Inc.(now Fluke Biomedical Corp.). To
use Infutest with medTester, your medTester must
have the
medCheck
firmware option installed, plus you
must be able to use the equipment data base program
Sentinel, also by DNI Nevada.
2. SETTING UP
Use a Datrend Syst ems SSC-1 cable to connect
Infutest to COM2 of the medTester.
Do not use a
null modem cable or adaptor.
Do not connect medTester to Infutest using the
medTester serial cable supplied by DNI Nevada.
This is a null modem cable for connecting COM1 of the
medTester to a PC.
Power up medTester and select
UTIL
from the main
menu level, followed by
PORTS
. Set
COM1
to
OFF
and
COM2
to
ON
.
Return to the
UTIL
menu.
Select
RS232
and then
COM2
. Program COM2 as
follows:
Set
Baud Rate
to
9600
Set
Stop Bits
to
1
Set
Length
to
8
Set
Parity
and
CTS
to
OFF
3. DESIGNING CHECKLISTS
A
Checklist
is a list of instructions or "check items"
which medTester performs sequentially and
automatically, pausing occasionally for data input from
the user via the medTester keyboard, or from an
external device connected to medTester's COM2 port.
Checklists are created on a PC using the Sentinel
program, and then are downloaded from your PC into
medTester's memory.
To control Infutest with medTester, your Checklist
must included check items which begin with
\M
followed by an Infutest remote control command. A
check item beginning with
\M
tells medTester to get
data from COM2, instead of from the medTester
keyboard. In executing a Checklist with
\M
items, the
medTester will transmit whatever characters follow
\M
to the Infutest via COM2, and then will wait for data to
be returned via COM2. Depending on the command
which follows the
\M
, Infutest may return up to 40
characters of data to the medTester.
\M
is also necessary to introduce delays into the
Checklist so the Infutest has time to start the test and
collect some measurement data. The syntax for this
is:
\M
pause
where
pause
is the number of seconds (1 to 32000)
you want medTester to wait until it continues with the
next check item.
For example, your Checklist might begin with some
PASS/FAIL items (
\P
items) for inputting information
about the condition of the pump under test, such as the
line cord and front panel keys and displays, and it might
end with AutoSequence 10 to test electrical safety of
the pump. In between, you want to conduct a test on
Channel A to check the flow at 100 ml/hr, and then
measure the occlusion pressure. To do the flow test,
your Checklist could include the following items:
\M RTA1
\M 180
\M STA
\M GSA1
This portion of a Checklist starts a Single Rate Test on
Channel A and runs the test for three minutes. The
flow test is stopped and medTester requests Infutest to
return the summary of the measurements made during
the test via the GSA1 command.
Now you want the medTester to tell Infutest to run the
Occlusion Pressure Test. To do that, the previous
check items would be succeeded by:
\M RTA4
\M 60
\M STA
\M GSA4
These check items star t an Occlusion Pressure Test
