MDEV-DEMO-RC-A [LINX]
HumRCTM Series Master Development System;
| 型号： | MDEV-DEMO-RC-A |
| 厂家： | 
Linx Technologies |
| 描述： | HumRCTM Series Master Development System |
| 文件： | 总25页 (文件大小：7168K) |
| 中文： | 中文翻译 | 下载： | 下载PDF数据表文档文件 |
HumRCTM Series
Master Development System
User's Guide
Warning: Some customers may want Linx radio frequency (“RF”)
!
Table of Contents
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”).
1 Introduction
2 Ordering Information
3 HumRCTM Series Transceiver Carrier Board
3 HumRCTM Series Transceiver Carrier Board Objects
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.
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
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.
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
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.
HumRCTM Master Development System
User's Guide
Figure 1: HumRCTM Series Master Development System
Introduction
The 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
–
–
1
Revised 8/30/2017
Ordering Information
HumRCTM Series Transceiver Carrier Board
Ordering Information
2
Part Number
EVAL-***-RC
MDEV-***-RC
HUM-***-RC
Description
HumRCTM Series Basic Evaluation Kit
HumRCTM Series Master Development System
HumRCTM Series Remote Control Transceiver
1
3
4
HumRCTM Series Remote Control Transceiver, Certified, UFL
Connector
HUM-900-RC-UFL
HumRCTM Series Remote Control Transceiver, Certified, Castella-
tion Connection
HUM-900-RC-CAS
EVM-***-RC
HumRCTM Series Carrier Board
HumRCTM Series Carrier Board with Certified module, UFL Con-
nector
EVM-900-RC-UFL
HumRCTM Series Carrier Board with Certified module, Castellation
Connection
EVM-900-RC-CAS
Figure 3: HumRCTM Series Transceiver Carrier Board
MDEV-DEMO-RC-A
MDEV-DEMO-RC-B
MDEV-PGDOCK
MDEV-PROTO
Development System Remote Control Demo Board, Type A
Development System Remote Control Demo Board, Type B
Development System Programming Dock
Development System Prototype Board
HumRCTM Series Transceiver Carrier Board Objects
1. HumRCTM Series Transceiver
2. MMCX RF Connector
3. Dual Row Header
4. Single Row Header
CON-SOC-EVM
EVM Module Socket Kit
*** = Frequency; 900MHz, 2.4GHz
Figure 2: Ordering Information
HumRCTM Series Transceiver Carrier Board Pin Assignments
38 S0
ANTENNA
1
2-5 GND (RF Connector)
39 S1
40 S2
GND
6
8
7
9
MODE_IND
41 S3
RESET
CMD_DATA_IN
42 S4
PDN 10
NC 12
11 LATCH_EN
13 ACK_EN
15 CMD_DATA_OUT
17 VCC
19 C0
43 S5
44 S6
PAIR 14
LNA_EN 16
LVL_ADJ 18
PA_EN 20
NC 22
45 S7
46 ACK_OUT
47 NC
48 NC
49 NC
50 NC
51 NC
52 NC
53 NC
54 NC
55 NC
56 NC
21 C1
23 NC
NC 24
25 NC
NC 26
27 NC
NC 28
29 NC
NC 30
31 NC
NC 32
33 NC
NC 34
35 NC
NC 36
37 NC
Figure 4: HumRCTM Series Transceiver Carrier Board Pin Assignments (Top View)
–
–
–
–
3
2
Programming Dock
Remote Control Demo Board
2
2
2
4
3
3
4
5
1
4
5
1
3
1
6
6
7
7
8
8
5
Figure 5: Programming Dock
Programming Dock Objects
1. Carrier Board Socket
2. RP-SMA Antenna Connector
3. MODE_IND LED
Board A
Board B
4. Micro USB Connector
5. LCD Display
Figure 6: Remote Control Demo Board
Remote Control Demo Board Objects
1. Carrier Board Socket
2. RP-SMA Antenna Connector
3. Power Switch
4. MODE_IND LED
5. CONFIRM LED
6. PAIR button
7. Status Line Output LEDs
8. Status Line Input Buttons
9. 4 AAA Batteries (Not shown, on the back of the boards)
–
–
–
–
5
4
Prototype Board
Initial Setup
There 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.
6
4
3
2
5
1
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.
8
10
11
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.
7
11
12
11
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.
9
Figure 7: Prototype Board
Prototype Board Objects
1. Carrier Board Socket
2. RP-SMA Antenna Connector
3. Micro USB Connector
4. Power Switch
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
5. Power LED
6. External Battery Connection
7. Prototyping Area
8. 3.3V Supply Bus
The development software supports Windows 7 and 10; with Java 1.6 or
later.
9. Ground Bus
10. USB Interface Lines
11. Module Interface Headers
12. Command Data Interface Routing Switches (on back)
–
–
–
–
7
6
Using the Programming Dock
Snap a Carrier Board onto the socket on the Programming Dock as shown
in Figure 8.
Using the Remote Control Demo Board
Snap a Carrier Board onto the socket on each Remote Control Demo
Board as shown in Figure 9.
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.
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.
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.
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.
–
–
–
–
9
8
Range Testing
Using the Prototype Board
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.
Snap a Carrier Board onto the socket on the Prototype Board as shown in
Figure 10.
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.
Figure 10: Prototype Board with a Carrier Board
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.
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.
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.
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.
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.
–
–
–
–
11
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.
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.
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 12 shows a convenient cross reference showing which lines on the
module connect to which lines on the prototype board.
Figure 11 shows the bottom of the board.
Module to Prototype Board Pin Number Cross Reference
Pin Name
Module Pin Number
Prototype Board Pin Number
MODE_IND
30
22
27
12
13
28
29
26
21
32
10
11
8
7
RESET
8
CMD_DATA_IN
9
POWER_DOWN
10
11
13
14
15
17
18
19
21
38
39
40
41
42
43
44
45
46
LATCH_EN
ACK_EN
PAIR
CMD_DATA_OUT
VCC
LVL_ADJ
C0
C1
S0
S1
7
S2
6
S3
5
Figure 11: Prototype Board Bottom Side
S4
4
S5
3
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.
S6
2
S7
1
ACK_OUT
31
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.
Figure 12: Module to Prototype Board Pin Number Cross Reference
–
–
–
–
13
12
8. The Status Details section shows the module’s control line states, radio
state and RSSI level.
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.
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.
1
11. The Show Commands button opens a larger window to view the serial
commands sent to and received from the module.
7
10
6
2
The modules are shown with three identifiers as shown in Figure 14.
3
4
1
5
2
3
8
Figure 14: The Master Development System Software Module Identifiers
9
1. The type of module (HumRC™ Series)
2. The module’s local address.
11
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 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.
Figure 15: The Master Development System Software Additional Information
–
–
–
–
15
14
The Advanced Configuration tab (Figure 16) offers more detailed
configuration options for the active module.
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.
1
2
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
3
10
11
12
4
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.
5
6
7
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.
13
14
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.
8
15
16
20
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.
17
18
19
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.
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.
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.
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.
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.
4. The Paired Modules Window lists all of the modules that are paired
with the active module and their Permissions Mask.
16. The Duty Cycle configuration sets the interval and Keep on times for
automatically cycling power to the receiver.
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.
17. The Module Identity box displays the module type, firmware version
and serial number of the active module.
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.
18. The Read All button reads all of the current configurations from the
active module.
–
–
–
–
17
16
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
5
2
3
4
Figure 18: The Master Development System Software Demo Command Set Tab Commands Menu
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.
6
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.
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 HumRC™ Series Transceiver
Command Data Interface Reference Guide for definitions of each value.
–
–
–
–
19
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.
The RC Configuration tab (Figure 21) allows configuration of the module’s
advanced remote control features.
5
1
6
2
3
7
8
4
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.
11
9
10
12
Figure 21: The Master Development System Software RC Configuration Tab
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.
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.
–
–
–
–
21
20
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.
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 22).
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.
Figure 22: 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 23.
Figure 23: 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 24.
–
–
–
–
23
22
Changing the active module is accomplished by dragging a module from
the Available list to the Active spot, as shown in Figure 26.
Figure 24: The Master Development System Software Pairing Modules
Once the module is dropped into the Given Permissions window it is
written to the active module’s memory. Clicking on the down arrow displays
the paired module’s Permissions Mask. This configures which output lines
the paired module is authorized to control. In Figure 25 the Permissions are
inactive since the active module only has inputs and no outputs to control.
Figure 26: 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 27).
Figure 27: The Master Development System Software Advanced Configuration
Figure 25: The Master Development System Software Paired Modules
–
–
–
–
25
24
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.
Figure 29: The Master Development System Software Demo and EZConfiguration Tab with Changes
The buttons have all changed to LEDs. The symbol next to each LED
indicates if it is latching or momentary (Figure 30). S0 is latching, the rest
are momentary.
1
2
Figure 28: The Master Development System Software Advanced Configuration with Changes
Figure 30: The Master Development System Software Latching (1) and Momentary (2) Symbols
This configuration changes the module to have all outputs. This is shown
by clicking on the Demo & EZConfiguration tab Figure 29.
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.
–
–
–
–
27
26
Full system operation is demonstrated by clicking on the Sandbox tab
(Figure 33).
Figure 31: The Master Development System Software Transmitting Module
Figure 33: 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 34).
Figure 34: The Master Development System Software Saved Profiles Window
Figure 32: The Master Development System Software Receiving Module
Clicking the Save Current button brings up a prompt asking for a name of
the profile (Figure 35).
–
–
–
–
29
28
Carrier Board Schematic
Figure 35: The Master Development System Software Save Profile
Once saved, the profile appears in the window, as shown in Figure 36.
1
Figure 36: 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.
V C C
L A T C H _ E N
1 3
L A T C H _ E N
2 1
R E S E T
R E S E T
L N A _ E N
P A _ E N
N
P O W E R _ D O W P D N
2 2
1 2
L N A _ E N
C 1
C 0
G N D
S 0
C 1
C 0
2 3
1 1
1 0
P A _ E N
2 4
G N D
2 5
9
8
7
6
5
C M D _ D A T A _ O U T
2 6
C M D _ D A T A _ O U T
C M D _ D A T A _ I N
S 0
S 1
S 2
S 3
C M D _ D A T A _ I N
2 7
S 1
A C K _ E N
A C K _ E N
P A I R
S 2
2 8
P A I R
S 3
2 9
Figure 37: HumRCTM Series Transceiver Carrier Board Module Schematic
–
–
–
–
31
30
CONREVSMA002
ANT1
Remote Control Demo Board Schematic
1
RF
Note: The Remote Control Demo boards are designed to accept carrier
boards for multiple module families. Some circuitry is not applicable for
some modules.
X2
X1
GND
GND
1.8nH
DNP
RESTORE
U2
S9
1
2
3
4
5
6
7
14
13
12
11
10
9
VCC
VDD
RA5
RA4
MCLR
RC5
RC4
RC3
GND
ICSPDAT
ICSPCLK
RA2
GND
PGD
PGC
SER_I/O
PIC A/B
MODE_IND
CRT_LRN
GND
GND
2
4
3
5
GND
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
D0
D1
D2
D3
D4
D5
D6
D7
MCLR
CMD_DATA_OUT
CMD_DATA_IN
IDENTITY
GND
GND
GND
RC0
RC1
RC2
6
8
10
7
9
MODE_IND
CMD_DATA_IN
LATCH_EN
ACK_EN
CMD_DATA_OUT
VCC
C0
C1
SEND
8
R14
330
PDN
PAIR
11
13
15
17
19
21
23
25
27
29
31
33
35
37
PIC16F1824
12
14
16
18
20
22
24
26
28
30
32
34
36
CONFIRM
IDENTITY
BAUD_0
SEL_TIMER
CRT_LRN
LVL_ADJ
D7
GND
SER_I/O
ED_SEL
D8
D9
D_CFG
A_CFG_0
A_CFG_1
Figure 38: Remote Control Demo Board Microcontroller Area Schematic
J1
Carrier Interconnect Female
VCC
SW1
SPDT
U1
VCC
Figure 40: Remote Control Demo Board RF Carrier Area Schematic
1
3
Vin
Vout
R2
330
B1
+
C2
100uF
C1
0.47uF
GND
D1
GND
GND
GND
GND
Figure 39: Remote Control Demo Board Power Supply Area Schematic
–
–
–
–
33
32
VCC
VCC
A Board
B Board
A Board
P1
D0
D1
D2
D3
1
R28 0 ohm
R29 0 ohm
R40 0 ohm
R30 0 ohm
R31 0 ohm
R39 0 ohm
C0
C1
VCC
GND
GND
GND
C0
C1
GND
VCC
VCC
VCC
R33
0
2
3
4
S8
PAIR
PIC A/B
ED_SEL
PIC A/B
ED_SEL
R43 10K
Header 4
R7
10K
SW2
R26
330
PAIR
CRT_LRN
R12
330
LVL_ADJ
P2
S0 VCC
S7 VCC
D6
D5
D4
1
2
3
R1
10K
D19
D5
R36
0
Header 3
D3
D17
R10
10K
GND
GND
VCC P3
R24
10K
GND
1
2
3
D7
GND
J2
GND
GND
GND
Header 3
MCLR
VCC
GND
PGD
PGC
1
2
3
4
5
6
R17
330
R22
330
S1 VCC
S2 VCC
S3 VCC
S6 VCC
S5 VCC
S4 VCC
VCC
D10
D15
D8
D13
GND
GND
R15
10K
R20
10K
GND
GND
R21
330
R18
330
R3
330
R27
330
D14
D11
D12
D9
D2
D20
GND
GND
R16
10K
R19
10K
GND
GND
GND
GND
GND
R25
330
R13
330
Figure 42: Remote Control Demo Board Miscellaneous Circuits Schematic
D6
D18
D16
D4
GND
GND
R23
10K
R11
10K
GND
GND
Figure 41: Remote Control Demo Board Remote Control Area Schematic
–
–
–
–
35
34
Programming Dock Board Schematic
5VUSB
U3
TPS2552
VCC
+
U4
LM3940IMP 3.3V
1
2
3
6
5
4
1
3
IN
OUT
ILIM
Vin
Vout
GND
GND
EN
C8
C9
0.47uF
R11
53.6k
100uF
PWREN#
FAULT
GND
GND
GND
GND
Figure 44: Programming Dock Board Power Supply Area Schematic
RXD
CMD_DATA_OUT
VCC
C M D _ D A T A _ I N
M O D E _ I N D
R46
10k
D4
Buffer Bypass DNP
R48 DNP
TXD
CMD_DATA_IN
U1
VCC
R8
1
5
NC
IN
GND OUT
VCC
330 ohm
1
2
3
GND
4
GND
VCC
R40
Buffer Bypass DNP
R49 DNP
RTS
nCMD
U5
VCC
5
VCC
0 ohm
1
2
3
NC
IN
GND OUT
VCC
S2
SW1
4
LADJ
R17
10k
GND
PAIR
R24
10k
2 - 5
G N
D
R41
0 ohm
GND
GND
GND
Figure 43: Programming Dock Board RF Carrier Area Schematic
Figure 45: Programming Dock Board Signal Routing Schematic
–
–
–
–
37
36
VCC
nPDN
R36
DNP
U8
VDC
RA5
RA4
MCLR
RC5
RC4
RC3
R5
D2
1
2
3
4
5
6
7
14
13
12
11
10
9
330 ohm
VCC
VCCP
GND
ICSPDAT
ICSPCLK
RA2
GND
PGD
PGC
RST
SCL
SI
GPIO1
PGM
R23
DNP
D1
CMD_DATA_IN
RC0
RC1
RC2
RXD
8
R42 DNP
CSB
RS
GND
PIC16F1825-I/ST
V C C I O
V C C
G N D
G N D
3
1 3
1 2
5
VCC
R6
0 Ohm
LCD1
LED+
1
C14
1uF
2
3
4
5
6
7
8
9
10
11
C1-
C1+
VOUT
VCC
GND
SI
SCL
CSB
RS
VCC
GND
C13
1uF
SI
SCL
CSB
RS
GND
RST
RST
12
GND
LED-
2x16 LCD
Figure 47: Programming Dock Board Microcontroller Area Schematic
G S H D
6
G S H D
7
Figure 46: Programming Dock Board USB Area Schematic
–
–
–
–
39
38
Prototype Board Schematic
J3
1
2
GND D1
C7
VCC
GND
100mil Header
Battery Input
SW3
10uF
U2
GND
U5
1
6
5VUSB
GND
EN
IN
OUT
ILIM
2
5
4
GND
C8
0.47uF
THERM
THERM
3
EN FAULT
TPS2553
R7
R9
GND
53.6k 53.6k
VCC
D2
5VUSB
Q1
BCD Charger
D3
R3
10k
GND
R22
330
R24
330
GND
R5
5VUSB
FAULT
FAULT
10k
GND
Figure 48: Prototype Board Power Supply Area Schematic
O
C
V C C I
V C
D
D
G N
G N
3
1 2
1 3
5
CONREVSMA001
X1
ANT1
J2
1
RF
Carrier Interconnect Female
GND
GND
2
4
3
5
GND
0 Ohm
X2
DNP
38
39
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
X3
DNP
GND
40
7
9
6
8
6
8
7
9
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
GND
10
12
14
16
18
20
22
24
26
28
30
32
34
36
10
12
14
16
18
20
22
24
26
28
30
32
34
36
11
13
15
17
19
21
23
25
27
29
31
33
35
37
11
13
15
17
19
21
23
25
27
29
31
33
35
37
GND
GND
G S H D
6
G S H D
7
Figure 49: Prototype Board RF Carrier Area Schematic
Figure 50: Prototype Board USB Area Schematic
–
–
–
–
41
40
Notes
S C T
S R T
D R X
D T X
4
3
2
1
1
Figure 51: Prototype Board Prototype Area Schematic
–
–
–
–
43
42
Linx Technologies
159 Ort Lane
Merlin, OR, US 97532
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 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.
相关型号：
©2020 ICPDF网 联系我们和版权申明