Linx Technologies MDEV-xxx-TT User Manual

TT Series

Master Development System

User's Guide

Warning: Some customers may want Linx radio frequency (“RF”)

!

products to control machinery or devices remotely, including machinery
or devices that can cause death, bodily injuries, and/or property
damage if improperly or inadvertently triggered, particularly in industrial
settings or other applications implicating life-safety concerns (“Life and
Property Safety Situations”).

Table of Contents

1 Introduction
2 Ordering Information
2 TT Series Transceiver Carrier Board

NO OEM LINX REMOTE CONTROL OR FUNCTION MODULE
SHOULD EVER BE USED IN LIFE AND PROPERTY SAFETY
SITUATIONS. No OEM Linx Remote Control or Function Module

should be modified for Life and Property Safety Situations. Such
modification cannot provide sufficient safety and will void the product’s
regulatory certification and warranty.

Customers may use our (non-Function) Modules, Antenna and
Connectors as part of other systems in Life Safety Situations, but
only with necessary and industry appropriate redundancies and
in compliance with applicable safety standards, including without
limitation, ANSI and NFPA standards. It is solely the responsibility
of any Linx customer who uses one or more of these products to
incorporate appropriate redundancies and safety standards for the Life
and Property Safety Situation application.

Do not use this or any Linx product to trigger an action directly
from the data line or RSSI lines without a protocol or encoder/
decoder to validate the data. Without validation, any signal from

another unrelated transmitter in the environment received by the
module could inadvertently trigger the action.

All RF products are susceptible to RF interference that can prevent
communication. RF products without frequency agility or hopping

implemented are more subject to interference. This module does have
a frequency hopping protocol built in, but the developer should still be
aware of the risk of interference.

2 TT Series Transceiver Carrier Board Objects
3 TT Series Transceiver Carrier Board Pin Assignments
3 Programming Dock
3 Programming Dock Objects
4 Remote Control Demo Board
4 Remote Control Demo Board Objects
5 Prototype Board
5 Prototype Board Objects
6 Initial Setup
7 Using the Programming Dock
8 Using the Remote Control Demo Board
10 Using the Prototype Board
13 The Development Kit Demonstration Software
20 Development Kit Demonstration Software Example
28 Carrier Board Schematic
29 Remote Control Demo Board Schematic
33 Programming Dock Board Schematic
37 Prototype Board Schematic

Do not use any Linx product over the limits in this data guide.
Excessive voltage or extended operation at the maximum voltage could
cause product failure. Exceeding the reflow temperature profile could
cause product failure which is not immediately evident.

Do not make any physical or electrical modifications to any Linx
product. This will void the warranty and regulatory and UL certifications

and may cause product failure which is not immediately evident.

TT Series Master Development System

User's Guide

Figure 1: TT Series Master Development System

Introduction

The Linx TT Series Remote Control Transceiver modules offer a simple,
efficient and cost-effective method of adding remote control capabilities to
any product. The Master Development System provides a designer with all
the tools necessary to correctly and legally incorporate the TT Series into
an end product. The boards serve several important functions:

• Rapid Module Evaluation: The boards allow the performance of the Linx
TT Series modules to be evaluated quickly in a user’s environment. The
development boards can be used to evaluate the range performance of
the modules.

• Application Development: A prototyping board allows the development
of custom circuits directly on the board. All signal lines are available on
headers for easy access.

• Software Development: A programming dock with a PC interface allows
development and testing of custom software applications for control of
the module.

• Design Benchmark: The boards provide a known benchmark against
which the performance of a custom design may be judged.

The Master Development System includes 2 Carrier Boards, 2 RC Demo
Boards, 2 Programming Dock Boards, 2 Prototype Boards, 4 TT Series
transceivers*, antennas, batteries and full documentation.

* One part is soldered to each Carrier Board

– –

1

Revised 3/18/2015

Ordering Information

TT Series Transceiver Carrier Board Pin Assignments

Ordering Information

Part Number Description

MDEV-900-TT TT Series Master Development System

MDEV-900-TT-A Amplified TT Series Master Development System

EVAL-900-TT TT Series Basic Evaluation Kit

EVAL-900-TT-A Amplified TT Series Basic Evaluation Kit

TRM-900-TT 900MHz TT Series Remote Control Transceiver

TRM-900-TT-A 900MHz Amplified TT Series Remote Control and Sensor

Transceiver

EVM-900-TT 900MHz TT Series Carrier Board

EVM-900-TT-A 900MHz Amplified TT Series Evaluation Module

MDEV-DEMO-RC-A Development System Remote Control Demo Board, Type A

MDEV-DEMO-RC-B Development System Remote Control Demo Board, Type B

MDEV-PGDOCK Development System Programming Dock

MDEV-PROTO Development System Prototype Board

CON-SOC-EVM EVM Module Socket Kit

Figure 2: Ordering Information

TT Series Transceiver Carrier Board

2

1

ANTENNA 1 2-5 GND (RF Connector)

GND 6

RESET 8

PDN 10

NC 12

PAIR 14

NC 16

LVL_ADJ 18

NC 20
NC 22
NC 24
NC 26
NC 28
NC 30
NC 32
NC 34
NC 36

7 MODE_IND
9 CMD_DATA_IN
11 LATCH_EN
13 ACK_EN
15 CMD_DATA_OUT
17 VCC
19 C0
21 C1
23 NC
25 RSSI
27 NC
29 NC
31 NC
33 NC
35 NC
37 NC

38 S0
39 S1
40 S2
41 S3
42 S4
43 S5
44 S6
45 S7
46 ACK_OUT
47 NC
48 NC
49 NC
50 NC
51 NC
52 NC
53 NC
54 NC
55 NC
56 NC

Figure 4: TT Series Transceiver Carrier Board Pin Assignments (Top View)

Programming Dock

4

2

2

3

1

3

4 4

BottomTop

Figure 3: TT Series Transceiver Carrier Board

TT Series Transceiver Carrier Board Objects

1. TT Series Transceiver

2. MMCX RF Connector

3. Dual Row Header

4. Single Row Header

– – – –

2

3

5

Figure 5: Programming Dock

Programming Dock Objects

1. Carrier Board Socket

2. RP-SMA Antenna Connector

3. MODE_IND LED

4. Micro USB Connector

5. LCD Display

3

Remote Control Demo Board

Prototype Board

2

4

5

6

Figure 6: Remote Control Demo Board

1

7

8

2

3

4

5

6

1

1

7

8

3

6

11

Board BBoard A

Figure 7: Prototype Board

4

3

5

8

10

7

9

2

1

11

12

11

Remote Control Demo Board Objects

1. Carrier Board Socket

2. RP-SMA Antenna Connector

3. Power Switch

4. MODE_IND LED

5. CONFIRM LED

6. PAIR button

7. Status Line Output LEDs

8. Status Line Input Buttons

9. 4 AAA Batteries (Not shown, on the back of the boards)

– – – –

4

Prototype Board Objects

1. Carrier Board Socket

2. RP-SMA Antenna Connector

3. Micro USB Connector

4. Power Switch

5. Power LED

6. External Battery Connection

7. Prototyping Area

8. 3.3V Supply Bus

9. Ground Bus

10. USB Interface Lines

11. Module Interface Headers

12. Command Data Interface Routing Switches (on back)

5

Initial Setup

There are several boards that are included with the Basic Evaluation
Kit and the Master Development System. The Basic Evaluation Kit
includes two Carrier Boards and two Remote Control Demo Boards. The
Master Development System includes these boards but also adds two
Programming Docks and two Prototype Boards.

The Carrier Boards have a TT Series transceiver on a daughter board with
headers. These boards snap into sockets on the other boards, enabling the
modules to be easily moved among the test boards.

There are two Remote Control Demo Boards that are populated differently.
Board A has the buttons on the right column and board B has them on the
left column. These accept the Carrier Boards and are used to demonstrate
the remote control functionality of the TT Series. They can also be used for
range testing. These boards use hardware configuration, so if any changes
have been made to the modules using the software then they may not
operate correctly. A restore to default configuration can be used to reset
the modules.

Using the Programming Dock

Snap a Carrier Board onto the socket on the Programming Dock as shown
in Figure 8.

The Programming Docks have a socket for a Carrier Board and a USB
interface for connection to a PC. This is used with the demonstration
software included with the kit to configure the module through its
Command Data Interface.

The Prototype Boards have a socket for a Carrier Board, a USB interface
and a large area of plated through holes that can be used to develop
custom circuitry. The board can be powered either from the USB
connection or an external battery.

Warning: Installing or removing a Carrier Board while power is

!

applied could cause permanent damage to the module. Either turn
off power to the board or unplug the USB cable before installing or
removing a Carrier Board

Figure 8: Programming Dock with a Carrier Board

Connect a micro USB cable into the connector at the top of the board.
Plug the other end into a PC. The board is powered by the USB bus.
The demonstration software included with the kit or custom application
software can be used to configure the module through its Command
Data Interface. The LCD is used to display information about the module.
This includes the module’s local address and a custom nickname. The
nickname is entered using the development kit software and can be
any name that helps distinguish the modules from one another. This is
convenient when multiple programming docks are connected to the same
computer. Please see the development kit software section for more
information on the nicknames.

The TT Series transceiver has a serial Command Data Interface that offers
the option to configure and control the transceiver through software instead
of through hardware. This interface consists of a standard UART with a
serial command set. This allows for fewer connections in applications
controlled by a microcontroller as well as for more control and advanced
features than can be offered through hardware pins alone.

– – – –

6

7

Using the Remote Control Demo Board

Snap a Carrier Board onto the socket on each Remote Control Demo
Board as shown in Figure 9.

Range Testing

Several complex mathematical models exist for determining path loss in
many environments. These models vary as the transmitter and receiver are
moved from indoor operation to outdoor operation. Although these models
can provide an estimation of range performance in the field, the most
reliable method is to simply perform range tests using the modules in the
intended operational environment.

Range testing can be performed with the Remote Control Demo Boards.
To prepare the board for range testing, simply turn it on by switching the
power switch to the ON position. Pressing a status line button on one
board (the IU) activates an LED on the other board (the RU). The RU then
sends an acknowledgement back to the IU, which turns on the CONFIRM
LED. This indicates good bi-directional RF communications and lets the
user set one board down and walk with the other board.

Figure 9: Remote Control Demo Board with a Carrier Board

Insert 4 AAA batteries into the holders on the back of each board, connect
antennas and turn on power.

The modules come paired out of the box, but to Pair additional modules,
press the PAIR button on both boards. The MODE_IND LEDs flash to
indicate that the modules are searching for each other and exchanging
addresses. The MODE_IND has a quick flash while searching (100ms on,
900ms off) and a longer flash once Pairing is complete (400ms on, 100ms
off). This process only takes a few seconds. The pairing process takes the
status line input / output directions into account. If these are changed then
the modules should be paired again.

Once complete, pressing a button on one board (the Initiating Unit or IU)
causes an LED to light up on the other board (the Responding Unit or RU).
The RU sends an acknowledgement message to the IU. If the message is
valid, the IU turns on the CONFIRM LED.

Note: To restore the default configuration, push the PAIR button four

times and hold it down on the fifth press. The MODE_IND LED flashes
when it has reset. Alternatively press and hold the RESTORE button on
the back of the board for 5 seconds. When the LED turns off, release the
button and the LED flashes twice to indicate a successful restore.

As the maximum range of the link in the test area is approached, it is not
uncommon for the signal to cut in and out as the radio moves. This is
normal and can result from other interfering sources or fluctuating signal
levels due to multipath effects. This results in cancellation of the transmitted
signal as direct and reflected signals arrive at the receiver at differing times
and phases. The areas in which this occurs are commonly called “nulls”
and simply walking a little farther usually restores the signal. If the signal is
not restored, then the maximum range of the link has been reached.

To achieve maximum range, keep objects such as your hand away from
the antenna and ensure that the antenna on the transmitter has a clear and
unobstructed line-of-sight path to the receiver board. Range performance
is determined by many interdependent factors. If the range you are able to
achieve is significantly less than specified by Linx for the products you are
testing, then there is likely a problem with either the board or the ambient
RF environment in which the board is operating. First, check the battery,
switch positions, and antenna connection. Next, measure the receiver’s
RSSI voltage with the transmitter turned off to determine if ambient
interference is present. High RSSI readings while the transmitter off indicate
there is interference. If this fails to resolve the issue, please contact Linx
technical support.

Note: The Remote Control Demo boards are designed for hardware

configuration. If the modules are changed through software configuration
then the boards may not operate as expected. A restore to default
configuration can be used to reset the modules.

– – – –

8

9

Using the Prototype Board

Snap a Carrier Board onto the socket on the Prototype Board as shown in
Figure 10.

Supply for the module is connected through R17. This can be removed and
replaced by another supply or used to measure the current consumption of
the module.

Note: The onboard 3.3-volt regulator has approximately 400mA available

for additional circuitry when plugged into a PC. If more current is
required, the user must power the board from an external supply or a
USB charger with more current capabilities, up to 1A.

Figure 11 shows the bottom of the board.

Figure 10: Prototype Board with a Carrier Board

Connect a micro USB cable into the connector at the top of the board.
Plug the other end into a PC or any USB power adapter. The board is
powered by the USB bus. This board features a prototyping area to
facilitate the addition of application-specific circuitry. The prototyping area
contains a large area of plated through-holes so that external circuitry
can be placed on the board. The holes are set at 0.100" on center with
a 0.040" diameter, accommodating most industry-standard SIP and DIP
packages.

At the top of the prototyping area is a row connected to the 3.3V power
supply and at the bottom is a row connected to ground. External circuitry
can be interfaced to the transceiver through the breakout headers. The
numbers next to the headers correspond to the pin numbers on the Carrier
Board. Figure Figure 4 shows the pin assignments for the Carrier Board.

The OVERLOAD LED indicates that that too much current is being pulled
from the USB bus. This is used to prevent damage to the parts or the bus.

– – – –

10

Figure 11: Prototype Board Bottom Side

SW1 and SW2 connect the USB interface to the Command Data Interface
lines on the module. This allows the prototype board to be used with the
development kit software or a custom application. When in the “USB
Connected position”, the module is connected to the USB interface. The
“Header Only” position connects the module to the header.

Footprints for 0603 size resistors are on most lines so that pull-ups or
pull-downs can easily be added to the lines. The pads are connected to
VCC or GND based on the most common configuration for the module. The
schematic at the end of this document shows how each line is connected.

11

The overload condition is reset once the excess current draw is removed.
The LADJ line has pads for both a pull up and pull down resistor. This can
be populated based on the needs of the specific module that is connected
to the prototype board. The TT Series uses the pull-down resistor. Do
not populate both resistors at the same time as this results in a direct
connection between power and ground.

Figure 12 shows a convenient cross reference showing which lines on the
module connect to which lines on the prototype board.

Module to Prototype Board Pin Number Cross Reference

Pin Name Module Pin Number Prototype Board Pin Number

MODE_IND 35 7

RESET 16 8

CMD_DATA_IN 27 9

POWER_DOWN 24 10

LATCH_EN 15 11

ACK_EN 36 13

PAIR 33 14

CMD_DATA_OUT 29 15

VCC 25 17

LVL_ADJ 14 18

C0 30 19

C1 32 21

RSSI 21 25

S0 9 38

S1 10 39

S2 12 40

S3 13 41

S4 20 42

S5 26 43

S6 19 44

S7 18 45

ACK_OUT 31 46

Figure 12: Module to Prototype Board Pin Number Cross Reference

The Development Kit Demonstration Software

The development kit includes software that is used to configure and control
the module through the Programming Dock. The software defaults to the
Demo & EZConfiguration tab when opened (Figure 13). This window offers
basic configuration and demonstration of the module’s functionality with the
current configuration.

1

7

2

6

3

4

5

8

9

11

Figure 13: The Master Development System Software Demo and EZConfiguration Tab

1. Clicking the Contact Linx, Documentation and About labels on the

left side expands them to show additional information and links to the
latest documentation. This is shown in Figure 15.

2. The Help window shows tips and comments about the software.

3. The active module is connected to the PC and being configured by the

software.

4. Available modules are connected to the PC but are not currently being

configured or controlled by the PC

5. Known Modules are not currently connected to the PC, but have either

been connected to the software in the past or have been manually
entered.

6. The Given Permissions window shows the list of modules that are

paired with the active module and the Permissions Mask for each one.

7. The demo area replicates a remote control device. The appearance

changes with the programmed configurations.

10

– – – –

12

13

8. The Status Details section shows the module’s control line states, radio
state and RSSI level.

9. The Sent and Received Packets window shows the commands
sent to the module and the responses from the module. This aids in
debugging custom software.

10. Once a module has been configured, the configurations can be saved
into a profile that can be recalled and programmed into other modules.
The Saved Profiles list shows all of the profiles that have been saved
into the software.

11. The Show Commands button opens a larger window to view the serial
commands sent to and received from the module.

The modules are shown with three identifiers as shown in Figure 14.

The Advanced Configuration tab (Figure 16) offers more detailed
configuration options for the active module.

1

5

6

7

2
3

4

9

10

11

12

13

1

2 3

Figure 14: The Master Development System
Software Module Identifiers

1. The type of module (TT Series)

2. The module’s local address.

3. A custom name that can be given to the module. Type a name into
the box and press Enter to apply it. This name is shown on the LCD
display on the programming dock.

Figure 15: The Master Development System
Software Additional Information

14

8

16

18

17

Figure 16: The Master Development System Software Advanced Configuration Tab

15

19

1. The Local Address box shows the module’s local address in
hexadecimal format. This can be changed by typing a new hex value.

2. The Status Line Mask sets the status lines as either inputs or outputs.
If the box is checked then the line is an input.

3. The Latch Mask determines if the status line outputs are latched or
momentary. If the box is checked then the output is latched. This
setting has no effect on lines that are configured as inputs.

4. The Paired Modules Window lists all of the modules that are paired
with the active module and their Permissions Mask.

5. The Address box enables manual pairing of a module. Enter an
address into this box and press the Set Module button to add the
address to the list.

6. The Permissions Mask determines whether a specific module is
authorized to control a specific status line output. If the box is checked
then the module is authorized to control that line.

– – – –

14

15

7. The Set Module button adds the address and Permissions Mask to
the list. If a current module is selected, then the Permissions can be
updated. The Remove module button removes the selected module
from the list. The Remove All Modules button removes all of the
modules from the list.

8. The Interrupt Mask sets the conditions under which an interrupt is to
be generated on the CMD_DATA_OUT line. The Message Select menu
sets the type of message that triggers the interrupt when the Selected
Message Ready box is checked.

9. The TX Power Level Source configures how the transmitter output
power is set. It uses either the voltage on the LVL_ADJ line or the value
in the box. The accepted range of values is –20 to +12.

10. The Transmitter Mode selection sets whether the module transmits
command messages when a status line input is asserted or when it
receives a software command.

11. The Receiver Mode selection turns the receiver on or off for power
savings. If the module is set as an Initiating Unit only with all status lines
as inputs, then the receiver is disabled by default.

12. The Status Line Direction selection sets how the status lines are
configured as inputs and outputs. Either the C0 and C1 hardware lines
are used to set them in groups of 4 or the Status Line Mask is used to
set them individually.

13. The Latch Status Outputs selection configures how the latched or
momentary operation for each status line output is set. Either the
LATCH_EN hardware line is used to set all of the lines the same way or
the Latch Mask is used to set the lines individually.

14. The Custom Data box enables a custom 2-byte value to be loaded
into the module to be transmitted with each control message or
Acknowledge with Data packet.

15. The Duty Cycle configuration sets the interval and Keep on times for
automatically cycling power to the receiver.

16. The Module Identity box displays the module type, firmware version
and serial number of the active module.

17. The Read All button reads all of the current configurations from the
active module.

18. The Submit button writes all changes to the active module.

19. The Set Defaults button restores the active module to factory default
conditions.

The Command Set tab (Figure 17) allows specific commands to be written
to the module.

1

2

Figure 17: The Master Development System Software Command Set Tab

3

6

4

5

1. The Command box shows the hexadecimal values that are written to
the module. Values can be typed into the box or a command can be
selected from the Commands menu.

2. The Response box shows the hexadecimal values that are returned
from the module in response to a command.

3. The Commands drop-down menu shows all of the commands that
are available for the active module (Figure 18). Selecting one of the
commands from this menu automatically fills in the Command box. The
values can be adjusted by typing in the box.

Figure 18: The Master Development System Software
Demo Command Set Tab Commands Menu

– – – –

16

17

4. The Items drop down menu displays all of the items that are available
for the active module (Figure 19). Selecting one of the items from
this menu automatically fills in the Command box. The values can be
adjusted by typing in the box.

The Sandbox tab shows the interaction of all of the connected modules
on one screen. Figure 20 shows two modules on the screen, but up to 8
modules can fit at one time.

Figure 19: The Master Development System Software
Demo Command Set Tab Items Menu

5. Clicking the Send button writes the values in the Command box to the
module.

6. The structure of the selected command and its response is shown
in the main window. Please see the TT Series Transceiver Command
Data Interface Reference Guide for definitions of each value.

Figure 20: The Master Development System Software Sandbox Tab

Clicking a button on one device causes the module to transmit control
messages. Paired modules with appropriate Permissions Mask settings
activate and their status is updated in the software. Paired modules that are
not connected to the PC can activate a module that is connected and the
connected module’s status is reflected in the software.

The Sandbox is a convenient place to show the interaction of multiple units
in one location, but it is a reflection of actual module operation. It is not a
simulation.

– – – –

18

19

Development Kit Demonstration Software Example

This example shows how to configure two modules to work with each
other. The software defaults to the Demo & EZConfiguration tab when
opened (Figure 21).

Figure 21: The Master Development System Software Demo and EZConfiguration Tab

Install Carrier Boards onto the Programming Docks and plug a USB cable
between the Programming Docks and the PC. The software automatically
detects attached devices. The first module that is identified appears
under the Active label. This is the module that is actively controlled by
the software. Subsequent modules are listed under the Available label as
shown in Figure 22.

Figure 23: The Master Development System Software Pairing Modules

Once the module is dropped into the Given Permissions window it is
written to the active module’s memory. Clicking on the down arrow displays
the paired module’s Permissions Mask. This configures which output lines
the paired module is authorized to control. In Figure 24 the Permissions are
inactive since the active module only has inputs and no outputs to control.

Figure 22: The Master Development System
Software Connected Modules

Modules must be paired with the active device. This is accomplished by
dragging modules from the Available or Known Modules lists to the Given
Permissions window as shown in Figure 23.

– – – –

20

Figure 24: The Master Development System Software Paired Modules

21

Changing the active module is accomplished by dragging a module from
the Available list to the Active spot, as shown in Figure 25.

Figure 25: The Master Development System Software Changing the Active Module

With the new module active, drag the original module to the Given
Permissions window. Click on the Advanced Configuration tab (Figure 26).

This tab shows the advanced configurations enabled by the module’s
Command Data Interface. Any changes are highlighted in red. In the
example in Figure 27 the output mask has been changed to all inputs, S0 is
latched, the Paired module is given full permissions, the status line direction
is set by the mask and the outputs are latched by the Latch Mask. Clicking
the Set Module button sets the updated Permissions Mask. Clicking the
Submit button writes all of the changes to the module’s memory.

Figure 26: The Master Development System Software Advanced Configuration

– – – –

22

Figure 27: The Master Development System Software Advanced Configuration with Changes

This configuration changes the module to have all outputs. This is shown
by clicking on the Demo & EZConfiguration tab Figure 28.

23

Figure 28: The Master Development System Software Demo and EZConfiguration Tab with Changes

The buttons have all changed to LEDs. The symbol next to each LED
indicates if it is latching or momentary (Figure 29). S0 is latching, the rest
are momentary.

1 2

Figure 29: The Master Development System Software
Latching (1) and Momentary (2) Symbols

Now that the modules are configured their use can be demonstrated.
Clicking a button on the transmitter module activates an LED on the
receiving module. Figure 30 shows the transmitter, Figure 31 shows the
receiver.

Figure 30: The Master Development System Software Transmitting Module

Figure 31: The Master Development System Software Receiving Module

– – – –

24

25

Full system operation is demonstrated by clicking on the Sandbox tab
(Figure 32).

Figure 32: The Master Development System Software Sandbox

These configurations can be saved as a profile for recalling or programming
into other modules. The Demo & EZConfiguration tab has the profile
window (Figure 33).

Figure 34: The Master Development System Software Save Profile

Once saved, the profile appears in the window, as shown in Figure 35.

Figure 33: The Master Development System
Software Saved Profiles Window

Clicking the Save Current button brings up a prompt asking for a name of
the profile (Figure 34).

– – – –

26

Figure 35: The Master Development System Software with a Saved Profile

To apply a profile, select it from a list and click the Program button. Clicking
the Remove button removes it from the list.

27

CONFIRM

S0
S1
S2
S3
S4
S5
S6
S7

38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56

PAIR

MODE_IND

LATCH_EN

RSSI

ACK_EN

RESET

PDN

LVL_ADJ

CMD_DATA_IN

CMD_DATA_OUT

ANT

C0
C1

1

23

45

67
89
10 11
12 13
14 15
16 17
18 19
20 21
22 23
24 25
26 27
28 29
30 31
32 33
34 35
36 37

J1
Carrier Interconnect Male

GND

GND

GND

GND

GND

VCC

RF MODULE AREA

RF MODULE CARRIER AREA

DG

Carrier Board Schematic

RF

1

GND

2-5

ANT1

CONREVSMA002

PAIR

MODE_IND

CONFIRM

LATCH_EN

D0
D1
D2
D3
D4
D5

ACK_EN

PDN

CMD_DATA_IN

CMD_DATA_OUT

D6
D7

SER_I/O

C0
C1
SEND

CRT_LRN

GND

GND

VCC

GNDGND

GND

GND

1

23

45

67
89
10 11
12 13
14 15
16 17
18 19
20 21
22 23
24 25
26 27
28 29
30 31
32 33
34 35
36 37

38
39
40

41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56

J1
Carrier Interconnect Female

LVL_ADJ IDENTITY

GND

X2

DNP

X1

1.8nH

ED_SEL

SEL_TIMER

D8
D9
D_CFG
A_CFG_0
A_CFG_1

BAUD_0

YC

RF MODULE AREA

MICROCONTROLLER AREA

RF MODULE CARRIER AREA

TR1

1

GND

2

NC

3

GND

4

NC

5

NC

6

GND

7

S0

S1

S2

S3

S7

S4

RSSI

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

TRM-XXX-TT

NC

NC

S0

S1

GND

S2

S3

LVL_ADJ

LATCH_EN

RESET

GND

S7

S6

S4

RSSI

GND

ANTENNA

MODE_IND

ACK_OUT

CMD_DATA_OUT

CMD_DATA_IN

POWER_DOWN

LATCH_EN

GND

GND

GND

GND

LVL_ADJ

RESET

GND

GN

Figure 36: TT Series Transceiver Carrier Board Module Schematic

GND

GND

NC

NC

GND

NC

NC

ACK_EN

GND

PAIR

C1

C0

GND

S5

VCC

GND

44

43

42

41

40

39

38

37

36

35

34

33

32

31

30

29

28

27

26

25

24

23

GND

ANT

GND

GND

ACK_EN

MODE_IND

GND

PAIR

C1

CONFIRM

C0

CMD_DATA_OUT

GND

CMD_DATA_IN

D5S6

VCC

PDN

ND

ANT

GND

GND

GND

RESET

PDN

PAIR

LVL_ADJ

23

1

45

67
89
10 11
12 13
14 15
16 17
18 19
20 21
22 23
24 25
26 27
28 29
30 31
32 33
34 35
36 37

J1
Carrier Interconnect Male

Figure 37: TT Series Carrier Board Header Schematic

Remote Control Demo Board Schematic

Note: The Remote Control Demo boards are designed to accept carrier

boards for multiple module families. Some circuitry is not applicable for
some modules.

GND

RESTORE

R14
330

S9

CMD_DATA_OUT

CMD_DATA_IN

GND

GND

MODE_IND
CMD_DATA_IN
LATCH_EN
ACK_EN
CMD_DATA_OUT

VCC
C0
C1

RSSI

VCC GND

MCLR

IDENTIT

U2

1

VDD

2

RA5

3

RA4

4

MCLR

5

RC5

6

RC4

7

RC3

PIC16F1824

ICSPDAT
ICSPCLK

GND

RA2
RC0
RC1
RC2

38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56

14
13
12
11
10
9
8

S0
S1
S2
S3
S4
S5
S6
S7

CONFIRM

PGD
PGC
SER_I/O
PIC A/B
MODE_IND

RT_LRN

– – – –

28

D7

GND

RESTORE COMPLETE GREEN

Figure 38: Remote Control Demo Board Microcontroller Area Schematic

29

CONREVSMA002

RF MODULE AREA

VCC

RF

1

GND

2-5

ANT1

CONREVSMA002

GND

GND

X2

DNP

X1

1.8nH

POWER SUPPLY AREA

RF MODULE AREA

1
2
3

P2

Header 3

D4

D5

D6

1
2
3
4

P1

Header 4

D0
D1
D2
D3

GND

R2
330

VCC

D1

POWER GREEN

MODE_IND

GND

R3
330

D2

MODE_IND BLUE

CONFIRM

GND

R27
330

D20

CONFIRM RED

GND

SW1
SPDT

GND

VCC

B1

GND

Vin

1

GND

2

Vout

3

U1

C1

0.47uF

GND

+

C2

100uF

R36
0

R33
0

VCC

GND

SW2

LVL_ADJ

ACK_EN

R32 0

VCC

R34 10K

BAUD_0

IDENTITY

SEL_TIMER

SEND

LATCH_EN

PDN

R8 0

R38 10K

R37 10K

R35 10K

R9 10K

D8

D9

R41 10K

R42 10K

D_CFG

A_CGF_0

A_CFG_1

R6 10K

R5 10K

R4 10K

GND

VCC

S8

PAIR

R1
10K

PAIR CRT_LRN

REMOTE CONTROL AREA

POWER SUPPLY AREA

MISC CIRCUITS

1
2
3

P3

Header 3

D7

VCC

GND

1
2
3
4

J2

MCLR

PGD

5
6

PGC

VCC
GND

ANT1

1

RF

GND

GND

2-5

GNDGND

GND

GND

PDN

PAIR

LVL_ADJ IDENTITY

SER_I/O

ED_SEL

X1

1.8nH

X2

GND

DNP

1

23

45

67
89
10 11
12 13
14 15
16 17
18 19
20 21
22 23
24 25
26 27
28 29
30 31
32 33
34 35
36 37

J1
Carrier Interconnect Female

GND

MODE_IND
CMD_DATA_IN
LATCH_EN
ACK_EN
CMD_DATA_OUT

VCC
C0
C1
SEND

Figure 39: Remote Control Demo Board RF Carrier Area Schematic

SW1

GND

SPDT

B1

GND

1

C1

0.47uF

U1

Vin

Vout

GND

2

GND

Figure 40: Remote Control Demo Board Power Supply Area Schematic

– – – –

30

A Board B Board A Board

R30 0 ohm

C0

R31 0 ohm

C1 GND

D0

PIC A/B

ED_SEL

R12
330

D5

38
39
40

41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56

D0
D1
D2
D3
D4
D5
D6
D7
CONFIRM

BAUD_0
SEL_TIMER

CRT_LRN

D8
D9
D_CFG
A_CFG_0
A_CFG_1

D10

D14

GND

GND

GND

R17
330

R21
330

D1

D2

SEND

SEND

SEND

D3

VCC

3

+

C2

100uF

GND

R2
330

D1

POWER GREEN

GND

D18

Figure 41: Remote Control Demo Board Remote Control Area Schematic

GND

R25
330

SEND

R39 0 ohm

R7 10K

D3

R10
10K

GND

D8

R15
10K

GND

D12

R19
10K

GND

D16

R23
10K

GND

VCCS0

D19

VCCS1

D15

VCCS2

D11

VCCS3

D6

31

VCC

GND

GND

GND

GND

GND

GND

R26
330

R22
330

R18
330

R13
330

D7

D6

D5

D4

C0

C1

PIC A/B

ED_SEL

D17

R24

SEND

10K

D13

R20

SEND

10K

D9

R16

SEND

10K

D4

R11

SEND

10K

R28 0 ohm

R29 0 ohm

R40 0 ohm

R43 10K

GND

GND

GND

GND

GND

VCC

VCC

VCC

VCCS7

VCCS6

VCCS5

VCCS4

P1

GND

R2
330

VCC

D1

POWER GREEN

RF

1

GND

2-5

ANT1

CONREVSMA002

PAIR

MODE_IND

CONFIRM

LATCH_EN

D0
D1
D2
D3
D4
D5

ACK_EN

PDN

CMD_DATA_IN

CMD_DATA_OUT

D6
D7

SER_I/O

C0
C1
SEND

CRT_LRN

GND

GND

VCC

GNDGND

GND

GND

1

23

45

67
89
10 11
12 13
14 15
16 17
18 19
20 21
22 23
24 25
26 27
28 29
30 31
32 33
34 35
36 37

38
39
40

41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56

J1
Carrier Interconnect Female

LVL_ADJ IDENTITY

GND

X2

DNP

X1

1.8nH

ED_SEL

SEL_TIMER

D8
D9
D_CFG
A_CFG_0
A_CFG_1

BAUD_0

GND

SW1
SPDT

GND

VCC

B1

GND

Vin

1

GND

2

Vout

3

U1

C1

0.47uF

GND

+

C2

100uF

VDD

1

RA5

2

RA4

3

MCLR

4

RC5

5

RC4

6

RC3

7

RC2

8

RC1

9

RC0

10

RA2

11

ICSPCLK

12

ICSPDAT

13

GND

14

U2

PIC16F1824

VCC GND

PGD
PGC

MCLR

CMD_DATA_IN

CMD_DATA_OUT

IDENTITYCRT_LRN

MODE_IND

GND

SER_I/O

R14
330

GND

S9

RESTORE

D7

RESTORE COMPLETE GREEN

PIC A/B

VCC

POWER SUPPLY AREA

RF MODULE AREA

MISC CIRCUITS

MICROCONTROLLER AREA

D0
D1
D2
D3

D6
D5
D4

D7

VCC

R4 10K

R32 0

R8 0

PDN

ACK_EN

1
2
3
4

VCC

GND

A_CFG_1

A_CGF_0

R5 10K

Header 4

P2

1
2
3

Header 3

P3

1
2
3

Header 3

R6 10K

D_CFG

LATCH_EN

R35 10K

R9 10K

GND

GND

SEND

R37 10K

R33
0

SW2

R36
0

SEL_TIMER

R38 10K

Figure 42: Remote Control Demo Board Miscellaneous Circuits Schematic

BAUD_0

LVL_ADJ

IDENTITY

R41 10K

R34 10K

D8

MCLR

PGD
PGC

R42 10K

VCC
GND

D9

VCC

S8

PAIR

PAIR CRT_LRN

R1
10K

GND

J2

1
2
3
4
5
6

MODE_IND

R3
330

D2

MODE_IND BLUE

GND

CONFIRM RED

GND

CONFIRM

R27
330

D20

Programming Dock Board Schematic

X1

1

ANT1

Figure 43: Programming Dock Board RF Carrier Area Schematic

X3

1nH

X2

GND

RF

DNP

DNP

R1

1 Ohm

VCC

GND

GND

2-5

GND

GND

GND

GND

GND

R15 10k

R14 10k

R13 10k

R12 10k

R10 10k

38394041424344454647484950515253545556

CMD_DATA_IN

MODE_IND

GND

1

23

45

67

GND

GND

GND GND

R40

VCC

GND

GND

GND

GND

R22 10k

R21 10k

R18 10k

GND

VCC

CMD_DATA_OUT

R20 10k

R17 10kR1610k

89

10 11

12 13

14 15

PAIR

R1910k

VCC

GND

0 Ohm

SW1

16 17

GND

GND

R9 10k

GND

R28 10k

IDENTITY

VCC

VCC

R29 10k

R27 10k

R25 10k

18 19

20 21

R7 10k

R2310k

GND

GND

CRT_LRN

R30 10k

R36 1k

GND

22 23

24 25

SER_I/O

GND

GND

GND

R34 10k

R33 10k

R32 10k

GND

GND

R44 10k

R45 10k

26 27

28 29

30 31

32 33

R2610k

R3710k

R3110k

VCC

GND

GND

GND

R41

0 Ohm

R35 10k

R3910k

GND

R38 10k

34 35

R4310k

GND

VCC

36 37

GND

J2

Carrier Interconnect

– – – –

32

33

5VUSB VCCU

CRT_LRN

IDENTITY

R9 10k

GND

GND

GND

GND

GND

GND

GND

GND

GND

GND

GND

GND

GND

GND

R35 10k

R34 10k

R33 10k

R32 10k

R30 10k

R28 10k

R22 10k

R21 10k

R18 10k

R15 10k

R14 10k

R13 10k

R12 10k

R10 10k

R36 1k

GND

R38 10k

VCC

C12

0.1uF

VCC

GND

GND

+

C8

100uF

VCC

GND

Vin

1

GND

2

Vout

3

U4
LM3940IMP 3.3V

C9

0.47uF

GND

IN

1

GND

2

EN3FAULT

4

ILIM

5

OUT

6

U3
TPS2552

GND

5VUSB VCCU

GND

R11

53.6k

PWREN#

SIGNAL ROUTING

CRT_LRN

38394041424344454647484950515253545556

IDENTITY

R9 10k

GND

GND

GND

GND

GND

GND

GND

GND

GND

GND

GND

GND

GND

GND

R35 10k

R34 10k

R33 10k

R32 10k

R30 10k

R28 10k

R22 10k

R21 10k

R18 10k

R15 10k

R14 10k

R13 10k

R12 10k

R10 10k

R36 1k

GND

R38 10k

VCC

R41

0 Ohm

R40

0 Ohm

VCC

GND

SW1

VCC

R1

1 Ohm

MODE_IND

CMD_DATA_IN

CMD_DATA_OUT

GND

GND

GND GND

GND

VCC

1

23

45

67

89

10 11

12 13

14 15

16 17

18 19

20 21

22 23

24 25

26 27

28 29

30 31

32 33

34 35

36 37

J2

Carrier Interconnect

SER_I/O

R29 10k

GND

GND

VCC

GND

VCC

VCC

R27 10k

R25 10k

R20 10k

R17 10kR1610k

R1910k

R3110k

VCC

PAIR

GND

R7 10k

GND

R2310k

GND

R2610k

GND

R3710k

GND

R3910k

GND

R4310k

R44 10k

GND

R45 10k

GND

RF

1

GND

2-5

ANT1

GND

GND

X1

1nH

X3

DNP

GND

X2

DNP

C12

0.1uF

VCC

GND

GND

MODE_IND

R8

330

D4

MODE_IND BLUE

IN

1

VCC

2

GND

3

NC

4

COM

5

NO

6

U5

MAX4544EUT

MODE_IND_MT

GND

C10

0.1uF

//IDENTITY

VCC

GND

IDENTITY

GND

VCC

A

1

GND

2

B

3

/B

4

VCC

5

/A

6

U7

NC7WZ04

GND

C11

0.1uF

/IDENTITY

/IDENTITY //IDENTITY

R24
10k

S2

VCC

PAIR

PAIR CRT_LRN

GND

GND

+

C8

100uF

VCC

GND

Vin

1

GND

2

Vout

3

U4
LM3940IMP 3.3V

C9

0.47uF

GND

IN

1

GND

2

EN3FAULT

4

ILIM

5

OUT

6

U3
TPS2552

GND

5VUSB VCCU

GND

R11

53.6k

PWREN#

USB AREA POWER SUPPLY AREA RF MODULE CARRIER AREA

SIGNAL ROUTING

GND

CRT_LRNIN

1

VCC

2

GND

3

NC

4

COM

5

NO

6

U1

MAX4544EUT

GND

C3

0.1uF

SER_I

SER_O

VCC

SER_I/O

CRT_LRN

CMD_DATA_IN

CMD_DATA_OUT

MODE_IND_MT

SER_ISER_O

RTS

CTS

DIR

1

A1

2

A2

3

A3

4

A4

5

A5

6

A6

7

A7

8

A8

9

GND

10

B8

11

B7

12

B6

13

B5

14

B4

15

B3

16

B2

17

B1

18

OE

19

VCC

20

U6

SN74AHC245

VCCVCC

/IDENTITY

GND

GND

PWREN#

VCC

GND

Figure 44: Programming Dock Board Power Supply Area Schematic

D4

R8

330

GND

PAIR CRT_LRN

U3
TPS2552

1

IN

2

GND

EN3FAULT

C12

0.1uF

MODE_IND

MODE_IND_MT

SER_O

MODE_IND BLUE

SER_I/O

SER_I

VCC

IDENTITY

S2

PAIR

GND

/IDENTITY //IDENTITY

R24
10k

CMD_DATA_IN

MODE_IND_MT

OUT

ILIM

U5

4
5
6

MAX4544EUT

U1

4

NC

5

COM

6

NO

MAX4544EUT

1
2
3

RTS

GND

6

5

4

GND

NC
COM
NO

U7

A
GND
B

NC7WZ04

U6

1
2
3
4
5
6
7
8
9

10

SN74AHC245

GND

Figure 45: Programming Dock Board Signal Routing Schematic

Vout

VCC

GND

3

VCC

+

GND

C11

0.1uF

C8

100uF

5VUSB

Figure 46: Programming Dock Board USB Area Schematic

+

C2

0.1uF

C1

4.7uF

CMD_DATA_IN

1

TXD

3

12

3V3OUT

U2

FT230X

10

GND

L1

600R/1.3A

J1

CMD_DATA_OUT

4

RXD

VCCIO

VCC

1

Micro USB

RTS

CTS

6

RTS#2CTS#

USBDM9USBDP8RESET#

R2 27

2

3NC4

5V

DAT+

DAT-

35

U4
LM3940IMP 3.3V

1

Vin

GND

VCC

//IDENTITY

CRT_LRNIN

20
19
18
17
16
15
14
13
12
11

GND

2

VCCVCC
/IDENTITY
SER_ISER_O
CMD_DATA_OUT
CRT_LRN
CTS

R11

53.6k

GND

VCC

GND
VCC

DIR
A1
A2
A3
A4
A5
A6
A7
A8
GND

– – – –

34

0.47uF

GND

3
2
1

IN

GND

3
2
1

GND

6

/A

5

VCC

4

/B

VCC

OE

B1
B2
B3
B4
B5
B6
B7
B8

GND

C10

0.1uF

GND

VCC

C3

0.1uF

/IDENTITY

C9

PWREN#

16

CBUS015CBUS114CBUS27CBUS3

GND
GND

11

GSHD

6

GSHD

7

C7

C6

C5

C4

R3 27

5

GND

R5

GND

GND

GND

D1

13

5

0.1uF

47pF

47pF

0.01uF

R4

0

TX/RX_IND ORANGE

330

5VUSB

CMD_DATA_OUT

CMD_DATA_IN

GND

+

C6

47pF

C2

0.1uF

VCC

12

VCCIO

3

3V3OUT

10

GND

5

GND

13

USBDM9USBDP8RESET#

11

TXD

1

RXD

4

RTS#2CTS#

6

CBUS015CBUS114CBUS27CBUS3

16

U2

FT230X

C5

47pF

PWREN#

C7

0.1uF

GND

5VUSB

5VUSB

D1

TX/RX_IND ORANGE

RTS

CTS

R2 27

R3 27

R5

330

USB AREA POWER SUPPLY AREA RF MODULE CARRIER AREA

MICROCONTROLLER AREA

T

GND BUS

1

TP3

39404142434445

4647484950515253545556

38

37

36

35

323334

1

2

3

4

J6

100mil Header

TXD

RXD

RTS

CTS

VCC BUS

123456789

10

11

J7 100mil Header

123456789

1011121314

J4

100mil Header

R45 DNP

GND

R44 DNP

R43 DNP

R42 DNP

R41 DNP

R40 DNP

R39 DNP

R38 DNP

GND

GND

GND

GND

GND

GND

GND

GND

R52 DNP

R50 DNP

GND

R47 DNP

GND

R48 DNP

GND

R49 DNP

GND

PROTOTYPE AREA

C10

0.1uF

GNDVCC

R32 DNP

GND

R34 DNP

GND

R35 DNP

GND

R53 DNP

GND

R54 DNP

GND

R55 DNP

GND

R56 DNP

GND

GND

R24
330

5VUSB

D2

POWER (GREEN)

D3

OVER CURRENT (RED)

R22
330

VCC

FAULT

VCC BUS

GND BUS

1

TP3

1

TP2

GND GND

1

TP4

VCC

39404142434445

4647484950515253545556

38

37

36

35

293031

323334

789101112131415161718192021222324252627

28

1

2

3

4

J6

100mil Header

TXD

RXD

RTS

CTS

12345678910111213141516171819202122232425

26

J5

100mil Header

VCC BUS

6

R6 0

GND

VCC

R10 DNP

VCC

123456789

10

11

J7 100mil Header

123456789

1011121314

J4

100mil Header

R45 DNP

GND

R44 DNP

R43 DNP

R42 DNP

R41 DNP

R40 DNP

R39 DNP

R38 DNP

GND

GND

GND

GND

GND

GND

GND

GND

R52 DNP

R19 DNP

GND

VCC

R11 DNP

GND

R50 DNP

GND

R14 DNP

GND

R170

VCC

R12 DNP

GND

R26 DNP

R23 DNP

GND

R21 DNP

GND

R47 DNP

GND

R48 DNP

GND

R49 DNP

GND

R15

DNP

VCC

R18

DNP

GND

R13 DNP

U2

R5

10k

GND

5VUSB

GND

+

C7
100uF

VCC

GND

Vin

1

GND

2

Vout

3

U3

C8

0.47uF

GND

FAULT

IN

1

GND

2

EN3FAULT

4

ILIM

5

OUT

6

TPS2553

SW3

EN

FAULT

GND1

2

J3

100mil Header

Battery Input

D1

RF MODULE CARRIER AREA

PROTOTYPE AREA

PROTOTYPE AREA

GND

R7

53.6kR953.6k

GND

Q1

R3
10k

BCD Charger

C10

0.1uF

GNDVCC

R8 DNP

GND

R16 DNP

GND

R20 DNP

GND

R28 DNP

GND

R29 DNP

VCC

R30 DNP

GND

R31 DNP

GND

C9

0.1uF

GND

R32 DNP

GND

R34 DNP

GND

R35 DNP

GND

R53 DNP

GND

R54 DNP

GND

R55 DNP

GND

R56 DNP

GND

C13
1uF

1
2
3
4
5
6
7

U8

VDC
RA5
RA4
MCLR
RC5
RC4
RC3

PIC16F1825-I/ST

VCC

R6
0 Ohm

C14
1uF

VCC

GND
SI
SCL
CSB
RS
RST

GND

10
11

12

1

2
3
4
5
6
7
8
9

ICSPDAT

ICSPCLK

LCD1

LED+

C1­C1+
VOUT
VCC
GND
SI
SCL
CSB
RS
RST

LED-

2x16 LCD

GND

RA2
RC0
RC1
RC2

VCC GND

R46

0 Ohm

R42

DNP

VCCP

PGM

CMD_DATA_IN

CSB RS

CMD_DATA_OUT

GND

Figure 47: Programming Dock Board Microcontroller Area Schematic

– – – –

36

14
13
12
11
10
9
8

PGD
PGC
RST
SCL
SI

Prototype Board Schematic

J3

2

100mil Header

Battery Input

1

2

U2

IN

GND

EN3FAULT

TPS2553

5VUSB

GND

EN

BCD Charger

Figure 48: Prototype Board Power Supply Area Schematic

Figure 49: Prototype Board RF Carrier Area Schematic

CONREVSMA001
ANT1

1

RF

GND

GND

X2
DNP

2-5

GND

X1

0 Ohm

GND1

OUT

ILIM

GND

X3
DNP

GND

D1

R5

10k

FAULT

SW3

5VUSB

U3

6

5

4

R7

FAULT

Q1

R3
10k

GND

0.47uF

53.6kR953.6k

C8

GND

1

Vin

VCC

2

GND

D2

R22

Vout

GND

3

5VUSB

330

POWER (GREEN)

OVER CURRENT (RED)

GND

GND

GND

6
89
10 11
12 13
14 15
16 17
18 19
20 21
22 23
24 25
26 27
28 29
30 31
32 33
34 35
36 37

23

45

67
89
10 11
12 13
14 15
16 17
18 19
20 21
22 23
24 25
26 27
28 29
30 31
32 33
34 35
36 37

J2
Carrier Interconnect Female

1

37

38
39
40
41
42
43
44
45
46

GND

GND

7

47
48
49
50
51
52
53
54
55
56

VCC

+

GND

C7
100uF

D3

R24
330

FAUL

38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56

GND

R24
330

5VUSB

D2

POWER (GREEN)

D3

OVER CURRENT (RED)

R22
330

VCC

FAULT

U2

R5

10k

GND

5VUSB

GND

+

C7
100uF

VCC

GND

Vin

1

GND

2

Vout

3

U3

C8

0.47uF

GND

FAULT

IN

1

GND

2

EN3FAULT

4

ILIM

5

OUT

6

TPS2553

SW3

5VUSB

EN

FAULT

GND1

2

J3

100mil Header

Battery Input

D1

USB AREA POWER SUPPLY AREA

RF MODULE CARRIER AREA

GND

R7

53.6kR953.6k

GND

Q1

R3
10k

BCD Charger

RF

1

23

45

67
89
10 11
12 13
14 15
16 17
18 19
20 21
22 23
24 25
26 27
28 29
30 31
32 33
34 35
36 37

38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56

J2
Carrier Interconnect Female

1

GND

2-5

ANT1

CONREVSMA001

GND

GND

GND

GND

GND

7
89
10 11
12 13
14 15
16 17
18 19
20 21
22 23
24 25
26 27
28 29
30 31
32 33
34 35
36 37

38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56

X1

0 Ohm

6

X3
DNP

GND

GND

X2
DNP

TP3

PROTOTYPE AREA

GNDVCC

GND

GND

GND

GND

GND

GND

GND

GND

GND

5VUSB

CMD_DATA_IN

SW1

3
12

U6

C2

0.1uF

+

C1

4.7uF

L1

600R/1.3A

9

TXD

RXD

1

4

TXD

RXD

VCC

3V3OUT

10

GND

J1 Micro USB

15

CMD_DATA_OUT

SW2

RTS

CTS

PWREN#

6

2

CTS

RTS

CBUS015CBUS114CBUS27CBUS3

VCCIO

USBDM9USBDP8RESET

R1 27

R2 27

1

2

3NC4

5

5V

DAT-

DAT+

GND

GSHD
GSHD

BCD Charger

16

11

C6

C5

C4

C3

6
7

Figure 50: Prototype Board USB Area Schematic

– – – –

38

GND
GND

0.1uF

47pF

47pF

0.01uF

FT230X

13

5

R4

C10

CTS
RTS
RXD
TXD

VCC

C9

GND

GND

0

GND

Figure 51: Prototype Board Prototype Area Schematic

GND

0.1uF

R32 DNP

323334

123456789

J4

100mil Header

4
3
2
1

J6

100mil Header

VCC BUS

0.1uF

1

TP4

J5

100mil Header

GND

GND

GND

R34 DNP

R35 DNP

R38 DNP

37

36

35

12345678910111213141516171819202122232425

789101112131415161718192021222324252627

6

R8 DNP

R6 0

R10 DNP

GND

GND

GND

GND

GND

GND

R42 DNP

R41 DNP

R40 DNP

R39 DNP

39404142434445

38

1011121314

R11 DNP

R14 DNP

R12 DNP

R13 DNP

VCC

VCC

GND

GND

VCC

GND

GND

GND

GND

R45 DNP

R44 DNP

R43 DNP

R16 DNP

R170

VCC

GND

GND

R15

DNP

39

R47 DNP

R48 DNP

R49 DNP

4647484950515253545556

123456789

J7 100mil Header

VCC BUS

R20 DNP

R19 DNP

GND

GND

R18

R21 DNP

GND

DNP

R23 DNP

GND

R53 DNP

R54 DNP

R55 DNP

R56 DNP

10

11

1

GND BUS

R52 DNP

R50 DNP

PROTOTYPE AREA

1

26

TP2

293031

28

R28 DNP

R29 DNP

R30 DNP

VCC

GND

VCC

R31 DNP

GND

GND GND

GND

GND

R26 DNP

Linx Technologies

159 Ort Lane

Merlin, OR, US 97532

Phone: [phone]

Fax: [phone]

www.linxtechnologies.com

Disclaimer

Linx Technologies is continually striving to improve the quality and function of its products. For this reason, we
reserve the right to make changes to our products without notice. The information contained in this Data Guide
is believed to be accurate as of the time of publication. Specifications are based on representative lot samples.
Values may vary from lot-to-lot and are not guaranteed. “Typical” parameters can and do vary over lots and
application. Linx Technologies makes no guarantee, warranty, or representation regarding the suitability of any
product for use in any specific application. It is the customer’s responsibility to verify the suitability of the part for
the intended application. NO LINX PRODUCT IS INTENDED FOR USE IN ANY APPLICATION WHERE THE SAFETY

OF LIFE OR PROPERTY IS AT RISK.

Linx Technologies DISCLAIMS ALL WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE. IN NO EVENT SHALL LINX TECHNOLOGIES BE LIABLE FOR ANY OF CUSTOMER’S INCIDENTAL OR
CONSEQUENTIAL DAMAGES ARISING IN ANY WAY FROM ANY DEFECTIVE OR NON-CONFORMING PRODUCTS
OR FOR ANY OTHER BREACH OF CONTRACT BY LINX TECHNOLOGIES. The limitations on Linx Technologies’

liability are applicable to any and all claims or theories of recovery asserted by Customer, including, without
limitation, breach of contract, breach of warranty, strict liability, or negligence. Customer assumes all liability
(including, without limitation, liability for injury to person or property, economic loss, or business interruption) for
all claims, including claims from third parties, arising from the use of the Products. The Customer will indemnify,
defend, protect, and hold harmless Linx Technologies and its officers, employees, subsidiaries, affiliates,
distributors, and representatives from and against all claims, damages, actions, suits, proceedings, demands,
assessments, adjustments, costs, and expenses incurred by Linx Technologies as a result of or arising from any
Products sold by Linx Technologies to Customer. Under no conditions will Linx Technologies be responsible for
losses arising from the use or failure of the device in any application, other than the repair, replacement, or refund
limited to the original product purchase price. Devices described in this publication may contain proprietary,
patented, or copyrighted techniques, components, or materials. Under no circumstances shall any user be
conveyed any license or right to the use or ownership of such items.

©2015 Linx Technologies. All rights reserved.

The stylized Linx logo, Wireless Made Simple, WiSE, CipherLinx and the stylized CL logo are trademarks of Linx Technologies.