Dcsi-B01 840 20 02 02
Dcsi-B01 840 20 02 02
Dcsi-B01 840 20 02 02
NOTE: This information is provided as an aid in Technical Support for trained support
personnel. Do not attempt to service the system without the appropriate technical training
and the proper tools.
Purpose To provide product experts a tool to troubleshoot serial
communications effectively.
Product LIS Troubleshooting Kit (PN 084-K048-01)
Applicability All systems that utilize RS-232 serial communication
Estimated Time N/A
Special Notes None
Special Materials RS232 Serial Analyzer Software (V5.5 or higher)
http://www.232analyzer.com/Comm-Front-Downloads.htm
Dual Port USB Serial Adapter Driver (V2.04.06 or higher)
http://www.ftdichip.com/Drivers/VCP.htm
Attachments None
References None
Part Numbers
Availability: Immediately.
Lead Time: 2 weeks (Anticipated delivery time following receipt of order).
The following part number is new. Make the part numbers available for order.
Activity Description REF SMN Part Number
DCSI-B01.840.20.02.02
LIS Troubleshooting Kit
Background Information
This LIS Troubleshooting Kit along with RS232 serial monitoring software
enables product specialists to utilize a service laptop as a tool to monitor and
troubleshoot serial communications issues. This tool is intended to remain in the
possession of the branch service specialist after it is ordered. The individual
components of the kit will not be spared separately.
The LIS Troubleshooting Kit contains off the shelf RS232 commercially available
components in a compact soft zipper case that can be utilized to capture serial
communication via a variety of serial (DB9, DB25, RJ45) interfaces.
Action
1. Countries and regions should identify which product specialists would
benefit from this tool and order as appropriate.
2. Once the kit is received, perform/read the following sections to prepare
your service laptop and yourself to troubleshoot LIS connectivity:
• Appendix C – to install drivers for USB serial adapter
• Appendix D – to download and install the RS232 Serial Analyzer
Software
• 232Analyzer Help Contents (F1) - to understand how to operate the
software.
• Appendix A & B – to understand basics of RS-232
3. To troubleshoot an instrument / LIS connection perform the following
• Procedure A – To test the instrument port and cabling
• Procedure B – On how to interconnect the service laptop in line with
serial communication line.
• Procedure C – How to capture data using the 232Analyzer software
Table of Contents
A Break Out Box is a test tool that is plugged in to the "middle" of an RS-232 link
and shows the signal status on each wire. The break out box is then "in the
middle" of the cable. When a signal is asserted on an RS-232 line, a
corresponding LED indicator lights up on the break out box. You get a visual
indication of the status of the link. The Break-Out Box has a male DB-25
connector on one side and a female on the other. A column of DIP (Dual In-line
Package) switches stand between these two connectors, making it possible to
selectively connect the pins on either side.
Note:
• When the switches are "ON" signals will flow from whatever is plugged
into the right side of the Break-Out Box and out to the left side.
• The numbers printed on the switches themselves should be ignored. Use
only the numbers printed to the left and right of the switches on the Break
Out Box to determine which switch governs which pin or receptacle.
• The Break-Out Box contains an LED for pins 2, 3, 4, 5, 6, 8, 15, 17, 20,
and 24. These indicators glow GREEN when there is negative voltage on
their respective pins and RED when the voltage is positive.
• Pin 1 is a hardware ground that does not have a switch.
• Switch number 7 must always be ON for any data to pass thru. Pin 7 is
signal ground, and it must always be ON!
Features:
Before troubleshooting cable issues it is best to confirm that the PC com port is
functioning properly. Use a Loopback Tester supplied in the LIS Troubleshooting
Kit on the PC com port utilizing the system software to confirm that the loop back
is successful before troubleshooting cable issues. The Loopback Tester is a 9
and 25 pin adapter with female ports on either end that loops the transmit lines to
the receive lines so that every byte that is transmitted is received back.
Loopback Tester
1. Insert the Loopback Tester in the male com port on the system to be
tested (Using either side of the Loopback Tester).
Note:
It may be necessary to use the LIS Troubleshooting Kit DB9 serial cable with
a male-male gender changer to accommodate physical obstructions with
various DB9 com ports on certain PCs.
2. Utilize the instrument specific software test screen to verify the com port.
If a Loopback tester is not available then proceed to the next step to
configure a BOB as a Loopback tester, If you have the ability to use the
Loopback Tester then skip to step 6.
3. On the BOB move all the DIP switches to the left except for pin 7 (upper
DIP bank #6, as shown in the following screen capture).
2 Æ 3
4 Æ 5
6 Æ 20
5. If you are testing a PC with a DB25 port then attach the female-female
DB25 pin gender changer onto the BOB right side cable and test the com
port. If you are testing a PC with a DB9 port then attach the DB25-DB9
(female-male) adapter to the BOB right side cable, then attach the
female-female DB9 pin gender changer on the adapter and then test the
com port utilizing the instrument specific software test screen.
(In lieu of the instrument specific software, Microsoft Windows
HyperTerminal can be used instead by the following procedure.)
• Navigate to Start > Programs > Accessories > Communication >
HyperTerminal.
• Using the HyperTerminal program, configure and open the port which
you choose to verify. Once the port is open, you will see a blank
window.
• Press keys on the keyboard see if text is displayed on the
HyperTerminal window. Text displayed on the window indicates the
Loopback test is successful.
6. Proceed as follows:
• If Loopback is not successful then troubleshoot the PC port and or
software.
• If Loopback is successful and data is being transferred then go to
Procedure B.
• If Loopback is successful and data is not being transferred then
continue with Procedure A.
One of the most common interfacing problems results when both machines are
wired like "terminals" (DTE). The best example would be the RS-232
communications ports on two computers. In almost every case, both will be set
up to be plugged into a modem (DCE). That means they will both be sending
data on pin 2 and expect to receive data on pin 3. To make them talk to each
other, these and other relevant pins must be switched so that each computer
thinks that it is talking to a modem (DCE).
6. Using the supplied jumper wires, insert them into the pins as follows:
2 Æ 3
3 Æ 2
4 Æ 5
5 Æ 4
6 Æ 20
20 Æ 6
7. Proceed as follows:
• If data can be transferred then inform the customer of the findings so
the cable can be re-wired correctly and then continue with Procedure B.
• If data can not be transferred then continue with procedure A.
Use this procedure when you did not find the transmit and received pins (2 & 3)
wired to the same pins. Pins 4, 5, 6, and 20 are special pins that act like traffic
directors, telling the equipment when to send and when to stop sending data. Try
shorting 4 and 5 together. Then try shorting 6 to 20 together. Then try shorting
them all together. Then try a different combination. It might not sound scientific,
but this is the way to make the equipment work in the shortest amount of time.
Most instruments do not utilize these signals and required them to be shorted at
the connector. Refer to your specific instrument LIS Interface Guide on required
wiring.
BOB Configuration
3. Using the supplied jumper wires, insert them into the pins as follows:
4 Æ 5
6 Æ 20
4 Æ 5
6 Æ 20
4. Try combinations of jumpers (start with one and work up to all four) with
testing the interface between each combination.
5. If serial communication is successful then inform the customer LIS
support personal of the finding and have them rewire the serial cable
appropriately.
1. On the service laptop connect the Dual Port USB Adapter into an
available USB port. If this is the first time this device has been installed,
perform procedure in Appendix C and then return to this section.
2. Connect the Full Duplex Spy Cable to the USB dual Port Adapter using
the two thin lead DB9 female connectors labeled “Monitoring”.
NOTE:
• The Full Duplex Cable allows for serial communication to pass
through as normal between the instrument and the host with the
monitoring lines allowing for “spying” on the communication
independent of the Host and the instrument.
• Be sure not to use a null modem adapter to connect anything in
this step. A null modem adapter will change the pin layout of your
setup.
Standard Connection
2. Select the lower numbered Service Laptop USB Serial Port in the drop
down arrow on the 232Anlayzer software Toolbar. (Refer to Appendix C,
step 7 to determine the correct com port # for your laptop)
3. Utilizing the drop down boxes on the 232Analzer software toolbar select
the correct Baud, Data (bits), Parity and Stop (Bits) for the serial
communication line you are spying on.
Toolbar Options
Monitoring Window
Display Option
NOTE: Setting the Display format will make it easier to view the saved monitoring
log in either a RTF or DOC format.
8. Start monitoring by clicking the Disconnected Port Icon on the
• The Clear button in the viewing Options window will clear all the contents
in the Comm Window.
11. If you choose to save the data logged in the Comm window by:
a. Click File and then click Save Log.
b. In the Save As window type a file name and click doc Files
(*.doc) in the Save as type dropdown box.
c. Navigate to the location for the file to be save in the Save in
dropdown box and then click Save.
12. When finished follow steps 8-9 in Procedure B to properly reconnect the
LIS serial communication line.
13. Exit out of the 232Anlayzer software by clicking File and then click Exit.
Regulatory
• There is no risk to health.
• There is no safety hazard.
Issued By
This document is issued by Siemens Healthcare Diagnostics Inc., Global Support
and Service, Phone (914) 524-3001, FAX (914) 524-2088.
Trademark Information
Copyright © 2008 CommFront Communications
Ring Indicator RI 22 9
* On RJ45 pin 4 is Tx ground and pin 5 is Rx ground
Null Modem
Null modem is a communication method to connect two DTEs (computer, terminal, printer etc.)
directly using a RS-232 serial cable. The original RS-232 standard only defined the connection
of DTEs with DCEs i.e. modems. With a null modem connection the transmit and receive lines
are crosslinked. Depending on the purpose, sometimes also one or more handshake lines are
crosslinked. Several wiring layouts are in use because the null modem connection is not
covered by a standard.
Loopback Connector
Sometimes instead of trying to communicate with another computer, you would like to be able to
test the transmission equipment itself. One practical way of doing this is to add a "loopback"
connector to the terminal device, like a PC with a serial data connection. This connector has no
cable attached, but loops the transmit lines to the receive lines. By doing this, you can simulate
both the transmission and receiving of data. When this sort of connector is used, you will
receive every byte that you transmit.
This is the counterpart to DTR with the communications equipment (or computer peripheral on
the serial line). When the DTR is sent as a signal, the communications equipment should
change this signal to -15V to indicate that it is ready to communicate as well. If the DCE goes
through a "boot" sequence when the DTR gets signaled, it should not signal DSR until it is
complete. But many connectors "hard wire" this pin to be directly connected to the DTR pin at
each end to reduce the number of wires needed in the cable. This can be useful for connecting
devices using existing telephone wires, but prevents applications from using the DTR and DSR
for handshaking.
Basically a signal from the DTE that says "Hello!, I'm ready if you are". This is a general
indicator to the DCE that the terminal is ready to start sending and receiving data. If there is
some initialization that needs to happen in the communications equipment, this is a way for the
terminal equipment to "boot" the receiving equipment. In an null modem setup this signal is
often connected to DCD, so the device signals itself that an (imaginary) carrier has been
detected, indication that the transmission line is up.
RX (Receive Data)
TX (Transmit Data)
The reverse of RX, this is where the terminal equipment (DTE) is transmitting serial data, using
the same format and protocol that the receiver is expecting.
A common "ground" reference between the equipment that is being connected to compare the
voltages for the other signals.
The signal (logical "1"), it indicates to the DCE that the terminal is ready to receive more data.
When it has a +15V (logical "0") signal, it indicates that the DCE should stop sending data
temporarily until the buffer can be cleared.
This is the response signal from the DCE regarding if the terminal equipment should be
transmitting any data. When this signal is -15V the terminal is "permitted" to transmit data. Like
the DTR/DSR pins, this one can be directly connected to the RTS pin to reduce the number of
wires needed, but this eliminates the possibility of hardware flow control.
RI (Ring Indicator)
Think back to a telephone modem, this is a signal that indicates that the telephone is "ringing".
Generally, even on a real telephone modem, this is only occasionally set to -15V for the signal.
Basically, when you would normally be hearing a "ring" on your telephone, this pin would be
signaled. On Null-modems, often this wire isn't even connected to anything.
Baud Rate
Baud means the number of changes to the transmission media per second in a modulated
signal. Baud is actually a shortened term named in honor of Émile Baudot, a French inventor of
early teleprinter machines that replaced the telegraph key using Morse Code.
Start Bit
When a transmission line is not sending anything, it remains in a logical state of "1", or -15V on
the wire. When you want to send a character, you start by changing the voltage to +15V,
indicating a logical "0" state. Each subsequent bit is based on the baud rate that is established
for communication between each device. This bit signals that the receiving device should start
scanning for subsequent bits to form the character.
Stop Bits
This really isn't a bit at all, but an agreement that once the character is sent that the transmitting
equipment will return to a logical "1" state. The RS-232 specification requires this logical state of
"1" to remain for at least one whole clock cycle, indicating that the character transmission is
complete.
Data Bits
This is the primary purpose of serial communications, where the data actually gets sent. The
number of bits here can vary quite a bit, although in current practice the number of bits typically
transmitted is eight bits and is a very common unit for transmitting data, and the most common
setting for RS-232 devices today.
The least significant bit (LSB) is transmitted first in this sequence of bits to form a character.
Parity Bit
To help perform a limited error check on the characters being transmitted, the parity bit has
been introduced. Parity can detect some transmission errors but not correct. The value of the
parity bit depends on the number of bits set to "1" in the string of data bits.
Odd Parity
When the sum of bits ends up coming up with an odd number (like the
sequence 01110110), this bit will be set to a logical state of "1".
Even Parity
Mark Parity
Space Parity
he opposite of Mark parity, this sends a logical "0" for the parity
checksum.
Parity None
3. In the Found New Hardware Wizard window click “Install from a list or
specific location (Advanced)” and then click Next.
4. In the Found New Hardware Wizard window click “Search for the best
driver in these locations” and then click “Include this location in the
search”. Browse to the C:\temp folder that was downloaded in step one
and then click Next.
6. Repeat steps three through five for installing port B of the serial
adapter.
7. Confirm the installation was successful by performing the following:
a. Right click on the My Computer icon on the service laptop
desktop and then click Properties.
My Computer Icon
b. At the System Properties window click the Hardware tab and
then click the Device Manager button.
232Analayzer Window
3. In the 232Analyzer window click Next.
Congratulations Window
NOTE: Utilize the 232Analyzer Software help contents on how to operate the
software.