APPLICATION NOTE
INFUTEST
Series C & Series D
AN-17.2004: Page 3 of 4
1-800-667-6557
www.datrend.com
©
Datrend Systems Inc.
b.
Do not plug an external keyboard into
medTester when you are using medTester
COM2.
medTester may default to reading data
from the external keyboard rather than
downloading data via COM2.
c.
After downloading any Sentinel data from your PC
to medTester via COM1, check that medTester
COM1 is
OFF
, COM2 is
ON
and that COM2 stop
bits remains set to
1
.
d.
Depending on the version of your medTester,
the RTS line of COM2 may inadvertently
switch low after certain operations. In order
for Infutest to transmit data to medTester,
medTester's RTS line must stay high
(the
default). The best way to determine that RTS is
high is to install an RS-232 breakout box between
Infutest and medTester COM2 at the medTester
end. Note that medTester is the Data Terminal
Equipment (DTE).
If you don't have an RS-232 breakout box, you can
open the DB-25 shell on your Datrend SSC-1
cable and plug this end into medTester COM2.
Use a voltmeter to probe COM2 pin 4 (RTS) with
respect to pin 7 (GND). The reading should be
higher than + 4 VDC. If the voltage is negative,
medTester's RTS signal will prevent Infutest from
downloading data.
To overcome this problem on the medTester, you
can modify your Datrend SSC-1 cable by opening
the DB-25 shells and cutting the wires connected
to pins 4 and 5. Solder a jumper lead so that
pin 4
of the SSC-1 is shorted to
pin 5
. Perform this
modification at
both
ends of the SSC-1. This will
override Infutest's RTS/CTS signalling.
6. DEBUGGING YOUR SYSTEM
In debugging your medTester-Infutest setup, you
should start by using simple 4-item Checklists like the
examples given in this app note. Always use a Datrend
SSC-1 cable, or make a cable using the wiring
information given in Chapter 3, Section 3.3 of the
Infutest Operating Manual.
If the Infutest does not respond to "run test" commands
(e.g. RTA1) by starting a flow test, you are probably
having hardware problems (e.g. cable, serial port
setup, etc.). If the Infutest seems to respond to "run
test" and "stop test" commands, but won't return test
data to medTester, you are probably experiencing
medTester bugs like (a.), (b.) or (d.) discussed in the
previous section.
7.
COMMAND SUMMARY
The table on the following page lists all the Infutest
commands which are compatible with the medTester
5000B. Further information on the format of data
returned by the Infutest in response to the "GS"
commands can be found in the
Infutest Operating
Manual.
