Patent Grant
11390488
This application claims the benefit of Indian Application No. 202011027220 filed Jun. 26, 2020, which is incorporated herein by reference in its entirety.
The present disclosure relates generally to passenger conveyor systems, and more particularly, to passenger conveyor maintenance and operational diagnostics.
Service providers of passenger conveyor systems such as elevator systems, escalator systems, etc., for example, typically rely on user complaints to alert of an existing malfunction or fault before the necessary components are repaired or replaced. Not only must the system to be taken off-line at unscheduled times because it is not known when a component or system will malfunction, but one or more follow-up visits are often required once the problem is identified in order to acquire ride quality data for accurate diagnosis. In addition, diagnosis and monitoring of passenger conveyor systems before and after component faults are identified requires access to circuitry, control boxes, drive systems, or components that may be hidden behind various panels or otherwise out of sight during normal operation. Accessing the circuitry, control boxes, drive systems, or other components may also require that the system be taken out-of-service to provide a technician access to the necessary components.
According to a non-limiting embodiment, a passenger conveyor diagnostic system includes a processor that stores at least one visual inspection diagnostic, and a passenger conveyor system including at least one sensor configured to capture one or both of an image and a sound. The processor applies the at least one visual inspection diagnostic to one or both of the image and the sound to generate a diagnosed status of the passenger conveyor system, and overlays the diagnosed status of the passenger conveyor system on the image.
According to another non-limiting embodiment, a mobile terminal device is configured to diagnose a passenger conveyor system. The mobile terminal device comprises a memory unit that stores a visual inspection application configured to perform at least one visual inspection diagnostic, and a network interface device that establishes communication with at least one sensor installed on the passenger conveyor system. The mobile terminal device further includes an electronic hardware controller that applies the at least one visual inspection diagnostic to one or both of images and a sounds obtained from the at least one sensor to determine at least one diagnostic result of the passenger conveyor system, and displays the image with the least one diagnostic result overlaid thereon.
According to still another non-limiting embodiment, a method is provided to diagnose a passenger conveyor system. The method comprises storing, via a processor, at least one visual inspection diagnostic, and capturing, via at least one sensor installed on the passenger conveyor system, one or both of an image and a sound. The method further comprises applying, via the processor, the at least one visual inspection diagnostic to one or both of the image and the sound to generate a diagnosed status of the passenger conveyor system. The method further comprises overlaying, via the processor, the diagnosed status of the passenger conveyor system on the image.
The following descriptions should not be considered limiting in any way. With reference to the accompanying drawings, like elements are numbered alike:
A detailed description of one or more embodiments of the disclosed apparatus and method are presented herein by way of exemplification and not limitation with reference to the Figures.
The term “about” is intended to include the degree of error associated with measurement of the particular quantity based upon the equipment available at the time of filing the application. For example, “about” can include a range of ±8% or 5%, or 2% of a given value.
With reference now to
The processor 106 also includes one or more input/output (I/O) devices 108. In some embodiments, the I/O device(s) 108 may include one or more of a keyboard or keypad, a touchscreen or touch panel, a display screen, a microphone, a speaker, a mouse, a button, a remote control, a joystick, a printer, a telephone or mobile device (e.g., a smartphone), etc. The I/O device(s) 108 may be configured to provide an interface to allow a user to interact with the system 100.
The computing system 100 further includes a network interface 110 capable of electrically communication with a cloud computing network 200, or any other remote network. The network interface 110 includes any communication device (e.g., a modem, wireless network adapter, etc.) that operates according to a network protocol (e.g., Wi-Fi, Ethernet, satellite, cable communications, etc.) which establishes a wired and/or wireless communication with the cloud computing network 200.
The computing system 100 is illustrative as an example. In some embodiments, one or more of the entities may be optional. In some embodiments, additional entities not shown may be included. For example, in some embodiments the computing system 100 may be associated with one or more networks, such as one or more computer or telephone networks. In some embodiments, the entities may be arranged or organized in a manner different from what is shown in
Turning now to
The cloud server 202 can store setup parameters for select functions. In some embodiments, the setup parameters can be stored in a controller. In some embodiments, there may be a simplified failover functionality located in the controller in the event that there is a connection loss between the controller and the cloud server 202.
In some embodiments, operational data and metrics may be collected and stored at a cloud server 202 across a portfolio of multiple units, sites, or groups. The data and metrics can include, but are not limited to, captured images, sounds and/or measurements. The cloud server 202 can also store various models, algorithms, software programs, prestored images and/or sounds, which can be utilized together with the collected data and metrics to perform analysis operations by the backend computer 206. For example, the backend computer 206 includes a processor configured to perform an analysis on the captured images and/or sounds, which may indicate trends and may be used to respond to needs (e.g., product needs or functionality needs). The analysis may also be used to facilitate diagnostic or troubleshooting capabilities. Metrics may be used to trigger or enhance the accuracy of sales proposals. Metrics may be used to provide or schedule maintenance activities, such as preventative maintenance activities. In some embodiments, interface protocols configured to operate with new devices, for example, may be stored in a cloud server 202 and used by a local controller. It should be appreciated that the computer 206 or processor performing the operations described above can be performed in the cloud network 200 or locally on the mobile terminal device 204.
In some embodiments, functional upgrades for diagnostics, prognostics, and remote repair/rescue functions can be deployed to customers as they are released and deployed into a cloud server 202. Functionality may be developed at the backend computer 206 (installed at a server location 207 remotely located from the mobile terminal device 204) and deployed to the cloud server 202. One or more tests may be executed to ensure that the functionality satisfies operational or safety requirements.
The mobile terminal device 204 is capable of communicating with the cloud server 202 over one or more connections, channels, or links facilitated by a network interface. The mobile terminal device 204 includes a smartphone 204, for example, which can be located in or near a passenger conveyor location 205, and is capable of electrically communicating with the cloud server 202 via a connection 208. The connection 208 can adhere to one or more communication protocols, standards, or the like. For example, the connection 208 can adhere to telephone, cellular, Wi-Fi, Ethernet, satellite, Bluetooth, Zigbee, zWave, cable communications, or any other known communication method. In some embodiments, the connection 208 may be constant or persistent. Although the mobile terminal device 204 will be referred to as a smartphone 204 hereinafter, the mobile terminal device 204 can include any mobile device capable of facilitating interaction between one or more stored software applications (i.e., apps) and the cloud server 202. For example, the mobile terminal device 204 can also include a computer tablet, a laptop computer, a smart watch, etc.
The smartphone 204 includes a display 220, and one or more sensors. The sensors include, but are not limited to, one or more cameras 222, a speaker 224, a microphone 226, and an accelerometer 228. The camera 222 is capable of capturing still images and/or moving images, which the smartphone 204 can reproduce on the display 220. The speaker 224 outputs sound from the smartphone 204 to an external environment. The microphone 226 captures sounds and noise present in the vicinity of the smartphone 204. The captured noise can be recorded to memory and reproduced via the speaker 224. The accelerometer 228 may be constructed as a single-axis or and multi-axis accelerometer, and is capable of detecting magnitude and direction of smartphone's proper acceleration, as a vector quantity. The accelerometer 228 can sense the orientation of the smartphone 204, coordinate acceleration, vibrations, shock, and movements.
As described above, functionality may be (re)located to a cloud server (e.g., cloud server 202). In terms of elevator systems, for example, such functionality may include dispatch functions for one or more passenger conveyor devices, mobile terminals, operational mode determinations, diagnostic functions, special contract features, etc. Regarding dispatch functions, in some embodiments a user request for service received at, e.g., a hall box located on a particular floor of a building may be communicated to the cloud server and the cloud server may transmit a command that directs a specified elevator car to relocate to that particular floor to fulfill the service request.
In some embodiments, a local controller (not shown) can maintain some functionality, and as such, may include hardware and computing resources to support such functionality. The controller can include hardware and/or software to communicate with the cloud server 202. For example, the controller can exchange data and commands with the cloud server 202 to perform control functions.
Turning now to
The elevator system 300 includes a machine 301 that drives an elevator car 302 positioned in a vertical hoistway (not shown). One or more elevator car rails 304 and guides 306 are attached to the hoistway walls. The elevator system 300 further includes one or more elongated hoists 308 which couple the elevator car 302 to a counterweight (not shown). In at least one embodiment, the elongated hoists 308 can be formed as ropes, cables or belts 308 configured to support the weight of the elevator car 302 and the counterweight so as to propel the elevator car 302 in a desired direction (e.g., up or down) within the hoistway. Although a single hoist 308 is shown, it should be appreciated that additional hoists 308 may be implemented without departing from the scope of the invention.
The elevator machine 301 is installed in a machine room 303 located remotely from the elevator car 302. The elevator machine 301 controls a traction sheave 305 that rotates and causes movement of the hoists 308 to drive the elevator car 302 in a selected direction. The elevator system 300 further includes one or more deflector or idler sheaves 310 to assist in guiding the movement of various traction hoists 308. In this manner, the elevator car 302 can be driven to one or more landings or floors vertically arranged with respect to one another. Accordingly, the elevator car 302 can be driven to a requested floor, where passengers can then enter or exit the car 302 via the elevator doors 312.
The elevator car 300 can include a car controller 314 and one or more sensors 316 and 318. The car controller 314 may be in signal communication with the cloud computing network 200 and/or the mobile terminal device 204 as described in greater detail below. In this manner, the car controller 314 can facilitate data exchange between the mobile terminal device 204 and the cloud computing network 200 and/or the video cameras 316 and microphones 318.
The sensors include, but are not limited to, an accelerometer and vibration sensor, along with one or more video cameras 316 and one or more microphones 318. The video cameras 316 and microphones 318 are in signal communication with the cloud computing network 200. The video cameras 316 are configured to capture video frames and/or generate a video stream of the elevator car 302 and/or the area and/or components located in the vicinity of the elevator car 302. The area includes, for example, the surrounding elevator shaft, while the components include, for example, the car rails 304, guides 306, hoists 308, and sheaves 310. The microphones 318 are configured to capture sounds (e.g., vibrations, rattles, squeaking, etc.) external to the elevator car 302, sounds within the elevator car 302, and/or sounds generated by various elevator components such as, for example, the car rails 304, guides 306, hoists 308, sheaves 305, 310 and the machine 301. Although the video cameras 316 and the microphones 318 are illustrated as separate and individual sensors, it should be appreciated that a video camera 316 and a microphone 318 can be integrated together to construct a single sensor without departing from the scope of the invention.
Still referring to
The maintenance technician 250 can operate the smartphone 204 to perform a visual inspection of the elevator system 300 without having to locate to one or more particular areas of the elevator system that may be experiencing technical issues. For instance, the smartphone 204 is installed with a visual inspection software application, and is configured to display an image or image stream overlaid with diagnostic results obtained using the visual inspection software. A technician may then analyze the image or image stream and overlaid diagnostic results to diagnose the elevator system without needing to physically locate themselves within the interior space (e.g., elevator shaft) of the elevator system.
The visual inspection software application can be executed by a processor installed on the smartphone 250 to initiate the video cameras 316 and microphones 318 and perform visual/audio inspection, along with quantitative measurements and analysis pertaining to the operation of the elevator system 300. For example, the visual inspection software application and processor work in conjunction to compare captures images and/or sounds to pre-stored images and/or sounds to diagnose the operation of the elevator system. Analytical data generated by the visual inspection software application can be stored locally on the smartphone 204 and/or can be stored in the cloud server 202. The analytical data includes, but is not limited to, machine noise, machine vibration, elevator car vibrations, rope noises, transient/travel noise, idler/deflector noises, rail and guide vibrations, and elevator door noise. The analytical data stored in the cloud server 202 and can further be archived and tracked over time to determine whether an identified problem has been resolved following a recent repair effort, or whether the problem remains or has worsened.
In one or more embodiments, the visual inspection software application sends a request to perform a visual inspection test, which is communicated to the car controller 314 and/or cloud computing network 200. In response to receiving the visual inspection test request, the car controller 314 or the cloud computing network 200 initiates the video cameras 316 and microphones 318. The initiation includes buffering memory associated with the video cameras 316 and microphones 318 before proceeding to execute the visual inspection test.
The visual inspection test request may also include a requested diagnostic operation selected by the user 250. While performing the selected diagnostic operation the video cameras 316 and microphones 318 may capture video, still images and sounds. Once the selected diagnostic operation is completed, the car controller 314 and/or the cloud computing network 200 executes the diagnostic operation selected by the user 250, while the video cameras 316 and microphones 318 capture video frames and/or sounds during the ongoing diagnostic operation. Following completion of the buffering, cloud computing network 200 and/or the visual inspection software can perform an analysis of the captured data to identify one or more abnormalities occurring during the diagnostic test. The analysis can include audio processing to identify a possible abnormality such as for example, a faulty component. In one or more embodiments, the cloud computing network 200 and/or the visual inspection software can compare an image of a component captured during the diagnostic operation to a stored image of a known normal operating component to determine whether the captured component appears normal or abnormal. Similarly, the cloud computing network 200 and/or the visual inspection software can compare sounds captured by the microphones 318 to sounds stored in memory to distinguish between normal operating components and abnormal operating components.
When an abnormality is detected, a timestamp is determined corresponding to the time period included among the video frames or during the video stream at which the abnormality occurred. The cloud computing network 200 and/or the visual inspection software then processes the corresponding captured video frames by generating a video stream and overlaying the video stream with a results graphic user interface (GUI) that displays the results of the diagnostic operation. In one or more embodiments, the results GUI can be operated in a diagnostic mode or a metrics mode. When the diagnostic mode is invoked, the results GUI overlays graphical status indicators indicating a diagnosed status of one or more given elevator system components. When the metrics mode is invoked, the results GUI overlays graphical status indicators alerting to normal or abnormal operating characteristics of the elevator system such as, for example, vibrations, maximum noise levels, average noise levels, etc. Although the diagnostic information and metric information are overlaid according to two separate results GUI modes, it should be appreciated that the results GUI can operate in a single mode to simultaneously overlay both the diagnostic information and the metric information without departing from the scope of the invention.
Turning to
The escalator system 400 includes a truss 402 extending between a lower landing 404 and an upper landing 406. A plurality of sequentially connected treadplates or steps 408 are connected to a drive chain (not shown) and travel through a closed loop path within the truss 402. A pair of handrails 410 are coupled to the truss 402 and are located at opposing sides of the steps 408. The handrails 410 move along with the steps 408 to provide passenger support. A machine 412 drives the steps 408 and handrails 410. The machine 412 is typically located in a machine space 414 under one of the landings e.g., contained within the lower landing 404.
In one or more non-limiting embodiments, the escalator system 400 can include a diagnostic system 450. The diagnostic system 450 can be integrated in one or more steps 408 of the escalator system 400 so as to provide a diagnostic step 409. In some embodiments, the diagnostic step 409 can be implemented as a fixed component of the escalator system 400. In other embodiments, the diagnostic step 409 can replace a standard escalator step 408 to facilitate diagnostic operations of the elevator system 400. Once the diagnostic operations are completed the diagnostic step 409 may optionally be removed and replaced with the standard step 408.
The diagnostic system 450 can include at least one camera (not shown), at least one microphone (not shown), various sensors (e.g., an accelerometer, vibration sensor, etc.) and a step controller (not shown) all which are integrated within the diagnostic step 409. The step controller includes a network interface as described herein. Accordingly, the diagnostic system 450 included in the diagnostic step 409 can wirelessly communicate with the cloud computing network 200 and/or the smartphone 204, e.g., via the step controller.
The camera is configured to capture images of the escalator interior space (e.g., the interior space of the escalator truss), while the microphone is configured to capture sounds such as vibrations, squeaks, etc. In one or more embodiments, the cameras and the microphones may collect images and/or sounds of various escalator components including, but not limited to, the handrail drive system, tracking system and/or or sprocket wheels. Further, the cameras and microphones can capture the images and/or sounds as the diagnostic step 409 travels along the track of the escalator system 400, thereby collecting diagnostic data (e.g., images and/or sound) at various locations. A more detailed description of the diagnostic step 409 implementing the diagnostic system 450 is described in U.S. Patent Application Publication 2018/0208441, which is assigned to Otis Worldwide Corp., and is expressly incorporated by reference herein in its entirety.
Still referring to
The visual inspection software application is capable of providing quantitative measurement and analysis of the escalator system 400 ride quality obtained by the smartphone 204. For example, the visual inspection software application is capable of performing real-time comparisons between actual performance of the escalator system 400 and its expected performance. Analytical data generated by the visual inspection software application can be stored locally on the smartphone 204 and/or can be stored in the cloud server of the cloud network 200. The analytical data includes, but is not limited to, machine noise, machine vibration, truss vibrations, step vibrations, step noise, handrail vibrations, handrail noise, and drive chain noise. The analytical data stored in the smartphone 204 and/or cloud server can further be archived and tracked over time determine whether an identified problem has been resolved following a recent repair effort, or whether the problem remains or has worsened.
In one or more non-limiting embodiments, the inspection software application installed on the smartphone 204 communicates with the cloud network 200 and/or the step controller, and initiates the cameras and microphones of the escalator diagnostic system 450 to capture images and sounds while executing the selected diagnostic. Following completion of the diagnostic, the camera and microphone data (e.g., captured images and sounds) is buffered, a video stream is generated, and the results GUI is overlaid on the video stream, similar to the diagnostic operations described regarding the elevator system 300 described above. In one or more embodiments, the diagnostic and/or metrics data displayed by the results GUI overlaid on the video stream can be changed based on the selected diagnostic operation. In addition, timestamps can be generated in response to detecting an anomaly during the diagnostic operation and an alert indicator can be included in the results GUI alerting the technician to the detected anomaly as described in detail above. As in the case of elevator diagnostic tests described above, the abnormal or sub-optimal noise and vibrations can be analyzed to implicate a particular product part or component. Symptoms, diagnoses and/or metrics are displayed by the results GUI, which is overlaid on the image stream generated according to the diagnostic operation as describe above with reference to the elevator system. In addition, the diagnostic data and/or metrics data displayed by the results GUI overlaid on the video stream dynamically change as the diagnostic step travels along the track to different locations of the escalator system 400.
Referring to
Referring to
The home GUI 500 includes a diagnostic selection field 502 and a user instruction field 504. The diagnostic selection field 502 allows the user to select a desired diagnostic operation among a plurality of different diagnostic operations capable of diagnosing different maintenance issues of a passenger conveyor system. In terms of an elevator system environment, for example, the various diagnostic operations include, but are not limited to, a “Door Cycle” diagnostic operation and a “Floor-to-Floor” diagnostic operation. The “Door Cycle” diagnostic test executes a testing routine to diagnose the operation of the elevator doors. The “Floor-to-Floor” diagnostic operation executes a testing routine to diagnose any abnormal or sub-optimal operation of the elevator as it travels within the building.
In terms of an escalator system environment, the diagnostic selection field 502 allows a user to select from various diagnostic operations including, but not limited to, a Machine Diagnostic, an Ascending Step Run diagnostic, a Descending Step Run diagnostic, a Full Track Run Diagnostic, a Handrail Diagnostic, and a Braking Diagnostic. The diagnostic operations are described in greater detail below.
The Machine Diagnostic operation allows for capturing noises and/or vibrations generated from within the machine space and compares the measured data to the expected range of noises and/or expected range of vibrations for that equipment.
The Ascending Step Run Diagnostic, Descending Step Run Diagnostic, and Full Track Run Diagnostic operations monitor real-time operation of the escalator system as the user rides along with the moving steps. The diagnostics during this operation include, sound detection of step and handrail noises, noises of the drive chain, vibrations of the steps, and step traveling speed.
The Handrail Diagnostic can be more specifically directed to diagnosing issues with the handrail. The diagnostics performed during the Handrail Diagnostic includes analyzing noises produced by the handrails and/or vibrations of the handrails.
The Braking Diagnostic can diagnose whether the steps of the escalator are brought to a stop in an expected amount of time following an escalator braking event. The deceleration of the steps can be compared to a threshold to determine whether the braking function of the escalator is performing as expected. The Braking Diagnostic can also diagnostic the deceleration of the steps. For example, any pulsations in the deceleration of the steps can implicate specific parts or components of the braking mechanism.
The user instruction field 504 displays diagnostic operating instructions that direct the user how to properly execute the selected diagnostic operation. The instructions include, for example, instructing a user where to locate the smartphone with respect to the user's person, along with a location with respect to the passenger conveyor system while will provide the user with most optimal results. When the “Door Cycle” diagnostic is selected, for example, the user instruction field 504 can instruct the user to “hold the phone chest high, face the landing door, and press start.” The instructions presented in the user instruction field 504 can vary based on the diagnostic operation selected from the diagnostic selection field 502. For example, when performing the Door Cycle diagnostic, the instructions may instruct the user to locate the smartphone 204 near the elevator doors or near a specific component associated with the doors, whereas instructions corresponding to the Machine Diagnostic instructions will instruct the user to locate the phone within the machine space of the escalator. Similar instructions can be provided to the user when performing diagnostic operations associated with another type of passenger conveyor system such as, for example, an escalator system.
Turning to
The smartphone 204 also displays a video playback interface 550. The video playback interface 550 includes a progress bar 551 and a progress indicator 552. The progress bar 551 is indicative of a complete duration of the video stream. The progress indicator indicates the current playback duration among the complete duration of the video stream. When the video stream includes one or more defects detected following analysis of the diagnostic operation, the smartphone 204 also displays an alert indicator 554. The alert indicator 554 is displayed at the time of the video stream that corresponds to the timestamp corresponding to an abnormality detected during the diagnostic operation. In this manner, a user can move (e.g., touch and slide) the progress indicator 552 toward the alert indicator 554 to quickly reach a point in the video stream that contains the detected abnormality.
The diagnostic results GUI 510 includes a component field 512 and a status indicator field 514. The component field 512 lists one or more components that were diagnosed according to a selected diagnostic operation (i.e., the diagnostic operation selected from the home GUI 500). One or more of the displayed components can change depending on the selected diagnostic operation. For example, “ropes” and “rails” may be displayed after performing the Floor-to-Floor diagnostic operation, while “sill” and “hanger” may be displayed after performing the Door Cycle diagnostic operation. Similarly, escalator components such as “step chain” and “handrail drive chain”, for example, may be displayed after performing one or more escalator system diagnostic operations.
The status indicator field 514 displays a status indicator 516a corresponding to each component name displayed in the component field 512. The status indicator 516a can be displayed with a unique identified (e.g., color, shape, etc.) which indicates a diagnosed status of the component following the diagnostic operation. For example, a first status indictor 516a (e.g., a green-colored graphical indicator) may indicate that the corresponding component is operating normally or as expected following the diagnostic operation. A second status indictor 516b (e.g., a yellow-colored graphical indicator) may indicate that although still providing suitable results, a corresponding component was detected as operating with one or more irregularities. For example, although an elevator car traveled between one or more floors with noise levels that are generally acceptable to most passengers, the noise may contain features that suggest a roller bearing is wearing and should be replaced. Therefore, the maintenance technician may monitor this unit carefully for the next several service visits.
The results GUI may be configured to dynamically (i.e., actively) change as video playback progresses through the duration of the video stream.
Referring to
Turning to
With reference now to
At operation 608, the selected diagnostic operation is performed and real-time ride quality data of the passenger conveyor system is obtained at operation 610. The ride quality data may include video frames, images, noises, sounds, and vibrations captured during the real-time operation of the passenger conveyor system during the executed diagnostic operation. At operation 612, a determination is made as to whether the diagnostic is complete. When the diagnostic operation is not complete, the method returns to operation 610 and continues capturing the real-time data.
When, however, the diagnostic operation is complete at operation 612, the method proceeds to operation 614 and analyzes the images and sounds captured during the diagnostic operation. The images and sounds and analyzed using various algorithms and processing applications. For example, real-time captured images and/or sounds can be compared to pre-stored images and sounds associated with normal operation conditions to determine whether an abnormal image or abnormal sound is present. In some examples, a vibrations and/or sounds can be compared to a threshold value to detect and abnormal condition.
At operation 616, a determination is made as to whether an abnormality is detected based, at least in part, on the analysis of the diagnostic operation results, and a video stream including the captured images and sounds is generated at operation 618. When an abnormality is detected, however, a timestamp corresponding to the detected abnormality is determined at operation 620. The timestamp includes a time period at which the abnormality occurs in the video stream.
Turning to operation 622, a results GUI is generated based, at least in part, on the analysis of the diagnostic results. At operation 624, a video stream is displayed on a display screen (e.g., on a screen of a smartphone) and the results GUI is overlaid on the video stream. When one or more abnormalities are detected at operation 616, an alert indicator based, at least in part, on a corresponding timestamp is added to a playback duration bar displayed on the display screen. At operation 626, the video stream is played (also referred as a video steam playback). Accordingly, the displayed results GUI indicates the status of the elevator system at the current playback duration of the video stream and the operation ends at operation 628.
Accordingly, various non-limiting embodiments described herein provide a visual inspection system that allows a technician to diagnose a passenger conveyor system without requiring the technician to physically locate to a specific area of the conveyor system. For instance, a technician can view a video stream overlaid with a results GUI to identify an abnormality within an interior space of a conveyor system (e.g., an elevator shaft or interior escalator space) without physically locating themselves in the interior space. In this manner, they safety of the technician can be improved while also improving servicing response time.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the present disclosure. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, element components, and/or groups thereof.
While the present disclosure has been described with reference to an exemplary embodiment or 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 present disclosure. In addition, many modifications may be made to adapt a particular situation or material to the teachings of the present disclosure without departing from the essential scope thereof. Therefore, it is intended that the present disclosure not be limited to the particular embodiment disclosed as the best mode contemplated for carrying out this present disclosure, but that the present disclosure will include all embodiments falling within the scope of the claims.
| Number | Date | Country | Kind |
|---|---|---|---|
| 202011027220 | Jun 2020 | IN | national |
| Number | Name | Date | Kind |
|---|---|---|---|
| 20050088520 | Wiesinger et al. | Apr 2005 | A1 |
| 20180208441 | Yamada et al. | Jul 2018 | A1 |
| 20200102188 | Holey et al. | Apr 2020 | A1 |
| 20200122974 | Yang | Apr 2020 | A1 |
| Number | Date | Country |
|---|---|---|
| 111606176 | Apr 2020 | CN |
| 3459889 | Mar 2019 | EP |
| 2006018883 | Feb 2006 | WO |
| 2010121629 | Oct 2010 | WO |
| 2020012608 | Jan 2020 | WO |
| Entry |
|---|
| Search Report issued in European Patent Application No. 20215132.0; Application Filing Date Dec. 17, 2020, dated Jun. 18, 2021 (7 pages). |
| Number | Date | Country | |
|---|---|---|---|
| 20210403283 A1 | Dec 2021 | US |
