Auteur: Photo-collector
Date: 01-11-2007 16:41
IBM PC - Typical RS232-C Chassis Configurations
Since the AT, most IBM PC's and their clones have offered RS232-C communications ports as standard items. Two different port
configurations are commonly seen in the field. Below are the pinouts generally encountered. Not all pins are listed as some are unused in
typical interfaces. Note also that IBM's are Data Communications Devices (DTE). So too are all X-Rite instruments. When two DTE devices
are connected a NULL-MODEM cable is required. In this cable several pairs of wires are crossed so as to connect the appropriate signal
and handshake lines.
Envoyer le lien de cette page par courrier électronique
IBM DB9p (9-pin Male) IBM DB25p (25-pin Male)
Pin # Function Pin # Function
2 Receive 2 Transmit
3 Transmit 3 Receive
5 Ground 4 Ready to Send
6 Data Set Ready 5 Clear to Send
7 Ready to Send 6 Data Set Ready
7 Ground
20 Data Terminal Ready
Using HyperTerminal to Test an Interface
HyperTerminal has shipped with Microsoft Windows almost since its introduction. The screen grabs and commentary that follow describe
how to configure this utility program for use as a quick test to ascertain the correct functioning of an X-Rite instrument's RS-232 interface.
Assumptions:
1. That test computer is equipped with a version of Microsoft Windows (Windows 95, Windows 98, or Windows 2000).
2. That computer has available "COMM" port to use for interface testing purposes.
3. That an appropriate X-Rite communications cable is attached to the port.
Note that Palm Pilots, internal modems, and other RS-232 devices may interfere with a computer's ability to operate with X-Rite
instruments. HyperTerminal will generate an error if it is directed to use a port that is already being controlled by other software. It is the
user's responsibility to understand this and to select a port that is free for these testing purposes.
1. Close all programs except Windows itself.
2. Left-click on the "Start" button and then on "Run..." as illustrated. Type in the word "hypertrm"
3. When the application launches, enter a 'name' for the connection - - any text is acceptable as shown.
4. Next select the DIRECT connection where the X-Rite instrument has been attached - generally "COM1" or "COM2".
5. Continue by setting appropriate communications parameters. Illustrated are the settings required for X-Rite instruments that
default to 9,600 baud. This is the most common speed though a few units will default to 1,200 after a factory reset. Note as
shown below, ALL X-Rite instruments require 8 data bits, No parity, 1 stop bit, and No flow control. Only baud may vary according
to model and type!
6. Once configured, HyperTerminal will present the user with a blank white screen. At this point data, entered through the computer's
keyboard, is directly transmitted to the instrument! It will NOT be displayed on the computer's screen! Instead, the screen will
display any and all data that is generated by the instrument.
7. To verify the proper operation of the instrument's RS-232 interface simply type the appropriate 'version' command. For example,
if testing a 500 series instrument, type the following letters and then press the "Enter" key. Type "SV" then "Enter". As shown
below [a] typed characters are NOT displayed and the instrument's response to the command IS displayed.
Done. The above test completely proves the ability of the instrument to both send and receive data. "SV" or "Software Version", followed
by the "Enter" key commands the instrument to identify itself. The attached 500 series instrument responds by sending "X-Rite
530 ,vC625" and then "<00>". The returned information identifies the instrument as an X-Rite model 530 of firmware build vC625. The
second line ( <00>) is the instrument's way of saying that no errors were detected. Should any number other than "00" be returned, refer to
the interface manual to decode the meaning of the error code.
Table that follows details settings required by each instrument model or family. Be aware that firmware in many instruments requires a
"GO" command. This command releases the unit to normal operation after it identifies itself (or after any other remote control instruction).
If this command is not required, the "GO" column is left blank. Finally, all commands are CaSe Sensitive. Be sure to enter the
commands exactly as shown in the table!
Test Unit Baud Handshake Identify Command Go Command
380..391 9,600 Off "SV" + "Enter" "GO" + "Enter"
400..428 1,200 Off "v" + "Enter" "g" + "Enter"
500..530 9,600 Off "SV" + "Enter"
810, 811 1,200 Off "V" + "Enter" "G" + "Enter"
880..892 1,200 Off "SV" + "Enter" "GO" + "Enter"
Envoyer le lien de cette page par courrier électronique
938..978 1,200 Off "v" + "Enter" "g" + "Enter"
939 9,600 Off "SV" + "Enter"
CF57 9,600 Off "V" + "Enter" "G" + "Enter"
DTP12 9,600 Off "SV" + "Enter"
DTP22 9,600 Off "V" + "Enter"
DTP32, 36 9,600 Off "SV" + "Enter"
DTP41 9,600 Off "SV" + "Enter"
DTP51 9,600 Off "SV" + "Enter"
MA58..68II 9,600 Off "v" + "Enter"
SP60..64 9,600 Off "SV" + "Enter"
SP68..98 9,600 Off "v" + "Enter"
|
|
