LATIN-081206-1-0-A (Revised)

LL..AA..TT.. II ..NN.. LLaattiinn AAmmeerriiccaa TTeecchhnniiccaall IInnffoorrmmaattiioonn NNootteess

LATIN: 081206-1-0-A

Issue Date: 11 May 2009 Expiration Date: 11 June 2010

To: Latin America & Caribbean Countries Region Authorized Distribution Channel

From: LACR Indirect Subscriber Engineering Group Plantation, Florida, USA

Subject: MOTOTRBO COR Configuration for System Release 1.4

The information contained in this L.A.T.I.N. is for informational purposes only, for use by Motorola Authorized Distribution Partners under an active Distribution agreement for the product(s) and conditions specified below. This L.A.T.I.N. is intended for the exclusive use of the Entities to whom it is addressed. Any dissemination, distribution or copying is strictly prohibited. No warranty is implied or authorized.

Description: Motorola is pleased to announce the release of the MOTOTRBO Carrier on Receive (COR) configuration available in the 1.4 MOTOTRBO System Release. The COR functionality is only available after updateing a mobile radio’s firmware version to R01.04.01, or later. Special cabling is required which is not provided by Motorola. The MOTOTRBO COR feature is only used in the Digital operating mode.

Models:

All MOTOTRBO Mobile models with firmware R01.04.01, or later.

Pre-requisists:

1. Special cabling is required to configure the COR system. This cabling is not provided by Motorola. Interface nomenclature and pin connections are contained within this document.

2. Knowledge of GCAI MAP pin connections are required to prepare the

cable and configure a proper setup. Please refer to section “Mobile Accessory Port (MAP) Specifications” for details. See Figure 3.

3. Knowledge of configuring the GCAI MAP Pins (i.e. GPIO physical pins)

via the CPS is required.

4. Knowledge of configuring the I/O Pins (i.e. physical pins) on other radios (PRO Series, EM200, EM400) to be connected to the MOTOTRBO mobile, via the CPS.

R02.4


Signal Descriptions: External PTT (Pin #17) This is an input line used for voice transmission which can be configured via CPS. Refer to Figure 1. The purpose of this pin is to let 3rd party applications indicate to the MOTOTRBO mobile radio that there is a voice signal in the Tx Audio line (Pin# 11). The Ext PTT pin shall be activated by the 3rd Party application whenever it requires the MOTOTRBO mobile to transmit voice. There are two states for this pin, Active and Inactive. Active - If the pin is activated by a 3rd party application, the MOTOTRBO mobile shall process (i.e. transmit) voice signals in the Tx Audio line. The 3rd party application is expected to have voice signals on the Tx Audio line when it activates the Ext PTT pin. Inactive - If the pin is inactivated by a 3rd party application, the MOTOTRBO mobile stops processing the voice signal in the Tx Audio line. When a 3rd party application has no voice data to transmit through the MOTOTRBO radio, it shall set the Ext PTT pin to inactive state. Figure 1

Configuration to set the GPIO Physical Pins

R02.4


PL/Talkgroup Detect (Pin #21),for Analog radios it’s CSQ This is an output line used for permitting an output to be activated when the radio is receiving carrier and the radio’s Un-mute Rule has been satisfied. This pin shall be configured via CPS. Refer to Figure 1. The purpose of this pin is to let the MOTOTRBO Mobile radio inform the 3rd party application that there is voice data in the Rx Audio line (Pin #14). There are two states for this line, Active and In-active. Active - When the MOTOTRBO mobile radio sets this pin to Active, the radio shall place the voice data that it has received in the Rx Audio line. The 3rd party application shall process the voice data in the Rx Audio line. Inactive - When the MOTOTRBO mobile radio sets this pin to the inactive state, the mobile radio is giving an indication to the 3rd Party application that there is no voice data in the Rx Audio Line. Note: The MOTOTRBO mobile shall set the PL/Talkgroup Detect pin to inactive state if the Ext PTT pin is activated by a 3rd party application. Tx Audio (Pin #11) This is the TX audio input pin. The 3rd party application is expected to send voice signals to the MOTOTRBO radio through this pin so the radio can process the signal (for transmission). Rx Audio (Pin #14): This is the RX audio output pin. The MOTOTRBO mobile radio shall send the voice signals to the 3rd party application through this pin, whenever it receives valid audio signals. GROUND (Pins #16, #18) At least one of these pins shall be grounded.

Configuration:

PL / Talkgroup Detect was chosen for flexibility in applications that may have a radio that can operate on an analog or digital channel by a user selection or channel steering the programmable accessory pins.

R02.4


The functionality of PL/Talkgroup Detect was enhanced to support digital channels in SR1.4. In the analog mode this is typically a PL or DPL audio detect condition. In the following examples, to utilize the COR feature on a MOTOTRBO mobile radio operating in the digital mode or the analog mode, the PL/Talkgroup Detect (CSQ) and Ext. PTT programmable accessory functions must be enabled on the accessory pins via the CPS. See Figure 1 or Figure 2. In the following examples, to utilize the COR feature on a MOTOTRBO mobile radio, the menu selection for the “Cable Type” needs to be configured as “Rear PC & Audio”. See Figure 2. Cable: It’s recommended to use the Motorola cable, part number PMKN4018A, for MOTOTRBO mobile radios. For Analog to Digital or Cross band applications, only 5 wires on each radio's accessory connector will be used. Two Motorola cables, PMKN4018A, will be needed for this cross band application. The PMKN4018A cable contains a pre-wired accessory connector and tinned wires. This cable has pins 2 and 26 labeled on the plastic connector for Pin identification reference. The individual wires that are NOT used will need to have some sort of termination (head shrink) so they DO NOT short out and damage the radio. When connecting two MOTOTRBO radios, in a cross band configuration, it will require two PMKN4018A cables. The alternative to the above recommendation is to order the Motorola connector part number PMLN5072A. The customer would be required to crimp the interconnect pins to their own supplied wire and place the pins into the plastic housing.

Detailed Information:

The possible COR configurations are as follows:

Analog to Digital Application

Cross Band Application (VHF to UHF, UHF to VHF, etc.)

Vehicular Repeater Configuration for Extending Range at a Local Site

PC Dispatch Console Application VOIP Interface

R02.4


Analog to Digital Cross Band/Mode Application:

The follow example shows a possible configuration between two MOTOTRBO Mobiles in a Cross Band configuration.

Back to Back mobiles for Analog to Digital cross band application where cross band communications can be configured from a UHF to VHF channel or VHF to UHF or a MOTOTRBO Analog to Digital, or where one radio is an MOTOTRBO Analog Radio and the other is a MOTOTRBO Digital radio.

Analog to Digital Cross Band/Mode Application

RX Audio (Pin 14) TX Audio (Pin 11)

TX Audio (MAP Pin 11) RX Audio (MAP pin 14)

MOTOTRBO Mobile (Digital)

MOTOTRBO Mobile (Analog)

Ext. PTT (Pin 17) PL/Talkgroup Detect (Pin 21)

Ext. PTT (Pin 17)PL/Talkgroup Detect (Pin 21)

Ground (Pins 16,18)

MOTOTRBO Analog Mobile Radio or another Conventional Radio

using a different frequency band

MOTOTRBO

Digital Mobile Radio

R02.4


In the above example, the Ext. PTT is programmed for accessory pin 17 and PL/Talkgroup Detect is programmed for accessory pin 21 through the CPS. See Figure 1 or Figure 2.

A Vehicular Repeater Configuration/ Extending Range at a Local Site

This configuration would use the cross band application in order to achieve greater portable radio coverage when a strategically located mobile is within range of the systems repeater but the local portable radios are not. This could be utilized in Construction site communications and Search and Rescue applications.

Figure 2

R02.4


Possible Third Party Accessory Interfaces:

The follow example shows a possible configuration between a MOTOTRBO Mobile and a 3rd Party PC, to be configured as a PC dispatch console

PC Dispatch Console

Application Support

MOTOTRBO

Digital Mobile Radio

Notes:

• Audio Cards could use audio detection Algorithms instead of receive signal indications.

• Other pins may be dictated by specific applications.

R02.4


The follow example shows a possible configuration between a MOTOTRBO Mobile and a 3rd Party VOIP device, to be configured as a VOIP interface device.

3rd Party VOIP Interface

MOTOTRBO

Digital Mobile Radio Notes:

• The third party VOIP interface box could use audio detection algorithms instead of the receive indication.

• Other pins may be dictated by specific applications.

R02.4


MOTOTRBO Mobile Accessory Port (MAP) Specifications In all possible configurations, the physical connections to the MOTOTRBO mobile radio are through the GCAI MAP pins (Refer to Figure 3 for details of the pins). We utilize the following pins to achieve COR functionality.

• Ext PTT pin (Pin #17) • PL/Talkgroup Detect pin (Pin #21) • Tx Audio (Pin #11) • Rx Audio (Pin #14) • The ground pins (Pin#16,18) shall be grounded.

Figure 3

Spkr

-

GP5

_1 (P

TT)

Tx A

udio

Gro

und

Emer

g Sw

Rx

Aud

io

SW B

+

Aud

io G

roun

d

Gro

und

GP5

_2 (M

onito

r)

Spkr

+

GP5

_8

GP5

_7

Ign

Sens

e

GP5

_3 (C

han

Act

)

VIP_

1 (E

xt A

larm

)

GP5

_6

D+

D-

USB

/ A

PM G

roun

dVb

us

APM

1 (1

-wire

)

Aux

Aud

io O

ut 1

/ R

xD

Aux

Aud

io O

ut 2

/ Tx

D

Pow

er G

roun

d

2 6

2 1

2 2

2 3

2 4

2 51 131 1 395 7 1 91 5 1 7

1 41 0 1 22 4 86 2 01 6 1 8

APM

2 (1

-wire

)

These are the MAP pin-outs as viewed from the rear of the radio. In general, no connections should be made to pins 1-6 as these are for USB communications and Smart Accessory detection. The remaining pins are labeled accordingly.

R02.4


Digital COR Limitations:

• In any cross band application calls could be missed on the digital channel if other users with different talk groups are using the digital channel.

• Calls could be missed on the analog channel if PL/Talkgroup Detect is used and the radio is currently receiving another users PL/talkgroup.

• Two radios are needed for each talkgroup supported.

• Scan can be used but the receiving radios may experience inherient longer unmute times and possibly missing words at the beginning of a transmission due to the culmination of scan delay times.

Additional Digital COR Considerations:

• Transmit inhibit on Busy should be enabled on analog channels to prevent mixing of audio on the analog RF frequency.

• The Digital COR signal shares the functionality of the PL/Talkgroup Detect programmable accessory output.

• The digital admit criteria on a digital mobile radio used in these applications should be configured for “Channel Free” (Polite to All) to avoid interfering with another call in progress.

• Special cabling is required which is not available from Motorola. This cabling is expected to be prepared by the 3rd party application developers.

• Any cabling should be properly shielded to prevent unnecessary audio distortion.

• Proper RF frequency separation should be considered in any application using COR between two radios. This is either physical separation of antenna cables or RF frequency separation.

R02.4


Configuration Example: EM200 UHF Analog Mobile to MOTOTRBO UHF Digital Application:

The follow example shows the wiring configuration between an EM200 UHF analog mobile radio, a MOTOTRBO UHF digital mobile radio, and the accessory codeplug configuration of both mobiles.

Back to Back mobiles for an Analog to Digital application, where cross platform communications can be configured from a Analog mobile to a Digital mobile, but in this example, one radio is a EM200 UHF Analog Radio and the other is a MOTOTRBO UHF Digital radio.

Note: The radios frequency bands do NOT have to be the same.

This is just a functional example. Specific COR applications and

configurations may be different under other COR scenerios.

Cable Wiring Configuration:

EM200 Analog MOTOTRBO Digital

RX Audio - Pin 11 TX Audio - Pin 11

TX Audio - Pin 2 RX Audio - Pin 14

Ground - Pin 7 Ground - Pins 16, 18

Ext. PTT - Pin 3 PL TalkGroup detect - Pin 21

CSQ Detect - Pin 8 Ext. PTT - Pin 17

Important Porgramming Parameters: EM200 Mobile Codeplug Configuration:

Accessory I/O Programming:

The Accessory Package is configured for Phone Patch or I750R

Each package assigns a related group of default settings to the fully programmable pins of the Accessory Connector. Once an Accessory Package has been assigned, individual pin settings may be modified. There are three categories for the 16 Accessory Connector pins: Fully Programmable, Partially Programmable, and Fixed - Not Programmable.

R02.4


Accessory Pin #3: Configured for External Mic PTT with an active LOW signal level.

Accessory Pin #8: Configured for PL/CSQ/Talkgroup Detect with an active LOW signal level.

R02.4


MOTOTRBO Codeplug Configuration:

Accessory I/O Programming:

The Cable Type is configured for Rear PC & Audio

Accessory Pin #17: Configured for External Mic PTT with an active LOW signal level.

Accessory Pin #21: Configured for PL/CSQ/Talkgroup Detect with an active LOW signal level.

R02.4


R02.4

This L.A.T.I.N. is for informational purposes only. No warranty is implied or authorized.

If you have any questions concerning this LATIN, please use the “Contact Us” feature on the MOL website at https://www.motorola.com/businessonline.

https://www.motorola.com/businessonline

LATIN-081206-1-0-A (Revised)

Documents

Transcript of LATIN-081206-1-0-A (Revised)