MDEV-900MHZ-DT [LINX]
HumDTTM Series Master Development System;
| 型号： | MDEV-900MHZ-DT |
| 厂家： | 
Linx Technologies |
| 描述： | HumDTTM Series Master Development System |
| 文件： | 总19页 (文件大小：5132K) |
| 中文： | 中文翻译 | 下载： | 下载PDF数据表文档文件 |
HumDTTM 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
2 HumDTTM Series Transceiver Carrier Board
2 HumDTTM Series Transceiver Carrier Board Objects
3 HumDTTM Series Carrier Board Pin Assignments
3 Programming Dock
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 Programming Dock Objects
4 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.
4 Prototype Board Objects
5 Initial Setup
6 Using the Prototype Board
8 Using the Programming Dock
10 The Development Kit Demonstration Software
17 Development Kit Demonstration Software Example
22 Carrier Board Schematic
23 Programming Dock Board Schematic
28 Prototype Board Schematic
30 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 not
have a frequency hopping protocol built in.
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.
HumDTTM Master Development System
User's Guide
Figure 1: HumDTTM Series Master Development System
Introduction
The Linx HumDTTM 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 HumDT™ 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
Programming Dock Boards, 2 Prototype Boards, 4 HumDT™ Series
transceivers*, antennas, USB cables and full documentation.
* One part is soldered to each Carrier Board
–
–
1
Revised 8/30/2017
Ordering Information
HumDTTM Series Carrier Board Pin Assignments
Ordering Information
38 VCCD
39 GPIO_7
40 GPIO_6
41 GPIO_5
42 GPIO_4
43 GPIO_3
44 GPIO_2
45 GPIO_1
46 ACTIVE
47 NC
ANTENNA
1
2-5 GND (RF Connector)
Part Number
MDEV-***-DT
HUM-***-DT
Description
GND
6
8
7
9
MODE_IND
HumDTTM Series Master Development System
HumDTTM Series Transceiver
RESET
CMD_DATA_IN
POWER_DOWN 10
NC 12
11 VCCD
13 CTS
15 CMD_DATA_OUT
17 VCC
19 VCCD
21 VCCD
23 NC
EVM-***-DT
HumDTTM Series Carrier Board
VCCD 14
LNA_EN 16
GPIO_0 18
PA_EN 20
NC 22
MDEV-PGDCK
MDEV-PROTO
CON-SOC-EVM
Development System Programming Dock
Development System Prototype Board
EVM Module Socket Kit
48 NC
49 NC
NC 24
25 NC
50 NC
NC 26
27 NC
51 NC
NC 28
29 NC
52 NC
*** = Frequency; 868MHz, 900MHz
NC 30
31 NC
53 NC
NC 32
33 NC
54 NC
NC 34
35 NC
55 NC
Figure 2: Ordering Information
NC 36
37 NC
56 NC
Figure 5: HumDTTM Series Transceiver Carrier Board Pin Assignments (Top View)
Programming Dock
2
4
HumDTTM Series Transceiver Carrier Board
2
3
1
1
3
4
5
Figure 3: HumDTTM Series Transceiver Carrier Board
Figure 4: Programming Dock
Programming Dock Objects
1. Carrier Board Socket
2. RP-SMA Antenna Connector
3. MODE_IND LED
4. Micro USB Connector
5. LCD Display
HumDTTM Series Transceiver Carrier Board Objects
1. HumDTTM Series Transceiver
2. MMCX RF Connector
3. Dual Row Header
4. Single Row Header
–
–
–
–
3
2
Prototype Board
Initial Setup
There are several boards that are included with the Development System.
The Carrier Boards have a HumDTTM 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 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.
7
11
12
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
11
9
The development software supports Windows 7 and 10; with Java 1.6 or
later.
Figure 6: Prototype Board
Prototype Board Objects
1. Carrier Board Socket
2. RP-SMA Antenna Connector
3. Micro USB Connector
4. Power Switch
5. Power LED
6. External Battery Connection
7. Prototyping Area
Note: The Prototype board uses a USB to UART chip to connect the
module to the PC. This chip is powered from the 5V on the USB cable.
It has an input line that detects the voltage on Vcc and sets the UART
voltage levels to match as soon as power is applied to the chip.
8. 3.3V Supply Bus
9. Ground Bus
10. USB Interface Lines
11. Module Interface Headers
It is important that the power switch (SW3) be set appropriately before
the USB cable is plugged in. If an external power supply is used and the
switch is off when the cable is plugged in, then the UART output voltage
may not be set correctly and could result in communication failures.
12. Command Data Interface Routing Switches (on back)
Set the switch to BAT when using an external supply or to USB to use
the USB bus to power the module. Then plug in the USB cable.
–
–
–
–
5
4
The overload condition is reset once the excess current draw is removed.
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.
Using the Prototype Board
Snap a Carrier Board onto the socket on the Prototype Board as shown in
Figure 7.
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 8 shows the bottom of the board.
Figure 7: Prototype Board with a Carrier Board
Set the power switch (SW3) and 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.
Figure 8: Prototype Board Bottom Side
SW1 and SW2 connect the USB interface to the Command Data Interface
lines on the module. This allows the prototype board to be used with the
development kit software or a custom application. When in the “USB
Connected position”, the module is connected to the USB interface. The
“Header Only” position connects the module to the header.
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 5 shows the pin assignments for the Carrier Board.
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.
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.
–
–
–
–
7
6
Range Testing
Using the Programming Dock
Snap a Carrier Board onto the socket on the Programming Dock as shown
in Figure 9.
Several complex mathematical models exist for determining path loss in
many environments. These models vary as the transmitter and receiver are
moved from indoor operation to outdoor operation. Although these models
can provide an estimation of range performance in the field, the most
reliable method is to simply perform range tests using the modules in the
intended operational environment.
Range testing can be performed with the Programming Docks and / or
the Prototype Boards. Data can be sent across the link using the included
software or a custom microcontroller connected to the module. The RSSI is
included with the output data messages, so this can be used to qualify the
link.
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 9: 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.
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, check the ambient RSSI
value 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.
The HumDTTM Series transceiver has a serial Command Data Interface that
is used to configure and control the transceiver. This interface consists of a
standard UART with a serial command set.
–
–
–
–
9
8
key. This can only be read from modules configured as an AP.
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 Advanced Configuration tab when opened (Figure 10). This window
configures the module’s settings.
9. The Address box shows the module’s current local address. The
Network ID is the identifier of the network that the module is in. No
other module with the same Network ID can have the same Address.
10. The Joined Modules list shows all of the modules that have joined
with the current module. An ED and RE are only joined with an AP, so
they have one entry. An AP can be joined to up to 50 other modules,
including up to 4 REs.
6
1
12
14
13
11. The Radio section configures the radio functions. The checkboxes
select which RF channels are used. The TX Power menu sets the
transmitter output power. The data rate menu sets the serial UART
data rate, which the module uses to configure the over-the-air data
rate. The RSSI Readback shows the RSSI value of the last good
packet that was received.
7
2
8
9
3
4
10
11
12. The GPIO Expander Type menus configure the eight GPIOs as digital
inputs, digital outputs or analog inputs. The digital inputs are also
configured to use internal pull-up or pull-down resistors, or set to
high-impedance. High impedance deactivates the internal resistors.
15
5
16 17
18
13. The Status column shows the current status of all of the GPIO lines on
the active module.
14. The Internal 20kohm radio button sets the internal resistors as either
pull-up or pull-down.
Figure 10: The Master Development System Software Advanced Configuration 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 11.
15. The module identity box shows the active module’s name, firmware
version and serial number.
16. The Read All button reads all of the values.
2. The Help window shows tips and comments about the software.
17. The Submit button writes all changes to the active module.
18. The Set Defaults button restores all settings to the factory defaults.
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 software.
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 memory setting configures the software to read and write from
either volatile memory or non-volatile memory.
7. The Device Type section configures the module as either an Access
Point, End Device or Range Extender.
8. The Encryption Key box shows the module’s 16 byte AES encryption
Figure 11: The Master Development System Software Additional Information
–
–
–
–
11
10
The 868MHz version of the module operates on one of 68 channels as
opposed to being agile among 4 channels. The software automatically
detects the frequency band for the active module and adjusts the selection.
The 868MHz module changes the channel selection from the check boxes
to a drop-down menu in the Radio section (1).
The modules are shown with four identifiers as shown in Figure 13.
3
4
2
1
Figure 13: The Master Development System Software Module Identifiers
1. The type of module (HumDT™ 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.
1
Figure 12: The Master Development System Software Advanced Configuration Tab
All other selections and operation are identical for both versions. The
examples that follow show the 900MHz version, but the same procedures
apply for the 868MHz version.
Figure 14: The Master Development System Programming Dock with Name and Address Displayed
4. The active module has an eject symbol that disconnects the software
from that module when clicked. The Available modules have a play
symbol that makes that module active when clicked.
–
–
–
–
13
12
The Wireless Chat tab (Figure 15) offers a demonstration of sending data
between two modules. There is a window for each connected module.
The Command Set tab (Figure 16) allows specific commands to be written
to the module.
1
5
2
3
4
1
6
2
3
4
5
7
8
7
6
9
Figure 16: 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.
Figure 15: The Master Development System Software Wireless Chat Tab
2. The Response box shows the hexadecimal values that are returned
from the module in response to a command.
1. The top of the window shows the address of the associated module.
3. The Commands drop-down menu shows all of the commands that
are available for the active module (Figure 17). 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. The Items drop down menu displays all of the items that are available
for the active module (Figure 18). Selecting one of the items from
this menu automatically fills in the Command box. The values can be
adjusted by typing in the box.
2. The chat screen shows the chat messages that have been sent and
received.
3. The Send box is where the message text is entered. The message is
transmitted when the Send button is pressed.
4. The To menu selects the address of the connected module that is to
receive the message (the destination address).
5. The TX Times box shows how many times the module has transmitted.
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 HumDT™ Series Transceiver Data
Guide for definitions of each value.
6. The RX Count box counts the number of messages that the module
has received.
7. The Clear button clears all of the messages from the chat window.
8. The RSSI box indicates the signal strength of the last received
message.
7. The Show Commands button opens a window that shows all of the
bytes sent to the module and the responses from the module.
9. When the Show As Bytes box is selected the messages are shown as
bytes in the chat window.
–
–
–
–
15
14
The Network tab shows the interaction of all of the connected modules
on one screen. Figure 20 shows two modules on the screen, but up to 8
modules can fit at one time.
Figure 17: The Master Development System Software Command Set Tab Commands Menu
Figure 20: The Master Development System Software Network Tab
The screen shows the network configuration of all modules that are
connected to the PC. The drop-down menu changes the module’s device
type and the text box has the module’s network ID. This screen makes it
easy to quickly set up the network and visually verify its configuration.
Figure 18: The Master Development System Software Command Set Tab Items Menu
Figure 19: The Master Development System Software Show Commands Window
–
–
–
–
17
16
Development Kit Demonstration Software Example
This example shows how to configure two modules to work with each
other. The software defaults to the Advanced Configuration tab when
opened (Figure 21).
Figure 23: The Master Development System Software with Connected Modules
Any changes to the current configurations are shown in red. These
changes are not written to the module until the Submit button is clicked.
Figure 21: The Master Development System Software Advanced Configuration Tab at Start-up
Install Carrier Boards onto the Programming Docks and plug a USB cable
between the Programming Docks and the PC. The software automatically
detects attached devices. The first module that is identified appears
under the Active label. This is the module that is actively controlled by
the software. Subsequent modules are listed under the Available label as
shown in Figure 22.
Figure 22: The Master Development System Software Connected Modules
Figure 24: The Master Development System Software Advanced Configuration with Changes
Once the modules are detected by the software, the appropriate options
are displayed on the Advanced Configurations tab and a Network tab
appears. The module’s documents appear under the Documentation link.
Changing the active module is accomplished by either clicking the play
symbol next to the desired module or dragging it from the Available list to
the Active spot. Changes can now be made to this module.
–
–
–
–
19
18
Clicking on the Network tab shows the current state of all modules
connected to the PC.
Figure 25: The Master Development System Software Dragging to Change the Active Module
Figure 26: The Master Development System Software Network Tab
There are several settings that must match in order for the modules to be
able to communicate. This example uses the following settings.
Both modules are set as End Devices. There must be at least one
Access Point in every network, so one module must be changed. This is
accomplished by clicking the drop-down menu on one of the modules and
selecting AP.
•ꢀ The Encryption Key must match on both modules. This can only be
read out of an AP.
•ꢀ Network ID must match on both devices.
•ꢀ The UART Baud Rate is 9600.
Other settings can be used as long as they match on both modules. Once
the settings are changed and submitted to both modules, the Network tab
can be used to graphically view the network topology and the Wireless
Chat tab can be used to transfer data.
Figure 27: The Master Development System Software Network Tab
Both modules must have the same Network ID, so change the ID number
in one or both of the boxes to match.
–
–
–
–
21
20
Figure 28: The Master Development System Software Network Tab
A dotted line appears between the modules indicating that they are joining
the network.
Figure 30: The Master Development System Software Wireless Chat Tab
Figure 29: The Master Development System Software Network Tab
A solid line appears between the modules when they are joined and ready
to communicate. The Wireless Chat tab can now be used to send data
between the modules.
–
–
–
–
23
22
Carrier Board Schematic
Programming Dock Board Schematic
1
C M D _ D A T A _ I N
M O D E _ I N D
1
V C C
V C C D
V C C D 4
2 1
1 3
P O W E R _ D O W P D N
R E S E T
R E S E T
L N A _ E N
P A _ E N
N
2 2
2 1
L N A _ E N
2 3
V C C D
V C C D
V C C D 3
1 1
1 0
P A _ E N
2 4
V C C D 2
G N D
G N D
9
2 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
V C C D
8
V C C D 1
G P I O _ 7
G P I O _ 6
G P I O _ 5
5 2 -
G N D
C M D _ D A T A _ I N
2 7
G P I O _ 7
7
C T S
C T S
V C C D
G P I O _ 6
6
2 8
V C C D 5
G P I O _ 5
5
2 9
Figure 32: Programming Dock Board RF Carrier Area Schematic
Figure 31: HumDTTM Series Transceiver Carrier Board Module Schematic
–
–
–
–
25
24
VCC
5VUSB
U3
VCC
TPS2552
U4
LM3940IMP 3.3V
R5
330 ohm
1
2
3
6
5
4
1
3
IN
OUT
ILIM
Vin
Vout
GND
GND
EN
+
C8
C9
0.47uF
D1
R11
53.6k
100uF
nPWREN
FAULT
GND
GND
GND
GND
Figure 33: Programming Dock Board Power Supply Area Schematic
V C C I O
V C C
G N D
G N D
3
1 3
1 2
5
RXD
CMD_DATA_OUT
VCC
R46
10k
D4
Buffer Bypass DNP
R48 0 ohm
TXD
CMD_DATA_IN
U1
VCC
5
R8
330 ohm
1
NC
IN
GND OUT
VCC
2
3
GND
4
GND
VCC
Buffer Bypass DNP
R49 0 ohm
RTS
nCMD
R40
0 ohm
U5
VCC
5
VCC
1
2
3
NC
IN
GND OUT
VCC
S2
SW1
4
LADJ
R17
10k
GND
PAIR
R24
10k
G S H D
6
G S H D
7
R41
0 ohm
GND
GND
GND
Figure 35: Programming Dock Board USB Area Schematic
Figure 34: Programming Dock Board Signal Routing Schematic
–
–
–
–
27
26
Prototype Board Schematic
nPDN
J3
R36
DNP
U8
VDC
RA5
RA4
MCLR
RC5
RC4
RC3
D1
1
2
GND
D2
1
2
3
4
5
6
7
14
13
12
11
10
9
C7
VCC
VCCP
GPIO1
PGM
R42 DNP
GND
ICSPDAT
ICSPCLK
RA2
GND
PGD
PGC
RST
SCL
SI
VCC
GND
100mil Header
Battery Input
SW3
10uF
R23
DNP
U2
RC0
RC1
RC2
GND
U5
RXD
8
1
6
5
4
CSB
RS
5VUSB
GND
EN
IN
OUT
ILIM
GND
PIC16F1825-I/ST
2
GND
C8
0.47uF
THERM
THERM
3
EN FAULT
TPS2553
R7
R9
GND
53.6k 53.6k
VCC
D2
5VUSB
Q1
BCD Charger
VCC
D3
R3
10k
R6
0 Ohm
GND
R22
330
R24
330
LCD1
LED+
GND
1
R5
5VUSB
FAULT
C14
1uF
2
3
4
5
6
7
8
9
10
11
FAULT
C1-
10k
GND
C1+
VOUT
VCC
GND
SI
SCL
CSB
RS
Figure 37: Prototype Board Power Supply Area Schematic
VCC
GND
C13
1uF
SI
SCL
CSB
RS
GND
CONREVSMA001
X1
ANT1
RST
RST
J2
1
RF
Carrier Interconnect Female
12
GND
LED-
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
2x16 LCD
X3
GND
40
7
9
DNP
Figure 36: Programming Dock Board Microcontroller Area Schematic
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
Figure 38: Prototype Board RF Carrier Area Schematic
–
–
–
–
29
28
S C T
S R T
D R X
D T X
4
3
2
1
O
C
V C C I
V C
D
D
G N
G N
3
1 2
1 3
5
1
G S H D
6
G S H D
7
Figure 40: Prototype Board Prototype Area Schematic
Figure 39: Prototype Board USB Area Schematic
–
–
–
–
31
30
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网 联系我们和版权申明