Upload
others
View
7
Download
0
Embed Size (px)
Citation preview
HumRCTM Series Master Development System
User's Guide
Table of Contents 1 Introduction 2 Ordering Information 3 HumRCTM Series Transceiver Carrier Board 3 HumRCTM Series Transceiver Carrier Board Objects 3 HumRCTM Series Transceiver Carrier Board Pin Assignments 4 Programming Dock 4 Programming Dock Objects 5 Remote Control Demo Board 5 Remote Control Demo Board Objects 6 Prototype Board 6 Prototype Board Objects 7 Initial Setup 8 Using the Programming Dock 9 Using the Remote Control Demo Board 11 Using the Prototype Board 14 The Development Kit Demonstration Software 23 Development Kit Demonstration Software Example 31 Carrier Board Schematic 32 Remote Control Demo Board Schematic 36 Programming Dock Board Schematic 40 Prototype Board Schematic 43 Notes
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”).
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.
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.
!
– –1
IntroductionThe Linx HumRCTM 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 module into an end product. The boards serve several important functions:
• Rapid Module Evaluation: The boards allow the performance of the Linx HumRC™ 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 HumRC™ Series transceivers*, antennas, batteries and full documentation.
* One part is soldered to each Carrier Board
HumRCTM Master Development System
User's Guide
Figure 1: HumRCTM Series Master Development System
Revised 8/30/2017
– – – –2 3
HumRCTM Series Transceiver Carrier Board Objects1. HumRCTM Series Transceiver2. MMCX RF Connector3. Dual Row Header4. Single Row Header
HumRCTM Series Transceiver Carrier BoardOrdering Information
Figure 2: Ordering Information
Figure 3: HumRCTM Series Transceiver Carrier Board
1
2
3 4
HumRCTM Series Transceiver Carrier Board Pin Assignments
Figure 4: HumRCTM Series Transceiver Carrier Board Pin Assignments (Top View)
7 MODE_IND9 CMD_DATA_IN11 LATCH_EN13 ACK_EN15 CMD_DATA_OUT17 VCC19 C021 C123 NC25 NC27 NC29 NC31 NC33 NC35 NC37 NC
GND 6RESET 8
PDN 10NC 12
PAIR 14LNA_EN 16
LVL_ADJ 18PA_EN 20
NC 22NC 24NC 26NC 28NC 30NC 32NC 34NC 36
41 S342 S443 S544 S645 S746 ACK_OUT47 NC48 NC49 NC50 NC51 NC52 NC53 NC54 NC55 NC56 NC
40 S239 S138 S0
ANTENNA 1 2-5 GND (RF Connector)
Ordering Information
Part Number Description
EVAL-***-RC HumRCTM Series Basic Evaluation Kit
MDEV-***-RC HumRCTM Series Master Development System
HUM-***-RC HumRCTM Series Remote Control Transceiver
HUM-900-RC-UFL HumRCTM Series Remote Control Transceiver, Certified, UFL Connector
HUM-900-RC-CAS HumRCTM Series Remote Control Transceiver, Certified, Castella-tion Connection
EVM-***-RC HumRCTM Series Carrier Board
EVM-900-RC-UFL HumRCTM Series Carrier Board with Certified module, UFL Con-nector
EVM-900-RC-CAS HumRCTM Series Carrier Board with Certified module, Castellation Connection
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
*** = Frequency; 900MHz, 2.4GHz
– – – –4 5
1
Remote Control Demo Board
Board BBoard A
Remote Control Demo Board Objects1. Carrier Board Socket2. RP-SMA Antenna Connector3. Power Switch4. MODE_IND LED5. CONFIRM LED6. PAIR button7. Status Line Output LEDs8. Status Line Input Buttons9. 4 AAA Batteries (Not shown, on the back of the boards)
Figure 6: Remote Control Demo Board
1
2
34
5
67
8
1
2
34
5
67
8
Programming Dock
Programming Dock Objects1. Carrier Board Socket2. RP-SMA Antenna Connector3. MODE_IND LED4. Micro USB Connector5. LCD Display
Figure 5: Programming Dock
2
3
4
5
1
– – – –6 7
Prototype Board
Prototype Board Objects1. Carrier Board Socket2. RP-SMA Antenna Connector3. Micro USB Connector4. Power Switch5. Power LED6. External Battery Connection7. Prototyping Area8. 3.3V Supply Bus9. Ground Bus10. USB Interface Lines11. Module Interface Headers12. Command Data Interface Routing Switches (on back)
Figure 7: Prototype Board
4
1
23
10
6
7
8
11
5
9
11
11
12
Initial SetupThere are several boards that are included with the Development System. The Carrier Boards have a HumRCTM 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 Programming Docks that 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.
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 HumRCTM 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.
There are two Prototype Boards that 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.
The development software supports Windows 7 and 10; with Java 1.6 or later.
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
!
– – – –8 9
Using the Programming DockSnap a Carrier Board onto the socket on the Programming Dock as shown in Figure 8.
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 HumRCTM 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.
Figure 8: Programming Dock with a Carrier Board
Using the Remote Control Demo BoardSnap a Carrier Board onto the socket on each Remote Control Demo Board as shown in Figure 9.
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.
Figure 9: Remote Control Demo Board with a Carrier Board
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.
– – – –10 11
Range TestingSeveral 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.
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.
Using the Prototype BoardSnap a Carrier Board onto the socket on the Prototype Board as shown in Figure 10.
Place the power switch into the “USB” position then connect a micro USB cable into the connector at the top of the board. Plug the other end into a PC or any USB charger. 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 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. The overload condition is reset once the excess current draw is removed.
Figure 10: Prototype Board with a Carrier Board
– – – –12 13
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.
Figure 11 shows the bottom of the board.
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.
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: Prototype Board Bottom Side
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 HumRCTM Series uses both resistors to create a voltage divider that determines the output power level. Please see the HumRCTM data guide for more details on this.
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 30 7
RESET 22 8
CMD_DATA_IN 27 9
POWER_DOWN 12 10
LATCH_EN 13 11
ACK_EN 28 13
PAIR 29 14
CMD_DATA_OUT 26 15
VCC 21 17
LVL_ADJ 32 18
C0 10 19
C1 11 21
S0 8 38
S1 7 39
S2 6 40
S3 5 41
S4 4 42
S5 3 43
S6 2 44
S7 1 45
ACK_OUT 31 46
Figure 12: Module to Prototype Board Pin Number Cross Reference
– – – –14 15
The Development Kit Demonstration SoftwareThe 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. 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.
7
4
1
2
3
106
8
11
5
9
Figure 13: The Master Development System Software Demo and EZConfiguration Tab
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.
1. The type of module (HumRC™ 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 14: The Master Development System Software Module Identifiers
12 3
Figure 15: The Master Development System Software Additional Information
– – – –16 17
The Advanced Configuration tab (Figure 16) offers more detailed configuration options for the active module.
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.
Figure 16: The Master Development System Software Advanced Configuration Tab
7
4
123
10
6
8
115
9
12
13
14
1617
18
15
19 20
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. If the Respond to Request Remote Sample is enabled, the module automatically responds to the request with a packet than contains the values determined by the MType field in the received packet.
15. 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.
16. The Duty Cycle configuration sets the interval and Keep on times for automatically cycling power to the receiver.
17. The Module Identity box displays the module type, firmware version and serial number of the active module.
18. The Read All button reads all of the current configurations from the active module.
– – – –18 19
19. The Submit button writes all changes to the active module.
20. 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. 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.
4
1
2 3
6
5
Figure 17: The Master Development System Software Command Set Tab
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.
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 HumRC™ Series Transceiver Command Data Interface Reference Guide for definitions of each value.
Figure 19: The Master Development System Software Demo Command Set Tab Items Menu
Figure 18: The Master Development System Software Demo Command Set Tab Commands Menu
– – – –20 21
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.
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.
Figure 20: The Master Development System Software Sandbox Tab
The RC Configuration tab (Figure 21) allows configuration of the module’s advanced remote control features.
1. The Analog Inputs Source area configures which lines are analog inputs, the number of readings to average, the reference voltage and the offset for each channel.
2. The Custom Data Source menu sets the source of custom data transmitted with each IU message.
3. The Trigger Operation area configures which lines are triggered inputs, their type of control, session duration and transmit interval.
4. The NV Memory Cycles show how many times data has been written to the module’s non-volatile memory. The module is capable of approximately 1,000 writes to NV memory before it wears out. This count gives an indication of how many more times the module can be written.
5. The Analog Input Readings show the current analog measurements.6. The Trigger Input Status shows the current states of the trigger lines.
Figure 21: The Master Development System Software RC Configuration Tab
7
4
1
2
3
10
6
8
11
5
9 12
– – – –22 23
7. The Pairing Status area shows the current status of any pairing operations.
8. The request Remote Sample configures the module to request a response from a remote unit. This area configures the type of sample that should be in the response and the address of the unit that should respond.
9. The Read All button reads all of the current configurations from the active module.
10. The Submit button writes all changes to the active module.
11. The Set Defaults button restores the active module to factory default conditions.
12. The Commit button writes any changed configurations to non-volatile memory. The changes should be written to the module using the Submit button first, then the Commit button is used to make the changes permanent.
Development Kit Demonstration Software ExampleThis example shows how to configure two modules to work with each other. The software defaults to the Demo & EZConfiguration tab when opened (Figure 22).
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 23.
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 24.
Figure 22: The Master Development System Software Demo and EZConfiguration Tab
Figure 23: The Master Development System Software Connected Modules
– – – –24 25
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 25 the Permissions are inactive since the active module only has inputs and no outputs to control.
Figure 25: The Master Development System Software Paired Modules
Figure 24: The Master Development System Software Pairing Modules
Changing the active module is accomplished by dragging a module from the Available list to the Active spot, as shown in Figure 26.
With the new module active, drag the original module to the Given Permissions window. Click on the Advanced Configuration tab (Figure 27).
Figure 26: The Master Development System Software Changing the Active Module
Figure 27: The Master Development System Software Advanced Configuration
– – – –26 27
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 28 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.
This configuration changes the module to have all outputs. This is shown by clicking on the Demo & EZConfiguration tab Figure 29.
Figure 28: The Master Development System Software Advanced Configuration with Changes
The buttons have all changed to LEDs. The symbol next to each LED indicates if it is latching or momentary (Figure 30). S0 is latching, the rest are momentary.
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 31 shows the transmitter, Figure 32 shows the receiver.
Figure 29: The Master Development System Software Demo and EZConfiguration Tab with Changes
Figure 30: The Master Development System Software Latching (1) and Momentary (2) Symbols
1 2
– – – –28 29
Figure 31: The Master Development System Software Transmitting Module
Figure 32: The Master Development System Software Receiving Module
Full system operation is demonstrated by clicking on the Sandbox tab (Figure 33).
These configurations can be saved as a profile for recalling or programming into other modules. The Demo & EZConfiguration tab has the profile window (Figure 34).
Clicking the Save Current button brings up a prompt asking for a name of the profile (Figure 35).
Figure 33: The Master Development System Software Sandbox
Figure 34: The Master Development System Software Saved Profiles Window
– – – –30 31
Once saved, the profile appears in the window, as shown in Figure 36.
To apply a profile, select it from a list and click the Program button. Clicking the Remove button removes it from the list.
Figure 35: The Master Development System Software Save Profile
Figure 36: The Master Development System Software with a Saved Profile
S7
38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56
AC
K_O
UT
S0
S1
S2
S3
S4
S5
S6
S7
PA
IR
MO
DE
_IN
D
LAT
CH
_EN
AC
K_E
N
RE
SE
TP
DN
LAD
J
CM
D_D
AT
A_I
N
CM
D_D
AT
A_O
UT
LNA
_EN
PAIR
PA_EN
RESET PDN
LAD
J
LNA_EN
MO
DE
_IN
D
LATCH_EN
ACK_EN
AC
K_O
UT
S0
S1
S2
S3
S4
S5
S6
S7
C0
C1
C0
C1
1
23
45
67
89
1011
1213
1415
1617
1819
2021
2223
2425
2627
2829
3031
3233
3435
3637
J1 Car
rier
Inte
rcon
nect
CMD_DATA_OUT
CMD_DATA_IN
X1
X2
GN
D
GN
D
GN
D
GN
D
GN
D
GN
D
GN
D
GN
D
GN
D
GN
D
GN
D
GN
D
GN
D
GN
D
VC
C
VC
C
PA
_EN
GN
D17
VCC21
GN
D18
RESET22
LNA_EN23
PA_EN24
CMD_DATA_OUT26
CMD_DATA_IN27
ACK_EN28
PAIR29
S6
2
GND25
1
MO
DE
_IN
D30
AC
K_O
UT
31
LVL_
AD
J32
S5
3
S4
4
AN
T19
GN
D20
S35
S26
S17
S08
C010
C111
POWER_DOWN12
LATCH_EN13
GND9
GN
D16
GN
D15
GN
D14
TR
1X
3
GN
D
5.3n
H
0 oh
m
1.2p
F
X2
X3
X1
2.4G
Hz
900M
Hz
DN
P
DN
P
DN
P
Figure 37: HumRCTM Series Transceiver Carrier Board Module Schematic
Carrier Board Schematic
– – – –32 33
Remote Control Demo Board Schematic
123
P2
Header 3
D4D5D6
1234
P1
Header 4
D0D1D2D3
GND
R2330
VCC
D1
PO
WE
R G
RE
EN
MO
DE
_IN
D
GND
R3330
D2
MO
DE
_IN
D B
LUE
CO
NF
IRM
GND
R27330
D20
CO
NF
IRM
RE
D
RF1
GN
D2-
5
ANT1CONREVSMA002
PAIR
MODE_IND
CONFIRM
LATCH_EN
D0D1D2D3D4D5
ACK_ENPDN
CMD_DATA_IN
CMD_DATA_OUTD6D7
SER_I/O
C0C1SEND
CRT_LRN
GND
GND
VCC
GND GND
GND
GND
12 3
4 5
6 78 910 1112 1314 1516 1718 1920 2122 2324 2526 2728 2930 3132 3334 3536 37
38394041424344454647484950515253545556
J1Carrier Interconnect Female
LVL_ADJ IDENTITY
GND
X2
DNP
X1
1.8nH
ED_SEL
SEL_TIMER
D8D9D_CFGA_CFG_0A_CFG_1
BAUD_0
GND
SW1SPDT
GND
VCC
B1
GND
Vin1
GN
D2
Vout3
U1
C10.47uF
GND
+ C2
100uF
VDD1
RA52
RA43
MCLR4
RC55
RC46
RC37
RC28
RC19
RC010
RA211
ICSPCLK12
ICSPDAT13
GND14
U2
PIC16F1824
VCC GNDPGDPGC
MCLR
CMD_DATA_INCMD_DATA_OUT
IDENTITY CRT_LRNMODE_IND
GND
SER_I/O
R14330
GND
S9RESTORE
D7
RE
ST
OR
E C
OM
PLE
TE
GR
EE
N
PIC A/B
R360
R330
VCC
GND
SW2
LVL_ADJ
AC
K_E
NR
320
VCC
R34
10K
GND
BA
UD
_0
IDE
NT
ITY
SE
L_T
IME
R
SE
ND
LAT
CH
_EN
PD
NR
80
R38
10K
R37
10K
R35
10K
R9
10K
D8
D9
R41
10K
R42
10K
D_C
FG
A_C
GF
_0
A_C
FG
_1
R6
10K
R5
10K
R4
10K
GND
VCC
S8PAIR
R110K
PAIR CRT_LRN
REMOTE CONTROL AREAPOWER SUPPLY AREA
RF MODULE AREA
MISC CIRCUITS
MICROCONTROLLER AREA
123
P3
Header 3
D7
VCC
GND 1234
J2
MCLR
PGD56
PGC
VCCGND
VCCS0
D0
SE
ND
D5
R12330
D3
R1010K
GND
GND
VCCS1
D1
SE
ND
R17330
R1510K
GND
GND
D10
D8
VCCS2
D2
SE
ND
R21330
R1910K
GND
GND
D14
D12
VCCS3
D3
SE
ND
R25330
R2310K
GND
GND
D18
D16
VCCS4
D4
SE
ND
R13330
R1110K
GND
GND
D6
D4
VCCS5
D5
SE
ND
R18330
R1610K
GND
GND
D11
D9
VCCS6
D6
SE
ND
R22330
R2010K
GND
GND
D15
D13
VCCS7
D7
SE
ND
R26330
R2410K
GND
GND
D19
D17
C0
C1 GND
VCCR30 0 ohm
R31 0 ohm
ED_SELR7 10K
R39 0 ohm GND
GND
PIC A/B
C0
C1
R28 0 ohm GND
VCCR29 0 ohm
R40 0 ohm VCC
ED_SELR43 10K
VCC
PIC A/B
A Board B Board A Board
Figure 38: Remote Control Demo Board Microcontroller Area 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.
123
P2
Header 3
D4D5D6
1234
P1
Header 4
D0D1D2D3
GND
R2330
VCC
D1
PO
WE
R G
RE
EN
MO
DE
_IN
D
GND
R3330
D2
MO
DE
_IN
D B
LUE
CO
NF
IRM
GND
R27330
D20
CO
NF
IRM
RE
D
RF1
GN
D2-
5
ANT1CONREVSMA002
PAIR
MODE_IND
CONFIRM
LATCH_EN
D0D1D2D3D4D5
ACK_ENPDN
CMD_DATA_IN
CMD_DATA_OUTD6D7
SER_I/O
C0C1SEND
CRT_LRN
GND
GND
VCC
GND GND
GND
GND
12 3
4 5
6 78 910 1112 1314 1516 1718 1920 2122 2324 2526 2728 2930 3132 3334 3536 37
38394041424344454647484950515253545556
J1Carrier Interconnect Female
LVL_ADJ IDENTITY
GND
X2
DNP
X1
1.8nH
ED_SEL
SEL_TIMER
D8D9D_CFGA_CFG_0A_CFG_1
BAUD_0
GND
SW1SPDT
GND
VCC
B1
GND
Vin1
GN
D2
Vout3
U1
C10.47uF
GND
+ C2
100uF
VDD1
RA52
RA43
MCLR4
RC55
RC46
RC37
RC28
RC19
RC010
RA211
ICSPCLK12
ICSPDAT13
GND14
U2
PIC16F1824
VCC GNDPGDPGC
MCLR
CMD_DATA_INCMD_DATA_OUT
IDENTITY CRT_LRNMODE_IND
GND
SER_I/O
R14330
GND
S9RESTORE
D7
RE
ST
OR
E C
OM
PLE
TE
GR
EE
N
PIC A/B
R360
R330
VCC
GND
SW2
LVL_ADJ
AC
K_E
NR
320
VCC
R34
10K
GND
BA
UD
_0
IDE
NT
ITY
SE
L_T
IME
R
SE
ND
LAT
CH
_EN
PD
NR
80
R38
10K
R37
10K
R35
10K
R9
10K
D8
D9
R41
10K
R42
10K
D_C
FG
A_C
GF
_0
A_C
FG
_1
R6
10K
R5
10K
R4
10K
GND
VCC
S8PAIR
R110K
PAIR CRT_LRN
REMOTE CONTROL AREAPOWER SUPPLY AREA
RF MODULE AREA
MISC CIRCUITS
MICROCONTROLLER AREA
123
P3
Header 3
D7
VCC
GND 1234
J2
MCLR
PGD56
PGC
VCCGND
VCCS0
D0
SE
ND
D5
R12330
D3
R1010K
GND
GND
VCCS1
D1
SE
ND
R17330
R1510K
GND
GND
D10
D8
VCCS2
D2
SE
ND
R21330
R1910K
GND
GND
D14
D12
VCCS3
D3
SE
ND
R25330
R2310K
GND
GND
D18
D16
VCCS4
D4
SE
ND
R13330
R1110K
GND
GND
D6
D4
VCCS5
D5
SE
ND
R18330
R1610K
GND
GND
D11
D9
VCCS6
D6
SE
ND
R22330
R2010K
GND
GND
D15
D13
VCCS7
D7
SE
ND
R26330
R2410K
GND
GND
D19
D17
C0
C1 GND
VCCR30 0 ohm
R31 0 ohm
ED_SELR7 10K
R39 0 ohm GND
GND
PIC A/B
C0
C1
R28 0 ohm GND
VCCR29 0 ohm
R40 0 ohm VCC
ED_SELR43 10K
VCC
PIC A/B
A Board B Board A Board
Figure 39: Remote Control Demo Board Power Supply Area Schematic
123
P2
Header 3
D4D5D6
1234
P1
Header 4
D0D1D2D3
GND
R2330
VCC
D1
PO
WE
R G
RE
EN
MO
DE
_IN
D
GND
R3330
D2
MO
DE
_IN
D B
LUE
CO
NF
IRM
GND
R27330
D20
CO
NF
IRM
RE
D
RF1
GN
D2-
5
ANT1CONREVSMA002
PAIR
MODE_IND
CONFIRM
LATCH_EN
D0D1D2D3D4D5
ACK_ENPDN
CMD_DATA_IN
CMD_DATA_OUTD6D7
SER_I/O
C0C1SEND
CRT_LRN
GND
GND
VCC
GND GND
GND
GND
12 3
4 5
6 78 910 1112 1314 1516 1718 1920 2122 2324 2526 2728 2930 3132 3334 3536 37
38394041424344454647484950515253545556
J1Carrier Interconnect Female
LVL_ADJ IDENTITY
GND
X2
DNP
X1
1.8nH
ED_SEL
SEL_TIMER
D8D9D_CFGA_CFG_0A_CFG_1
BAUD_0
GND
SW1SPDT
GND
VCC
B1
GND
Vin1
GN
D2
Vout3
U1
C10.47uF
GND
+ C2
100uF
VDD1
RA52
RA43
MCLR4
RC55
RC46
RC37
RC28
RC19
RC010
RA211
ICSPCLK12
ICSPDAT13
GND14
U2
PIC16F1824
VCC GNDPGDPGC
MCLR
CMD_DATA_INCMD_DATA_OUT
IDENTITY CRT_LRNMODE_IND
GND
SER_I/O
R14330
GND
S9RESTORE
D7
RE
ST
OR
E C
OM
PLE
TE
GR
EE
N
PIC A/B
R360
R330
VCC
GND
SW2
LVL_ADJ
AC
K_E
NR
320
VCC
R34
10K
GND
BA
UD
_0
IDE
NT
ITY
SE
L_T
IME
R
SE
ND
LAT
CH
_EN
PD
NR
80
R38
10K
R37
10K
R35
10K
R9
10K
D8
D9
R41
10K
R42
10K
D_C
FG
A_C
GF
_0
A_C
FG
_1
R6
10K
R5
10K
R4
10K
GND
VCC
S8PAIR
R110K
PAIR CRT_LRN
REMOTE CONTROL AREAPOWER SUPPLY AREA
RF MODULE AREA
MISC CIRCUITS
MICROCONTROLLER AREA
123
P3
Header 3
D7
VCC
GND 1234
J2
MCLR
PGD56
PGC
VCCGND
VCCS0
D0
SE
ND
D5
R12330
D3
R1010K
GND
GND
VCCS1
D1
SE
ND
R17330
R1510K
GND
GND
D10
D8
VCCS2
D2
SE
ND
R21330
R1910K
GND
GND
D14
D12
VCCS3
D3
SE
ND
R25330
R2310K
GND
GND
D18
D16
VCCS4
D4
SE
ND
R13330
R1110K
GND
GND
D6
D4
VCCS5
D5
SE
ND
R18330
R1610K
GND
GND
D11
D9
VCCS6
D6
SE
ND
R22330
R2010K
GND
GND
D15
D13
VCCS7
D7
SE
ND
R26330
R2410K
GND
GND
D19
D17
C0
C1 GND
VCCR30 0 ohm
R31 0 ohm
ED_SELR7 10K
R39 0 ohm GND
GND
PIC A/B
C0
C1
R28 0 ohm GND
VCCR29 0 ohm
R40 0 ohm VCC
ED_SELR43 10K
VCC
PIC A/B
A Board B Board A Board
Figure 40: Remote Control Demo Board RF Carrier Area Schematic
– – – –34 35
123
P2
Header 3
D4D5D6
1234
P1
Header 4
D0D1D2D3
GND
R2330
VCC
D1
PO
WE
R G
RE
EN
MO
DE
_IN
D
GND
R3330
D2
MO
DE
_IN
D B
LUE
CO
NF
IRM
GND
R27330
D20
CO
NF
IRM
RE
D
RF1
GN
D2-
5
ANT1CONREVSMA002
PAIR
MODE_IND
CONFIRM
LATCH_EN
D0D1D2D3D4D5
ACK_ENPDN
CMD_DATA_IN
CMD_DATA_OUTD6D7
SER_I/O
C0C1SEND
CRT_LRN
GND
GND
VCC
GND GND
GND
GND
12 3
4 5
6 78 910 1112 1314 1516 1718 1920 2122 2324 2526 2728 2930 3132 3334 3536 37
38394041424344454647484950515253545556
J1Carrier Interconnect Female
LVL_ADJ IDENTITY
GND
X2
DNP
X1
1.8nH
ED_SEL
SEL_TIMER
D8D9D_CFGA_CFG_0A_CFG_1
BAUD_0
GND
SW1SPDT
GND
VCC
B1
GND
Vin1
GN
D2
Vout3
U1
C10.47uF
GND
+ C2
100uF
VDD1
RA52
RA43
MCLR4
RC55
RC46
RC37
RC28
RC19
RC010
RA211
ICSPCLK12
ICSPDAT13
GND14
U2
PIC16F1824
VCC GNDPGDPGC
MCLR
CMD_DATA_INCMD_DATA_OUT
IDENTITY CRT_LRNMODE_IND
GND
SER_I/O
R14330
GND
S9RESTORE
D7
RE
ST
OR
E C
OM
PLE
TE
GR
EE
N
PIC A/B
R360
R330
VCC
GND
SW2
LVL_ADJ
AC
K_E
NR
320
VCC
R34
10K
GND
BA
UD
_0
IDE
NT
ITY
SE
L_T
IME
R
SE
ND
LAT
CH
_EN
PD
NR
80
R38
10K
R37
10K
R35
10K
R9
10K
D8
D9
R41
10K
R42
10K
D_C
FG
A_C
GF
_0
A_C
FG
_1
R6
10K
R5
10K
R4
10K
GND
VCC
S8PAIR
R110K
PAIR CRT_LRN
REMOTE CONTROL AREAPOWER SUPPLY AREA
RF MODULE AREA
MISC CIRCUITS
MICROCONTROLLER AREA
123
P3
Header 3
D7
VCC
GND 1234
J2
MCLR
PGD56
PGC
VCCGND
VCCS0
D0
SE
ND
D5
R12330
D3
R1010K
GND
GND
VCCS1
D1
SE
ND
R17330
R1510K
GND
GND
D10
D8
VCCS2
D2
SE
ND
R21330
R1910K
GND
GND
D14
D12
VCCS3
D3
SE
ND
R25330
R2310K
GND
GND
D18
D16
VCCS4
D4
SE
ND
R13330
R1110K
GND
GND
D6
D4
VCCS5
D5
SE
ND
R18330
R1610K
GND
GND
D11
D9
VCCS6D
6
SE
ND
R22330
R2010K
GND
GND
D15
D13
VCCS7
D7
SE
ND
R26330
R2410K
GND
GND
D19
D17
C0
C1 GND
VCCR30 0 ohm
R31 0 ohm
ED_SELR7 10K
R39 0 ohm GND
GND
PIC A/B
C0
C1
R28 0 ohm GND
VCCR29 0 ohm
R40 0 ohm VCC
ED_SELR43 10K
VCC
PIC A/B
A Board B Board A Board
Figure 41: Remote Control Demo Board Remote Control Area Schematic
123
P2
Header 3
D4D5D6
1234
P1
Header 4
D0D1D2D3
GND
R2330
VCC
D1
PO
WE
R G
RE
EN
MO
DE
_IN
D
GND
R3330
D2
MO
DE
_IN
D B
LUE
CO
NF
IRM
GND
R27330
D20
CO
NF
IRM
RE
D
RF1
GN
D2-
5
ANT1CONREVSMA002
PAIR
MODE_IND
CONFIRM
LATCH_EN
D0D1D2D3D4D5
ACK_ENPDN
CMD_DATA_IN
CMD_DATA_OUTD6D7
SER_I/O
C0C1SEND
CRT_LRN
GND
GND
VCC
GND GND
GND
GND
12 3
4 5
6 78 910 1112 1314 1516 1718 1920 2122 2324 2526 2728 2930 3132 3334 3536 37
38394041424344454647484950515253545556
J1Carrier Interconnect Female
LVL_ADJ IDENTITY
GND
X2
DNP
X1
1.8nH
ED_SEL
SEL_TIMER
D8D9D_CFGA_CFG_0A_CFG_1
BAUD_0
GND
SW1SPDT
GND
VCC
B1
GND
Vin1
GN
D2
Vout3
U1
C10.47uF
GND
+ C2
100uF
VDD1
RA52
RA43
MCLR4
RC55
RC46
RC37
RC28
RC19
RC010
RA211
ICSPCLK12
ICSPDAT13
GND14
U2
PIC16F1824
VCC GNDPGDPGC
MCLR
CMD_DATA_INCMD_DATA_OUT
IDENTITY CRT_LRNMODE_IND
GND
SER_I/O
R14330
GND
S9RESTORE
D7
RE
ST
OR
E C
OM
PLE
TE
GR
EE
N
PIC A/B
R360
R330
VCC
GND
SW2
LVL_ADJ
AC
K_E
NR
320
VCC
R34
10K
GND
BA
UD
_0
IDE
NT
ITY
SE
L_T
IME
R
SE
ND
LAT
CH
_EN
PD
NR
80
R38
10K
R37
10K
R35
10K
R9
10K
D8
D9
R41
10K
R42
10K
D_C
FG
A_C
GF
_0
A_C
FG
_1
R6
10K
R5
10K
R4
10K
GND
VCC
S8PAIR
R110K
PAIR CRT_LRN
REMOTE CONTROL AREAPOWER SUPPLY AREA
RF MODULE AREA
MISC CIRCUITS
MICROCONTROLLER AREA
123
P3
Header 3
D7
VCC
GND 1234
J2
MCLR
PGD56
PGC
VCCGND
VCCS0
D0
SE
ND
D5
R12330
D3
R1010K
GND
GND
VCCS1D
1
SE
ND
R17330
R1510K
GND
GND
D10
D8
VCCS2
D2
SE
ND
R21330
R1910K
GND
GND
D14
D12
VCCS3
D3
SE
ND
R25330
R2310K
GND
GND
D18
D16
VCCS4
D4
SE
ND
R13330
R1110K
GND
GND
D6
D4
VCCS5
D5
SE
ND
R18330
R1610K
GND
GND
D11
D9
VCCS6
D6
SE
ND
R22330
R2010K
GND
GND
D15
D13
VCCS7
D7
SE
ND
R26330
R2410K
GND
GND
D19
D17
C0
C1 GND
VCCR30 0 ohm
R31 0 ohm
ED_SELR7 10K
R39 0 ohm GND
GND
PIC A/B
C0
C1
R28 0 ohm GND
VCCR29 0 ohm
R40 0 ohm VCC
ED_SELR43 10K
VCC
PIC A/B
A Board B Board A Board
Figure 42: Remote Control Demo Board Miscellaneous Circuits Schematic
– – – –36 37
GND
+ C8
100uF
VCC
GND
Vin1
GN
D2
Vout 3
U4LM3940IMP 3.3V
C90.47uF
GND
IN1
GND2
EN3 FAULT 4
ILIM 5
OUT 6
U3TPS2552
GND
5VUSB
GND
R1153.6kPWREN#
USB AREA POWER SUPPLY AREA RF MODULE CARRIER AREA
SIGNAL ROUTING
U8
VDC1
RA52
RA43
MCLR4
RC55
RC46
RC37 RC2 8RC1 9RC0 10RA2 11ICSPCLK 12ICSPDAT 13GND 14
PIC16F1825-I/ST
VCC GND
PGM
CSB RSSISCLRSTPGCPGD
R42 DNP
VCCP
VCC
RS
SISCL
RST
CSB
VCC
GND
GNDC131uF
GND
C141uF C1-2
C1+3
VOUT4
VCC5
GND6
SI7
SCL8
CSB9
RS10
LED+1
LED-12
RST11
LCD1
2x16 LCD
R60 Ohm
MICROCONTROLLER AREA
D2
GN
D
GN
D
+C
14.
7uF
C4
0.01
uF
L1 600R
/1.3
A
GN
D
C6
47pF
R4
0
C2
0.1u
F
VCC12
VCCIO3
3V3O
UT
10
GND 5
GND 13
US
BD
M9
US
BD
P8
RE
SE
T#11
TXD
1
RX
D4
RTS
#2
CTS
#6
CB
US
015
CB
US
114
CB
US
27
CB
US
316
U2
FT23
0X
C5
47pF
PW
RE
N#
C7
0.1u
F
GN
D
5V1
DA
T-
2
DA
T+3
NC
4
GSHD 6GSHD 7
GN
D5
J1 Mic
ro U
SB
5VU
SB
RTS
R2
27
R3
27
TXD
RX
D
nCTS
VC
C R20
10k
R47
DN
P
GP
IO2
RX
TXLE
D
D1
R5330 ohm
OR
AN
GE
RX
TXLE
D
VCC
R1710k
GND
NC1
IN2
GND3 OUT 4
VCC 5U5 VCC
GND
R49 DNPBuffer Bypass DNP
RTS nCMD
CMD_DATA_OUTRXD
NC1
IN2
GND3 OUT 4
VCC 5U1 VCC
GND
R4610k
VCC
R48 DNPCMD_DATA_INTXD
Buffer Bypass DNP
GND
MO
DE
_IN
D
R8330 ohm
D4
MO
DE
_IN
D B
LUE
R2410k
S2
VCC
PA
IR
PAIR
GND
R410 ohm
R400 ohm
VCC
GND
SW1
LADJ
R36DNP
R23DNP
GPIO1
RXD
GND
nPDN
R9
10k
GN
D
38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56
GN
DG
ND
GN
DG
ND
GN
DG
ND
GN
DG
ND
GN
DG
ND
GN
D
GN
DG
ND
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
GN
DR
3810
kV
CC
R16
10k
VC
C
VC
C R1
1 O
hm
MODE_INDCMD_DATA_IN
CM
D_D
ATA
_OU
T
GN
D
GN
D
GN
DG
ND
GN
D
1
23
45
67
89
1011
1213
1415
1617
1819
2021
2223
2425
2627
2829
3031
3233
3435
3637
J2 Car
rier I
nter
conn
ectR29
10k
GN
D
GN
DV
CC
VC
CR
2710
kR
2510
k
R19
10k
R31
10k
VC
C
PA
IR
GN
DR
2610
kG
ND
R37
10k
GN
DR
3910
kG
ND
R43
10k
R44
10k
GN
DR
4510
kG
ND
RF
1
GND 2-5
AN
T1
GN
DG
ND
X1
1nH
X3
DN
P
GN
DX2
DN
P
LAD
J
nPD
NnC
MD
nCTS
CMD_DATA_IN
GP
IO1
GP
IO2
GP
IO1
Figure 43: Programming Dock Board RF Carrier Area Schematic
Programming Dock Board Schematic
GND
+ C8
100uF
VCC
GND
Vin1
GN
D2
Vout 3
U4LM3940IMP 3.3V
C90.47uF
GND
IN1
GND2
EN3 FAULT 4
ILIM 5
OUT 6
U3TPS2552
GND
5VUSB
GND
R1153.6kPWREN#
USB AREA POWER SUPPLY AREA RF MODULE CARRIER AREA
SIGNAL ROUTING
U8
VDC1
RA52
RA43
MCLR4
RC55
RC46
RC37 RC2 8RC1 9RC0 10RA2 11ICSPCLK 12ICSPDAT 13GND 14
PIC16F1825-I/ST
VCC GND
PGM
CSB RSSISCLRSTPGCPGD
R42 DNP
VCCP
VCC
RS
SISCL
RST
CSB
VCC
GND
GNDC131uF
GND
C141uF C1-2
C1+3
VOUT4
VCC5
GND6
SI7
SCL8
CSB9
RS10
LED+1
LED-12
RST11
LCD1
2x16 LCD
R60 Ohm
MICROCONTROLLER AREA
D2
GN
D
GN
D
+C
14.
7uF
C4
0.01
uF
L1 600R
/1.3
A
GN
D
C6
47pF
R4
0
C2
0.1u
F
VCC12
VCCIO3
3V3O
UT
10
GND 5
GND 13
US
BD
M9
US
BD
P8
RE
SE
T#11
TXD
1
RX
D4
RTS
#2
CTS
#6
CB
US
015
CB
US
114
CB
US
27
CB
US
316
U2
FT23
0X
C5
47pF
PW
RE
N#
C7
0.1u
F
GN
D
5V1
DA
T-
2
DA
T+3
NC
4
GSHD 6GSHD 7
GN
D5
J1 Mic
ro U
SB
5VU
SB
RTS
R2
27
R3
27
TXD
RX
D
nCTS
VC
C R20
10k
R47
DN
P
GP
IO2
RX
TXLE
D
D1
R5330 ohm
OR
AN
GE
RX
TXLE
D
VCC
R1710k
GND
NC1
IN2
GND3 OUT 4
VCC 5U5 VCC
GND
R49 DNPBuffer Bypass DNP
RTS nCMD
CMD_DATA_OUTRXD
NC1
IN2
GND3 OUT 4
VCC 5U1 VCC
GND
R4610k
VCC
R48 DNPCMD_DATA_INTXD
Buffer Bypass DNP
GND
MO
DE
_IN
D
R8330 ohm
D4
MO
DE
_IN
D B
LUE
R2410k
S2
VCC
PA
IR
PAIR
GND
R410 ohm
R400 ohm
VCC
GND
SW1
LADJ
R36DNP
R23DNP
GPIO1
RXD
GND
nPDN
R9
10k
GN
D
38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56
GN
DG
ND
GN
DG
ND
GN
DG
ND
GN
DG
ND
GN
DG
ND
GN
D
GN
DG
ND
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
GN
DR
3810
kV
CC
R16
10k
VC
C
VC
C R1
1 O
hm
MODE_INDCMD_DATA_IN
CM
D_D
ATA
_OU
T
GN
D
GN
D
GN
DG
ND
GN
D
1
23
45
67
89
1011
1213
1415
1617
1819
2021
2223
2425
2627
2829
3031
3233
3435
3637
J2 Car
rier I
nter
conn
ectR29
10k
GN
D
GN
DV
CC
VC
CR
2710
kR
2510
k
R19
10k
R31
10k
VC
C
PA
IR
GN
DR
2610
kG
ND
R37
10k
GN
DR
3910
kG
ND
R43
10k
R44
10k
GN
DR
4510
kG
ND
RF
1
GND 2-5
AN
T1
GN
DG
ND
X1
1nH
X3
DN
P
GN
DX2
DN
P
LAD
J
nPD
NnC
MD
nCTS
CMD_DATA_IN
GP
IO1
GP
IO2
GP
IO1
Figure 44: Programming Dock Board Power Supply Area Schematic
GND
+ C8
100uF
VCC
GND
Vin1
GN
D2
Vout 3
U4LM3940IMP 3.3V
C90.47uF
GND
IN1
GND2
EN3 FAULT 4
ILIM 5
OUT 6
U3TPS2552
GND
5VUSB
GND
R1153.6kPWREN#
USB AREA POWER SUPPLY AREA RF MODULE CARRIER AREA
SIGNAL ROUTING
U8
VDC1
RA52
RA43
MCLR4
RC55
RC46
RC37 RC2 8RC1 9RC0 10RA2 11ICSPCLK 12ICSPDAT 13GND 14
PIC16F1825-I/ST
VCC GND
PGM
CSB RSSISCLRSTPGCPGD
R42 DNP
VCCP
VCC
RS
SISCL
RST
CSB
VCC
GND
GNDC131uF
GND
C141uF C1-2
C1+3
VOUT4
VCC5
GND6
SI7
SCL8
CSB9
RS10
LED+1
LED-12
RST11
LCD1
2x16 LCD
R60 Ohm
MICROCONTROLLER AREA
D2
GN
D
GN
D
+C
14.
7uF
C4
0.01
uF
L1 600R
/1.3
A
GN
D
C6
47pF
R4
0
C2
0.1u
F
VCC12
VCCIO3
3V3O
UT
10
GND 5
GND 13
US
BD
M9
US
BD
P8
RE
SE
T#11
TXD
1
RX
D4
RTS
#2
CTS
#6
CB
US
015
CB
US
114
CB
US
27
CB
US
316
U2
FT23
0X
C5
47pF
PW
RE
N#
C7
0.1u
F
GN
D
5V1
DA
T-
2
DA
T+3
NC
4
GSHD 6GSHD 7
GN
D5
J1 Mic
ro U
SB
5VU
SB
RTS
R2
27
R3
27
TXD
RX
D
nCTS
VC
C R20
10k
R47
DN
P
GP
IO2
RX
TXLE
D
D1
R5330 ohm
OR
AN
GE
RX
TXLE
D
VCC
R1710k
GND
NC1
IN2
GND3 OUT 4
VCC 5U5 VCC
GND
R49 DNPBuffer Bypass DNP
RTS nCMD
CMD_DATA_OUTRXD
NC1
IN2
GND3 OUT 4
VCC 5U1 VCC
GND
R4610k
VCC
R48 DNPCMD_DATA_INTXD
Buffer Bypass DNP
GND
MO
DE
_IN
D
R8330 ohm
D4
MO
DE
_IN
D B
LUE
R2410k
S2
VCC
PA
IR
PAIR
GND
R410 ohm
R400 ohm
VCC
GND
SW1
LADJ
R36DNP
R23DNP
GPIO1
RXD
GND
nPDN
R9
10k
GN
D
38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56
GN
DG
ND
GN
DG
ND
GN
DG
ND
GN
DG
ND
GN
DG
ND
GN
D
GN
DG
ND
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
GN
DR
3810
kV
CC
R16
10k
VC
C
VC
C R1
1 O
hm
MODE_INDCMD_DATA_IN
CM
D_D
ATA
_OU
T
GN
D
GN
D
GN
DG
ND
GN
D
1
23
45
67
89
1011
1213
1415
1617
1819
2021
2223
2425
2627
2829
3031
3233
3435
3637
J2 Car
rier I
nter
conn
ectR29
10k
GN
D
GN
DV
CC
VC
CR
2710
kR
2510
k
R19
10k
R31
10k
VC
C
PA
IR
GN
DR
2610
kG
ND
R37
10k
GN
DR
3910
kG
ND
R43
10k
R44
10k
GN
DR
4510
kG
ND
RF
1
GND 2-5
AN
T1
GN
DG
ND
X1
1nH
X3
DN
P
GN
DX2
DN
P
LAD
J
nPD
NnC
MD
nCTS
CMD_DATA_IN
GP
IO1
GP
IO2
GP
IO1
Figure 45: Programming Dock Board Signal Routing Schematic
– – – –38 39
GND
+ C8
100uF
VCC
GND
Vin1
GN
D2
Vout 3
U4LM3940IMP 3.3V
C90.47uF
GND
IN1
GND2
EN3 FAULT 4
ILIM 5
OUT 6
U3TPS2552
GND
5VUSB
GND
R1153.6kPWREN#
USB AREA POWER SUPPLY AREA RF MODULE CARRIER AREA
SIGNAL ROUTING
U8
VDC1
RA52
RA43
MCLR4
RC55
RC46
RC37 RC2 8RC1 9RC0 10RA2 11ICSPCLK 12ICSPDAT 13GND 14
PIC16F1825-I/ST
VCC GND
PGM
CSB RSSISCLRSTPGCPGD
R42 DNP
VCCP
VCC
RS
SISCL
RST
CSB
VCC
GND
GNDC131uF
GND
C141uF C1-2
C1+3
VOUT4
VCC5
GND6
SI7
SCL8
CSB9
RS10
LED+1
LED-12
RST11
LCD1
2x16 LCD
R60 Ohm
MICROCONTROLLER AREA
D2
GN
D
GN
D
+C
14.
7uF
C4
0.01
uF
L1 600R
/1.3
A
GN
D
C6
47pF
R4
0
C2
0.1u
F
VCC12
VCCIO3
3V3O
UT
10
GND 5
GND 13
US
BD
M9
US
BD
P8
RE
SE
T#11
TXD
1
RX
D4
RTS
#2
CTS
#6
CB
US
015
CB
US
114
CB
US
27
CB
US
316
U2
FT23
0X
C5
47pF
PW
RE
N#
C7
0.1u
F
GN
D
5V1
DA
T-
2
DA
T+3
NC
4
GSHD 6GSHD 7
GN
D5
J1 Mic
ro U
SB
5VU
SB
RTS
R2
27
R3
27
TXD
RX
D
nCTS
VC
C R20
10k
R47
DN
P
GP
IO2
RX
TXLE
D
D1
R5330 ohm
OR
AN
GE
RX
TXLE
D
VCC
R1710k
GND
NC1
IN2
GND3 OUT 4
VCC 5U5 VCC
GND
R49 DNPBuffer Bypass DNP
RTS nCMD
CMD_DATA_OUTRXD
NC1
IN2
GND3 OUT 4
VCC 5U1 VCC
GND
R4610k
VCC
R48 DNPCMD_DATA_INTXD
Buffer Bypass DNP
GND
MO
DE
_IN
D
R8330 ohm
D4
MO
DE
_IN
D B
LUE
R2410k
S2
VCC
PA
IR
PAIR
GND
R410 ohm
R400 ohm
VCC
GND
SW1
LADJ
R36DNP
R23DNP
GPIO1
RXD
GND
nPDN
R9
10k
GN
D
38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56
GN
DG
ND
GN
DG
ND
GN
DG
ND
GN
DG
ND
GN
DG
ND
GN
D
GN
DG
ND
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
GN
DR
3810
kV
CC
R16
10k
VC
C
VC
C R1
1 O
hm
MODE_INDCMD_DATA_IN
CM
D_D
ATA
_OU
T
GN
D
GN
D
GN
DG
ND
GN
D
1
23
45
67
89
1011
1213
1415
1617
1819
2021
2223
2425
2627
2829
3031
3233
3435
3637
J2 Car
rier I
nter
conn
ectR29
10k
GN
D
GN
DV
CC
VC
CR
2710
kR
2510
k
R19
10k
R31
10k
VC
C
PA
IR
GN
DR
2610
kG
ND
R37
10k
GN
DR
3910
kG
ND
R43
10k
R44
10k
GN
DR
4510
kG
ND
RF
1
GND 2-5
AN
T1
GN
DG
ND
X1
1nH
X3
DN
P
GN
DX2
DN
P
LAD
J
nPD
NnC
MD
nCTS
CMD_DATA_IN
GP
IO1
GP
IO2
GP
IO1
Figure 46: Programming Dock Board USB Area Schematic
GND
+ C8
100uF
VCC
GND
Vin1
GN
D2
Vout 3
U4LM3940IMP 3.3V
C90.47uF
GND
IN1
GND2
EN3 FAULT 4
ILIM 5
OUT 6
U3TPS2552
GND
5VUSB
GND
R1153.6kPWREN#
USB AREA POWER SUPPLY AREA RF MODULE CARRIER AREA
SIGNAL ROUTING
U8
VDC1
RA52
RA43
MCLR4
RC55
RC46
RC37 RC2 8RC1 9RC0 10RA2 11ICSPCLK 12ICSPDAT 13GND 14
PIC16F1825-I/ST
VCC GND
PGM
CSB RSSISCLRSTPGCPGD
R42 DNP
VCCP
VCC
RS
SISCL
RST
CSB
VCC
GND
GNDC131uF
GND
C141uF C1-2
C1+3
VOUT4
VCC5
GND6
SI7
SCL8
CSB9
RS10
LED+1
LED-12
RST11
LCD1
2x16 LCD
R60 Ohm
MICROCONTROLLER AREA
D2
GN
D
GN
D
+C
14.
7uF
C4
0.01
uF
L1 600R
/1.3
A
GN
D
C6
47pF
R4
0
C2
0.1u
F
VCC12
VCCIO3
3V3O
UT
10
GND 5
GND 13
US
BD
M9
US
BD
P8
RE
SE
T#11
TXD
1
RX
D4
RTS
#2
CTS
#6
CB
US
015
CB
US
114
CB
US
27
CB
US
316
U2
FT23
0X
C5
47pF
PW
RE
N#
C7
0.1u
F
GN
D
5V1
DA
T-
2
DA
T+3
NC
4
GSHD 6GSHD 7
GN
D5
J1 Mic
ro U
SB
5VU
SB
RTS
R2
27
R3
27
TXD
RX
D
nCTS
VC
C R20
10k
R47
DN
P
GP
IO2
RX
TXLE
D
D1
R5330 ohm
OR
AN
GE
RX
TXLE
D
VCC
R1710k
GND
NC1
IN2
GND3 OUT 4
VCC 5U5 VCC
GND
R49 DNPBuffer Bypass DNP
RTS nCMD
CMD_DATA_OUTRXD
NC1
IN2
GND3 OUT 4
VCC 5U1 VCC
GND
R4610k
VCC
R48 DNPCMD_DATA_INTXD
Buffer Bypass DNP
GND
MO
DE
_IN
D
R8330 ohm
D4
MO
DE
_IN
D B
LUE
R2410k
S2
VCC
PA
IR
PAIR
GND
R410 ohm
R400 ohm
VCC
GND
SW1
LADJ
R36DNP
R23DNP
GPIO1
RXD
GND
nPDN
R9
10k
GN
D
38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56
GN
DG
ND
GN
DG
ND
GN
DG
ND
GN
DG
ND
GN
DG
ND
GN
D
GN
DG
ND
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
GN
DR
3810
kV
CC
R16
10k
VC
C
VC
C R1
1 O
hm
MODE_INDCMD_DATA_IN
CM
D_D
ATA
_OU
T
GN
D
GN
D
GN
DG
ND
GN
D
1
23
45
67
89
1011
1213
1415
1617
1819
2021
2223
2425
2627
2829
3031
3233
3435
3637
J2 Car
rier I
nter
conn
ectR29
10k
GN
D
GN
DV
CC
VC
CR
2710
kR
2510
k
R19
10k
R31
10k
VC
C
PA
IR
GN
DR
2610
kG
ND
R37
10k
GN
DR
3910
kG
ND
R43
10k
R44
10k
GN
DR
4510
kG
ND
RF
1
GND 2-5
AN
T1
GN
DG
ND
X1
1nH
X3
DN
P
GN
DX2
DN
P
LAD
J
nPD
NnC
MD
nCTS
CMD_DATA_IN
GP
IO1
GP
IO2
GP
IO1
Figure 47: Programming Dock Board Microcontroller Area Schematic
– – – –40 41
GN
D
OU
TIN
GND
GND
+
C7
10uF
THERM
4
123
U5
THERM
RF
12 3
4 5
6 78 910 1112 1314 1516 1718 1920 2122 2324 2526 2728 2930 3132 3334 3536 37
38394041424344454647484950515253545556
J2Carrier Interconnect Female
1
GN
D2-
5
ANT1CONREVSMA001
GND
GND
GND
GND
GND
78 910 1112 1314 1516 1718 1920 2122 2324 2526 2728 2930 3132 3334 3536 37
38394041424344454647484950515253545556
X1
0 Ohm
6
X3DNP
GNDGND
X2DNP
GND
R24330
5VUSB
D2
PO
WE
R (G
RE
EN
)
D3
OV
ER
CU
RR
EN
T (R
ED
)
R22330
VCC
FAULT
U2
R5
10k
GND
5VUSB
GND
C80.47uF
FAU
LT
IN1
GND2
EN3 FAULT 4
ILIM 5
OUT 6
TPS2553
SW3
5VUSB
EN
FAULT
GND12
J3
100mil HeaderBattery Input
D1
GND
R753.6k
R953.6k
GND
Q1
R310k
BCD Charger
VCC
+
GND
GND
C14.7uF
C3
0.01uF
L1600R/1.3A
GND
C5
47pF
R40
C20.1uF
VC
C12
VC
CIO
3
3V3OUT10
GN
D5
GN
D13
USBDM9
USBDP8
RESET11
TXD 1
RXD 4
RTS 2
CTS 6
CBUS0 15
CBUS1 14
CBUS2 7
CBUS3 16
U6
FT230X
C4
47pF
C60.1uF
GND
5V 1
DAT- 2
DAT+ 3
NC 4
GS
HD
6G
SH
D7
GND 5
J1 Micro USB
RTSCTS
R1 27
R2 27
5VUSB
EN
BCD Charger
TXD
RXD
SW1
SW2
9
15
CMD_DATA_IN
CMD_DATA_OUT
NC1
IN2
GND3 OUT 4
VCC 5U3 VCC
GND
R25DNP
VCC
R27 DNP
NC 1
IN 2
GND 3OUT4
VCC5
U4
R33DNP
GND
VCC
R36 DNP
PROTOTYPEAREA
GND BUS
1
TXD
RX
DR
TSC
TS
VCC BUS
1
TP3
1
TP2
GND GND
TP1
VCC
39404142434445
4647484950515253545556
38373635
293031
323334
78910111213141516171819202122232425262728
1 2 3 4
J6100mil Header
1234567891011121314151617181920212223242526
J5100mil Header
GND
VCC
R10 DNPVCC
123456789
1011
J7100mil Header
123456789
1011121314
J4100mil Header
R45 DNP GND
R44 DNPR43 DNPR42 DNPR41 DNPR40 DNPR39 DNPR38 DNP
GNDGNDGNDGNDGNDGNDGND
GNDR52 DNPR53 DNP GND
R19 DNPGND
VCC
R11 DNPGND
R50 DNP GND
R14 DNPGND
R17 0 ohmVCC
R12 DNPGND
R26 DNP
R23 DNPGND
R21 DNPGND R47 DNP GNDR48 DNP GNDR49 DNP GND
R15DNP
VCC
R18DNP
GND
R13 DNP
R8 DNP
R16 DNPGND
R20 DNPGND
R28 DNPGND R29 DNPVCC R30 DNPGND R31 DNPGND
R32 DNP GND
R34 DNP GNDR35 DNP GND
R54 DNP GNDR55 DNP GNDR56 DNP VCC
C9
0.1uF
GND
VCC
6R6 DNP
Figure 48: Prototype Board Power Supply Area Schematic
GN
D
OU
TIN
GND
GND
+
C7
10uF
THERM
4
123
U5
THERM
RF
12 3
4 5
6 78 910 1112 1314 1516 1718 1920 2122 2324 2526 2728 2930 3132 3334 3536 37
38394041424344454647484950515253545556
J2Carrier Interconnect Female
1
GN
D2-
5
ANT1CONREVSMA001
GND
GND
GND
GND
GND
78 910 1112 1314 1516 1718 1920 2122 2324 2526 2728 2930 3132 3334 3536 37
38394041424344454647484950515253545556
X1
0 Ohm
6
X3DNP
GNDGND
X2DNP
GND
R24330
5VUSB
D2
PO
WE
R (G
RE
EN
)
D3
OV
ER
CU
RR
EN
T (R
ED
)
R22330
VCC
FAULT
U2
R5
10k
GND
5VUSB
GND
C80.47uF
FAU
LT
IN1
GND2
EN3 FAULT 4
ILIM 5
OUT 6
TPS2553
SW3
5VUSB
EN
FAULT
GND12
J3
100mil HeaderBattery Input
D1
GND
R753.6k
R953.6k
GND
Q1
R310k
BCD Charger
VCC
+
GND
GND
C14.7uF
C3
0.01uF
L1600R/1.3A
GND
C5
47pF
R40
C20.1uF
VC
C12
VC
CIO
3
3V3OUT10
GN
D5
GN
D13
USBDM9
USBDP8
RESET11
TXD 1
RXD 4
RTS 2
CTS 6
CBUS0 15
CBUS1 14
CBUS2 7
CBUS3 16
U6
FT230X
C4
47pF
C60.1uF
GND
5V 1
DAT- 2
DAT+ 3
NC 4
GS
HD
6G
SH
D7
GND 5
J1 Micro USB
RTSCTS
R1 27
R2 27
5VUSB
EN
BCD Charger
TXD
RXD
SW1
SW2
9
15
CMD_DATA_IN
CMD_DATA_OUT
NC1
IN2
GND3 OUT 4
VCC 5U3 VCC
GND
R25DNP
VCC
R27 DNP
NC 1
IN 2
GND 3OUT4
VCC5
U4
R33DNP
GND
VCC
R36 DNP
PROTOTYPEAREA
GND BUS
1
TXD
RX
DR
TSC
TS
VCC BUS
1
TP3
1
TP2
GND GND
TP1
VCC
39404142434445
4647484950515253545556
38373635
293031
323334
78910111213141516171819202122232425262728
1 2 3 4
J6100mil Header
1234567891011121314151617181920212223242526
J5100mil Header
GND
VCC
R10 DNPVCC
123456789
1011
J7100mil Header
123456789
1011121314
J4100mil Header
R45 DNP GND
R44 DNPR43 DNPR42 DNPR41 DNPR40 DNPR39 DNPR38 DNP
GNDGNDGNDGNDGNDGNDGND
GNDR52 DNPR53 DNP GND
R19 DNPGND
VCC
R11 DNPGND
R50 DNP GND
R14 DNPGND
R17 0 ohmVCC
R12 DNPGND
R26 DNP
R23 DNPGND
R21 DNPGND R47 DNP GNDR48 DNP GNDR49 DNP GND
R15DNP
VCC
R18DNP
GND
R13 DNP
R8 DNP
R16 DNPGND
R20 DNPGND
R28 DNPGND R29 DNPVCC R30 DNPGND R31 DNPGND
R32 DNP GND
R34 DNP GNDR35 DNP GND
R54 DNP GNDR55 DNP GNDR56 DNP VCC
C9
0.1uF
GND
VCC
6R6 DNP
Figure 49: Prototype Board RF Carrier Area Schematic
Prototype Board Schematic
GND
OUT
IN
GN
D
GN
D
+
C7
10uF
THE
RM
4
1
2
3
U5
THE
RM
RF
1
23
45
67
89
1011
1213
1415
1617
1819
2021
2223
2425
2627
2829
3031
3233
3435
3637
38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56
J2 Car
rier I
nter
conn
ect F
emal
e1
GND 2-5
AN
T1C
ON
RE
VS
MA
001
GN
D
GN
D
GN
D
GN
D
GN
D
78
910
1112
1314
1516
1718
1920
2122
2324
2526
2728
2930
3132
3334
3536
37
38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56
X1
0 O
hm
6
X3
DN
P
GN
DG
NDX
2D
NP
GN
D
R24
330
5VU
SB
D2
POWER (GREEN)
D3
OVER CURRENT (RED)
R22
330
VC
C
FAU
LT
U2
R5
10k
GN
D 5VU
SB
GN
D
C8
0.47
uF
FAULT
IN1
GN
D2
EN
3FA
ULT
4
ILIM
5
OU
T6
TPS
2553
SW
3
5VU
SB
EN
FAU
LT
GN
D1 2
J3
100m
il H
eade
rB
atte
ry In
put
D1
GN
D
R7 53.6
kR
9 53.6
k
GN
DQ1
R3
10k
BC
D C
harg
er
VC
C
+
GN
D
GN
D
C1
4.7u
F
C3
0.01
uF
L160
0R/1
.3A
GN
D
C5
47pF
R4
0
C2
0.1u
F
VCC12
VCCIO3
3V3O
UT
10
GND 5
GND 13
US
BD
M9
US
BD
P8
RE
SE
T11
TXD
1
RX
D4
RTS
2
CTS
6
CB
US
015
CB
US
114
CB
US
27
CB
US
316
U6
FT23
0X
C4
47pF
C6
0.1u
F
GN
D
5V1
DA
T-
2
DA
T+3
NC
4
GSHD 6GSHD 7
GN
D5
J1M
icro
US
B
RTS
CTS
R1
27
R2
27
5VU
SB
EN
BC
D C
harg
er
TXD RX
D
SW
1 SW
2
9
15
CM
D_D
ATA
_IN
CM
D_D
ATA
_OU
T
NC
1
IN2
GN
D3
OU
T4
VC
C5
U3
VC
C
GN
D
R25
DN
P
VC
C
R27
DN
P
NC
1
IN2
GN
D3
OU
T4
VC
C5
U4
R33
DN
P
GN
DVC
C
R36
DN
P
PR
OTO
TYP
EA
RE
A
GN
D B
US
1
TXDRXDRTSCTS
VC
C B
US
1
TP3
1
TP2
GN
DG
ND
TP1
VC
C
39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 5638373635
29 30 31
32 33 347 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28
1234
J6 100m
il H
eade
r1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26
J510
0mil
Hea
der
GN
D
VC
C
R10
DN
PV
CC
1 2 3 4 5 6 7 8 9 10 11J7 100m
il H
eade
r
1 2 3 4 5 6 7 8 9 10 11 12 13 14J4 100m
il H
eade
r
R45
DN
PG
ND
R44
DN
PR
43D
NP
R42
DN
PR
41D
NP
R40
DN
PR
39D
NP
R38
DN
P
GN
DG
ND
GN
DG
ND
GN
DG
ND
GN
D
GN
DR
52D
NP
R53
DN
PG
ND
R19
DN
PG
ND
VC
C
R11
DN
PG
ND
R50
DN
PG
ND
R14
DN
PG
ND
R17
0 oh
mV
CC
R12
DN
PG
ND
R26
DN
P
R23
DN
PG
ND
R21
DN
PG
ND
R47
DN
PG
ND
R48
DN
PG
ND
R49
DN
PG
ND
R15
DN
P
VC
C R18
DN
P
GN
D
R13
DN
P
R8
DN
P
R16
DN
PG
ND
R20
DN
PG
ND
R28
DN
PG
ND
R29
DN
PV
CC
R30
DN
PG
ND
R31
DN
PG
ND
R32
DN
PG
ND
R34
DN
PG
ND
R35
DN
PG
ND
R54
DN
PG
ND
R55
DN
PG
ND
R56
DN
PV
CC
C9
0.1u
F
GN
D
VC
C
6R
6D
NP
Figure 50: Prototype Board USB Area Schematic
– – – –42 43
GND
OUT
IN
GN
D
GN
D
+
C7
10uF
THE
RM
4
1
2
3
U5
THE
RM
RF
1
23
45
67
89
1011
1213
1415
1617
1819
2021
2223
2425
2627
2829
3031
3233
3435
3637
38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56
J2 Car
rier I
nter
conn
ect F
emal
e1
GND 2-5
AN
T1C
ON
RE
VS
MA
001
GN
D
GN
D
GN
D
GN
D
GN
D
78
910
1112
1314
1516
1718
1920
2122
2324
2526
2728
2930
3132
3334
3536
37
38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56
X1
0 O
hm
6
X3
DN
P
GN
DG
NDX
2D
NP
GN
D
R24
330
5VU
SB
D2
POWER (GREEN)
D3
OVER CURRENT (RED)
R22
330
VC
C
FAU
LT
U2
R5
10k
GN
D 5VU
SB
GN
D
C8
0.47
uF
FAULT
IN1
GN
D2
EN
3FA
ULT
4
ILIM
5
OU
T6
TPS
2553
SW
3
5VU
SB
EN
FAU
LT
GN
D1 2
J3
100m
il H
eade
rB
atte
ry In
put
D1
GN
D
R7 53.6
kR
9 53.6
k
GN
DQ1
R3
10k
BC
D C
harg
er
VC
C
+
GN
D
GN
D
C1
4.7u
F
C3
0.01
uF
L160
0R/1
.3A
GN
D
C5
47pF
R4
0
C2
0.1u
F
VCC12
VCCIO3
3V3O
UT
10
GND 5
GND 13
US
BD
M9
US
BD
P8
RE
SE
T11
TXD
1
RX
D4
RTS
2
CTS
6
CB
US
015
CB
US
114
CB
US
27
CB
US
316
U6
FT23
0X
C4
47pF
C6
0.1u
F
GN
D
5V1
DA
T-
2
DA
T+3
NC
4
GSHD 6GSHD 7
GN
D5
J1M
icro
US
B
RTS
CTS
R1
27
R2
27
5VU
SB
EN
BC
D C
harg
er
TXD RX
D
SW
1 SW
2
9
15
CM
D_D
ATA
_IN
CM
D_D
ATA
_OU
T
NC
1
IN2
GN
D3
OU
T4
VC
C5
U3
VC
C
GN
D
R25
DN
P
VC
C
R27
DN
P
NC
1
IN2
GN
D3
OU
T4
VC
C5
U4
R33
DN
P
GN
DVC
C
R36
DN
P
PR
OTO
TYP
EA
RE
A
GN
D B
US
1
TXDRXDRTSCTS
VC
C B
US
1
TP3
1
TP2
GN
DG
ND
TP1
VC
C
39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 5638373635
29 30 31
32 33 347 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28
1234
J6 100m
il H
eade
r1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26
J510
0mil
Hea
der
GN
D
VC
C
R10
DN
PV
CC
1 2 3 4 5 6 7 8 9 10 11J7 100m
il H
eade
r
1 2 3 4 5 6 7 8 9 10 11 12 13 14J4 100m
il H
eade
r
R45
DN
PG
ND
R44
DN
PR
43D
NP
R42
DN
PR
41D
NP
R40
DN
PR
39D
NP
R38
DN
P
GN
DG
ND
GN
DG
ND
GN
DG
ND
GN
D
GN
DR
52D
NP
R53
DN
PG
ND
R19
DN
PG
ND
VC
C
R11
DN
PG
ND
R50
DN
PG
ND
R14
DN
PG
ND
R17
0 oh
mV
CC
R12
DN
PG
ND
R26
DN
P
R23
DN
PG
ND
R21
DN
PG
ND
R47
DN
PG
ND
R48
DN
PG
ND
R49
DN
PG
ND
R15
DN
P
VC
C R18
DN
P
GN
D
R13
DN
P
R8
DN
P
R16
DN
PG
ND
R20
DN
PG
ND
R28
DN
PG
ND
R29
DN
PV
CC
R30
DN
PG
ND
R31
DN
PG
ND
R32
DN
PG
ND
R34
DN
PG
ND
R35
DN
PG
ND
R54
DN
PG
ND
R55
DN
PG
ND
R56
DN
PV
CC
C9
0.1u
F
GN
D
VC
C
6R
6D
NP
Figure 51: Prototype Board Prototype Area Schematic
Notes
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.
©2018 Linx Technologies. All rights reserved.
The stylized Linx logo, Wireless Made Simple, WiSE, CipherLinx and the stylized CL logo are trademarks of Linx Technologies.
Linx Technologies
159 Ort Lane
Merlin, OR, US 97532
Phone: +1 541 471 6256
Fax: +1 541 471 6251
www.linxtechnologies.com