In one embodiment, a data storage device is provided. The data storage device includes a ramp configured to support at least one head in the data storage device, and a movement mechanism coupled to the ramp and configured to move the ramp from a first position to a second position by at least one of expansion or contraction of at least a portion of the movement mechanism. The data storage device further includes a ramp motion control module operably coupled to the movement mechanism. The ramp motion control module is configured to provide the movement mechanism with a first control signal that causes the movement mechanism to move the ramp from the first position to the second position. The data storage device additionally includes a latch configured to hold the ramp.
In another embodiment, a method of operating a ramp that is configured to support a head in a data storage device is provided. The method includes moving the ramp from a first position to a second position. The method also includes selectively releasing the ramp from the second position at different speeds corresponding to different operating conditions in the data storage device.
In yet another embodiment, a data storage system in provided. The data storage system includes a ramp configured to support at least one head in the data storage system. The ramp has a plurality of positions in the data storage system. The data storage system also includes a latch configured to hold the ramp in at least two of the plurality of positions.
Other features and benefits that characterize embodiments of the disclosure will be apparent upon reading the following detailed description and review of the associated drawings.
Embodiments of the disclosure relate to a moveable head-support ramp for use in a data storage device (e.g., a hard disc drive (HDD)).
In general, in order to keep read/write heads from landing on one or more discs in the HDD when, for example, power is removed from the HDD, and to prevent the heads from colliding with outer edges of the discs during load and unload operations, a head-support ramp is provided adjacent to an outer diameter (OD) of the disc or discs. In a traditional HDD, the ramp is placed over portions of the disc surfaces near the OD such that the heads can easily move on and off the discs straight from/onto the ramp. Such ramps, which remain stationary during HDD operation in traditional HDDs, take space on the discs and reduce the area for recording, thereby leading to loss of storage capacity per HDD, about 5% loss in capacity in some cases.
To address this above-noted problem, embodiments of the disclosure employ a retractable ramp that moves completely off the disc(s), or nearly off the disc(s), when the OD area is to be accessed, thereby enabling data recording to be carried out on substantially entire surfaces of the disc(s). Details regarding the different embodiments are provided below in connection with
It should be noted that the same reference numerals are used in different figures for same or similar elements. It should also be understood that the terminology used herein is for the purpose of describing embodiments, and the terminology is not intended to be limiting. Unless indicated otherwise, ordinal numbers (e.g., first, second, third, etc.) are used to distinguish or identify different elements or steps in a group of elements or steps, and do not supply a serial or numerical limitation on the elements or steps of the embodiments thereof. For example, “first,” “second,” and “third” elements or steps need not necessarily appear in that order, and the embodiments thereof need not necessarily be limited to three elements or steps. It should also be understood that, unless indicated otherwise, any labels such as “left,” “right,” “front,” “back,” “top,” “bottom,” “forward,” “reverse,” “clockwise,” “counter clockwise,” “up,” “down,” or other similar terms such as “upper,” “lower,” “aft,” “fore,” “vertical,” “horizontal,” “proximal,” “distal,” “intermediate” and the like are used for convenience and are not intended to imply, for example, any particular fixed location, orientation, or direction. Instead, such labels are used to reflect, for example, relative location, orientation, or directions. It should also be understood that the singular forms of “a,” “an,” and “the” include plural references unless the context clearly dictates otherwise.
It will be understood that, when an element is referred to as being “connected,” “coupled,” or “attached” to another element, it can be directly connected, coupled or attached to the other element, or it can be indirectly connected, coupled, or attached to the other element where intervening or intermediate elements may be present. In contrast, if an element is referred to as being “directly connected,” “directly coupled” or “directly attached” to another element, there are no intervening elements present. Drawings illustrating direct connections, couplings or attachments between elements also include embodiments, in which the elements are indirectly connected, coupled or attached to each other.
As indicated above, in general, in order to keep read/write heads 102 from landing on discs 104 in a data storage device 100 when, for example, power is removed from the data storage device 100, and to prevent the heads 102 from colliding with outer edges of the discs 104 during load and unload operations, a head-support ramp 136 is provided adjacent to the OD 109 of the discs 104. As can be seen in
When, for example, heads 102 are in the parked position and data storage device 100 receives a command from a host (not shown) to access one or more disc 104 surfaces, actuator mechanism 110 rotates about axis 126 to move the heads 102 toward the disc 104 surfaces. Such movement of the actuator mechanism 110 causes the lifts or lift tabs 149 to move towards the discs 104 by following surfaces of the tapers 144 towards the edges 146. When the heads 102 reach the edges 146, they establish bearings (e.g., air bearings) on the disc 104 surfaces and are then able to access the disc 104 surfaces for reading and/or writing to complete executing the command received from the host.
The process of moving the heads 102 from the ramp 136 to the disc 104 surfaces, which is referred to as a head load (or simply a load) operation, occurs smoothly when the edges 146 of the tapers 144 are located over portions of the disc surfaces near the OD 109. Similarly, the process of moving the heads 102 from the disc 104 surfaces to the ramp 136, which is referred to as a head unload (or simply an unload) operation, takes place smoothly when the when the edges 146 of the tapers 144 are located over portions of the disc surfaces near the OD 109. The heads 102 may be unloaded when, for example, the data storage device 100 no longer needs to access the disc 104 surfaces. Portions of the disc 104 surfaces over which the edges 146 of the tapers 144 are positioned during head load and unload operations are referred to as load/unload zones and are denoted by reference numeral 150 in
As indicated above, not recording data in the load/unload zones may amount to a loss of about 5% storage capacity of the data storage device 100. To avoid such a loss in capacity, data storage device 100 employs a retraction mechanism (or movement mechanism) 152 that is attached to ramp 136 and is operable to retract ramp 136, such that edges 146 of tapers 144 are withdrawn from the OD 109 region to no longer substantially overlap the load/unload zones 144 after the heads 102 are properly loaded and supported by, for example, the air bearings, thereby making the load/unload zones 150 accessible for data storage/retrieval.
In some embodiments, in addition to retracting ramp 136 to allow for recording data in load/unload zone 150 during operation of data storage as shown in
In some embodiments, a number of heads 102 is less than a number of disc 104 surfaces. For example, data storage device 100 of
In order to enable the up/down movement of the HSA 138, head-support ramp 136 is designed to be retractable away from the OD 109 to permit the upward/downward movement of the ramp and HSA 138 without contacting the data storage media 104. In order to move the HSA 138 from either the upper position to the lower position or from the lower position to the upper position, the HSA 138 is first rotated about axis 126 until lift tabs 149 of the HSA 138 are supported on ramp 136 when the edges 146 of the tapers 144 are located over portions of the disc surfaces near the OD 109. Then, the ramp 136, with the lift tabs 149 of the HSA 138 thereon, is retracted away from the discs 104 by the retraction mechanism 152. Once the ramp 136 supporting the heads 102 is retraced as shown in
In the embodiment illustrated in
In some embodiments, when a number of heads 102 is less than a number of disc 104 surfaces, and the discs 104 are closely spaced, at least some of the discs 104 may be moved up/down by retractable ramp 136 to enable read/write operations to be carried out. Such an embodiment is shown in
Referring to
In the embodiment shown in
Referring to
To move the ramp 402 to the retracted position shown in
To carry out a “quick release” of the ramp 402 from the retracted position to its non-retraced position (not shown in
At 512, use of the load/unload zone for the read/write operations is monitored. Once it determined that load/unload zone is no longer to be used, control passes to 514. At 514, power is provided to the ramp retraction mechanism (e.g., power is provided to the SMA wire connected to the ramp). Thereafter, at 516, power is provided to the latch mechanism (e.g., power is provided to the SMA coupled to the latch). This causes the latch to disengage from the ramp. At 518, power to the ramp retraction mechanism is terminated (e.g., the power provided to the SMA wire connected to the ramp is terminated). This causes the SMA wire connected to the ramp to expand, thereby returning the ramp to its non-retracted position. After a predetermined wait period shown at 520, the power to the latching mechanism is terminated (e.g., power is provided to the SMA coupled to the latch is terminated) at 522, thereby returning the latch to the non-bent position.
It should be noted that the method embodiments described above may be carried out by drive circuitry 112, head circuitry 132, ramp 136, latch mechanism 406, retraction mechanism 152 (e.g., ramp retraction control module 421), elevator 140, etc. Portions of drive circuitry 112, head circuitry 132 and ramp retraction control module 421 may together constitute a controller that carries out at least some control operations in the method embodiments described above.
In the above-described embodiments, the retraction mechanism employs a SMA wire the contracts when it is energized. The SMA wire is only one example of an element that may be used to carry out the retraction of the ramp. In general, any retraction mechanism that moves the ramp between non-retracted and retracted positions by expansion and/or contraction may be employed. The expansion and/or contraction may act in a manner similar to a muscle that can change length by contracting and/or stretching. Thus, the ramp retraction mechanism may also be viewed as a muscle-based system. In general, any suitable expansion/contraction system may be employed in different embodiments. For example, some alternate embodiments may employ piezoelectric elements to enable the retraction of the ramp.
In the above-described embodiments, the movement of the ramp (e.g., ramp 402 of
As described above in connection with
In different embodiments, latch 406 may be configured to hold the ramp 402 in a retracted position, a non-retracted position, one or more intermediate positions between the retracted and non-retracted positions, one or more rotary positions if the ramp 402 is rotatable, etc. In general, latch 406 may be configured to hold the ramp 402 in any suitable position. It should be noted that different types of latches may be employed in different embodiments. For example, in an alternate embodiment, the latch may be a clamp-like system where, rather than catching on a hook/protrusion, the latch holds/clamps on to the ramp 402 in an engaged position, and may be released from the engaged position. The latching mechanism may be SMR-based, piezo-based or may use any other suitable form of actuation including magnetic actuation. If magnetic actuation is employed for the latch, magnetic shielding may be utilized to protect the head from magnetic fields from the magnetic actuation system.
The illustrations of the embodiments described herein are intended to provide a general understanding of the structure of the various embodiments. The illustrations are not intended to serve as a complete description of all of the elements and features of apparatus and systems that utilize the structures or methods described herein. Many other embodiments may be apparent to those of skill in the art upon reviewing the disclosure. Other embodiments may be utilized and derived from the disclosure, such that structural and logical substitutions and changes may be made without departing from the scope of the disclosure. Additionally, the illustrations are merely representational and may not be drawn to scale. Certain proportions within the illustrations may be exaggerated, while other proportions may be reduced. Accordingly, the disclosure and the figures are to be regarded as illustrative rather than restrictive.
One or more embodiments of the disclosure may be referred to herein, individually and/or collectively, by the term “invention” merely for convenience and without intending to limit the scope of this application to any particular invention or inventive concept. Moreover, although specific embodiments have been illustrated and described herein, it should be appreciated that any subsequent arrangement designed to achieve the same or similar purpose may be substituted for the specific embodiments shown. This disclosure is intended to cover any and all subsequent adaptations or variations of various embodiments. Combinations of the above embodiments, and other embodiments not specifically described herein, will be apparent to those of skill in the art upon reviewing the description.
The Abstract of the Disclosure is provided to comply with 37 C.F.R. § 1.72(b) and is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. In addition, in the foregoing Detailed Description, various features may be grouped together or described in a single embodiment for the purpose of streamlining the disclosure. This disclosure is not to be interpreted as reflecting an intention that the claimed embodiments employ more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter may be directed to less than all of the features of any of the disclosed embodiments.
The above-disclosed subject matter is to be considered illustrative, and not restrictive, and the appended claims are intended to cover all such modifications, enhancements, and other embodiments, which fall within the true spirit and scope of the present disclosure. Thus, to the maximum extent allowed by law, the scope of the present disclosure is to be determined by the broadest permissible interpretation of the following claims and their equivalents, and shall not be restricted or limited by the foregoing detailed description.
This application is a continuation-in-part of U.S. application Ser. No. 16/910,593, filed on Jun. 24, 2020, which published as U.S. publication number 2021/0407538 A1, on Dec. 30, 2021, the content of which is hereby incorporated by reference in its entirety.
Number | Name | Date | Kind |
---|---|---|---|
3311902 | Appleton | Mar 1967 | A |
3940794 | Griffiths et al. | Feb 1976 | A |
4164767 | Gyi et al. | Aug 1979 | A |
4208685 | Matla et al. | Jun 1980 | A |
4566087 | Kraft | Jan 1986 | A |
4703376 | Edwards et al. | Oct 1987 | A |
4742410 | Smith | May 1988 | A |
4839756 | Chew et al. | Jun 1989 | A |
4884261 | Dalziel | Nov 1989 | A |
4888751 | Yoshimaru et al. | Dec 1989 | A |
5023737 | Yaeger | Jun 1991 | A |
5283705 | Iwabunchi | Feb 1994 | A |
5293282 | Squires et al. | Mar 1994 | A |
5307224 | Minase | Apr 1994 | A |
5341260 | Jabbari | Aug 1994 | A |
5343347 | Gilovich | Aug 1994 | A |
5347414 | Kano | Sep 1994 | A |
5459921 | Hudson et al. | Oct 1995 | A |
5467238 | Lee et al. | Nov 1995 | A |
5550695 | Matsumoto | Aug 1996 | A |
5764437 | Meyer et al. | Jun 1998 | A |
5831795 | Ma et al. | Nov 1998 | A |
5973886 | Khuu | Oct 1999 | A |
5973887 | Cameron | Oct 1999 | A |
5995332 | Patterson | Nov 1999 | A |
5999351 | Albrecht et al. | Dec 1999 | A |
6005747 | Gilovich | Dec 1999 | A |
6055134 | Boutaghou | Apr 2000 | A |
6067208 | Segar | May 2000 | A |
6081399 | Lee et al. | Jun 2000 | A |
6091576 | Eckerd et al. | Jul 2000 | A |
6122130 | Boutaghou et al. | Sep 2000 | A |
6134076 | Boutaghou et al. | Oct 2000 | A |
6157520 | Mangold et al. | Dec 2000 | A |
6160686 | Albrecht et al. | Dec 2000 | A |
6201666 | Resh | Mar 2001 | B1 |
6275356 | Boutaghou et al. | Aug 2001 | B1 |
6278584 | Zhang et al. | Aug 2001 | B1 |
6404580 | Fioravanti | Jun 2002 | B1 |
6449129 | Macpherson et al. | Sep 2002 | B1 |
6452753 | Hiller et al. | Sep 2002 | B1 |
6473270 | McDonald et al. | Oct 2002 | B1 |
6480361 | Patterson | Nov 2002 | B1 |
6487050 | Liu | Nov 2002 | B1 |
6490135 | Sannino et al. | Dec 2002 | B1 |
6507460 | Fayeulle et al. | Jan 2003 | B2 |
6519115 | Yaeger | Feb 2003 | B1 |
6577473 | Macpherson et al. | Jun 2003 | B1 |
6597540 | Tsuda et al. | Jul 2003 | B2 |
6621651 | Ratliff et al. | Sep 2003 | B1 |
6650506 | Risse | Nov 2003 | B1 |
6693773 | Sassine | Feb 2004 | B1 |
6710964 | Rao et al. | Mar 2004 | B1 |
6775107 | Kasajima et al. | Aug 2004 | B2 |
6847504 | Bennett et al. | Jan 2005 | B1 |
6855282 | Fayeulle et al. | Feb 2005 | B2 |
6952319 | Weiehelt et al. | Oct 2005 | B2 |
6989965 | Mundt et al. | Jan 2006 | B2 |
7102842 | Howard | Sep 2006 | B1 |
7385781 | Craig et al. | Jun 2008 | B1 |
7548399 | Shin | Jun 2009 | B2 |
7672083 | Yu et al. | Mar 2010 | B1 |
7675712 | Liu et al. | Mar 2010 | B2 |
7733610 | Scura et al. | Jun 2010 | B2 |
7813078 | Gleason et al. | Oct 2010 | B1 |
7848057 | Shukla | Dec 2010 | B1 |
7986491 | Albrecht et al. | Jul 2011 | B2 |
8024853 | Rivera | Sep 2011 | B2 |
8035913 | Kim et al. | Oct 2011 | B2 |
8112580 | Bandic et al. | Feb 2012 | B2 |
8194345 | Kwon et al. | Jun 2012 | B2 |
8208215 | Molaro et al. | Jun 2012 | B2 |
8493690 | Ono et al. | Jul 2013 | B1 |
8824094 | Furlong et al. | Sep 2014 | B1 |
8873200 | Warn et al. | Oct 2014 | B2 |
8958172 | Hansen | Feb 2015 | B1 |
8958173 | Hirano et al. | Feb 2015 | B1 |
9025277 | Hirano | May 2015 | B1 |
9171560 | Davidson et al. | Oct 2015 | B1 |
9183862 | Shah et al. | Nov 2015 | B1 |
9218833 | Shah et al. | Dec 2015 | B1 |
9449649 | Rejae et al. | Sep 2016 | B1 |
9536552 | Chen et al. | Jan 2017 | B1 |
9552835 | Tamayo et al. | Jan 2017 | B1 |
9704521 | Shah et al. | Jul 2017 | B1 |
10269380 | Sun et al. | Apr 2019 | B1 |
10622012 | Tu et al. | Apr 2020 | B1 |
11308984 | Herdendorf et al. | Apr 2022 | B2 |
20050280945 | Duvall et al. | Dec 2005 | A1 |
20050286171 | Kim et al. | Dec 2005 | A1 |
20060002028 | Nayar et al. | Jan 2006 | A1 |
20060117558 | Koh et al. | Jun 2006 | A1 |
20060171078 | Kajitani | Aug 2006 | A1 |
20060256478 | Hayakawa | Nov 2006 | A1 |
20070008653 | Ohno et al. | Jan 2007 | A1 |
20070139810 | Kim et al. | Jun 2007 | A1 |
20080055773 | Nigam | Mar 2008 | A1 |
20090279199 | Zhang | Nov 2009 | A1 |
20100091408 | Albrecht et al. | Apr 2010 | A1 |
20100271733 | Kim | Oct 2010 | A1 |
20110038074 | Viskochil et al. | Feb 2011 | A1 |
20120002328 | Aoki et al. | Jan 2012 | A1 |
20120075750 | Chan et al. | Mar 2012 | A1 |
20140126084 | Nakamiya et al. | May 2014 | A1 |
20190333533 | Mendonsa et al. | Oct 2019 | A1 |
20200027477 | Garbarino | Jan 2020 | A1 |
20200027480 | Myers et al. | Jan 2020 | A1 |
Number | Date | Country |
---|---|---|
2020018854 | Jan 2020 | WO |
Entry |
---|
Prior Art Database Technical Disclosure, IP.com No. IPCOM000228512D, “Retracting Load/Unload Ramp”, https://ip.com/IPCOM/000228512, dated Jun. 14, 2013, 6 pages. |
Maplesoft Application Brief, “Optimal Control Design of a Voice Coil Head Actuator in a Hard Drive”, www.maplesoft.com/appsbriefs, dated 2008, 30 pages. |
World's first commercial Hard Drive—IBM 350 (RAMAC); https://www.youtube.com/watch?v=aTkL4FQL2FI; Nov. 27, 2016; 5 pages. |
U.S. Appl. No. 16/863,287, filed Apr. 30, 2020, 22 pages. |
Restriction Requirement for U.S. Appl. No. 15/946,859, dated May 19, 2020, 8 pages. |
Final Office Action for U.S. Appl. No. 15/965,097, dated Mar. 11, 2020, 8 pages. |
Notice of Allowance for U.S. Appl. No. 15/965,097, dated May 20, 2020, 6 pages. |
Non-Final Office Action for U.S. Appl. No. 15/965,097, dated Jul. 13, 2020, 6 pages. |
Application and Drawings for U.S. Appl. No. 16/805,174, dated Feb. 28, 2020, 40 pages. |
Non-Final Office Action for U.S. Appl. No. 15/965,097, dated Nov. 21, 2019, 7 pages. |
Non-Final Office Action for U.S. Appl. No. 15/965,097, dated Apr. 12, 2019, 7 pages. |
Non-Final Rejection for U.S. Appl. No. 16/805,174, dated Sep. 25, 2020, 7 pages. |
Notice of Allowance (PTOL-85) for U.S. Appl. No. 15/965,097, dated Sep. 22, 2020, 6 pages. |
Non-Final Rejection for U.S. Appl. No. 16/863,287, dated Dec. 23, 2020, 8 pages. |
Notice of Allowance and Fee(s) Due for U.S. Appl. No. 16/805,174, dated Jan. 11, 2021, 6 pages. |
USPTO-issued prosecution for U.S. Appl. No. 16/910,593, including: Notice of Allowance and Fee(s) Due (PTOL-85) and Examiner Interview Summary Record (PTOL-413) dated Dec. 20, 2021, 11 pages Examiner Interview Summary Record (PTOL-413) dated Nov. 3, 2021, 3 pages; Non-Final Rejection dated Sep. 16, 2021, 16 pages; Requirement for Restriction/Election dated Jun. 25, 2021, 7 pages. |
Number | Date | Country | |
---|---|---|---|
20220238137 A1 | Jul 2022 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 16910593 | Jun 2020 | US |
Child | 17721664 | US |