The present disclosure relates generally to monitoring systems and, more specifically, to methods for monitoring a dock leveler deck.
Typical loading docks provide an area for vehicles (e.g., trucks, trailers, etc.) to back up next to an elevated platform of a building so that cargo can be readily transferred between the vehicle and the building. Some loading docks include equipment such as dock levelers, vehicle restraints and/or various sensors. Dock levelers provide an adjustable bridge over which material handling equipment can travel between the platform and the vehicle's truck or trailer bed. Some example vehicle restraints have barriers that engage some part of the vehicle to help prevent the vehicle from prematurely driving away from the platform.
Example dock leveler systems and methods disclosed herein detect the presence of personnel in an area adjacent a door of a loading dock. In some examples, the example dock leveler systems and methods disclosed herein employ a sensor (e.g., a touchless sensor) to detect or determine the presence of a potential obstruction on a deck of the dock leveler system and/or whether the deck of the dock leveler system is at desired predetermined elevation. In some examples, the dock leveler systems and methods determine when the deck is raised to an elevation relative to a vehicle sufficient to allow a lip of the dock leveler system to be extended between a stored position and a deployed position (e.g., to be extended from a front edge of the deck) without interference with a lower rear edge of a vehicle parked at the loading dock. In some examples, the dock leveler systems and methods disclosed herein determine whether an incline of the deck is at an angle greater than (e.g., that may be too steep relative to) a minimum angle required for certain material handling equipment to traverse the deck such as, for example, automatic guided vehicles. In some examples, the dock leveler systems and methods disclosed herein determine whether a cargo door of a vehicle is in open position or a closed position when the vehicle is parked at the loading dock.
The example sensor 26 of
The example sensor 30 of
In some examples, the sensor 26 and/or the sensor 30 emits and/or receives one or more beams 28′ (
In some examples, as shown in
The controller 50 is schematically illustrated to represent any suitable controller. The term, “controller” refers to a logic circuit (e.g., wiring, relays, IC circuit, computer, programmable logic controller, etc.) that emits or generates a visual signal, an audible signal and/or a machine actuating signal in response to receiving input from the sensor 26, from a manual input device (e.g., a push button), and/or from other devices (e.g., electromechanical limit switches) communicatively coupled (e.g., via a network, wire, Bluetooth, etc.). In some examples, the controller 50 processes and/or analyzes information based on one or more signals from the sensor 26 and causes an output such as, for example, generating an audible signal, a visual signal, etc. In some examples, the controller 50 is located remotely from the sensor 26. In some examples, the controller 50 and the sensor 26 are housed within a common enclosure or housing. In some examples, parts of the controller 50 are integrated within the sensor 26 while other parts are spaced apart or located remotely from the sensor 26. In some examples, the controller 50 is housed within a single enclosure. In some examples, the controller 50 is divided among multiple enclosures.
The term “normal state” refers to the sensor's output when the deck 14 is at the lowered position while body 12 is absent or not present on the deck 14. The term “triggered state” refers to the sensor's output or reaction when the sensor 26 detects a certain interruption in the field of view 28, where the interruption includes, for example, the deck 14 having moved to the raised position and/or the body 12 being on the deck 14. In examples where the sensor 26 is a camera or 3D imaging scanner, the sensor 26 is in a triggered state when the sensor's captured and analyzed image indicates that the deck 14 is at or above the raised position and/or the body 12 is present on the deck 14. In examples where the sensor 26 is a photoelectric eye or similar device, the sensor 26 is in the normal state when one or more beams 28′ is unobstructed or in an uninterrupted state (e.g., the beams 28′ or 34 are not interrupted by either the deck 14 or the body 12). In examples where the sensor 26 is a photoelectric eye or a similar device, the sensor 26 is in the triggered state when one or more of the beams 28′ is obstructed in a pattern or characteristic indicative of the deck 14 being at or above the raised position and/or the body 12 is on the deck 14.
Once the controller 50 determines that the deck 14 has moved to the predetermined raised position, in some examples, the controller 50 (e.g., automatically) commands the lip 18 to extend or deploy. In other examples, when the controller 50 determines that the deck 14 has moved to the predetermined raised position, the controller 50 prompts manual activation of the lip 18 and the controller 50 does not cause the lip 18 to extend until the controller 50 receives an input signal 60 (e.g., a manual pushbutton activation—see
In addition or alternatively,
The sensor 1102 of the illustrated example detects information related to a condition of a loading dock. In this example, the condition relates to a position of a deck of the loading dock. Additionally or alternatively, in some examples, the condition is based on a presence of an object (e.g., a body, personnel, etc.) present on the deck, the deck moving to an upright position, the deck in the upright position, a position of a door of the loading dock (e.g., a dock door), a presence of a vehicle and/or whether a door of the vehicle is open, etc. In this example, the input detector 1104 detects input related to the controller such as a presence of the input signal 60. In this example, the sensor data analyzer 1106 receives sensor data from the sensor 1102, which is then sent to the loading dock condition analyzer 1108 to determine, define, interpret and/or analyze a condition of the loading dock. In this example, the loading dock condition analyzer 1108 signals the device controller to control a device such as an actuator, for example, on the loading dock (e.g., controls the deck). In some examples, the loading dock condition analyzer 1108 signals and/or triggers the reporter 1114 to provide an indication (e.g., the visual and/or audible signal 52) of the condition of the loading dock.
While an example manner of implementing the controller 1100 of
A flowchart representative of example machine readable instructions for implementing the controller 1100 of
As mentioned above, the example processes of
The program of
The loading dock condition analyzer 1108 of the illustrated example uses data related to positions of components of the loading dock (e.g., a position of the deck, a position of a lip of a deck, etc.) and/or the presence of objects and/or bodies on the deck to determine a condition of the loading dock based on monitoring the loading dock (block 1204). In this example, the condition is also based on a position of a door of the loading dock, which is determined based on monitoring the area of the loading dock and/or the sensor data received. In other examples, the condition is further based on a position of a vehicle (e.g., the vehicle 36) and/or a position of the vehicle is also determined based on monitoring the area and/or sensor data received. The loading dock condition analyzer 1108 of the illustrated example periodically receives data from the sensor and, in turn, processes the data as the data is received at the sensor data analyzer 1106. In some other examples, the loading dock analyzer 1108 receives input at the input detector 1104, for example, and determination of the condition is further based on the input.
In some examples, the sensor detects a presence of a vehicle at the loading dock (block 1206). Additionally or alternatively, the sensor detects a distance of the vehicle to the loading dock. In some examples, the condition is further based on the presence of the vehicle and/or the distance of the vehicle to the loading dock.
In some examples, movement and/or displacement of the deck and/or a lip of the deck is controlled based on the sensor data and/or a condition of the loading dock determined (block 1208). In particular, the deck of the illustrated example is moved by an actuator or motor via the device controller 1112, for example. In some examples, a body or object detected on the deck prevents the deck from being moved. In some examples, the deck being at a certain elevation causes the device controller 1112 to allow the deck to move further. Additionally or alternatively, the lip of the deck is prevented from extending until the deck is determined to be at a certain position and/or displacement relative to an original position of the deck. In other examples, a docking position of the deck or a degree to which the deck and/or the lip displace is based on sensor data related to a vehicle docked and/or a vertical distance to a storage level (e.g., the trailer bed 62) of the vehicle.
In some examples, an alert is generated at the reporter 1114 if one or more conditions is determined to occur (block 1210). For example, one or more conditions triggers the visual and/or audible signal 52. In some examples the alert is generated and/or triggered by a presence of a body or object detected on the deck, the deck moving to an upright position, the deck being positioned in the upright position, the door of the loading dock being closed, a position of a door of a vehicle at the loading dock, and/or a relative displacement of a trailer bed of a vehicle to the loading dock, etc. Next, the process ends (block 1212).
The program of
In this example, the sensor detects a presence and/or a distance of a vehicle relative to the loading dock (1306). Once the vehicle is positioned in proximity to the deck and/or the condition of the loading dock permits deployment of the deck, for example, the deck and/or the lip of the deck is controlled via the device controller 1112 (block 1308) to the move the deck onto a flatbed of the vehicle. In this example, the spatial data generated via the sensor data is utilized to determine the relative position of the deck to the flatbed. In some examples, an alert is generated and/or displayed at the reporter 1114 (block 1310) and the process ends (block 1312).
The processor platform 1400 of the illustrated example includes a processor 1412. The processor 1412 of the illustrated example is hardware. For example, the processor 1412 can be implemented by one or more integrated circuits, logic circuits, microprocessors or controllers from any desired family or manufacturer.
The processor 1412 of the illustrated example includes a local memory 1413 (e.g., a cache). The processor 1412 includes the example input detector 1104, the example sensor data analyzer 1106, the example sensor data analyzer, the example loading dock condition analyzer 1108, the example device controller 1112, and the example reporter 1114. The processor 1412 of the illustrated example is in communication with a main memory including a volatile memory 1414 and a non-volatile memory 1416 via a bus 1418. The volatile memory 1414 may be implemented by Synchronous Dynamic Random Access Memory (SDRAM), Dynamic Random Access Memory (DRAM), RAMBUS Dynamic Random Access Memory (RDRAM) and/or any other type of random access memory device. The non-volatile memory 1416 may be implemented by flash memory and/or any other desired type of memory device. Access to the main memory 1414, 1416 is controlled by a memory controller.
The processor platform 1400 of the illustrated example also includes an interface circuit 1420. The interface circuit 1420 may be implemented by any type of interface standard, such as an Ethernet interface, a universal serial bus (USB), and/or a PCI express interface.
In the illustrated example, one or more input devices 1422 are connected to the interface circuit 1420. The input device(s) 1422 permit(s) a user to enter data and commands into the processor 1412. The input device(s) can be implemented by, for example, an audio sensor, a microphone, a camera (still or video), a keyboard, a button, a mouse, a touchscreen, a track-pad, a trackball, isopoint and/or a voice recognition system.
One or more output devices 1424 are also connected to the interface circuit 1420 of the illustrated example. The output devices 1024 can be implemented, for example, by display devices (e.g., a light emitting diode (LED), an organic light emitting diode (OLED), a liquid crystal display, a cathode ray tube display (CRT), a touchscreen, a tactile output device, a printer and/or speakers). The interface circuit 1420 of the illustrated example, thus, typically includes a graphics driver card, a graphics driver chip or a graphics driver processor.
The interface circuit 1420 of the illustrated example also includes a communication device such as a transmitter, a receiver, a transceiver, a modem and/or network interface card to facilitate exchange of data with external machines (e.g., computing devices of any kind) via a network 1426 (e.g., an Ethernet connection, a digital subscriber line (DSL), a telephone line, coaxial cable, a cellular telephone system, etc.).
The processor platform 1400 of the illustrated example also includes one or more mass storage devices 1428 for storing software and/or data. Examples of such mass storage devices 1428 include floppy disk drives, hard drive disks, compact disk drives, Blu-ray disk drives, RAID systems, and digital versatile disk (DVD) drives.
The coded instructions 1432 of
From the foregoing, it will appreciate that the above disclosed methods and apparatus to monitor and/or determine a condition of a loading dock.
Although certain example methods, apparatus and articles of manufacture have been disclosed herein, the scope of coverage of this patent is not limited thereto. On the contrary, this patent covers all methods, apparatus and articles of manufacture fairly falling within the scope of the claims of this patent.
This patent arises from a continuation of U.S. patent application Ser. No. 14/509,860, (Now U.S. Pat. No. 10,227,190) which was filed on Oct. 8, 2014. U.S. patent application Ser. No. 14/509,860 is hereby incorporated herein by reference in its entirety. Priority to U.S. patent application Ser. No. 14/509,860 is hereby claimed.
Number | Name | Date | Kind |
---|---|---|---|
3138812 | Prosser | Jun 1964 | A |
3290709 | Whitenack, Jr. et al. | Dec 1966 | A |
3290710 | Whitenack, Jr. | Dec 1966 | A |
3599262 | Carder et al. | Aug 1971 | A |
4279050 | Abbott | Jul 1981 | A |
4727613 | Alten | Mar 1988 | A |
4977635 | Alexander | Dec 1990 | A |
5191328 | Nelson | Mar 1993 | A |
5205010 | Hageman | Apr 1993 | A |
5299386 | Naegelli et al. | Apr 1994 | A |
5396676 | Alexander et al. | Mar 1995 | A |
5440772 | Springer et al. | Aug 1995 | A |
5586355 | Metz et al. | Dec 1996 | A |
5774920 | Alexander | Jul 1998 | A |
5826291 | Alexander | Oct 1998 | A |
5831540 | Sullivan et al. | Nov 1998 | A |
6205721 | Ashelin et al. | Mar 2001 | B1 |
6233885 | Hoffmann et al. | May 2001 | B1 |
6311352 | Springer | Nov 2001 | B1 |
6499169 | Hahn et al. | Dec 2002 | B2 |
6502268 | Ashelin et al. | Jan 2003 | B2 |
6880301 | Hahn et al. | Apr 2005 | B2 |
7032267 | Mitchell et al. | Apr 2006 | B2 |
7045764 | Beggs et al. | May 2006 | B2 |
7185463 | Borgerding | Mar 2007 | B2 |
7213285 | Mitchell | May 2007 | B2 |
7380375 | Maly | Jun 2008 | B2 |
7954606 | Tinone et al. | Jun 2011 | B2 |
8065770 | Proffitt et al. | Nov 2011 | B2 |
8307588 | Hoffmann et al. | Nov 2012 | B2 |
8424254 | Ballester | Apr 2013 | B2 |
8547234 | Maly et al. | Oct 2013 | B2 |
8590087 | Swessel et al. | Nov 2013 | B2 |
8616826 | Cotton et al. | Dec 2013 | B2 |
8678736 | Andersen et al. | Mar 2014 | B2 |
8806689 | Riviere et al. | Aug 2014 | B2 |
8926254 | Pocobello et al. | Jan 2015 | B2 |
9284135 | Sveum | Mar 2016 | B2 |
9290336 | Ballester | Mar 2016 | B2 |
9776511 | Brooks et al. | Oct 2017 | B2 |
9830825 | Anstett | Nov 2017 | B2 |
9926148 | Hochstein | Mar 2018 | B2 |
9957121 | Sveum | May 2018 | B2 |
10106342 | Avalos | Oct 2018 | B2 |
20030145535 | DiBiase et al. | Aug 2003 | A1 |
20040075046 | Beggs et al. | Apr 2004 | A1 |
20060137261 | Maly | Jun 2006 | A1 |
20060266275 | DiBiase et al. | Nov 2006 | A1 |
20070248440 | Andersen et al. | Oct 2007 | A1 |
20070260429 | Vera et al. | Nov 2007 | A1 |
20080010757 | Hochstein et al. | Jan 2008 | A1 |
20080042865 | Shephard et al. | Feb 2008 | A1 |
20080127435 | Maly et al. | Jun 2008 | A1 |
20080141470 | Belongia | Jun 2008 | A1 |
20080223667 | Tinone et al. | Sep 2008 | A1 |
20090274542 | Pocobello et al. | Nov 2009 | A1 |
20100146719 | Swessel et al. | Jun 2010 | A1 |
20100269273 | Proffitt et al. | Oct 2010 | A1 |
20110219632 | Odom | Sep 2011 | A1 |
20120025964 | Beggs et al. | Feb 2012 | A1 |
20130030873 | Davidson | Jan 2013 | A1 |
20130291455 | Wiegel et al. | Nov 2013 | A1 |
20130320828 | Nitzsche et al. | Dec 2013 | A1 |
20150009046 | Senfleben et al. | Jan 2015 | A1 |
20150013083 | Palmersheim | Jan 2015 | A1 |
20150047132 | Sveum et al. | Feb 2015 | A1 |
20150047133 | Sveum | Feb 2015 | A1 |
20150375947 | Hochstein et al. | Dec 2015 | A1 |
20160075526 | Avalos | Mar 2016 | A1 |
20160104364 | Brooks et al. | Apr 2016 | A1 |
20170043967 | Walford et al. | Feb 2017 | A1 |
20170341514 | Brooks et al. | Nov 2017 | A1 |
20170341515 | Brooks et al. | Nov 2017 | A1 |
20170341516 | Brooks et al. | Nov 2017 | A1 |
20170368939 | Brooks et al. | Dec 2017 | A1 |
20190232785 | Brooks et al. | Aug 2019 | A1 |
Number | Date | Country |
---|---|---|
1146309 | May 1983 | CA |
3049611 | Jul 1982 | DE |
2206664 | Jul 2010 | EP |
2360110 | Aug 2011 | EP |
2373558 | Jul 2013 | EP |
2865622 | Apr 2015 | EP |
2144706 | Mar 1985 | GB |
2008307932 | Dec 2008 | JP |
02070383 | Sep 2002 | WO |
2006061495 | Jun 2006 | WO |
2008008699 | Jan 2008 | WO |
2009073001 | Jun 2009 | WO |
2010064989 | Jun 2010 | WO |
2015166339 | Nov 2015 | WO |
Entry |
---|
Crawford, “Crawford Docking Equipment Product Datasheet,” last retrieved from [http://www.crawfordsolutions.com.sa//AAES/crawfordsolutionsCOM/EN/Products/Docking/Dock%201evellers/Docking%20equipment/1.%20Product%20datasheet/PD_DEQP_ALL_EN_ORG.pdf] on Jun. 16, 2015, 16 pages. |
“Redacted Proposal Dock Equipment Automation,” Jul. 9, 2013, 10 pages. |
International Bureau, “International Preliminary Report on Patentability,” issued in connection with International Application No. PCT/US2014/050716, dated Feb. 25, 2016, 9 pages. |
International Bureau, “International Preliminary Report on Patentability,” issued in connection with International Application No. PCT/US2014/050721, dated Feb. 25, 2016, 10 pages. |
International Bureau, “International Preliminary Report on Patentability,” issued in connection with International Patent Application No. PCT/US2015/038311, dated Jan. 19, 2017, 8 pages. |
International Searching Authority, “International Search Report,” issued in connection with International Patent Application No. PCT/US2015/038311, dated Oct. 16, 2015, 3 pages. |
International Searching Authority, “Written Opinion,” issued in connection with International Patent Application No. PCT/US2015/038311, dated Oct. 16, 2015, 3 pages. |
International Searching Authority, “International Search Report,” issued in connection with International Patent Application No. PCT/US2014/050716, dated Dec. 11, 2014, 6 pages. |
International Searching Authority, “Written Opinion,” issued in connection with International Patent Application No. PCT/US2014/050716, dated Dec. 11, 2014, 6 pages. |
International Searching Authority, “International Search Report,” issued in connection with International Patent Application No. PCT/US2014/050721, dated Dec. 11, 2014, 6 pages. |
International Searching Authority, “Written Opinion,” issued in connection with International Patent Application No. PCT/US2014/050721, dated Dec. 11, 2014, 8 pages. |
United States Patent and Trademark Office, “Non-Final Office Action,” issued in connection with U.S. Appl. No. 14/204,987, dated Jan. 14, 2015, 6 pages. |
United States Patent and Trademark Office, “Non-Final Office Action,” issued in connection with U.S. Appl. No. 14/204,987, dated Jun. 25, 2015, 8 pages. |
United States Patent and Trademark Office, “Requirement for Restriction and/or Election,” issued in connection with U.S. Appl. No. 14/204,987, dated Oct. 3, 2014, 8 pages. |
United States Patent and Trademark Office, “Notice of Allowance and Fee(s) Due,” issued in connection with U.S. Appl. No. 14/204,987, dated Nov. 5, 2015, 6 pages. |
United States Patent and Trademark Office, “Advisory Action,” issued in connection with U.S. Appl. No. 13/965,730, dated Jan. 7, 2015, 3 pages. |
United States Patent and Trademark Office, “Examiner's Answer,” issued in connection with U.S. Appl. No. 13/965,730, dated Aug. 26, 2015, 11 pages. |
United States Patent and Trademark Office, “Non-Final Office Action,” issued in connection with U.S. Appl. No. 13/965,730, dated Dec. 19, 2013, 10 pages. |
United States Patent and Trademark Office, “Final Office Action,” issued in connection with U.S. Appl. No. 13/965,730, dated Apr. 7, 2014, 6 pages. |
United States Patent and Trademark Office, “Non-Final Office Action,” issued in connection with U.S. Appl. No. 13/965,730, dated Jul. 18, 2014, 6 pages. |
United States Patent and Trademark Office, “Final Office Action,” issued in connection with U.S. Appl. No. 13/965,730, dated Oct. 29, 2014, 6 pages. |
United States Patent and Trademark Office, “Notice of Allowance and Fee(s) Due,” issued in connection with U.S. Appl. No. 13/965,730, dated Dec. 28, 2017, 5 pages. |
United States Patent and Trademark Office, “Non-Final Office Action,” issued in connection with U.S. Appl. No. 14/752,332, dated Jun. 2, 2016, 10 pages. |
United States Patent and Trademark Office, “Final Office Action,” issued in connection with U.S. Appl. No. 14/752,332, dated Nov. 7, 2016, 11 pages. |
United States Patent and Trademark Office, “Notice of Allowance and Fee(s) Due,” issued in connection with U.S. Appl. No. 14/752,332, dated Jun. 21, 2017, 10 pages. |
United States Patent and Trademark Office, “Non-Final Office Action,” issued in connection with U.S. Appl. No. 15/682,235, dated Apr. 4, 2018, 14 pages. |
United States Patent and Trademark Office, “Non-Final Office Action,” issued in connection with U.S. Appl. No. 15/682,262, dated Apr. 3, 2018, 16 pages. |
United States Patent and Trademark Office, “Non-Final Office Action,” issued in connection with U.S. Appl. No. 15/682,216, dated Apr. 3, 2018, 16 pages. |
United States Patent and Trademark Office, “Non-Final Office Action,” issued in connection with U.S. Appl. No. 15/682,250, dated Apr. 4, 2018, 21 pages. |
Canadian Intellectual Property Office, “Office Action,” issued in connection with Canadian Patent Application No. 2,953,708, dated Jan. 18, 2018, 4 pages. |
European Patent Office, “Communication pursuant to Rules 161(1) and 162 EPC,” issued in connection with European Patent Application No. 15790719.7, dated May 16, 2017, 2 pages. |
European Patent Office, “Communication pursuant to Rules 161(1) and 162 EPC,” issued in connection with European Patent Application No. 15745012.3, dated Feb. 15, 2017, 2 pages. |
European Patent Office, “Communication pursuant to Article 94(3) EPC,” issued in connection with European Patent Application No. 15745012.3, dated Mar. 29, 2018, 6 pages. |
IP Australia, “Notice of Acceptance,” issued in connection with Australian Patent Application No. 2015288224, dated Dec. 8, 2017, 4 pages. |
IP Australia, “Examination Report No. 1,” issued in connection with Australian Patent Application No. 2015288224, dated Oct. 10, 2017, 5 pages. |
Canadian Intellectual Property Office, “Office Action,” issued in connection with Canadian Patent Application No. 2,919,890, dated Dec. 9, 2016, 4 pages. |
Canadian Intellectual Property Office, “Office Action,” issued in connection with Canadian Patent Application No. 2,919,890, dated Jul. 31, 2017, 4 pages. |
Canadian Intellectual Property Office, “Office Action,” issued in connection with Canadian Patent Application No. 2,919,891, dated Dec. 16, 2016, 4 pages. |
Canadian Intellectual Property Office, “Office Action,” issued in connection with Canadian Patent Application No. 2,919,891, dated Sep. 1, 2017, 3 pages. |
United States Patent and Trademark Office, “Non-Final Office Action,” issued in connection with U.S. Appl. No. 14/752,332, dated Feb. 24, 2017, 12 pages. |
IFM Efector, Inc., “Image Sensor,” 1998-2015, retrieved from http://www.ifm.com/ifmus/web/pmd3d-portal1.htm; http://www.ifm.com/ifmus/web/padv/020_020_010_010_010_010.html; http://www.ifm.com/ifmus/web/news/pnews_8r3n6b.html; http://www.ifm.com/ifmus/web/news/pnews_8t9jh3.html on Jan. 27, 2015, 7 pages. |
Bea, “Sparrow: Unidirectional opening sensor for automatic industrial doors,” Jan. 2010, last retrieved from http://www.bea-industrial.be/uploads/docs/manuals/ug_sparrow_en_vl.pdf, on Jan. 27, 2015, 2 pages. |
Bea, “Sparrow: Opening Sensor for Industrial Doors Commercial sheet,” last retrieved from http://www.bea-industrial.be/uploads/docs/product_sheets/ind_cs_sparrow_en_vl_web.pdf, on Jan. 27, 2015, 2 pages. |
Bea, “LZR-I100/I110 Laser Scanners for Industrial Doors,” May 2011, last retrieved from http://www.bea-industrial.be/uploads/docs/manuals/ug_lzr-100-110_en_v5.pdf, on Jan. 27, 2015, 12 pages. |
Bea, “LZR-i100 Safety Sensor for Industrial Doors Commercial sheet,” last retrieved from http://www.bea-industrial.be/uploads/docs/product_sheets/ind_cs_LZR-i100_en_vl_web.pdf, on Jan. 27, 2015, 2 pages. |
Bea, “LZR-i110 Safety Sensor for Industrial Doors Commercial sheet,” last retrieved from http://www.bea-industrial.be/uploads/docs/product_sheets/ind_cs_LZR-i110_en_vl_web.pdf, on Jan. 27, 2015, 2 pages. |
Bea, “Falcon/-XL Opening sensor for automatic industrial doors,” last retrieved from http://www.bea-industrial.be/uploads/docs/manuals/ug_falcon_en_v3.pdf, on Jan. 27, 2015, 2 pages. |
Bea, “Falcon: Opening Sensor for Industrial Doors Commercial sheet,” last retrieved from http://www.bea-industrial.be/uploads/docs/product_sheets/ind_cs_falcon_falconxl_en_vl_web.pdf, on Jan. 27, 2015, 2 pages. |
Bea, “LZE i30 Safety Sensor for Industrial Doors,” Nov. 22, 2013, last retrieved from http://www.beainc.com/wp-content/themes/bea/documents/79.0006.04.EN%20LZR-i30%2020131122.pdf, on Jan. 27, 2015, 2 pages. |
Pepperl & Fuchs, “Ultrasonic sensor UC4000-30GM-IUR2-V15 Technical data,” Aug. 12, 2014, last retrieved from http://files.pepperl-fuchs.com/selector_files/navi/productInfo/edb/104094_eng.pdf on Jan. 27, 2015, 5 pages. |
Pepperl & Fuchs, “Multi-Ray LED Scanner OMD8000-R2100-R2-2V15 Dimensions,” Sep. 25, 2014, last retrieved from http://files.pepperl-fuchs.com/selector_files/navi/productInfo/edb/264888_eng.pdf, on Jan. 27, 2015, 3 pages. |
International Searching Authority, “International Search Report,” issued in connection with Application No. PCT/US2015/054647, dated Jan. 28, 2016, 6 pages. |
International Searching Authority, “Written Opinion,” issued in connection with Application No. PCT/US2015/054647, dated Jan. 28, 2016, 7 pages. |
United States Patent and Trademark Office, “Advisory Action,” issued in connection with U.S. Appl. No. 14/509,860, dated Dec. 29, 2016, 8 pages. |
United States Patent and Trademark Office, “Final Office Action,” issued in connection with U.S. Appl. No. 14/509,860, dated Oct. 7, 2016, 21 pages. |
United States Patent and Trademark Office, “Non-Final Office Action,” issued in connection with U.S. Appl. No. 14/509,860, dated Jun. 2, 2017, 21 pages. |
United States Patent and Trademark Office, “Non-Final Office Action,” issued in connection with U.S. Appl. No. 14/509,860, dated Jan. 4, 2018, 25 pages. |
United States Patent and Trademark Office, “Non-Final Office Action,” issued in connection with U.S. Appl. No. 14/509,860, dated Apr. 1, 2016, 39 pages. |
International Searching Authority, “International Preliminary Report on Patentability,” issued in connection with PCT Application No. PCT/US2015/054647, dated Apr. 20, 2017, 9 pages. |
IP Australia, “Examination report No. 1,” issued in connection with Australian Patent Application No. 2018201797, dated Oct. 17, 2018, 3 pages. |
IP Australia, “Examination report No. 1,” issued in connection with Australian Patent Application No. 2018201796, dated Oct. 16, 2018, 16 pages. |
United States Patent and Trademark Office, “Notice of Allowance and Fee(s) Due,” issued in connection with U.S. Appl. No. 14/509,860, dated Jul. 13, 2018, 16 pages. |
United States Patent and Trademark Office, “Notice of Allowance and Fee(s) Due,” issued in connection with U.S. Appl. No. 14/509,860, dated Oct. 17, 2018, 33 pages. |
Canadian Intellectual Property Office, “Office Action,” issued in connection with Canadian Patent Application No. 2,962,140, dated Feb. 4, 2020, 5 pages. |
European Patent Office, “Communication under Rule 71(3) EPC,” issued in connection with European Patent Application No. 15 790 719.7, dated Jan. 29, 2020, 41 pages. |
United States Patent and Trademark Office, “Non-Final Office Action,” issued in connection with U.S. Appl. No. 15/682,250, dated Apr. 4, 2018, 50 pages. |
United States Patent and Trademark Office, “Non-Final Office Action,” issued in connection with U.S. Appl. No. 15/682,216, dated Apr. 3, 2018, 42 pages. |
United States Patent and Trademark Office, “Non-Final Office Action,” issued in connection with U.S. Appl. No. 15/682,262, dated Apr. 3, 2018, 39 pages. |
United States Patent and Trademark Office, “Non-Final Office Action,” issued in connection with U.S. Appl. No. 16/121,375 dated Jun. 13, 2019, 39 pages. |
Canadian Intellectual Property Office, “Notice of Allowance,” issued in connection with Canadian Patent Application No. 2,919,891, dated Aug. 2, 2018, 1 page. |
Canadian Intellectual Property Office, “Notice of Allowance,” issued in connection with Canadian Patent Application No. 2,919,890, dated Jun. 7, 2018, 1 page. |
Number | Date | Country | |
---|---|---|---|
20190202646 A1 | Jul 2019 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 14509860 | Oct 2014 | US |
Child | 16298664 | US |