Automated Logic S6104 Technical Instructions Download Page 5

Revised 7/30/02 • S6104

5

© 2002 Automated Logic Corporation

Using the S6104 on an ARC156 
Segment

When communicating at 156 kbps, the 
network segment uses a unique 
implementation of the industry standard 
BACnet-over-ARCNET protocol called 
ARC156. For a summary of the differences 
between ARCNET and ARC156, please refer to 

ARC156 CMnet Wiring Technical Instructions

.

Use the appropriate wire for network 
communications. When using an ARC156 
network, use an A3ARC156 wire available 
from:

Magnum Cable Corporation
Cleveland, OH 44110-0500
(800) 421-0820

When the CMnet Select jumper is set to 
ARC156, the CMnet port is connected to an 
ARCNET processor, enabling the S6104 to 
communicate on an ARC156 network 
segment. Communication speed is 156 kbps 
regardless of the Baud Select jumper setting 
(see Table 1). 

Using the S6104 on a Legacy CMnet

Use a dedicated 22AWG to 18AWG twisted 
pair wire for legacy CMnet (EIA-485) wiring. 
For more information about CMnet wiring, 
refer to the 

Technical Handbook

.

When the CMnet Select jumper is set to 
Legacy, the module communicates on a 
legacy CMnet at the baud rate set by the Baud 
Select jumper (see Table 1). The Port Select 
jumper must also be set to Access.

NOTE

Setting the CMnet jumper to Legacy 

disables the industry standard BACnet-over-
ARCNET (ARC156) protocol for the network 
segment and enables the proprietary ALC 
CMnet protocol.

Connecting the S6104 to the 
Network

Before connecting the S6104 to the CMnet, be 
sure the S6104’s power is off.

1. Set the CMnet mode (ARC156 or legacy 

CMnet) using the CMnet Select jumper. 

2. If communicating on a legacy CMnet, set 

the Baud Select jumper for either 9600 bps 
or 38.4 kbps.

NOTE

All modules on the CMnet must 

use the same baud rate.

3. Set the Port Select jumper:

• On a legacy CMnet, set the Port Select 

jumper for Access. 

• On an ARC156 CMnet on a WebcTRL 

system, set the Port Select jumper for 
LogiStat.

• On an ARC156 CMnet on a 

SuperVision system, set the Port 
Select jumper for either Access or 
LogiStat depending on which port will 
be used for serial communications 
(see “Communicating with the 
Workstation Using SuperVision” on 
page 6
).

4. Check the network communication wiring 

for shorts and grounds.

5. Connect the CMnet wires to the module’s 

screw terminals as shown in Figure 3 on 
page 6
. Be sure to follow the same 
polarity as the rest of the CMnet.

 

Table 1. Jumper positions

CMnet 
Type

CMnet Select Port Select Baud Select

ARC156

ARC156

Access or 
LogiStat

Not 
Applicable

Legacy 
CMnet

Legacy Access

9600 bps or 
38.4 kbps

Summary of Contents for S6104

Page 1: ...ounting 3 Addressing 3 Power Wiring 4 Network Communications 4 Using the S6104 on an ARC156 Segment 5 Using the S6104 on a Legacy CMnet 5 Connecting the S6104 to the Network 5 Communicating with the W...

Page 2: ...log outputs A single board provides the power circuitry microprocessor and non volatile memory stores data even during a power failure The Access Port allows communication with WebCTRL or SuperVision...

Page 3: ...Outputs 6 digital outputs Form A 3A max Analog Outputs 4 analog outputs 0 to 10VDC 20mA source capability Output resolution 8 bit D A Communication For WebCTRL 156 kbps BACnet over ARCNET and 9600 bp...

Page 4: ...he S6104 has an operating range of 21 6VAC to 26 4VAC If voltage measured at the module s power input terminals is outside this range the module may not work properly 1 Turn the module s power off Thi...

Page 5: ...lect jumper must also be set to Access NOTE Setting the CMnet jumper to Legacy disables the industry standard BACnet over ARCNET ARC156 protocol for the network segment and enables the proprietary ALC...

Page 6: ...ommunication speed is fixed at 1200 baud 1 Connect the computer s serial port to the EIA 232 port of the APT using a standard straight through cable 2 Set the APT s Mode Select switch to TTL see Figur...

Page 7: ...rt when finished to allow the S6104 to receive inputs from the LogiStat Communicating Through the Access Port Using SuperVision When using SuperVision you can connect a workstation or portable compute...

Page 8: ...ource to power the 4 20mA transducer The B terminal is capable of supplying 18 to 24VDC but the total current of all B terminals must not exceed 200mA If the voltage measured from the B terminal to Gn...

Page 9: ...e of sensor used Make sure the jumper is positioned correctly and be sure to grip the jumper by the sides only See Figure 10 Figure 8 Input Wiring 15 16 17 18 20 19 14 13 12 11 10 9 8 7 6 5 4 3 2 1 IN...

Page 10: ...pin 2 Temp of the LogiStat Port The LogiStat Plus also provides the slidepot position and TLO inputs through pin 3 Sw The LogiStat Pro provides temperature setpoint adjust and TLO inputs through seria...

Page 11: ...mode by setting the HOA switches see Figure 1 on page 2 for the switches location Table 5 on page 12 shows the status of the digital output based on the output s configuration and the HOA switch posit...

Page 12: ...put s operation lock the output to a known condition using the Function Block s Properties page in WebCTRL or Parameter page in SuperVision Be sure the equipment operates as specified Writing GFBs for...

Page 13: ...pend on the type of sensor or actuator attached to the I O point You can select the channel number offset and gain using SuperVision s Point Help feature or Configure Points utility Alternatively you...

Page 14: ...ute Download button If any downloads failed they are listed in the Failures section under the tree in the UI 2 Thermistor 32 17 to 213 F 27 to 100 6 C 0 00 0 00 15 88 15 69 mA or Volts 32 0 to 20mA 0...

Page 15: ...SC key type MO module address 15 and press Enter 3 Transfer memory to the module In SuperVision v3 0 click Tools Troubleshooting Transfer Memory to Module In SuperVision v2 6b download memory for This...

Page 16: ...imal Figure 17 S6104 LED locations Table 9 LED Signals Run LED Error LED Condition 2 flashes per second Off Normal 2 flashes per second 1 flash then pause Normal but module is alone on the CMnet this...

Reviews: