sensornet, rs-422, and manchester protocols application...

SENSORNET, RS-422, and MANCHESTER PROTOCOLS 8200-2621-01, REV A

APPLICATION NOTE 0026 1 of 36

APPLICATION NOTE

AN_0026

SensorNet, RS-422, and Manchester Protocols

Application Note

This document explains the use of SensorNet, RS-422, and Manchester proprietary protocols. It also illustrates how domes are connected to matrixes / controllers MP48PLUS, MPCPU, MPLT, ADACSNET, and ADTT16E Touch Tracker®.

Contents I. SensorNet Protocol ............................................ 2

SensorNet Protocol Key Points ...................... 2 Advantages of SensorNet Protocol ................ 3

II. RS-422 Protocol ................................................ 4 RS-422 Protocol Key Points ........................... 4 RS-422 Protocol Specifications ...................... 5

III. Manchester Protocol ........................................ 6 Manchester Protocol Key Points..................... 6 Manchester Protocol Specifications ............... 6

Appendix A: Typical SensorNet Connections ....... 7 Appendix B: Typical RS-422 Connections .......... 26 Appendix C: Typical Manchester Connections ... 33

© 2010 Sensormatic Electronics, LLC



I. SensorNet Protocol

SensorNet is a two-wire serial data protocol that provides half-duplex, multi-drop, differential communications.

Cable segment: Includes all of the electrically connected wire between all of the multi-drop devices of a communications topology. It does not include the wire beyond the repeater devices.

Communication Source: The device that is managing the communications or polling other devices, also referred to as host or primary. On a cable segment that does not have a direct communications source it is the repeater that is repeating the data from the host or primary.

Repeater: Any device that will amplify the signal.

Device: Any unit that is attached to a network.

SensorNet Protocol Key Points

1. Only terminate a communications source or network device if it is at the end of a cable or “end-of-

line.” Each SensorNet device has a termination switch or jumper. Terminating the devices at the

ends of the cable prevent the signals from reflecting back along a cable. Proper termination makes

communications more reliable. J-Box and distribution panel outputs renew or amplify the signals,

so they are considered communications sources. In daisy chain and backbone networks, they are

considered end-of-line and should be terminated. In star networks, they are not considered end-of-

line and should not be terminated. J-Box and distribution panel inputs are considered network

devices. Terminate them only if they are end-of-line.

2. No more than four repeaters are allowed between any two devices connected with cable segments

through repeaters. Devices include SensorNet Domes, Touch Trackers, ADMPCPU, SensorNet

I/O units, SensorNet to RS-422 converters, SensorNet Distribution Panels, SensorNet links for

American Dynamics MPLT / MP48 / VM96 / AD168 switches, SensorNet J-Boxes, and fiber optic

transceivers that contain repeaters between their separate output ports.

This 4-repeater restriction includes devices that are not on the same cable segment or leg of the

network. Data packet collisions resulting in loss of data may occur between out-bound (from the

communications source) and in-bound (to the communications source) communications.

3. Signal repeaters (J-Boxes, Distribution Panels) should only be used when cable distances exceed

the maximum allowed or when noise is an issue. SensorNet devices can operate at signal levels

from 0.3V to 5V, but 1V to 5V is recommended.

4. If shielded cable is used, signals may rapidly decline as more devices are connected or as the

cable length increases. As a result, the maximum length is less for shielded cable, and signal

integrity is reduced; therefore they are not recommended, and should only be used for short

distances when unavoidable. Problems have been experienced. The shield should be connected

at the communications source end only.

5. Attach network devices in stages. Check that their response is correct so you can correct the

problem before continuing with the installation. Use ping tests to measure failure rate or operate

the dome to verify proper operation.

6. No more than 32 devices per cable segment. With a daisy chain or backbone network, a cable

segment starts at the first network device on the cable and ends at the last network device on the

cable. The network device at the start or end of the cable may be a communications source. A star

network supports up to four branches. All four branches are considered one cable segment for

determining the cable length. However, the network device at the end of each of the four branches

should be terminated to ensure reliable communication.



7. If a repeater must be used, place the repeater at the 66% distance point along the cable

(measured from the source). This will ensure that there is a reliable signal at the input to the

repeater.

8. SensorNet can be used with Star, Daisy Chain, or Backbone networks.

9. SensorNet connections are not polarized.

Advantages of SensorNet Protocol

1. The connections are not polarized and the two wires can be connected in any order.

2. Firmware can be uploaded to domes using a PC with a USB-to-SensorNet module (ADACSNET), an MP48 Plus system, or an ADTT16E controller.

3. A ping test can be used to determine the reliability of the network.

4. Remote manual dome reset command from console.

5. SensorNet outputs are transformer coupled to provide 2000V galvanic isolation, to prevent ground loops, and to prevent conducted discharge currents from flowing through the system.

6. SensorNet outputs incorporate TVS (Transient Voltage Suppression) surge protection devices and drivers that can withstand 2000V ESD level surges.

7. SensorNet outputs are protected with PTC (Positive Temperature Coefficient) self-resetting fuses to guard against inadvertent wiring connection to up to 30Vac, class 2, LPS power.

Defining Devices vs. Repeaters

Devices

SpeedDome

SpeedDome Ultra

SpeedDome Optima

ADMPCPU

Touch Trackers (VM16, ADTT16E, & VM32)

SensorNet to RS-422 code converter (RCSN422)

USB SensorNet module (ADACSNET)

MPLT matrix

Repeaters

SensorNet J-Boxes

Matrixes such as MP48PLUS, & VM96

SensorNet Fiber Module

SensorNet / Manchester Distribution Panel (ADACSNETD)



SensorNet Protocol Specifications

Item Specifications

Address Range 1 to 254

Bit Rate 230.4 kbps

Network Distance 1 km per node

Maximum Loads 32 per node

Node Repeaters SensorNet J-boxes, distribution panels

Topologies Daisy chain, backbone, or star

Transmission Medium Single Non-polarized unshielded twisted pair UTP 0.326mm2 (22AWG)

Terminating Resistor 120Ω, switch selectable

Physical Layer RS-485, transformer-isolated, 2-wire

Data Encoding FM-0

Link Layer Framing SDLC/HDLC

Link Layer Channel Bi-directional, half duplex

Collision Avoidance Polling by primary Touch Tracker ®

Application Protocol Proprietary

Network Nodes Domes, Junction Boxes, Secondary Touch Tracker, and SensorNet I/O Unit

II. RS-422 Protocol

Duplex RS-422 uses four wires to provide duplex, multi-drop, differential communications.

Advantages: No termination required, allows more repeaters per line.

Disadvantages: Slower speed, 4-wire polarized, less noise immunity.

Simplex RS-422 uses two wires to provide simplex, multi-drop, differential communications.

Advantages: Two wires, no termination required, allows more repeaters per line.

Disadvantages: Slow speed, one-way communications, polarized wiring, less noise immunity.

Network Topologies: Daisy Chain, Backbone.

RS-422 Protocol Key Points

1. RS-422 does not require terminations.

2. If a repeater must be used, place the repeater mid-way along the cable. This will ensure that there

is a reliable signal at the input to the repeater.

3. More than four repeaters are allowed between any two devices on the network. Devices include

Domes, RS-422 converters (RCSN422), RS-422 Distribution Panels, RS-422 links for American

Dynamics MPCPU / MP48 / VM96 / AD168 switches, and RS-422 J-Boxes.

4. Signal repeaters (J-Boxes, Distribution Panels) should only be cascaded when cable distances

exceed the maximum allowed or when noise is an issue.

5. Ground the shield wire at the source device only. This will prevent ground loops.




problem before continuing with the installation.

7. No more than 10 devices per cable segment. With a daisy chain or backbone network, a cable


cable. The network device at the start or end of the cable may be a communications source.

8. RS-422 can be used with Daisy Chain or Backbone networks only.

9. RS-422 connections are polarized. Care must be taken to connect the correct wires to the

appropriate device terminals.

RS-422 Protocol Specifications

Item Duplex RS-422 Simplex RS-422

Cable Type 2 Twisted-Pair Shielded

Belden 8102 / 88102 (0.205mm

2 (24AWG) PVC / FEP 2 pair)

or equivalent

1 Twisted-Pair Shielded

Belden 8102 / 88102 (0.205mm

2 (24AWG) PVC / FEP 2 pair),

Belden 8760 / 88760 (0.823mm

2 (18AWG) PVC/FEP 1 pair)

or equivalent

Wire Gauge 0.326 mm2 (

22AWG) 0.326 mm2 (

22AWG)

Max. Length 1000m (3300ft) 1000m (3300ft)

Connection Polarized Polarized

Termination No No

Data Rate 4.8 kbits/second 4.8 kbits/second

Max. Devices 10 per line 10 per line

Max. Address 99 99

Network Topologies Daisy Chain, Backbone Daisy Chain, Backbone



III. Manchester Protocol

Manchester uses two wires to provide simplex, multi-drop, differential communications.

Advantages: Moderate speed, high noise/surge/static immunity.

Disadvantages: Polarized wiring, not high speed, drives three devices. Proper termination required for reliable communications.

Network Topologies: Daisy Chain, Backbone.

Manchester Protocol Key Points

1. Only terminate a communications source or network device if it is at the end of a cable or “end-of-

line”. Each device has a termination switch or jumper. Terminating the devices at the ends of the

cable prevent the signals from reflecting back along a cable. Proper termination makes

communications more reliable. Distribution panel outputs renew or amplify the signals, so they are

considered communications sources. In daisy chain and backbone networks, they are considered

end-of-line and should be terminated. Distribution panel inputs are considered to be network

devices. Terminate them only if they are the end-of-line.

2. If a repeater must be used, place the repeater mid-way along the cable. This will ensure that there

is a reliable signal at the input to the repeater.

3. No more than three repeaters are allowed between any two devices on the network. Devices

include Domes, code converters, Manchester Distribution Panels, and Manchester links for

American Dynamics MPCPU / MP48 / AD168 / AD2150 switches.

4. Signal repeaters (Distribution Panels) should only be cascaded when cable distances exceed the

maximum allowed or when noise is an issue.

5. Ground the shield wire at the source device only. This will prevent ground loops.


problem before continuing with the installation.

7. No more than 3 devices per cable segment. In a daisy chain or backbone network, a cable


cable. The network device at the start or end of the cable may be a communications source.

8. Manchester can be used with Daisy Chain or Backbone networks only.

9. Manchester connections are polarized. Care must be taken to connect the correct wires to the

appropriate device terminals.

Manchester Protocol Specifications

Item Description

Cable Type 1 Twisted Pair Shielded (Belden 8760 / 88760 or equivalent)

Wire Gauge 0.823 mm2 (

18AWG)

Max. Length 1500m (5000ft)

Connection Polarized

Termination Yes

Data Rate 31 kbits/second

Max. Devices 3 per line

Max. Address 64

Network Topologies Daisy Chain, Backbone



Appendix A: Typical SensorNet Connections

Figure 1. ADTT16E Star (Diagram 01) ......................................................................... 8

Figure 2. ADTT16E Backbone / Daisy Chain (Diagram 02) ......................................... 9

Figure 3. ADTT16E to RJ6SN to Domes (Diagram 03) ............................................. 10

Figure 4. ADTT16E to ADACSNETD to Domes (Diagram 04) .................................. 11

Figure 5. ADMP48PLUS to Domes (Diagram 05) ...................................................... 12

Figure 6. ADMP48PLUS to RJ6SN to Domes (Diagram 06) ..................................... 13

Figure 7. ADMP48PLUS to ADACSNETD to Domes (Diagram 07) .......................... 14

Figure 8. ADMPLT to Domes (Diagram 08) ............................................................... 15

Figure 9. ADMPLT to RJ6SN to Domes (Diagram 09) .............................................. 16

Figure 10. ADMPLT to ADACSNETD to Domes (Diagram 10) .................................. 17

Figure 11. Intellex to ADACSNET to Domes (Diagram 11) ....................................... 18

Figure 12. Intellex to ADACSNET to RJ6SN to Domes (Diagram 12) ....................... 19

Figure 13. Intellex to ADACSNET to ADACSNETD to Domes (Diagram 13) ............ 20

Figure 14. ADMPCPU to Domes (Diagram 14).......................................................... 21

Figure 15. ADMPCPU to RJ6SN to Domes (Diagram 15) ......................................... 22

Figure 16. ADMPCPU to ADACSNETD to Domes (Diagram 16) .............................. 23

Figure 17. Redundant ADMPCPUs to RJ6SN to Domes (Diagram 17) .................... 24

Figure 18. Redundant ADMPCPUs to ADACSNETD to Domes (Diagram 18) .......... 25



Figure 1. ADTT16E Star (Diagram 01)

ADTT16E Using a Star Topology

Sensornet cable

#4 #3

#2

#5

#1

Sensornet cable

Sensornet cable

T

T

T

150 meters (~500 feet)

75

me

ters

(~

25

0 f

ee

t)

30

me

ters

(~

10

0 f

ee

t)


T

EIMU

ADTT16E

Touch Tracker

Cable

segments

Cable

segments

DIAGRAM #1

NOTE: The External Interface

Module (EIM) is a passive

circuit board required for

interface to and considered

part of the Touch Tracker.

· This is a star topology with 5 devices (key point #8).

· It has 4 branches with less than 32 devices total (key

point #6).

· Devices #1, #2, #3, and #4 are terminated because

they are at the end of the line (key point #1).

· No Sensornet repeater is used (key point #2).

· Total Sensornet cable distance is 345 meters (~1150

feet) (key point #6).

SENSORNET PROTOCOL

KEY POINTS

T

U

Terminated

Unterminated

LEGEND



Figure 2. ADTT16E Backbone / Daisy Chain (Diagram 02)

ADTT16E Using Backbone / Daisy Chain Topology

EIM

ADTT16E

Touch Tracker

Sensornet cable

#1

#2

#3 #4 #5

#6


30 meters

(~100 feet)

45 meters

(~150 feet)

60 meters

(~200 feet)

75 meters

(~250 feet)

T

U

U U U

T

T

U

Terminated

Unterminated

LEGEND

Cable

segment

DIAGRAM #2

· This is a backbone / daisy chain topology

with 6 devices on one cable segment (key

point #8).

· The cable segment starts with device #1,

ends with device #6, and has less than 32

devices (key point #6).

· Devices #1 and the External Interface

Module (EIM) are terminated (key point #1).

· No Sensornet repeater is used (key point

#2).

· The Sensornet network cable length is 360

meters (~1200 feet).

SENSORNET PROTOCOL

KEY POINTS






Daisy Chain

(Cut)

Backbone

(Uncut)



Figure 3. ADTT16E to RJ6SN to Domes (Diagram 03)

RJ6SN

J-BOX

HOST AUX

P2

P1

P3

P4

P5

P6

123 123

123

DOME 123

JW1

DOME 456

JW2

HOST

JW3

AUX

JW4

3 2 1

RJ6SN

J-BOX

HOST AUX

P2

P1

P3

P4

P5

P6

123

123

DOME 123

JW1

DOME 456

JW2

HOST

JW3

3 2 1

P8P8

EIM#1

30

0 m

ete

rs

(~1

00

0 ft.)

REPEATER REPEATER

123

AUX

JW4

U

ADTT16E to RJ6SN to Domes

ADTT16E

Touch Tracker

#1 #2 #3 #4 #5

The repeater function

is not used when the

cable distance from

the Touch Tracker to

the last J-BOX is less

than 1 kilometer

(~3300 feet).

#10

#6 #7

T

U

U U

T

T T

T T

T T T U T

T T

15

0 m

ete

rs (~

50

0 fe

et)9

0 m

ete

rs (

~3

00

fe

et)

75

me

ters

(~2

50

fe

et)

Cable

segments

12

0 m

ete

rs

(~4

00

ft.)


Terminate the

dome or host

when it is at the

end of the line

P4-P6, P1-P3, or

P8

Unterminate the

dome or host when

it is NOT at the end

of the line P4-P6,

P1-P3, or P8

15

0 m

ete

rs (

~5

00

fe

et)

15

0 m

ete

rs (~

50

0 fe

et)


DIAGRAM #3

T

U

Terminated

Unterminated

LEGEND

U T

· Dome #1-2 and #3-5 cable segments are using the daisy-chain

topology (key point #8).

· Domes #1-7 are properly terminated (key point #1).

· Dome #1-2, #3-5, #6, and #7 cable segments have less than 32

devices each (key point #6).

· There are 2 repeaters maximum in the path between any two

devices. From device #6 to #7, the signal passes through only

1 repeater. From device #1 to #6, the signal passes through 2

repeaters (key point #2).

· Repeaters (RJ6SN) are used in this Sensornet configuration

and each cable segment is less than 1km (~3300 feet).

SENSORNET PROTOCOL

KEY POINTS






#8 #9

Balance connection ports

with domes (don't limit

loading to one side).



Figure 4. ADTT16E to ADACSNETD to Domes (Diagram 04)

EIM

ADTT16E to ADACSNETD to Domes

ADTT16E

Touch Tracker

· Domes #1 and #2 are properly terminated (key point #1).

· Domes #1 and #2 are on separate cable segments with less

than 32 devices each (key point #6).

· Between any two devices, such as device #1 and #4 or #1 and

#2, the signal passes through only 1 repeater ADACSNETD

(key point #2).

· A repeater is used in this Sensornet configuration and each

cable segment is less than 1km (~3300 feet).

#1 #2

#4

T

T T

SENSORNET PROTOCOL

KEY POINTS

90

me

ters

(~3

00

fe

et)

75

me

ters

(~

25

0 fe

et)

Cable

segments

ADACSNETD

90

me

ters

(~

30

0 fe

et)

REPEATERT

T T

DIAGRAM #4






#3

T

U

Terminated

Unterminated

LEGEND

Cable

segments

HOST A



Figure 5. ADMP48PLUS to Domes (Diagram 05)

AD MegaPower 48 PLUS to Domes

Sensornet cable

#1

#2

#3 #4 #5


30 meters

(~100 feet)

45 meters

(~150 feet)

60 meters

(~200 feet)

75 meters

(~250 feet)

T

U

U U U

Daisy Chain

(Cut)

Backbone

(Uncut)

Cable

segment


with 6 devices on one cable segment (key

point #8).


ends with device #6, and has less than 32

devices (key point #6).

· Devices #1 and #6 are terminated (key point

#1).


meter (~1200 feet).

SENSORNET PROTOCOL

KEY POINTS

AD MegaPower 48 PLUS

T

DIAGRAM #5

#6

NOTE: Although the MP48 PLUS

has a REPEATER capability, this

configuration does not utilize it.

U

Terminated

Unterminated

LEGEND

T



Figure 6. ADMP48PLUS to RJ6SN to Domes (Diagram 06)

RJ6SN

J-BOX

HOST AUX

P2

P1

P3

P4

P5

P6

123 123

123

DOME 123

JW1

DOME 456

JW2

HOST

JW3

AUX

JW4

3 2 1

RJ6SN

J-BOX

HOST AUX

P2

P1

P3

P4

P5

P6

123

123

DOME 123

JW1

DOME 456

JW2

HOST

JW3

3 2 1

P8P8

30

0 m

ete

rs (

~1

00

0 fe

et)

REPEATER REPEATER

123

AUX

JW4

AD MegaPower 48 PLUS to RJ6SN to Domes

#1 #2 #3 #4 #5

Unterminate the

dome or host when


of the line P4-P6,

P1-P3, or P8

#6 #7



loading to one side)

U

U U

T

T T

T T

T T T U T

T T

90

me

ters

(~

30

0 f

ee

t)

75

me

ters

(~2

50

fe

et)

Cable

segments

Terminate the

dome or host

when it is at the

end of the line

P4-P6, P1-P3,

or P8


T

T


15

0 m

ete

rs (~

50

0 fe

et)

12

0 m

ete

rs

(~3

00

fee

t) 15

0 m

ete

rs (

~5

00

fe

et)

15

0 m

ete

rs (~

50

0 fe

et)


·D

om

e #

1-2

an

d #

3-5

ca

ble

se

gm

en

ts a

re u

sin

g th

e d

ais

y-

ch

ain

to

po

log

y (

ke

y p

oin

t #8

).

·D

om

es #

1-7

are

pro

pe

rly te

rmin

ate

d (

ke

y p

oin

t #1).

·D

om

e #

1-2

, #3

-5, #6

, a

nd

#7

ca

ble

se

gm

en

ts h

ave

le

ss th

an

32

de

vic

es e

ach

(ke

y p

oin

t #6).

·T

he

re a

re 3

re

pe

ate

rs m

axim

um

in

th

e p

ath

be

twe

en

an

y tw

o

de

vic

es. F

rom

de

vic

e #

6 to

#7

, th

e s

ign

al p

asse

s th

rou

gh

on

ly 1

re

pe

ate

r. F

rom

de

vic

e #

1 to

#6, th

e s

ign

al p

asse

s

thro

ug

h 3

re

pe

ate

rs (

ke

y p

oin

t #2).

·R

ep

ea

ters

are

use

d in

th

is S

en

so

rne

t co

nfig

ura

tio

n a

nd

ea

ch

ca

ble

se

gm

en

t is

le

ss th

an

1km

(~

33

00

fe

et)

.

SE

NS

OR

NE

T P

RO

TO

CO

L K

EY

PO

INT

S

DIAGRAM #6

Terminated

Unterminated

LEGEND

#8#9

TT

#10

T

U

REPEATER



Figure 7. ADMP48PLUS to ADACSNETD to Domes (Diagram 07)

30

0 m

ete

rs (

~1

00

0 fe

et)

AD MegaPower 48 PLUS to ADACSNETD to Domes


·D

om

es #

1 a

nd

#2

are

pro

pe

rly te

rmin

ate

d (

ke

y p

oin

t #

1).

·D

om

es #

1 a

nd

#2

are

on

se

pa

rate

ca

ble

se

gm

en

ts w

ith

le

ss

tha

n 3

2 d

evic

es e

ach

(ke

y p

oin

t #

6).

·B

etw

ee

n a

ny tw

o d

evic

es,

su

ch

as d

evic

e #

1 a

nd

#4

or

#1

an

d

#2

, th

e s

ign

al p

asse

s th

ru o

nly

1 r

ep

ea

ter

AD

AC

SN

ET

D (

ke

y

po

int #

2).

·R

ep

ea

ters

are

use

d in

th

is S

en

so

rne

t co

nfig

ura

tio

n a

nd

ea

ch

ca

ble

se

gm

en

t is

le

ss th

an

1km

(~

33

00

fe

et)

.

#1 #2

T T

SE

NS

OR

NE

T P

RO

TO

CO

L K

EY

PO

INT

S

75

me

ters

(~

25

0 f

ee

t)

Cable

segments

ADACSNETD9

0 m

ete

rs (

~3

00

fe

et)

REPEATER

T T

T

DIAGRAM #7

T

LEGEND

T

U

Terminated

Unterminated

#3

#4

NOTE: Although the MP48 PLUS

has a REPEATER capability, this

configuration does not utilize it.

HOST A



Figure 8. ADMPLT to Domes (Diagram 08)

30

0 m

ete

rs (

~1

00

0 fe

et)


AD MegaPowerLT to Domes

#17 #18 #19 #20 #1 #2

T U T

AD MegaPower LTCAM 17-32 CAM 1-16

SNET ASNET B

T T

30 meters (~100 feet)·

Do

me

#1

-2 a

nd

#1

7-2

1 c

ab

le s

eg

me

nts

are

usin

g th

e d

ais

y-

ch

ain

to

po

log

y (

ke

y p

oin

t #

8).

·D

om

es #

1, #2

, a

nd

#1

7-2

1 a

re p

rop

erly te

rmin

ate

d (k

ey

po

int #

1).

·D

om

e #

1-

2 a

nd

#1

7-2

1 c

ab

le s

eg

me

nts

ha

ve

le

ss th

an

32

de

vic

es e

ach

(ke

y p

oin

t #

6).

·N

o r

ep

ea

ters

are

use

d in

th

is S

en

so

rne

t co

nfig

ura

tio

n a

nd

ea

ch

ca

ble

se

gm

en

t is

le

ss th

an

1km

(~

33

00

fe

et)

.

SE

NS

OR

NE

T P

RO

TO

CO

L

KE

Y P

OIN

TS


UU

#21

U

NOTE: Each

Sensornet port on the

MPLT has it own

driver which means

port A does not talk to

port B or vice versa.

DIAGRAM #8

LEGEND

T

U

Terminated

Unterminated

U

#3



Figure 9. ADMPLT to RJ6SN to Domes (Diagram 09)

RJ6SN

J-BOX

HOST AUX

P2

P1

P3

P4

P5

P6

123 123

123

DOME 123

JW1

DOME 456

JW2

HOST

JW3

AUX

JW4

3 2 1

RJ6SN

J-BOX

HOST AUX

P2

P1

P3

P4

P5

P6

123

123

DOME 123

JW1

DOME 456

JW2

HOST

JW3

3 2 1

P8P8

30

0 m

ete

rs (

~1

00

0 fe

et)


REPEATER REPEATER

123

AUX

JW4

AD MegaPowerLT to RJ6SN to Domes

#17 #18 #19 #20 #21

Unterminate the

dome or host when


of the line P4-P6,

P1-P3, or P8

#1 #16



loading to one side)

U

U U

T

T T

T T

T T T U T

T T

Terminate the

dome or host

when it is at the

end of the line

P4-P6, P1-P3,

or P8

AD MegaPower LTCAM 17-32 CAM 1-16

SNET ASNET B

T T

15

0 m

ete

rs (~

50

0 fe

et) 1

50

me

ters

(~

50

0 f

ee

t)

15

0 m

ete

rs (~

50

0 fe

et)

90

me

ters

(~

30

0 f

ee

t)

75

me

ters

(~2

50

fe

et)


·D

om

e #

17

-18

an

d #

19-2

1 c

ab

le s

eg

me

nts

are

usin

g th

e

da

isy-c

ha

in to

po

log

y (

ke

y p

oin

t #8).

·D

om

es #

1, #

16

, a

nd

#1

7-2

1 a

re p

rop

erly te

rmin

ate

d (k

ey

po

int #

1).

·D

om

e #

1, #

16

, #

17-1

8, a

nd

#1

9-2

1 c

ab

le s

eg

me

nts

ha

ve

less th

an

32

de

vic

es e

ach

(ke

y p

oin

ts #

6).

·B

etw

ee

n a

ny tw

o d

evic

es, su

ch

as d

evic

e #

1 a

nd

#1

6 o

r #1

7

an

d #

19

, th

e s

ign

al p

asse

s th

ru o

nly

1 r

ep

ea

ter

RJ6S

N (

ke

y

po

int #

2)

·R

ep

ea

ters

are

use

d in

th

is S

en

so

rne

t co

nfig

ura

tio

n a

nd

ea

ch

ca

ble

se

gm

en

t is

le

ss th

an

1km

(~

33

00

fe

et)

.

SE

NS

OR

NE

T P

RO

TO

CO

L K

EY

PO

INT

S

Note: each


MPLT has it own

driver which means



DIAGRAM #9

12

0 m

ete

rs

(~3

00

fee

t)

LEGEND

T

U

Terminated

Unterminated

#2 #3

#4

T T



Figure 10. ADMPLT to ADACSNETD to Domes (Diagram 10)

AD MegaPowerLT to ADACSNETD to

Domes

ADACSNETDADACSNETD

AD MegaPower LT

CAM 17-32 CAM 1-16

SNET ASNET B

TT·

Do

me

#1

7-1

8 a

nd

#1

9-2

1 c

ab

le s

eg

me

nts

are

usin

g th

e

da

isy-c

ha

in to

po

log

y (

ke

y p

oin

t #8).

·D

om

es #

1, #2

, a

nd

#1

7-2

1 a

re p

rop

erly te

rmin

ate

d (

ke

y p

oin

t

#1

).

·D

om

e #

1, #

2, #1

7-1

8, a

nd

#1

9-2

1 c

ab

le s

eg

me

nts

ha

ve

le

ss

tha

n 3

2 d

evic

es e

ach

(ke

y p

oin

t #

6).

·B

etw

ee

n a

ny tw

o d

evic

es, su

ch

as d

evic

e #

1 a

nd

#2

or

#1

7

an

d #

19

, th

e s

ign

al p

asse

s th

rou

gh

on

ly 1

re

pe

ate

r

AD

AC

SN

ET

D (

ke

y p

oin

t #2)

·R

ep

ea

ters

are

use

d in

th

is S

en

so

rne

t co

nfig

ura

tio

n a

nd

ea

ch

ca

ble

se

gm

en

t is

le

ss th

an

1km

(~

33

00

fe

et)

.

SE

NS

OR

NE

T P

RO

TO

CO

L

KE

Y P

OIN

TS

30

0 m

ete

rs (

~1

00

0 fe

et)

30

0 m

ete

rs (

~1

00

0 fe

et)

#17 #18 #19 #20

#1 #2T U

T

150 meter (~500 feet)

U

#21

U


T

Cable segments

30

0 m

ete

rs

(~1

00

0 fe

et)

Note: Each


MPLT has it own

driver which means



30

0 m

ete

rs (

~1

00

0 fe

et)

30

0 m

ete

rs (

~1

00

0 fe

et)

T

DIAGRAM #10

LEGEND

T

U

Terminated

Unterminated

T T

T T

T T

#3 #4

#5

REPEATER REPEATER

HOST A HOST A



Figure 11. Intellex to ADACSNET to Domes (Diagram 11)

Intellex to ADACSNET to Domes

#1

#2

#3 #4 #5

15

0 m

ete

rs (~

50

0 ft.)

30 meters

(~100 ft)

45 meters

(~150 ft.)

60 meters

(~200 ft.)

75 meters

(~250 ft.)

T

U

U U U

T

U

Terminated

Unterminated

LEGEND

Daisy Chain

(Cut)

Backbone

(Uncut)

INTELLEX REAR VIEW

USB

PORT


with 6 devices on one cable segment

(key point # 8).

· The cable segment starts with device #1

and ends with #6 and has less than 32

devices on it (key point #6).

· Devices #1 and ADACSNET are

terminated (key point #1).

· No Sensornet repeater is used (key point

#2).

· The Sensornet network cable length is

360 meters (~1200 feet).

SENSORNET PROTOCOL

KEY POINTS

#6

ADACSNET

T

DIAGRAM #11



Figure 12. Intellex to ADACSNET to RJ6SN to Domes (Diagram 12)

RJ6SN

J-BOX

HOST AUX

P2

P1

P3

P4

P5

P6

123 123

123

DOME 123

JW1

DOME 456

JW2

HOST

JW3

AUX

JW4

3 2 1

RJ6SN

J-BOX

HOST AUX

P2

P1

P3

P4

P5

P6

123

123

DOME 123

JW1

DOME 456

JW2

HOST

JW3

3 2 1

P8P8

30

0 m

ete

rs

(~1

00

0 fe

et)

REPEATER REPEATER

123

AUX

JW4

Intellex to ADACSNET to RJ6SN

to Domes

#1 #2 #3 #4 #5

The repeater function

is not used when the

cable distance from

the ADACSNET to the

last J-BOX is less than

1 kilometer (~3300

feet).

#6 #7

U

U U

T

T T

T T

T T T U T

T T

15

0 m

ete

rs (~

50

0 fe

et)9

0 m

ete

rs (

~3

00

fe

et)

75

me

ters

(~2

50

fe

et)

Cable

segments

12

0 m

ete

rs

(~3

00

fee

t)


Terminate the

dome or host

when it is at the

end of the line

P4-P6, P1-P3, or

P8.

Unterminate the

dome or host when


of the line P4-P6,

P1-P3, or P8.

15

0 m

ete

rs (

~5

00

fe

et)

15

0 m

ete

rs (~

50

0 fe

et)


· Dome #1-2 and #3-5 cable segments are using the daisy-

chain topology (key point #8).

· Domes #1-7 are properly terminated (key point #1).

· Dome #1-2, #3-5, #6, and #7 cable segments have less

than 32 devices each (key point #6).

· There are 2 repeaters maximum in the path between any

two devices. From device #10 to #1, the signal passes

through only 1 repeater. From device #1 to #6, the signal

passes through 2 repeaters (key point #2).

· Repeaters are used in this Sensornet configuration and

each cable segment is less than 1km (~3300 feet).

SENSORNET PROTOCOL KEY POINTS

INTELLEX REAR VIEW

#10

ADACSNET

TUSB

PORT

DIAGRAM #12

#8 #9

LEGEND

T Terminated

Unterminated

T

U

U



loading to one side).



Figure 13. Intellex to ADACSNET to ADACSNETD to Domes (Diagram 13)

Intellex to ADACSNET to ADACSNETD

to Domes

· Domes #1 and #2 are properly terminated (key point

#1).

· Domes #1 and #2 are on separate cable segments

with less than 32 devices each (key point #6).

· Between any two devices, such as device #1 and #4

or #1 and #2, the signal passes through only 1

repeater ADACSNETD (key point #2).

· A repeater is used in this Sensornet configuration

and each cable segment is less than 1km (~3300

feet).

#1 #2

T T

SENSORNET PROTOCOL KEY POINTS

90

me

ters

(~

30

0 f

ee

t)

75

me

ters

(~

25

0 f

ee

t)

ADACSNETD

90

me

ters

(~

30

0 f

ee

t)

REPEATERT

T T

INTELLEX REAR VIEW

#4

ADACSNET

T

USB

PORT

DIAGRAM #13

#3

T

U

Terminated

Unterminated

LEGEND

Cable

segments

HOST A



Figure 14. ADMPCPU to Domes (Diagram 14)

ADMPCPU to Domes

17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 DATA L INE

3

42

AD MegaPower CPU

30 meters

(~100 feet)

45 meters

(~150 feet)

60 meters

(~200 feet)

75 meters

(~250 feet)

Sensornet port 2

(dome addresses

255-508)

Sensornet port 1

(dome addresses

001-254)

DIAGRAM #14

Sensornet cable

#1

#2

#3 #4 #5


T

U

U U U

Daisy Chain

(Cut)

Backbone

(Uncut)

Cable

segment

· This is a backbone / daisy chain topology with

6 devices on one cable segment (key point #

8).


ends with the ADMPCPU, and has less than

32 devices (key point #6).

· Device #1 and the ADMPCPU are terminated

(key point #1).

· No Sensornet repeater is used (key point #2).


meters (~1200 feet).

SENSORNET PROTOCOL

KEY POINTS

T

U

Terminated

Unterminated

LEGEND

T

Default Configuration:



Figure 15. ADMPCPU to RJ6SN to Domes (Diagram 15)

ADMPCPU to RJ6SN to Domes

P1

P2

P3

P4

P5

P6

RJ6SN

T

host

T T

T

UU

U

aux

P1

P2

P3

P4

P5

P6

RJ6SN

T

host

T

UT

T

aux

P1

RJ1SNUD

host

T

T

aux

UT

P1

P2

P3

P4

P5

P6

RJ6SN

host

T TREPEATER

UU

aux

P1

RJ1SNUD

host

T

T

aux

T

15

0 m

ete

rs (

~5

00

fe

et)


T

TT


T

#1

#2

#3

#4

#5 #6

#7

#8

#255

17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 DATA L INE

3

42

#256

#257

#258

#259

#260


#261

AD MegaPower CPU

U60 meters (~200 feet)

T

T

REPEATER

REPEATERREPEATER

REPEATER

Sensornet port 2

(dome addresses

255-508)

Sensornet port 1

(dome addresses

001-254)

DIAGRAM #15

U

Terminated

Unterminated

LEGEND

T

TT

TTT




Figure 16. ADMPCPU to ADACSNETD to Domes (Diagram 16)

17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 DATA L INE

3

42

Sensornet port 2

(dome addresses

255-508)

AD MegaPower CPU

#1

U T

90

me

ters

(~3

00

fe

et)

75

me

ters

(~

25

0 fe

et)

Cable

segments

ADACSNETDP

90

me

ters

(~

30

0 fe

et)

T

T T

#2

U

#16

T UU

#17 #18 #19

ADMPCPU to ADACSNETD to Domes

Sensornet port 1

(dome addresses

001-254)

REPEATER

DIAGRAM #16

U

Terminated

Unterminated

LEGEND

T

T


HOST A



Figure 17. Redundant ADMPCPUs to RJ6SN to Domes (Diagram 17)

Redundant ADMPCPUs to RJ6SN to Domes

P1

P2

P3

P4

P5

P6

RJ6SN

T

host

T T

T

UU

T

aux

P1

P2

P3

P4

P5

P6

RJ6SN

T

host

T

UT

T

aux

P1

RJ1SNUD

host

T

T

aux

UU

P1

P2

P3

P4

P5

P6

RJ6SN

host

T TREPEATER

UU

aux

P1

RJ1SNUD

host

T

T

aux

U


T

TT


T

#1

#2

#3

#4

#5 #6

#7

#8

#255

T

U

Terminated

Unterminated

LEGEND

17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 DATA LINE

3

42

Sensornet port 2

(dome addresses

255-508)

#256

#257

#258

#259

#260


#261

AD MegaPower CPU2

T

T

Sensornet port 1

(dome addresses 001-254)

REPEATER

REPEATERREPEATER

REPEATER

17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 DATA LINE

3

42

AD MegaPower CPU1

U

T

U

24

0 m

ete

rs (~

80

0 fe

et)

DIAGRAM #17

T TT

TT





Figure 18. Redundant ADMPCPUs to ADACSNETD to Domes (Diagram 18)

ADACSNETD

T

17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 DATA LINE

3

42

Sensornet port 1


17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 DATA LINE

3

42

AD MegaPower CPU2

AD MegaPower CPU1

Sensornet port 2


Sensornet port 1


Sensornet port 2


#1

#2

#3

200 meters (650 feet)60 meters

(~200 feet)75 meters

(~250 feet)

T U

T T

HOST BHOST A

ADACSNETD

T

#255

#256


60 meters

(~200 feet)

75 meters

(~250 feet)

T U

T T

HOST BHOST A

#257

T



Redundant ADMPCPUs to ADACSNETD to Domes

T

T

T

REPEATER

REPEATER

DIAGRAM #18

U

Terminated

Unterminated

LEGEND

T

U

U





Appendix B: Typical RS-422 Connections

Figure 19. Intellex to ADAC485CV232 (Diagram 22) .......................................... 27

Figure 20. ADMPLT to RCSN422 to Domes (Diagram 23) .................................. 28

Figure 21. ADMPLT to RCSN422 to RJ860 to Domes (Diagram 24) .................. 29

Figure 22. ADMP48PLUS RS-422 to Domes (Diagram 25) ................................ 30

Figure 23. ADMP48PLUS RS-422 to RJ-860 to Domes (Diagram 26) ................ 31

Figure 24. ADMPCPU to AD2083-02C RS-422 to Domes (Diagram 27) ............ 32



Figure 19. Intellex to ADAC485CV232 (Diagram 22)

ADAC485CV232

(RS232 to RS-422 Converter)

Pin 2: TX

Pin 3: RX

Pin 5: GND

12 VDC

SpeedDome

Ultra

DB9M

DB9F

ADACUSBCVT1

(USB to RS-232 Adapter)

Pin 2: RX

Pin 3: TX

Pin 5: GND

INTELLEX

INTELLEX Dome Control Via RS-232 to RS-422

Converter (ADAC485CV232)

DB9M to DB9F

Straight Serial Cable

Dome I/O P1 ADAC485CV232

Pin 1: Rx+ Tx+

Pin 2: Rx- Tx-

Pin 3: Tx+ Rx+

Pin 4: Tx- Rx-

DIAGRAM #22



Figure 20. ADMPLT to RCSN422 to Domes (Diagram 23)

#1

61 2 3 4 5

Ultra I/O Board

P1

R+R-T+T-

sensornet

termination

switch

address swpower switch

rx h

irx

lotx

hi

tx lo

rx h

irx

lotx

hi

tx lo

rx h

irx

lotx

hi

tx lo

rx h

irx

lotx

hi

tx lo

rx h

irx

lotx

hi

tx lo

rx h

irx

lotx

hi

tx lo

rx h

irx

lotx

hi

tx lo

RS422RS422RS422RS422RS422RS422RS422

24

va

c

24

va

cg

nd

RCSN422

REAR VIEW

ADMPLT to RCSN422 Via RS-422 to Domes

NOTE(2): If there are

MINIDOMEs on the RS-422

network, set the device address

to 16. For SPEEDDOME or

later models, set the device

address to 32.

ADCC200/300

KEYBOARD

DOME 1-16DOME 17-32NOTES(1):

· There are 2 separate Sensornet

ports on the ADMPLT -- Port A &

Port B.

· The matrix embedded configuration

menu determines which camera

address is routed to which

Sensornet port.

· By default, ALL of the cameras are

set to AD Up-the-Cable (UTC)

protocol and must be reconfigured

for Sensornet Port A or Port B

routing.

· If conversion of both ports to RS-422

is necessary, a second RCSN422

module is required.

DIAGRAM #23AD MegaPower LT

LEGEND

T

U

Terminated

Unterminated

T

T

RS-422

Sensornet Port A

Sensornet Port B



Figure 21. ADMPLT to RCSN422 to RJ860 to Domes (Diagram 24)

sensornet

termination

switch

address swpower switch

rx h

irx

lotx

hi

tx lo

rx h

irx

lotx

hi

tx lo

rx h

irx

lotx

hi

tx lo

rx h

irx

lotx

hi

tx lo

rx h

irx

lotx

hi

tx lo

rx h

irx

lotx

hi

tx lo

rx h

irx

lotx

hi

tx lo

RS422RS422RS422RS422RS422RS422RS422

24

va

c

24

va

cg

nd

RCSN422

REAR VIEW

ADMPLT to RCSN422 to RJ860 to Domes

1

2

3

4

5

6

7

8

9

10

11

12

RJ860AP

J-BOX

tx h

itx

lo

rx h

irx

lo

RS-422

SEE TABLES BELOW

J1 J2 J3 J4 J5

J6 J7 J8 J9 J10

RJ860-AP TO ULTRA PIGTAIL

(J1-J10)

PIN 1 (TX+) --------------PIN 6 (RX+)

PIN 2 (TX-) ---------------PIN 7 (RX-)

PIN 3 (AC) ----------------PIN 3 (AC)

PIN 4 (GND) --------------PIN 4 (GND)

PIN 5 (AC) ----------------PIN 5 (AC)

PIN 6 (N/A)

PIN 7 (RX-) ---------------PIN 9 (TX-)

PIN 8 (RX+) --------------PIN 8 (TX+)

RJ860-AP TO ULTRA I/O

(J1-J10) P1 P7

PIN 1 (TX+) ------PIN 1 (RX+)

PIN 2 (TX-) -------PIN 2 (RX-)

PIN 3 (AC) --------------------------------PIN 3 (AC)

PIN 4 (GND) ------------------------------PIN 4 (GND)

PIN 5 (AC) ---------------------------------PIN 5 (AC)

PIN 6 (N/A)

PIN 7 (RX-) -------PIN 4 (TX-)

PIN 8 (RX+) ------PIN 3 (TX+)

RJ860-AP TO OPTIMA

(J1-J10)

PIN 1 (TX+) ------PIN 1 (RX+)

PIN 2 (TX-) -------PIN 2 (RX-)

PIN 3 (AC) -------(AC)

PIN 4 (GND) ----(GND)

PIN 5 (AC) -------(AC)

PIN 6 (N/A)

PIN 7 (RX-) -------PIN 4 (TX-)

PIN 8 (RX+) ------PIN 3 (TX+)

RJ860-AP TO OPTIMA LT

(J1-J10)

PIN 1 (TX+) ------PIN 1 (RX+)

PIN 2 (TX-) -------PIN 2 (RX-)

PIN 3 (AC) -------(AC)

PIN 4 (GND) ----(GND)

PIN 5 (AC) -------(AC)

PIN 6 (N/A)

PIN 7 (RX-)

PIN 8 (RX+)

RJ860-AP TO UNICARD SPEEDDOME

(J1-J10) P3

PIN 1 (TX+) --------------PIN 7 (RX+)

PIN 2 (TX-) ---------------PIN 6 (RX-)

PIN 3 (AC) ----------------PIN 3 (AC)

PIN 4 (GND) --------------PIN 4 (GND)

PIN 5 (AC) ----------------PIN 5 (AC)

PIN 6 (N/A)

PIN 7 (RX-) ---------------PIN 1 (TX-)

PIN 8 (RX+) --------------PIN 2 (TX+)

RJ860-AP TO MINIDOME

(J1-J10) J5

PIN 1 (TX+) --------------PIN 1 (RX+)

PIN 2 (TX-) ---------------PIN 2 (RX-)

PIN 3 (AC) ----------------PIN 3 (AC)

PIN 4 (GND) --------------PIN 4 (GND)

PIN 5 (AC) ----------------PIN 5 (AC)

PIN 6 (N/A)

PIN 7 (RX-) ---------------PIN 7 (TX-)

PIN 8 (RX+) --------------PIN 8 (TX+)

ADCC200/300

KEYBOARD

DOME 1-16DOME 17-32

DIAGRAM #24

NOTE(2): If there are

MINIDOMEs on the RS-422

network, set the device address

to 16. For SPEEDDOME or

later models, set the device

address to 32.

Sensornet Port A

NOTES(1):

· There are 2 separate Sensornet ports on

the ADMPLT -- Port A & Port B.

· The matrix embedded configuration

menu determines which camera address

is routed to which SensorNet port.

· By default, ALL of the cameras are set

to AD Up-the-Cable (UTC) protocol and

must be reconfigured for SensorNet Port

A or Port B routing.

· If conversion of both ports to RS-422 is

necessary, a second RCSN422 module

is required.

LEGEND

T

U

Terminated

Unterminated

T

T

Sensornet

Port B



Figure 22. ADMP48PLUS RS-422 to Domes (Diagram 25)

ADMP48PLUS RS-422 to Domes

MegaPower 48 PLUS

#1

61 2 3 4 5

Ultra I/O Board

P1

R+ R- T+ T- R+R- T+ T-

R+R-T+T-

DIAGRAM #25


RS-422



Figure 23. ADMP48PLUS RS-422 to RJ-860 to Domes (Diagram 26)

ADMP48PLUS RS-422 to RJ-860 to Domes

MegaPower 48 PLUS

#1

61 2 3 4 5

Ultra I/O Board

P1

R+ R- T+ T- R+R- T+ T-

R+R-T+T-

121110987654321

Tx+

Cinch Jones

10 Pos. J-Box

( RJ 860 AP )

Dome P1 RJ-860 Cinch Jones

Pin 1~Rx+ Pin 1~Tx+

Pin 2~Rx- Pin 2~Tx-

Pin 3~Tx+ Pin 8~Rx+

Pin 4~Tx- Pin 7~Rx-

Tx-

Rx+

Rx-

MP48PLUS RJ-860 Host

Rx+ Pin 6~Tx+

Rx- Pin 5~Tx-

Tx+ Pin 12~Rx+

Tx- Pin 11~Rx-

DIAGRAM #26




Figure 24. ADMPCPU to AD2083-02C RS-422 to Domes (Diagram 27)


ADMPCPU to AD2083-02C RS-422

to Domes

17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 DATA L INE

3

42

AD MegaPower CPU

Terminated with 75

ohms

Terminated with 75

ohms

#1

61 2 3 4 5

Ultra I/O Board

P1

R+R-T+T-

DIAGRAM #27

61 2 3 4 5

Ultra I/O Board

P1

R+R-T+T-

61 2 3 4 5

Ultra I/O Board

P1

R+R-T+T-

#2 #3

AD2083-02C

Daisy Chain

(Cut)

Backbone

(Uncut)



Appendix C: Typical Manchester Connections

Figure 25. ADMP48PLUS Manchester to Domes (Diagram 19) ................................ 34

Figure 26. ADMP48PLUS Manchester to ADACSNETD to Domes (Diagram 20) .... 35

Figure 27. ADMPCPU to AD0291 Manchester to Domes (Diagram 21) ................... 36



Figure 25. ADMP48PLUS Manchester to Domes (Diagram 19)

ADMP48PLUS Manchester to Domes

#1


MegaPower 48 PLUS

61 2 3 4 5

Ultra I/O Board

P1

B W S

MAN

BW

Note: When using the Manchester

protocol, the maximum number of

domes that may be daisy chained is

3. If more than 3 domes are required,

the ADACSNETD (Manchester

distribution panel) is needed.

DIAGRAM #19

· This is a backbone / daisy chain topology with 3

devices on one cable segment (key points #7 and

#8).

· Device #1 is terminated because it is at the end of

the line (key point #1).

· Devices #1, #2, #3, and #4 are connected

maintaining proper signal polarity (key point #9).

· No Manchester repeater is used (key point #4).

· Total Manchester cable distance is 170 meters

(~600 feet).

MANCHESTER PROTOCOL

KEY POINTS

61 2 3 4 5

Ultra I/O Board

P1

BW

61 2 3 4 5

Ultra I/O Board

P1

BW

#2

#3

U

Daisy Chain

(Cut)

Backbone

(Uncut)

U

T4

0 m

ete

rs (

~1

40

fe

et)

30

me

ters

(~

10

0 f

ee

t)

#4


Terminated

Unterminated

LEGEND

U

T



Figure 26. ADMP48PLUS Manchester to ADACSNETD to Domes (Diagram 20)

30

0 m

ete

r (10

00

fee

t)

AD MegaPower 48 PLUS Manchester to

ADACSNET to Domes

ADACSNETD


MegaPower 48 PLUS

B W S

MAN


#1

61 2 3 4 5

Ultra I/O Board

P1

BW

#2

61 2 3 4 5

Ultra I/O Board

P1

BW

90

me

ters

(~

30

0 f

ee

t)

DIAGRAM #20

REPEATER


T

T

T

T T Terminated

Unterminated

LEGEND

U

T

HOST A



Figure 27. ADMPCPU to AD0291 Manchester to Domes (Diagram 21)

30

0 m

ete

rs (

~1

00

0 fe

et)

ADMPCPU to AD2091 Manchester

to Domes

AD2091

90

me

ters

(~

30

0 f

ee

t)

#1

61 2 3 4 5

Ultra I/O Board

P1

BW

#2

61 2 3 4 5

Ultra I/O Board

P1

BW

17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 DATA L INE

3

42

AD MegaPower CPU

Terminated with 75

ohms

Terminated with 75

ohms

DIAGRAM #21

sensornet, rs-422, and manchester protocols application...

Documents