various iPod, iPhone and/or iPad accessories in this District and elsewhere that are not
Filed07/22/10 Page9 of 113
licensed or otherwise authorized by Apple, including, but not limited to: cables identified as iPhoneSyncCable01 ASIN, iPodSyncCable01 - ASIN5, and iPodSyncRetractableCable01 ASIN; chargers identified as iphone3G_CAR_charger_ASIN; cradles identified as iPhone3G_Metal_CRADLE-UPC and iPhone3G_Plastic_CRADLE; FM transmitters identified as FM2in1BLK-iPhone_3G ASIN, FM2in1BLK-iPhone_3G - ASIN1, FMALLKIT_, FMALLKIT_LCD_ASIN4, iPhone3G_FM2in1BLK_ASIN6, FM2in1BLK-iPhone3G-UPC, FM2in1BLK-iPhone3GS-UPC_, FM4in1_iphone_NS ASIN, FM8in1_ARM_RV008 CrazyOD, FM8in1_BLK_iphone_3G_UPC, iPh3G_FM6in1_Remote, iPhone_iTRIP_FM_REMOTE UPC, iPhone3G_FM8in1BLK_ASIN, and iPhone3G_iTRIP_NEW03REMOTE-Touch2G-UPC. 29. Upon information and belief, Defendant Boxwave distributes and/or sells various
iPod, iPhone and/or iPad accessories in this District and elsewhere that are not licensed or otherwise authorized by Apple, including, but not limited to: cables identified as miniSync for Apple iPhone 3G and DirectSync Cable for Apple iPhone 3G; chargers identified as Micro Car Charger Apple iPhone 3G and Wall Charger Direct for Apple iPhone 3G; and cradles identified as Desktop Cradle Apple iPhone 3G. 30. As alleged further below, the various iPod, iPhone and/or iPad accessories
offered by Defendants infringe Apples patent and trademark rights. By misappropriating Apples proprietary technology and designs, and by utilizing Apples registered word and design trademarks, Defendants are infringing on Apples intellectual property and are wrongfully and unfairly exploiting Apples name and reputation. FIRST CLAIM FOR RELIEF (Infringement of U.S. Patent No. 7,627,343) (Against All Defendants) 31. 32. Apple incorporates by reference paragraphs 1 through 30 above. On December 1, 2009, United States Patent No. 7,627,343 (the 343 patent) was
duly and legally issued for an invention entitled: Media Player System. Apple is the assignee of the 343 patent and continues to hold all rights and interest in the 343 patent. A copy of the 343 patent is attached hereto as Exhibit A.

and legally issued for an invention entitled: Docking Station. Apple is the assignee of the 621 patent and continues to hold all rights and interest in the 621 patent. A copy of the 621 patent is attached hereto as Exhibit I. 73. Defendants Eforcity, Accstation, Itrimming, Everydaysource, Crazyondigital, and
Boxwave have directly infringed and continue to directly infringe the 621 patent through their manufacture, use, sale, importation and/or offer for sale of unlicensed iPod and/or iPhone accessories including, but not limited to, Boxwaves Desktop Cradle Apple iPhone 3G product, Crazyondigitals iPhone3G_Plastic_CRADLE product, and the following products of Eforcity, Accstation, Everydaysource, and Itrimming: DAPPIPODCR10, DAPPIPODCR11, and DAPPIPODCR12. Apple anticipates that additional infringing products will be found and will duly accuse such products as discovery progresses. Said Defendants advertisements and marketing materials, including but not limited to internet websites, encourage customers to infringe the 621 patent through use of the identified products with the iPod and/or iPhone devices. The identified products are especially made or especially adapted for use with the iPod and/or iPhone devices in a manner that infringes the 621 patent, are not staple articles or commodities of commerce, and are not suitable for substantial noninfringing use.

- 17 -

Filed07/22/10 Page18 of 113
Said Defendants infringement of the 621 patent has caused and continues to cause
damage to Apple in an amount to be determined at trial. Apple is also entitled to an award of Defendants profits derived from the infringement pursuant to 35 U.S.C. 289. 75. Said Defendants infringement as herein alleged will continue to cause immediate
and irreparable harm to Apple for which there is no adequate remedy at law, unless this Court enjoins and restrains such activities. TENTH CLAIM FOR RELIEF (Infringement of U.S. Patent No. D578,110) (Against Defendants Eforcity, Accstation, Itrimming, Everydaysource, and Crazyondigital) 76. 77. Apple incorporates by reference paragraphs 1 through 30 above. On October 7, 2008, United States Patent No. D578,110 (the 110 patent) was duly

computer). For example, in the case of a music player, a user may use the device while working out at the gym. In case of a camera, a user may use the device while mountain climbing. In the case of a game player, the user can use the device while traveling in a car. Furthermore, the device may be operated by the users hands, no reference surface such as a desktop is needed. In the illustrated embodiment, the media player 100 is a pocket sized hand held MP3 music player that allows a user to store a large collection ofmusic (e.g., in some cases up to 4,000 CD-quality songs). Although used primarily for storing and playing music, the MP3 music player shown herein may also include additional functionality such as storing a calendar and phone lists, storing and playing games, storing photos and the like. In fact, in some cases, it may act as a highly transportable storage device. By way ofexample, the MP3 music player may correspond to the Ipod MP3 player manufactured by Apple Computer of Cupertino, Calif. The pocket sized Ipod has a width of about 2.4 inches, a height ofabout 4 inches and depths ranging from about 0.72 to about 0.84 inches. As shown in FIG. 1, the media player 100 includes a housing 102 that encloses internally various electrical components (including integrated circuit chips and other circuitry) to provide computing operations for the media player 100. In addition, the housing may also define the shape or form of the media player. That is, the contour of the housing 102 may embody the outward physical appearance of the media player 100. The integrated circuit chips and other circuitry contained within the housing may include a microprocessor (e.g., CPU), memory (e.g., ROM, RAM), a power supply (e.g., battery), a circuit board, a hard drive, other memory (e.g., flash) andlorvarious input/output (I/O) support circuitry. The electrical components may also include components for inputting or outputting music or sound such as a microphone, amplifier and a digital signal processor (DSP). The electrical components may also include components for capturing images such as image sensors (e.g., charge coupled device (CCD) or complimentary oxide semiconductor (CMOS)) or optics (e.g., lenses, splitters, filters). The electrical components may also include components for sending and receiving media (e.g., antenna, receiver, transmitter, transceiver, etc.). In the illustrated embodiment, the media player 100 includes a hard drive thereby giving the media player massive storage capacity. For example, a 20 GB hard drive can store up to 4000 songs or about 266 hours of music. In contrast, flash-based media players on average store up to 128 MB, or about two hours, of music. The hard drive capacity may be widely varied (e.g., 5,10,20 MB, etc.). In addition to the hard drive, the media player 100 shown herein also includes a battery such as a rechargeable lithium polymer battery. These type of batteries are capable of offering about 10 hours of continuous playtime to the media player. The media player 100 also includes a user interface 103. The user interface 103 allows the user ofthe media player 100 to initiate actions on the media player 100 and provides the user with output associated with using the media player (e.g., audio, video, images, etc.). The user interface 103 may be widely varied. By way ofexample, the user interface 103 may include switches, buttons, keys, dials, trackballs, joysticks, touch pads, touch screens, displays, microphones, speakers, cameras, and the like. In the illustrated embodiment, the media player 100 includes a display screen 104 and related circuitry. The display screen 104 is used to display a graphical user interface as well as other information to the user (e.g., text, objects, graphics). By way of example, the display screen 104 may be a

(AC, DC), and/or the like. In most cases, the data corresponds to data associated with the media player as for example audio, video, images and the like. Both the media player 152 and the media device 154 include a media terminal 158A and 158B, respectively. The media terminals 158 may provide a direct connection between the media player 152 and the media device 154 (e.g., integrally formed with the media device) or it may provide an indirect connection between the media player 152 and the media device 154 (e.g., a stand alone device). The media terminals 158 provide the media link 156 through one or more connection interfaces. As such, the media player 152 may serve the media devices 154 and/or the media devices 154 may serve the media player 152. The connection interfaces associated with the media terminals 158 may be wired or wireless connection interfaces. In wired connections, the media terminals 158 are configured to physically connect so as to operatively couple the media player 152 to the media device 154. For example, the media player 152 and the media device 154 may include a mating connection made up of connector and port. By way of example, the connection interface may include one or more of the following interfaces: PS/2, serial, parallel, network (e.g., Ethernet), USB, Firewire and/or the like. The connection interface may also include one or more remote, audio (digital or analog), video (digital or analog), and/or charging interfaces. In one embodiment, the media terminal 158B is a part of docking station that permits the media player 152 to connect with the media device 154. The docking station may be integrally formed with the media device 154 thereby providing a direction connection with the media player 152 or it may be a standalone device that provides an indirect connection between the media player 154 and the media device 152. In wireless connections, the media terminals 158 do not physically connect. For example, the media player 152 and the media device 154 may include a receiver and transmitter for wireless communications therebetween. By way of example, the connection interface may include one or more of the following interfaces: FM, RF, Bluetooth, 802.11 UWB (ultra wide band), IR, magnetic link (induction) and/or the like. In brief, FM (frequency modulation) is a method of impressing data onto an alternating-current (AC) wave by varying the instantaneous frequency of the wave. This scheme can be used with analog or digital data. RF generally refers to alternating current AC having characteristics such that, if the current is input to an antenna, an electromagnetic field is generated suitable for wireless broadcasting and/or communications. The frequencies associated with RF cover a wide range of the electromagnetic radiation spectrum as for example from about 9 kHz to thousands of GHz. Bluetooth generally refers to a computing and telecommunications industry specification that describes how mobile phones, computers and personal digital assistants can easily interconnect with each other using short range wireless connection. 802.11 generally refers to a family of specification for wireless local area networks (WLANs) developed by a working group of the Institute of Electrical and Electronics Engineers (IEEE). UWB refers to a wireless technology for transmitting large amounts of digital data over a wide spectrum of frequency bands with very low power for a short distance. IR generally refers wireless technologies that convey data through infrared radiation. FIGS. 3 and 4 are diagrams of docking stations 170 and 172, respectively, in accordance with several embodiment of the present invention. The docking stations 170 and 172 are hardware components that include a set of connection inter-

Filed07/22/10 Page46 of 113

US 7,627,343 B2 9

faces that allow a media player 174 to communicate with other media devices (not shown) that are not usually taken along with the media player 174. That is, the docking stations 170 and 172 make available additional functionality that would not otherwise be achieved through the media player 174 and/or the other media devices. The docking stations 170 and 172 may be built into the media device (e.g., hard wired) or they may be stand-alone devices that are connected to the media device through a separate connection (e.g., cord). By way of example, the media player 174 may generally correspond to the media player shown in FIG. 1. As shown, each ofthe docking stations includes a housing 178. The housings 178 are configured with a media bay 180 capable of receiving the media player 174 for direct or indirect connection to a media device. The media bay 180 includes a media bay opening 182 in the surface 184 of the housing 178. The media bay opening 182 is configured to physically receive the media player 174. In other words, the media player 174 can be inserted into the media bay opening 182. Once the media player 174 is inserted into the media bay opening 182 (as shown in FIGS. 3B and 4B), the functionality provided by a media device operatively coupled to the docking stations 170 and 172 becomes available for use by the media player 174. Additionally or alternatively, the functionality provided by the media player 174 may become available for use by the media device operatively coupled to the docking stations 170 and 172. Inmost cases, a connector 186 ofthe media player 174 couples to a corresponding connector 188 within the media bay 180 when the media player 174 is placed in the inserted position. The media player 180 essentially becomes a fixed location device when coupled to the docking stations 170 and 172 through the media bay 180 (unless the docking station happens to be in another mobile device). When the media player 174 is taken out, it becomes mobile again. As should be appreciated, the docking stations 172 and 174 let a user simultaneously enjoy expansion possibilities with the portability of a smaller device. The media bays 180 of the docking stations 170 and 172 may be widely varied. In most cases, the media bay openings 182 are dimensioned to receive the media players 174. That is, the inner peripheral surfaces of the media bay openings 182 are sized to receive the outer peripheral surfaces ofthe media player 174 (allowing for some tolerances). In FIG. 3, the media bay 180 is configured to receive the back end of the media player 174 while in FIG. 4 the media bay 180 is configured to receive a bottom end ofthe media player174. In either case, the connector 186 on the media player 174 is configured to connect with the connector 188 on the docking station 170 and 172 when the media player 174 is inserted in the media bay 180. The position of the inserted media player 174 relative to the housing 178 may be widely varied. For example, the media bay 180 may be configured to receive the entire media player 174 as shown in FIG. 3 or it may only be configured to receive a portion of the media player 174 as shown in FIG. 4. The inserted media player 174 is typically retained within the media bay 180 until it is removed from the media bay 180 (e.g., doesn't slide out). For example, a retention mechanism such as a snap, a spring loaded latch or a magnet may be used to hold the media player 174 within the media bay opening 182. The media player 174 may also be held within the opening 182 by the force of the engaged connectors 186/188 or under its own weight (e.g., gravity). An ejection mechanism may additionally be used to release the media player 174 from the media bay 180 (e.g., to overcome any holding forces). In some cases (as shown inFIG. 3), the user interface 175 ofthe media player 174 is completely exposed to the user

Filed07/22/10 Page53 of 113
9. A male plug connector for connecting to a corresponding receptacle connector of a media player, the male plug connector comprising: a housing designed to accommodate 30 contacts spaced apart in a single row of sequentially numbered contact locations, wherein the sequentially numbered contact locations include: digital contact locations 3 to 9 designated for digital signals including USB contact locations designated for USB signals interleaved with contact locations designated for other digital signals to improve impedance matching; analog contact locations 25 to 28 designated for one or more analog signals including at least one audio signal; and ground contact locations 1, 16 and 30 designated for ground, wherein, analog contact locations 25 to 28 are spaced apart from digital contact locations 3 to 9 to reduce crosstalk noise, and wherein locations 1, 16 and 30 are designated for ground contacts to improve ground coverage. 10. The male plug connector of claim 9, wherein the sequentially numbered contact locations further include ground contact locations 2, 15, and 29 designated for ground. 11. The male plug connector of claim 9, further comprising: digital contacts disposed contact locations 3 to 9 and appropriated for carrying the digital signals; analog contacts disposed at contact locations 25-28 and appropriated for carrying the analog signals; and ground contacts disposed at contact locations 1 and 30 and appropriated for ground, wherein at least a subset of the plurality of contacts can be active when the plug connector is connected to the corresponding receptacle connector of the media player. 12. The male plug connector of claim 9, wherein the sequentially numbered contact locations further include an accessory identifY contact location 10 designated for an accessory identifY signal that has an associated electrical pull down function to notifY the media player of an accessory identification. 13. The male plug connector of claim 9, wherein the sequentially numbered contact locations further include: an accessory power contact location 13 designated for an accessory power signal that can receive power from the media player; and an accessory detect contact location 20 designated for an accessory detect signal. 14. The male plug connector of claim 9, wherein the sequentially numbered contact locations further include: serial protocol contact locations 18 and 19 designated for serial protocol signals. 15. The male plug connector of claim 9, wherein contact locations 3, 5, 7 and 9 are designated for Firewire signals. 16. The male plug connector of claim 9, wherein locations 4, 6, and 8 are designated for USB signals. 17. The male plug connector of claim 9, wherein the housing is made of plastic; wherein the contacts are made ofan electrically conductive material, are disposed in a corresponding one of the sequentially numbered contact locations for the 30 contacts, and are recessed inside the housing in an off-center position; and wherein at least one contact is made of a copper alloy. 18. The male plug connector of claim 9, wherein the housing further comprises a latch that engages and disengages and

PATENT NO. APPLICATION NO. DATED INVENTOR(S) : 7,627,343 B2 : 10/423490 : December 1,2009 : Anthony M. Fadell et aI. Page 1 of 1
It is certified that error appears in the above-identified patent and that said Letters Patent is hereby corrected as shown below:
In column 3, line 32, after "invention" insert --. --.
Signed and Sealed this Twenty-fifth Day of May, 2010
David J. Kappas Director ofthe United States Patent and Trademark Office
Filed07/22/10 Page56 of 113

EXHIBIT B

Filed07/22/10 Page57 of 113
111111111111111111111111111111111111111111111111111111111111111111111111111 US007305506Bl

Lydon et al.

METHOD AND SYSTEM FOR TRANSFERRING STATUS INFORMATION BETWEEN A MEDIA PLAYER AND AN ACCESSORY Inventors: Gregory T. Lydon, Santa Cruz, CA (US); Lawrence G. Bolton, Fremont, CA (US); Emily C. Schubert, Los Altos, CA (US); Jesse Dorogusker, Menlo Park, CA (US); Donald J. Novotney, San Jose, CA (US); John B. Filson, San Jose, CA (US); David Tupman, San Francisco, CA (US) Assignee: Apple Inc., Cupertino, CA (US) Notice: Subject to any disclaimer, the term of this patent is extended or adjusted under 35 U.S.c. 154(b) by 0 days.
Patent No.: US 7,305,506 Bl Date of Patent: Dec. 4, 2007
4/2004 Hutchison et al. 8/2004 Kubota et al. 8/2005 Payne et al. 5/2006 Curtiss et al. 6/2006 Goldstein et al. 1112003 Hymel 5/2004 Gabehart et al. 1112004 Fadell et al. 1/2005 Findikli 8/2006 de Janasz.. 710/9 455/404.1 455/419 715/744 709/220. 710/2 455/66.1 455/557 705/72 455/557
6,725,061 Bl 6,776,660 Bl
6,931,456 B2 * 7,050,783 B2 * 7,062,261 B2 * 2003/0220988 Al 2004/0103223 2004/0224638 2005/0014531 2006/0184456
7,127,678 B2 * 10/2006 Bhesania et al.

* Al * Al * Al * Al *

Primary Examiner-Raymond N Phan (74) Attorney, Agent, or Firm-Townsend and Townsend and Crew LLP

(21) (22)

Appl. No.: 111476,262 Filed: Jun. 27, 2006 Related U.S. Application Data

(63) (51) (52) (58)

Continuation-in-part of application No. 10/833,689, filed on Apr. 27, 2004. Int. Cl. G06F 13/42 U.S. Cl.
(2006.01) 710/105; 710/300; 710/72; 710/63; 710/64 710/300-315, Field of Classification Search 710/62-66,8-13,72, 104-105; 455/557, 455/575; 719/312,327; 709/321,220 See application file for complete search history. References Cited U.S. PATENT DOCUMENTS
A method, system, and connector interface for transferring status information between a media player and an accessory. The method includes determining, by the accessory, when a button event occurs; and transmitting, by the accessory, at least one button status command to the media player, where the one or more button status commands comprise a contextspecific button status command and at least one command associated with a particular media type. According to the method and system disclosed herein, the media player and accessory may utilize a plurality of commands in a variety of environment such as within a connector interface system environment to facilitate the transfer of status information. 30 Claims, 11 Drawing Sheets

6,453,371 Bl

9/2002 Hampson et al.

710/37

Determining when a button event occurs

V- 602

Transmitting at least one button status packet

V- 604

Transmitting at least one acknowledgement status packet in response to at least one button status packet
Filed07/22/10 Page58 of 113

Patent

Dec. 4, 2007

Sheet 1 of 11

US 7,305,506 Bl
r_----A'"-----"\
Filed07/22/10 Page59 of 113

Sheet 2 of 11

lb~204

FIG.2A

Power 3.3V

Ground

FIG. 28

FIG.2C

Filed07/22/10 Page60 of 113

Sheet 3 of 11

Signal N3me 1 DGND

F'uJ1ction

Digital Ground Digital Ground rirewirc si~nai USB signal fir~wirc siRTIs.! USB signal Firewil'e si~nal USB power in. NOT for powering; only to detect USB host Firewire signal l'uU down in dock to notU}" iPod of specific device F'ircwire and cbarger input power (8V to 30V dt)

3 TP.4.+ 5 TPA 6 USB l).

USBPWR

flO flO 1/0

IPSAccessory [dcntify flW P\\IRt
Ff"IPWR+ ACce~Sf)r1' Pwr(3V3) Reserved
Firewire and cbar2'cr input power (8V tft 311Y de) 3.3V output (mm iPod. Current limited to WOntA.
GND Digital Ground.in iPod GND Digi tal Gnmud in iFod

17 Reserved

DockTx DockRx

Accessory Detect

S Video Y

0 I/O 0

Serial pr(jt<Jcol (Data to iPod) Serial prowell} (Data from iPQd)

Lmnrnaflce COIDlWneut

22 S Video C
13 Video Composite 24 Remote Sense 25 LINE-IN L Z6 L[NE-L~R

Chromin311ce Component

LIKE-OUTL LINE-OUTR

29 Audio Return

30 DGND 31 Chassis 32 Chassis
CGmposite Signal I Detect Remote r Line level input to the iPod for the feft channel r Line level input to the iPod (or the right cbannd 0 IAlll~ level output to the iPod lor tbe left channel 0 Line level output to the iPod for tbe ri~ht channel Gl\1J Audio return - Si~nlll never to be gr(lUnded il1side accessory GND Digital Ground iPod Chassis ground for connector shell Cbassis ground for coul1ech)1' shelf
Filed07/22/10 Page61 of 113
[;". b r.reWIre onter SIeId -~ -----I

M"

".'
. -. - - --. - - - -- - - - -- - - - - - - - - -- - - - - - - - ~TPA SHIELD - - -~ Fir.cwireTPA.+(Green)=>c<

~i!~'.Y!r~

I 1- - - I - -. - - - - -. -.
.IFA-1R.e~L ____ ___ ____ __ _" Fire-wire TPS+- (Bluef. -. --. --. -:.

3 ! "

'.I. - -. _. - -. - - - -
v> ~ (' IreWlre 'CPs - (0ranae. _. - _. - - - _. -. - - - ~. "TPB SHIELD- - _"

BACKGROUND OF THE INVENTION A media player stores media assets, such as audio tracks or photos that can be played or displayed on the media player. One example of a media player is the iPod media player, which is available from Apple Computer, Inc. of Cupertino, Calif. Often, a media player acquires its media assets from a host computer that serves to enable a user to manage media assets. As an example, the host computer can execute a media management application to manage media assets. One example of a media management application is iTunes, version 6.0, produced by Apple Computer, Inc. A media player typically includes one or more counectors or ports that can be used to interface to the media player. For example, the connector or port can enable the media player to couple to a host computer, be inserted into a docking system, or receive an accessory device. There are today many different types of accessory devices that can interconnect to the media player. For example, a remote control can be connected to the connector or port to allow the user to remotely control the media player. As another example, an automobile can include a connector and the media player can be inserted onto the connector such that an automobile media system can interact with the media player, thereby allowing the media content on the media player to be played within the automobile. With the introduction of various media types (images and video), communication between a media player and an accessory may be confusing to end users. Furthermore, it may be difficult to determine, if at all, whether information has been successfully transferred between a media player and an accessory. Thus, there is a need for improved techniques to enable manufacturers of electronic devices to exchange information. SUMMARY OF THE INVENTION A method, system, and connector interface for transferring status information between a media player and an accessory is disclosed. The method includes determining, by the accessory, when a button event occurs; and transmitting, by the accessory, at least one button status command to the media player, where the one or more button status commands comprise a context-specific button status command and at least one command associated with a particular media type.
Filed07/22/10 Page70 of 113
command, a video status button command, and an audio button status command. The media player may then transmit at least one acknowledgement status command to the accessory in response to the button status command. The media player and the accessory may utilize status commands, which may include commands associated with dedicated button status commands for different media types (e.g. image/slideshow, video, audio, etc.). The commands provide media control commands that support not only basic buttons such as play/pause, volume up, volume down, next track, and previous track but also media control commands that support context specific buttons such as next album, previ0us album, down arrow, etc. The media player and accessory may utilize the plurality of commands utilized in a variety of envirouments to facilitate the transfer of status infonnation. One such environment is within a connector interface system environment such as described in detail hereinbelow. Connector Interface System Overview To describe the features of the connector interface system in accordance with the present invention in more detail, refer now to the following description in conjunction with the accompanying drawings. Docking Connector FIGS. 1A and 1B illustrate a docking connector 100 in accordance with the present invention. Referring first to FIG. lA, the keying features 102 are of a custom length 104. In addition, a specific key arrangement is used where one set of keys is separated by one length at the bottom of the connector and another set of keys is separated by another length at the top of the connector. The use of this key arrangement prevents noncompliant connectors from being plugged in and causing potential damage to the device. The connector for power utilizes a Firewire specification for power. The connector includes a first make/last break contact to implement this scheme. FIG. 1B illustrates the first make/last break contact 202 and also illustrates a ground pin and a power pin related to providing an appropriate first make/last break contact. In this example, the ground pin 204 is longer than the power pin 206. Therefore, the ground pin 204 would contact its mating pin in the docking accessory before the power pin 206, minimizing internal electrical damage to the electronics of the device. In addition, a connector interface system in accordance with the present invention uses both USB and Firewire interfaces as part of the same docking connector alignment, thereby making the design more compatible with different types of interfaces, as will be discussed in detail hereinafter. In so doing, more remote accessories can interface with the media player. Remote Connector The connection interface system also includes a remote connector which provides for the ability to output and input audio, and output video and which also provides I/O serial protocol. FIG. 2A is a front and top view of a remote connector 200 in accordance with the present invention. As is seen, the remote connector 200 includes a top headphone receptacle 202, as well as a second receptacle 204 for remote devices. FIG. 2B illustrates a plug 300 to be utilized in the remote connector. The plug 300 allows the functions to be provided via the remote connector. FIG. 2C illustrates the plug 300 inserted into the remote connector 200. Heretofore, all of these features have not been implemented in a remote connector. Therefore, a standard headphone cable can be plugged in, but also special remote control cables, microphone cables, and video cables could be utilized with the remote connector.

DETAILED DESCRIPTION The present invention relates generally to multi-communication devices and more particularly to a connector interface system for such devices. The following description is presented to enable one of ordinary skill in the art to make and use the invention and is provided in the context of a patent application and its requirements. Various modifications to the preferred embodiment and the generic principles and features described herein will be readily apparent to those skilled in the art. Thus, the present invention is not intended to be limited to the embodiment shown but is to be accorded the widest scope consistent with the principles and features described herein. Connector System Overview To describe the features of the connector system in accordance with the present invention in more detail, refer now to the following description in conjunction with the accompanying drawings. Docking Connector FIGS. 1A and 1B illustrate a docking connector 100 in accordance with the present invention. Referring first to FIG. lA, the keying features 102 are of a custom length 104. In addition, a specific key arrangement where one set ofkeys are separated by one length are at the bottom and another set of keys are separated by another length at the top ofthe connector is used. The use ofthis key arrangement prevents noncom-
Filed07/22/10 Page86 of 113
pliant connectors from being plugged in and causing potential damage to the device. The connector for power utilizes a Firewire specification for power. The connector includes a first make/last break contact to implement this scheme. FIG. IB illustrates the first make/last break contact 202 and also illustrates a ground pin and a power pin related to providing an appropriate first mate/last break contact. In this example, the ground pin 204 is longer than the power pin 206. Therefore, the ground pin 204 would contact its mating pin in the docking accessory before the power pin 206. Therefore internal electrical damage of the electronics of the device is minimized. In addition, a connector interface system in accordance with the present invention uses both USB and Firewire interfaces as part of the same docking connector alignment, thereby making the design more compatible with different types of interfaces, as will be discussed in detail hereinafter. In so doing, more remote systems and devices can interface with the multi-communication device. Remote Connector The connection interface system also includes a remote connector which provides for the ability to output audio, input audio, and output video using an I/O serial protocol. FIG. 2A is a front and top view of a remote connector 200 in accordance with the present invention. As is seen, the remote connector 200 includes a top headphone receptacle 202, as well as, a second receptacle 204 for remote devices. FIG. 2B illustrates a plug 300 to be utilized in the remote connector. The plug 300 allows the features to be provided via the remote connector. FIG. 2C illustrates the plug 300 inserted into the remote connector 200. Heretofore, all these features have not been implemented in a remote connector. Therefore, a standard headphone cable can be plugged in but also special remote control cables, microphone cables, video cables could be utilized with the remote connector. Serial Protocol The connector interface system also includes a serial protocol. The protocol is utilized to allow external devices to control the multi-communication device. These controls help a user sort and display for data more efficiently utilizing the device. A representation list of controls includes, but are not limited to: Next album Previous album Next chapter Previous chapter Next play list Previous play list Shuffle setting advance Repeat setting advance Backlight for 30 seconds Begin fast forward Begin rewind To describe the features of the connector interface system in more detail, please find below a functional description of the docking connector, remote connector and a serial protocol in accordance with the present invention. Docking and Remote Connector Specifications For an example of the connector pin designations for both the docking connector and for the remote connector for a multi-communication device such as an iPod device by Apple Inc., refer now to FIGS. 3A and 3B. FIG. 3A illustrates the connector pin designations for the docking connector. FIG. 3B illustrates the connection pin designations for the remote connector.

Filed07/22/10 Page87 of 113
contents only. This means that no packet is valid for sending from both the host and device. All devices must be able to handle variable-length packets. For example, even though an identifY packet currently has no defined data, a device must be able to understand an identify packet with data and should respond to the best of its ability. It must at least not lose sync to the packet signaling.
Lingo Specifications Lingo General Microphone Simple Remote Display Remote RF transmitter
Simple Remote Button Map Button Play/Pause Volume Up Volume Down Next Track Previous Track Next Album Previous Album Stop Play/Resume Pause Mute toggle Next Chapter Previous Chapter Next Playlist Previous Playlist Shuffle setting advance Repeat setting advance Power On Power Off Backlight for 30 seconds Begin FF BeginREW Number Byte No, Mask

OxOO OxOl Ox02 Ox03 Ox05

The general lingo is shared for housekeeping commands 20 across all devices. The microphone lingo is used by the remote connector on the multi-communication device. The simple remote lingo is used by a standard in-line remote control. The display remote lingo is reserved for a device with similar functionality to the standard remote but with a display 25 for status.
O,OxOl 0,Ox02 0,Ox04 0,Ox08 0, Ox10 0,Ox20 0,Ox40 0,Ox80 1,0xOl I,Ox02 I,Ox04 I,Ox08 1, Ox10 I,Ox20 I,Ox40 I,Ox80 2,OxOl 2,Ox02 2,Ox04 2,Ox08 2, Ox10 2,Ox20
General Lingo Specification Command Request identifY Identify

Data Length

OxOO OxOl

OxOO OxOl+ 35

The host may send a request identifY to the device to ask the device to reidentifY itself. The device sends an identify packet to identify itself. At this time multifunction (combo) devices are not supported. 40 The identifY data payload is thus the command ID OxOl followed by a single byte of the same value as the lingo specification of the functionality the device implements unless specified otherwise. The identifY packet returned in response to a request identifY packet does not need to have the 45 extra sync bytes and delays used during the startup process.
Simple Remote Lingo Specification Command Buttons status
A simple remote device sends a buttons status command to indicate an updated status of which buttons are held down. The data of the packet is a number of bytes indicating which buttons are currently held down. The bytes are made up by ORing the masks ofthe buttons together. The device will send a OxOO in data (or no data) to indicate all buttons are released. While any buttons are held down the device should repeat this packet on a predetermined interval. If no packet ofthis sort is received by the host for 200 ms the host may assume a packet was lost and go to "all buttons up" mode. A representative simple remote button map is shown below:

determine when the control is no longer activated; and transmit another button status command to the multi-communication device comprising a button status bitmask with all status bits set to a state indicating that a corresponding control is not activated. 13. The protocol of claim 9 wherein the accessory is configured to continuously transmit the button status command to the multi-communication device at a predetermined interval while the control remains activated. 14. An accessory capable of being communicatively coupled with a multi-communication device, the accessory comprising: a plurality of controls; and a control component configured to: determine when a control in the plurality of controls is activated; and transmit a button status command to the multi-communication device comprising a button status bitmask, the button status bitmask including a status bit associated with each of the plurality of controls, wherein the plurality of controls includes a play/pause control, a volume up control, and a volume down control, and wherein the play/pause, volume up, and volume down controls are associated with status bits corresponding to a first lowest-order bit, a second lowest-order bit, and a third lowest-order bit respectively. 15. The accessory of claim 14 wherein the button status bitmask further includes a fourth lowest-order bit corresponding to next track, a fifth lowest-order bit corresponding to previous track, a sixth lowest-order bit corresponding to next album, a seventh lowest-order bit corresponding to previous album, and an eighth lowest-order bit corresponding to stop. 16. The accessory of claim 14 wherein the control component is further configured to: determine when the control is no longer activated; and transmit another button status command to the multi-communication device comprising a button status bitmask with all status bits set to a state indicating that a corresponding control is not activated. 17. The accessory of claim 14 wherein the control component is further configured to continuously transmit the button status command to the multi-communication device at a predetermined interval while the control remains activated. 18. The accessory of claim 14 wherein the button status command is transmitted via a connector of the accessory. 19. The accessory of claim 18, wherein the connector includes: a plurality of pins configured to mate with a corresponding plurality of pins of a connector of the multi-communication device; and an accessory-identifying resistor connected between two of the plurality of pins. 20. A multi-communication device capable of being communicatively coupled with an accessory, the multi-communication device comprising: a plurality of controls; and a control component configured to: determine when a control in the plurality of controls is activated; and transmit a button status command to the accessory comprising a button status bitmask, the button status bitmask including a status bit associated with each ofthe plurality of controls,

Filed07/22/10 Page89 of 113

US 7,587,540 B2 9

of an accessory, cause the accessory to transfer button status wherein the plurality of controls includes a play/pause control, a volume up control, and a volume down coninformation to a multi-communication device, the program trol, and code comprising: wherein the play/pause, volume up, and volume down concode instructing the control component to determine when trols are associated with status bits corresponding to a a control in a plurality of controls is activated; and first lowest-order bit, a second lowest-order bit, and a code instructing the control component to transmit a button third lowest-order bit respectively. status command to the multi-communication device, the 21. The multi-communication device of claim 20 wherein button status command comprising a button status bitthe button status bitmask further includes a fourth lowestmask, the button status bitmask including a status bit order bit corresponding to next track, a fifth lowest-order bit 10 associated with each of the plurality of controls, corresponding to previous track, a sixth lowest-order bit corwherein the plurality of controls include a play/pause conresponding to next album, a seventh lowest-order bit corretrol, a volume up control, and a volume down control, sponding to previous album, and an eighth lowest-order bit and corresponding to stop. wherein the play/pause, volume up, and volume down con22. The multi-communication device of claim 20 wherein 15 trols are associated with status bits corresponding to a the control component is further configured to: first lowest-order bit, a second lowest-order bit, and a determine when the control is no longer activated; and third lowest-order bit respectively. transmit another button status command to the accessory 27. The computer-readable medium of claim 26 wherein comprising a button status bitmask with all status bits set the button status bitmask further includes a fourth lowestto a state indicating that a corresponding control is not 20 order bit corresponding to next track, a fifth lowest-order bit activated. corresponding to previous track, a sixth lowest-order bit cor23. The multi-communication device of claim 20 wherein responding to next album, a seventh lowest-order bit correthe control component is further configured to continuously sponding to previous album, and an eighth lowest-order bit transmit the button status command to the accessory at a 25 corresponding to stop. predetermined interval while the control remains activated. 28. The computer-readable medium of claim 26, wherein 24. The multi-communication device of claim 20 wherein the program code further comprises: the button status command is transmitted via a connector of code instructing the control component to determine when the multi-communication device. the control is no longer activated; and 25. The multi-communication device of claim 24 wherein code instructing the control component to transmit another 30 the connector comprises: button status command to the multi-communication a plurality of pins configured to mate with a corresponding device comprising a button status bitmask with all status plurality of pins of a connector of the accessory; and bits set to a state indicating that a corresponding control an accessory-identifying resistor connected between two is not activated. of the plurality of pins. 26. A computer-readable medium having stored thereon 35 program code which, when executed by a control component * * * * *

NOTES If KTSync Setup Wizard locates an older version of KTSync on your computer, you will be prompted to remove the older program before installing the new version. Select Remove KTSync then click Finish. When removal is complete, click Close. Go to Step 2 to run KTSync Setup Wizard. If you have any problems, please refer to the Manual Installation section.

KTSync Setup Wizard

Below are the screen images you will see during the installation of KTSync.
Click Next icon in KTSync Setup Wizard window
KDC300 User Manual Click Next icon in KTSync Confirm Installation window
Within a few minutes, installation of KTSync will be complete. Click Close icon and wait for the Device Driver Installation Wizard to load.
Device Driver Installation Wizard
Below are the screen images you will see during the installation of the KDC Device Driver.
Click Next icon in Device Driver Installation Wizard window
Click Continue Anyway icon in Software Installation Logo testing window
Click Finish icon in Device Driver Installation Wizard window

Connect KDC to Computer

Using the USB cable included with the KDC, follow the directions below. Connect the cables ultra mini USB connector to the KDC. Connect the cables Type A USB connector to your PC. Wait until your computer beeps and/or displays the message Found New Hardware.
Found New Hardware Wizard
Select No, not this time option in Found New Hardware Wizard and click Next if your PC pops up the following Found New Hardware Wizard.
Select Install the software automatically (Recommended) option in Found New Hardware Wizard and click Next if your PC pops up the following Found New Hardware Wizard.
KDC300 User Manual Click Continue Anyway icon in Software Installation Logo testing window
Click Finish icon in Found New Hardware Wizard window

Verify COM Port Address

User can verify installed COM Port in Device Manager

Vista and Windows 7

Click Close icon in KTSync Installation Complete window and wait for Device Driver Installation Wizard
Click Install this driver software anyway in Windows Security window
KDC300 User Manual Click Finish icon in Device Driver Installation Wizard window
Using the USB cable included with the KDC, follow the directions below. Connect ultra mini USB connector to the KDC. Connect Type A USB connector to your PC. Wait until your computer beeps and/or displays the message Found New Hardware.

Windows Mobile 5.0+

WARNING: PLEASE CONNECT PDA TO PC PRIOR TO INSTALLATION
1. PC_Setup.exe creates Mobile_Setup.exe file under C:\Program Files\KoamTac\KTSync\Windows.Mobile directory 2. Execute Mobile_Setup.exe
Select Windows Mobile version to install.

Click Next icon.

KDC300 User Manual Click OK icon in Pending Application Install window

Synchronizing Barcode Data to PC
Use the KTSync program to synchronize barcode data from the KDC to your PC. Please refer to Chapter 4 for details.

3.3 KDC Menus

Default Top Menu Sub Menu Options KDC100
Normal Default Custom Application View/Delete Data Enabled/Disabled Enabled/Disabled Enabled/Disabled Enabled/Disabled Enabled/Disabled Enabled/Disabled Enabled/Disabled Enabled/Disabled Enabled/Disabled Enabled/Disabled Enabled/Disabled Enabled/Disabled Enabled/Disabled Enabled/Disabled Enabled/Disabled Enabled/Disabled Enabled/Disabled Codabar Code 11 Code 32 Code 39 Code 93 Code 128 EAN-8 EAN-13 Enable Enable Enable Enable Enable Enable Enable Enable Enable Enable Enable Enable Disable Disable Disable Disable Disable N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A

KDC200(i)

Default Custom Application View/Delete Data Enable Enable Enable Enable Enable Enable Enable Enable Enable Enable Enable Enable Disable Disable Disable Disable Disable N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A

KDC250(Gi)

KDC300(i)
Default Custom Application View/Delete Data N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A Enable Enable Enable Enable Enable Enable Enable Enable Enable Enable Enable Enable Enable Enable Enable Enable Enable Enable

KDC Mode

Application

View Data

View/Delete EAN13 EAN8 UPCA UPCE CODE39 ITF14 CODE128 I2of5
Set Barcodes (100/200/250)
CODABAR GS1-128 CODE93 CODE35 BooklandEAN EAN13withAddon EAN8withAddon UPCAwithAddon UPCEwithAddon

Set Barcodes (300)

GS1 Composit 1D Symbology I2of5 Matrix 2of5 MSI Plessey PosiCode GS1 Omni GS1 Limited GS1 Expanded S2of5 Ind
S2of5 IATA TCL39 Telepen Trioptic UPCA UPCE0 UPCE1 AztecCode AztecRunes CodablockF Code16K Code49 2D Symbology DataMatrix MaxiCode MicroPDF PDF417 QRCode HanXin Code Postnet PlanetCode UK Post Canada Post Postal Codes Kix Post Australia Post Japan Post China Post Korea Post OCR Off OCR A OCR B OCR OCR USC OCR MICR OCR SEMI CodaBar_NoStartStopChars UPCE_as_UPCA EAN8_as_EAN13 UPCE_as_EAN13 Enabled/Disabled Enabled/Disabled Enabled/Disabled Enabled/Disabled Enabled/Disabled Enabled/Disabled Enabled/Disabled Enabled/Disabled Enabled/Disabled Enabled/Disabled
N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A Disable Disable Disable Disable Disable Disable Disable Disable Disable Disable

N/A N/A N/A N/A N/A N/A N/A N/A Wide Normal 2 second(s) 4 chars N/A 2 level Disable Medium Enabled chars Select
Disable Enable Disable A&B LimitedB Disable No Emulate Disable Disable N/A N/A 2 second(s) N/A 4 chars N/A Disable Medium N/A chars Select
PostNet PlanetCode Scan Angle Filter Time Out Min. Barcode Length Min. Barcode Length Security Level

Scan Options

Auto Trigger Reread Delay Finger Trigger

Default

Data Process
Data Editor/Prefix Data Editor/Suffix Data Editor/AIM ID
Delete Delete None/In Prefix/In Suffix Start Position
Delete Delete None chars Select Disable CR+LF Disable N/A N/A N/A N/A N/A N/A N/A
Delete Delete None chars Select Disable CR+LF Disable Default (200)
Delete Delete None chars Select Disable CR+LF Disable Default (250)
Delete Delete None chars Select Disable CR+LF Disable Default (300)

Data Editor/Partial Data

No. of Char(s) Action
Handshake Terminator Chk Duplicate
Enable/Disable None, CR, LF, CR+LF, Tab Enabled/Disabled SPP

ConnectDevice

HID iPhone
Default(200i) Disable Disable Disable Enable
Default(250i) Disable Disable Disable N/A
Default(300i) Disable Disable Disable Enable

BT Config (200/250/300)

Auto Connect Auto Power On Auto Power On/Power Off Time Auto Power Off
Enabled/Disabled Enabled/Disabled Disable, 1sec to 10second(s) Enabled/Disabled
Auto Power Off/Beep Warning Auto Power Off/Power Off Time PowerOff Msg MAC Address BT FW Version Wakeup Nulls BT Toggle HID AutoLock HID Keyboard Power Pairing Discovering Connecting to GPS Power Power Mode
Enabled/Disabled 1 to 30 minutes Enabled/Disabled 12 Characters Bluetooth MAC Address v1.2.xrt Bluetooth Firmware Version Enabled/Disabled Enable/Disable Disabled/1m/2m/3m/4m/5m/10m/15m US/German Enabled/Disabled Pairing neighboring Bluetooth devices Discovering neighboring Bluetooth devices View Connect to Bluetooth device Enabled/Disabled Normal/Power Save Enabled/Disabled
N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A
Enable 5 minute(s) Disable

N/A N/A Disable

Disable Disable 1min US Enable
Disable Disable 1min US Disable

BT Service (200/250/300)

N/A N/A N/A N/A N/A

Disabled Normal Disabled

GPS Config (250G)

Bypass Data Acqurie Test Reset GPS
No. of Stored Barcodes Memory Status Free Memory Available Memory(Empties Data) Reset Memory Application Memory BT Registry(KDC100 Not use) Auto Erase Sleep Timeout Enabled/Disabled Disable, 1sec to 10minute(s) Bluetooth GPS Module Auto PowerOff PWR OFF Time N/A N/A Disables, 5Min, 10Min, 20Min, 30Min, 1Hr, 2Hr N/A Disabled 5 second(s) N/A N/A Disabled 5 second(s) N/A N/A Disabled 5 second(s) Disabled Disabled Disabled 5 second(s) N/A N/A

Date / Time

YYYY:MM:DD & HH:MM:SS % of Battery Charge Available Firmware Version & Serial No. Enabled/Disabled Enabled/Disabled Enabled/Disabled Enabled/Disabled Time & Battery / Type & Time / Type & Battery / Memory Status / GPS Data(KDC250 only) Enable/Disable Enabled/Disabled 1 to 15 level (8 level) Restores Default Settings Disable Enable Enable Enable Disable Enable Enable Enable Disable Enable Enable Enable Disable Enable Enable Enable

System Config

Battery Version Button Lock Beep Sound Auto Exit Port Status

Display Format

Time & Battery
Menu Barcode Scrolling Brightness Factory Default

N/A Enable 8 level

Disable Enable 8 level
Table 3 - KDC Menu Options 31

KDC Mode Menu

The KDC Mode Menu has two options Normal and Application modes. Normal: This is the default mode which provides basic barcode scanning. In Normal mode barcode data can be manipulated directly through the KDC or using KTSync during the synchronization process. Application: This mode allows you to run the user application created by Application Generation Tool described in Chapter 6.

View Data Menu

This menu option allows you to view and/or delete barcodes stored in the KDC.

Set Barcodes Menu

This menu lists all the barcode symbologies supported by your KDC and allows you to select the barcode symbologies you will be scanning. For maximum scan performance, you should select only the symbologies you are scanning. Please refer to Appendix A.1 Symbologies for a detailed listing of symbologies supported by your KDC.

Code Options Menu

Your KDC supports various Code Options including Transmission of Start and Stop Characters, Symbology Conversion, Verification of Optional Check Character, Transmission of Check Digit, and Concatenate. Please refer to Section 4.3 and Honeywell IT5x80 reference manual for a detailed listing of Code Options for the symbologies supported by the KDC.

Scan Options Menu

Timeout: Allows you to set the length of time before the KDC will stop scanning a barcode from.5 second up to 10 seconds. The default is 2 seconds. Minimum Barcode Length: Allows you to set a barcode length from 2 characters to 36 characters. It is strongly recommended that you maximize the minimum barcode length setting to prevent possible errors. The default is 4 characters.
Minimum (Default) Codabar Code 11 Code 32 Code 39 Code 93 Code 128 EAN-8 EAN-13 GS1 Composit I2of5 Matrix 2of5 1D Symbology MSI Plessey PosiCode GS1 Omni GS1 Limited GS1 Expanded S2of5 Ind S2of5 IATA TCL39 Telepen Trioptic UPCA UPCE0 UPCE1 AztecCode AztecRunes CodablockF Code16K 2D Symbology Code49 DataMatrix MaxiCode MicroPDF PDF417 QRCode 33 1(1) 0(1) 1(1) 1(1) 1(1) 1(1) 1(1) 1(1) 1(1) 1(1) 4(4) 1(4) 1(4) 2(4) 1(4) 4(4) 4(4) 2(4) 0(0) 0(0) 0(0) 2(4) 1(4)
Maximum (Default) 60(60) 80(80)

48(48) 80(80) 80(80)

80(80) 80(80) 48(48) 48(48) 80(48)

74(74) 48(48) 48(48)

60(60)

3750(3750)

2048(2048) 160(160) 81(81) 1500(1500) 150(150) 366(366) 2750(2750) 3500(3500)
HanXin Code Postnet PlanetCode UK Post Canada Post Postal Codes Kix Post Australia Post Japan Post China Post Korea Post OCR Off OCR A OCR OCR B OCR USC OCR MICR OCR SEMI Table 4 KDC300 Minimum Barcode Length 2(4) 2(4) 80(80) 80(48)
Auto Trigger: Allows users to scan a barcode automatically once Auto Trigger is enabled and USB cable is connected. User can adjust Reread delay from Short to Extra Long. Partial Display: Allows you to display partial data. User defines the start position and number of characters to be displayed.

Data Process Menu

Wedge/Store - The KDC provides five modes of data transmission in keyboard wedging mode. Wedge Only: Barcode data is NOT stored in memory but transmitted to the host. Wedge & Store Only: Barcode data is stored in memory and transmitted to the host. Store Only: Barcode data is stored in memory but NOT transmitted to the host. Save if Sent: If data transmission is successful, barcode data is stored in memory. Save if Not Sent: If data transmission is NOT successful, barcode data is stored in memory. Data Format - The KDC provides two data formats, Barcode Only and Packet Data. Barcode Only: KDC transmits scanned barcodes only. User may incorporate proper data transmission error detection and correction mechanism in this mode. 34
KDC300 User Manual KDC supports various termination characters for barcode only format. User can select <NONE>, <CR>, <LF>, <CR+LF> or <TAB> as the termination character. Packet Data: KDC transmits packet data with checksum to minimize transmission errors. KTSync sets Data Format to Packet Data format upon execution. User may change Data Format to Barcode only if user prefers to use Barcode only mode but either KTSync program terminates abnormally or user disconnects KDC without exiting KTSync program normally. [Note] Barcode Index: KDC200i/300i add 4 bytes barcode index to support maintaining last synchronized barcode information. This optional index would be added if data format is Packet Data and (1) 4 bytes index would be added before @ when responding to p command (2) 4 bytes index plus @ character would be added after checksum byte if user scan a barcode and wedging to the host

Handshake - KDC provides Handshake mode when Data Format is set to Packet Data. Handshake Mode will increase the reliability of barcode data transmission. The default mode for Handshake is Disabled. Data transmission speed is slower when Handshake Mode is Enabled.
Terminator KDC supports various termination characters when the Data Format mode is set to Barcode Only. This option allows you to select <NONE>, <CR>, <LF>, <CR+LF>, or <TAB> as the termination character. The default terminator is <CR+LF>. Up/Down/Left/Right arrow terminator is also available for HID mode.
Chk Duplicate This option allows you to prevent collecting duplicated data.
BT Config Menu - KDC200 / KDC250 / KDC300
The KDC supports Bluetooth Ver2.1+EDR. Before utilizing the advantages of Bluetooth functionality with the KDC, you should become familiar with Bluetooth connectivity and its impact on your host environment. To configure your KDC for Bluetooth functionality, you must use the KDC Menus. To access the menus, simultaneously press the UP and DOWN scroll buttons on the side of the KDC. Use the DOWN button to scroll to Bluetooth then press the Scan button. Below is a listing of the Bluetooth options and their settings. The default settings for these options have been set to increase the usability of Bluetooth technology without compromising the KDC battery usage. IMPORTANT: We strongly recommend NOT changing these settings until you have fully tested the Bluetooth connection between the KDC and the host device. For more detailed information regarding Bluetooth functionality with the KDC, please refer to Chapter 4. ConnectDevice Only applicable to KDC200i and KDC300i Auto Connect - Enabled or Disabled Auto Power On - Enabled or Disabled o PWR On Time Disabled, 1 to 10 seconds Auto Power Off - Enabled or Disabled (KDC250 should use option in system menu) o Beep Warning - Enabled or Disabled o PWR Off Time - 1 to 30 Minutes PowerOff Msg Enabled or Disabled MAC Address 12 characters Bluetooth MAC Address FW Version Display Bluetooth Firmware Version Wakeup Nulls Enabled or Disabled Autolock Time 0, 1, 2, 3, 4, 5, 10, 15 minutes BT Toggle Enable or Disable HID soft keyboard or iPhone mode connection On/Off toggle. HID Keyboard English or German

4.11 Autolock Time

iPhone/iPad/iPod touch loses incoming Bluetooth data in sleep mode. Users can set KDC Autolock time to the same Autolock time of your iPhone/iPad/iPod touch to use automatic wakeup feature in HID mode to prevent data loss. There would be a one second delay of barcode transmission if Autolock time is set to more than one minute and the barcode scan interval is larger than auto lock time. The autolock time would be set as 0, 1, 2, 3, 4, 5, 10, 15 minutes. 0 means iPhone/iPad/iPod touch never enters sleep mode.

4.12 BT Toggle

User can connect and disconnect Bluetooth connection with the host device by pressing Up and Down key if this option is enabled

Setting

Mode HID
Up key Reconnect to the last connected device if the Bluetooth is disconnected Display Bluetooth connection status
Down key Toggle Soft Keyboard Disconnect the Bluetooth connection Display KDC date/time

Enabled iPhone Disabled

[Note1] New soft keyboard toggle option using Down key inHIDmodeiseffectivefromBTFWversion
1.2.6orhigherandKDCFWversionis2.85(6).200(300).Iorhigher.PriortoBTFWversion1.2.5 orKDCFW2.85(6).200(300).HenablesthesoftkeyboardbypressingtheDownkeyand disablesthesoftkeyboardbypressingtheUpkey. [Note2]iPhone/iPad/iPodtouchlosesincomingBluetoothdatainsleepmode.Usersshouldwakeup iPhone/iPad/iPodtouchbeforescanningabarcodeinHIDmode. [Note3]KDCsupportsautoiPhone/iPad/iPodtouchwakeupfeatureinHIDmodefromBTFW1.2.6and KDCFW2.85(6).200(300).Iversion.UsersshouldsetKDCAutolocktimetothesameAutolock timeofyouriPhone/iPad/iPodtouchtouseautomaticwakeupfeatureinHIDmode.There wouldbeaoneseconddelayofbarcodetransmissionifAutolocktimeissettomorethanone minuteandthebarcodescanintervalislargerthanautolocktime.

Bluetooth Service

4.13 Power
The POWER option allows you to Enable or Disable the Bluetooth functionality of the KDC. To use Bluetooth, this option must be set to Enable. However, like all devices enabled for Bluetooth, the KDC will search constantly to connect with a Bluetooth host when set to enable. Constant searching uses battery power. Unless you are using Bluetooth with your KDC, this option should be set to Disable. IMPORTANT: To prevent unnecessary power problems, it is strongly recommended that the POWER option be set to Disable if the KDC is idle for an extended period of time.

4.14 Pairing

Before you are able to use Bluetooth, the KDC must be paired with the host device. This paring process only needs to be completed once with each host device. After pairing, the host device will always recognize the KDC as a Bluetooth device unless the Bluetooth configuration is modified. If it is modified, you may need to pair the devices again.

The KDC can be configured in one of five Wedge/Store modes Wedge Only - Scanned data is transmitted to the host. The KDC does not store scanned data. Wedge & Store - Scanned data is stored in the KDC and transmitted to the host. Store Only - Scanned data is stored in the KDC but NOT transmitted to the host. Save if Sent - Scanned data is stored in the KDC ONLY if transmission to the host is successful. Save if Not Sent - Scanned data is stored in the KDC ONLY if transmission to the host is unsuccessful.
Enable Wedge (Handheld Scanner Mode) - This option will be checked if Wedge Only or Wedge & Store option is selected.
Keep Scan Data in KDC - This option will be checked if Store Only or Wedge & Store option is selected.

Synchronization Options

Synchronize KDC Time with PC Time when Connected
This option enables you to synchronize the KDC date and time with the host date and time. Synchronization of date and time occurs after the data is uploaded to the host device.

Delays

You can set transmission delays between barcodes and characters during the synchronization process. It is important to set proper delays to prevent errors during the transmission of collected barcodes. Some Windows applications such as Excel require longer delay times.

Attachments

Timestamp, Barcode Type, and Serial Number can be attached to the scanned barcode by selecting these options. The Serial Number of the KDC can be attached to the Start or End of Record.

Prefix and Suffix

Enter the characters you want appended to the front (Prefix) or back (Suffix) of the barcode in the Prefix and Suffix fields. The character set is any combination of ASCII characters including alphanumeric, line feed (\n), and carriage return (\r).

Order and Delimiter

Select Order of Data Type, Data, and Timestamp Select the Delimiter between Data Tab, Space, Comma, and Semicolon Select the Delimiter between Records None, LF, CR, Tab, and <LF & CR>

Application Options

Synchronize Non-Compliant Data
The KDC will synchronize both compliant and non-compliant data (filtered data) if Synchronize NonCompliant Data option is Enabled.
Consolidate Steps in One Record
KTSync will consolidate the data collected in Step 1 with the data collected in Step 2 and/or Step 3. Data will be consolidated into one record instead of individual data records for each step when Consolidate Steps in One Record is Enabled. Non-complete records, i.e. three steps were defined but data was only collected for two steps; would be discarded if this option is Enabled.

Attach Quantity

Quantity would be attached to the left or right of the data if this option is Enabled. 56
5.4 Barcode & KDC Settings
KTSync allows you to configure the KDC Scan Options and Barcode Settings. The configuration options for the KDC using KTSync are similar to the Set Barcodes, Code Options, Data Editing and Scan Options on the KDC Menu. Please refer to Appendix A for proper barcode settings for your application. NOTE: You must configure barcode and scan options properly for optimal KDC performance.
Figure 17 - Barcode & KDC Settings, Symbologies, Data Editing and Scan Options
Select Symbologies and Symbology Options
The process for scanning and reading barcodes is delicate and complicated. Although your KDC is equipped with a high performance scan engine, if configured incorrectly it may not perform at its peak performance level. To ensure its high performance, the KDC comes configured to optimize its scan engine technology. Unless you clearly understand the impact of your changes to the KDC settings, please do not change factory default settings. Please refer to Appendix A for details. Pressing the Default icon will reset all symbology related options to factory default settings.

Data Editing Option

Prefix - Allows you to add a prefix to scanned data which can then be stored in KDC or wedged to the host. The Prefix format must be defined in the data format menu of KTSync. The maximum length for a Prefix is 11 characters. NOTE: This Prefix option is different from the Prefix option in KTSync which appends the prefix to data during synchronization. Suffix - Allows you to add a suffix to scanned data which can then be stored in KDC or wedged to the host. The Suffix must be defined in the data format menu of KTSync. The maximum length for a Suffix is 11 characters. NOTE: This Suffix option is different from the Suffix option in KTSync which appends the suffix to data during synchronization. AIM ID - Allows you to add AIM ID to scanned data which can then be stored in KDC or wedged to the host. AIM ID must be defined in data format menu of KTSync. AIM ID is either added to the end of Prefix or Suffix. Partial Data: Allows you to display and store partial data. User defines the start position and number of characters to be displayed and stored. Select the x characters from y position Set Partial Data Start Position to y, Partial Data Length to x, Partial Data Action to Select Partial Data Length 0 means Select all characters from y position. Erase the x characters from y position Set Partial Data Start Position to y, Partial Data Length to x, Partial Data Action to Erase Partial Data Length 0 means Erase all characters from y position.

5.5 Others Settings

Other options under the Settings menu allows you to select four additional settings.

Ask Confirmation before Trying Auto Connection prevents unintentional launch of KTSync. Ask Confirmation before Starting Auto Synchronization prevents unintentional synchronization of data. Minimize KTSync on Start will minimize KTSync and send to the tray upon execution. Keep Checking Bluetooth Connection allows reconnection of KDC once Bluetooth signal is detected. This feature is useful when moving from Bluetooth host device frequently. KTSync will automatically reconnect Bluetooth connection when you enter an effective Bluetooth network range. (Not Available on KDC100)
To select any of these settings, click on the box to the left of the setting. A check mark () will display next to the setting to indicate that it is selected.
Figure 18 - KTSync Confirmation Settings

5.6 Mobile pKTSync

pKTSync provides limited functionality for Pocket PC 2003 and Mobile 5.0+ users.
1. Synchronization - Provides data upload functionality to your applications. 2. Keyboard Emulator - Allows scanned data to be uploaded directly into your application as if the data were being entered manually on a keyboard.
For detailed explanations of these functions, please refer to earlier sections of this chapter.
WARNING: The user must assign the correct COM port to KDC prior to use pKTSync. Please refer to your mobile device manual for details on Bluetooth pairing and COM port assignment methods.

Figure 19 Mobile pKTSync

5.7 Android aKTSync
The aKTSync provides limited functionality of PC KTSync to Android users.
[NOTE 1] aKTSync only supports Android devices with 2.1+ OS version and that are compatible with BluetoothChat application. [NOTE 2] KDC with Bluetooth Spec2.1+EDR doesnt prompt Pin code entry menu

KDC and Android Pairing

1. Pairing Select SPP Bluetooth profile from KDC ConnectDevice submenu in BT Config menu. Search KDC200/200i/300/300i from Android and pairing two devices. KDC200/200i/300/300i PIN code is 0000 2. Connection Click Connect icon in aKTSync Android would list up paired Bluetooth devices and user should select the target KDC. 3. Synchronization - Provides data upload functionality to your applications. 4. Settings User can change various Synchronization options in settings menu. 5. Wedging User can wedge barcode data to any Android application. Press home key and launch the target application.

How to disconnect and reconnect HID mode using Up and Down Button keys.
1. Users needs to select the option to use this feature in the BT Config > HID Control. 2. Press the DOWN button to disconnect the HID connection and bring a soft keyboard. 3. Press the UP button to connect HID 4. The BT toggle is a useful feature if users desire to use both the KDC and soft keyboard.
KDC200i/300i connection using iPhone mode
[NOTE 1] Users have to RESET the iPhone/iPad/iPod touch to change HID to iPhone mode or vice versa. [NOTE 2] KDC with Bluetooth Spec2.1+EDR doesnt prompt Pin code entry menu.
1. Download and install iKTSync from the Apple App Store. http://itunes.apple.com/us/app/ktsync/id372916602?mt=8 2. Press the two KDC side buttons together to enter menu mode 3. Scroll down to Bluetooth menu 4. Press the front middle scan button 5. Scroll down to Discovering and press the front middle scan button A. B. Discovering Started message will be displayed on KDC screen Discovering will take about 30 seconds.
6. Select discovered iPhone/iPod touch device name and press the front middle scan button A. B. [Pin Code] User Default/Enter PinCode will be displayed Press the front middle scan button to select the Use Default option
C. Connencting to iPhone/iPod touch device name will be displayed D. iPhone/iPad/iPod touch will ask for the PIN number. E. F. Please enter 0000 and hit connect icon iPhone Connected message will be displayed
7. Launch KTSync and configure Settings
Figure 21 iPad/iPhone/iPod touch KTSync
How to connect and reconnect iPhone mode using UP keys.
1. Users needs to select the option to use this feature in the BT Config > iPhone Button 2. Press the UP button to connect or reconnect to the iPhone/iPad/iPod touch

5.9 Blackberry bKTSync

The bKTSync provides limited functionality of PC KTSync for Blackberry users. [NOTE] KDC with Bluetooth Spec2.1+EDR doesnt prompt Pin code entry menu
1. Download and install bKTSync from the Blackberry App World. http://appworld.blackberry.com/webstore/search/ktsync?lang=en 2. Go to Blackberry Options > Applications menu and Enable Input Simulation option 3. Change KDC Bluetooth profile in ConnectDevice option to SPP 4. Execute Blackberry Bluetooth manager and KDC Bluetooth pairing option A. Execute KDC Bluetooth Pairing option B. Launch the Blackberry Bluetooth manager and select Search. The KDC model and 6 digits of the serial number would be displayed. C. Highlight the KDC and press the Enter or Select Key D. Enter 0000 PIN code and press the Enter or Select Key E. The Blackberry will display Pairing with KDCcomplete. F. Close the Blackberry Bluetooth manager 5. Go to Downloads folder and execute KTSync 6. User can configure KDC options in KDC settings and Symbologies Settings menu 7. Go to KTSync Synchronization Settings and select Destination. To send collected barcode as an email attachment, choose Email Attachment as destination, enter email address, subject and body message. You can enter multiple email addresses using the semicolon(;) separator. 8. To scan barcodes into any application (like email, notes, worksheet or web browser), press the menu key and select Running in the background option. bKTSync will maintain the connection and place the scanned barcode data where ever the cursor is flashing.

Data Filter Settings

When you select Enable data filtering, you must click on the Settings box to select the Data filter setting. The option for the data filter settings are the same for Step1, Step 2, and Step 3.
Figure 26 Data Filter Settings

Barcode Type

This field allows you to select the type of barcodes the KDC will collect. When you click on the box, Select Symbols is enabled. A listing of the symbologies supported by the KDC displays. To select a barcode symbology, click on the box associated with the symbology.

Minimum Data Length

This field allows you to define the minimum length of the scanned barcode. The length can be between 2 and 36 characters. If a user scans a barcode whose length is less than the defined length, the barcode data is not collected.
[Note] The default KDC minimum barcode length defined in scan option is 4. Therefore, users should change KDC minimum barcode length to 2 or 3 to define minimum data length to 2 or 3.

Maximum Data Length

This field allows you to define the maximum length of a scanned barcode. The defined length can be between 2 and 256 characters. If a user scans a barcode whose length is greater than the defined length, the barcode data is not collected.
[Note] The default KDC minimum barcode length defined in scan option is 4. Therefore, users should change KDC minimum barcode length to 2 or 3 to define maximum data length to 2 or 3.

Barcode Collation

This option enables you to define a data string that the KDC will use to compare scanned barcodes. o Starting Position This is the start position of the scanned barcode data to be compared with the defined data string. o Data String This is the defined value to be compared with scanned barcode data. This value can be up to 32 characters

Collect Partial Data

This option allows you to define partial barcode data to be collected when a barcode is scanned. Only the partial data will be stored in the KDC. o Start position This is the starting position that the KDC will use when collecting scanned barcode data.

Figure 32 Inventory Application Menu

7. TROUBLESHOOTING

PROBLEM
KDC not working Hardware failure Bad battery KDC not charging Poor USB port Damaged barcode Out of scan range Incorrect angle Failed reading Symbology not supported Scan options Dirty scan window Damaged scan window Dirty scan window KDC reads wrong barcode Damaged scan window Poor quality barcode USB cable is not connected properly Software is not working properly COM configuration LED blinks yellow Buffer Full Message Empty Battery Message Low battery power Full Memory Empty battery

Dead battery

SOLUTION
Charge battery by connecting KDC to your PC using the included cable Contact distributor for technical support Replace battery Contact Local Distributor USB port doesnt supply proper current to KDC - Charge KDC using a different USB port on your PC Scan a different barcode Move the scanner closer to barcode Move scanner farther from the barcode Change the angle of scanner to barcode Contact KoamTac - www.koamtac.com for possibility of custom symbology support Check scan option settings Clean scan window Replace scan window Clean scan window Replace scan window Select only necessary barcodes Increase minimum barcode length Increase security level Check cable connection between KDC and host device Reload the software Check COM port configurations Charge the battery by connecting KDC to PC. KDC will lose collected data if the battery is empty. Clear the Memory using Synchronization program Connect USB immediately. Synchronize the collected data and charge KDC Disable Quickset Utility before using KTSync. Dell Quickset utility interrupts normal KTSync operation Disable WSED Wireless enable/disable utility
Cant communicate with PC, PDA, or smartphone
Quickset Utility Abnormal KTSync Operation on DELL PC

WSED Utility

delete the folder C:\Program Files\WSED, which contains a file WSED.exe, with the same icon as in the taskbar
Delete the registry entry KEY_LOCAL_MACHINE \SOFTWARE\Microsoft\Windows\CurrentVersion\Run\WSED
Table 6 - Troubleshooting Techniques 84