26-Aug-10 USB-232 HW143-19 www.firmwarefactory.com plugs. The micro connector pin-out is the same as the mini" />
參數(shù)資料
型號(hào): TPFLXIC005
廠商: Microchip Technology
文件頁數(shù): 10/11頁
文件大?。?/td> 0K
描述: IC MICROCONTROLLER
標(biāo)準(zhǔn)包裝: 1
系列: *
p8 of 11
26-Aug-10
USB-232
HW143-19
www.firmwarefactory.com
plugs. The micro connector pin-out is the same as the
mini connector.
Figure 10 Common USB pin-outs for male connectors
Table 5. USB Connection Key
Pin
Std Mini
Name
Cable
color
Description
1
Vcc
Red
+5V (can dip to 4.08V)
2
D–
White
Data –
3
D+
Green
Data +
4
ID
Type A: Connect to ground
Type B: Not connected
4
5
Gnd
Black
Signal ground
For ultra-low cost products, it is possible to form a USB
Type-A plug direct from a circuit board as shown in
figure 11. This connector is only suitable for a number
of insertions (~50 before cleaning is required).
It is
unshielded and recommended only for ‘dongle’ type
products with no cables attached.
4. Vss
11.75
1.00-2.00
1.00
0.50
3.00
12.00
Shoulder required to prevent over-insertion
Overall PCB width 16.00 or less
Contacts plated with hard
gold flash (0.25-1.27m)
over nickel (2.6-5.0m)
Overall PCB thickness
including tracks 2.00 - 2.20
3. D+
2. D-
1. Vdd
2.25
1.25
Dimensions in mm
Fig 11.
For further dimensional information, refer to figure 6-7 of
the USB 2.0 Specification, in the development kit.
Host-Side Interfacing
Prior to writing your own software, you can use the
HIDconfig.exe software in the development kit to
evaluate USB-232.
USB-232 uses the Human Interface Device (HID) USB
interface. It has the advantages that no device drivers
are required, and that a host application can easily
locate the USB-232.
All exchanges of data (‘reports’) between the host and
the USB-232 are 64 bytes in length, regardless of how
many bytes of meaningful data are actually transferred.
In HID terms, all transfers are 1ms interrupt reports of
64 bytes, to and from output ID 0 on EP1.
The host software has two perform two tasks. First it
has to locate the device. Then it has to communicate
with it. To locate the device, enumerate all devices with
Vendor ID 0x0B40 and Product ID 0x011A (2450-based
devices) or 0x011B (14K50-based devices). Then use a
Get Feature request for the string 4, the Product GUID.
If this matches the product GUID you configured for the
device, you have located it.
Once you have located the device, you need to open a
file to communicate with it. You can then send data and
receive data as 64-byte reports.
Sample source code for Windows and a Windows
dynamic link library (DLL) are provided in the
development kit. For a detailed description, please refer
to the comments embedded in the source code and the
Visual Basic example in the Excel spreadsheet. Sample
source code for Mac OS and Linux is in preparation.
Sending and Receiving Data
The first byte of the report (byte 0) is termed the
identifier. If its value is 0x01-0x3F, then it indicates that
the packet is data for transmission to or received from
the TxD and RxD pins. The value equals the number of
data bytes being transferred. The data is located from
byte 1 of the report onwards.
If its value is 0x41-0x7F, it should be interpreted exactly
the same as 0x01-0x3F except the value equals the
number of data bytes being transferred plus 0x40, and
the report must be acknowledged before the next data
report is sent.
A data report is acknowledged by
sending a report with an identifier of value 0x40.
(Note: Prior to rev 0008, the maximum number of data
bytes is 0x3E, i.e. the identifiers 0x3F and 7F are not
permitted.)
Break conditions are not supported. Contact us if this is
an important design requirement.
Commands
All commands are sent using identifiers of value 0x80 or
higher. If a response to the command is required, the
response will have the same identifier as the command
to which it is responding. The Interrupt response has no
command associated with it and it may be received by
the host at any time.
Note: Accidentally sending a command in the range
0x80-0x8F can modify settings that may permanently
disable the device. During product development, it is
recommended that you work with a device that has been
write locked using HIDconfig.exe. Devices intended for
production should always be write locked.
Get Pin
The identifier GETPIN (0x90) retrieves value of a pin.
The command payload has one byte, which indicates
the pin, as shown in table 6. The response payload has
two bytes, as shown in table 6.
Example:
90 25
Command – Get DTR pin
90 25 01
Response – Pin is active
Get Analog
The identifier GETANALOG (0x96) retrieves the voltage
of the analog pin. The command has not payload. The
response payload has two bytes, representing a number
相關(guān)PDF資料
PDF描述
PIC12C508A-04I/SM IC MCU OTP 512X12 8-SOIJ
PIC16LF1903-I/SS MCU 7KB FLASH LCD DVR 28-SSOP
PIC12C509A-04/SN IC MCU OTP 1KX12 8SOIC
VE-BT1-IX-F4 CONVERTER MOD DC/DC 12V 75W
VE-BT1-IX-F2 CONVERTER MOD DC/DC 12V 75W
相關(guān)代理商/技術(shù)參數(shù)
參數(shù)描述
TPFLXIC006 功能描述:插座和適配器 FlexiPnl USB-232-SS RoHS:否 制造商:Silicon Labs 產(chǎn)品:Adapter 用于:EM35x
TPFLXIC007 功能描述:插座和適配器 FlexiPnl USB-SPI-DIL RoHS:否 制造商:Silicon Labs 產(chǎn)品:Adapter 用于:EM35x
TPFLXIC008 功能描述:插座和適配器 FlexiPnl USB-SPI-SS RoHS:否 制造商:Silicon Labs 產(chǎn)品:Adapter 用于:EM35x
TPFLXIC009 功能描述:插座和適配器 FlexiPnl USB-I2C-DIL RoHS:否 制造商:Silicon Labs 產(chǎn)品:Adapter 用于:EM35x
TPFLXIC010 功能描述:插座和適配器 FlexiPnl USB-I2C-SS RoHS:否 制造商:Silicon Labs 產(chǎn)品:Adapter 用于:EM35x