The present disclosure relates generally to flex button systems, and more particularly, to vehicle flex button systems.
Existing vehicle window switches are mostly hinge or pivot-based, which become incompatible with sleek interior designs of modern vehicles. Such hinge or pivot mechanics disrupt smooth surfaces of the interior of vehicle doors. Therefore, it is desirable to replace such switches with new systems that can detect press actions without unseemly movement of a button.
One aspect of the present disclosure is directed to a flex button system. The system may comprise a top panel. The top panel may comprise one or more cut-through openings and one or more flaps. At least one side of the flap may be edged by the cut-through opening. The flap may be configured to flex with respect to the top panel, in response to a press of the flap. At least one of the one or more cut-through openings may be configured to accommodate one or more fingers.
Another aspect of the present disclosure is directed to a vehicle. The vehicle may comprise a top panel on a door of the vehicle. The top panel may comprise one or more cut-through openings and one or more flaps. The at least one side of the flap may be edged by the cut-through opening. The flap may be configured to flex with respect to the top panel, in response to a press of the flap. At least one of the one or more cut-through openings may be configured to accommodate one or more fingers.
It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only, and are not restrictive of the invention, as claimed.
The accompanying drawings, which constitute a part of this disclosure, illustrate several embodiments and, together with the description, serve to explain the disclosed principles.
Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. The following description refers to the accompanying drawings in which the same numbers in different drawings represent the same or similar elements unless otherwise represented. The implementations set forth in the following description of exemplary embodiments consistent with the present invention do not represent all implementations consistent with the invention. Instead, they are merely examples of systems and methods consistent with aspects related to the invention.
Existing vehicle window switches cannot meet the design requirements for an integrated and smooth vehicle interior. The disclosed systems can combine the simplicity of human-interface switches and the visual appearance of a continuous surface. The disclosed systems may mitigate or overcome one or more of the problems set forth above and/or other problems in the prior art.
As illustrated in
Vehicle 10 may have any body style of an automobile, such as a sports car, a coupe, a sedan, a pick-up truck, a station wagon, a sports utility vehicle (SUV), a minivan, or a conversion van. Vehicle 10 may also embody other types of transportation, such as motorcycles, boats, buses, trains, and planes. Vehicle 10 may be an electric vehicle, a fuel cell vehicle, a hybrid vehicle, or a conventional internal combustion engine vehicle. Vehicle 10 may be configured to be operated by a driver occupying vehicle 10, remotely controlled, and/or autonomous.
Vehicle 10 may be in communication with a plurality of devices, such as third party device 30 and mobile communication device 40. Mobile communication device 40 may include a smart phone, a tablet, a personal computer, a wearable device, such as a smart watch or Google Glass™, and/or complimentary components. Mobile communication device 40 may be configured to connect to a network, such as a nationwide cellular network, a local wireless network (e.g., Bluetooth™ or WiFi), and/or a wired network. Mobile communication device 40 may also be configured to access apps and websites of third parties, such as iTunes™, Google™, Facebook™, Yelp™, or other apps and websites associated with vehicle 10. Vehicle 10, third party device 30, and mobile communication device 40 may store and share data and information, such as a profile of vehicle 10 (e.g., the year, make, model, and owner of a vehicle).
In some embodiments, mobile communication device 40 may be carried by or associated with one or more users of vehicle 10. For example, vehicle 10 may be configured to determine the identity of a user based on a digital signature or other identification information from mobile communication device 40. For instance, processing unit 114 of vehicle 10 may be configured to relate the digital signature to stored profile data including the person's name and the person's relationship with vehicle 10. The digital signature of mobile communication device 40 may include a determinative emitted radio frequency (RF) or a global positioning system (GPS) tag. Mobile communication device 40 may be configured to automatically connect to or be detected by vehicle 10 through local network 70.
Third party device 30 may include smart phones, personal computers, laptops, pads, servers, and/or processors of third parties. Third party devices 30 may be accessible to the users through mobile communication device 40 or directly accessible by vehicle 10 via network 70.
Vehicle 10 may include a specialized onboard computer 110, a controller 120, an actuator system 130, and an indicator system 140. Onboard computer 110, actuator system 130, and indicator system 140 may all connect to controller 120. Onboard computer 110 may comprise, among other things, an I/O interface 112, a processing unit/processor 114, a storage unit 116, and a memory module 118, which may transfer data and send or receive instructions among one another. Storage unit 116 and memory module 118 may be non-transitory and computer-readable and may store instructions that, when executed by processing unit 114, cause one or more components of system 100 to perform one or more methods. One or more of the components of vehicle 10 may be optional. For example, processing unit 114 may directly connect to indicator system 140, bypassing I/O interface 112 and controller 120. Therefore, it is not necessary that all of the above components be shown in order to disclose an illustrative embodiment.
I/O interface 112 may be configured for two-way communication between onboard computer 110 and various components of system 100. I/O interface 112 may send and receive operating signals to and from mobile communication device 40 and third party device 30. I/O interface 112 may send and receive the data between each of the devices via communication cables, wireless networks, or other communication mediums. For example, mobile communication device 40 and third party devices 30 may be configured to send and receive signals to I/O interface 112 via a network 70. Network 70 may be any type of wired or wireless network that may facilitate transmitting and receiving data. For example, network 70 may be a nationwide cellular network, a local wireless network (e.g., Bluetooth™ or WiFi), and/or a wired network.
Processing unit 114 may be configured to receive signals (e.g., sensor signals from indicator system 140, or a user input from charging target 20, third party device 30, or mobile communication device 40) and process the signals to determine a plurality of conditions of the operation of vehicle 10 (e.g., operations of various components of actuator system 130). Processing unit 114 may also be configured to generate and transmit command signals, via I/O interface 112, in order to actuate other components.
Storage unit 116 and/or memory module 118 may be configured to store one or more computer programs that may be executed by onboard computer 110 to perform functions of vehicle 10. Storage unit 116 and/or memory module 118 may be configured to store information of various vehicle. Storage unit 116 and/or memory module 118 may be further configured to store data and/or look-up tables used by processing unit 114.
Vehicle 10 may also include a controller 120 connected to onboard computer 110 and capable of controlling one or more aspects of operation of vehicle 10. In some examples, controller 120 is connected to one or more actuator systems 130 and one or more indicator systems 140. One or more actuator systems 130 may include, but are not limited to, a motor 131, an engine 132, a power system 133, a brake 134, a motion system 135, a transmission gearing 136, a suspension setup 137, a steering system 138, and one or more doors 139. Onboard computer 110 may control, via controller 120, one or more components of the actuator systems 130 during operation. One or more doors 139 may comprise a flex button system 1391 described below with reference to
The one or more indicator systems 140 can include, but are not limited to, one or more speakers 141, one or more lights 142, one or more displays 143, and one or more user interfaces 144. Onboard computer 100 can control, via controller 120, one or more of the indicator systems 140 to provide indications of the vehicle, the vehicle's surroundings or another vehicle, to receive instructions, and/or to provide information. Display 143 may be disposed at various locations at vehicle 10. Display 143 may be configured to display information related to the vehicle, such as vehicle profile, battery information, access control, and etc.
User interface 144 may be configured to receive inputs from users or devices and to transmit data. For example, user interface 144 may have a display including an LCD, an LED, a plasma display, or any other type of display, and provide a graphical user interface (GUI) presented on the display for user input and data display. User interface 144 may further include speakers or other voice playing devices. User interface 144 may further include input devices, such as a touchscreen, a keyboard, a mouse, a microphone, and/or a tracker ball, to receive a user input. User interface 144 may also connect to a network to remotely receive instructions or user inputs. Thus, the input may be directly entered by a user, captured by user interface 144, or received by user interface 144 over the network.
User interface 144 may also be configured to receive user-defined settings. For example, user interface 144 may be configured to receive user profiles including, for example, an age, a gender, a driving license status, frequent destinations, vehicle charging frequencies, vehicle charging stations, and etc. In some embodiments, user interface 144 may include a touch-sensitive surface configured to receive biometric data (e.g., detect a fingerprint of a user). The touch-sensitive surface may be configured to detect the ridges and furrows of a fingerprint based on a change in capacitance and generate a signal based on the detected fingerprint, which may be processed by processing unit 114. Processing unit 114 may be configured to compare the signal with stored data to determine whether the fingerprint matches recognized users. Vehicle 10 may also be able to connect to the Internet, obtain data from the Internet, and compare the signal with obtained data to identify the users. User interface 144 may be configured to include biometric data into a signal, such that processing unit 114 can identify the person generating the input. User interface 144 may also compare a received voice input with stored voices to identify the person generating the input. Furthermore, user interface 144 may be configured to store data history accessed by the identified person. Based on the identities, processing unit 114 may grant or decline access to use one or more batteries associated with the vehicle.
In some embodiments, user interface 144 may include one or more electrophysiological sensors for encephalography-based autonomous driving. For example, an electrophysiological sensor may detect electrical activities of brains of the user(s) and convert the electrical activities to signals, such that processing unit 114 can execute a corresponding command.
Panel 212 may comprise one or more sensors 213a-213g, e.g., pressure sensors or tactile switches configured to trigger one or more signals based on a detected touch or pressure from top panel 211. Since panel 211 covers panel 212, as shown in
Panel 212 may have a box shape overall and comprise depression areas, such as cavity 216 on top. The depression areas may fit or match with openings on panel 211, such that, for example, a finger may reach into the depression area. Cavity 216 may be divided by a divider 215 into a left and a right depression areas, such that the left and right depression areas are each hosting one sensor and are each configured to accommodate one finger. In some embodiments, a light strip is routed within divider 215 and used to provide illumination to both left and right depression areas.
A left depression area is illustrated in an exploded section view in
In some embodiments, sensor 213e may be configured to control a down motion of a driver side rear window, sensor 213g may be configured to control a up motion of the driver side rear window. Similar to sensor 213e, sensor 213f may be configured to control a down motion of a passenger side rear window, sensor 213d may be configured to control a down motion of a passenger side front window, sensor 213c may be configured to control a down motion of a driver side front window, sensor 213b may be configured to lock or unlock all windows of a vehicle, and sensor 213a may be configured to control a down motion of all windows of the vehicle.
In some embodiments, curved strip opening 223c is illuminated by internal lighting. Internal lighting may be provided by one or more LEDs installed within the depression areas. Internal lighting may also be provided by a light strip installed within divider 215.
As described above, the disclosed flex button systems can replace many discrete parts of hinge or pivot buttons with one piece of material, and are more cost-efficient. With a proper geometric design, the flex button system can last longer than hinge or pivot buttons. Further, the disclosed flex button systems can provide ergonomically smooth surfaces in switch panels to enhance an overall sleek interior design of vehicles.
The specification has described flex button systems. The illustrated structures and steps are set out to explain the exemplary embodiments shown, and it should be anticipated that ongoing technological development will change the structures and the manner in which particular functions are performed. Thus, these examples are presented herein for purposes of illustration, and not limitation. Alternatives (including equivalents, extensions, variations, deviations, etc., of those described herein) will be apparent to persons skilled in the relevant art(s) based on the teachings contained herein. Such alternatives fall within the scope and spirit of the disclosed embodiments.
While examples and features of disclosed principles are described herein, modifications, adaptations, and other implementations are possible without departing from the spirit and scope of the disclosed embodiments. Also, the words “comprising,” “having,” “containing,” and “including,” and other similar forms are intended to be equivalent in meaning and be open ended in that an item or items following any one of these words is not meant to be an exhaustive listing of such item or items, or meant to be limited to only the listed item or items. It must also be noted that as used herein and in the appended claims, the singular forms “a,” “an,” and “the” include plural references unless the context clearly dictates otherwise.
It will be appreciated that the present invention is not limited to the exact construction that has been described above and illustrated in the accompanying drawings, and that various modifications and changes can be made without departing from the scope thereof. It is intended that the scope of the invention should only be limited by the appended claims.
This application claims the benefit of U.S. Provisional Application No. 62/382,124, filed Aug. 31, 2016, the entirety of which is hereby incorporated by reference.
Number | Date | Country | |
---|---|---|---|
62382124 | Aug 2016 | US |