Production line PCB serial programming and testing method and system

Information

  • Patent Grant
  • 10104487
  • Patent Number
    10,104,487
  • Date Filed
    Friday, December 15, 2017
    6 years ago
  • Date Issued
    Tuesday, October 16, 2018
    5 years ago
  • Inventors
  • Original Assignees
  • Examiners
    • Bernardi; Brenda C
    Agents
    • Goodhue, Coleman & Owens, P.C.
Abstract
A system and method for testing a wireless earpiece which provides improved efficiencies in manufacturing. Automated testing of one or more printed circuit boards of the wireless earpiece is initiated. The semi-assembled wireless earpiece is tested. End-of-line functional testing is performed. Final acoustic testing of the wireless earpiece is performed.
Description
FIELD OF INVENTION

The present invention relates to wireless device manufacturing. More particularly, but not exclusively, the present invention relates to production line PCB serial programming and testing.


BACKGROUND

Usage of wireless devices has grown significantly in recent years as manufacturing processes, devices, and wireless standards have improved. As wireless devices become smaller and more portable, space limitations for components and circuitry become even more constrained. Space constraints are particularly limited for wireless earpieces. Such space constraints preclude the usage of significant number of tests points for device layouts utilizing printed circuit boards (PCBs). As a result, testing PCBs during the manufacturing process may be difficult, potentially resulting in additional time and equipment requirements, failed devices, extra troubleshooting, and additional expense.


SUMMARY

One aspect includes a system, method, and testing device including a processor and memory with instructions that are executed to test a wireless earpiece. Automated testing of one or more printed circuit boards of the wireless earpiece is initiated. The semi-assembled wireless earpiece is tested. End-of-line functional testing is performed. Final acoustic testing of the wireless earpiece is performed.


Another aspect includes a system for testing a wireless earpiece. The system may include a computing device connected to the wireless earpiece. The system may also include a reference wireless earpiece connected to the computing device. The computing device may be configured to initiate automated testing of one or more printed circuit boards (PCBs) of the wireless earpiece, test the semi-assembled wireless earpiece, perform end-of-line functional testing, and perform final acoustic testing of the wireless earpiece.





BRIEF DESCRIPTION OF THE DRAWINGS

Illustrative embodiments of the present invention are described in detail below with reference to the attached drawing figures, which are incorporated by reference herein and wherein:



FIG. 1 is a pictorial representation of a testing system in accordance with an illustrative embodiment;



FIG. 2 is a flowchart of a process for testing a PCB of a wireless earpiece in accordance with an illustrative embodiment;



FIG. 3 is a flowchart of a process for initiating an automated production panel testing in accordance with an illustrative embodiment;



FIG. 4 is a flowchart of a process for performing semi-assembly of the wireless device in accordance with an illustrative embodiment; and



FIG. 5 depicts a computing system 500 in accordance with an illustrative embodiment.





DETAILED DESCRIPTION

The illustrative embodiments provide a system and method for production line PCB serial programming and testing. In one embodiment, the PCBs may be a component of a wireless earpiece, such as concha or external auditory canal device. When referencing the PCB herein, reference may be made to one or more PCBs, systems, sub-systems, components, or the entire device.


PCBs as well as the sub-systems of the wireless earpiece may be tested throughout the various phases of integration of the wireless earpiece. By utilizing the processes, steps, and methods herein described, the illustrative embodiments provide significant advantages in improving the efficiency of manufacturing production lines for one or more versions of wireless earpieces. In addition, substantial costs savings may be achieved by removing defective components before the defective components are further integrated into the wireless earpiece. As a result, defective devices may be removed more dynamically during the manufacturing process to preserve functioning parts instead of discarding entire systems or sub-systems of the wireless earpiece. In another embodiment, the wireless earpiece may represent any number of wireless devices.


During the described testing processes, the PCBs and corresponding wireless earpieces may be programmed to serially certify functionality of all component sets of the PCB and wireless earpiece. The testing may be performed by a testing system utilizing custom jigs that may be connected or otherwise interface to the PCBs and wireless earpieces. In one embodiment, the testing, certification, and other processes of the illustrative embodiments may be implemented utilizing four phases as herein described.



FIG. 1 is a pictorial representation of a testing system 100 in accordance with an illustrative embodiment. In one embodiment, the testing system 100 may be configured for testing an external auditory canal device, such as the wireless earpiece including the PCB 104. The testing system 100 may utilize any number of devices or components or be configured in various ways for performing the processes herein described.


In one embodiment, the testing system 100 may include a computing device 106, an interface 108, testing jigs 110, one or more devices under test (DUT) 102, a reference device 116, and an interface 118.


The computing device 106 may be a desktop computing device, specialized computing device, tablet, one or more servers, databases, or other device(s) for testing the DUT 102. The computing device 106 may represent one or more computing devices that are configured to communicate or otherwise interface with the DUT 102. In one example, the computing device 106 may represent a personal computer, server, and database for storing testing information for a number of DUTs.


The computing device 106 may have dedicated hardware and logic, such as signal generators, transceivers, signal processors, light sensors, microphones, speakers, sensors, and measuring devices that may be utilized to measure the performance, characteristics, and responses of the DUT 102. In another embodiment, the computing device 106 may include databases or instructions that are executed by a processor of the computing device to perform testing. For example, a set of instructions stored in the non-transitory memory of the computing device 106 may be executed to perform the steps herein described.


In another embodiment, all or portions of the measurement equipment may be integrated with or connected to the testing jigs 110. The computing device 106 may also be connected to one or more data or wireless networks. For example, the computing device 106 (as well as the DUT 102 may communicate with one or more wireless networks (e.g., Bluetooth, WiFi, cell, Zigbee, etc.), local area networks, or other wired networks (e.g., Ethernet, powerline, fiber optics, etc.). The networks may represent any number of public and private networks (e.g., the Internet) operated by one or more service providers. For example, testing scripts, programs, updates, or instructions may be retrieved through a number of interconnected networks including a private WiFi network, local area networks, and public or cloud networks.


The interface 108 and 118 may represent a serial connection, cable, or wire connected between the computing device 106 and the DUT 102 and the computing device 106 and the reference device 116, respectively. For example, the interfaces 108 and 118 may be USB connections from the computing device 106 to the DUT 102 and the reference device 116. The interfaces 108 and 118 may also represent wireless connections, such as Bluetooth, WiFi, near field communications, radio frequency (RF) communications, or other wireless connections that may be established utilizing transmitters, receivers, or transceivers. As a result, the functional aspects of the DUT 102 may be tested.


The testing jigs 110 physically secure the DUT 102 as well as electrically interface with the DUT 102 as a whole as well as individual components of the DUT 102 to fully test the DUT 102 and the corresponding PCBs 104. For example, the testing jigs 110 may mechanically secure the DUT 102 utilizing one or more clamps or arms. The testing jigs 110 may also include wires, micro interfaces (e.g., micro USB, etc.), BLUETOOTH or other wireless systems such as radio frequency antennas or other electrical interfaces for connecting, probing, or programming to any number of test points of the PCBs 104.


The reference device 116 may be utilized to generate reference signals for the testing and measuring the DUT 102. In addition, the reference device 116 may be utilized to communicate with the DUT 102 to perform functionality testing as is herein described. The wireless earpiece 102 may be configured for use as a pair (i.e., left ear and right ear). The reference device is used to test the magnetic induction link, to control and trace the semi-assembled DUT 102. The reference device 116 communicates via a gateway to the DUT 102. The reference device may test all major PCB component subsystems; a passing grade allows the PCB to move further down the assembly line for integration into the assembled product.



FIG. 2 is a flowchart of a process for testing a PCB of a wireless earpiece in accordance with an illustrative embodiment. The processes of FIGS. 2-4 may be implemented utilizing a testing system or device and may include multiple phases or steps as herein described. The processes may be performed on a single device at a time or for multiple devices in batches or runs of devices. In one embodiment, the PCBs of the wireless earpiece are produced on a panel that may include PCBs for a number of different devices. The test sequence may be run on each PCB associated with a device on a panel (of which each PCB may also be referred to as a device under test—DUT 102). The testing of PCBs on the panel may be performed in parallel, serially, or sequentially. Any PCBs that fail testing may be reworked (e.g., modified, refurbished, discarded, recycled, etc.). Reworking at a rework station may provide enhanced test result information for testers. After all the PCBs have been tested on the panel, the successfully evaluated devices may be removed from the panel for integration in a final product. Robotics and computerized testing logic (e.g., logic circuits, firmware, scripts, etc.) may be utilized to minimize manual user intervention in the process. For example, robotics may be used to connect the PCB/DUT to the testing jig, as well as to identify passing PCBs and select these for further assembly line integration, leaving the PCBs that do not pass on the main circuit board assembly for reworking.


The process of FIG. 2 may begin by initiating an automated production panel testing (step 200). In one embodiment, the system may include a personal computer, server, or other computing device that may be physically connected to a customized PCB. The computing device may be connected to a number of testing devices and equipment that interface with the PCB. In one embodiment, the system may utilize a unique radio frequency (RF) antenna connected to an RF test box. For example, the panel may be enclosed in a RF test box that isolates outside radio frequencies for more accurate testing. If there is a problem with the panel, the panel may be conveyed 210 to a single rework station 214 attached to a monitor 212. The single rework station 214 may provide detailed data regarding the specific reason(s) for the original test failure. At this point, either the system corrects the issue and returns 216 the DUT back for automated production panel testing 200 or else it is rejected 219.


Next, the system performs semi-assembly testing of the wireless device (step 202). During step 202, the semi-assembly of the DUT is tested utilizing a jig that connects the semi-assembled DUT to the system for automated testing. If there is a problem with the semi-assembly, the semi-assembly may be conveyed 220 to a single rework station 224 attached to a monitor 222. The single rework station 224 may provide detailed data regarding the specific reason(s) for the original test failure. At this point, either the system corrects the issue and returns 226 the semi-assembly back for automated semi-assembly testing 202 or else it is rejected 229.


Next, the system performs end-of-line functionality testing (step 204). During step 204, the wireless device may be completely formed with the battery fully enclosed inside the device. As before, custom-built jigs may be utilized for final testing of the light sensitive componentry. In one embodiment, a reference wireless earpiece may be utilized for testing the DUT. In one embodiment, the reference wireless earpiece is used to test the NFMI antenna and chip combination by communicating in such a way as to test the limits of the NFMI antenna of the DUT and replicating the most extreme conditions expected to be encountered by the DUT. The DUT is expected to communicate without errors and at the limits of the connection range. The testing jig utilized during step 204 may expose any of the potential NFMI linkage errors of the DUT. The testing jig is also utilized to test the pulse oximeter, touch sensors, and red green and blue (RGB) light emitting diodes (LEDs). In one embodiment, the jig may include a mechanical arm for engaging or activating the touch sensor(s). The testing jig may also emulate a pulse for testing the pulse oximeter. The testing jig may include light sensors or devices for detected or reflecting light generated by the LEDs. In one embodiment, the DUT may be light insulated or otherwise enclosed within a shield to ensure that ambient light does not affect the results of the testing. In another embodiment, the DUT itself is utilized to measure the LED and pulse oximetry outputs by reflecting the light emitted back onto the sensor contained within the DUT. If the DUT fails the testing, the DUT is rejected 239.


Next, the system performs final acoustic testing (step 206) with the process terminating thereafter. During the final acoustic testing of step 206, a customized testing jig is utilized to perform testing. The testing of step 206 may be performed in an acoustically isolated chamber or room for testing the external auditory canal (EAC) microphone which may be a bone microphone tuned to detect vibrations of the surrounding bony structures, EAC speaker, ambient microphone located on the superolateral segment, and audio over the NFMI linkage of the DUT.


During step 206, audio may be played into the ambient microphone of the DUT and then retransmitted by the EAC loudspeaker and recorded by the microphone placed underneath the testing jig. The recorded audio may then be analyzed against the reference signal. In one embodiment, there are four segments analyzed including: low—for example, 100+ Hz (testing of microphones and speakers for bass), mid—for example, 1000 Hz+ testing for obstruction, high—for example, 3000 Hz+ testing for reference and calibration, and white noise—looking for gaps or peaks, resonance frequencies, or blockages.


Audio may also be played into the EAC microphone and then transmitted by the NFMI to the reference wireless earpiece in the testing jig. The reference wireless earpiece may then send the audio to the computer where the signal may be analyzed against the reference signal. If it fails here, it is rejected 249. After successful performance of final acoustic testing, the successfully produced DUT is sent for packaging 208.


In one embodiment, a single customized jig may be utilized to perform testing during the different steps of FIG. 2. The illustrative embodiments provide point of production analysis and identification of component set issues. The illustrative embodiments maximize the efficiency of production, recognition failures much earlier in the production process and save money through minimizing the waste of functional component sets coupled to failed components. By finding the problems earlier in the process, components may not be irreversibly combined. In some cases, the problems may be diagnosed for preventing other devices from suffering from similar issues. Additionally, some components may be saved for reworking, reusing, or recycling where appropriate.



FIG. 3 is a flowchart of a process for initiating an automated production panel testing in accordance with an illustrative embodiment. In one embodiment, the process of FIG. 3 may correspond to step 200 of FIG. 2. First, the system tests component sets of the PCB for energy consumption (step 302). The system may ensure that the energy consumption (as well as the other testing measurements of the processes described herein) is within designated tolerances, thresholds, or ranges (e.g., voltage, current, power in Watts, etc.). Upper, lower, and median measurement values may be specified. Alarms may be generated or the PCB marked for reworking in response to failing any of the tests. For example, a database of the testing system may be utilized to track the test results (including failures) for subsequent analysis. A serial number, bar code, radio frequency tag, or other assigned identifier may be utilized to associate the PCB or components with the test results and measurements.


Next, the system programs intelligent components on the PCB (step 304). The PCB may include any number of intelligent or programmable components, such as Bluetooth chips, logic chips, field programmable gate arrays (FPGAs), processing chips (e.g., Kinetics ARM chip), and so forth.


Next, the system performs RF testing (step 306). In one embodiment, the Bluetooth device or RF components (e.g., Bluetooth transceiver, WiFi transceiver, etc.) may be instructed to transmit and/or receive on a planned frequency with crystal trimming being performed. Frequency adjustments may be performed to tune or tweak the frequency transmissions of the RF transceiver.


Next, the system tests Bluetooth of the PCB (step 308). In one embodiment, a number of tests may be implemented and measured according to the preset standards. In one embodiment, test data is transmitted to a receiver of the system and evaluated for errors. In addition, a noise baseline or floor may be set for the Bluetooth components of the PCB.


Next, the system performs a battery protection test of the PCB (step 310). The PCB and corresponding circuits will be checked to verify that the system is configured to utilize minimal current when battery voltage is below the manufacturer's minimum specification. Next, the system tests normal battery charging capabilities of the PCB (step 312). In one embodiment, the voltage and current utilized to charge the battery may be determined as well as the capacity of the battery when fully charged.


Next, the system removes external power and measures power usage (step 314). During step 314, the system verifies that the PCB utilizes power within a specified range when drawing power from the internal battery connection.


Next, the system tests to verify the microcontroller of the PCB is able to connect to the touch sensor, accelerometer, memory, and near-field magnetic induction (NFMI) chip (step 316). In one embodiment, test signals may be sent to each of the various sub-systems (e.g., touch sensor, accelerometer, memory, NFMI chip, radio frequency identification tag, gyroscope, etc.). Once the testing of FIG. 3 is complete, the system powers down the PCB. After a short delay the PCB is connected to a USB or other interface. The system may then determine the size of the memory available on the PCB. Configuration of the memory or uploading of default files may also be performed as needed.



FIG. 4 is a flowchart of a process for performing semi-assembly of the wireless device in accordance with an illustrative embodiment. In one embodiment, the testing of FIG. 4 may correspond to step 202 of FIG. 2. The PCB may be expensive to manufacture and as a result an electro-mechanical testing jig as previously described may be utilized to interface all or portions of the system (e.g., a computing device) with the PCB.


The process begins by fitting the lateral segment and the medial segment of the DUT to the jig (step 402). At this point, both the lateral and medial segments, (or sub-assemblies) are separate and have not yet been fused together allowing for changes to be made as needed before final assembly. If there is a failure of either of the lateral or medial segments, the segment may be reworked to reduced costs and minimize wastes. The medial segment is the portion of the DUT that is destined to be placed closest to the tympanic membrane.


Next, the system verifies functionality by loading an initialization file through the jig (step 404). The system loads internal software for the DUT to do testing. During step 404, the DUT is rebooted from the USB. The DUT is then ready to operate as if fully integrated. During the reboot, the DUT is expected to reboot with verification of the various internal devices including NFMI antenna (e.g., calibration), battery, pulse oximeter, amplifier, and other sub-systems and components.


Next, the system reconnects to the DUT to re-enumerate as a mass storage device (step 406). The system may be reconnected through an interface, such as a USB connection. During step 406, the initialization file previously loaded is deleted from the DUT. In addition, a trace file utilized to document functionality of the components of the DUT is copied and removed from the DUT for analysis and to determine if there are any errors.


Next, the system copies all files onto the DUT (step 408). If the DUT continues to pass each step of FIG. 4, the system copies all of the system, audio, and other files. At any time during the process of FIG. 4 if a failure occurs, the particular sub-system, such as the lateral or medial segment, is marked for reworking and further processed. After the process of FIG. 4, the sub-assemblies may be welded together.


The illustrative embodiments may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a “circuit,” “module” or “system.” Furthermore, embodiments of the inventive subject matter may take the form of a computer program product embodied in any tangible medium of expression having computer usable program code embodied in the medium. The described embodiments may be provided as a computer program product, or software, that may include a machine-readable medium having stored thereon instructions, which may be used to program a computing system (or other electronic device(s)) to perform a process according to embodiments, whether presently described or not, since every conceivable variation is not enumerated herein. A machine readable medium includes any mechanism for storing or transmitting information in a form (e.g., software, processing application) readable by a machine (e.g., a computer). The machine-readable medium may include, but is not limited to, magnetic storage medium (e.g., floppy diskette); optical storage medium (e.g., CD-ROM); magneto-optical storage medium; read only memory (ROM); random access memory (RAM); erasable programmable memory (e.g., EPROM and EEPROM); flash memory; or other types of medium suitable for storing electronic instructions. In addition, embodiments may be embodied in an electrical, optical, acoustical or other form of propagated signal (e.g., carrier waves, infrared signals, digital signals, etc.), or wireline, wireless, or other communications medium.


Computer program code for carrying out operations of the embodiments may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C++ or the like and conventional procedural programming languages, such as the “C” programming language or similar programming languages. The program code may execute entirely on a user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN), a personal area network (PAN), or a wide area network (WAN), or the connection may be made to an external computer (e.g., through the Internet using an Internet Service Provider).



FIG. 5 depicts a computing system 500 in accordance with an illustrative embodiment. includes a processor unit 501 (possibly including multiple processors, multiple cores, multiple nodes, and/or implementing multi-threading, etc.). The computing system includes memory 507. The memory 507 may be system memory (e.g., one or more of cache, SRAM, DRAM, zero capacitor RAM, Twin Transistor RAM, eDRAM, EDO RAM, DDR RAM, EEPROM, NRAM, RRAM, SONOS, PRAM, etc.) or any one or more of the above already described possible realizations of machine-readable media. The computing system also includes a bus 503 (e.g., PCI, ISA, PCI-Express, HyperTransport®, InfiniBand®, NuBus, etc.), a network interface 505 (e.g., an ATM interface, an Ethernet interface, a Frame Relay interface, SONET interface, wireless interface, etc.), and a storage device(s) 509 (e.g., optical storage, magnetic storage, etc.). The system memory 507 embodies functionality to implement embodiments described above. The system memory 507 may include one or more functionalities that facilitate retrieval of the audio information associated with an identifier. Code may be implemented in any of the other devices of the computing system 500. Any one of these functionalities may be partially (or entirely) implemented in hardware and/or on the processing unit 501. For example, the functionality may be implemented with an application specific integrated circuit, in logic implemented in the processing unit 501, in a co-processor on a peripheral device or card, etc. Further, realizations may include fewer or additional components not illustrated in FIG. 5 (e.g., video cards, audio cards, additional network interfaces, peripheral devices, etc.). The processor unit 501, the storage device(s) 509, and the network interface 505 are coupled to the bus 503. Although illustrated as being coupled to the bus 503, the memory 507 may be coupled to the processor unit 501.


While the embodiments are described with reference to various implementations and exploitations, it will be understood that these embodiments are illustrative and that the scope of the inventive subject matter is not limited to them. In general, techniques for testing and processing wireless earpieces, PCBs, and other components as described herein may be implemented with devices, facilities, or equipment consistent with any hardware system(s). Many variations, modifications, additions, and improvements are possible.


Plural instances may be provided for components, operations or structures described herein as a single instance. Finally, boundaries between various components, operations and data stores are somewhat arbitrary, and particular operations are illustrated in the context of specific illustrative configurations. Other allocations of functionality are envisioned and may fall within the scope of the inventive subject matter. In general, structures and functionality presented as separate components in the exemplary configurations may be implemented as a combined structure or component. Similarly, structures and functionality presented as a single component may be implemented as separate components. These and other variations, modifications, additions, and improvements may fall within the scope of the inventive subject matter. The previous detailed description is of a small number of embodiments for implementing the invention and is not intended to be limiting in scope. The following claims set forth a number of the embodiments of the invention disclosed with greater particularity.

Claims
  • 1. A method for testing a wireless earpiece, the method comprising: initiating an automated production panel testing, wherein a plurality of PCB (printed circuit boards) are produced on the automated production panel;conveying the production panel to a first rework station if a failure occurs with the production panel during testing;correcting the failure and returning the production panel back for automated production panel testing; andrejecting the production panel if the failure cannot be corrected.
  • 2. The method according to claim 1, further comprising the steps of: performing semi-assembly testing of the wireless earpiece;conveying the semi-assembly to a second rework station if a failure occurs with the semi-assembly during testing;correcting the failure and returning the semi-assembly back for semi-assembly testing; andrejecting the semi-assembly if the failure cannot be corrected.
  • 3. The method according to claim 2, further comprising the step of performing end-of-line functional testing.
  • 4. The method according to claim 3, further comprising the step of rejecting the wireless earpiece if a failure is detected during end-of-line functional testing.
  • 5. The method according to claim 4, further comprising the step of performing final acoustic testing on the wireless earpiece.
  • 6. The method according to claim 5, further comprising the step of rejecting the wireless earpiece if a failure is detected during final acoustic testing.
  • 7. The method according to claim 6, further comprising the step of packaging the wireless earpiece.
  • 8. A system for testing a wireless earpiece, the system comprising: a computing device operably coupled to a production panel for automated testing, wherein a plurality of PCB (printed circuit boards) are produced on the production panel, wherein the PCBs are components of the wireless earpiece;a first rework station for receiving a failed production panel from the computing device; anda first monitor operably coupled to the first rework station providing data regarding the reason for the production panel failing; wherein the failed production panel is rejected if the first rework station cannot repair the failed production panel and the failed production panel is returned to the computing device for production panel automated testing if the failed production panel can be repaired or defective components can be removed to prevent integration into a semi-assembly.
  • 9. The system according to claim 8, further comprising a second rework station for receiving a failed semi-assembly from the computing device; and a second monitor operably coupled to the second rework station providing data regarding the reason for the semi-assembly failing; wherein the failed semi-assembly is rejected if the second rework station cannot repair the failed semi-assembly and the failed semi-assembly is returned to the computing device for semi-assembly testing if the failed semi-assembly can be repaired.
  • 10. The system according to claim 9, wherein the computing device performs end-of-line functional testing.
  • 11. The system according to claim 10, wherein the wireless earpiece is rejected if a failure is detected during end-of-line functional testing.
  • 12. The system according to claim 11, wherein the computing device performs final acoustic testing of the wireless earpiece and rejects any failed wireless earpiece.
  • 13. The system according to claim 11, wherein the wireless earpiece is packaged.
  • 14. A method for testing a wireless earpiece, the method comprising: initiating an automated production panel testing, wherein a plurality of PCB (printed circuit boards) are produced on the automated production panel;conveying the production panel to a first rework station if a failure occurs with the production panel during testing;correcting the failure and returning the production panel back for automated production panel testing;rejecting the production panel if the failure cannot be corrected, wherein defective components are removed before being integrated into a semi-assembly;performing semi-assembly testing of the wireless earpiece;conveying the semi-assembly to a second rework station if a failure occurs with the semi-assembly during testing;correcting the failure and returning the semi-assembly back for semi-assembly testing; andrejecting the semi-assembly if the failure cannot be corrected.
  • 15. The method according to claim 14, further comprising the step of performing end-of-line functional testing.
  • 16. The method according to claim 15, further comprising the step of rejecting the wireless earpiece if a failure is detected during end-of-line functional testing.
  • 17. The method according to claim 16, further comprising the step of performing final acoustic testing on the wireless earpiece.
  • 18. The method according to claim 17, further comprising the step of rejecting the wireless earpiece if a failure is detected during final acoustic testing.
  • 19. The method according to claim 18, further comprising the step of packaging the wireless earpiece.
  • 20. The method according to claim 19, further comprising the step of testing component sets of a PCB for energy consumption.
PRIORITY STATEMENT

This application claims priority to U.S. Provisional Patent Application No. 62/211,724, filed Aug. 29, 2015 and is a continuation application of U.S. patent application Ser. No. 15/244,834 filed on Aug. 23, 2016, both applications are hereby incorporated by reference in their entirety.

US Referenced Citations (294)
Number Name Date Kind
2325590 Carlisle et al. Aug 1943 A
2430229 Kelsey Nov 1947 A
3047089 Zwislocki Jul 1962 A
D208784 Sanzone Oct 1967 S
3586794 Michaelis Jun 1971 A
3934100 Harada Jan 1976 A
3983336 Malek et al. Sep 1976 A
4069400 Johanson et al. Jan 1978 A
4150262 Ono Apr 1979 A
4334315 Ono et al. Jun 1982 A
D266271 Johanson et al. Sep 1982 S
4375016 Harada Feb 1983 A
4588867 Konomi May 1986 A
4617429 Bellafiore Oct 1986 A
4654883 Iwata Mar 1987 A
4682180 Gans Jul 1987 A
4791673 Schreiber Dec 1988 A
4852177 Ambrose Jul 1989 A
4865044 Wallace et al. Sep 1989 A
4984277 Bisgaard et al. Jan 1991 A
5008943 Arndt et al. Apr 1991 A
5036479 Prednis Jul 1991 A
5123016 Muller Jun 1992 A
5185802 Stanton Feb 1993 A
5191602 Regen et al. Mar 1993 A
5201007 Ward et al. Apr 1993 A
5201008 Arndt et al. Apr 1993 A
D340286 Seo Oct 1993 S
5280524 Norris Jan 1994 A
5295193 Ono Mar 1994 A
5298692 Ikeda et al. Mar 1994 A
5343532 Shugart Aug 1994 A
5347584 Narisawa Sep 1994 A
5363444 Norris Nov 1994 A
D367113 Weeks Feb 1996 S
5497339 Bernard Mar 1996 A
5513099 Schein Apr 1996 A
5596587 Douglas Jan 1997 A
5606621 Reiter et al. Feb 1997 A
5613222 Guenther Mar 1997 A
5654530 Sauer et al. Aug 1997 A
5692059 Kruger Nov 1997 A
5721783 Anderson Feb 1998 A
5748743 Weeks May 1998 A
5749072 Mazurkiewicz et al. May 1998 A
5771438 Palermo et al. Jun 1998 A
D397796 Yabe et al. Sep 1998 S
5802167 Hong Sep 1998 A
D410008 Almqvist May 1999 S
5929774 Charlton Jul 1999 A
5933506 Aoki et al. Aug 1999 A
5949896 Nageno et al. Sep 1999 A
5987146 Pluvinage et al. Nov 1999 A
6021207 Puthuff et al. Feb 2000 A
6054989 Robertson et al. Apr 2000 A
6081724 Wilson Jun 2000 A
6084526 Blotky et al. Jul 2000 A
6094492 Boesen Jul 2000 A
6111569 Brusky et al. Aug 2000 A
6112103 Puthuff Aug 2000 A
6157727 Rueda Dec 2000 A
6167039 Karlsson et al. Dec 2000 A
6181801 Puthuff et al. Jan 2001 B1
6208372 Barraclough Mar 2001 B1
6230029 Yegiazaryan et al. May 2001 B1
6275789 Moser et al. Aug 2001 B1
6339754 Flanagan et al. Jan 2002 B1
D455835 Anderson et al. Apr 2002 S
6408081 Boesen Jun 2002 B1
6424820 Burdick et al. Jul 2002 B1
D464039 Boesen Oct 2002 S
6470893 Boesen Oct 2002 B1
D468299 Boesen Jan 2003 S
D468300 Boesen Jan 2003 S
6542721 Boesen Apr 2003 B2
6560468 Boesen May 2003 B1
6563301 Gventer May 2003 B2
6654721 Handelman Nov 2003 B2
6664713 Boesen Dec 2003 B2
6690807 Meyer Feb 2004 B1
6694180 Boesen Feb 2004 B1
6718043 Boesen Apr 2004 B1
6738485 Boesen May 2004 B1
6748095 Goss Jun 2004 B1
6754358 Boesen et al. Jun 2004 B1
6784873 Boesen et al. Aug 2004 B1
6823195 Boesen Nov 2004 B1
6852084 Boesen Feb 2005 B1
6879698 Boesen Apr 2005 B2
6892082 Boesen May 2005 B2
6920229 Boesen Jul 2005 B2
6943614 Kuei Sep 2005 B1
6952483 Boesen et al. Oct 2005 B2
6987986 Boesen Jan 2006 B2
7010137 Leedom et al. Mar 2006 B1
7113611 Leedom et al. Sep 2006 B2
D532520 Kampmeier et al. Nov 2006 S
7136282 Rebeske Nov 2006 B1
7203331 Boesen Apr 2007 B2
7209569 Boesen Apr 2007 B2
7215790 Boesen et al. May 2007 B2
D549222 Huang Aug 2007 S
7279887 King Oct 2007 B1
D554756 Sjursen et al. Nov 2007 S
7403629 Aceti et al. Jul 2008 B1
D579006 Kim et al. Oct 2008 S
7463902 Boesen Dec 2008 B2
7508411 Boesen Mar 2009 B2
D601134 Elabidi et al. Sep 2009 S
7825626 Kozisek Nov 2010 B2
7965855 Ham Jun 2011 B1
7979035 Griffin et al. Jul 2011 B2
7983628 Boesen Jul 2011 B2
D647491 Chen et al. Oct 2011 S
8095188 Shi Jan 2012 B2
8108143 Tester Jan 2012 B1
8140357 Boesen Mar 2012 B1
D666581 Perez Sep 2012 S
8300864 Müllenborn et al. Oct 2012 B2
8406448 Lin Mar 2013 B2
8436780 Schantz et al. May 2013 B2
D687021 Yuen Jul 2013 S
8719877 Vondoenhoff et al. May 2014 B2
8774434 Zhao et al. Jul 2014 B2
8831266 Huang Sep 2014 B1
8891800 Shaffer Nov 2014 B1
8994498 Agrafioti et al. Mar 2015 B2
D728107 Martin et al. Apr 2015 S
9013145 Castillo et al. Apr 2015 B2
9037125 Kadous May 2015 B1
D733103 Jeong et al. Jun 2015 S
9081944 Camacho et al. Jul 2015 B2
9510159 Cuddihy et al. Nov 2016 B1
D773439 Walker Dec 2016 S
D775158 Dong et al. Dec 2016 S
D777710 Palmborg et al. Jan 2017 S
9544689 Fisher et al. Jan 2017 B2
D788079 Son et al. May 2017 S
20010005197 Mishra et al. Jun 2001 A1
20010027121 Boesen Oct 2001 A1
20010043707 Leedom Nov 2001 A1
20010056350 Calderone et al. Dec 2001 A1
20020002413 Tokue Jan 2002 A1
20020007510 Mann Jan 2002 A1
20020010590 Lee Jan 2002 A1
20020030637 Mann Mar 2002 A1
20020046035 Kitahara et al. Apr 2002 A1
20020057810 Boesen May 2002 A1
20020076073 Taenzer et al. Jun 2002 A1
20020118852 Boesen Aug 2002 A1
20030002705 Boesen Jan 2003 A1
20030065504 Kraemer et al. Apr 2003 A1
20030079165 Ffrench Apr 2003 A1
20030100331 Dress et al. May 2003 A1
20030104806 Ruef et al. Jun 2003 A1
20030115068 Boesen Jun 2003 A1
20030125096 Boesen Jul 2003 A1
20030218064 Conner et al. Nov 2003 A1
20040070564 Dawson et al. Apr 2004 A1
20040160511 Boesen Aug 2004 A1
20050017842 Dematteo Jan 2005 A1
20050043056 Boesen Feb 2005 A1
20050094839 Gwee May 2005 A1
20050125320 Boesen Jun 2005 A1
20050148883 Boesen Jul 2005 A1
20050165663 Razumov Jul 2005 A1
20050196009 Boesen Sep 2005 A1
20050251455 Boesen Nov 2005 A1
20050266876 Boesen Dec 2005 A1
20060029246 Boesen Feb 2006 A1
20060073787 Lair et al. Apr 2006 A1
20060074671 Farmaner et al. Apr 2006 A1
20060074808 Boesen Apr 2006 A1
20060166715 Engelen et al. Jul 2006 A1
20060166716 Seshadri et al. Jul 2006 A1
20060220915 Bauer Oct 2006 A1
20060258412 Liu Nov 2006 A1
20060276987 Bolander Dec 2006 A1
20080076972 Dorogusker et al. Mar 2008 A1
20080090622 Kim et al. Apr 2008 A1
20080146890 LeBoeuf et al. Jun 2008 A1
20080187163 Goldstein et al. Aug 2008 A1
20080253583 Goldstein et al. Oct 2008 A1
20080254780 Kuhl et al. Oct 2008 A1
20080255430 Alexandersson et al. Oct 2008 A1
20090003620 McKillop et al. Jan 2009 A1
20090008275 Ferrari et al. Jan 2009 A1
20090017881 Madrigal Jan 2009 A1
20090073070 Rofougaran Mar 2009 A1
20090097689 Prest et al. Apr 2009 A1
20090105548 Bart Apr 2009 A1
20090154739 Zellner Jun 2009 A1
20090191920 Regen et al. Jul 2009 A1
20090245559 Boltyenkov et al. Oct 2009 A1
20090261114 McGuire et al. Oct 2009 A1
20090296968 Wu et al. Dec 2009 A1
20100033313 Keady et al. Feb 2010 A1
20100203831 Muth Aug 2010 A1
20100207651 Suto Aug 2010 A1
20100210212 Sato Aug 2010 A1
20100320961 Castillo et al. Dec 2010 A1
20110102276 Jimenez May 2011 A1
20110140844 McGuire et al. Jun 2011 A1
20110239497 McGuire et al. Oct 2011 A1
20110286615 Olodort et al. Nov 2011 A1
20120057740 Rosal Mar 2012 A1
20120155670 Rutschman Jun 2012 A1
20130106454 Liu May 2013 A1
20130316642 Newham Nov 2013 A1
20130346168 Zhou et al. Dec 2013 A1
20140014697 Schmierer et al. Jan 2014 A1
20140079257 Ruwe et al. Mar 2014 A1
20140106677 Altman Apr 2014 A1
20140122116 Smythe May 2014 A1
20140146973 Liu May 2014 A1
20140153768 Hagen et al. Jun 2014 A1
20140163771 Demeniuk Jun 2014 A1
20140185828 Helbling Jul 2014 A1
20140219467 Kurtz Aug 2014 A1
20140222462 Shakil et al. Aug 2014 A1
20140235169 Parkinson et al. Aug 2014 A1
20140270227 Swanson Sep 2014 A1
20140270271 Dehe et al. Sep 2014 A1
20140335908 Krisch et al. Nov 2014 A1
20140348367 Vavrus et al. Nov 2014 A1
20150028996 Agrafioti et al. Jan 2015 A1
20150035643 Kursun Feb 2015 A1
20150036835 Chen Feb 2015 A1
20150110587 Hori Apr 2015 A1
20150148989 Cooper et al. May 2015 A1
20150245127 Shaffer Aug 2015 A1
20150264472 Aase Sep 2015 A1
20150264501 Hu Sep 2015 A1
20150358751 Deng Dec 2015 A1
20150373467 Gelter Dec 2015 A1
20150373474 Kraft et al. Dec 2015 A1
20160033280 Moore et al. Feb 2016 A1
20160072558 Hirsch et al. Mar 2016 A1
20160073189 Lindén et al. Mar 2016 A1
20160125892 Bowen et al. May 2016 A1
20160353196 Baker et al. Dec 2016 A1
20160360350 Watson et al. Dec 2016 A1
20170059152 Hirsch et al. Mar 2017 A1
20170060262 Hviid et al. Mar 2017 A1
20170060269 Förstner et al. Mar 2017 A1
20170061751 Loermann et al. Mar 2017 A1
20170062913 Hirsch et al. Mar 2017 A1
20170064426 Hviid Mar 2017 A1
20170064428 Hirsch Mar 2017 A1
20170064432 Hviid et al. Mar 2017 A1
20170064437 Hviid et al. Mar 2017 A1
20170078780 Qian et al. Mar 2017 A1
20170078785 Qian et al. Mar 2017 A1
20170108918 Boesen Apr 2017 A1
20170109131 Boesen Apr 2017 A1
20170110124 Boesen et al. Apr 2017 A1
20170110899 Boesen Apr 2017 A1
20170111723 Boesen Apr 2017 A1
20170111725 Boesen et al. Apr 2017 A1
20170111726 Martin et al. Apr 2017 A1
20170111740 Hviid et al. Apr 2017 A1
20170127168 Briggs et al. May 2017 A1
20170142511 Dennis May 2017 A1
20170151447 Boesen Jun 2017 A1
20170151668 Boesen Jun 2017 A1
20170151918 Boesen Jun 2017 A1
20170151930 Boesen Jun 2017 A1
20170151957 Boesen Jun 2017 A1
20170151959 Boesen Jun 2017 A1
20170153114 Boesen Jun 2017 A1
20170153636 Boesen Jun 2017 A1
20170154532 Boesen Jun 2017 A1
20170155985 Boesen Jun 2017 A1
20170155992 Perianu et al. Jun 2017 A1
20170155993 Boesen Jun 2017 A1
20170155997 Boesen Jun 2017 A1
20170155998 Boesen Jun 2017 A1
20170156000 Boesen Jun 2017 A1
20170178631 Boesen Jun 2017 A1
20170180842 Boesen Jun 2017 A1
20170180843 Perianu et al. Jun 2017 A1
20170180897 Perianu Jun 2017 A1
20170188127 Perianu et al. Jun 2017 A1
20170188132 Hirsch et al. Jun 2017 A1
20170193978 Goldman Jul 2017 A1
20170195829 Belverato et al. Jul 2017 A1
20170208393 Boesen Jul 2017 A1
20170214987 Boesen Jul 2017 A1
20170215016 Dohmen et al. Jul 2017 A1
20170230752 Dohmen et al. Aug 2017 A1
20170251933 Braun et al. Sep 2017 A1
20170257698 Boesen et al. Sep 2017 A1
20170263236 Boesen et al. Sep 2017 A1
20170273622 Boesen Sep 2017 A1
Foreign Referenced Citations (21)
Number Date Country
204244472 Apr 2015 CN
104683519 Jun 2015 CN
104837094 Aug 2015 CN
1469659 Oct 2004 EP
1017252 May 2006 EP
2903186 Aug 2015 EP
2074817 Apr 1981 GB
2508226 May 2014 GB
2008103925 Aug 2008 WO
2008113053 Sep 2008 WO
2007034371 Nov 2008 WO
2011001433 Jan 2011 WO
2012071127 May 2012 WO
2013134956 Sep 2013 WO
2014046602 Mar 2014 WO
2014043179 Jul 2014 WO
2015061633 Apr 2015 WO
2015110577 Jul 2015 WO
2015110587 Jul 2015 WO
2016032990 Mar 2016 WO
2016187869 Dec 2016 WO
Non-Patent Literature Citations (50)
Entry
Akkermans, “Acoustic Ear Recognition for Person Identification”, Automatic Identification Advanced Technologies, 2005 pp. 219-223.
Announcing the $3,333,333 Stretch Goal (Feb. 24, 2014).
Ben Coxworth: “Graphene-based ink could enable low-cost, foldable electronics”, “Journal of Physical Chemistry Letters”, Northwestern University, (May 22, 2013).
Blain: “World's first graphene speaker already superior to Sennheiser MX400”, htt://www.gizmag.com/graphene-speaker-beats-sennheiser-mx400/31660, (Apr. 15, 2014).
BMW, “BMW introduces BMW Connected-The personalized digital assistant”, “http://bmwblog.com/2016/01/05/bmw-introduces-bmw-connected-the-personalized-digital-assistant”, (Jan. 5, 2016).
BRAGI Is On Facebook (2014).
BRAGI Update—Arrival Of Prototype Chassis Parts—More People—Awesomeness (May 13, 2014).
BRAGI Update—Chinese New Year, Design Verification, Charging Case, More People, Timeline(Mar. 16, 2015).
BRAGI Update—First Sleeves From Prototype Tool—Software Development Kit (Jun. 5, 2014).
BRAGI Update—Lets Get Ready To Rumble, A Lot To Be Done Over Christmas (Dec. 22, 2014).
BRAGI Update—Memories From Apr.—Update On Progress (Sep. 16, 2014).
BRAGI Update—Memories from May—Update On Progress—Sweet (Oct. 13, 2014).
BRAGI Update—Memories From One Month Before Kickstarter—Update On Progress (Jul. 10, 2014).
BRAGI Update—Memories From The First Month of Kickstarter—Update on Progress (Aug. 11, 2014).
BRAGI Update—Memories From The Second Month of Kickstarter—Update On Progress (Aug. 22, 2014).
BRAGI Update—New People @BRAGI—Prototypes (Jun. 26, 2014).
BRAGI Update—Office Tour, Tour To China, Tour to CES (Dec. 11, 2014).
BRAGI Update—Status On Wireless, Bits and Pieces, Testing-Oh Yeah, Timeline(Apr. 24, 2015).
BRAGI Update—The App Preview, The Charger, The SDK, BRAGI Funding and Chinese New Year (Feb. 11, 2015).
BRAGI Update—What We Did Over Christmas, Las Vegas & CES (Jan. 19, 2014).
BRAGI Update—Years of Development, Moments of Utter Joy and Finishing What We Started(Jun. 5, 2015).
BRAGI Update-Alpha 5 and Back To China, Backer Day, On Track(May 16, 2015).
BRAGI Update-Beta2 Production and Factory Line(Aug. 20, 2015).
BRAGI Update-Developer Units Shipping and Status(Oct. 5, 2015).
BRAGI Update-Developer Units Started Shipping and Status (Oct. 19, 2015).
BRAGI Update-Developer Units, Investment, Story and Status(Nov. 2, 2015).
BRAGI Update-Getting Close(Aug. 6, 2015).
BRAGI Update-On Track, Design Verification, How It Works and What's Next(Jul. 15, 2015).
BRAGI Update-Status On Wireless, Supply, Timeline and Open House@BRAGI(Apr. 1, 2015).
BRAGI Update-Unpacking Video, Reviews On Audio Perform and Boy Are We Getting Close(Sep. 10, 2015).
Healthcare Risk Management Review, “Nuance updates computer-assisted physician documentation solution” (Oct. 20, 2016).
Hoffman, “How to Use Android Beam to Wirelessly Transfer Content Between Devices”, (Feb. 22, 2013).
Hoyt et. al., “Lessons Learned from Implementation of Voice Recognition for Documentation in the Military Electronic Health Record System”, The American Health Information Management Association (2017).
Hyundai Motor America, “Hyundai Motor Company Introduces A Health + Mobility Concept For Wellness In Mobility”, Fountain Valley, Californa (2017).
International Search Report & Written Opinion, PCT/EP2016/070247 (dated Nov. 18, 2016).
Last Push Before The Kickstarter Campaign Ends on Monday 4pm CET (Mar. 28, 2014).
Nemanja Paunovic et al, “A methodology for testing complex professional electronic systems”, Serbian Journal of Electrical Engineering, vol. 9, No. 1, Feb. 1, 2012, pp. 71-80, XPO55317584, YU.
Nigel Whitfield: “Fake tape detectors, ‘from the stands’ footie and UGH? Internet of Things in my set-top box”; http://www.theregister.co.uk/2014/09/24/ibc_round_up_object_audio_dlna_iot/ (Sep. 24, 2014).
Nuance, “ING Netherlands Launches Voice Biometrics Payment System in the Mobile Banking App Powered by Nuance”, “https://www.nuance.com/about-us/newsroom/press-releases/ing-netherlands-launches-nuance-voice-biometrics.html”, 4 pages (Jul. 28, 2015).
Staab, Wayne J., et al., “A One-Size Disposable Hearing Aid is Introduced”, The Hearing Journal 53(4):36-41) Apr. 2000.
Stretchgoal—It's Your Dash (Feb. 14, 2014).
Stretchgoal—The Carrying Case for The Dash (Feb. 12, 2014).
Stretchgoal—Windows Phone Support (Feb. 17, 2014).
The Dash + The Charging Case & The BRAGI News (Feb. 21, 2014).
The Dash-A Word From Our Software, Mechanical and Acoustics Team + An Update (Mar. 11, 2014).
Update From BRAGI—$3,000,000—Yipee (Mar. 22, 2014).
Wertzner et al., “Analysis of fundamental frequency, jitter, shimmer and vocal intensity in children with phonological disorders”, V. 71, n.5, 582-588, Sep./Oct. 2005; Brazilian Journal of Othrhinolaryngology.
Wikipedia, “Gamebook”, https://en.wikipedia.org/wiki/Gamebook, Sep. 3, 2017, 5 pages.
Wikipedia, “Kinect”, “https://en.wikipedia.org/wiki/Kinect”, 18 pages, (Sep. 9, 2017).
Wikipedia, “Wii Balance Board”, “https://en.wikipedia.org/wiki/Wii_Balance_Board”, 3 pages, (Jul. 20, 2017).
Related Publications (1)
Number Date Country
20180109891 A1 Apr 2018 US
Provisional Applications (1)
Number Date Country
62211724 Aug 2015 US
Divisions (1)
Number Date Country
Parent 15244834 Aug 2016 US
Child 15843140 US