44185_-_ATI_ACB.pdf

Acoustic Technology, Inc April 16, 2010

ATI Advanced Communication Board

(PN 44185)

The AdvancedCB connects to an ATI siren or CCU over RS485 or RS232 and provides a variety of additional interfaces:

IP interface over Ethernet (adaptors to WiFi, Fiber, Mesh Radio, Microwave, etc)

MP3 chip & SD flash socket provide drop in replacement for existing Digital

Message Board with enhanced quality. Voice messages can be updated remotely if IP connection available.

FSK modem, DTMF and Two Tone sequential over radio or phone line

Microphone preamp for local PA

Flexible IO including interface for Door Control Panel

Same size board as existing CB and DMB

Flexibility in power options – from “host” board or use on-board regulators

RCM4xxx Module

USB

Chip

Telephone

Interface

(2 or 4 wire)

Radio

Interface

SP_B

FSK Modem

DTMF generate

& detect tone generate & detect

Analog

Audio

Output

CPLD

I/O

RS485 to main board

Radio

Telephone line

Optional Ethernet or WiFi

RS232

port

SP_D SP_C

SP_F

IO_Bus

USB port

MP3

chip

SD Flash socket

Onboard voltage regulators

Microphone preamp

GP IO

DMB

Interface

16 15 6, 7

1, 2

8, 9

A/D

SP_E

Door Control

Panel

ACB Block Diagram

1 - Phone

LEDs

2 – Phone

Jack P5

3 – RS232

P3

4- Reset &

DIP switches

5 - Rabbit CPU module (shown with Ethernet)

6 – MiniSD socket P6

(underneath)

7 -SD_Active

LED

8 – Aux power

J11

10 – DCP

I/F J6

11 –

RS485 J1

12 -RS485

TX LED

13- FirmWare

LEDs

14- Altera prog port J9

145 – DMB I/F

J5 (note pin order)

16 – GPIO

J10 17 – Mic input J7

18– USB

type B P4

19 - Radio

I/F J3 +

LEDs

ATI Advanced Communication Board Physical Layout Guide

20 – FSK,

tone chips

9 – power status LEDS

1) Phone LEDs

/Hook – when lit, indicates connection to phone line

PTT_P – when lit, indicates ACB is transmitting on phone line

2) Analog telephone interface (RJ11, P5) ring detect, hook switch, Loop Current detection

600 ohm interface, 2 wire or 4 wire selected by JP1

Max transmit level = 0 dBm (2.2 v PP)

3) RS232 Interface (DB9 connector, P3)

Includes full set of modem control signals

Connected to serial port F of Rabbit Module

4) Switches

PB1 is momentary push button for reset of ACB and Rabbit module

SW1 is 8 position DIP switch readable by Rabbit (FW dependant), but typical function:

o Position (4-1) – RS485 address - first ACB typically set to 0001 o Position (6-5) – undefined o Position (7) – 1 force IP address to 10.123.124.125, 0 – use loaded IP addr o Position (8) – 1- attached to CCU, 0 – attached to siren

5) Rabbit RCM4000 series Module

10 x faster than Rabbit 2000 typically 512K Flash, 512K SRAM many pin compatible modules with different external interfaces allow flexibility

J1 in upper left corner of module is Rabbit programming port (.05 in pin spacing)

6) miniSD Flash socket + MP3 chip

Provides digital messages on miniSD flash – better sound, many hours

Potential for remote update of messages without site visit

Note some Rabbit modules include their own miniSD socket but we will typically use the socket on the ACB

7) SD Active LED

Indicates SD Flash is active

8) Aux Power connector (2 pin 5.08 phoenix type, J11)

Power is typically supplied by RS485 cable or DMB cable and J11 is unused

However for longer runs +12v or +24v can be supplied to J11 with other voltages generated onboard by adding regulator modules U34, U36 as needed

9) Power Status LEDs 3 LEDs indicate status of +12v, +5v and +3.3 volts. Ordinarily, these should always be on.

10) Door Control Panel Interface (6 pin 3.81 phoenix, J6) provides 12v, 5v, 3.3v and GND connections (500 ma max)

TTL level serial port E for auxiliary devices such as LCD.

11) RS485 Connector (5 x 2 header .1”, J1)

ATI standard: Power + RS485 bus + Audio IO

12) RS485 Tx LED

“ON” indicates the ACB RS485 port is transmitting

13) Firmware LEDs

4 LEDs controlled by firmware on Rabbit module. Application dependant.

14) Altera Programming Port (5 x 2 header .1”, J9)

Use Altera ByteBlaster or USBBlaster to configure CPLD

15) DMB Interface (10 x 2 header .1”, J5)

Mimics existing DMB (except pin ordering is correct)

Note: new cable required – use straight through (aux amp) cable, not old DMB cable which has pins reversed

16) General Purpose IO (5 x 2 header .1”, J10)

Header provides IO which includes 4 digital IO, 4 A/D inputs

17) Microphone Pre-Amp (4 pin header .1”, J7)

Jumper JP2 selects gain for normal or noise canceling microphone

JP2.1 is digital input for use as microphone PTT

18) USB Interface (Standard USB Type B connector, P4)

Endpoint device only

RS232 emulation mode provides raw data stream to Rabbit. Driver appears as com port on PC providing easy migration path for our software.

Can NOT plug in random USB devices such as memory sticks and have

AdvancedCB act as hub

19) Radio Interface (10 x 1 Phoenix style 3.81 connector, J3)

Analog xmit/rcv, PTT, SQ control lines – similar to existing ATI boards

20) FSK/Tone section

FSK modem (Bell 202 or V23) 300/1200 bps

DTMF digits generation/detection

Two tone sequential generation/detection nd tone gen chip, extra audio gates to support dual sinewave audio tones

Shared by phone and radio interfaces so generally only one may be active at a time

Power required from main board:

200 milliamp @ 4.75-5.25 volt (not including optional control panel or modem)

20 milliamp @12V

Initial Debug sequence

Check that all 3 power LEDs are on. If not, inspect cable connections, check power supplies.

Press reset PB1, firmware LEDs should go off and come back on. If Ethernet connected, LEDs on Rabbit module should come on. If no activity, maybe you need to load firmware. (Rev level of firmware can be read over Remote Utility if you’re unsure what’s on a specific ACB)

Most of the functions and ports of the ACB need to be properly configured using the

Remote Utility and the proper files before they will turn on. Assuming desired ports and functions have been enabled:

If ACB is connected to RTU or Soundblaster, check RS485 Tx LED is blinking.

Current RS485 protocol exchanges packet roughly once/second. If no activity:

o Check cable o Check SW(4-1) is set to desired RS485 address (typically 0001) o Check ACB configuration o Check Soundblaster/RTU firmware is correct o Check ACB Firmware is correct

Observe port LEDs – generate packet from host board (press reset on

Soundblaster or do poll from CCU) o If ethernet path enabled, check that Yellow Ethernet LED blinks o If radio connected to ACB (as opposed to main board), observe PTT_R and SQ change appropriately o If using hardwired FSK, /HOOK should always be on and PTT_P should go on momentarily when a packet is sent