An attachment for use with a mobile device with an imaging device and a mobile-device light source can include one or more of an attachment base and an attachment body. The attachment base can be configured to secure the attachment body to the mobile device via a case for the mobile device. The attachment body can include at least one optical device for use with the imaging device, and an optical sensor to receive optical control signals from the mobile-device light source.
|
1. An attachment assembly for use with a mobile device and a case for the mobile device, the mobile device including an imaging device and a mobile-device light source, and the case including a case optical opening that is optically aligned with one or more of the imaging device and the mobile-device light source when the case is secured to the mobile device, the attachment assembly comprising:
an attachment base configured to be secured to the case, with a cut-out of the attachment base disposed at least partly around the case optical opening; and
an attachment body configured to be removably secured to the attachment base in order to removably secure the attachment body to the case;
the attachment body including:
at least one optical device for use with the imaging device during one or more of image targeting and image acquisition; and
a protrusion with a first window and a second window;
the protrusion of the attachment body being configured to extend into the case optical opening, when the attachment body is removably secured to the attachment base and the attachment base is secured to the case, so that the first window is in optical alignment with the imaging device and the second window is in optical alignment with the mobile-device light source.
2. The attachment assembly according to
3. The attachment assembly according to
wherein the at least one optical device of the attachment body includes a beam splitter and a targeting light source;
wherein the beam splitter is configured to direct light from the targeting light source out of the third window onto an imaging target; and
wherein the beam splitter is further configured to permit light to pass from the third window to the first window, to allow the imaging device to acquire images of the imaging target.
4. The attachment assembly according to
a chassis configured to secure the beam splitter and the targeting light source within the attachment body, with the targeting light source in optical alignment with the beam splitter and with the beam splitter in optical alignment with the first and third windows.
5. The attachment assembly according to
6. The attachment assembly according to
wherein the chassis is configured to engage a feature on the internal support structure to secure the beam splitter and the targeting light source within the attachment body.
7. The attachment assembly according to
wherein the at least one optical device of the attachment body includes at least one attachment light source that is disposed in optical alignment with the fourth window to provide illumination for image acquisition.
8. The attachment assembly according to
a circuit assembly including a plurality of printed circuit boards (“PCBs”) secured to each other by flexible connectors;
wherein, the circuit assembly is configured to be installed within the attachment body with the circuit assembly in a folded configuration, in which a first PCB with a targeting light source is disposed perpendicularly to a second PCB with an optical sensor, and in which the second PCB is disposed parallel to but perpendicularly offset from a third PCB with a power connector.
9. The attachment assembly according to
a chassis configured to secure the targeting light source within the attachment body;
wherein the attachment body further includes a third window;
wherein, when the attachment body is secured to the attachment base and the attachment base is secured to the case, the third window is in optical alignment with the first window to enable image acquisition by the imaging device via the first and third windows; and
wherein the chassis secures the targeting light source in optical alignment with the third window by securing the first PCB relative to the third window.
10. The attachment assembly according to
wherein the attachment body includes a different one of the attachment rail and the attachment groove; and
wherein the attachment rail extends into the attachment groove to secure the attachment body to the attachment base.
|
This application is a continuation-in-part of co-pending U.S. patent application Ser. No. 15/285,576, titled “Optical Accessory for Attachment to Mobile Device and filed on Oct. 5, 2016, which is a continuation-in-part of co-pending U.S. patent application Ser. No. 15/092,028, titled “Optical Accessory for Attachment to Mobile Device” and filed on Apr. 6, 2016, which is a continuation-in-part of co-pending U.S. patent application Ser. No. 14/682,062, titled “System for Capturing a Coded Image” and filed on Apr. 8, 2015 and a continuation-in-part of co-pending U.S. patent application Ser. No. 14/682,072, titled “Aimer Accessory for Capturing a Coded Image” and filed on Apr. 8, 2015, all of which are incorporated herein by reference.
Not applicable.
The present invention relates to devices for optically acquiring data, and in particular, to optical barcode scanning devices.
Handheld image and barcode scanning devices are well known and used in a wide range of enterprise applications. Barcode scanners are regularly used in connection with checkout stations at supermarkets and other retail establishments for reading barcodes on consumer goods. They are also useful in inventory collection and control for warehousing, shipping and storage of products.
Mobile electronic devices, such as smartphones and tablet computers, are well known and leveraged in a wide range of corporate and personal applications. Such devices, executing specialized software, are frequently being utilized to scan and decode barcodes on products, promotions, and coupons. The specialized software, or app, is typically downloaded to the device but may be preloaded. The app configures the smartphone or mobile device to use the built-in camera in the smartphone or mobile device to scan barcodes, such as those found on products or in magazines, stores, websites, and billboards.
Today's enterprise and personal workplace is changing. Technology is becoming more integrated with daily processes and procedures. In a mobile workplace, the mobile electronic device may provide a more cost effective and flexible alternative to traditional, dedicated and purpose-built handheld scanning devices.
However, scanning a barcode with a smartphone or other mobile electronic device can be cumbersome. To scan a barcode, the user is typically required to view the barcode through the display screen of the device in order to aim and focus the camera lens before the barcode can be successfully decoded. If the device's camera is not properly aimed and focused, it may be difficult or impossible to read the barcode, or may take an excessive amount of time to capture, detect, and decode the barcode from an image. As a result, the scanning of barcodes using a mobile electronic device is inefficient whenever there is a need for convenient, rapid, or high volume barcode detection and decoding. Improving the efficiency and ease-of-use of barcode scanning, using the built-in camera along with enhanced decoding software, is desirable.
Thus, methods and devices are needed to improve the efficiency and ease-of-use of scanning a barcode using a mobile device, such as a smartphone.
Technologies are described for optical devices, and in particular to a system for scanning a barcode using a smartphone and other mobile devices.
Some embodiments of the invention provide an attachment for use with a mobile device and a case for the mobile device. The mobile device can include an imaging device and a mobile-device light source, and the case can include a case optical opening that is optically aligned with one or more of the imaging device and the mobile-device light source when the case is secured to the mobile device. The attachment can include an attachment base and an attachment body. The attachment base can be configured to be secured to the case with the attachment base disposed at least partly within the case optical opening, and the attachment body can be configured to be removably secured to the attachment base. The attachment body can include at least one optical device for use with the imaging device during image targeting and image acquisition. The attachment base can removably secure the attachment body to the case when the attachment body is secured to the attachment base and the attachment base is secured to the case.
Some embodiments of the invention provide a system for communicating with a mobile device, where the mobile device includes an imaging device and a mobile-device light source. The system can include an attachment with a light detector, at least one attachment light source, and a processor. The light detector can be configured to receive optical signals from the mobile-device light source. The processor can be configured to, based upon the optical signals received at the light detector from mobile-device light source, at least one of activate the at least one attachment light source to direct light onto an external target and configure at least one illumination parameter for the attachment. The processor can further be configured to activate the at least one attachment light source to communicate with the mobile device via the imaging device.
Some embodiments of the invention provide a method of communicating information between a mobile device and an attachment, where the mobile device includes an imaging device and a mobile-device light source, and the attachment includes a light detector and at least one attachment light source. First optical signals can be received at the light detector. Based on the first optical signals, at least one of: the at least one attachment light source can be activated for image acquisition and targeting; and at least one illumination parameter for the attachment can be configured. The at least one attachment light source can also be activated to provide second optical signals to the imaging device to transmit non-image information to the mobile device.
Some embodiments of the invention provide an attachment assembly for use with a mobile device and a case for the mobile device, with the mobile device including an imaging device and a mobile-device light source, and the case including a case optical opening that is optically aligned with one or more of the imaging device and the mobile-device light source when the case is secured to the mobile device. An attachment base can be configured to be secured to the case with a cut-out of the attachment base disposed at least partly around the case optical opening. An attachment body can be configured to be removably secured to the attachment base, in order to removably secure the attachment body to the case. The attachment body can include at least one optical device for use with the imaging device during one or more of image targeting and image acquisition, and a protrusion with a first window and a second window. The protrusion of the attachment body can be configured to extend into the case optical opening, when the attachment body is removably secured to the attachment base and the attachment base is secured to the case, so that the first window is in optical alignment with the imaging device and the second window is in optical alignment with the mobile-device light source.
Some embodiments of the invention provide a system for communicating with a mobile device that is configured to acquire and analyze images of symbols, with the mobile device including an imaging device and a mobile-device light source. An attachment can include an optical sensor configured to receive optical signals from the mobile-device light source, and at least one attachment light source. A processor can be configured to, based upon the optical signals received at the optical sensor from mobile-device light source, at least one of: activate the at least one attachment light source to direct light onto an external target; and configure at least one illumination parameter for the attachment. The processor can be further configured to activate the at least one attachment light source to communicate with the mobile device via the imaging device.
Some embodiments of the invention provide a method of communicating information between a mobile device and an attachment, with the mobile device including an imaging device and a mobile-device light source, and with the attachment including an optical sensor and at least one attachment light source. First optical signals can be received at the optical sensor. Based on the first optical signals, one or more of the following can be implemented: activating the at least one attachment light source for one or more of image acquisition and image targeting; and configuring at least one illumination parameter for the attachment. The at least one attachment light source can be activated to provide second optical signals to the imaging device to transmit non-image information to the mobile device.
To the accomplishment of the foregoing and related ends, the invention, then, comprises the features hereinafter fully described. The following description and the annexed drawings set forth in detail certain illustrative aspects of the invention. However, these aspects are indicative of but a few of the various ways in which the principles of the invention can be employed. Other aspects, advantages and novel features of the invention will become apparent from the following detailed description of the invention when considered in conjunction with the drawings.
The features and advantages of the invention are apparent from the following description taken in conjunction with the accompanying drawings in which:
In the following detailed description, reference is made to the accompanying drawings that form a part hereof. In the drawings, similar symbols typically identify similar components, unless context dictates otherwise. The illustrative embodiments described in the detailed description, drawings, and claims are not meant to be limiting. Other embodiments may be utilized, and other changes may be made, without departing from the spirit or scope of the subject matter presented herein. It will be readily understood that the aspects of the present disclosure, as generally described herein, and illustrated in the Figures, can be arranged, substituted, combined, separated, and designed in a wide variety of different configurations, all of which are explicitly contemplated herein.
Disclosed herein are methods and apparatus that permit users of mobile devices, such as a smartphone, to perform “blind and targeted scanning” of barcodes and other information bearing symbols. Generally, the methods and apparatus include an aimer module that collimates diffuse light from a lamp (LED or flash mechanism) on a mobile device for use in capturing a barcode image. The aimer module may also be integrated into a given mobile device or a protective case. Alternatively, the aimer module may be configured as an attachment for retrofit of a mobile device. Operation of the mobile device may be complemented with additional software to take advantage of the functionality of the aimer module. In order to provide some background for the teachings herein, some context is first provided.
Referring now to
For purposes of convention and to aid in the discussion herein, terms of orientation are provided with regard to the figures. For example,
Referring now to
The CPU 26 may be an ARM or other processor. The power supply 27 may be from a battery or a source of direct current (DC), such as a transformer coupled to a conventional alternating current (AC) outlet. User controls 8 may be a home button 6 and an on/off switch 3 shown in
The communication interface 23 may include a wired interface and/or a wireless interface. The wireless interface may include a wireless service processor. Illustrative wireless interfaces may make use of a protocol such as cellular, Bluetooth, Wi-Fi, near field technology (NFC), ZigBee, or other technology. Communication services provided over the wireless communication interface may include Wi-Fi, Bluetooth, Ethernet, DSL, LTE, PCS, 2G, 3G, 4G, LAN, CDMA, TDMA, GSM, WDM and WLAN. The communication interface 23 may include an auditory channel. That is, the communication interface 23 may include a microphone for receiving voice commands, and may further include a speaker. In some embodiments, the speaker may provide an auditory signal when a barcode has been read. The communication interface 23 may further include a status light or other such visual indicators.
The communication interface 23 provides for, among other things, voice communications as well as data communications. The data communications may be used to provide for communication of software and data (such as at least one image; results of analyses, and other such types of data). Communication through the communication interface 23 may be bi-directional or in a single direction.
The mobile device 10 may include additional components such as sensors. Illustrative sensors may include an accelerometer that provides for orientation information and a GPS sensor that provides for location information. The mobile device may also include peripheral interface and communication ports.
As discussed herein, the term “software” 22 generally refers to machine-executable instructions that provide for the implementation of the methods of this disclosure that are explained below. The machine-executable instructions may be stored on non-transitory machine-readable media such as memory 21. Illustrative methods that may be implemented to actuate the mobile device hardware may include instructions for operation of the camera 7, the lamp 9, communications through the communication interface 23, and other aspects of this disclosure as discussed further below. In some of the illustrative embodiments discussed herein, the software 22 provides for detecting and decoding barcodes within an image. However, it should be noted that the term “software” might describe sets of instructions to perform a great variety of functions.
The memory 21 may include multiple forms of memory. For example, the memory 21 may include non-volatile random access memory (NVRAM) and/or volatile random access memory (RAM). Generally, the non-volatile random access memory (NVRAM) is useful for storing software 22 as well as data generated by or needed for operation of the software 22 such as rules, configurations and similar data. The memory 21 may include read only memory (ROM). The read only memory (ROM) may be used to store firmware that provides instruction sets necessary for basic operation of the components within the topology 20.
The camera 7 may include any appropriate sensor and at least one optical element such as a lens. Generally, the camera 7 may include those components as needed to record (also referred to as “capture”) images of items such as a barcode and further include photodetectors, amplifiers, transistors, and processing hardware and power management hardware. The lamp 9 may include any appropriate source of illumination. Illustrative components for the lamp 9 include at least one light emitting diode (LED).
Although the illustrative mobile device 10 disclosed is a smartphone, the mobile device 10 is not limited to this embodiment and may include other devices. Accordingly, it is not required that the mobile device 10 incorporate all of the components of
As discussed herein, the term “barcode” generally refers to an optical machine-readable symbology that contains a representation of data. Generally, any given barcode is a representation of data that is related to the object to which it is attached. A barcode as discussed herein may include data that is arranged in a one-dimensional (1D) array, a two-dimensional (2D) array; and/or a 3D physical tag. Information may be conveyed in a given barcode according to arrangements of symbology, and may further convey information in a plurality of wavelengths and/or colors (i.e., varying groups of visible wavelengths).
Illustrative forms of one-dimensional (1D) barcodes include: Codabar; Code 25 (Interleaved); Code 25 (Non-interleaved); Code 11; Code 39; Code 93; Code 128; CPC Binary; DUN 14; EAN 2; EAN 5; EAN-8, EAN-13; Facing Identification Mark; GS1-128; GS1 DataBar; HIBC; Intelligent Mail barcode; ITF-14; JAN; KarTrak ACI; Latent image barcode; MSI; Pharmacode; PLANET; Plessey; PostBar; POSTNET; RM4SCC/KIX; Telepen; and UPC., as well as others.
Illustrative forms of two-dimensional (2D) barcodes (also referred to as a “matrix code”) include: Aztec Code; Code 1; ColorCode; Color Construct Code; CrontoSign; CyberCode; d-touch; DataGlyphs; Data Matrix; Datastrip Code; digital paper; EZcode; Color; High Capacity Color Barcode; HueCode; InterCode; MaxiCode; MMCC; NexCode; Nintendo e-Reader; Dotcode; PDF417; QR code; ShotCode; SPARQCode; and others.
As discussed herein, a “light pipe” or “light tube” is a physical structure used for transporting of light for the purpose of illumination and is an example of an optical waveguide. A light pipe generally provides the transport of light to another location, minimizing the loss of light. A light pipe may include highly transmissive material, and may include reflective materials, collectors, reflectors, concentrators, at least one lens, and other components as deemed appropriate. An illustrative light pipe is an optical fiber. Light pipes, as discussed herein, may be formed of any suitable material. Illustrative materials include acrylic plastic, silicon glass, and other such materials. A light pipe may be hollow and open or closed to the external atmosphere. A light pipe can be configured to transmit only light of a particular color (or colors).
Generally, the following discussion provides an introduction to an aimer module, methods for use of the aimer module, aspects of some illustrative embodiments of the aimer module, and some detail on software that may be used in conjunction with the aimer module.
Broadly speaking, an aimer module for a mobile device and method of use is provided by this disclosure. The aimer module collimates diffuse light from a lamp on a mobile device for use in capturing a barcode image. The aimer module includes a means for receiving light from a lamp of the mobile device, and generating a light pattern on the surface containing a barcode. The receiving and generating means may include a grating or configuration of mirrors. Registration of the light pattern and the barcode in a scan area enhances the ability of the specialized software on the mobile device to read the barcode.
As used herein, the term “registration” means that a barcode and a light pattern generated by the aimer module on the surface containing the barcode are in the viewing angle of the camera. This viewing angle can change depending on the lens and the smartphone. In one illustrative example, the camera may use a cone type lens. In this example, if the barcode and the light pattern on the surface containing the barcode are both in the cone of viewing, there would be a registration of the light pattern and the barcode according to this disclosure. As explained in this disclosure, once the barcode and the light pattern generated by the aimer module on the surface containing the barcode are in “registration,” the smartphone may capture the barcode image and decode the barcode as explained below.
Broadly speaking, there are at least three types of registration contemplated by this disclosure. These three types of registration correspond to three modes of operation of the aimer module contemplated by this disclosure. These three modes of operation are blind mode scanning, targeted mode scanning, and smartphone display mode scanning, otherwise referred to as display mode scanning. In addition, both blind mode scanning and targeted mode scanning may be used with or without display mode of operation. Hence, this disclosure provides for at least five modes of operation. These modes of operation are depicted in the Table 1 and are explained in greater detail below.
TABLE 1
Modes of operation of Smartphone or Other
Mobile Device with Aimer Module
Targeted
Display
Blind Mode
Mode
Mode
Configuration
Operation
Operation
Operation
Blind Mode
Blind Mode
Configuration ON -
Blind
Display Not Used
Blind Mode
Blind Mode
Configuration ON -
Targeted
Display Used
Targeted MODE
Targeted
Configuration ON -
Mode Blind
Display Not Used
Targeted MODE
Targeted
Configuration ON -
Mode
Display Used
Targeted
Blind Mode AND
Display
Targeted Mode
Mode
Configurations OFF -
Display Used
In blind mode of operation, the light pattern on the surface containing the barcode can be anywhere in the cone of viewing. The user uses the light pattern generated by the aimer module of this disclosure as a pointer and points the light pattern at the surface containing the barcode. There is no need for the user to look through the display of the smartphone when operating the scanning features of this disclosure in blind mode. So long as the user aims the light pattern at the surface containing the barcode, such that the light pattern and barcode are both within the cone of viewing, there is a registration of the light pattern and the barcode in blind mode according to this disclosure. As indicated in Table 1, the user may employ blind mode operation with or without the use of the display. The most efficient manner of blind mode operation involves a blind mode blind operation without the use of the display. In this case, the user would simply look at and direct the light pattern generated by this disclosure at or around the barcode image in order to “register” the light pattern with the barcode image as previously explained. After registration, the barcode image is captured by activation of a mechanical trigger on the smartphone, an activation button on the display of the smartphone, or by lapse of a predetermined period of time after registration of the light pattern with the barcode image as explained below. However, in some cases of blind mode operation, the user may look through the display of the smartphone to assist in the guiding of the pattern of light at or about the barcode image. This mode of operation is known as blind mode targeted mode of operation since the display of the smartphone is used to “target” the pattern of light at or about the barcode image to generate the registration required for blind mode operation as taught by this disclosure.
In targeted mode of operation, the light pattern on the surface containing the barcode must hover over the barcode. As in blind mode, the user uses the light pattern generated by the aimer module of this disclosure as a pointer and points the light pattern at the surface containing the barcode. In targeted mode, the light pattern must hover over the barcode to be in registration unlike blind mode where registration may occur when the light pattern is shining outside the barcode but still within the cone of viewing. As the user aims the light pattern at the surface containing the barcode such that the light pattern is hovering over the barcode and within the cone of viewing, there is a registration of the light pattern and the barcode in targeted mode according to this disclosure. As indicated in Table 1, the user may employ targeted mode operation with or without the use of the display. The most efficient manner of targeted mode operation involves a targeted mode blind operation without the use of the display. In this case, the user would simply look at and “hover” the light pattern generated by this disclosure over the barcode image in order to “register” the light pattern with the barcode image as previously explained. After registration, the barcode image is captured by activation of a mechanical trigger on the smartphone, an activation button on the display of the smartphone, or by lapse of a predetermined period of time after registration of the light pattern with the barcode image as explained below. However, in some cases of targeted mode of operation, the user may look through the display of the smartphone to assist in the guiding of the pattern of light to hover over the barcode image. This mode of operation is known as targeted mode targeted mode of operation since the display of the smartphone is used to “target” the pattern of light to “hover” over the barcode image to generate the registration required for targeted mode operation as taught by this disclosure.
In display mode of operation, the user uses the display of the smartphone to point the camera lens at the image. So long as the user points the camera lens at the image such that the light pattern and barcode are both within the cone of viewing, there is a registration of the light pattern and the barcode in smartphone display mode according to this disclosure. The aimer module is not used when the smartphone is operating in display mode of operation. Instead of using the light pattern generated by the aimer module of this disclosure, the lamp of the smartphone is used conventionally to provide direct diffuse lighting for illuminating the barcode image in order that the smartphone can capture the barcode image.
Referring now to
In the illustrative embodiment depicted in
In some embodiments, at least one mirror is used with or without the grating 36. In some other embodiments, at least one mirror is used with additional optical elements as deemed appropriate. This is explained further in connection with
Referring now to
In
As shown in
The software 22 makes use of the light pattern 55 cast by the aimer accessory 30. Generally, once the software 22 has received a command from the user to commence scanning, or a predetermined period of time has elapsed after registration of the light pattern and the barcode, the software 22 begins processing images collected from the camera 7 on a continuing basis. When the light pattern 55 is appropriately manifested within the scan area 56, the software 22 identifies a focal point 57 (shown in
The decoding software of this disclosure takes care of decoding the images of the barcode captured by the smartphone. In both blind mode blind mode operation and targeted mode blind mode operation, there is no need for the user to look through the display of the smartphone when operating the scanning features of this disclosure in blind or targeted mode. In blind mode targeted mode operation, targeted mode targeted mode operation, and display mode operation, the user will look through the display to point the light at the barcode.
Further, in blind mode blind mode operation and blind mode targeted mode, it is only necessary for the user to aim the light pattern generated by the aimer module at the surface containing the barcode such that the light pattern and barcode are both within the cone of viewing. This ensures registration of the light pattern and the barcode in blind mode according to this disclosure. In targeted mode blind mode operation and targeted mode targeted mode operation, it is necessary for the user to aim the light pattern at the surface containing the barcode such that the light pattern is hovering over the barcode and within the cone of viewing. This ensures registration of the light pattern and the barcode in targeted mode according to this disclosure. In display mode, the aimer module is not used when the smartphone is operating in display mode of operation. Instead of using the light pattern generated by the aimer module of this disclosure, the lamp of the smartphone is used conventionally to provide direct diffuse lighting for illuminating the barcode image in order that the smartphone can capture the barcode image.
A user may find the blind mode of operation most efficient when a surface contains only a single barcode. With a single barcode within the cone of vision, the specialized software of the mobile device, equipped with an aimer module of this disclosure, recognizes there is only one barcode to decode. The decoding software may invoke the scan any time during the process as previously explained. No further logic is needed. However, when a surface contains two or more barcodes, the software of the aimer module requires further logic to determine which barcode to decode. This disclosure provides this further logic within the targeted mode of operation by requiring the user to point the light pattern within the barcode desired for decoding and keep the light pattern over the barcode (i.e., hover over the barcode). The user then initiates a trigger to capture the image or the user hovers over the barcode for a predetermined period of time which may be set by the user. Illustratively, this period of time may be one-half second, but the exact time is a matter of design choice. It will be appreciated that a user may use the aimer module of this disclosure in targeted mode to also scan a surface containing a single barcode. However, because this mode of operation requires the user to hover the light pattern over the barcode, it may be a less efficient procedure for scanning a single barcode than scanning the barcode in blind mode of operation, but with multiple barcodes present in a given area on a page, it may be the desired method of reading the targeted barcode. With display mode, the software of the aimer module requires further logic to determine when the user has lined up the camera lens with the barcode through the display. This logic is illustratively provided by a trigger the user may initiate after the display indicates the camera lens is lined up with the barcode.
The smartphone captures 73 one or more images and typically stores them in memory 21 (
Starting with one captured image, which may be the first image captured and stored in memory, the software of the aimer module will look 74 at an edge of the captured image.
The aimer module software then determines the symbology of the barcode. In this regard, the aimer module software will illustratively access a memory map of symbologies such as depicted in
If the aimer module software does not recognize the barcode type whether because it has not identified a start and/or stop character or the start and/or stop characters it has identified do not match the start and stop characters in the memory map depicted in
If the aimer module software recognizes the barcode type, the aimer module software decodes 76 the barcode and then calculates and matches 77 the check sum it has calculated with the check sum found in the pattern of the barcode. The aimer module software then determines 78 if the calculated error is correct (i.e., that the calculated check sum matches the check sum in the pattern of the barcode). If the calculated error value is not correct, the aimer module software will determine 83 if it has another captured image of the barcode to further use in this process of decoding the captured barcode. If the aimer module software determines there are further images available for use in the process, the aimer module software will advance 82 to the next image and repeat steps 76, 77, and 78. If the aimer module software determines there are no further images available for use in the process, the aimer module software prompts 84 the user that the scan failed and the process ends 86. This means that the user will need to begin the process over if the scan of the barcode remains of interest. If the aimer module software determines 78 that the calculated error is correct (i.e., that the calculated check sum matches the check sum in the pattern of the barcode), the aimer module software continues 79 the software program which can prompt the user that the scan was successful and the process ends 86. The notification can be an audible, a vibration, a display LED coloring or blinking, or any combination of these or other physical notifications.
Referring in particular to
Without the teachings of this disclosure, lamp 9 diffuses and emits light across a wide range of angles with respect to light axis, L. With this disclosure, the light from lamp 9 is collimated and redirected to the light shifted axis, LS, to improve the ability of the user to point the smartphone or mobile device's built-in camera at a barcode in order to capture and decode the barcode. Because the light is shifted, there is also less interference between the shifted light and the reflected image that is captured by the camera. This may in some circumstances allow the camera to capture a better quality image than with ambient light. While the effect of the offset is to increase the effective range, R, this increase was found to be negligible and to not significantly alter the advantages obtained by collimating the light and redirecting the collimated light to the light shifted axis, LS. The transformation of diffuse light from lamp 9 into a collimated beam of light according to this disclosure effectively serves to modify the lighting from lamp 9 into a flashlight. Advantageously, this “flashlight” allows for blind and targeted aiming of the mobile device at, and efficient scanning of, a barcode according to the teachings of this disclosure.
Moreover, ambient light may oftentimes be sufficient to allow for the capture of barcode images of a quality sufficient for decoding. An additional feature of this disclosure is that it provides additional lighting to the barcode surface which may improve the contrast of the dark and light barcodes and hence provide for capture of better quality barcode images.
The scanning software 214 includes the executable instructions for performing the scanning functions of registration and capturing a barcode image as described in
The decoder software includes the executable instructions for transforming the barcode image data represented by the electrical signals into an encoded ASCII character data string.
The data storage software 212 includes the executable instructions for storing and retrieving captured barcode images and other data in a memory. The library software 210 includes the executable instructions for storing and retrieving information such as symbology type from a library registry within the memory. Additionally, the library registry may also include information regarding a variety of aimer accessories 30. For example, a user may wish to exchange aimer accessories 30 while in the field, like to exchange a tube offset aimer of
In another embodiment, the instance of a barcode reader software 200 may recognize a specific aimer module shape and if recognized for a specific timeframe while hovering over a specific barcode for a programmed amount of time (−500 msec or 1 sec), then this triggers a barcode scan and initiates a decode of the barcode data.
The user interface software includes the executable instructions for displaying a graphical user interface on the display for configuring the instance of the barcode reader software 200 and for rendering images, such as an image of the barcode on the display of the smartphone. For example, user interface software 211 may generate text, alert information, auditory signals, alarms, warnings, pictures, graphics, or other types of output. In some embodiments, output of the interface software 211 may be used to invoke other functions. For example, output of the interface software 211 may be sent via communication interface software 216 to a printer, or it may be sent to a smartphone to initiate a phone call, or sent to any computing device to perform some other function.
The hardware controller software 215 includes the executable instructions for controlling the hardware of the smartphone such as controlling the camera lens to bring a barcode image into focus, energizing the lamp, controlling the display to render images, controlling the speaker of the smart phone to prompt a user, and so on.
The communication interface function 216 includes the executable instructions for communicating data to or from a remote device. The communicating to a remote device may include conducting a query of a remote source, such as a database, for more comprehensive information. The query may be received by the communication interface function 216 from the user through the user interface software 211. Similarly, a remote user may communicate information over the communication interface 216 to the smartphone. Thus, for example, a smartphone may be remotely programmed with software updates and updates to the database, such as the table of symbologies. Programming may occur over-the-air. Alternatively, the smart phone may be tethered to a remote device via a communication cable to provide such remote programming or bi-directional communication between the smart phone and the remote device. The remote device may be a computing device, for example, another smart phone, a desktop computer, or server, including a cloud server, capable of communicating with the smart phone that is operating according this disclosure.
The engine 201 includes the executable instructions that coordinate the operation of the foregoing and other programs on the smartphone.
The software 200 described in connection with
By virtue of the registration process of the light pattern 55 of this disclosure with a barcode 50 on a target as explained in this disclosure, an appropriately equipped mobile device 10 is capable of automatic scanning and reading of barcodes. That is, the mobile device 10 that is so equipped does not require human intervention to carefully focus the camera through the display 5. The user need not look through the view finder projected on the display to focus the image to be captured by the mobile device. Instead, in blind mode blind mode operation and target mode blind mode operation, the user need only point the collimated light that is generated according to this disclosure at the barcode. Accordingly, the teachings herein provide for enablement of “blind” and “targeted” blind mode scanning. That is, the blind or targeted scanning according to this disclosure permits a user to read a barcode without viewing and focusing of the device camera through use of the display 5 (shown in
In some embodiments, the software 22 of the code reader 200 depicted in
Referring now to
In various embodiments, the retainer 38 provides a clamping force to the mobile device 10 or to an external protective case surrounding mobile device 10. In some embodiments, the clamping force is realized by having opposing retainers 38. Opposing retainers 38 may be realized by having one retainer configured for retention on a left side of the mobile device 10 or protective case with the opposing retainer 38 configured for retention on a right side of the mobile device 10 or protective case (not shown). In some embodiments, the retainer 38 includes the detents, nipples, ridges or other features as may be known in the art to assist with retention and registration or alignment with mobile device 10.
In some embodiments, such as the one shown in
An aimer accessory according to this disclosure can be secured to a mobile device, or a case for a mobile device, in various ways. In some embodiments, an aimer accessory (e.g., the aimer accessory 30) can be secured directly to a mobile device or to a case using adhesives, adhesive strips (e.g., double-sided tapes), magnetic devices, fasteners (e.g., screws), and so on. In some embodiments, a clip-like tab such as the retainer 38 (see, e.g.,
In some embodiments, an aimer accessory can be formed from an attachment base and an attachment body that are configured to be removably secured together. With this type of arrangement, the attachment base can be secured to a mobile device or case (e.g., using adhesives, adhesive strips, magnetic devices, fasteners, and so on) independently of the attachment body. The attachment body, which can be configured to include an optical device such as a light pipe or arrangement of mirrors, can then be secured to the attachment base for use with the mobile device. This can be useful, for example, in order to allow for reliable and repeatable orientation of the attachment body—and the included optical device—relative to a camera or light source of the mobile device, without necessarily requiring a permanent engagement between the attachment body and the mobile device or case.
Specific examples of this type of arrangement are discussed below in the context of direct attachment to a mobile device and in the context of attachment to a mobile device via attachment to a case for the mobile device. It will be understood, however, that other arrangements are possible and that the principles discussed below (e.g., securing an attachment body with an optical element to a mobile device or case via attachment of the attachment body to an attachment base) can be applied to other embodiments, including various embodiments discussed above (e.g., the various arrangements of the aimer accessory 30 illustrated in
An aimer accessory 300 for a mobile device is illustrated in
In the embodiment illustrated, the attachment base 302 is formed as a single-piece body that includes a relatively large camera opening 306 configured for alignment with a camera of a mobile device (not shown in
The attachment base 302 also includes a light-source opening 316. Generally, the light-source opening 316 is disposed relative to the camera opening 306 so that when the camera opening 306 is aligned with a camera or camera lens of a mobile device, the light-source opening 316 is also appropriately aligned with a light source of the mobile device (e.g., a light source such as the optical element 32 illustrated in
In some embodiments, a light-source opening on an attachment base can be shaped to partly mask a light source on a mobile device. This can be useful, for example, if a light source on a mobile device is expected to be overly bright, or if a light source on a mobile device includes multiple light-emitting elements (e.g., LEDs), some of which it may be desirable to mask. In the embodiment illustrated, the light-source opening 316 is configured as a generally semi-circular or semi-ovular opening with one wall 316a of the light-source opening 316 configured as a solid blocking feature. This can be useful, for example, for use with light sources that include a white-light LED and a yellow-light LED, in order to block light from the yellow-light LED while allowing light from the white-light LED to pass through the attachment base 302 into the attachment body 304.
The attachment base 302 can also generally include structures to assist in removably securing the attachment body 304 to the attachment base 302. In the embodiment illustrated, for example, the attachment base 302 includes a set of attachment openings 318 and 320, each of which includes a respective overhang 322 and 324 formed by partially angled features 322a and 324a on an upper portion the attachment base 302. In the embodiment illustrated, the ends of the attachment openings 318 and 320 are offset from each other along a length direction 326, as are the ends of the overhangs 322 and 324 and the features 322a and 324a. In other embodiments, however, other configurations are possible.
Each of the attachment openings 318 and 320 is also generally adjacent to a respective indent 328 and 330, which are disposed on an opposite side of the respective attachment openings 318 and 320 from the respective overhangs 322 and 324. In the embodiment illustrated, the indent 328 is configured as a rounded indent spaced apart from the attachment opening 318 and the indent 330 is configured as a rounded indent extending into an edge of the attachment opening 320. In other embodiments, however, other configurations are possible.
Still referring to
In the embodiment illustrated, the shell 342 is configured to enclose an optical device configured as a mirror assembly including mirrors 344 and 346 and lens 348 (see
As illustrated in
Generally, the shell 342 can be configured for relatively low-profile attachment to a mobile device or case, and can include various features to facilitate use of the attachment body 304 with a camera of a mobile device. For example, a wall 342b of the shell 342 that is to be disposed generally adjacent to a field of view of a camera can be configured with an angled geometry so that interference with camera operation by the shell 342 can be minimized. The angled geometry of the wall 342b can also, for example, help to appropriately support one or more components of an optical device within the shell 342, such as the mirror 344 (e.g., as discussed above).
The attachment body 304 can also generally include features for removably securing the attachment body 304 to the attachment base 302. In the embodiment illustrated, for example, the attachment body 304 includes a set of attachment arms 364 and 366 extending out of a main opening 342c of the shell 342. The free end of each of the attachment arms 364 and 366 includes a respective protrusion 368 and 370, each of which can generally be configured with a complimentary (e.g., complimentarily angled) geometry to a corresponding one of the overhangs 322 and 324 on the attachment base 302.
In the embodiment illustrated, the ends of the protrusions 368 and 370 are offset from each other along the length direction 326, as are the ends of the attachment arms 364 and 366 generally. This arrangement can be similar to the offset arrangement for the attachment openings 318 and 320 and the overhangs 322 and 324, as discussed above. In other embodiments, however, other configurations are possible.
The attachment body 304 can also include features for engaging the indents 328 and 330 of the attachment base 302. In the embodiment illustrated, for example, each of the attachment arms 364 and 366 is disposed near, but spaced apart from, respective detents 372 and 374 (see
The attachment body 304 can also include various other features. In the embodiment illustrated, for example, the shell 342 includes an extended lower portion 376 that extends generally below a remainder of the shell 342 (e.g., a peripheral lower surface 378 of the shell 342), as well as an attachment lip 380 extending generally below the remainder of the extended lower portion 376. Generally, the attachment lip 380 can include a complimentary (e.g., complimentarily curved) geometry as the indent 308 in the camera opening 306 of the attachment base 302. In other embodiments, however, other configurations are possible.
In the embodiment illustrated, the attachment body 304 also includes an attachment tab 382, which can help to secure the attachment body 304 directly to a mobile device or case. In the embodiment illustrated, the attachment tab 382 exhibits a generally curved profile extending away from and below the shell 342, with an elongated detent 384 near a free end of the attachment tab 382 to engage a corresponding groove on a case or other object.
As illustrated in particular in
As also noted above, the attachment openings 318 and 320 are offset from each other along the length direction 326, as are the protrusions 368 and 370 and the attachment arms 364 and 366. This arrangement can result in a relatively stable connection between the attachment body 304 and the attachment base 302, due to contact points between the protrusion 368 and the angled feature 322a being offset from contact points between the protrusion 370 and the angled feature 324a along both the length and the width of the assembly.
Other relative offsets of various features can also be useful. For example, as illustrated in
In some aspects, a lack of offsets between different parts of the aimer accessory 300 can also provide useful stability. For example, as illustrated in
With the attachment body 304 and the attachment base 302 assembled as illustrated, the camera opening 306 of the attachment base 302 is left generally open, while the light-source opening 316 of the attachment base 302 is fully enclosed (at least on one side of the attachment base 302) by the shell 342 of the attachment body 304. Further, the light-source opening 316 is generally aligned with one or more components of the optical device of the attachment body 304 (e.g., with the first mirror 344 within the shell 342). Accordingly, the assembled aimer accessory 300 can be used with a camera of a mobile device to capture images via the camera opening 306. Further, due to the enclosure of the light-source opening 316 by the shell 342, the assembled aimer accessory 300 can be used both to route light from a light source of the mobile device through the optical device of the attachment body 304, and to otherwise generally occlude the light source to prevent unwanted illumination of external objects.
In order to use the aimer accessory 300 with a mobile device having a camera and a light source, the aimer accessory 300 can be secured in place relative to the mobile device with the camera opening 306 aligned with the camera, and with the light-source opening 316 aligned with the light source. In some embodiments, this alignment can be obtained through the use of a case configured to engage the attachment base 302.
As illustrated in
As illustrated in
Further, in the embodiment illustrated, the indent 308 in the camera opening 306 is aligned with a microphone 410 (or other similarly located feature) on the mobile device 406, so that the microphone (or other feature) can still be used (e.g., for noise-cancellation purposes) even with the attachment base 302 in place. Also in the embodiment illustrated, the light-source opening 316 is generally aligned with a light source 412 of the mobile device 406, but with the blocking feature formed by the wall 316a of the light-source opening 316 partially occluding the light source 412 (e.g., a yellow-colored portion thereof). Accordingly, when the attachment body 304 is secured to the attachment base 302, some but not all of the light from the light source 412 can pass into the shell 342 for manipulation by the optical device therein (e.g., the assembly of the lens 348 and the mirrors 344 and 346).
As illustrated in
In other embodiments, other configurations are possible, including variations on the features discussed above. For example, in some embodiments, one or more attachment arms can be provided on an attachment base rather than on an attachment body, and one or more corresponding attachment openings can be provided on the attachment body rather than on the attachment base. Similarly, for example, one or more features similar to the detents 372 and 374 can be provided on an attachment base rather than on an attachment body, and one or more corresponding indents can be provided on the attachment body rather than on the attachment base. In some embodiments, an attachment base can be configured to entirely occlude a light source of a mobile device.
In other embodiments, an attachment base can also (or alternatively) be configured to attach in different ways to a case (or mobile device). For example, an attachment base can be configured to attach to the exterior of a case rather than through engagement with an internal shoulder of the case.
An attachment body 430 for another aimer accessory is illustrated in
In the embodiment illustrated, the attachment body 430 includes a housing portion generally formed as a single-piece shell 432 that is configured to enclose and support part or all of one or more optical devices. For example, the shell 432 can be configured to enclose and support a mirror assembly or a light pipe for use with a light source on a relevant mobile device.
Also in the embodiment illustrated, the shell 432 is configured to enclose an optical device configured as a mirror assembly with various mirrors (not shown) and a lens (not shown). Accordingly, the shell 432 includes internal support surfaces 434 and 436 to support various mirrors (not shown), as well as a lens opening 438 configured to receive a lens (not shown). The lens and mirrors (not shown) can be secured within the shell 432 in various ways, including through the use of adhesives, press-fit engagement, and so on.
Generally, the shell 432 can be configured for relatively low-profile attachment to a mobile device or case, and can include various features to facilitate use of the attachment body 304 with a camera of a mobile device. For example, a wall 432a of the shell 432 that is to be disposed generally adjacent to a field of view of a camera can be configured with an angled geometry so that interference with camera operation by the shell 432 can be minimized. The angled geometry of the wall 432a can also, for example, help to appropriately support one or more components of an optical device, such as a mirror, within the shell 432.
The attachment body 430 can also generally include features for removably securing the attachment body 430 to an attachment base (e.g., an attachment base as discussed below). For example, the shell 432 can include a pair of support legs 440 extending downwardly from a main body 442 of the shell 432, with a set of internal grooves 444 and 446. In the embodiment illustrated, the grooves 444 and 446 extend partly along the length of the support legs 440 from an area below an overhang 448 at one end of the support legs 440 to tapered ends 444a and 446a of the respective grooves 444 and 446.
The attachment body 430 can also include various other features. In the embodiment illustrated, for example, the shell 432 includes a rounded opening 452 at a bottom end of the wall 432a, and an inwardly curving channel 454 extending along part of the wall 432a to the opening 452. The shell 432 also includes an internal recess 450 extending into the interior of the shell 432 from within the overhang 448.
An attachment base 460 for use with the attachment body 430 is illustrated in
The attachment base 460 can also generally include structures to assist in removably securing the attachment body 430 to the attachment base 460. In the embodiment illustrated, for example, the attachment base 460 includes a set of attachment rails 470 and 472, a pair of grip arms 474 and 476, and a cantilevered locking tab 478. The attachment rails 470 and 472 generally extend along part of the length of the attachment base 460 between respective end walls of the grip arms 474 and 476 and respective tapered ends 470a and 472a of the attachment rails 470 and 472. The grip arms 474 and 476 are configured to be generally rigid and include respective sets of raised grip features 488, which can assist a user in manually positioning or otherwise holding the attachment base 460. The locking tab 478 extends generally between the grip arms 474 and 476 and is configured to be elastically deformable relative to the remainder of the attachment base 460 (e.g., relative to the grip arms 474 and 476) when the locking tab 478 is manually subjected to force at or near a free end 478a. An upper surface of the locking tab 478 includes a detent 480, with a flattened locking wall 480a and a sloped and rounded entrance wall 480b.
As illustrated in
Referring in particular to
As the attachment rails 470 and 472 are moved farther into the grooves 444 and 446, the detent 480 on the locking tab 478 can come into contact with a rear wall 432b of the shell 432. With continued movement of the attachment body 430 in the direction of the arrow 484, the angled profile of the entrance wall 480b of the detent and the movement of the attachment body 430 relative to the attachment base 460 can then deflect the locking tab 478 downward (e.g., as indicated by arrow 486). With further relative movement of the attachment body 430 and the attachment base 460, the detent 480 can clear the wall 432b, such that the locking tab 478 is released from the noted deflection and the detent 480 can move into the recess 450 in the shell 432. The locking wall 480a of the lock can then seat against an interior surface of the wall 432b to generally prevent disconnection of the attachment body 430 from the attachment base 460 by movement of the attachment body 430 opposite the direction of arrow 484.
In some embodiments, the attachment rails 470 and 472 and the grooves 444 and 446 can be dimensioned so that the detent 480 clears the wall 432b substantially simultaneously with the tapered ends 470a and 472a of the attachment rails 470 and 472 reaching the tapered ends 444a and 446a of the grooves 444 and 446. Accordingly, the detent 480, the wall 432b, the grooves 444 and 446, and the attachment rails 470 and 472 can collectively and snugly secure the attachment body 430 to the attachment base 460.
To remove the attachment body 430 from the attachment base 460, the locking tab 478 can be deformed downward (e.g., with manual force applied at the free end 478a) until the detent 480 clears the wall 432b. The attachment rails 470 and 472 can then be slid free of the grooves 444 and 446 and the attachment body 430 generally separated from the attachment base 460.
As also illustrated in
As also noted above, different arrangements are possible for an optical device included in an aimer accessory according to this disclosure. In some embodiments, an optical device can include one or more mirrors (or other features, such as other reflecting surfaces, for changing the path of light rays) as well as a mask (or other feature) to help create a particular pattern of light on a relevant target. As illustrated in
In the embodiment illustrated in
In the embodiments illustrated in
In some embodiments, other configurations of mirrors (or other reflecting surfaces) can be used. As illustrated in
In some embodiments, an optical device can use features or components other than mirrors to direct light. As illustrated in
In other embodiments, other configurations are possible. As illustrated in
In some embodiments, an attachment for a mobile device can include electronic components, such as light sources, processor assemblies (e.g., flexible printed circuit board “PCB” assemblies), sensors, and so on. For example, an optical attachment can include a power source, a controller such as a PCB assembly with one or more processors, and an LED (or LEDs) that is powered via the power source and controlled by the controller. With the assistance of appropriate optical devices of the attachment (e.g., lens assemblies, mirrors, and so on), the LED can provide light to project an illuminated targeting (or other) pattern onto a target for image acquisition. Accordingly, lighting of a target with the optical attachment (e.g., for image targeting) can be freed from any limitations imposed by a light source on a particular mobile device (e.g., limitations regarding pattern color or brightness). Further, with a self-contained power source such as a battery, the optical attachment can operate at a relatively high power level without draining the battery of the mobile device.
In one embodiment, an attachment can include an attachment body that is removably securable to a mobile device. The attachment body can generally provide a relatively light-proof cover for a camera of the mobile device, aside from one or more imaging openings in the attachment body, through which the camera can image external targets. Further, the attachment body can house a battery pack and a relatively high-power LED that can be operated by an onboard (or remote) processor. An optical device (e.g., a lens arrangement) included in the attachment body can be configured to project light from the LED towards external targets, as can be useful, for example, for targeting operations. In some cases, the optical device can include a dichroic mirror assembly, which can allow the LED light to be projected onto the target along the optical axis of the camera without requiring the LED to be disposed along the optical axis of the camera. For example, in some embodiments, a dichroic mirror can be disposed in optical alignment with the camera and with the LED, between two imaging openings in the attachment body. Light for imaging can accordingly pass from external targets through the imaging openings and the mirror to reach the camera, while light from the LED can be reflected from the mirror onto the external targets for illumination and targeting.
In some embodiments, an attachment can be configured to optically (or otherwise) communicate with a mobile device when secured to the mobile device for operation. This can be useful, for example, where the operation of a light source included in an attachment needs to be coordinated with one or more operations on an associated mobile device (e.g., image acquisitions). For example, an attachment can include a light detector (i.e., a photon detector of various kinds) that can be disposed in optical alignment with a light source on a mobile device when the attachment is secured to the mobile device. With this arrangement, data can be transmitted from the mobile device to the attachment by projecting light from the mobile-device light source onto the light detector of the attachment. The attachment can then interpret signals from light detector to extract the data (e.g., via firmware applications, hardware, and so on). As such, for example, software operating on the mobile device can control operation of an attachment light source (or other attachment component) in order to project targeting patterns for image acquisition (or provide other functionality). Further, in some implementations, software operating on the mobile device can optically transmit firmware (and other) updates to an attachment so that operation of the attachment can be easily improved when appropriate.
Similarly, in some embodiments, data can be optically (or otherwise) transmitted from an attachment to a mobile device. For example, an attachment can include a light source that can be placed into optical alignment with a camera of a mobile device, when the attachment is secured to the mobile device. With this configuration, light from the attachment light source can be projected onto the camera in order to transmit data from the attachment to the mobile device (e.g., via interpretation of the optical signals via software on the mobile device). As such, for example, the attachment can optically communicate identification information, firmware information, and other data to the mobile device.
In some implementations, an attachment can communicate certain information upon being secured to, or paired with, a mobile device. For example, an attachment can be configured to communicate a part number, a serial number, and a firmware version upon first receiving a pairing or control signal from a mobile device, or upon being physically connected to the mobile device. This can trigger further communication, as appropriate, to complete a connection or pairing of the attachment and the mobile device, and can thereby enable control of an attachment light source by the mobile device.
In some implementations, other data can also be communicated. For example, a battery monitor on an attachment can monitor an attachment battery (or other power source), so that an attached mobile device can be provided with status information for the battery (or other power source). For example, a battery monitor can monitor power status of an on-board battery, then use optical communication to alert a user, via the mobile device, when the battery is in need of replacement or recharging.
In some embodiments, an attachment light source for optical communication with a mobile device can also be used to project patterns for image targeting. For example, the light source can be controlled to communicate data via modulation (e.g., controlled ON-OFF flickering) of a targeting pattern projected onto an external target. By imaging the external target, a camera of the mobile device can accordingly record the optical data transmission. In contrast, in some arrangements, an attachment light source can be disposed to directly project light onto the camera (i.e., project light onto the camera without the light being first projected onto an external imaging target). For example, an attachment can include a dedicated (or shared) communication opening that is optically aligned with the attachment light source and with the camera, so that light from the LED can be projected onto the camera via the opening rather than (or in addition to) being projected onto an external target.
In some embodiments, an attachment can include a dedicated light source for optical communication as well as one or more additional light sources. For example, an attachment body can include a first LED for projecting patterns for image targeting, and a second LED for transmitting information directly to a camera of an attached mobile device.
Although beneficial results can be obtained with non-optical communication, optical communication of data between an attachment and a mobile device can have particular advantages. For example, in some embodiments, optical signaling by an attachment can be implemented using components that are also useful for other purposes (e.g., light sources for projecting targeting patterns onto external targets). Accordingly, communication between an attachment and an associated mobile device can be obtained without adding expensive and/or sizable electronic components such as Bluetooth equipment, radio antennas, and so on. Similarly, in some embodiments, optical signaling can be implemented without necessarily requiring a user to secure and maintain of external data connections. For example, communication architectures relying on head-phone or other data-port connections can require plugs or cords that extend well outside of an attachment, and are thus potentially subject to accidental disconnect or damage, as well as other issues.
An example aimer accessory 700, which includes some of the features and capabilities discussed above, is illustrated in
In some embodiments, the aimer accessory 700 can be removably secured to the case 702 (e.g., for targeting and image acquisition operations) using an attachment base configured to removably engage the attachment body 704. An example attachment base 716, formed as a single integral body, is illustrated in
The attachment base 716 is generally configured to engage with the case 702 at an imaging opening in the case 702 (not shown in
In some embodiments, when the attachment base 716 is installed in the case 702 with a mobile device, the underside of an attachment base can rest against parts of the mobile device. Accordingly, in some embodiments, the attachment base 716 can be contoured to match the geometry of a particular mobile device type. For example, the underside of the anchor portion 716a (see
The attachment base 716 also includes a generally plate-like tongue 724, attached to and extending away from one end of the anchor portion 716a. The tongue 724 attaches to the anchor portion 716a at a pair of raised shoulders 726 and extends from the shoulders 726 to a rounded end 728. The tongue 724 is generally resiliently deformable, with a central, partially spherical recess 730 at the rounded end 728. An exterior shoulder 732 extends around the outer perimeter of the tongue 724, facing generally oppositely from the shoulder 720 to form a pair of parallel attachment rails between the shoulders 726 and the rounded end 728.
As illustrated in
Generally, the use of a separate attachment base (e.g., the attachment base 716) can allow for relatively easy addition or removal of an aimer accessory for a particular mobile device. This can be particularly useful, for example, in self-powered versions of aimer accessories, for which it may be useful to rapidly swap a fully-charged accessory for an accessory with a depleted internal power source. Similarly, the use of a separate attachment base can also allow for a relatively modular range of different aimer accessories. For example, multiple attachment bodies, each with different optical arrangements (or other components), can be configured to universally attach to a particular attachment base, thereby allowing one of several attachment bodies to be selected for a particular task with a particular mobile device.
Also illustrated in
To support and secure different components of the aimer accessory 700 (e.g., one or more optical devices) relative to the base plate 750, the top side of the base plate 750 includes a number of support and engagement features. As illustrated in particular in
Other portions of a base plate for an attachment body can also include useful features. For example, each of the lateral sides of the base plate 750 includes a set of wedged protrusions 786 that can help to secure the shell 706 (see, e.g.,
As also discussed above, it may be useful to capture images through optical openings in an aimer accessory, as well as to exchange optical communication signals with an attached mobile device. To this end, for example, the base plate 750 includes a pair of optical openings 782, 784. In the example configuration discussed below, the opening 782 is configured as an imaging opening and the opening 784 is configured as a communication opening for transmission of optical communications. Communication and imaging via the openings 782, 784 is also discussed below.
In other embodiments, other configurations are possible. In some embodiments, a base plate can include a different number or arrangement of optical openings. For example, a base plate for use with the aimer accessory 700 can include multiple optical openings for transmission of optical communication (i.e., multiple communication openings), or can include only a single optical opening for both communication transmissions and imaging.
In some embodiments, a bottom portion of a base plate can be configured to engage with any variety of attachment bases, or to match the geometry of any variety of mobile-device cases. In some embodiments, alternative (or additional) locking devices can be used. For example, the boss 762 of the base plate 750 can be instead configured as a recess sized to engage a corresponding protrusion on an associated attachment base.
As illustrated in
As illustrated in particular in
As also illustrated in
Further, with the base plate 750 secured to the attachment base 716, the imaging opening 782 and the communication opening 784 of the base plate 750 are disposed generally within the optical opening 718 of the attachment base 716. Accordingly, for example, light source 740 of the mobile device 742 (see, e.g.,
As illustrated in particular in
An example set of components for the aimer accessory 700 is illustrated in
As illustrated in
Because of the optical properties of the dichroic mirror 810, light from the target that reflects back to the aimer accessory 700 and passes through the optical opening 708 can be received by the camera 738 for imaging via the dichroic mirror 810, the optical opening 734, and the imaging opening 782. This is illustrated in
As also illustrated in
In some embodiments, an optical arrangement for an aimer accessory can include other types of reflectors or filters in place of (or in addition to) a dichroic mirror such as the dichroic mirror 810. Likewise, in some embodiments, the part 812a of the PCB assembly 812 (or another feature) can support a light source distinct from the LED 828 for direct communication with the mobile device 742 via the communication opening 784 and the camera 738. In some embodiments, as also noted above, optical devices (or general structural arrangements) can be included to direct light from the LED 828 through the communication opening 784 for direct communication with the mobile device 742.
In some embodiments, one or more filters or masks (not shown) can be included. For example, filters or masks can be included to allow the LED 828 to provide an aiming pattern generally similar to those discussed above, or various other aiming patterns.
In some embodiments, other power sources can be provided. For example, a larger battery compartment and battery pack can be included, or an aimer accessory can draw power from an external (e.g., separate but attached) battery pack.
In some embodiments, the configuration of the optics block 816 and the relative arrangement of the optics block 816 and the LED 828 (or other light source) can be used to obtain a particular type of illumination pattern with the LED 828. As illustrated in
An example control architecture for the PCB assembly 812 is illustrated in
In other embodiments, other configurations are possible. For example, an additional LED and an additional LED controller (not shown) can be disposed in communication with the microcontroller 860, or with another processing device. This can be useful, for example, in order to provide a dedicated light source for optical communication with an associated mobile device. Likewise, in some embodiments, other electronic devices can additionally (or alternatively) be included.
Another example aimer accessory 880 is illustrated in
Similarly to the aimer accessory 700, the aimer accessory 880 includes an attachment body 882 with an optical opening 882a, and an attachment base 884 (see, e.g.,
The attachment body 882 includes a base plate 898 configured to engage a shell 906, to generally support optical devices and other components, and to slidingly engage the attachment base 884 to secure the attachment body 882 to the mobile-device case 892. Similarly to the base plate 750, the base plate 898 includes a locking finger 900 with a boss 902 configured to engage a corresponding recess 904 on the tongue 896 of the attachment base 884. The base plate 898 also includes a pair of curved guides 908 disposed to engage the interior sides of an optical opening 910 in the attachment base 884.
The base plate 898 further includes an imaging opening 912 and a communication opening 914, which are optically aligned with the optical openings 890, 910, when the base plate 898 is installed for use (see, e.g.,
Support structures on the top of the base plate 898, as well as the optical devices housed by the shell 906, also vary from those of the base plate 750 and the shell 706. For example, as illustrated in
With the chassis 924 installed on the base plate 898 and the base plate 898 secured to the attachment base 884, the dichroic mirror 926 is optically aligned with the imaging opening 912 on the base plate 898. Accordingly, the aimer accessory 880 can be used similarly to the aimer accessory 700, in order to project an aimer pattern onto an external target (not shown), while also providing an optical path for a camera 934 of the mobile device 894 to image the target. Further, with the aimer accessory 880 appropriately installed, the communication opening 914 and the communications block 932 are optically aligned with the optical opening 910 on the attachment base 884. Accordingly, via the communications block 932, the camera 934 and a mobile-device light source 936, the aimer accessory 880 can directly optically communicate with the mobile device 894.
In other embodiments, other configurations are possible. In some embodiments, for example, the communications block 932 can be a structural block or other member, rather than part of a PCB assembly. As such, for example, with the various components of the aimer accessory 880 arranged as illustrated in
In some embodiments, masks, filters, or other similar devices can be included. In the embodiment illustrated, for example, a pinhole mask 938 is disposed between the light-source recess 930 and a lens 940, in order to provide for projection of an appropriate pattern of light from the LED (not shown) onto an external target.
In the embodiment of
Optical communication between an aimer accessory and a mobile device can be effected in various ways. Generally, for example, it may be useful to transmit data via binary signaling, with modulation of mobile-device and attachment light sources providing bit information, and with one or more controllers implementing appropriate packet architecture, forward error correction, signal decoding, and so on.
In some embodiments, a mobile device can be configured to capture video, or a series of still-frame images, then analyze the resulting image data to identify optical signals. For example, a camera of a mobile device can capture video of a target on which a projected targeting pattern is being modulated, and can then analyze the video to identify a binary-encoded signal from the modulation. In some implementations, the video (or a similar series of still images) can be converted to grayscale and then adjusted to a relatively high level of contrast. The resulting high contrast images can then be compared to a reference image (e.g., a previously-acquired reference image of an illuminated, or non-illuminated, target) to determine the nature of the imaged data (e.g., an illuminated “1”, or a non-illuminated “0”). As appropriate, once a certain amount of information has been thus received and/or decoded, a check (e.g., cyclic redundancy check (“CDC”) error detecting) can be executed to determine whether the information represents a valid communication signal.
In some embodiments, a light source of a mobile device can be used to establish a timing for optical transmission of data from an aimer accessory to the mobile device. For example, the light source of the mobile device can be cycled on and off rapidly, with a predetermined (e.g., hardware-limited minimum) interval between successive “on” states. Over the interval between the “on” states, the mobile device can capture images of a relevant illumination target (e.g., an imaging target being illuminated by a light source of the aimer accessory). Depending on whether an image that is captured during the interval indicates an “on” state for the light source of the aimer accessory, the mobile device can then register a bit of one type (e.g., a “1”) or another (e.g., a “0”). In this way, for example, with appropriate message validation and error correction, relatively reliable optical communication from the aimer accessory to the mobile device can be obtained. The approach noted above, and others like it, may be useful, for example, in embodiments in which the mobile device and the aimer accessory lack a common clock or other timing synchronization.
In some embodiments, a somewhat reversed implementation may alternatively (or additionally) be possible. For example, an aimer accessory can be configured to transmit an “intro” or “prefix” message, a timing message, or other optical message to a mobile device in order to initiate and/or regulate timing for a transmission of optical data from the aimer accessory to the mobile device.
In some implementations, a mobile device can be configured to communicate with an aimer accessory in a relatively direct fashion. For example, when the aimer accessory is set to receive data (e.g., as a default configuration of the aimer accessory) the light source of the mobile device can be modulated (e.g., switched controllably on and off) in order to selectively trigger a light detector of the aimer accessory. An associated controller can receive the trigger signals from the light detector, and can then decode, verify, and act on the signals as appropriate (e.g., to command illumination of a targeting pattern in response to a request from the mobile device).
As also noted above, optical communication between a mobile device and an aimer accessory can be useful in implementing a variety of functions. For example, a mobile device can optically communicate with an aimer accessory to trigger illumination of a target with a targeting pattern. In some implementations, the mobile device can further provide, or otherwise cause an aimer accessory to select and implement, one or more parameters for the illumination, such as light color, timing, intensity, duration, pattern, modulation type (e.g., steady illumination or flashing illumination) and so on. As another example, a mobile device can communicate firmware updates or other useful information to an aimer accessory (e.g., identification information for the mobile device), so that the aimer accessory can be operated with appropriate efficiency and functionality.
In some implementations, an aimer accessory can optically communicate with a mobile device in order to provide information regarding the aimer accessory. For example, when first attached to or paired with a mobile device, or at other times, an aimer accessory can optically communicate identifying information, such as part and serial numbers, and firmware version. Software on the mobile device can then respond appropriately, including by registering the aimer accessory (e.g. locally with the mobile device, or remotely with a registration server), enabling or disabling particular options for controlling the aimer accessory, automatically opening menus or other interfaces, automatically providing a firmware update or reminder to update firmware, and so on. Similarly, an aimer accessory can communicate other information, including alerts with regard to battery life or other factors pertinent to accessory performance.
Battery monitoring to inform alerts relating to battery life can be implemented in various ways. In some implementations, for example, the aimer accessory (or a mobile device) can track how often an LED of the aimer accessory is on. Because operation of an LED can represent a significant portion of power expenditure, total operation time for an LED can serve as (or help to determine) a relatively accurate indicator of battery life for an aimer accessory. In some implementations, a battery monitor can simply detect brown-outs or delays at a relevant controller and can infer a particular battery state from a particular frequency or severity of these events. In some implementations, rather than (or in addition to) communicating battery information to a mobile device, an aimer accessory can include an external battery-life indicator (e.g., an external LED). In some implementations, information relating to battery life can be stored in memory within an aimer accessory, so that appropriately accurate battery-life information can be determined despite changes between different mobile devices or relatively long delays between uses of the aimer accessory.
Consistent with the discussion above, some embodiments of the invention can include a communication and control method 950 as illustrated in
Generally, under the method 950, first optical signals can be received 952 at a light detector of an attachment for a mobile device. In some implementations, the first optical signals can be transmitted 954 to the attachment by a light source of the mobile device. The transmitted 954 first optical signals can include various information, including instructions for initialization or operation of the attachment. In some implementations, for example, based on receiving the first optical signals, a processing device can activate 956a at least one light source of the attachment for use in image acquisition or targeting (e.g., projection of an illuminated target pattern). In some implementations, based on receiving the first optical signals, a processing device can undertake other operations. For example, the processing device can select and implement 956b particular operational (e.g., illumination) parameters for the attachment, configure the attachment for communication with the particular mobile device, and so on.
Also under the method 950, the processing device can activate 958 the at least one light source of the attachment in order to provide second optical signals to the imaging device. In this way, for example, non-image information 960 such as identification information for the attachment, firmware information for the attachment, power-source status for the attachment, information regarding illumination or other parameters for the attachment, and so on, can be transmitted from the attachment to the mobile device.
In some implementations, the attachment can include at least two light sources. Accordingly, for example, a first light source can be activated 956a for use in image acquisition or targeting, and a second light source can be activated 958 to transmit non-image information 960 to the mobile device. In this regard, for example, activation 958 of a light source for transmission of optical signals to the mobile device can occur independently of, or in coordination with, activation 956a of a light source for image acquisition or targeting or various other operations.
In some implementations, the non-image information 960 can be transmitted to the mobile device by activating 958 an attachment light source to illuminate 962 an external target, then acquiring 964 images of the target with the imaging device of the mobile device. In this way, although the imaging device may acquire one or more images of the target as part of the communication of the non-image information 960, upon decoding the captured images can provide the non-image information 960 in non-image form. For example, the illumination 962 can be modulated on and off in order to encode binary data for transmission to the imaging device in order to transmit identification information, firmware information, power-source (e.g., battery) status, and so on.
In some implementations, communication of the non-image information 960 via the illumination 962 of an external target can proceed without requiring a detailed image of the external target (e.g., an image in which features of the external target can be visually distinguished). Likewise, the external target for the illumination 962 may not necessarily be a target with a symbol or other specific aspect that is intended to be imaged for further analysis. Further, the external target for the illumination 962 may not necessarily be an external target that is remotely disposed relative to the relevant attachment and imaging devices.
Similarly, in some embodiments, a mobile device can be configured to receive the non-image information 960 based on a general determination of luminosity (e.g., rather than based on acquisition of a detailed image). In this regard, for example, a relevant light source can be activated (or deactivated) in accordance with an encoding of non-image information. Based on sensing by an imaging device, a processor (e.g., of a related mobile device) can then determine whether the overall sensed luminosity exceeds a threshold (e.g., indicates a binary “1”) or does not exceed a threshold (e.g., indicates a binary “0”), without necessarily needing to acquire an image suitable for other detailed analysis.
Correspondingly, for example, rather than be pointed at a remote target to be imaged, the relevant mobile device and attachment can be placed on a surface, such as a table-top, with an imaging window of the attachment close to or flush with the surface (e.g., with the mobile device “face down,” from the perspective of the imaging device). With the mobile device and the attachment thus disposed, communication of non-image information 960 by a light source of the attachment can be commenced. The imaging device can then determine (e.g., based on a luminosity threshold) whether the relevant light source is on or off, even if the imaging device cannot acquire an otherwise useful image of the surface on which the mobile device and attachment are resting (e.g., an image that could be analyzed to decode a barcode or other symbol).
In other embodiments, other configurations are possible. For example,
An exterior shell 992 of the cover 980 includes a generally square shoulder 994 that extends at an oblique angle between top and bottom ends of the shell 992. A generally squared attachment portion 996 extends away from the shoulder 994 and supports a latching feature 998. As illustrated in
As illustrated in
At the top end of the shell 992, a curved attachment tab 1006 extends upward and rearward. A tooth-like protrusion 1008 extends generally downward near the free end of the tab 1006. As also discussed below, the tab 1006 can help to secure the shell 992 to a mobile device (e.g., via attachment to a mobile-device case). In other embodiments, the tab 1006 can be configured differently, in order to help secure the shell 992 to a variety of different structures.
Other features can also be included. For example, as illustrated in
As illustrated in
In different embodiments, different types and configurations of optical and other devices, such as circuit assemblies, can be configured to be contained and supported by the attachment body 1040. In some embodiments, a flexible or partly flexible (e.g., semi-rigid) circuit assembly can be configured for inclusion in the attachment body 1040. For example, a circuit assembly 1050, illustrated in
Various configurations for the circuit assembly 1050 are possible, depending on the spatial and functional needs of a final assembly. In the embodiment illustrated, for example, the LEDs 1052 and the power connectors 1054 are supported on a main PCB 1058, and an optical sensor 1060 (see
As illustrated in
As illustrated in 71A through 72, the PCB 1058 includes a number of openings (not numbered). In some embodiments, these openings can be aligned with features on the base 1020 (see, e.g.,
Certain features of the PCBs 1058, 1062, and 1064 are not discussed in detail herein. One of skill in the art, however, will recognize the inherent inclusion of various features. For example, it will be understood that one or more of the PCBs 1058, 1062, and 1064 can include one or more processor devices, in order to execute appropriate computer logic (e.g., for illumination control). Further, in some embodiments, communication devices can be included, such as USB, near-field communication, Bluetooth®, or other wired or wireless communication devices. (Bluetooth is a registered trademark of the Bluetooth Special Interest Group in the United States and/or other jurisdictions.)
As illustrated in
With the chassis 1080 fully assembled, as illustrated in
As illustrated in
As illustrated in
Usefully, as also discussed below, the chassis 1080 can be used with a variety of different attachments, including the attachment body 1040 and others. In particular, the chassis 1080 can reliably secure optical devices in appropriate alignment with each other and with the chassis 1080 itself, so that the optical devices can be reliably used for image capture and other operations, with a variety of different types of attachments.
A variety of configurations are possible for the optical and other devices supported by the attachment body 1040. In some embodiments, the LED 1056 can be a green LED configured for use to provide aiming patterns on a target surface. As illustrated in
With the aperture block 1084, a concentrator or other lens (not shown), and the beam splitter 1082 also secured in place by the chassis 1080, the LED 1056 is accordingly positioned to controllably project light out of the window 986. With the use of appropriate masks (as desired), or other devices, one or more patterns (e.g., as also discussed above) can accordingly be projected onto a target surface in order to assist a user in aligning a mobile device to capture images. In some embodiments, as also discussed above and below, the LED 1056 can be controlled to similarly project light onto a target surface in order to communicate commands or other information to a mobile device via imaging of the light by the mobile device. For example, as illustrated in
In other embodiments, other devices can also (or alternatively) be disposed along the optical path of light traveling from the LED 1056 out of the attachment body 1040. For example, a diffusion cap or other diffuser can be disposed at the LED 1056 or between the LED 1056 and the exterior of the attachment body 1040, in order to appropriately diffuse light from the LED 1056.
In some embodiments, the LEDs 1052 can be configured as white LEDs. In some embodiments, the LEDs 1052 can be configured to be separately controlled. As noted above, the LEDs 1052 are generally aligned with the window 984 of the cover 980. Accordingly, with appropriate configuration, the LEDs 1052 can be used to provide illumination for imaging, or various other functionality. In some embodiments, for example, the LEDs 1052 can be configure to provide sufficient illumination that a mobile device can still image a target with high reliability, via the window 986, despite the loss of some light due to the imposition of the beam splitter 1082 between the window 986 and a relevant imaging device (e.g., a camera of a mobile device).
In other embodiments, the LEDs 1052 (or other LEDs) can be differently configured. In some embodiments, one or more non-white LEDs can be employed, in order to provide appropriate lighting in a variety of environments. For example, red or amber lighting can be provided for highly reflective environments, infrared or other lighting can be provided to illuminate specialized barcodes (e.g., barcodes that are rendered visible only when illuminated with non-visible light), and so on.
As noted above, in the embodiment illustrated in
It will be noted that a beam splitter may still generally reduce the incidence of light on an image sensor disposed behind the beam splitter (e.g., as part of a camera of a mobile device for use with the attachment body 1040). Accordingly, in some embodiments, it may be useful to pair a beam splitter with appropriately powerful light sources (e.g., the LEDs 1052), so that appropriately detailed images can be acquired. For example, the combination of the LEDs 1052 and the beam splitter 1082 can allow for relatively detailed images to be acquired through the window 986 (and the attachment body 1040 generally), whether for capturing and decoding bar codes or for other detailed imaging.
As another example, in some cases, covers of various configurations can be provided at one or more windows in an attachment body. As illustrated in
In some cases, the covers 1110 and 1112 (and others) can be securely fixed to the shell 992 or other components (e.g., via ultrasonic welding), so as to provide appropriate leak sealing (e.g., to satisfy Ingress Protection 54 rating for sealed enclosures or other relevant ratings requirements). In some cases, different instances of the covers 1110 and 1112 (and others) that exhibit different properties (e.g., different lens types, different opacities, and so on) can be configured to be interchangeable (e.g., during manufacturing) so that customized properties can be provided without necessarily varying other aspects of an attachment's design.
In view of the example components discussed above, such as the relatively highly-powered LEDs 1052, it may be useful to provide a power source for the attachment body 1040 that is separate (at least in part) from an integrated power source of an associated mobile device. In some embodiments, as discussed above with regard to the aimer accessory 700, an internal power source (e.g., a set of internal batteries) can be provided to this end. In some embodiments, a separate battery pack can be used.
Each of the battery packs 1120 and 1122 can be configured to secure the attachment body 1040, as illustrated in the various FIGS., to the respective battery packs 1120 and 1122. In this regard, for example, the top corners of each of the battery packs 1120 and 1122 include substantially identical cut-outs 1124 and 1126, with angled end walls 1124a and 1126a that are generally complementary to the angled shoulder 994 on the shell 992 of the cover 980 of the attachment body 1040. Likewise, recesses 1128 and 1130 extend into the bodies of the battery packs 1120 and 1122 adjacent to the end walls 1124a and 1126a, with a latching mechanism (not shown) to engage the hook structure 1000 of the latching feature 998 of the cover 980 (see, e.g.,
In order to further assist in securing the attachment body 1040, each of the battery packs 1120 and 1122 also includes an attachment rail 1136 and 1138 (see, e.g.,
Other features can also be included. For example, in the embodiment illustrated, status lights 1140 and 1142 are provide, as are additional attachment rails 1144 and 1146 to secure further accessories to the battery packs 1120 and 1122. In some embodiments, the battery packs 1120 and 1122 can be configured to provide electrical power to an associated mobile device, as well as to the attachment body 1040.
A method of attaching the attachment body 1040 to the battery packs 1120 and 1122 is illustrated in
As with other embodiments discussed above, it should be noted that the described rail and groove arrangement for the attachment body 1040 and the battery packs 1120 and 1122 can be reversed, as desired. For example, an attachment rail similar to the rails 1136 and 1138 can be provided on the attachment body 1040, with an attachment groove similar to the groove 1004 provided on the battery packs 1120 and 1122.
With the attachment body 1040 moved fully into either of the cut-outs 1124 and 1126, as illustrated in
With the attachment body 1040 secured to the battery pack 1120 or 1122, and the battery pack 1120 or 1122 secured to the case 1150 or 1152, other beneficial structural arrangements may also result. For example, as illustrated in
In some embodiments, the rounded protrusion 1026 can snap into the relevant camera opening 1154 or 1156, in order to provide useful tactile and auditory feedback to users. In some embodiments, the rounded protrusion 1026 may not entirely fill the relevant camera opening. For example, as illustrated in
Generally, as well as providing for secure attachment of the attachment body 1040 to a mobile device, the example arrangement described above (and other similar arrangements) can provide significant flexibility with regard to the particular mobile device with which the attachment body 1040 is to be used. For example, as illustrated in
In other embodiments, other configurations are possible. For example, as illustrated in
Usefully, in some embodiments, some internal aspects of the attachment body 1194 can be similar to some internal aspects of the attachment body 1040 (see, e.g.,
In some cases, operation of the attachment bodies 1040 and 1194 can be controlled as discussed above (e.g., as outlined in
In some implementations, light sources for targeting (e.g., the LED 1056) also can be turned on or off 1210, can be activated with different intensities 1212, can be flickered 1214, and so on. In some implementations, operation of an aiming light source (e.g., the LED 1056) can be modulated 1216 to facilitate image acquisition (e.g., via frame capture from a video stream of an imaging device of a relevant mobile device, as controlled by an application on the mobile device). For example, where light from the aiming light source is sufficiently bright so as to potentially interfere with image acquisition, the aiming light source can be turned on and off 1218 relatively rapidly (e.g., every 10 ms). This can provide the aiming pattern with a flickering appearance, which may help a user to more easily identify the aiming pattern and align the aiming pattern over a target. Further, an application on the relevant mobile device can be configured to cause image acquisition (e.g., via video frame capture) when the aiming light source is momentarily off, so that the image (e.g., of a barcode to be decoded) may not be overly obscured by the aiming pattern.
In some implementations, light sources for targeting (e.g., the LED 1056) can be modulated 1216 in conjunction with light sources for image acquisition (e.g., the LEDs 1052) to facilitate image capture. For example, the LED 1056 can be turned off to cease targeting (at least temporarily) as one or both of the LEDs 1052 are turned on to illuminate a target for image capture.
In some implementations, it may be possible to control an attachment body, including the attachment body 1040, to provide a variety of aiming patterns. For example, a mechanism for electronically implemented masking or filtering can be controlled, in order to provide an appropriate illumination pattern for an appropriate application or context.
In some implementations, the optical sensor 1060 can be configured mainly to receive communication from a mobile device (e.g., via a flash or other light source of the mobile device), in order for the mobile device to control operation of the attachment body 1040. Correspondingly, for example, the attachment body 1040 can communicate to the mobile device via modulated illumination of one or more of the LEDs 1052 or 1056, which can be received by the mobile device via acquisition of images of an illuminated target area by a camera of the mobile device. For example, as similarly described above, the attachment body 1040 can be placed “face down” on a surface, with the windows 984 and 986 flush with (or otherwise close to) the surface. The illumination LEDs 1052 can then be activated in order to transmit non-image information, which can be received and interpreted at the relevant mobile device based on luminosity analysis of signals from the relevant imaging device.
In other embodiments, other configurations and approaches may be possible. For example, an optical device (e.g., a mirror, light pipe, or beam splitter) can be configured to route optical signals directly from one of the LEDs 1052 or 1056 (or another light source of an attachment body) to a camera of a mobile device, in order to directly communicate with the mobile device.
Another example of internal components for an attachment according to this disclosure is partially illustrated in
In some aspects, however, the components illustrated in
As another example, additional features can be provided to help secure the lens 1238 to the aperture block 1234, and to help secure the lens 1238 and the aperture bock 1234, collectively, to the chassis 1232. For example, as illustrated in particular in
It will be understood that many variations on the embodiments discussed above may be possible, including variations combining elements of multiple of the embodiments together, variations substituting elements from one embodiment for elements of another embodiment, and variations rearranging elements of one or more embodiments, both together and separately. For example, with regard to the optical devices illustrated in
There is thus disclosed an aimer module, aimer accessory and method for a mobile device. In some embodiments, the aimer module collimates diffuse light from a lamp on a mobile device for use in capturing a barcode image. The aimer module includes a means for receiving light from a lamp of the mobile device, and a means for generating a light pattern on the surface containing a barcode. The receiving means and the generating means may include a grating and/or configuration of mirrors. Registration of the light pattern and the barcode in a scan area enhances the ability of the specialized software on the mobile device to read the barcode.
In one embodiment, an aimer module for a mobile device is provided. The aimer module includes a grating configured to receive light from a lamp of the mobile device and to generate a light pattern on the surface containing a barcode. Registration of the light pattern and the barcode in a scan area enhances the ability of the specialized software on the mobile device to read the barcode.
An optical element for receiving light from the lamp and providing the light to the grating may be included. The optical element may further include at least one of a lens, a reflective surface, a light pipe and an optical fiber. A collector may be included that is configured for collecting light incident upon the camera.
The grating may include at least one of a pair of substantially parallel slits and a substantially rectangular array of holes. The aimer accessory may be configured to offset light from the lamp away from the camera, and may be configured to extend an optical range for reading the barcode. The aimer accessory may be configured as one of a simple offset aimer, a basic aimer, an elongated offset aimer, a standard offset aimer, or a tube offset aimer.
The aimer accessory may be configured for reading a barcode including in a format that is one of: Codabar; Code 25 (Interleaved); Code 25 (Non-interleaved); Code 11; Code 39; Code 93; Code 128; CPC Binary; DUN 14; EAN 2; EAN 5; EAN-8, EAN-13; Facing Identification Mark; GS1-128; GS1 DataBar; HIBC; Intelligent Mail barcode; ITF-14; JAN; KarTrak ACI; Latent image barcode; MSI; Pharmacode; PLANET; Plessey; PostBar; POSTNET; RM4SCC/KIX; Telepen; UPC; as well as others.
The aimer accessory may be configured for reading a barcode including a format that is one of: Aztec Code; Code 1; ColorCode; Color Construct Code; CrontoSign; CyberCode; d-touch; DataGlyphs; Data Matrix; Datastrip Code; digital paper; EZcode; Color; High Capacity Color Barcode; HueCode; InterCode; MaxiCode; MMCC; NexCode; Nintendo e-Reader; Dotcode; PDF417; QR code; ShotCode; SPARQCode; as well as others.
In another embodiment, a mobile device configured for blind or targeted scanning of a barcode is provided. The mobile device includes an aimer module affixed to the mobile device. The aimer module includes a grating configured to receive light from a lamp of the mobile device and to generate a light pattern on the surface containing a barcode. Registration of the light pattern and the barcode either in a scan area illuminated by the aimer module or in the near vicinity of the light pattern enhances the capability of a camera of the mobile device to read the barcode.
The mobile device may include one of a smartphone, a tablet computer, or other special purpose device. Blind and targeted scanning may enable reliable readout of the barcode without use of a display. The light pattern may include parallel lines, a single line, a square or rectangle, an image outline, a single or an array of dots, an arrow, a set of crosshairs, or other shapes or images.
The mobile device may include a computer program product that consists of machine executable instructions stored on non-transitory machine readable media, with the instructions configured for performing the functions depicted in
According to a method of this disclosure, light is emitted from a lamp of the mobile device along a first optical path toward a barcode target. The first optical path defines a light axis L. The optical path of the emitted light is then changed from the first optical path to a second optical path that is oblique to the barcode target. The optical path of the emitted light is then changed again from the oblique optical path to a third optical path that is directed at the barcode target. The third optical path defines a light shifted axis L. Finally, the mobile device captures the image of the barcode target.
In some embodiments, an aimer accessory for a mobile device is provided. The aimer accessory includes a body configured for being affixed to the mobile device. The body includes a collimator terminating with a grating disposed in a distal portion thereof. The grating is configured to receive light from a lamp of the mobile device and to generate a light pattern on the surface containing a barcode. Registration of the light pattern and the barcode in a scan area enhances the ability of the mobile device to capture a barcode image. Registration may be configured for blind mode or target mode scanning. In blind mode scanning, the registration occurs on a detection of the light pattern and the barcode in a viewing angle of a camera of the mobile device. In target mode scanning, the registration occurs on a detection of the light pattern hovering over the barcode in a viewing angle of a camera of the mobile device.
The accessory may further include an optical element for receiving light from the lamp and providing the light to the grating. The optical element may include at least one of a lens, a reflective surface, a light pipe and an optical fiber. The accessory may further include a collector configured for collecting light incident upon the camera. The grating may include at least one of a pair of substantially parallel slits and a substantially rectangular array of holes.
The accessory may be configured to offset light from the lamp away from the camera. The offset may be configured to extend an optical range for reading the barcode. The accessory may be configured as one of a simple offset aimer, a basic aimer, an elongated offset aimer, a standard offset aimer, a tube offset aimer, and a fitted aimer.
The body of the accessory may further include a retainer for retaining the accessory on the mobile device. The retainer may terminate in a clip. The accessory may be configured as a clip-on accessory.
The accessory may be configured for reading a barcode including a format that is one of: Codabar; Code 25, non-interleaved 2 of 5; Code 25 interleaved 2 of 5; Code 11; Code 39; Code 93; Code 128; CPC Binary; DUN 14; EAN 2; EAN 5; EAN-8, EAN-13; Facing Identification Mark; GS1-128; GS1 DataBar; HIBC; Intelligent Mail barcode; ITF-14; JAN; KarTrak ACI; Latent image barcode; MSI; Pharmacode; PLANET; Plessey; PostBar; POSTNET; RM4SCC/KIX; Telepen; and, U.P.C.
The accessory may be configured for reading a barcode comprising a format that is one of: Aztec Code; Code 1; ColorCode; Color Construct Code; CrontoSign; CyberCode; d-touch; DataGlyphs; DataGlyphs; Data Matrix; Datastrip Code; digital paper; EZcode; High Capacity Color; High Capacity Color Barcode; HueCode; InterCode; MaxiCode; MMCC; NexCode; Nintendo e-Reader#Dot code; PDF417; Qode; QR code; ShotCode; and, SPARQCode. The accessory may be configured for reading a barcode comprising a plurality of colors.
In another illustrative embodiment, a mobile device configured for either blind or targeted scanning of a barcode is provided. The mobile device includes a body configured for being clipped onto the mobile device. The body includes a collimator terminating with a grating disposed in a distal portion thereof. The grating is configured to receive light from a lamp of the mobile device and to generate a light pattern on the surface containing the barcode. Registration of the light pattern and the barcode in a scan area enhances the ability of the mobile device to capture a barcode image. Registration may be configured for blind mode or target mode scanning. In blind mode scanning, the registration occurs on a detection of the light pattern and the barcode in a viewing angle of a camera of the mobile device. In target mode scanning, the registration occurs on a detection of the light pattern hovering over the barcode in a viewing angle of a camera of the mobile device.
The mobile device may include one of a smart phone, a tablet computer and a special purpose device.
The either blind or targeted scanning enables reliable readout of the barcode without use of a display. The light pattern may include at least one of substantially parallel lines, an array of dots, and a set of crosshairs. Combinations of slits and holes may be used. A variety of orientations may be provided, and geometric patterns may be used as well.
In another illustrative embodiment, a method for configuring a mobile device for scanning a barcode is provided. The method includes selecting an aimer accessory for the mobile device. The aimer accessory includes a body configured for being affixed to the mobile device. The body includes a collimator terminating with a grating disposed in a distal portion thereof. The grating is configured to receive light from a lamp of the mobile device and to generate a light pattern on the surface containing a barcode. Registration of the light pattern and the barcode in a scan area enhances the ability of the mobile device to capture a barcode image. The aimer accessory is affixed to the mobile device. The method may further include detecting the light pattern and the barcode in a viewing angle of a camera of the mobile device and capturing the image of the barcode target. The method may further include detecting the light pattern as hovering over the barcode in a viewing angle of a camera of the mobile device and capturing the image of the barcode target.
The aimer accessory and the code reader application may be employed on a variety of mobile devices. Generally, it is only required that the mobile device include a camera, a lamp, and appropriate components for operation thereof. Examples of other mobile devices include tablet computers, as well as special purpose devices such as handheld units used for taking field inventory of assets, a dedicated barcode reader, and other such devices.
The grating may generate a variety of light patterns. For example, a set of dots, a single line, a square or rectangle, and crosshairs may be used. Combinations of slits and holes may be used. A variety of orientations may be provided, and geometric patterns may be used as well. In some embodiments, the grating is configured with regard for a particular type, or symbology, of barcode that will be read. For example, a substantially rectangular array of holes may be useful for registration with a substantially rectangular barcode, such as a PDF417 barcode.
In addition, a variety of techniques may be employed for barcode recognition. Use of horizontal bars, parallel lines, dots, crosshairs, and other such aiming patterns may be used to assist with barcode recognition.
An appropriately equipped aimer accessory may provide for re-concentrating light that would otherwise be dispersed.
Software may be downloaded onto or provided with the mobile device of this disclosure that produces a software-produced button on the display of the mobile device. In addition, initiation or triggering of a scan by the mobile device may be performed by programmatically re-mapping of one of the mobile device buttons for such use, or triggered externally using Wi-Fi, NFC, or other technology.
The software may further provide user feedback on “good” or “bad” images, or decode of a symbology, via user prompts such as an audible sound from the mobile device, a vibration from the mobile device, an activity on the display, such as blinking of the screen, a color change, a movement of an image displayed, etc. Additionally, the feedback may be wirelessly transmitted to a remote location for action, recording, etc.
The aimer module and accessory of this disclosure may further assist in battery conservation and power management since images may be captured more efficiently according to this disclosure.
In some embodiments, an aimer accessory can be formed to include an attachment base and an attachment body that can be removably secured to the attachment base. The attachment base can be configured to be secured to a mobile device or case through alignment with a case opening, adhesives, magnets, or other attachment mechanisms. The attachment body can include an optical device, such as a mirror arrangement, light pipe, or grating, and can be configured to be removably secured to the attachment base. In this way, for example, the attachment body can be removably secured to the mobile device or case so that the optical device of the attachment body can be used with a camera or light source of the mobile device.
In some embodiments, an attachment for use with a mobile device and a case for the mobile device can include an attachment base and an attachment body that can be removably secured to the attachment base. The attachment body can include an optical device, such as a mirror arrangement, light pipe, grating, LED or other light source, and so on. The attachment base can include an anchor portion configured to be disposed at least partly in an interior portion of the case, and a tongue configured to extend away from the anchor portion along an exterior portion of the case. A controller included in the attachment body can control some functions of a light source included in the attachment body based upon optical signals received from a light source of the mobile device at a light detector included in the attachment body. The light source can be controlled to illuminate an imaging target (e.g., with a targeting pattern) and can be controlled to optically communicate with the mobile device via an imaging device of the mobile device.
In some embodiments, a method of communication between a mobile device and an attachment can include a light source of the mobile device transmitting optical signals to a light detector of the attachment. The method can also include a light source of the attachment transmitting optical signals to an imaging device of the mobile device.
In some embodiments, an attachment assembly can be provided for use with a mobile device and a case for the mobile device, with the mobile device including an imaging device and a mobile-device light source, and the case including a case optical opening that is optically aligned with one or more of the imaging device and the mobile-device light source when the case is secured to the mobile device. An attachment base can be secured to the case with a cut-out disposed at least partly around the case optical opening. An attachment body can be removably secured to the attachment base, with a protrusion of the attachment body that includes a first window and a second window extending into the optical opening of the case, with the first window in optical alignment with the imaging device and the second window in optical alignment with the mobile-device light source.
In some embodiments, a system can be provided for communicating with a mobile device that is configured to acquire and analyze images of symbols, with the mobile device including an imaging device and a mobile-device light source. An attachment can include an optical sensor configured to receive optical signals from the mobile-device light source, and at least one attachment light source. Based upon the optical signals received at the optical sensor from mobile-device light source, a processor can activate the at least one attachment light source to direct light onto an external target; or can configure at least one illumination parameter for the attachment. The processor can be additionally configured to activate the at least one attachment light source to communicate with the mobile device via the imaging device.
In some embodiments, a method is provided for communicating information between a mobile device and an attachment, with the mobile device including an imaging device and a mobile-device light source, and with the attachment including an optical sensor and at least one attachment light source. First optical signals can be received at the optical sensor. Based on the first optical signals, one or more of the following can be implemented: activating the at least one attachment light source for one or more of image acquisition and image targeting; and configuring at least one illumination parameter for the attachment. The at least one attachment light source can be activated to provide second optical signals to the imaging device to transmit non-image information to the mobile device.
Various other components may be included and called upon for providing for aspects of the teachings herein. For example, additional materials, combinations of materials, and/or omission of materials may be used to provide for added embodiments that are within the scope of the teachings herein.
Standards for performance, selection of materials, functionality, and other discretionary aspects are to be determined by a user, designer, manufacturer, or other similarly interested party. Any standards expressed herein are merely illustrative and are not limiting of the teachings herein.
When introducing elements of the present invention or the embodiment(s) thereof, the articles “a,” “an,” and “the” are intended to mean, unless otherwise limited or defined, that there are one or more of the elements. Similarly, the adjective “another,” when used to introduce an element, is intended to mean one or more elements. The terms “including”, “comprising,” “having” and variations thereof are intended to be inclusive such that there may be additional elements other than the listed elements. Similarly, unless otherwise limited or defined, the phrases “at least one of A, B, and C,” “one or more of A, B, and C,” and the like, are meant to indicate A, or B, or C, or any combination of A, B, and/or C, including, potentially, single or multiple instances of each of A, B, and/or C.
While the invention has been described with reference to illustrative embodiments, it will be understood by those skilled in the art that various changes may be made and equivalents may be substituted for elements thereof without departing from the scope of the invention. In addition, many modifications will be appreciated by those skilled in the art to adapt a particular instrument, situation or material to the teachings of the invention without departing from the essential scope thereof. Therefore, it is intended that the invention not be limited to the particular embodiment disclosed as the best mode contemplated for carrying out this invention, but that the invention will include all embodiments falling within the scope of the appended claims.
Boatner, John Bryan, Gifford, Michael, Kearns, Steven, Gifford, Bobby Dale, Stein, David James
Patent | Priority | Assignee | Title |
10528772, | Feb 24 2012 | SOCKET MOBILE, INC | Assisted aimer for optimized symbol scanning by a portable computing device having an integral camera |
10719675, | Feb 24 2012 | Socket Mobile, Inc. | Assisted aimer for optimized symbol scanning by a portable computing device having an integral camera |
10909340, | Feb 24 2012 | Socket Mobile, Inc. | Aimer beam formation facilitating rapid barcode processing by a user with a standard smart phone |
Patent | Priority | Assignee | Title |
8346979, | Jul 06 2011 | KOAMTAC, INC | Connectivity sled for electronic pairing and physical cooperation between a mobile device and associated peripheral devices |
8832323, | Jul 06 2011 | KOAMTAC, INC | Connectivity sled for electronic pairing and physical cooperation between a mobile device and associated peripheral devices |
9107484, | Jan 08 2013 | Hand Held Products, Inc. | Electronic device enclosure |
9110355, | Jul 03 2014 | BBY SOLUTIONS, INC | External flash device for mobile electronic devices |
20100134679, | |||
20130013813, | |||
20130109316, | |||
20140071547, | |||
20140078594, | |||
20150199549, | |||
20150220766, | |||
20150254485, | |||
20150356336, | |||
20160188940, | |||
20160209735, | |||
20160232389, | |||
20160292477, | |||
EP2500758, |
Executed on | Assignor | Assignee | Conveyance | Frame | Reel | Doc |
May 19 2017 | Cognex Corporation | (assignment on the face of the patent) | / | |||
May 23 2017 | BOATNER, JOHN BRYAN | Cognex Corporation | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 042600 | /0600 | |
May 24 2017 | STEIN, DAVID JAMES | Cognex Corporation | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 042600 | /0600 | |
May 25 2017 | GIFFORD, MICHAEL | Cognex Corporation | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 042600 | /0600 | |
May 25 2017 | GIFFORD, BOBBY DALE | Cognex Corporation | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 042600 | /0600 | |
Jun 02 2017 | KEARNS, STEVEN | Cognex Corporation | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 042600 | /0600 |
Date | Maintenance Fee Events |
Jan 24 2022 | REM: Maintenance Fee Reminder Mailed. |
Jul 11 2022 | EXP: Patent Expired for Failure to Pay Maintenance Fees. |
Date | Maintenance Schedule |
Jun 05 2021 | 4 years fee payment window open |
Dec 05 2021 | 6 months grace period start (w surcharge) |
Jun 05 2022 | patent expiry (for year 4) |
Jun 05 2024 | 2 years to revive unintentionally abandoned end. (for year 4) |
Jun 05 2025 | 8 years fee payment window open |
Dec 05 2025 | 6 months grace period start (w surcharge) |
Jun 05 2026 | patent expiry (for year 8) |
Jun 05 2028 | 2 years to revive unintentionally abandoned end. (for year 8) |
Jun 05 2029 | 12 years fee payment window open |
Dec 05 2029 | 6 months grace period start (w surcharge) |
Jun 05 2030 | patent expiry (for year 12) |
Jun 05 2032 | 2 years to revive unintentionally abandoned end. (for year 12) |