TT Series
Master Development System
User's Guide
Table of Contents
1^
2^
2^
2^
3^
3^
3^
4^
4^
5^
5^
6^
7^
8^
10^
13^
20^
28^
29^
33^
37^
A large-print version of this document is available at
www.linxtechnologies.com.
Introduction
Ordering Information
TT Series Transceiver Carrier Board
TT Series Transceiver Carrier Board Objects
TT Series Transceiver Carrier Board Pin Assignments
Programming Dock
Programming Dock Objects
Remote Control Demo Board
Remote Control Demo Board Objects
Prototype Board
Prototype Board Objects
Initial Setup
Using the Programming Dock
Using the Remote Control Demo Board
Using the Prototype Board
The Development Kit Demonstration Software
Development Kit Demonstration Software Example
Carrier Board Schematic
Remote Control Demo Board Schematic
Programming Dock Board Schematic
Prototype Board Schematic
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 1/13/14
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
ANTENNA
1
2-5
GND
RESET
PDN
NC
PAIR
NC
LVL_ADJ
NC
NC
NC
NC
NC
NC
NC
NC
NC
6
8
10
12
14
16
18
20
22
24
26
28
30
32
34
36
7
9
11
13
15
17
19
21
23
25
27
29
31
33
35
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
GND (RF Connector)
MODE_IND
CMD_DATA_IN
LATCH_EN
ACK_EN
CMD_DATA_OUT
VCC
C0
C1
NC
RSSI
NC
NC
NC
NC
NC
NC
S0
S1
S2
S3
S4
S5
S6
S7
ACK_OUT
NC
NC
NC
NC
NC
NC
NC
NC
NC
NC
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 4: TT Series Transceiver Carrier Board Pin Assignments (Top View)
Programming Dock
2
4
Figure 2: Ordering Information
TT Series Transceiver Carrier Board
2
2
3
1
1
3
4
3
4
5
Top
Bottom
Figure 3: TT Series Transceiver Carrier Board
TT Series Transceiver Carrier Board Objects
1.
2.
3.
4.
TT Series Transceiver
MMCX RF Connector
Dual Row Header
Single Row Header
Figure 5: Programming Dock
Programming Dock Objects
1.
2.
3.
4.
5.
–2 –
Carrier Board Socket
RP-SMA Antenna Connector
MODE_IND LED
Micro USB Connector
LCD Display
– 3 –
Remote Control Demo Board
Prototype Board
2
4
6
2
3
2
5
4
1
4
1
1
5
5
6
3
3
6
7
8
1
10
11
7
8
8
11
7
12
11
Board A
Figure 6: Remote Control Demo Board
Figure 7: Prototype Board
Remote Control Demo Board Objects
1.
2.
3.
4.
5.
6.
7.
8.
9.
9
Board B
Carrier Board Socket
RP-SMA Antenna Connector
Power Switch
MODE_IND LED
CONFIRM LED
PAIR button
Status Line Output LEDs
Status Line Input Buttons
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
Using the Programming Dock
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.
Snap a Carrier Board onto the socket on the Programming Dock as shown
in Figure 8.
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.
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
–6 –
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.
– 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.
–8 –
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.
– 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.
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.
Figure 12 shows a convenient cross reference showing which lines on the
module connect to which lines on the prototype board.
1
Module to Prototype Board Pin Number Cross Reference
Pin Name
Module 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
7
Prototype Board Pin Number
10
6
2
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.
–12 –
– 13 –
8. The Status Details section shows the module’s control line states, radio
state and RSSI level.
The Advanced Configuration tab (Figure 16) offers more detailed
configuration options for the active module.
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.
1
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.
2
3
9
10
4
11
5
6
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.
12
7
13
1
2
3
Figure 14: The Master Development System
Software Module Identifiers
14
8
15
16
1. The type of module (TT Series)
17
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.
18
19
Figure 16: The Master Development System Software Advanced Configuration Tab
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.
Figure 15: The Master Development System
Software Additional Information
–14 –
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.
– 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.
The Command Set tab (Figure 17) allows specific commands to be written
to the module.
1
2
5
3
4
6
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.
Figure 17: The Master Development System Software Command Set Tab
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.
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.
–16 –
Figure 18: The Master Development System Software
Demo Command Set Tab Commands Menu
– 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.
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.
–18 –
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 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.
– 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 23: The Master Development System Software Pairing Modules
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.
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.
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 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).
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.
Figure 26: The Master Development System Software Advanced Configuration
–22 –
– 23 –
Figure 28: The Master Development System Software Demo and EZConfiguration Tab with Changes
Figure 30: The Master Development System Software Transmitting Module
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 31: The Master Development System Software Receiving Module
–24 –
– 25 –
Full system operation is demonstrated by clicking on the Sandbox tab
(Figure 32).
Figure 34: The Master Development System Software Save Profile
Once saved, the profile appears in the window, as shown in Figure 35.
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 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.
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 –
– 27 –
TR1
44
GND
S0
10
S1
GND
D0
D1
S2
D2
D3
S3
GND
12
S2
13
14
LVL_ADJ
15
LATCH_EN
D6
RESET
D5
D4
GND
16
17
18
S7
19
S6
D7
20
S4
21
RSSI
22
GND
VCC
P1
S3
21
22
GND
36
NC
35
NC
MODE_IND
34
NC
GND
33
ACK_EN
PAIR
MODE_IND
VCC
GND
R33
PAIR
0
S0
S1
32 MODE_IND
C1
C1
GND
S2
GND
CONFIRM
31
SW2
ACK_OUT
PAIR
30
LVL_ADJ
C0
C0
GND
GND
MODE_IND BLUE
D9
R42 10K
IDENTITY
BAUD_0
SEL_TIMER
D8
R41 10K
R34 10K
R38 10K
LATCH_EN
D_CFG
A_CGF_0
SEND
R37 10K
R35 10K
10K
R9
10K
R6
10K
VCC
36
S8 ACK_EN
PAIR
35
MODE_IND
34
PAIR
33
GND
PAIR
CRT_LRN
29
TRM-XXX-TT
R5
A_CFG_1
ACK_EN
38
32
C1
C1
CMD_DATA_OUT
R1
31
10K
CONFIRM
LVL_ADJ
28 ACK_OUT
GND
R36 GND
30
C0
C0
LATCH_EN
0
27
CMD_DATA_IN
CMD_DATA_IN
GND
29
CMD_DATA_OUT
CMD_DATA_OUT
RESET
26
D5
S5
28
GND
GND GND
GND
25
J2
VCC
VCC
27
S7
CMD_DATA_IN
1CMD_DATA_IN
24MCLR
PDN
POWER_DOWN
VCC
2
26
GNDS5
S6
3D5
23
GND
GND
PGD
4
25
S4
VCC
PGC
5 VCC
6
24
PDN
RSSI
POWER_DOWN
S3
CMD_DATA_OUT
Figure 36: TT Series Transceiver Carrier Board Module Schematic
PDN
GND
37
23
ANT
3
X2
GND
1
38
39
4
5
GND
1.8nH
40
DNP
6
7
MODE_IND
GND
41
8
9
RESET
CMD_DATA_IN
42
2
3
GND
LATCH_EN
10 GND
11
PDN
43
12 13
ACK_EN
44
4
5
GND
PAIR
14 GND
15
CMD_DATA_OUT
45
GND
GND
2
3
16 GND
17
VCC
6
7
MODE_IND 46 38
C08
18RESET
19
LVL_ADJ
47 39
9
CMD_DATA_IN
GND
GND
4
5
C110 11
20 PDN
21
LATCH_EN 48 40
226 23 7
49 41
GND
MODE_IND
12
13
ACK_EN
RSSI
248 PAIR
25 9
50 42
CMD_DATA_IN
14
15
CMD_DATA_OUT
261027 11
51 43
PDN
LATCH_EN
16
17
VCC
281229 13
52 44
ACK_EN
C0
18
19
LVL_ADJ
301431 15
53 45
PAIR
CMD_DATA_OUT
C1
20
21
321633 17
54 46
22VCC
23
341835 19
55 47
LVL_ADJ
C0 25
24
RSSI
362037 21
56 48
C1 27
26
49
22
23
SEND
28
29
J1
50
24
25
SER_I/O
31
Carrier Interconnect30
Male
ED_SEL
51
26
27
32 33
52
28
29
34 35
Figure 37: TT Series Carrier30
Board31
Header Schematic
53
36 37
54
32
33
J1
55
34
35
Carrier Interconnect Male
56
36
37
GND
GND
GND
Remote Control Demo Board Schematic
U2
VCC
D2
GND
D20
GND
R14
330
MCLR
CMD_DATA_OUT
CMD_DATA_IN
IDENTITY
1
2
3
4
5
6
7
VDD
RA5
RA4
MCLR
RC5
RC4
RC3
GND
ICSPDAT
ICSPCLK
RA2
RC0
RC1
RC2
PIC16F1824
D7
GND
GND
Figure 38: Remote Control Demo Board Microcontroller Area Schematic
–28 –
54
D855
D956
D_CFG
A_CFG_0
A_CFG_1
J1
RESTORE
S9
R27
330
S0
S1
S2
S3
S4
S5 38
S6 39
S7 40
CONFIRM
D041
D142
D243
D344
D445
D546
D647
D748
CONFIRM
49
IDENTITY
50
BAUD_0
51
SEL_TIMER
52
CRT_LRN
53
Note: The Remote Control
Demo boards
Carrier Interconnect
Female are designed to accept carrier
boards for multiple module families. Some circuitry is not applicable for
MICROCONTROLLER AREA
some modules.
GND
R3
330
GND
2
X1
GND
D1
GND
39
GND
NC
Header
11 4
GND
LVL_ADJ
12
S2
P2
LATCH_EN
13
S3 1
RESET 2
14
LVL_ADJ3
GND
Header
15 3
LATCH_EN
S7
VCC P3
16
RESET1
S6
2 17
GND 3
S4
18 3
GND S7Header
RSSI
19
S6
GND
20
S4
TRM-XXX-TT
R4 10K
R32 0
0
R8
8
1
9
S0 2
3
10
S1 4
RSSI
GND 40
NC
GND
ACK_EN
ACK_EN
MISC
CIRCUITS
7
S1
11
6
GND
NC
GND
37
NC
GND
41
NC
38
GND
NC
5
NC
9
NC
100uF
42
GND
GND
39
GND
1
NC
8
S0
4
NC
R2
330
1
7
C1
GND 0.47uF
3
GND
GND
43
C2 ANT
+
40 ANTENNA
CONREVSMA002
ANT1
1
RF
GND
NC
6
NC
GND
2-5
GND
GND
2
GND VCC
3
44
GND
Vout
41
RF MODULE AREA
VCC
CONFIRM
4
B1
5
GND
42
U1GND
Vin
NC
1
GND
GND
NC
TR1
1
2
SPDT
GND
3
ANT
POWER GREEN
ANTENNA
NC Board
SW1
Carrier
Schematic
RESTORE COMPLETE GREEN
43
CONFIRM RED
2
GND
GND
POWER SUPPLY AREA
ANT
GND
MODE_IND
1
GND
– 29 –
14
13
12
11
10
9
8
GND
PGD
PGC
SER_I/O
PIC A/B
MODE_IND
CRT_LRN
S0
S1
S2
S3
S4
S5
S6
S7
CONFIRM
REMOTE CONTROL AREA
RF MODULE AREA
D0
GND
R39 0 ohm
PIC A/B
ED_SEL
GND
R7
R12
330
DNP
SER_I/O
ED_SEL
D8
D9
D_CFG
A_CFG_0
A_CFG_1
D3
R10
10K
GND
D6
GND
R17
330
S1
GND
GND
R15
10K
GND
S2
GND
GND
GND
GND
VCC
VCC
S7
VCC
S6
VCC
S5
VCC
S4
VCC
D13
R20
10K
GND
GND
R19
10K
RF MODULE AREA
D4
SEND
D3
D12
GND
S3
GND
GND
D9
R16
10K
GND
R13
330
VCC
D6
X2
D16X1
GND
GND
R23
1.8nH
10K
DNP
D4
R11
10K
GND
MISC CIRCUITS
Figure 40: Remote Control Demo Board Power Supply Area Schematic
1
2
3
4
GND
VCC
R33
0
–30 –
VCC
GND
2
GND
1
P1
D0
D1
D2
D3
10K
R24
10K
R18
330
VCC
GND
D18
SEND
D7
D1
CONREVSMA002
R25
ANT1
330
1
RF
2-5
GND
1
POWER
AREA
VCC SUPPLY
GND
VDD
POWER GREEN
GND
R43
VCC
D11
GND
2
B1
RESTORE COMPLETE GREEN
GND
0 ohm
GND
D8
D14
14
GND
13
2
ICSPDAT
PGD
RA5
VCC
SW1
12
3
PGC
ICSPCLK
RA4
SPDT
11
4
VCC
MCLR U1
SER_I/O
RA2
MCLR
10
5
1
3 RC0
CMD_DATA_OUT
RC5
PIC A/B
Vin
Vout
9
6
CMD_DATA_IN
MODE_IND R2
RC1
RC4
7
8
R14
IDENTITY
CRT_LRN
RC3
RC2
330
+
C2
330
C1
PIC16F1824
100uF
0.47uF
R40
GND
D15
R21
330
U2
0 ohm
D17
R22
330
VCC
D10
MICROCONTROLLER AREA
RESTORE
S9
SEND
GND
J1
Carrier Interconnect Female
Figure 39: Remote Control Demo Board RF Carrier Area Schematic
0 ohm
R29
R26
330
SEND
LVL_ADJ
ED_SEL
SEND
PAIR
GND
MODE_IND
CMD_DATA_IN
LATCH_EN
ACK_EN
CMD_DATA_OUT
VCC
C0
C1
SEND
PIC A/B
D5
7
9
11
13
15
17
19
21
23
25
27
29
31
33
35
37
SEND
5
6
8
10
12
14
16
18
20
22
24
26
28
30
32
34
36
D0
D1
D2
D3
D4
D5
D6
D7
CONFIRM
IDENTITY
BAUD_0
SEL_TIMER
CRT_LRN
GND
R28
D19
SEND
4
GND
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
C1
D1
GND
PDN
GND
3
D2
1
2
GND
VCC
D5
GND
C0
GND
10K
S0
VCC
SEND
1.8nH
R31 0 ohm
C1
X2
X1
A Board
R30 0 ohm
C0
2-5
GND
B Board
D7
A Board
CONREVSMA002
ANT1
1
RF
3
GND
Figure 41: Remote Control
Demo Board4 Remote5 Control Area
Schematic
GND
GND
S8
PAIR
GND
PDN
6
8
10
7
9
11
MODE_IND
CMD_DATA_IN
LATCH_EN
– 31 –
38
39
40
41
42
43
D0
D1
D2
D3
D4
D5
DNP
GND
GND
1
R1
1 Ohm
VCC
R28
R30
R36
R32
R33
R34
R35
R38
10k
10k
1k
10k
10k
10k
10k
10k
GND
GND
GND
GND
VCC
GND
R9 10k
GND
GND
CRT_LRN
IDENTITY
GND
GND
GND
GND
GND
GND
GND
GND
10k
10k
10k
10k
10k
10k
10k
10k
D8
D9
D_CFG
A_CFG_0
A_CFG_1
GND
GND
7
9
11
13
15
17
19
21
23
25
27
29
31
33
35
37
10k
10k
10k
10k
10k
SER_I/O
R31
R26
R37
R39
R43
VCC
GND
GND
GND
GND
GND
GND
PAIR
R7 10k
R23 10k
R16 10k
R19 10k
VCC
GND
GND
GND
– 33 –
J2
Carrier Interconnect
R44 10k
R45 10k
VCC
VCC
GND
R25 10k
R27 10k
R29 10k
GND
VCC
CMD_DATA_OUT
R17 10k
R20 10k
GND
5
6
8
10
12
14
16
18
20
22
24
26
28
30
32
34
36
GND
PGD
PGC
SER_I/O
PIC A/B
MODE_IND
CRT_LRN
4
3
GND
Figure 43: Programming Dock Board RF Carrier Area Schematic
SN74AHC245
–32 –
14
13
12
11
10
9
8
GND
VCC
/IDENTITY
SER_I
CMD_DATA_OUT
CRT_LRN
CTS
R41
0 Ohm
20
19
18
17
16
15
14
13
12
11
SW1
VCC
OE
B1
B2
B3
B4
B5
B6
B7
B8
R40
0 Ohm
DIR
A1
A2
A3
A4
A5
A6
A7
A8
GND
GND
GND
ICSPDAT
ICSPCLK
RA2
RC0
RC1
RC2
VDD
RA5
RA4
MCLR
RC5
RC4
RC3
PIC16F1824
1nH
GND
D7
U2
GND
1
2
3
4
5
6
7
8
9
10
GNDC11
0.1uF
R14
330
X2
DNP
VCC
CMD_DATA_IN
SER_O
RTS
MODE_IND_MT
D20
X1
//IDENTITY
GND
1
2
3
4
5
6
7
MCLR
CMD_DATA_OUT
CMD_DATA_IN
IDENTITY
1
NC7WZ04
/IDENTITY
D2
RF
6
5
4
R27
330
ANT1
/A
VCC
/B
VCC
GND
VCC
GND
D0
D1
D2
D3
D4
D5
D6
D7
CONFIRM
IDENTITY
BAUD_0
SEL_TIMER
CRT_LRN
J1
Carrier Interconnect Female
RESTORE
S9
GND
C3
R3
0.1uF
330
D9
D8
A
GND
B
R42 10K
R41 10K
1
2
3
U7
CRT_LRN
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
MICROCONTROLLER AREA
X3
DNP
RESTORE COMPLETE GREEN
GND
VCC
MODE_IND
CMD_DATA_IN
LATCH_EN
ACK_EN
CMD_DATA_OUT
VCC
C0
C1
SEND
R10
R12
R13
R14
R15
R18
R21
R22
SER_I/O
ED_SEL
GND
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
GND
GND
R1
10K
CONFIRM
IDENTITY
BAUD_0
3
2
1
GND
VCC
IN
MAX4544EUT
R34 10K
SEL_TIMER
SEND
IDENTITY
GND
/IDENTITY
NC
COM
NO
R38 10K
4
5
6
R37 10K
LATCH_EN
R35 10K
D_CFG
10K
R9
10K
R6
LVL_ADJ
CONFIRM RED
MODE_IND BLUE
PAIR
R5 10K
GND
Figure 42: Remote Control Demo Board Miscellaneous Circuits
U6 Schematic
GND
PAIR
MCLR
1
U5
VCC
2
4
3GND
3
GND
NC
GND
5
2
VCC 4
COM
VCCPGD
6
1
5
//IDENTITY
NO
INPGC
6
MAX4544EUT
C10
0.1uF
GND
CRT_LRN
R24
10k
PDN
J2
SIGNAL ROUTING
SER_O
SER_I/O
SER_I
A_CGF_0
R4 10K
A_CFG_1
R32 0
ACK_EN
0
R8
PDN
GND
U1
PAIR
7
9
11
13
15
17
19
21
23
25
27
29
31
33
35
37
GND
MODE_IND
MODE_IND_MT
S2
6
8
10
12
14
16
18
20
22
24
26
28
30
32
34
36
C8
R36
0
Header 3
VCC
GND
CRT_LRN 100uF
GND
MODE_IND
GND
5
2
GND
1
2
3
D7
GND
C9
R11
0.47uF PAIR
53.6k
LVL_ADJ
MODE_IND BLUE
GND
R8
330
SW2
4
3
+
GND
C12
Header 3
0.1uF
VCC P3
VCC
D4
5
1
2
3
VCC
VinPAIR Vout
4
GND
FAULT
1
GND
ILIM
R33
0 6
GND
2-5 GND
D6
D5
D4
OUT
VCC
U4
LM3940IMP
3.3V
S8
2
3
EN
P2
PWREN#
VCCU
MODE_IND
CMD_DATA_IN
GND
RF MODULE CARRIER AREA
GNDDock Board
GND
2
3 Schematic
Programming
VCC
VCC
U3
1TPS2552
2
1 3
IN
4
2
Header
GND4
5VUSB
D0
D1
D2
D3
VCC
P1
1
MISC CIRCUITS
POWER SUPPLY AREA
MICROCONTROLLER AREA
USB AREA
POWER
POWER SUPPLY
SUPPLY AREA
AREA
U3
U3
TPS2552
TPS2552
VCCU
VCCU
GND
GND
R10 10k
10k
R10
GND
GND
R12
10k
CMD_DATA_IN
R12
10k
GND
GND
R13
10k
CMD_DATA_OUT
R13
10k
GND
GND
R14
10k
RTS
R14
10k
GND
GND
R15
10k
CTS
R15
10k
GND
GND
R18
10k
R18 10k
GND
15 R21 10k
GND
PWREN#
R21
10k
GND
14 R22 10k
GND
R22 10k
GND
7
GND
16
R9 10k
10k
R9
IDENTITY
IDENTITY
GND
GND
R28 10k
10k
R28
GND
D1R30 10k
GND
R30 10k
CRT_LRN
CRT_LRN
R36 1k
1k
R36
R32 10k
10k
R32
GND
GND
R33 10k
10k
R33
GND
GND
R34
10k
R5 R34 10k
GND
GND
R35
10k
330R35 10k
GND
GND
R38
10k
R38 10k
VCC
VCC
1
4
2
6
C12
C12
0.1uF
0.1uF
GND
GND
38
38
39TXD
39
40RXD
40
RTS#
41
41
CTS#
42
42
43
43
CBUS0
44
44
CBUS1
45
45
CBUS2
46
46
CBUS3
47
47
48
48
49
49
50
50
51
51
52
52
53
53
54
54
55
55
56
56
5VUSB
Figure 45: Programming Dock Board Signal Routing Schematic
– 35 –
GND
J2
J2
Carrier Interconnect
Interconnect
Carrier
GND
GND
GND
GND
SER_I/O
SER_I/O
R31 10k
10k
R31
R26 10k
10k
R26
R37 10k
10k
R37
R39 10k
10k
R39
R43 10k
10k
R43
GND
R4
0
GND
GND
R41
R41
Ohm
00 Ohm
GND
VCC
VCC
GND
GND
GND
GND
GND
GND
GND
GND
R7 10k
10k
R7
R23
10k
C5 10k
R23
47pF
C4
0.01uF
GND
GND
PAIR
PAIR
GND
GND
R16 10k
10k
R16
R19 10k
10k
R19
VCC
VCC
GND
GND
1
5V
R40 2
DAT-R40
3
Ohm
00 Ohm
DAT+
4
NC
5
GND
SW1
SW1
Figure 46: Programming Dock Board USB Area Schematic
–34 –
R44 10k
10k
R44
R45 10k
10k
R45
GND
GND
27
9
55
77 R2
99
11
11
13
13
R3
15
15
17
17
19
19
21C7
21
230.1uF
23
25
25
27
27
29
29
31
31
33
33
35
35
37
37
66
88
10
10
12
12
14
14
16
16
18
18
C6 20
20
47pF22
22
24
24
26
26
28
28
30
30
32
32
34
34
36
36
44
GND
GND
GND
GND
GND
GND
10
33
22
GND
GND
GND
L1
600R/1.3A
C2
0.1uF
C1
GND
GND
4.7uF
X3
X3
DNP
DNP
1nH
1nH
X1
X1
USBDM
R17 10k
10k
R17
GND
8
GND
R20 10k
10k
USBDP
R20
VCC
VCC
27
CMD_DATA_OUT
CMD_DATA_OUT
11
R25 10k
10k
RESET#
R25
VCC
VCC
R27 10k
10k
R27
VCC
VCC
R29 10k
10k
R29
GND
GND
3V3OUT
U2
FT230X
VCC
VCC
/IDENTITY
/IDENTITY
SER_I
SER_I
CMD_DATA_OUT
CMD_DATA_OUT
CRT_LRN
CRT_LRN
CTS
CTS
J1
Micro USB
SN74AHC245
SN74AHC245
20
20
19
19
18
18
17
17
16
16
15
15
14
14
13
13
12
12
11
11
VCC
VCC
VCC
VCC
OE
OE
B1
B1
B2
B2
B3
B3
B4
B4
B5
B5
B6
B6
B7
B7
B8
B8
GND
GND
DIR
DIR
A1
A1
A2
A2
A3
A3
A4
A4
A5
A5
A6
A6
A7
A7
A8
A8
GND
GND
GND
GND
11
22
33
44
55
66
77
88
99
10
10
X2
X2
DNP
DNP
VCC
VCC
CMD_DATA_IN
CMD_DATA_IN
SER_O
SER_O
RTS
RTS
MODE_IND_MT
MODE_IND_MT
RF
RF
GND
GND
GND
GND
U6
U6
11
R24
R24
10k
10k
ANT1
ANT1
CRT_LRN
CRT_LRN
+
PAIR
PAIR
PAIR
PAIR
GSHD
GSHD
0.1uF
0.1uF
NC7WZ04
NC7WZ04
7
6
VCC
VCC
5VUSB
11
U1
U1
GND
2-5
2-5 GND
MODE_IND BLUE
BLUE
MODE_IND
MODE_IND
MODE_IND
CMD_DATA_IN
CMD_DATA_IN
C14
1uF
2 GND
GND
C13
C1+
4
44
33
VOUT
SER_O
NC
GND
GND
SER_O
GND 25
GND
55 NC
2
VCC
VCC
COM
VCC
VCC
SER_I/O
COM
VCC
VCC 16
SER_I/O
66 C13
1
GND
GND
SER_I
NO
IN
CRT_LRN
SER_I
NO
IN
CRT_LRN
1uF
7
GND
GND
SI C3
SI
C3
8
MAX4544EUT
MAX4544EUT
SCL0.1uF
SCL
0.1uF
GND
9
CSB
CSB
10
RS
RS
VCC
VCC
11
VCC
VCC
GND
RST
RST
GND
U7
U7
12
66 LED11
/IDENTITY
IDENTITY
AA GND /A
/IDENTITY
/A
IDENTITY
55
22
S2
S2
GND
VCC
GND
GND
VCC
GND
33
442x16 LCD
/IDENTITY
//IDENTITY
BB
/B
/IDENTITY
//IDENTITY
/B
C11
C11
R8
R8
330
330
12
VCC
33
GND
GND
GND
GND
22
VCC
VCC
VCC
VCC
1
1
R6
//IDENTITY
IN
//IDENTITY
IN
0 Ohm
MAX4544EUT
MAX4544EUT
LCD1C10
C10
0.1uF
1
0.1uF
LED+
NC
NC
COM
COM
NO
NO
3
D4
D4
U5
U5
VCC
MODE_IND
MODE_IND
MODE_IND_MT
MODE_IND_MT
44
55
66
VCCIO
Figure 44: Programming Dock Board Power Supply Area Schematic
SIGNAL
SIGNAL ROUTING
ROUTING
R1
R1
Ohm
11 Ohm
GND
GND
GND
GND
CMD_DATA_OUT
CSB
5
13
DNP
VCC
VCC
661
2
553
4
445
6
7
GND
GND
IN
OUT
IN
OUT
VCCP
0 Ohm
22
GND
GND
ILIM
GND
GND
ILIM
PGM
33
PWREN#
EN
FAULT
PWREN#
EN
FAULT
CMD_DATA_IN
R42
22
R46
11
VCC
VCC
VCC
U4
U4
LM3940IMP
LM3940IMP 3.3V
3.3V
U8
11
1433
Vin
Vout
Vin
Vout
VDC
GND
GND
13
PGD
RA5
ICSPDAT
12 ++ C8
PGCC8
RA4
ICSPCLK
11
C9
C9
RST
MCLR
RA2
R11
100uF
R11
100uF
10
0.47uF
0.47uF
SCL
RC5
RC0
53.6k
53.6k
9
SI
RC4
RC1
8
RS
RC3
RC2
GND
GND
GND
GND
GND
GND
PIC16F1825-I/ST
GND
GND
TX/RX_IND ORANGE
5VUSB
5VUSB
RF
RF MODULE
MODULE CARRIER
CARRIER AREA
AREA
USB AREA
MICROCONTROLLER
AREA
POWER
SUPPLY
USB
AREA AREA
USB AREA
2R5 2 GND
GND
330
PWREN#
RESET#
11
27
R3
GND
VCC
D2
D2
R22
330
R22
330
5VUSB
GND
5VUSB
D3
D3
R24
330
R24
330
FAULT
FAULT
GND
C7
0.1uF
27
R2
VCC GND
VCC
3 +
C7
100uF
+
C7
100uF
GND
5VUSB
CURRENT
OVEROVER
CURRENT
(RED)(RED)
D1
15
14
7
16
CBUS0
CBUS1
CBUS2
CBUS3
USBDP
8
USBDM
9
10
Vout
GND
POWER
(GREEN)
POWER
(GREEN)
CMD_DATA_IN
CMD_DATA_OUT
RTS
CTS
1
TXD
4
FAULT
FAULT
RXD
2
RTS#
6
CTS#
3V3OUT
U2
FT230X
C6
47pF
C5
47pF
35
37
GND
35
37
GND
R4
0
53
7
95
117
139
15
11
17
13
19
15
21
17
23
19
25
21
27
23
29
25
31
27
33
29
35
31
37
33
1
5V
DATDAT+
NC
GND
– 37 –
J2
Carrier Interconnect Female
GND
J2
38
Carrier Interconnect Female
39
GND
GND
40
38
41
7
39
42
9 GND
40
43
11
41
7
44
13
42
9
45
15
43
11
46
17
44
13
47
19
45
15
48
21
46
17
49
23
47
19
50
25
48
21
51
27
49
23
52
29
50
25
53
31
51
27
54
33
52
29
55
35
53
31
56
37
54
33
C4
0.01uF
3
1
GND
L1
600R/1.3A
J1
Micro USB
GND GND
1
2
3
4
5
GND GND
R4
0
R4
0
Vin
GND
C2
0.1uF
2-5
C4
C3 C4
+
C5
VCC
3
Vout
RF MODULE CARRIER AREA
CONREVSMA001
X1
ANT1
1
CONREVSMA001
RF
X1
ANT1
GND
2
0 Ohm
1
RF
X2
X3
42
DNP
GND
0 Ohm DNP GND
X2
X3
6
6
DNP
DNP GND
8
84
GND
10
10
6
6
GND
GND
12
12
8
8
GND
14
14
10
10
GND
GND
16
16
12
12
18
18
14
14
20
20
16
16
22
22
18
18
24
24
20
20
26
26
22
22
28
28
24
24
30
30
26
26
32
32
28
28
34
34
30
30
36
36
32
32
34
34
36
Figure 49: Prototype Board RF Carrier Area Schematic 36
GND
GND
2-5
R2
27
R2
GND GND
11
C6 C6 11
RESET
RESET
0.1uF
0.1uF
0.01uF0.01uF 47pF 47pF 47pF 47pF
FT230X
FT230X
27
9
9
USBDM
USBDM
27
8
8
USBDP
USBDP
R1
27
R1
Q1
Figure 48: Prototype Board Power Supply Area Schematic
LED-
C3
7
6
J1 Micro
J1 Micro
USB USB
15V 1
5V
2
2
DAT- DAT3
3
DAT+
DAT+
4
4
NC
NC
5
5
GND
GND
7
6
GSHD
GSHD
GSHD
GSHD
+
Vin
U3
1
FAULT
10k
RF MODULE CARRIER AREA
C5
GND GND
5VUSB
15
CBUS0
CBUS0
14
CBUS1
CBUS1
7
CBUS2
CBUS2
16
CBUS3
CBUS3
1
1
TXD TXD 4 TXD TXD
4
RXD
RXD
RXD
2 RXD
2
RTS RTS 6 RTS RTS
6
CTS CTS
CTS CTS
U6 U6
10
10
3V3OUT
3V3OUT
12
3
12
3
+
C1 C1
L1
4.7uF 4.7uF
L1
600R/1.3A
600R/1.3A
Q1
GND
C1C1+
VOUT
VCC
GND
SI
SCL
CSB
RS
RST
C1
4.7uF
SW1 SW1
CMD_DATA_IN
CMD_DATA_IN
9
9
SW2 SW2
CMD_DATA_OUT
CMD_DATA_OUT
15
15
PWREN#
15
PWREN#
14
7
16
BCD Charger
BCD Charger
12
4
GSHD
GSHD
2
3
4
5
6
7
8
9
10
11
C8
0.47uF
C8
R7
R90.47uF
53.6k 53.6k GND
R7
R9
53.6k 53.6k GND
45
R3
10k
LED+
Figure 47: Programming Dock Board Microcontroller Area Schematic
5VUSB
5VUSB
EN FAULT
TPS2553
56
R3 GND
10k
GND
GND
2x16 LCD
–36 –
EN
GND FAULT
ILIM
LCD1
1
U3
1
7
6
GND
GND
VCC
VCCIO
VCC
VCCIO
GND
3
ILIM
OUT
BCD Charger
5
13
SI
SCL
CSB
RS
RST
32
GND
IN
BCD Charger
R6
0 Ohm
VCC
GND
21
OUT
FAULT
10k
R5
5VUSB
SW3
6
U2
IN
TPS2553
GND
GND
C2 C2
0.1uF 0.1uF
EN
5
13
GND
EN
GND
VCC
C14
1uF
C13
1uF
GND
5VUSB
1
12
CMD_DATA_OUT
PIC16F1825-I/ST
5VUSB
3
CSB
100mil Header
U2 Input
Battery
R5
5VUSB
SW3
VCC
DNP
GND
PGD
PGC
RST
SCL
SI
RS
D1
GND
VCCIO
R42
GND
ICSPDAT
ICSPCLK
RA2
RC0
RC1
RC2
100mil 1Header
Battery2Input
GND
GND
PGM
CMD_DATA_IN
VDC
RA5
RA4
MCLR
RC5
RC4
RC3
14
13
12
11
10
9
8
D1
GND
5
13
U8
1
2
3
4
5
6
7
VCCP
0 Ohm
1
J3
2
TX/RX_IND ORANGE
VCC
R46
POWER SUPPLY AREA
J3
Prototype
Board Schematic
55
56
38
39
40
38
41
39
42
40
43
41
44
42
45
43
46
44
47
45
48
46
49
47
50
48
51
49
52
50
53
51
54
52
55
53
56
54
55
56
PROTOTYPE AREA
POWER SUPPLY AREA
DNP
DNP
DNP
DNP
DNP
DNP
R47 DNP
R48 DNP
R49 DNP
GND
R50
R52
R53
R54
R55
R56
46
47
48
49
50
51
52
53
54
55
56
VCC BUS
TP3
5VUSB
GND
R22
330
OVER CURRENT (RED)
GND
D2
R24
330
FAULT
4
5
6
8
10
12
14
16
18
20
22
24
26
28
30
32
34
36
7
9
11
13
15
17
19
21
23
25
27
29
31
33
35
37
Figure 51: Prototype Board Prototype Area Schematic
– 39 –
DNP
DNP
DNP
DNP
R28
R29
R30
R31
GND
VCC
GND
GND
VCC
R26 DNP
GND
R19 DNP
R20 DNP
R21 DNP
DNP
DNP
DNP
DNP
DNP
R10
R11
R12
R13
R14
GND
DNP
R8
GND
0
R6
GND
R18 GND
DNP GND
GND
GND
R16 DNP
R17 0
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
6
8
10
12
14
16
18
20
22
24
26
28
30
32
34
36
1
3
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
TP2
2
1
2
3
4
5
6
7
8
9
10
11
12
13 1
14
15
16
17
18
19
20
21
22
23
24
25
26
TP4
2-5
GND
GND
GND
X3
DNP GND
0 Ohm
X2
DNP
J2
Carrier Interconnect Female
GND
38
39
GND
40
41
7
42
9
43
11
44
13
45
15
46
17
47
19
48
21
49
23
50
25
51
27
52
29
53
31
54
33
55
35
56
37
GND
0.1uF
GND
VCC
D3
RF MODULE CARRIER AREA
CONREVSMA001
X1
ANT1
1
RF
C9
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
1
GND
GND
VCC
R3
10k
C7
100uF
GND BUS
1
2
3
4
5
6
2
GND
7
8
9
10
11
R45 DNP
DNP
DNP
DNP
DNP
DNP
DNP
DNP
R38
R39
R40
R41
R42
R43
R44
J7 100mil Header
GND
GND
GND
GND
GND
GND
GND
GND
GND
GND
R34 DNP
R35 DNP
R32 DNP
32
33
34
35
36
37
38
39
40
FAULT41
42
43
44
45
GND
Q1
VCC
GND
VCC
GND
VCC
R15 GND
DNP
GND
VCC
GND
GND
0.01uF
R4
0
5V
DATDAT+
NC
GND
Figure 50: Prototype Board USB Area Schematic
–38 –
R9
53.6k
R23 DNP
11
C6
0.1uF
47pF
47pF
C5
C4
7
9
11
13
15
17
19
21
23
25
27
29
31
33
35
37
+
GND
J2
Carrier Interconnect Female
GND
38
39
GND
40
41
7
42
9
43
11
44
13
45
15
46
17
47
19
48
21
49
23
50
25
51
27
52
29
53
31
54
33
55
35
56
37
C3
27
R2
1
27
R1
6
8
10
12
14
16
18
20
22
24
26
28
30
32
34
36
5
1
2
3
4
5
GND
C2
0.1uF
GND
5VUSB
GND
6
8
10
12
14
16
18
20
22
24
26
28
30
32
34
36
J1 Micro USB
GND
C1
4.7uF
+
4
L1
600R/1.3A
GND
X3
DNP GND
3
GSHD
GSHD
2-5
2
R7
53.6k
TPS2553
Vout
GND
GND
7
6
GND
FAULT
FAULT
1
0 Ohm
X2
DNP
EN
VCC
3
C8
0.47uF
4
BCD Charger
D3
R24
330
ILIM
Vin
PROTOTYPE AREA
R22
330
GND
5
U3
1
POWER (GREEN)
D2
OUT
FAULT
10k
1
2
3
4
5
6
7
8
9
10
11
12
13
14
J4
100mil Header
5VUSB
RF MODULE CARRIER AREA
CONREVSMA001
X1
ANT1
1
RF
GND
0.1uF
VCC
GND
RESET
USBDP
USBDM
9
8
12
3
U6
3V3OUT
VCC
VCCIO
10
GND
GND
VCC
GND
GND
GND
GND
6
IN
J6
100mil Header
GND
3
J5
100mil Header
1
TXD
4
RXD
2
RTS
6
CTS
R3
10k
GND
2
VCC BUS
Q1
BCD Charger
C7
100uF
EN
OVER CURRENT (RED)
R9
53.6k
PWREN#
TPS2553
BCD Charger
R7
53.6k
5VUSB
+
1
R5
5VUSB
SW3
U2
3
2
C8
0.47uF
4
FAULT
Vout
D1
GND
100mil Header
Battery Input
VCC
Vin
FT230X
POWER (GREEN)
5
1
2
GND
C10
U3
CBUS0
CBUS1
CBUS2
CBUS3
EN
SW2
ILIM
SW1
GND
FAULT
10k
1
6
15
14
7
16
3
OUT
FAULT
TXD
RXD
RTS
CTS
EN
2
IN
SW3
5
13
GND
1
R5
5VUSB
GND
U2
5VUSB
CMD_DATA_OUT
15
CMD_DATA_IN
9
100mil Header
Battery Input
J3
TXD
RXD
RTS
CTS
D1
GND
1
2
3
4
1
2
GND
GND
GND
GND
J3
GND
GND
GND
GND
GND
POWER SUPPLY AREA
USB AREA
Linx Technologies
159 Ort Lane
Merlin, OR, US 97532
3090 Sterling Circle, Suite 200
Boulder, CO 80301
Phone: +1 541 471 6256
Fax: +1 541 471 6251
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 Customer’s responsibility to verify the suitability of the part for the
intended application. At Customer’s request, Linx Technologies may provide advice and assistance in designing
systems and remote control devices that employ Linx Technologies RF products, but responsibility for the ultimate
design and use of any such systems and devices remains entirely with Customer and/or user of the RF products.
LINX TECHNOLOGIES DISCLAIMS ANY AND ALL WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
PARTICULAR PURPOSE. IN NO EVENT SHALL LINX TECHNOLOGIES BE LIABLE FOR ANY CUSTOMER’S OR
USER’S INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF OR RELATED TO THE DESIGN OR USE
OF A REMOTE CONTROL SYSTEM OR DEVICE EMPLOYING LINX TECHNOLOGIES RF PRODUCTS OR FOR ANY
OTHER BREACH OF CONTRACT BY LINX TECHNOLOGIES. CUSTOMER AND/OR USER ASSUME ALL RISKS
OF DEATH, BODILY INJURIES, OR PROPERTY DAMAGE ARISING OUT OF OR RELATED TO THE USE OF LINX
TECHNOLOGIES RF PRODUCTS, INCLUDING WITH RESPECT TO ANY SERVICES PROVIDED BY LINX RELATED
TO THE USE OF LINX TECHNOLOGIES RF PRODUCTS. LINX TECHNOLOGIES SHALL NOT BE LIABLE UNDER ANY
CIRCUMSTANCES FOR A CUSTOMER’S, USER’S, OR OTHER PERSON’S DEATH, BODILY INJURY, OR PROPERTY
DAMAGE ARISING OUT OF OR RELATED TO THE DESIGN OR USE OF A REMOTE CONTROL SYSTEM OR DEVICE
EMPLOYING LINX TECHNOLOGIES RF PRODUCTS.
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.
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.
All rights reserved. ©2013 Linx Technologies
The stylized Linx logo, Wireless Made Simple, CipherLinx, WiSE and the stylized CL logo are trademarks of Linx Technologies.
工商网监
湘ICP备2023018690号
