Manual Jbox

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

SENSORNET, RS-422, and MANCHESTER PROTOCOLS APPLICATION NOTE 0026 8200-2621-01, REV A
1 of 36
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 -ofline. 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-ofline 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.
SENSORNET, RS-422, and MANCHESTER PROTOCOLS APPLICATION NOTE 0026
8200-2621-01, REV A
2 of 36
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)
8200-2621-01, REV A
3 of 36
SensorNet Protocol Specifications Item

Address Range Bit Rate Network Distance Maximum Loads Node Repeaters Topologies Transmission Medium Terminating Resistor Physical Layer Data Encoding Link Layer Framing Link Layer Channel Collision Avoidance Application Protocol Network Nodes
Specifications
1 to 254 230.4 kbps 1 km per node 32 per node SensorNet J-boxes, distribution panels Daisy chain, backbone, or star Single Non-polarized unshielded twisted pair UTP 0.326mm (22AWG) 120, switch selectable RS-485, transformer-isolated, 2-wire FM-0 SDLC/HDLC Bi-directional, half duplex Polling by primary Touch Tracker Proprietary Domes, Junction Boxes, Secondary Touch Tracker, and SensorNet I/O Unit
2
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.
8200-2621-01, REV A
4 of 36
6. Attach network devices in stages. Check that their response is correct so you can correct the problem before continuing with the installation. 7. No more than 10 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. 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
Cable Type
Duplex RS-422
2 Twisted-Pair Shielded Belden 8102 / 88102 2 (0.205mm (24AWG) PVC / FEP 2 pair) or equivalent
Simplex RS-422
1 Twisted-Pair Shielded Belden 8102 / 88102 2 (0.205mm (24AWG) PVC / FEP 2 pair), Belden 8760 / 88760 2 (0.823mm (18AWG) PVC/FEP 1 pair) or equivalent 0.326 mm 22AWG) 1000m (3300ft) Polarized No 4.8 kbits/second 10 per line 99 Daisy Chain, Backbone
2(
Wire Gauge Max. Length Connection Termination Data Rate Max. Devices Max. Address Network Topologies
0.326 mm 22AWG) 1000m (3300ft) Polarized No 4.8 kbits/second 10 per line 99 Daisy Chain, Backbone
2(
8200-2621-01, REV A
5 of 36
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 -ofline. 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. 6. Attach network devices in stages. Check that their response is correct so you can correct the problem before continuing with the installation. 7. No more than 3 devices per cable segment. In 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. 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
Cable Type Wire Gauge Max. Length Connection Termination Data Rate Max. Devices Max. Address Network Topologies 0.823 mm 18AWG) 1500m (5000ft) Polarized Yes 31 kbits/second 3 per line 64 Daisy Chain, Backbone
2(
Description
1 Twisted Pair Shielded (Belden 8760 / 88760 or equivalent)
8200-2621-01, REV A
6 of 36
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
8200-2621-01, REV A
7 of 36
Figure 1. ADTT16E Star (Diagram 01)
DIA
ADTT16E Using a Star Topology

Sensornet cable T T #1
GR A
#1
30 meters (~100 feet)
#2
T #3 90 meters (~300 feet) Sensornet cable
T #4
Cable segments Sensornet cable 150 meters (~500 feet)
Cable segments
NOTE: The External Interface Module (EIM) is a passive circuit board required for interface to and considered part of the Touch Tracker.
EIM
#5 ADTT16E Touch Tracker

SENSORNET PROTOCOL KEY POINTS

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).
LEGEND T U Terminated Unterminated
8200-2621-01, REV A
8 of 36
Figure 2. ADTT16E Backbone / Daisy Chain (Diagram 02)
DIA
ADTT16E Using Backbone / Daisy Chain Topology

75 meters (~250 feet) U T #1 #2 U #3 U #4 U #5 Daisy Chain (Cut) 60 meters (~200 feet) 45 meters (~150 feet) 30 meters (~100 feet)
GR A
#2
Backbone (Uncut)

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 cable 150 meters (~500 feet) Cable segment
EIM
LEGEND #6 T ADTT16E Touch Tracker U Terminated Unterminated
8200-2621-01, REV A
9 of 36
Figure 3. ADTT16E to RJ6SN to Domes (Diagram 03)

Cable segments
ADTT16E to RJ6SN to Domes

60 meters (~200 feet) T
DI AG RA
#3
T #7
T #1
T #2
T #3
U #4
T #5
120 meters (~400 ft.)
#6
Balance connection ports with domes (don't limit loading to one side).
#8
RJ6SN J-BOX REPEATER

P4 P1 P5 P2
#9

P4 P1 P5 P2 P6 P3
Unterminate the dome or host when it is NOT at the end of the line P4-P6, P1-P3, or P8
P6 P3
DOME 456 JW2
321
HOST JW3
U U
U T
AUX
3 21
DOME 123 JW1
3 21
HOST
3 21
AUX JW4
Terminate the dome or host when it is at the end of the line P4-P6, P1-P3, or P8
DOME 456 JW2
321
HOST JW3
T T
HOST
T T
3 21
DOME 123 JW1 AUX JW4
3 21
3 21
AUX
P8 U 120 meters (~400 feet)

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).
P8 T
300 meters (~1000 ft.)

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).
T EIM#1
LEGEND #10 ADTT16E Touch Tracker T U Terminated Unterminated
8200-2621-01, REV A
10 of 36
Figure 4. ADTT16E to ADACSNETD to Domes (Diagram 04)
DIA
ADTT16E to ADACSNETD to Domes

Cable segments
GR A
#4
#1
#2 Cable segments
T ADACSNETD
T #3
T
HOST A
REPEATER

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).
T EIM
#4 T ADTT16E Touch Tracker U
LEGEND Terminated Unterminated
8200-2621-01, REV A
11 of 36
Figure 5. ADMP48PLUS to Domes (Diagram 05)
DIA
AD MegaPower 48 PLUS to Domes

GR A
#5
Backbone (Uncut)
Sensornet cable

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 #6 are terminated (key point #1). The Sensornet network cable length is 360 meter (~1200 feet).
Cable segment
#6
AD MegaPower 48 PLUS
NOTE: Although the MP48 PLUS has a REPEATER capability, this configuration does not utilize it.
LEGEND T Terminated U Unterminated
8200-2621-01, REV A
12 of 36
Figure 6. ADMP48PLUS to RJ6SN to Domes (Diagram 06)

Cable segments
DIA AD MegaPower 48 PLUS to RJ6SN to Domes GRA

#6
T #6
T #7
T #1
T #2
T #3
U #4
T #5
Balance connection ports with domes (don't limit loading to one side)
#8

P4 P1 P5 P2
#9

P4 P1 P5 P2 P6 P3
P6 P3
DOME 456 JW2
321
HOST JW3
U U
U T
AUX
3 21
DOME 123 JW1
DOME 456 JW2
321
T T
HOST
T T
3 21
3 21
HOST
3 21
AUX JW4
P8 T
HOST JW3
3 21
3 21
AUX
P8
Dome #1-2 and #3-5 cable segments are using the daisychain 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 3 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 3 repeaters (key point #2). Repeaters are used in this Sensornet configuration and each cable segment is less than 1km (~3300 feet).
T 300 meters (~1000 feet) #10 AD MegaPower 48 PLUS
REPEATER T LEGEND T Terminated U Unterminated T
8200-2621-01, REV A
13 of 36

Cable segments

APPLICATION NOTE 0026
#1
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 thru only 1 repeater ADACSNETD (key point #2). Repeaters are used in this Sensornet configuration and each cable segment is less than 1km (~3300 feet).
ADACSNETD
SENSORNET, RS-422, and MANCHESTER PROTOCOLS
#2
T
HOST A
LEGEND T #4 T
T Terminated U Unterminated
Figure 7. ADMP48PLUS to ADACSNETD to Domes (Diagram 07)
DI AG RA AD MegaPower 48 PLUS to ADACSNETD to Domes M
NOTE: Although the MP48 PLUS has a REPEATER capability, this configuration does not utilize it.
14 of 36
T REPEATER
#3
#7
8200-2621-01, REV A
Figure 8. ADMPLT to Domes (Diagram 08)
AD MegaPowerLT to Domes
DI AG RA
#8
T #17
U #18
U #19
U #20
U #21
T #1
U #2

Dome #1-2 and #17-21 cable segments are using the daisychain topology (key point #8). Domes #1, #2, and #17-21 are properly terminated (key point #1). Dome #1- 2 and #17-21 cable segments have less than 32 devices each (key point #6). No repeaters are used in this Sensornet configuration and each cable segment is less than 1km (~3300 feet).
AD MegaPower LT
CAM 17-32 CAM 1-16
#3 SNET B
NOTE: Each Sensornet port on the MPLT has it own driver which means port A does not talk to port B or vice versa.
SNET A
8200-2621-01, REV A
15 of 36
Figure 9. ADMPLT to RJ6SN to Domes (Diagram 09)
AD MegaPowerLT to RJ6SN to Domes

DIA
GR A
#9
T #17
T #18
T #19
U #20
T #21
T #1
T #16
Balance connection ports with domes (don't limit loading to one side)
#2

P4 P1 P5 P2
#3

P4 P1 P5 P2 P6 P3
P6 P3
DOME 456 JW2
321
HOST JW3
U U
U T
AUX
3 21
DOME 123 JW1
DOME 456 JW2
321
T T
HOST
T T
3 21
3 21
HOST
3 21
AUX JW4
P8 T
HOST JW3
3 21
3 21
AUX
P8
Dome #17-18 and #19-21 cable segments are using the daisy-chain topology (key point #8). Domes #1, #16, and #17-21 are properly terminated (key point #1). Dome #1, #16, #17-18, and #19-21 cable segments have less than 32 devices each (key points #6). Between any two devices, such as device #1 and #16 or #17 and #19, the signal passes thru only 1 repeater RJ6SN (key point #2) Repeaters are used in this Sensornet configuration and each cable segment is less than 1km (~3300 feet).
T LEGEND T Terminated
U Unterminated
AD MegaPower LT
CAM 17-32 CAM 1-16
#4 SNET B
Note: each Sensornet port on the MPLT has it own driver which means port A does not talk to port B or vice versa.
SNET A
8200-2621-01, REV A
16 of 36

T #17
APPLICATION NOTE 0026
#3
#18
ADACSNETD
HOST A
Dome #17-18 and #19-21 cable segments are using the daisy-chain topology (key point #8). Domes #1, #2, and #17-21 are properly terminated (key point #1). Dome #1, #2, #17-18, and #19-21 cable segments have less than 32 devices each (key point #6). Between any two devices, such as device #1 and #2 or #17 and #19, the signal passes through only 1 repeater ADACSNETD (key point #2) Repeaters are used in this Sensornet configuration and each cable segment is less than 1km (~3300 feet).
#19
SENSORNET, RS-422, and MANCHESTER PROTOCOLS
#5 #20
CAM 17-32
REPEATER
SNET B
T T U
#21
Figure 10. ADMPLT to ADACSNETD to Domes (Diagram 10)
AD MegaPower LT
AD MegaPowerLT to ADACSNETD to Domes 30 meters (~100 feet)
Note: Each Sensornet port on the MPLT has it own driver which means port A does not talk to port B or vice versa.
17 of 36
#4 T LEGEND ADACSNETD Terminated Unterminated CAM 1-16
HOST A
#1
Cable segments
150 meter (~500 feet)
SNET A
T
#2
DI AG RA
T
REPEATER
#1 0
8200-2621-01, REV A
Figure 11. Intellex to ADACSNET to Domes (Diagram 11)
Intellex to ADACSNET to Domes

75 meters (~250 ft.) U T #1 #2 U #3 U #4 U #5 Daisy Chain (Cut) 60 meters (~200 ft.) 45 meters (~150 ft.) 30 meters (~100 ft)
DIA
GR A
#1
Backbone (Uncut)
150 meters (~500 ft.)
INTELLEX REAR VIEW
USB PORT
#6 T

This is a backbone / daisy chain topology 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).
LEGEND T U Terminated ADACSNET Unterminated
8200-2621-01, REV A
18 of 36
Figure 12. Intellex to ADACSNET to RJ6SN to Domes (Diagram 12)
Cable segments
Intellex to ADACSNET to RJ6SN to Domes

60 meters (~200 feet) T
DIA
GR A
#1
T #1
T #2
T #3
U #4
T #5
#6
#7
Balance connection ports with domes (don't limit loading to one side).
#8

P4 P1 P5 P2
#9

P4 P1 P5 P2 P6 P3
Unterminate the dome or host when it is NOT at the end of the line P4-P6, P1-P3, or P8.
P6 P3
DOME 456 JW2
321
HOST JW3
U U
U T
AUX
3 21
DOME 123 JW1
3 21
HOST
3 21
AUX JW4
Terminate the dome or host when it is at the end of the line P4-P6, P1-P3, or P8.
DOME 456 JW2
321
HOST JW3
T T
HOST
T T
3 21
3 21
3 21
AUX
P8
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).
P8 T

Dome #1-2 and #3-5 cable segments are using the daisychain 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).
INTELLEX REAR VIEW
USB PORT
#10
T LEGEND T Terminated
ADACSNET
U Unterminated
8200-2621-01, REV A
19 of 36
Figure 13. Intellex to ADACSNET to ADACSNETD to Domes (Diagram 13)
DIA
Intellex to ADACSNET to ADACSNETD to Domes

T #1 T #2 Cable segments
GR A
#1
T ADACSNETD
#3
REPEATER
HOST A

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).
INTELLEX REAR VIEW
USB PORT
#4 T T U ADACSNET LEGEND Terminated Unterminated
8200-2621-01, REV A
20 of 36
Figure 14. ADMPCPU to Domes (Diagram 14)
ADMPCPU to Domes
DIA
GR A
#1
Backbone (Uncut)

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 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). The Sensornet network cable length is 360 meters (~1200 feet).
Cable segment
Sensornet cable 150 meters (~500 feet)

Default Configuration: Sensornet port 2 (dome addresses 255-508) Sensornet port 1 (dome addresses 001-254)
LEGEND T
2 4
17
3
DATA L INE
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
10
11
12
13
14
15
16
AD MegaPower CPU
8200-2621-01, REV A
21 of 36
Figure 15. ADMPCPU to RJ6SN to Domes (Diagram 15)
ADMPCPU to RJ6SN to Domes

#1 #2 T RJ6SN T
REPEATER
DI AG RA
#6 RJ1SNUD T
REPEATER
#1
#3
T #5 RJ6SN
REPEATER
#8
P4 P1 P5 P2 P6 P3
#4
U U
P4 P1 P5 P2 P6 P3
#7
P1
T U
host
aux
host
aux
T 120 meters (~400 feet)
T T 120 meters (~400 feet)
host
aux
#255 #256 #257
T RJ6SN T T
REPEATER
#258 #259 RJ1SNUD

REPEATER
#261
P4 P1 P5 P2 P6 P3
T T
P1
U U
#260
host aux

host
aux
T T 240 meters (~800 feet)
LEGEND T T Terminated U Unterminated

29 30 31 32
17
3
DATA L INE
18
19
20
21
22
23
24
25
26
27
28
10
11
12
13
14
15
16
AD MegaPower CPU
22 of 36
Figure 16. ADMPCPU to ADACSNETD to Domes (Diagram 16)
DIA
ADMPCPU to ADACSNETD to Domes

T #16 U #2 U #1 T #17 U #18 U #19
GR A
#1
Cable segments
T ADACSNETDP
T
HOST A
REPEATER
T
2 4
17
3
DATA L INE
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
10
11
12
13
14
15
16
AD MegaPower CPU
23 of 36
Figure 17. Redundant ADMPCPUs to RJ6SN to Domes (Diagram 17)
Redundant ADMPCPUs to RJ6SN to Domes

#1 T RJ6SN #2 T
REPEATER
DI AG RA
T
#3
#5 RJ6SN
REPEATER
#1
#6 RJ1SNUD
REPEATER
#8
P4 P1 P5 P2 P6 P3
T #4
U U
P4 P1 P5 P2 P6 P3
#7
P1
T U
host
aux
host
aux
host
aux
#255 #256 #257 LEGEND T Terminated U Unterminated
T RJ6SN T T
REPEATER
#258 #259 RJ1SNUD

REPEATER
T #261
P4 P1 P5 P2 P6 P3
T T
P1
U U
#260 T 240 meters (~800 feet)

Default Configuration: Sensornet port 2 (dome addresses 255-508)
host aux
host
aux
U U
17
3
DATA LINE
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
10
11
12
13
14
15
16
AD MegaPower CPU1
T U
17
3
DATA LINE
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
10
11
12
13
14
15
16
AD MegaPower CPU2 T
Default Configuration: Sensornet port 1 (dome addresses 001-254)
8200-2621-01, REV A
24 of 36
Figure 18. Redundant ADMPCPUs to ADACSNETD to Domes (Diagram 18)
Redundant ADMPCPUs to ADACSNETD to Domes

75 meters (~250 feet) U T #1 #2 60 meters (~200 feet) U #3 200 meters (650 feet) ADACSNETD T
DIA
GR A
#1
REPEATER
75 meters (~250 feet) T #255
U #256
60 meters (~200 feet) U #257

HOST A
HOST B
T 200 meters (~650 feet) T ADACSNETD T
REPEATER
HOST A
HOST B
T T
AD MegaPower CPU1
2 4
17
3
DATA LINE
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
10
11
12
13
14
15
16
T AD MegaPower CPU2
2 4
50 meters (~160 feet) LEGEND
17
3
DATA LINE
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
10
11
12
13
14
15
16
8200-2621-01, REV A
25 of 36
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
8200-2621-01, REV A
26 of 36
Figure 19. Intellex to ADAC485CV232 (Diagram 22)
INTELLEX Dome Control Via RS-232 to Converter (ADAC485CV232)
DI AG RA RS-422
#2 2
INTELLEX
Dome I/O P1 Pin 1: Rx+ Pin 2: RxPin 3: Tx+ Pin 4: Tx-
ADAC485CV232 Tx+ TxRx+ Rx-
SpeedDome Ultra
ADACUSBCVT1 (USB to RS-232 Adapter) Pin 2: RX Pin 3: TX Pin 5: GND DB9F
DB9M
DB9M to DB9F Straight Serial Cable
12 VDC
ADAC485CV232 (RS232 to RS-422 Converter) Pin 2: TX Pin 3: RX Pin 5: GND

8200-2621-01, REV A
27 of 36
Figure 20. ADMPLT to RCSN422 to Domes (Diagram 23)
ADMPLT to RCSN422 Via RS-422 to Domes

AD MegaPower LT
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.
DIA
GR A
#2
DOME 17-32
DOME 1-16
Sensornet Port A Sensornet Port B
ADCC200/300 KEYBOARD
RCSN422
Ultra I/O Board P1 #1

R+R-T+T-
RS422
RS422
RS422
RS422
RS422
RS422
RS422 sensornet termination switch address sw power switch
tx lo tx hi rx lo rx hi
123456
REAR VIEW
24 vac gnd 24vac
RS-422
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.
8200-2621-01, REV A
28 of 36
Figure 21. ADMPLT to RCSN422 to RJ860 to Domes (Diagram 24)
D ADMPLT to RCSN422 to RJ860 to Domes IAG DOME 17-32 DOME 1-16 RA
#2
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.
Sensornet Port B
ADCC200/300 KEYBOARD
REAR VIEW
RS422 RS422 RS422 RS422 sensornet termination switch address sw power switch
RS422
RS422
RS422
RCSN422
RS-422
J6 J7 J8 J9 J10
12 11 10 9 8 7 6 5 4 3 2 1
tx hi tx lo
SEE TABLES BELOW
rx hi rx lo
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+)
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+)
J1 J2 J3 J4 J5 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.
RJ860AP J-BOX
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 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+)
29 of 36
24 vac gnd 24vac
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+)
8200-2621-01, REV A
Figure 22. ADMP48PLUS RS-422 to Domes (Diagram 25)
ADMP48PLUS RS-422 to Domes

R+R-T+T-
DI AG RA
#2 5
123456
MegaPower 48 PLUS
R+ R- T+ T- R+ R- T+ T-
RS-422
8200-2621-01, REV A
30 of 36
Figure 23. ADMP48PLUS RS-422 to RJ-860 to Domes (Diagram 26)
DIA
ADMP48PLUS RS-422 to RJ-860 to Domes

R+R-T+T-
GR A
#2
123456
Dome P1 RJ-860 Cinch Jones Pin 1~Rx+ Pin 1~Tx+ Pin 2~Rx- Pin 2~TxPin 3~Tx+ Pin 8~Rx+ Pin 4~Tx- Pin 7~Rx-
Cinch Jones
10 Pos. J-Box ( RJ 860 AP )
12 11 10 9 8 7 6 5 4 3 2 1
Rx+ RxTx+ Tx-
MegaPower 48 PLUS
MP48PLUS Rx+ RxTx+ Tx-
RJ-860 Host Pin 6~Tx+ Pin 5~TxPin 12~Rx+ Pin 11~Rx-
R+ R- T+ T- R+ R- T+ T-
8200-2621-01, REV A
31 of 36
Figure 24. ADMPCPU to AD2083-02C RS-422 to Domes (Diagram 27)
ADMPCPU to AD2083-02C RS-422 to Domes

R+R-T+T-
DIA
GR A
#2

R+R-T+T-

R+R-T+T-
123456
123456
123456
Daisy Chain (Cut)
Backbone (Uncut)
AD2083-02C
Terminated with 75 ohms
17
3
DATA L INE
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
10
11
12
13
14
15
16
AD MegaPower CPU
8200-2621-01, REV A
32 of 36
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
8200-2621-01, REV A
33 of 36
Figure 25. ADMP48PLUS Manchester to Domes (Diagram 19)
ADMP48PLUS Manchester to Domes

BW
DI AG RA
#1
MANCHESTER PROTOCOL KEY POINTS

Daisy Chain (Cut)
123456
Backbone (Uncut)

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

BW
123456
MegaPower 48 PLUS
#4
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.
MAN
LEGEND
B W S
T U
Terminated Unterminated
8200-2621-01, REV A
34 of 36
Figure 26. ADMP48PLUS Manchester to ADACSNETD to Domes (Diagram 20)
AD MegaPower 48 PLUS Manchester to ADACSNET to Domes

BW
DI AG RA
#2

BW
LEGEND 123456 T T U Terminated Unterminated
123456
75 meters (~250 feet) 90 meters (~300 feet) T ADACSNETD T
REPEATER
HOST A
300 meter (1000 feet)
MegaPower 48 PLUS
MAN
B W S
8200-2621-01, REV A
35 of 36
Figure 27. ADMPCPU to AD0291 Manchester to Domes (Diagram 21)
ADMPCPU to AD2091 Manchester to Domes

BW
DI AG RA
#2

BW
123456
123456
AD2091
17
3
DATA L INE
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
10
11
12
13
14
15
16
AD MegaPower CPU
8200-2621-01, REV A
36 of 36

Manual Jbox

Uploaded by

Copyright:

Available Formats

Manual Jbox

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Manual Jbox

Uploaded by

Copyright:

Available Formats

APPLICATION NOTE

SensorNet, RS-422, and Manchester Protocols Application Note

2010 Sensormatic Electronics, LLC

SensorNet Protocol Key Points

SENSORNET, RS-422, and MANCHESTER PROTOCOLS APPLICATION NOTE 0026

Advantages of SensorNet Protocol

SENSORNET, RS-422, and MANCHESTER PROTOCOLS APPLICATION NOTE 0026

SensorNet Protocol Specifications Item

II. RS-422 Protocol

RS-422 Protocol Key Points

SENSORNET, RS-422, and MANCHESTER PROTOCOLS APPLICATION NOTE 0026

RS-422 Protocol Specifications

SENSORNET, RS-422, and MANCHESTER PROTOCOLS APPLICATION NOTE 0026

III. Manchester Protocol

Manchester Protocol Key Points

Manchester Protocol Specifications

SENSORNET, RS-422, and MANCHESTER PROTOCOLS APPLICATION NOTE 0026

Appendix A: Typical SensorNet Connections

SENSORNET, RS-422, and MANCHESTER PROTOCOLS APPLICATION NOTE 0026

Figure 1. ADTT16E Star (Diagram 01)

ADTT16E Using a Star Topology

30 meters (~100 feet)

75 meters (~250 feet)

T #3 90 meters (~300 feet) Sensornet cable

Cable segments Sensornet cable 150 meters (~500 feet)

#5 ADTT16E Touch Tracker

SENSORNET PROTOCOL KEY POINTS

LEGEND T U Terminated Unterminated

SENSORNET, RS-422, and MANCHESTER PROTOCOLS APPLICATION NOTE 0026

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

ADTT16E Using Backbone / Daisy Chain Topology

SENSORNET PROTOCOL KEY POINTS

Sensornet cable 150 meters (~500 feet) Cable segment

LEGEND #6 T ADTT16E Touch Tracker U Terminated Unterminated

SENSORNET, RS-422, and MANCHESTER PROTOCOLS APPLICATION NOTE 0026

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

ADTT16E to RJ6SN to Domes

90 meters (~300 feet)

150 meters (~500 feet)

150 meters (~500 feet)

75 meters (~250 feet)

RJ6SN J-BOX REPEATER

RJ6SN J-BOX REPEATER

DOME 123 JW1

DOME 456 JW2

DOME 123 JW1 AUX JW4

P8 U 120 meters (~400 feet)

300 meters (~1000 ft.)

SENSORNET PROTOCOL KEY POINTS

LEGEND #10 ADTT16E Touch Tracker T U Terminated Unterminated

SENSORNET, RS-422, and MANCHESTER PROTOCOLS APPLICATION NOTE 0026

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

ADTT16E to ADACSNETD to Domes

75 meters (~250 feet)

90 meters (~300 feet)

90 meters (~300 feet)

SENSORNET PROTOCOL KEY POINTS

#4 T ADTT16E Touch Tracker U

LEGEND Terminated Unterminated

SENSORNET, RS-422, and MANCHESTER PROTOCOLS APPLICATION NOTE 0026