MD485 RS-485 Multidrop Interface Revision: 10/10 C o p y r i g h t © 2 0 0 3 - 2 0 1 0 C a m p b e l l S c i e n t i f i c , I n c .
Warranty and Assistance The MD485 RS-485 MULTIDROP INTERFACE is warranted by Campbell Scientific, Inc. to be free from defects in materials and workmanship under normal use and service for twelve (12) months from date of shipment unless specified otherwise. Batteries have no warranty. Campbell Scientific, Inc.'s obligation under this warranty is limited to repairing or replacing (at Campbell Scientific, Inc.'s option) defective products.
MD485 Table of Contents PDF viewers note: These page numbers refer to the printed version of this document. Use the Adobe Acrobat® bookmarks tab for links to specific sections. 1. Introduction..................................................................1 2. Specifications ..............................................................1 3. System Components ...................................................2 3.1 MD485 RS-485 Multidrop Interface ........................................................
MD485 Table of Contents C. MD485 to RF401 Network .......................................C-1 C.1 Connection using a PS100 with A100................................................. C-1 C.2 Connection using a Null Modem Cable .............................................. C-4 D. Digital Cellular Modem to MD485 Network............D-1 D.1 RavenXT-series, Raven100, and Raven110 Digital Cellular Modems ........................................................................................... D-1 D.
MD485 Table of Contents Tables 1. Specifications..............................................................................................1 2. Lacking 12 V on CS I/O Pin 8....................................................................
MD485 Table of Contents iv
MD485 RS-485 Multidrop Interface 1. Introduction The MD485 is an intelligent RS-485 interface. It is configurable to use any two of its three interface ports (RS-485, RS-232 and CS I/O) at a time. The MD485 device's primary function is to provide a connection to an RS-485 network (using CS I/O or RS-232). It can also be used to provide an RS-232 connection to a datalogger's CS I/O port (SDC or ME). MD485s may be networked thereby permitting a computer to address and communicate with multiple dataloggers.
MD485 RS-485 Multidrop Interface 3. System Components 3.1 MD485 RS-485 Multidrop Interface 3.1.1 Ground Lug The MD485 has a GND lug (see Figure 1). Connect this GND lug to earth ground with 8 AWG wire. This connection should be as short as possible. 3.1.2 Indicator LEDs The MD485 has two red LEDs. When 12V power is applied the LEDs light for one second. The LEDs then begin flashing once every two seconds, while there is no activity on the ports.
MD485 RS-485 Multidrop Interface 3.1.3 Configuring the MD485 The MD485 is typically configured using the Device Configuration (DevConfig) utility, which is included with PC400 and LoggerNet and can be downloaded at no charge from our web site. Using DevConfig, you select and configure the active ports and choose the communication mode (see Figure 2). Changed settings are saved in Flash memory.
MD485 RS-485 Multidrop Interface NOTE The baud rate for each port is set independently, so they can be different. However, in some instances, mismatched baud rates can cause an MD485 buffer overflow and create communication failures. Regardless of the baud rates set on other interface ports, the RS-485 ports of all MD485s in a system must be set to the same baud rate. 3.2 Power Supplies The typical base station MD485 connected directly to a PC uses a wall transformer to supply 12 VDC power.
MD485 RS-485 Multidrop Interface (-) (+) (-) (+) Connect at one end only to chassis GND. FIGURE 3. RS-485 Connections and Grounding 3.4 Serial Cables In an MD485 base station, a straight-through DB9M/DB9F RS-232 cable will connect from the MD485’s RS-232 port to the PC COM port. This cable is included with the MD485. A remote MD485 normally uses the included SC12 cable to connect the MD485’s CS I/O port to the datalogger’s CS I/O port.
MD485 RS-485 Multidrop Interface Step 1 – Set Up Base MD485 a. Connect serial cable from PC COM port to base MD485 RS-232 port. b. Plug transformer into AC outlet and plug barrel connector into base MD485 “DC Pwr” jack. You will see both red LEDs light immediately for 1 second. Both LEDs then begin to flash once every 2 seconds. c. Using DevConfig or the MD485 setup menu as explained in Section 3.1.3, change the active ports of the base MD485 to “RS-232 and RS-485.
MD485 RS-485 Multidrop Interface Current dataloggers and wiring panels (not mentioned in Table 2) provide 12 V on pin 8. For older products not listed, check for 12 V between CS I/O connector pin 8 and pin 2 (GND) or contact Campbell Scientific. b. Use default settings of MD485. Step 3 – Connect Base MD485 to Remote MD485 a. Connect the CABLE2TP cable from the 3-pin terminal block on the Base MD485 to the 3-pin terminal block on the Remote MD485 as described in Section 3.3.
MD485 RS-485 Multidrop Interface b. Set the Maximum Baud Rate for 9600 baud which is the rate at which the MD485 communicates by default. The datalogger “Extra Response Time” can be left at 0. Step 5 – Connect You are now ready to Connect to your datalogger using PC400, LoggerNet, or PC208W Connect screen. Datalogger program transfer and data collection are now possible. 5.
MD485 RS-485 Multidrop Interface The base MD485 is connected to the computer's COM port with a serial cable. A transformer supplies +12 VDC power to the MD485. The MD485 at the computer is connected to one or more remote MD485s with the CABLE2TP cable. The MD485 at the datalogger is connected via an SC12 cable (supplied with the MD485) and is powered from the datalogger CS I/O port. Each MD485 includes (2) green 3-pin terminal blocks to allow for cable connections. 5.
MD485 RS-485 Multidrop Interface active ports, while the remote MD485 has the active ports set to RS-485 and CS I/O. With the MD485s configured as transparent devices, the only protocol limitation is the fact that RS-485 is a half-duplex interface. If used with traditional datalogger communication, PC software must take the half-duplex nature of the link into account. For array-based dataloggers, this is accomplished by PC400, LoggerNet, or PC208W. RS-232 RS-485 CS I/O To Wall Transformer FIGURE 8.
MD485 RS-485 Multidrop Interface SCADA-PC MODBUS To Wall Transformer SCADA-PC FIGURE 10. Transparent Point-to-Multipoint Network 5.2 MD9 Emulation In MD9 emulation mode, the MD485 mimics the link-oriented dialing characteristics of the MD9. Note that the RS-485 interface is not physically compatible with the coaxial cable used by the MD9, so an MD485 cannot be used with an MD9. The MD9 emulation mode is not used with PakBus dataloggers, such as the CR800, CR850, CR1000, or CR3000.
MD485 RS-485 Multidrop Interface 5.3 PakBus Networking When configured to use PakBus protocol, the MD485 makes use of the PakBus/Mdrop protocol on the RS-485 side. This allows reliable peer-to-peer networking of multiple devices over the three-wire RS-485 interface. When the communication mode is set to PakBus Networking, the MD485 does not need to be represented in the device map of LoggerNet or PC208W. The dataloggers are simply attached to a PakBusPort.
MD485 RS-485 Multidrop Interface 7. Call-back Datalogger initiated communication, commonly referred to as “call-back,” is possible through MD485s in transparent mode. In order to do call-back, LoggerNet Setup, MD485 Configuration and Hardware should be done as described in the Transparent Communication section of Appendix A with two changes in the LoggerNet Setup.
MD485 RS-485 Multidrop Interface The RS-485 specification also recommends connecting a 100 ohm resistor of at least 0.5 W in series between each node’s signal ground and the network’s ground wire. This resistor is in the MD485, between the terminal block connection marked with the ground symbol and the MD485 power ground. This way, if the ground potentials of two nodes vary, the resistors limit the current in the ground wire. See Figure 1, Figure 3, and Section 3.
MD485 RS-485 Multidrop Interface • In most instances, no termination is required. • If large ground potentials exist, use optical isolation. (B&B’s Model 4850P) • Electrically, 256 MD485s can be connected, but that may be an unmanageable network.
MD485 RS-485 Multidrop Interface 16
Appendix A. Phone to MD485 Network It is possible to access an MD485 network via telephone when the network is miles from the PC. See Figure A-1. A Campbell Scientific Model COM220 Telephone Modem is used in conjunction with a Model PS100 Power Supply and A100 Null Modem Adapter to communicate with an MD485. The COM220 and the MD485 are both supplied with a 9 pin SC12 cable suitable for connection to the A100.
Appendix A. Phone to MD485 Network 1. HARDWARE REQUIREMENTS a. b. c. d. e. f. 2. MD485s COM220 PS100 with A100 Transformer (CSI Item # 9591) or solar panel Three SC12 cables (one included with each MD485 and one with COM220) CABLE2TP cable TRANSPARENT COMMUNICATION (POINT-TO-POINT) PC-Modem----COM220-PS100 with A100-MD485---MD485-DL LoggerNet Setup a. Setup: ComPort_1 PhoneBase PhoneRemote PakBus Port (PakBus dataloggers only) CR1000 b. ComPort_1 – default settings c.
Appendix A. Phone to MD485 Network 3. MD9 EMULATION (POINT-TO-MULTIPOINT) PC-Modem ----COM220-PS100 with A100-MD485 ----------MD485-DL1 ----------MD485-DL2 LoggerNet Setup a. Setup: ComPort_1 PhoneBase PhoneRemote MD9Base MD9Remote CR10X MD9Remote_2 CR10X_2 b. ComPort_1 – default settings c. PhoneBase 1) Modem Type – specify PC's phone modem 2) Maximum Baud Rate – 9600 3) Extra Response Time – 0 s d. PhoneRemote – input base site’s phone number e. MD9Base – defaults f.
Appendix A. Phone to MD485 Network FIGURE A-2. LoggerNet Phone to MD485 MD9 Emulation Setup MD485 Configuration a. Base MD485 1) Active Ports – “CS I/O and RS-485” 2) Communication Mode – “MD9 Emulation” with address 255 3) CS I/O Port Configuration – “Modem to Modem w/o Datalogger” 4) RS-485 Port Configuration – Desired baud rate b. Remote MD485s 1) Active Ports – “CS I/O and RS-485” 2) Communication Mode – “MD9 Emulation” with address 1, 2, etc.
Appendix A. Phone to MD485 Network COM220 and the base MD485 CS I/O port. Connect the site phone line to COM220. Connect power to PS100. When you turn on the PS100 supply, the MD485 receives 12V power and you will see the LEDs light in their power-up sequence. Remote MD485s normally connect to datalogger CS I/O ports via SC12 cables. Powering up the datalogger will start the MD485 operating.
Appendix A. Phone to MD485 Network This is a blank page.
Appendix B. RF401 to MD485 Network Where an RF401 to MD485 network is desired, the following configurations will provide access to an MD485 network via RF401s. The connection between the remote RF401 and the base MD485 can be made in two different ways. 1) Using a Campbell Scientific PS100 Power Supply with A100 Null Modem Adapter. The PS100 provides 5 and 12 volts for system operation and the A100 performs the function of a null modem (the RF401 and MD485 are both "modem" devices).
Appendix B. RF401 to MD485 Network 1. HARDWARE REQUIREMENTS a. b. c. d. e. f. g. 2. MD485s RF401s PS100 with A100 Transformer (CSI Item #15966) for base RF401 Transformer (CSI Item # 9591) or solar panel for PS100 Three SC12 cables (one included with each MD485 and one with RF401) CABLE2TP TRANSPARENT COMMUNICATION (POINT-TO-POINT) PC-RF401----RF401-PS100 with A100-MD485---MD485-DL LoggerNet Setup a. Setup: ComPort_1 PakBus Port (PakBus dataloggers only) CR1000 b. ComPort_1 – default settings c.
Appendix B. RF401 to MD485 Network 3. MD9 EMULATION (POINT-TO-MULTIPOINT) PC-RF401 ----RF401-PS100 with A100-MD485 ----------MD485-DL1 ----------MD485-DL2 LoggerNet Setup a. Setup: ComPort_1 MD9Base MD9Remote CR10X MD9Remote_2 CR10X_2 b. ComPort_1 – default settings c. MD9Base – defaults d. MD9Remote – Address: “1“ e. MD9Remote_2 – Address: “2“ f. Dataloggers – default settings, schedule collections as desired FIGURE B-2.
Appendix B. RF401 to MD485 Network MD485 Configuration a. Base MD485 1) 2) 3) 4) b. Active Ports – “CS I/O and RS-485” Communication Mode – “MD9 Emulation” with address 255 CS I/O Port Configuration – “Modem to Modem w/o Datalogger” RS-485 Port Configuration – Desired baud rate Remote MD485s 1) Active Ports – “CS I/O and RS-485” 2) Communication Mode – “MD9 Emulation” with address 1, 2, etc.
Appendix B. RF401 to MD485 Network 2. TRANSPARENT COMMUNICATION (POINT-TO-POINT) PC-RF401----RF401--null modem--MD485---MD485-DL LoggerNet Setup a. Setup: ComPort_1 PakBus Port (PakBus dataloggers only) CR1000 b. ComPort_1 – default settings c. PakBus Port – defaults (PakBus dataloggers only) d. CR1000 – corresponding PakBus address (PakBus dataloggers only), other settings default, schedule collections as desired MD485 Configuration a. Base MD485 1) 2) 3) 4) b.
Appendix B. RF401 to MD485 Network b. ComPort_1 – default settings c. MD9Base – defaults d. MD9Remote – Address: “1“ e. MD9Remote_2 – Address: “2“ f. Dataloggers – default settings, schedule collections as desired MD485 Configuration a. Base MD485 1) 2) 3) 4) b.
Appendix B. RF401 to MD485 Network FIGURE B-3. LoggerNet PakBus Networking Setup MD485 Configuration a. Base MD485 1) 2) 3) 4) b.
Appendix B. RF401 to MD485 Network 5. HARDWARE After configuring LoggerNet or PC208W, the RF401s and the MD485s you are ready to set up hardware. Connect the base RF401 RS-232 port to the PC COM port. Attach the null modem cable to the RS-232 ports of the remote RF401 and the base MD485. Attach transformers to the DC Pwr jack of each RF401 and the base MD485. Remote MD485s normally connect to datalogger CS I/O ports via SC12 cables. Powering up the datalogger will start the MD485 operating.
Appendix C. MD485 to RF401 Network Where an MD485 to RF401 network is desired, the following configurations will provide access to an RF401 network via MD485s. The connection between the remote MD485 and the base RF401 can be made in two different ways. 1) Using a Campbell Scientific PS100 Power Supply with A100 Null Modem Adapter. The PS100 provides 5 and 12 volts for system operation and the A100 performs the function of a null modem (the RF401 and MD485 are both "modem" devices).
Appendix C. MD485 to RF401 Network 1. HARDWARE REQUIREMENTS a. b. c. d. e. f. g. 2. MD485s RF401s PS100 with A100 Transformer (CSI Item #15966) for base MD485 Transformer (CSI Item # 9591) or solar panel for PS100 Three SC12 cables (one included with MD485 and one with each RF401) CABLE2TP cable TRANSPARENT COMMUNICATION (POINT-TO-POINT) PC-MD485----MD485-PS100 with A100-RF401---RF401-DL LoggerNet Setup a. Setup: ComPort_1 PakBus Port (PakBus dataloggers only) CR1000 b.
Appendix C. MD485 to RF401 Network 3. MD9 EMULATION PC-MD485----MD485-PS100 with A100-RF401---RF401-DL LoggerNet Setup a. Setup: ComPort_1 MD9Base MD9Remote CR10X b. ComPort_1 – default settings c. MD9Base – defaults d. MD9Remote – Address: “1“ e. Datalogger – default settings, schedule collections as desired MD485 Configuration a. Base MD485 1) 2) 3) 4) b.
Appendix C. MD485 to RF401 Network When you turn on the PS100 supply, the MD485 and the RF401 receive 12V power and you will see the LEDs light in their power-up sequence. The remote RF401 connects to datalogger CS I/O port via an SC12 cable. Powering up the datalogger will start the RF401 operating. Connect the two twisted pair, shielded cable between the RS-485 ports of the base and remote MD485s and you are ready to connect to the datalogger. C.
Appendix C. MD485 to RF401 Network b. Remote MD485 1) 2) 3) 4) Active Ports – “RS-232 and RS-485” Communication Mode – “Transparent Communication” RS-232 Port Configuration – Desired baud rate RS-485 Port Configuration – Desired baud rate RF401 Configuration The RF401s may be left in their default settings. However, if there is a neighboring RF401 network, you should change the Hopping Sequence of base and remote RF401s to a new setting to avoid interference. 3.
Appendix C. MD485 to RF401 Network RF401 Configuration The RF401s may be left in their default settings. However, if there is a neighboring RF401 network, you should change the Hopping Sequence of base and remote RF401s to a new setting to avoid interference. NOTE When using MD9 Emulation, after disconnecting from a datalogger, you must wait for a 40-second timeout before being able to connect again. 4. PAKBUS NETWORKING PC-MD485---MD485--null modem---RF401---RF401-DL LoggerNet Setup a.
Appendix C. MD485 to RF401 Network 4. HARDWARE After configuring LoggerNet or PC208W, the RF401s and the MD485s you are ready to set up hardware. Connect the base MD485 RS-232 port to the PC COM port. Attach the null modem cable to the RS-232 ports of the remote MD485 and the base RF401. Attach transformers to the DC Pwr jack of each MD485 and the base RF401. Remote RF401s normally connect to datalogger CS I/O ports via SC12 cables. Powering up the datalogger will start the RF401 operating.
Appendix C. MD485 to RF401 Network This is a blank page.
Appendix D. Digital Cellular Modem to MD485 Network It is possible to access an MD485 network via a digital cellular modem when the network is miles from the PC (see Figure D-1). Although hardware requirements are similar, the LoggerNet setup for our RavenXT-series, Raven100, and Raven110 digital cellular modems is different than the LoggerNet setup for the Redwing100 and Redwing105 digital cellular modems.
Appendix D. Digital Cellular Modem to MD485 Network 2. TRANSPARENT COMMUNICATION (POINT-TO-POINT) PC--—Cell Tower--Raven—null modem—MD485—MD485-DL LoggerNet Setup a. Setup IPPort PakBusPort (PakBus dataloggers only) CR1000 b. IPPort – Internet IP address/domain name and the Port number (the Raven template file configures the port to be 3001). c. PakBus Port—defaults d. CR1000 – default settings, schedule collections as desired MD485 Configuration a. Base MD485 1) 2) 3) 4) b.
Appendix D. Digital Cellular Modem to MD485 Network 3. MD9 EMULATION (POINT-TO-MULTIPOINT) PC--—Cell Tower--Raven—null modem—MD485----MD485-DL1 ---- MD485-DL2 LoggerNet Setup a. Setup IPPort MD9Base MD9Remote CR10X MD9Remote_2 CR10X_2 b. IPPort – Internet IP address/domain name and the Port number (the Raven template file configures the port to be 3001). c. MD9Base —defaults d. MD9Remotes – appropriate addresses e.
Appendix D. Digital Cellular Modem to MD485 Network b. IPPort – Internet IP address/domain name and the Port number (the Raven template file configures the port to be 3001). c. PakBus Port—defaults d. Dataloggers – corresponding PakBus address, other setting defaults, schedule collections as desired MD485 Configuration a. Base MD485 1) 2) 3) 4) b. Remote MD485 1) 2) 3) 4) 5.
Appendix D. Digital Cellular Modem to MD485 Network 2. TRANSPARENT COMMUNICATION PC-Modem----Cell Tower Redwing-null modem-MD485-MD485-DL LoggerNet Setup a. Setup: TAPIPort TAPIRemote PakBus Port (PakBus dataloggers only) CR1000 b. TAPIPort – TAPI line corresponding to PC's modem c. TAPIRemote – input digital cellular modem's phone number d. PakBus Port – defaults (PakBus dataloggers only) e. CR1000 – default settings, schedule collections as desired MD485 Configuration a.
Appendix D. Digital Cellular Modem to MD485 Network c. TAPIRemote – input digital cellular modem's phone number d. MD9Base – defaults e. MD9Remote – Address: “1“ f. MD9Remote_2 – Address: “2“ g. Dataloggers – default settings, schedule collections as desired FIGURE D-2. LoggerNet Digital Cellular Modem to MD485 MD9 Emulation Setup MD485 Configuration a.
Appendix D. Digital Cellular Modem to MD485 Network b. Remote MD485s 1) Active Ports – “CS I/O and RS-485” 2) Communication Mode – “MD9 Emulation” with address 1, 2, etc. (unique for each remote MD485 and must agree with respective MD9 in device map) 3) CS I/O Port Configuration – Modem Enable 4) RS-485 Port Configuration – Desired baud rate 4. PAKBUS NETWORKING PC-Modem ---Redwing--null modem---MD485 ----------MD485-DL1 -----------MD485-DL2 LoggerNet SETUP a.
Appendix D. Digital Cellular Modem to MD485 Network FIGURE D-3. LoggerNet Digital Cellular Modem to MD485 PakBus Networking Setup MD485 CONFIGURATION a. Base MD485 1) 2) 3) 4) b. Remote MD485s 1) 2) 3) 4) 5.
Appendix D. Digital Cellular Modem to MD485 Network Remote MD485s normally connect to datalogger CS I/O ports via SC12 cables. Powering up the datalogger will start the MD485 operating. Connect the CABLE2TP cable between the RS-485 ports of the base and remote MD485s and you are ready to connect to the datalogger.
Appendix D. Digital Cellular Modem to MD485 Network This is a blank page.
Appendix E. NL100 to MD485 Network It is possible to access an MD485 network via a TCP/IP network using an NL100. See Figure E-1. To wall transformer Logan, Utah NL10 NETW 0 ORK LINK INTERF ACE POWE R G 12V SN: RS485 RS485 CS I/O LA N LIN K MADE RS232 IN US A 10 BA CS I/O SE T RS232 LAN LINK 10 BA SE T To TCP/IP Network FIGURE E-1.
Appendix E. NL100 to MD485 Network b. IPPort – Internet IP Address – NL100 IP address : NL100 RS-485 serial server port number. (The NL100 RS-485 serial server port number is configured using the NL100 configuration menu.) c. PakBus Port – defaults (PakBus dataloggers only) d.
Appendix E. NL100 to MD485 Network PC -------NL100-------MD485 ----------MD485-DL1 -----------MD485-DL2 LoggerNet Setup a. Setup: IPPort MD9Base MD9Remote CR10X MD9Remote_2 CR10X_2 b. IPPort – Internet IP Address – NL100 IP address : RS-232 serial port number. (The RS-232 serial port number is configured using the NL100 configuration menu.) c. MD9Base – defaults d. MD9Remotes – appropriate addresses e.
Appendix E. NL100 to MD485 Network 4. PAKBUS NETWORKING PC ---------------NL100 ----------MD485-DL1 -----------MD485-DL2 LoggerNet Setup a. Setup: IPPort PakBus Port CR1000 CR1000_2 b. IPPort – Internet IP Address – NL100 IP address : NL100 PakBus/TCP server port number. (In Figure E-3 123.45.6.789 represents the NL100 IP address and 6781 is the NL100 PakBus/TCP server port number. The NL100 PakBus/TCP server port number is configured using the NL100 configuration menu.) E-4 c.
Appendix E. NL100 to MD485 Network FIGURE E-3.
Appendix E. NL100 to MD485 Network 5. HARDWARE After configuring LoggerNet or PC208W, the NL100 and the MD485(s), you are ready to set up hardware. Attach the Ethernet cable to the 10BaseT port of the NL100. Supply power to the NL100. The remote MD485(s) connect to datalogger CS I/O ports via SC12 cables. Powering up the datalogger(s) will start the MD485(s) operating.
Appendix F. MD485 to CC640 Digital Camera The MD485 is used with the CC640 Digital Camera when the distance between the datalogger is greater than 25 ft. MD485 to CC640 communications is only supported with PakBus networking. FIGURE F-1. Camera to MD485 Connection Hardware Requirements a. b. c. d. MD485 CC640 Digital Camera SC12 cable (one included with each MD485) CABLE5CBL-L 5-conductor cable with shield and Santoprene jacket MD485 Configuration a. b. c. d.
Appendix F. MD485 to CC640 Digital Camera This is a blank page.
Appendix G. MD485 to AVW200 Interface The MD485 is used with the AVW200 Interface for situations where wireless communication is impractical and the distance between the AVW200 interfaces needs to be extended. MD485 to AVW200 communications is only supported with PakBus networking. Both point-to-point and point-to-multipoint configurations are possible. The point-to-point configuration is the simplest MD485-to-AVW200 network. In this configuration, two MD485s are required (see Figure G-1).
Appendix G. MD485 to AVW200 Interface MD485 Configuration Each MD485 in the network must be configured with the following settings (see Figure G-2): a. b. c. d. Active Ports – RS-232 and RS-485 Communication Mode – PakBus Networking RS-232 Baud Rate – 38.4k RS-485 Baud Rate – 38.4k FIGURE G-2. Deployment tab in DevConfig with proper MD485 configuration. AVW200 Configuration The AVW200 is configured using DevConfig. a. b. c.
Appendix H. MD485 Port Pin Descriptions CS I/O Port The CS I/O port is Campbell Scientific's input/output port. It is not a standard RS-232 pin-out. The following table provides pin-out information on the port when connected to a datalogger.
Appendix H.
Campbell Scientific Companies Campbell Scientific, Inc. (CSI) 815 West 1800 North Logan, Utah 84321 UNITED STATES www.campbellsci.com • info@campbellsci.com Campbell Scientific Africa Pty. Ltd. (CSAf) PO Box 2450 Somerset West 7129 SOUTH AFRICA www.csafrica.co.za • cleroux@csafrica.co.za Campbell Scientific Australia Pty. Ltd. (CSA) PO Box 444 Thuringowa Central QLD 4812 AUSTRALIA www.campbellsci.com.au • info@campbellsci.com.au Campbell Scientific do Brazil Ltda.
