Campbell Scientific MD485 RS-485 Multidrop Interface User Guide

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. There are two RS-485 terminals to allow for easy networking. Both are connected to the same port internally, so either may be used for an RS-485 connection. For networking, one may be used for input and the other for output. Total cable length may be up to 4000 feet.

PDF Download

Document

MD485 RS-485

Multidrop

Interface

User Guide

Issued 14.12.10

©

2003-2010 Campbell Scientific Inc.

Printed under licence by Campbell Scientific Ltd.

CSL 526

Guarantee

This equipment is guaranteed against defects in materials and workmanship.

This guarantee applies for twelve months from date of delivery. We will repair or replace products which prove to be defective during the guarantee period provided they are returned to us prepaid. The guarantee will not apply to:

•

Equipment which has been modified or altered in any way without the written permission of Campbell Scientific

•

Batteries

•

Any product which has been subjected to misuse, neglect, acts of God or damage in transit.

Campbell Scientific will return guaranteed equipment by surface carrier prepaid. Campbell Scientific will not reimburse the claimant for costs incurred in removing and/or reinstalling equipment. This guarantee and the Company’s obligation thereunder is in lieu of all other guarantees, expressed or implied, including those of suitability and fitness for a particular purpose. Campbell

Scientific is not liable for consequential damage.

Please inform us before returning equipment and obtain a Repair Reference

Number whether the repair is under guarantee or not. Please state the faults as clearly as possible, and if the product is out of the guarantee period it should be accompanied by a purchase order. Quotations for repairs can be given on request. It is the policy of Campbell Scientific to protect the health of its employees and provide a safe working environment, in support of this policy a

“Declaration of Hazardous Material and Decontamination” form will be issued for completion.

When returning equipment, the Repair Reference Number must be clearly marked on the outside of the package. Complete the “Declaration of

Hazardous Material and Decontamination” form and ensure a completed copy is returned with your goods. Please note your Repair may not be processed if you do not include a copy of this form and Campbell Scientific Ltd reserves the right to return goods at the customers’ expense.

Note that goods sent air freight are subject to Customs clearance fees which

Campbell Scientific will charge to customers. In many cases, these charges are greater than the cost of the repair.

Campbell Scientific Ltd,

Campbell Park, 80 Hathern Road,

Shepshed, Loughborough, LE12 9GX, UK

Tel: +44 (0) 1509 601141

Fax: +44 (0) 1509 601091

Email: [email protected] www.campbellsci.co.uk

PLEASE READ FIRST

About this manual

Please note that this manual was originally produced by Campbell Scientific Inc. primarily for the

North American market. Some spellings, weights and measures may reflect this origin.

Some useful conversion factors:

Area:

1 in

Length:

(square inch) = 645 mm

1 in. (inch) = 25.4 mm

1 ft (foot) = 304.8 mm

1 yard = 0.914 m

1 mile = 1.609 km

Mass:

1 oz. (ounce) = 28.35 g

1 lb (pound weight) = 0.454 kg

Pressure:

1 psi (lb/in

) = 68.95 mb

Volume:

1 UK pint = 568.3 ml

1 US gallon = 3.785 litres

In addition, while most of the information in the manual is correct for all countries, certain information is specific to the North American market and so may not be applicable to European users.

Differences include the U.S standard external power supply details where some information (for example the AC transformer input voltage) will not be applicable for British/European use.

Please note, however, that when a power supply adapter is ordered it will be suitable for use in your country.

Reference to some radio transmitters, digital cell phones and aerials may also not be applicable according to your locality.

Some brackets, shields and enclosure options, including wiring, are not sold as standard items in the

European market; in some cases alternatives are offered. Details of the alternatives will be covered in separate manuals.

Part numbers prefixed with a “#” symbol are special order parts for use with non-EU variants or for special installations. Please quote the full part number with the # when ordering.

Recycling information

At the end of this product’s life it should not be put in commercial or domestic refuse but sent for recycling. Any batteries contained within the product or used during the products life should be removed from the product and also be sent to an appropriate recycling facility.

Campbell Scientific Ltd can advise on the recycling of the equipment and in some cases arrange collection and the correct disposal of it, although charges may apply for some items or territories.

For further advice or support, please contact Campbell Scientific Ltd, or your local agent.

Campbell Scientific Ltd, Campbell Park, 80 Hathern Road, Shepshed, Loughborough, LE12 9GX, UK

Tel: +44 (0) 1509 601141 Fax: +44 (0) 1509 601091

Email: [email protected] www.campbellsci.co.uk

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 ........................................................ 2

3.1.1 Ground Lug .................................................................................... 2

3.1.2 Indicator LEDs ............................................................................... 2

3.1.3 Configuring the MD485 ................................................................. 3

3.2 Power Supplies ......................................................................................... 4

3.3 RS-485 Cable ........................................................................................... 4

3.4 Serial Cables ............................................................................................ 5

4. Quick Start

................................................................... 5

5. System Configuration

................................................. 8

5.1 Transparent Communication .................................................................... 9

5.2 MD9 Emulation ...................................................................................... 11

5.3 PakBus Networking ............................................................................... 11

6. Combining with Other Devices

................................. 12

7. Call-back

..................................................................... 13

8. Wiring Specifications

................................................ 13

8.1 RS-485 Line Length ............................................................................... 13

8.2 Grounding .............................................................................................. 13

8.3 Protection and Isolation ......................................................................... 14

8.4 Termination ............................................................................................ 14

8.5 Summary ................................................................................................ 14

Appendices

A. Phone to MD485 Network

....................................... A-1

B. RF401 to MD485 Network

....................................... B-1

B.1 Connection using a PS100 with A100 ................................................. B-1

B.2 Connection using a Null Modem Cable ............................................... B-4

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.2 Redwing100 and Redwing105 Digital Cellular Modems .................... D-4

E. NL100 to MD485 Network

........................................ E-1

F. MD485 to CC640 Digital Camera

............................ F-1

G. MD485 to AVW200 Interface

................................... G-1

H. MD485 Port Pin Descriptions

................................. H-1

Figures

1. The MD485 has a ground lug that should be attached to earth ground and LEDs that indicate traffic on the ports ....................................... 2

2. MD485 Setup Menu ................................................................................... 3

3. RS-485 Connections and Grounding .......................................................... 5

4. MD485 Basic Point-to-Point Network ....................................................... 6

5. Point-to-Point LoggerNet Network Map .................................................... 7

6. MD485 Point-to-Multipoint Network ........................................................ 8

7. RS-232 to CS I/O Conversion .................................................................... 9

8. Long Distance RS-232 to CS I/O Conversion .......................................... 10

9. MD485 to Serial Printer ........................................................................... 10

10. Transparent Point-to-Multipoint Network .............................................. 11

A-1. Telephone to MD485 Conversion ...................................................... A-1

A-2. LoggerNet Phone to MD485 MD9 Emulation Setup ......................... A-4

B-1. RF401 to MD485 Conversion ............................................................ B-1

B-2. LoggerNet RF401 to MD485 MD9 Emulation Setup ........................ B-3

B-3. LoggerNet PakBus Networking Setup ............................................... B-7

C-1. MD485 to RF401 Conversion ............................................................ C-1

D-1. Digital Cellular Modem to MD485 Conversion ................................. D-1

D-2. LoggerNet Digital Cellular Modem to MD485 MD9

Emulation Setup ........................................................................... D-6

D-3. LoggerNet Digital Cellular Modem to MD485 PakBus

Networking Setup ......................................................................... D-7

E-1. NL100 to MD485 Conversion ............................................................ E-1

E-2. NL100 to MD485 Conversion for MD9 Emulation ........................... E-2

E-3. LoggerNet NL100 to MD485 PakBus Networking Setup ................. E-4

F-1. Camera to MD485 Connection ............................................................ F-1

G-1. MD485 to AVW200 Connection (point-to-point) ............................. G-1

G-2. Deployment tab in DevConfig with proper MD485 configuration .... G-2

Tables

1. Specifications ............................................................................................. 1

2. Lacking 12 V on CS I/O Pin 8 ................................................................... 6

iii

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. There are two RS-485 terminals to allow for easy networking. Both are connected to the same port internally, so either may be used for an RS-485 connection. For networking, one may be used for input and the other for output. Total cable length may be up to 4000 feet.

With the communication link initiated and controlled by a PC using Campbell

Scientific's LoggerNet or similar software, the operation of the MD485 in the system is transparent to the user.

2. Specifications

Table 1. Specifications

Size:

15.88 x 6.35 x 1.91 cm

Weight:

127.6 g

Accessories:

RS-232 cable, SC12 cable, 3-pin Terminal Block (2)

Voltage:

12 Volts from datalogger or Transformer (004202/004248)

Current:

Standby

Communicating 2-7

Power:

Standby

ESD:

Air Discharge Complies with IEC61000-4-2, test level 4 (±15 kV)

Contact Discharge Complies with IEC61000-4-2, test level 4 (±8 kV)

Surge:

Complies with IEC61000-4-5, test level 3 (±2 kV, 2 ohms coupling impedance)

Temperature range:

-25 to +50oC

Baud rates:

115.2K, 57.6K, 38.4K, 19.2K, 9600, 1200

Communication cable:

CABLE2TP-L two-twisted-pair cable

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.

When the RS-485 port is an active port, the LED nearest that connector (labelled

B in Figure 1) indicates traffic on the RS-485 port, and the other LED (labelled A) indicates traffic on the other active port (CS I/O or RS-232). When CS I/O and

RS-232 are the active ports, the LED between the CS I/O connector and the RS-

232 connector (A) indicates activity on the CS I/O port, and the other LED (B) indicates traffic on the RS-232 port. When data is being received and transmitted, the LEDs will flash. The LED for the port that is transmitting will be on more than the LED for the receiving port.

The LED nearest the RS-485 (B) connector will blink twice a second to indicate an RS-485 receiving error. This most likely indicates a wiring problem between the RS-485 ports of the base and remote MD485s.

GND lug connects to earth ground

Figure 1. The MD485 has a ground lug that should be attached to earth ground and LEDs that indicate traffic on the ports.

User Guide

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. Changed settings are saved in Flash memory.

Alternatively, a Setup Menu can be accessed by connecting the MD485’s RS-232 port to a PC running a terminal program such as Hyper Terminal

(shown in

Figure 2) or Procomm

(always 9600 baud, 8-N-1) and pressing the “Setup” button on the MD485. Changed settings are saved in flash memory by selecting menu item “7” as you exit the Setup Menu. If left idle, the Setup Menu will time out 2 minutes after the last received character and exit without saving any parameter changes with the message “Setup Timeout.”

NOTE

A datalogger can remain connected to the CS I/O port while setting

MD485 parameters on the RS-232 port, although CS I/O communications would be inactive until exiting DevConfig or the

Setup Menu.

Figure 2. MD485 Setup Menu

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. You can order the optional wall transformer. In a phone to MD485 base station configuration (without datalogger) the MD485 can obtain power from a PS100 Power Supply with an A100 Null

Modem Adapter. (The PS100 with an A100 attached replaces the PS512M.

Either may be used whenever the PS100/A100 is referenced in this manual.)

The typical remote MD485 will be connected to a datalogger CS I/O port and get its 12 V power from that. If your datalogger is an earlier unit without 12 V on CS

I/O pin 8 (see Table 2) or if the remote MD485 is connecting to a datalogger RS-

232 port, there is an optional Field Power Cable available with tinned leads to connect to power at the datalogger 12 V output terminals and barrel connector to plug into the MD485’s “DC Pwr” jack. If 230 VAC is available at the site, the wall transformer is an option.

A 12 V supply may connect to either the MD485’s “DC Pwr” jack or CS I/O pin 8

(or both, since there is diode isolation between supply inputs). The 12 V supply inputs are diode protected against the application of reverse polarity power.

3.3 RS-485 Cable

The connection between MD485s is made with CABLE2TP-L. For most installations, 22 or 24 AWG twisted pair PVC insulated cable will be appropriate.

One pair is used for the differential data (“A” connects to “A,” “B” connects to

“B”), and one line of the other twisted pair is used for the signal ground (the third connection on the MD485 terminal block). This is shown in Figure 3. The cable shield should be connected to a chassis or earth ground (NOT the signal ground) at one end as shown in figure.

When connecting to equipment that uses “-” and “+” terminal markings, the

MD485 “A” terminal is connected to the “-” terminal and the MD485 “B” terminal is connected to the “+” terminal.

If an application requires both the maximum distance (4000 ft) and the highest data rate (115k) of the MD485, a better quality cable, such as a polyethylene data cable could be used.

(-)

(+)

(-)

(+)

User Guide

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.

A remote MD485 can be connected to a CR200-series, CR800, CR850, CR1000,

CR3000, or CR5000’s RS-232 port with a null modem DB9M/DB9M cable.

4. Quick Start

This section is intended to serve as a “primer” enabling you to quickly build a simple system and see how it operates. This section describes in five steps how to set up a pair of MD485s in a direct connect, point-to-point network. We recommend that you do this before undertaking field installation.

For this system you will need the following hardware or the equivalent:

2. Transformer

3. Serial cable for PC COM port to MD485 RS-232 port (included with

MD485)

4. SC12 cable (included with MD485)

5. CSL Datalogger (such as CR1000, CR3000, CR10X, or CR23X)

6. Field Power Cable if older datalogger or wiring panel doesn’t have 12 V on pin 8 of CS I/O port

7. CABLE2TP-L

You will also need:

1. A PC with one available COM port

2. LoggerNet, PC400, or PC208W installed

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. Use default settings of MD485 setup menu as explained in Section 3.1.3, change the active ports of the base MD485 to “RS-232 and RS-485.” All other options can be left in their default state..

RS-485

RS-232 apx

HICKSVILLE, NEW YORK

CLASS 2 TRANSFORMER

MODEL NO:

INPUT:

AP2105W

120VAC 60Hz 20W

OUTPUT:

UL LISTED

E144634

12VDC 1.0A

MADE IN CHINA

CS I/O

PC Running

LoggerNet or PC400

Figure 4. MD485 Basic Point-to-Point Network

Step 2 – Set Up Remote MD485

a. Connect SC12 cable from datalogger CS I/O port to remote MD485

CS I/O port. Current datalogger/wiring panel CS I/O ports apply power to the remote MD485.

With older dataloggers lacking 12 V on pin 8 (see Table 2), you can power the MD485 using a Field Power Cable (see above hardware list) between the datalogger’s 12 V (output) terminals and the MD485’s “DC Pwr” jack.

Table 2. Lacking 12 V on CS I/O Pin 8

CR7 700X Bd.

< 2779

CR10 Wiring Panels All (black, grey, silver)

PS512M Power Supply < 1712

When you connect power to the MD485 (through the SC12 cable or the optional Field Power Cable) you should see the power-up sequence of the red

LEDs described in Step 1 (assuming datalogger is powered).

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.

User Guide

Step 3 – Connect Base MD485 to Remote MD485

a. Connect CABLE2TP-L 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.

Step 4 – PC400/LoggerNet/PC208W Set-up

a. The next step is to run PC400/LoggerNet/PC208W and configure it to connect to the datalogger via the MD485 point-to-point network you have set up. The MD485 in a point-to-point network can operate transparent to

PC400/LoggerNet/PC208W. Using the EZSetup Wizard in PC400 or

LoggerNet, transparent communications is set up as if it is a direct connect.

If not using the EZSetup Wizard, simply add a datalogger to a COM port in the Device Map.

Figure 5. Point-to-Point LoggerNet Network Map

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.

MD485 RS-485 Multidrop Interface

Datalogger program transfer and data collection are now possible.

5. System Configuration

The block diagram in Figure 6 depicts the connection of a computer to a network of Campbell Scientific dataloggers using MD485s.

RS-485

RS-232

CS I/O

Wall

Transformer

Figure 6. MD485 Point-to-Multipoint Network

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

CABLE2TP-L.

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.

User Guide

5.1 Transparent Communication

When configured as a transparent device, the MD485 simply passes serial data from one interface to the other as quickly as possible without translation. If communication rates are different, the MD485 can buffer up to 1000 bytes.

Functioning as a transparent device, the MD485 becomes somewhat protocol independent. It acts as a way to get from one physical interface to another. In this mode the MD485 uses what is called “send-data” transmit control. The 485 transceiver is normally set to receive. When data needs to be transmitted on the

RS-485 link, the driver is enabled, and stays enabled for 1 character tone after the last byte is sent. After this time, the transceiver switches back to receiving.

When using the EZSetup Wizard provided in PC400 and LoggerNet, select Direct

Connect for the Connection Type. In transparent mode, the MD485 does not need to be represented in the network map of LoggerNet or PC208W.

Figure 7 shows an MD485 being used as an RS-232 to CS I/O interface converter.

The MD485 is powered by the datalogger through the CS I/O interface. RS-232 and CS I/O are chosen as the active ports in the MD485 Setup Menu. In this configuration, the MD485 acts as a full-duplex device, fully compatible with all datalogger protocols and CS I/O configurations.

RS-232

CS I/O

Figure 7. RS-232 to CS I/O Conversion

Figure 8 would allow the longer distance characteristics of RS-485 to be taken advantage of, while still providing an RS-232 interface for the PC and using the

CS I/O interface on the datalogger. A transformer is required to power the

MD485 closest to the PC. The base MD485 has RS-232 and RS-485 chosen as 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.

MD485 RS-485 Multidrop Interface

RS-232

RS-485

CS I/O

To Wall Transformer

Figure 8. Long Distance RS-232 to CS I/O Conversion

Figure 9 shows how an MD485 could be used to send one-way data to a serial printer via a P96 instruction. A null modem may be required in the RS-232 line for the printer. A transformer would be needed to power the MD485 nearest the printer, because the MD485 is not port-powered from the RS-232 or RS-485 ports.

In this configuration, the MD485 near the datalogger has CS I/O and RS-485 as active ports. The CS I/O port should be configured to Addressed Print Device which emulates a CSL SC99. RS-485 and RS-232 are the active ports for the

MD485 near the printer. Since printer data is one-way only, the fact that the RS-

485 interface is half-duplex is not an issue.

G 12V

Logan, Utah

DIFF

G H

AG H

10 11

L AG H

L AG E3 AG G G 5V 5V G

SW 12V CTRL

SW 12V

G 12V

POWER

CS I/O

CR10X WIRING PANEL

MADE IN USA

EARTH

GROUND

DIFF

G H

AG H

4 5

L AG H

L AG E1 AG E2 G

SDM

P1 G P2 G C8 C7 C6 C5 C4 C3 C2 C1 G 12V 12V

WIRING

PANEL NO.

CS I/O

RS-485

Null Modem Cable

To Wall Transformer

Figure 9. MD485 to Serial Printer

Figure 10 shows the MD485 used in a point-to-multipoint configuration. With the

MD485s in transparent mode, only a master-slave protocol is supported.

MODBUS is the only such protocol supported by CSL dataloggers and commonly used in the SCADA industry.

SCADA-PC

User Guide

MODBUS

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 dialling 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.

The MD485 Setup Menu is used to put the device into MD9 emulation mode.

When this option is chosen for the communication mode, an MD9 address must also be assigned. The base MD485 should be given address 255. Remote

MD485s can be assigned addresses between 1 and 254.

In MD9 emulation mode, the MD485 looks like an MD9 to the PC, thus allowing legacy software to use an MD485 network as if it were an MD9 network. In the

LoggerNet Setup Menu, an MD9Base is inserted at the appropriate point in the device map to represent the base MD485. Then an MD9Remote representing each remote MD485 in the network is connected to the MD9Base. The appropriate address for each remote MD485 must be entered into the address field. The corresponding datalogger is then connected to each remote in the network map.

If using PC208W, an MD9 Modem is inserted into the network map to represent the base MD485. The remote MD485s are not shown in the network map.

Rather, the dataloggers are directly attached to the MD9 Modem. The address of each remote MD485 is entered in the “Switch Setting of Remote MD9” field of the corresponding datalogger.

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.

MD485 RS-485 Multidrop 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.

When using PakBus Networking, dataloggers must be set up with PakBus addresses. They must also have beacons or neighbor filters set up as appropriate.

(Beaconing is used for most applications. Networks with RF416s use neighbor filters.)

In PakBus Networking mode, datalogger-to-datalogger communication is possible.

6. Combining with Other Devices

Besides the “direct” to PC communications described in the Quick Start and

System Configuration sections, it is possible to combine methods in datalogger communications.

NOTE

When using the MD9 emulation, PC400 software does not support these combined communication options; use either LoggerNet or

PC208W software.

Some combined communications examples:

1) Phone to MD485: PC to external modem to COM220 to PS100 with A100 to

MD485 to MD485 to datalogger (see Appendix A)

2) RF416 to MD485: PC to RF416s then through null modem cable (or PS100 with A100) to MD485s to datalogger (see Appendix B)

3) MD485 to RF416: PC to MD485s then through null modem cable (or PS100 with A100) to RF416s to datalogger (see Appendix C)

4) Cellular Digital Modem to MD485: PC to modem to Cellular Digital Modem then through null modem cable to MD485 to MD485 to datalogger (see

Appendix D)

5) Network to MD485: PC to Internet to NL100 to MD485 to datalogger (use

LoggerNet IPPort or PC208W socket, remote IP address, port number, see

Appendix E)

The MD485 can also be used with the CC640 digital camera, allowing the distance between the camera and a PakBus datalogger to exceed 25 feet (see

Appendix F).

User Guide

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. The ComPort must have “Call-back Enabled” checked and the datalogger must have the “Call-back ID” entered to match the

Call-back ID in the P97 instruction of the Edlog program.

For information on how to program the datalogger for call-back, see the appendix covering Call-back or Datalogger Initiated Communication in the datalogger manual.

8. Wiring Specifications

8.1 RS-485 Line Length

The EIA/TIA RS-485 communications standard, an upgrade of RS-422, supports

32 devices (driver/receiver pairs) in a party line or multi-drop mode, on a cable of up to 4,000 feet.

The standard specifies that each device has a “unit load” of not more than 12k ohm. It does not specify cable type or data rate.

The MD485 has a 1/8-unit-load receiver input impedance (96k ohm) that allows up to 256 transceivers on the bus. Practical network design will be more of a limitation than the electrical load limit of 256 nodes for the MD485.

The RS-485 data transceivers used in the MD485 feature fail-safe circuitry, which guarantees a logic-high receiver output when the receiver inputs are open or shorted. Because of this no “biasing resistors” need to be used. They also feature reduced slew-rate drivers that minimize EMI and reduce reflections. Because of this, termination resistors do not need to be used for most applications.

8.2 Grounding

The MD485 has a ground lug. Connect this ground lug to earth ground with an 8

AWG wire. This connection should be as short as possible.

The differential signalling of RS-485 does not require a signal ground to communicate. The standard allows for a common-mode voltage (Vcm) of -7 to

+12 V. As long as the MD485 local grounds do not exceed this common-mode voltage limit, the RS-485 communication will work fine.

Over a distance of hundreds or thousand of feet, there can be significant differences in the voltage level of “ground”; it can easily extend beyond the common-mode voltage limits of RS-485. The signal ground wire serves to tie the signal ground of each node to one common ground, which is within the commonmode voltage of the RS-485 specification.

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.

MD485 RS-485 Multidrop Interface

See Figure 1, Figure 3, and Section 3.3 for more information on ground connections.

8.3 Protection and Isolation

The MD485 incorporates gas tubes and multilayer varistors on the RS-485 port for protection against ESD and surge. The MD485 passes IEC61000-4-2, test level 4 for both contact and air discharge. It also passes IEC61000-4-5, test level 3 for surge immunity.

If large ground potentials exist, optical isolation may be desired. One recommended optical isolator is B&B’s Model 485OP, which provides 2 kV isolation. If most of the nodes in the network close together (limited ground differences), and one node is located at a distance (large ground difference), then a single optical isolator can be located on the distant node. If all of the nodes are distant from each other, optical isolation will be needed at every node.

The Model 485OP can also be used as a repeater to extend the network.

8.4 Termination

The RS-485 spec says to use termination. For high baud rates (>115k) and long cable runs, this is true.

In most equipment though, with max speeds of 115kbit, it is unnecessary. Adding termination dramatically increases power consumption, and complicates system design. It rarely solves problems when used in the kilobit data range.

If power is not a concern, and signal integrity is questioned, the network can be terminated with a 120 ohm resistor at the extreme ends of the line. There should be no more than two terminations in a system that does not use repeaters.

8.5 Summary

•

Use two pair, 24 AWG shielded cable for most installations.

•

Connect the MD485’s ground lug to earth ground with an 8 AWG wire. This connection should be as short as possible.

•

Connect the “signal ground” wire between MD485s.

•

Ground the shield at one end only (to earth ground).

•

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.

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. The PS100 provides

5 and 12 volts for system operation and the A100 performs the function of a null modem (the COM220 and MD485 are both "modem" devices).

NOTE

The telephone to MD485 Network using a PS100 with A100 may be done with Transparent Communication or MD9 Emulation, but is not possible with PakBus Networking. Connection to a single

PakBus Datalogger is still possible with Transparent

Communication. PakBus Networking can be done by using a datalogger in place of the PS100/A100 for routing.

To Phone Line

To Wall

Transformer or

Solar Panel

BATTERY - INTERNAL (12V 7 AMP HOUR)

BATTERY

EXTERNAL RECHARGEABLE BATTERY

Logan, Utah

MADE IN USA

CHARGE - CHARGING VOLTAGE PRESENT

OFF ON

- POWER TO 12V TERMINALS WARNING:

PERMANENT DAMAGE TO

RECHARGEABLE CELLS MAY

RESULT IF DISCHARGED

BELOW 10.5 VOLTS

LIFT TO

REMOVE

CHARGE

+12V

FROM CHARGER OR SOLAR PANEL

16-28VDC OR 18VAC RMS

TO EITHER TERMINAL, TO OTHER

POWER TO DATALOGGERS

OR 12V PERIPHERALS

PS100 12V POWER SUPPLY

WITH CHARGING REGULATOR

The A100 Null Modem

Adapter has two 9-pin connectors. The SC12 cable from the COM220 is connected to either connector and the SC12 from the MD485 is connected to the other.

To RS-485 Network

Figure A-1. Telephone to MD485 Conversion

Where a phone to MD485 Base is desired, the following configurations will provide Point-to-Point or Point-to-Multipoint communications.

A-1

Appendix A. Phone to MD485 Network

a. MD485s b. COM220 c. PS100 with A100 d. Transformer (CSI Item # 9591) or solar panel e. Three SC12 cables (one included with each MD485 and one with

COM220)

2. TRANSPARENT COMMUNICATION (POINT-TO-POINT)

PC-Modem----COM220-PS100 with A100-MD485---MD485-DL

LoggerNet Setup

a. Setup:

ComPort_1

PhoneBase

PhoneRemote

CR1000 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. PakBus Port – defaults f. CR1000 – default settings, schedule collections as desired

MD485 Configuration

1) Active Ports – “CS I/O and RS-485”

2) Communication Mode – “Transparent Communication”

3) CS I/O Port Configuration – “Modem to Modem w/o Datalogger”

4) RS-485 Port Configuration – Desired baud rate b. Remote MD485

1) Active Ports – “CS I/O and RS-485”

2) Communication Mode – “Transparent Communication”

3) CS I/O Port Configuration – Modem Enable

4) RS-485 Port Configuration – Desired baud rate

A-2

Appendix A. Phone to MD485 Network

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. MD9Remote – Address: “1“ g. MD9Remote_2 – Address: “2“ h. Dataloggers – default settings, schedule collections as desired

A-3

Appendix A. Phone to MD485 Network

A-4

Figure A-2. LoggerNet Phone to MD485 MD9 Emulation Setup

MD485 Configuration

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

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. HARDWARE

After configuring LoggerNet or PC208W and the MD485s you are ready to set up hardware. The A100 null modem connectors (it’s not important which connector goes to which unit) connect via SC12 cables to the 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.

Appendix A. Phone 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.

A-5

Appendix A. Phone to MD485 Network

This is a blank page.

A-6

Appendix B. RF416 to MD485 Network

Where an RF416 to MD485 network is desired, the following configurations will provide access to an MD485 network via RF416s.

The connection between the remote RF416 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 RF416 and

MD485 are both "modem" devices). 2) Using a null modem cable and transformers to provide power to the RF416 and the MD485.

The following sections will describe how to set-up the RF416 to MD485 network using each of these two methods for each communication mode.

B.1 Connection using a PS100 with A100

Figure B-1 shows an RF416 to MD485 network using a PS100 with A100. The following configurations will provide communications in transparent mode or with MD9 emulation. Connection to a single PakBus datalogger is possible with transparent communication. PakBus Networking is not possible using the

PS100/A100, but can be done using a datalogger in place of the PS100/A100 for routing.

RS-232

To Wall Transformer

Power

CS I/O

BATTERY - INTERNAL (12V 7 AMP HOUR)

BATTERY - EXTERNAL RECHARGEABLE BATTERY

CHARGE - CHARGING VOLTAGE PRESENT

Logan, Utah

MADE IN USA

OFF ON - POWER TO 12V TERMINALS

CHARGE

+12V

FROM CHARGER OR SOLAR PANEL

16-28VDC OR 18VAC RMS

TO EITHER TERMINAL, TO OTHER

POWER TO DATALOGGERS

OR 12V PERIPHERALS

WARNING:

PERMANENT DAMAGE TO

RECHARGEABLE CELLS MAY

RESULT IF DISCHARGED

BELOW 10.5 VOLTS

LIFT TO

REMOVE

PS100 12V POWER SUPPLY

WITH CHARGING REGULATOR

RS-485

Figure B-1. RF416 to MD485 Conversion

CS I/O

B-1

Appendix B. RF416 to MD485 Network

a. MD485s b. RF416s c. PS100 with A100 d. Transformer (CSI Item #15966) for base RF416 e. Transformer (CSI Item # 9591) or solar panel for PS100 f. Three SC12 cables (one included with each MD485 and one with

RF416) g. CABLE2TP

2. TRANSPARENT COMMUNICATION (POINT-TO-POINT)

PC-RF416----RF416-PS100 with A100-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 – default settings, schedule collections as desired

MD485 Configuration

1) Active Ports – “CS I/O and RS-485”

2) Communication Mode – “Transparent Communication”

3) CS I/O Port Configuration – “Modem to Modem w/o Datalogger”

4) RS-485 Port Configuration – Desired baud rate b. Remote MD485

1) Active Ports – “CS I/O and RS-485”

2) Communication Mode – “Transparent Communication”

3) CS I/O Port Configuration – Modem Enable

4) RS-485 Port Configuration – Desired baud rate

RF416 Configuration

The RF416s may be left in their default settings. However, if there is a neighbouring RF416 network, you should change the Hopping Sequence of base and remote RF416s to a new setting to avoid interference.

B-2

Appendix B. RF416 to MD485 Network

PC-RF416 ----RF416-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. LoggerNet RF416 to MD485 MD9 Emulation Setup

B-3

Appendix B. RF416 to MD485 Network

MD485 Configuration

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

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

RF416 Configuration

4. HARDWARE

After configuring LoggerNet or PC208W, the RF416s and the MD485s you are ready to set up hardware. Connect the base RF416 RS-232 port to the PC

COM port. The A100 null modem connectors (it’s not important which connector goes to which unit) connect via SC12 cables to the CS I/O ports of the remote RF416 and the base MD485. Connect power to the 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.

MD485s and you are ready to connect to the datalogger.

B.2 Connection using a Null Modem Cable

The RF416 to MD485 conversion can be done using a null modem cable in place of the PS100/A100. The following configurations will provide communications in transparent mode, MD9 Emulation or PakBus Networking. a. MD485s b. RF416s c. Three transformers (CSI Item #15966) d. Null modem cable (CSI Item #18663) e. Three SC12 cables (one included with each MD485 and one with

RF416) f. CABLE2TP

2. TRANSPARENT COMMUNICATION (POINT-TO-POINT)

PC-RF416----RF416--null modem--MD485---MD485-DL

B-4

Appendix B. RF416 to MD485 Network

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) Active Ports – “RS-232 and RS-485”

2) Communication Mode – “Transparent Communication”

3) RS-232 Port Configuration – Desired baud rate

4) RS-485 Port Configuration – Desired baud rate b. Remote MD485

1) Active Ports – “CS I/O and RS-485”

2) Communication Mode – “Transparent Communication”

3) CS I/O Port Configuration – Modem Enable

4) RS-485 Port Configuration – Desired baud rate

RF416 Configuration

PC-RF416 ----RF416--null modem---MD485 ----------MD485-DL1

---------

--MD485-DL2

LoggerNet Setup

a. Setup:

ComPort_1

MD9Base

MD9Remote

CR23X

MD9Remote_2

CR23X_2 b. ComPort_1 – default settings c. MD9Base – defaults d. MD9Remote – Address: “1“ e. MD9Remote_2 – Address: “2“

B-5

Appendix B. RF416 to MD485 Network

f. Dataloggers – default settings, schedule collections as desired

MD485 Configuration

1) Active Ports – “RS-232 and RS-485”

2) Communication Mode – “MD9 Emulation” with address 255

3) RS-232 Port Configuration – Desired baud rate

4) RS-485 Port Configuration – Desired baud rate

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

RF416 Configuration

PC-RF416 ----RF416--null modem---MD485 ----------MD485-DL1

---------

--MD485-DL2

LoggerNet Setup

a. Setup:

ComPort_1

CR1000

CR1000_2 b. ComPort_1 – default settings c. PakBus Port – defaults d. Dataloggers – corresponding PakBus address, other setting default, schedule collections as desired

B-6

Appendix B. RF416 to MD485 Network

Figure B-3. LoggerNet PakBus Networking Setup

MD485 Configuration

a. Base MD485

1) Active Ports – “RS-232 and RS-485”

2) Communication Mode – “PakBus Networking”

3) RS-232 Port Configuration – Desired baud rate

4) RS-485 Port Configuration – Desired baud rate

1) Active Ports – “CS I/O and RS-485”

2) Communication Mode – “PakBus Networking”

3) CS I/O Port Configuration – SDC Address 7 or SDC Address 8

4) RS-485 Port Configuration – Desired baud rate

RF416 Configuration

B-7

Appendix B. RF416 to MD485 Network

5. HARDWARE

After configuring LoggerNet or PC208W, the RF416s and the MD485s you are ready to set up hardware. Connect the base RF416 RS-232 port to the PC

COM port. Attach the null modem cable to the RS-232 ports of the remote

RF416 and the base MD485. Attach transformers to the DC Pwr jack of each

RF416 and the base MD485.

MD485s and you are ready to connect to the datalogger.

B-8

Appendix C. MD485 to RF416 Network

Where an MD485 to RF416 network is desired, the following configurations will provide access to an RF416 network via MD485s.

The connection between the remote MD485 and the base RF416 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 RF416 and

MD485 are both "modem" devices). 2) Using a null modem cable and transformers to provide power to the RF416 and the MD485.

The following sections will describe how to set-up the MD485 to RF416 network using each of these two methods for each communication mode.

C.1 Connection using a PS100 with A100

Figure C-1 shows an MD485 to RF416 network using a PS100 with A100. The following configurations will provide communications in transparent mode or with MD9 emulation. Connection to a single PakBus datalogger is possible with transparent communication. PakBus Networking is not possible using the

PS100/A100, but can be done using a datalogger in place of the PS100/A100 for routing.

RS-485

RS-232

To Wall Transformer

BATTERY - INTERNAL (12V 7 AMP HOUR)

BATTERY - EXTERNAL RECHARGEABLE BATTERY Logan, Utah

MADE IN USA

CHARGE - CHARGING VOLTAGE PRESENT

OFF ON - POWER TO 12V TERMINALS

CHARGE

+12V

FROM CHARGER OR SOLAR PANEL

16-28VDC OR 18VAC RMS

TO EITHER TERMINAL, TO OTHER

POWER TO DATALOGGERS

OR 12V PERIPHERALS

RECHARGEABLE CELLS MAY

RESULT IF DISCHARGED

BELOW 10.5 VOLTS

LIFT TO

REMOVE

PS100 12V POWER SUPPLY

WITH CHARGING REGULATOR

Wall

Transformer

CS I/O

Figure C-1. MD485 to RF416 Conversion

C-1

Appendix C. MD485 to RF416 Network

a. MD485s b. RF416s c. PS100 with A100 d. Transformer (CSI Item #15966) for base MD485 e. Transformer (CSI Item # 9591) or solar panel for PS100 f. Three SC12 cables (one included with MD485 and one with each

RF416)

2. TRANSPARENT COMMUNICATION (POINT-TO-POINT)

PC-MD485----MD485-PS100 with A100-RF416---RF416-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 – default settings, schedule collections as desired

MD485 Configuration

1) Active Ports – “RS-232 and RS-485”

2) Communication Mode – “Transparent Communication”

3) RS-232 Port Configuration – Desired baud rate

4) RS-485 Port Configuration – Desired baud rate b. Remote MD485

1) Active Ports – “CS I/O and RS-485”

2) Communication Mode – “Transparent Communication”

3) CS I/O Port Configuration – Modem Enable

4) RS-485 Port Configuration – Desired baud rate

RF416 Configuration

The active interface of the base RF416 should be set to “COM2xx to

RF416”. All other RF416 settings maybe left in their default state.

However, if there is a neighbouring RF416 network, you should change the

Hopping Sequence of base and remote RF416s to a new setting to avoid interference.

C-2

Appendix C. MD485 to RF416 Network

PC-MD485----MD485-PS100 with A100-RF416---RF416-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) Active Ports – “RS-232 and RS-485”

2) Communication Mode – “MD9 Emulation” with address 255

3) RS-232 Port Configuration – Desired baud rate

4) RS-485 Port Configuration – Desired baud rate

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

RF416 Configuration

The active interface of the base RF416 should be set to “COM2xx to

RF416”. All other RF416 settings maybe left in their default state.

However, if there is a neighbouring RF416 network, you should change the

Hopping Sequence of base and remote RF416s to a new setting to avoid interference.

4. HARDWARE

After configuring LoggerNet or PC208W, the RF416s and the MD485s you are ready to set up hardware. Connect the base MD485 RS-232 port to the

PC COM port. Attach a transformer to the DC Pwr jack of the base MD485.

The A100 null modem connectors (it’s not important which connector goes to which unit) connect via SC12 cables to the CS I/O ports of the remote

MD485 and the base RF416. Connect power to the PS100. When you turn on the PS100 supply, the MD485 and the RF416 receive 12V power and you will see the LEDs light in their power-up sequence.

The remote RF416 connects to datalogger CS I/O port via an SC12 cable.

Powering up the datalogger will start the RF416 operating.

C-3

Appendix C. MD485 to RF416 Network

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.2 Connection using a Null Modem Cable

The MD485 to RF416 conversion can be done using a null modem cable in place of the PS100/A100. The following configurations will provide communications in transparent mode, MD9 Emulation or PakBus Networking. a. MD485s b. RF416s c. Three transformers (CSI Item #15966) d. Null modem cable (CSI Item #18663) e. Three SC12 cables (one included with each RF416 and one with

MD485)

2. TRANSPARENT COMMUNICATION (POINT-TO-POINT)

PC-MD485----MD485--null modem--RF416---RF416-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 – default settings, schedule collections as desired

MD485 Configuration

1) Active Ports – “RS-232 and RS-485”

2) Communication Mode – “Transparent Communication”

3) RS-232 Port Configuration – Desired baud rate

4) RS-485 Port Configuration – Desired baud rate

C-4

Appendix C. MD485 to RF416 Network

b. Remote MD485

1) Active Ports – “RS-232 and RS-485”

2) Communication Mode – “Transparent Communication”

3) RS-232 Port Configuration – Desired baud rate

4) RS-485 Port Configuration – Desired baud rate

RF416 Configuration

PC-MD485----MD485--null modem---RF416--RF416-DL

LoggerNet Setup

a. Setup:

ComPort_1

MD9Base

MD9Remote

CR23X b. ComPort_1 – default settings c. MD9Base – defaults d. MD9Remote – Address: “1“ e. Dataloggers – default settings, schedule collections as desired

MD485 Configuration

a. Base MD485

1) Active Ports – “RS-232 and RS-485”

2) Communication Mode – “MD9 Emulation” with address 255

3) RS-232 Port Configuration – Desired baud rate

4) RS-485 Port Configuration – Desired baud rate

1) Active Ports – “RS-232 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) RS-232 Port Configuration – Desired baud rate

4) RS-485 Port Configuration – Desired baud rate

C-5

Appendix C. MD485 to RF416 Network

NOTE

RF416 Configuration

When using MD9 Emulation, after disconnecting from a datalogger, you must wait for a 40-second timeout before being able to connect again.

PC-MD485---MD485--null modem---RF416---RF416-DL

LoggerNet Setup

a. Setup:

ComPort_1

CR1000 b. ComPort_1 – default settings c. PakBus Port – defaults d. Dataloggers – corresponding PakBus address, other setting default, schedule collections as desired

MD485 Configuration

1) Active Ports – “RS-232 and RS-485”

2) Communication Mode – “PakBus Networking”

3) RS-232 Port Configuration – Desired baud rate

4) RS-485 Port Configuration – Desired baud rate

1) Active Ports – “RS-232 and RS-485”

2) Communication Mode – “PakBus Networking”

3) RS-232 Port Configuration – Desired baud rate

4) RS-485 Port Configuration – Desired baud rate

RF416 Configuration

C-6

Appendix C. MD485 to RF416 Network

4. HARDWARE

After configuring LoggerNet or PC208W, the RF416s 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 RF416. Attach transformers to the DC Pwr jack of each MD485 and the base RF416.

Remote RF416s normally connect to datalogger CS I/O ports via SC12 cables. Powering up the datalogger will start the RF416 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.

C-7

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.

Digital Cellular Modem

Power

Supply

CS I/O

RS-232 Null Modem Cable

Wall

Transformer

RS-485

Network

Figure D-1. Digital Cellular Modem to MD485 Conversion

D.1 RavenXT-series, Raven100, and Raven110 Digital

Cellular Modems

Where a RavenXT-series, Raven100, or Raven110 digital cellular modem to

MD485 base is desired, the following configurations will provide communications in transparent mode, with MD9 Emulation or PakBus Networking. a. MD485s b. RavenXT-series, Raven100, or Raven110 digital cellular modem d. Null modem cable (CSI Item #18663) e. SC12 cables (one included with each MD485)

2. TRANSPARENT COMMUNICATION (POINT-TO-POINT)

D-1

Appendix D. Digital Cellular Modem to MD485 Network

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). d. CR1000 – default settings, schedule collections as desired

MD485 Configuration

1) Active Ports – “RS-232 and RS-485”

2) Communication Mode – “Transparent Communications”

3) RS-232 Port Configuration – Desired baud rate

4) RS-485 Port Configuration – Desired baud rate

1) Active Ports – “CS I/O and RS-485”

2) Communication Mode – “Transparent Communications”

3) CS I/O Port Configuration – Modem Enable

4) RS-485 Port Configuration – Desired baud rate

D-2

Appendix D. Digital Cellular Modem to MD485 Network

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). d. MD9Remotes – appropriate addresses e. Dataloggers – default settings, schedule collections as desired

MD485 Configuration

1) Active Ports – “RS-232 and RS-485”

2) Communication Mode – “MD9 Emulation” with address 255

3) RS-232 Port Configuration – Desired baud rate

4) RS-485 Port Configuration – Desired baud rate

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

LoggerNet Setup

a. Setup

IPPort

PakBusPort

CR1000

CR1000_2 b. IPPort – Internet IP address/domain name and the Port number (the

Raven template file configures the port to be 3001).

D-3

Appendix D. Digital Cellular Modem to MD485 Network

d. Dataloggers – corresponding PakBus address, other setting defaults, schedule collections as desired

MD485 Configuration

1) Active Ports – “RS-232 and RS-485”

2) Communication Mode – “PakBus Networking”

3) RS-232 Port Configuration – Desired baud rate

4) RS-485 Port Configuration – Desired baud rate

1) Active Ports – “CS I/O and RS-485”

2) Communication Mode – “PakBus Networking”

3) CS I/O Port Configuration – SDC Address 7 or SDC Address 8

4) RS-485 Port Configuration – Desired baud rate

5. HARDWARE

After configuring LoggerNet or PC208W and the DM485s, you are ready to set up hardware. Attach the null modem cable to the RS-232 ports of the digital cellular modem and the base MD485. Attach the wall transformer to the DC Pwr jack of the base MD485.

MD485 s and you are ready to connect to the datalogger.

D.2 Redwing100 and Redwing105 Digital Cellular

Modems

Where a Redwing100 or Redwing105 digital cellular modem to MD485 Base is desired, the following configurations will provide communications in transparent mode, with MD9 Emulation or PakBus Networking. a. MD485s b. Redwing100 or Redwing105 CDMA modem c. Transformer (CSI Item #15966) d. Null modem cable (CSI Item #18663) e. SC12 cables (one included with each MD485)

D-4

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. Base MD485

1) Active Ports – “RS-232 and RS-485”

2) Communication Mode – “Transparent Communication”

3) RS-232 Port Configuration – Desired baud rate

4) RS-485 Port Configuration – Desired baud rate b. Remote MD485

1) Active Ports – “CS I/O and RS-485”

2) Communication Mode – “Transparent Communication”

3) CS I/O Port Configuration – Modem Enable

4) RS-485 Port Configuration – Desired baud rate

PC-Modem----Cell Tower Redwing-null modem cable-MD485 ------MD485-DL1

------MD485-DL2

LoggerNet Setup

a. Setup:

TAPIPort

TAPIRemote

MD9Base

MD9Remote

CR10X

MD9Remote_2

CR10X_2 b. TAPIPort – TAPI line corresponding to PC's modem c. TAPIRemote – input digital cellular modem's phone number d. MD9Base – defaults

D-5

Appendix D. Digital Cellular Modem to MD485 Network

e. MD9Remote – Address: “1“ f. MD9Remote_2 – Address: “2“ g. Dataloggers – default settings, schedule collections as desired

D-6

Figure D-2. LoggerNet Digital Cellular Modem to MD485 MD9 Emulation Setup

MD485 Configuration

1) Active Ports – “RS-232 and RS-485”

2) Communication Mode – “MD9 Emulation” with address 255

3) RS-232 Port Configuration – Desired baud rate

4) RS-485 Port Configuration – Desired baud rate

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

Appendix D. Digital Cellular Modem to MD485 Network

PC-Modem ---Redwing--null modem---MD485 ----------MD485-DL1

---------

--MD485-DL2

LoggerNet SETUP

a. Setup:

TAPIPort

TAPIRemote

PakBus Port

CR1000

CR1000_2 b. TAPIPort – TAPI line corresponding to PC's modem c. TAPIRemote – input digital cellular modem's phone number d. PakBus Port – defaults e. Dataloggers – corresponding PakBus address, other setting default, schedule collections as desired

Figure D-3. LoggerNet Digital Cellular Modem to MD485 PakBus Networking Setup

D-7

Appendix D. Digital Cellular Modem to MD485 Network

MD485 CONFIGURATION

1) Active Ports – “RS-232 and RS-485”

2) Communication Mode – “PakBus Networking”

3) RS-232 Port Configuration – Desired baud rate

4) RS-485 Port Configuration – Desired baud rate

1) Active Ports – “CS I/O and RS-485”

2) Communication Mode – “PakBus Networking”

3) CS I/O Port Configuration – SDC Address 7 or SDC Address 8

4) RS-485 Port Configuration – Desired baud rate

5. HARDWARE

After configuring LoggerNet or PC208W and the MD485s you are ready to set up hardware. Attach the null modem cable to the RS-232 ports of the digital cellular modem and the base MD485. Attach wall transformers to the

DC Pwr jack of the base MD485 and the digital cellular modem.

MD485s and you are ready to connect to the datalogger.

D-8

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

POWER

G 12V

Logan, Utah

RS485

NETW

NL100

ORK LINK INTERF

ACE

CS I/O

RS232

CS I/O

RS232

LAN

SN:

MADE IN U

LAN

LINK

10 B

ASE

To TCP/IP Network

Figure E-1. NL100 to MD485 Conversion

Where an NL100 to MD485 network is desired, the following configurations will provide communications in transparent mode, with MD9 emulation or with

PakBus Networking. The NL100 does not perform MD9 emulation. So at least two MD485s are always required for MD9 emulation with an NL100. a. MD485(s) b. NL100 c. NL100 Transformer (CSI Item #13947) or other source of power for

NL100 e. SC12 cable(s) (one included with each MD485)

2. TRANSPARENT COMMUNICATION (POINT-TO-POINT)

PC------------NL100---MD485-DL

LoggerNet Setup

a. Setup:

IPPort

PakBus Port (PakBus dataloggers only)

CR1000 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.)

E-1

Appendix E. NL100 to MD485 Network

c. PakBus Port – defaults (PakBus dataloggers only) d. CR1000 – default settings, schedule collections as desired

MD485 Configuration

1) Active Ports – “CS I/O and RS-485”

2) Communication Mode – “Transparent Communication”

3) CS I/O Port Configuration – Modem Enable

4) RS-485 Port Configuration – Desired baud rate

NL100 Configuration

1) RS-485 config – “TcpSer”

2) RS-485 bps – Desired baud rate

3) RS-485 serial server port number – May be left at default, but must match what is entered in LoggerNet Setup

4) Ethernet 10BaseT – “enabled”

5) 10BaseT port IP address – NL100 IP address

6) 10BaseT port network mask– NL100 network mask

The other NL100 options can be left in their default state.

To Wall Transformer

POWER

G 12V

Logan, Utah

RS485

CS I/O

NL100

SN:

ACE

MADE IN USA

RS232

LAN

LINK

10 B

ASE

To TCP/IP Network

To Wall Transformer

Figure E-2. NL100 to MD485 Conversion for MD9 Emulation

E-2

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. Dataloggers – default settings, schedule collections as desired

Base MD485 Configuration

1) Active Ports – “RS-232 and RS-485”

2) Communication Mode – “MD9 Emulation” with address 255

3) RS-232 Port Configuration – Desired baud rate

4) 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.

(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

NL100 Configuration

1) RS-232 config – “TcpSer”

2) RS-232 bps – Desired baud rate

3) RS-232 serial server port number – may be left at default, but must match what is entered in LoggerNet setup.

4) Ethernet 10BaseT – “enabled”

5) 10BaseT port IP address – NL100 IP address

6) 10BaseT port network mask– NL100 network mask

The other NL100 options can be left in their default state.

E-3

Appendix E. NL100 to MD485 Network

PC ---------------NL100 ----------MD485-DL1

---------

--MD485-DL2

LoggerNet Setup

a. Setup:

IPPort

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.) c. PakBus Port – defaults d. Dataloggers – corresponding PakBus address, other setting default, schedule collections as desired

E-4

Figure E-3. LoggerNet NL100 to MD485 PakBus Networking Setup

Appendix E. NL100 to MD485 Network

MD485 Configuration

5) Active Ports – “CS I/O and RS-485”

6) Communication Mode – “PakBus Networking”

7) CS I/O Port Configuration – SDC7 or SDC8

8) RS-485 Port Configuration – Desired baud rate

NL100 Configuration

7) RS-485 config – “PakBus”

8) RS-485 bps – Desired baud rate

9) RS-485 beacon interval – 60

10) Ethernet 10aseT – “enabled”

11) 10BaseT port IP address – NL100 IP address

12) 10aseT port network mask– NL100 network mask

13) PakBus/TCP server config – “enabled”

14) PakBus/TCP server port number – May be left at default, but must match what is entered in LoggerNet Setup

The other NL100 options can be left in their default state.

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. For transparent communication or PakBus networking, connect the CABLE2TP cable between the RS-485 ports of the NL100 and the MD485(s) and you are ready to connect to the datalogger(s). For MD9 emulation, connect the RS-

232 port of the NL100 to the RS-232 port of the base MD485. Connect the

CABLE2TP cable between the RS-485 ports of all MD485(s).

E-5

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

MD485 b.

CC640 Digital Camera c.

SC12 cable (one included with each MD485) d.

CABLE5CBL-L 5-conductor cable with shield and Santoprene jacket

MD485 Configuration

Active Ports – CS I/O and RS-485 b.

Communication Mode – PakBus Networking c.

CS I/O Port Configuration – SDC7 or SDC8 d.

RS-485 Port Configuration – Desired baud rate

CC640 Configuration

The camera is configured using DevConfig. a.

PakBus Port – RS-485 b.

PakBus Address –set to a unique value in the PakBus network c.

PakBus Destination Address – the datalogger’s PakBus address d.

RS-485 BAUD rate – this baud rate must match the MD485’s baud rate

All other parameters may use the defaults (see CC640 manual for more information).

Hardware

The MD485 connects to the datalogger via the SC12 cable. Connect the

CABLE5CBL 5-conductor cable to the RS-485 port on the MD485. Connect the other end of the CABLE5CBL cable to the terminal block on the camera.

This is a blank page.

F-1

Appendix F. MD485 to CC640 Digital Camera

F-2

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).

The point-to-multipoint configuration uses several AVW200s. In this configuration, you need one MD485 to connect with the datalogger and another

MD485 for each AVW200 in the network. Each AVW200 must have a unique

PakBus address.

RS-232 Null Modem Cable

RS-485

Null Modem Cable

RS-232

Figure G-1. MD485 to AVW200 Connection (point-to-point)

Hardware Requirements

a. MD485s b. AVW200(s) c. Null Modem Cables (CSI Item #18663); one null modem cable connects the

MD485 to the datalogger; another null modem cable is required for each

AVW200 in the network d. CABLE2TP 2-twisted-pair cable with shield and Santoprene Jacket

MD485 Configuration

Each MD485 in the network must be configured with the following settings (see

Figure G-2): a. Active Ports – RS-232 and RS-485 b. Communication Mode – PakBus Networking c. RS-232 Baud Rate – 38.4k d. RS-485 Baud Rate – 38.4k

G-1

Appendix G. MD485 to AVW200 Interface

Figure G-2. Deployment tab in DevConfig with proper

MD485 configuration.

AVW200 Configuration

The AVW200 is configured using DevConfig. a. Protocol – PakBus b. PakBus Address –set to a unique value for each AVW200 in the network c. RS-232 Baud Rate – 38.4k

Hardware Connections

Use the CABLE2TP cable to connect the MD485s to each other. Use a 18663

Null Modem Cable to connect the MD485 to the datalogger; one end of the null modem cable attaches to the RS-232 port on the MD485, and the other end attaches to the RS-232 port on the datalogger. Use another 18663 Null Modem

Cable to connect each of AVW200s to an MD485; one end of the null modem cable attaches to the RS-232 port on the MD485, and the other end attaches to the

RS-232 port on the AVW200.

G-2

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.

CS I/O

CONNECTOR, 9-PIN D-SUB MALE

PIN I/O FUNCTION DESCRIPTION

1 NC 5 V Supplied by

Datalogger

Datalogger sources 5 VDC to power peripherals

GND 2 GND

3 O

GND

Ring Raised by modem to put datalogger into telecommunications mode

Serial data receive line 4 O RX

5 I Modem determines that associated modem raised the ring line

6 I Synchronous Device

Enable

Used by datalogger to address synchronous devices; can be used as a printer enable

7 I CLK/Handshake Used by datalogger with SDE and

TX lines to transfer data to synchronous devices

8 PWR 12 V Supplied by

Datalogger

Datalogger sources 12 VDC to power peripherals

Serial data transmit line 9 I TX

I = Signal Into the MD485, O = Signal Out of the MD485, NC = No Connection

RS-232 Port

The “RS-232” port is a partial implementation of RS-232C. It is configured as

Data Communications Equipment (DCE) for direct cable connection to Data

Terminal Equipment (DTE) such as a PC serial port.

H-1

Appendix H. MD485 Port Pin Descriptions

RS-232

CONNECTOR, 9-PIN D-SUB FEMALE

PIN I/O FUNCTION

1 +5V DCD

2 O RXD

3 I TXD

4 NC DTR

5 GND GND

6 +5V DSR

7 NC RTS

8 O CTS

9 NC RI

I = Signal Into the MD485, O = Signal Out of the MD485, NC = No Connection

RS-485 Port

RS-485

CONNECTOR, 3-PIN TERMINAL BLOCK

PIN I/O FUNCTION

I = Signal Into the MD485, O = Signal Out of the MD485

H-2

CAMPBELL SCIENTIFIC COMPANIES

Campbell Scientific, Inc. (CSI)

815 West 1800 North

Logan, Utah 84321

UNITED STATES www.campbellsci.com

• [email protected]

Campbell Scientific Africa Pty. Ltd. (CSAf)

PO Box 2450

Somerset West 7129

SOUTH AFRICA www.csafrica.co.za

• [email protected]

Campbell Scientific Australia Pty. Ltd. (CSA)

PO Box 444

Thuringowa Central

QLD 4812 AUSTRALIA www.campbellsci.com.au

• [email protected]

Campbell Scientific do Brazil Ltda. (CSB)

Rua Luisa Crapsi Orsi, 15 Butantã

CEP: 005543-000 São Paulo SP BRAZIL www.campbellsci.com.br

• [email protected]

Campbell Scientific Canada Corp. (CSC)

11564 - 149th Street NW

Edmonton, Alberta T5M 1W7

CANADA www.campbellsci.ca

• [email protected]

Campbell Scientific Centro Caribe S.A. (CSCC)

300N Cementerio, Edificio Breller

Santo Domingo, Heredia 40305

COSTA RICA www.campbellsci.cc

•

[email protected]

Campbell Scientific Ltd. (CSL)

Campbell Park

80 Hathern Road

Shepshed, Loughborough LE12 9GX

UNITED KINGDOM www.campbellsci.co.uk

• [email protected]

Campbell Scientific Ltd. (France)

3 Avenue de la Division Leclerc

92160 ANTONY

FRANCE www.campbellsci.fr

• [email protected]

Campbell Scientific Spain, S. L.

Avda. Pompeu Fabra 7-9

Local 1 - 08024 BARCELONA

SPAIN www.campbellsci.es

• [email protected]

Campbell Scientific Ltd. (Germany)

Fahrenheitstrasse13, D-28359 Bremen

GERMANY www.campbellsci.de

• [email protected]

Please visit www.campbellsci.com to obtain contact information for your local US or International representative.

Hello! I am an AI chatbot specifically trained to assist you with the Campbell Scientific MD485 RS-485 Multidrop Interface User Guide. I have thoroughly reviewed the document and can help you locate the exact information you need or explain the content in clear and simple terms. Whether you’re looking for guidance on specific features, troubleshooting steps, or general usage, feel free to ask your questions. The more details you provide about your concerns or needs, the more accurately and effectively I can assist you!

Show related prompts

Assistant typing

Assistant terminated

Key features

Intelligent RS-485 interface
Configurable to use any two of its three interface ports
Provides connection to an RS-485 network
Provides an RS-232 connection to a datalogger's CS I/O port
Networked for multiple dataloggers communication
Supports up to 4000 feet cable length

Frequently asked questions

The MD485 has two RS-485 ports.

The maximum cable length for the MD485 is 4000 feet.

The MD485 is typically configured using the Device Configuration (DevConfig) utility.

The MD485 supports three communication modes: Transparent Communication, MD9 Emulation, and PakBus Networking.

MD485 RS-485

Multidrop

Interface

User Guide

©

Guarantee

PLEASE READ FIRST

About this manual

Recycling information

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

2. Specifications

3. System Components

4. Quick Start

5. System Configuration

6. Combining with Other Devices

7. Call-back

8. Wiring Specifications

Appendices

A. Phone to MD485 Network

B. RF401 to MD485 Network

C. MD485 to RF401 Network

D. Digital Cellular Modem to MD485 Network

E. NL100 to MD485 Network

F. MD485 to CC640 Digital Camera

G. MD485 to AVW200 Interface

H. MD485 Port Pin Descriptions

Figures

Tables

MD485 RS-485 Multidrop Interface

1. Introduction

2. Specifications

3. System Components

3.1 MD485 RS-485 Multidrop Interface

3.1.1 Ground Lug

3.1.2 Indicator LEDs

3.1.3 Configuring the MD485

3.2 Power Supplies

3.3 RS-485 Cable

3.4 Serial Cables

4. Quick Start

Step 1 – Set Up Base MD485

Step 2 – Set Up Remote MD485

Step 3 – Connect Base MD485 to Remote MD485

Step 4 – PC400/LoggerNet/PC208W Set-up

Step 5 – Connect

5. System Configuration

5.1 Transparent Communication

5.2 MD9 Emulation

5.3 PakBus Networking

6. Combining with Other Devices

7. Call-back

8. Wiring Specifications

8.1 RS-485 Line Length

8.2 Grounding

8.3 Protection and Isolation

8.4 Termination

8.5 Summary

Appendix A. Phone to MD485 Network

Appendix B. RF416 to MD485 Network

B.1 Connection using a PS100 with A100

B.2 Connection using a Null Modem Cable

Appendix C. MD485 to RF416 Network

C.1 Connection using a PS100 with A100

C.2 Connection using a Null Modem Cable

Appendix D. Digital Cellular Modem to

MD485 Network

D.1 RavenXT-series, Raven100, and Raven110 Digital

Cellular Modems

D.2 Redwing100 and Redwing105 Digital Cellular

Modems

Appendix E. NL100 to MD485 Network

Appendix F. MD485 to CC640 Digital

Camera

Appendix G. MD485 to AVW200 Interface

Appendix H. MD485 Port Pin

Descriptions

CAMPBELL SCIENTIFIC COMPANIES