CROSS-REFERENCE TO RELATED APPLICATION

[0001] This application is a PCT International Application which claims priority to and the benefit of United States Patent Application No. 15/851,256 filed December 21, 2017. The entire disclosure of the above application is incorporated herein by reference.

FIELD

[0002] The present disclosure relates to computerized railroad track mapping methods and systems.

BACKGROUND

[0003] This section provides background information related to the present disclosure which is not necessarily prior art.

[0004] Trains are commonly used to transport passengers, goods, and/or materials on railroad tracks. The trains include one or more railroad cars for carrying the passengers, goods, and/or materials, and one or more locomotives for pushing and/or pulling the railroad cars. Sometimes one or more maps of the railroad tracks are generated by a land surveyor calculating three-dimensional points on the railroad tracks and the distances and angles between the points.

DRAWINGS

[0005] The drawings described herein are for illustrative purposes only of selected embodiments and not all possible implementations, and are not intended to limit the scope of the present disclosure.

[0006] Fig. 1 is a flow chart of a method for mapping one or more railroad tracks according to one example embodiment of the present disclosure.

[0007] Fig. 2 is a flow chart of a method for initially calibrating sensors on a train according to another example embodiment.

[0008] Fig. 3 is a flow chart of a method for collecting and storing data for generating and/or updating a map according to yet another example embodiment. [0009] Fig. 4 is a flow chart of a method for processing data received from one or more sensors according to another example embodiment.

[0010] Fig. 5 is a flow chart of a method for generating one or more alarms according to yet another example embodiment.

[0011] Fig. 6 is a diagram of a system including two trains and a remote computer server in communication with the trains via a wireless network according to another example embodiment.

[0012] Fig. 7 is a diagram of a generated map illustrating a track between two cities, elevation grades of the track and angles in the track according to yet another example embodiment.

[0013] Fig. 8 is a diagram of a generated map illustrating multiple tracks in a switchyard and elevation grades of the tracks according to another example embodiment.

DETAILED DESCRIPTION

[0014] Example embodiments will now be described more fully with reference to the accompanying drawings.

[0015] As recognized by the subject inventor, the industrial Internet of Things (IIoT) is rapidly expanding through the railroad industry. For example, trains including their locomotives are commonly equipped with various sensors and wireless connectivity points to allow for this growing automation trend. As further explained below, data may be collected from these various sensors and used to generate and/or update maps including rail environments and/or track conditions. This mapping of the rail environments and track conditions may ensure passenger, cargo, bystander, etc. safety.

[0016] Additionally, the collected sensor data may be used to detect track malfunctions (e.g., wear, degradation, catastrophic failure, etc.) in particular locations that may not otherwise be detectable. For example, as more trains travel over the same railroad track, that track may begin to sink into the ground over time due to the weight of the trains. This malfunction may be detected by the collected sensor data and reported if desired, as further explained below.

[0017] Further, the generated maps, collected data, etc. may be used by an automated control in a locomotive for controlling braking, acceleration, etc. and/or to improve map accuracy as compared to conventional systems. For instance, the collected sensor data may provide backup and/or verification data to cross check track profile maps used in existing automated systems.

[0018] For example, a computer-implemented method of mapping one or more railroad tracks in a defined area according to one example embodiment of the present disclosure is illustrated in Fig. 1 and indicated generally by reference number 100. As shown in Fig. 1, the method 100 includes collecting data from one or more sensors onboard (e.g., inside, etc.) at least one train at a plurality of different locations in a defined area in block 102, and generating a map of the one or more tracks based on the data collected from the one or more sensors at the plurality of different locations in the defined area in block 104.

[0019] The data may be collected from sensors in or onboard a single train, and the maps may be generated based on that data. In other example embodiments, data may be collected from sensors in or onboard multiple trains at different locations in the defined area, and the maps may be generated based on that data. As further explained below, data may be collected from two trains (e.g., locomotives), five trains, 100 trains, 1,000 trains, and/or any other suitable number of trains.

[0020] In some embodiments, multiple datasets may be collected from a single train traveling over the same route on multiple occasions. If desired, the datasets may be compared to each other to ensure the data is valid. In other examples, multiple datasets may be collected from different trains as explained above. In such examples, the datasets from the different trains traveling over the same route may be compared to each other to ensure the data is valid. In either case, if the data is valid, the maps may be generated (and/or updated) based on the valid data and location data from the train(s). In some examples, data from the multiple datasets may be averaged together and then the maps may be generated (and/or updated) based on the averaged data and location data from the train(s).

[0021] Once generated and/or updated, the maps may be used to control one or more trains. For example, control units in or onboard the trains may store the maps for automated control, an engineer may use the maps when controlling a train, etc. [0022] In some examples, the comparison may indicate the data is not validated (e.g., invalid data). In such examples, the sensors may be calibrated (and/or recalibrated), as further explained below. In other examples, an alarm may be generated when a comparison between the datasets indicates a variation greater than a defined threshold as further explained below. For example, if the variation in a new dataset (and/or subsequent collected datasets) is larger than a defined threshold, an alarm indicating track damage, inspection required, etc. may be generated. As further explained below, this alarm may be sent to appropriate personnel (e.g., via text messaging, emails, push alerts, etc.), main control boards, etc. In other examples, the sensors may be calibrated (and/or recalibrated) if the data is invalid.

[0023] The defined area in which data is collected may include one or more railways between two points. For example, the defined area may include a specific line between two cities, two railroad stops, two railroad crossings, etc. In other embodiments, the defined area may include one or more railways in a switchyard (e.g., railroad yard) where railroad cars are stored, loaded and switched to different tracks with one or more locomotives. The sensor data may be collected while the trains are moving and/or stationary in the defined area.

[0024] The one or more sensors onboard the trains may be calibrated before collecting data. This initial calibration process may be performed by a computer server (broadly, a device) in communication with the trains and/or by a control unit on the trains. For example, Fig. 2 illustrates an initial calibration process 200 including multiple steps for calibrating sensors on a train. As shown in Fig. 2, the process 200 includes determining whether all of the sensors on the train are reporting (e.g., communicating with the computer server remote from the train, the train’s control unit, etc.) in block 202. If so, the computer server and/or train’s control unit determines if a global navigation satellite system (GNSS) on the train is reporting a fix in block 204. For example, the computer server and/or train’s control unit determines whether the train’s GNSS is attempting to obtain more precise location data, or if the location data is accurate enough to report (e.g., within a precision threshold). For instance, GNSS data may include an indication in a message (e.g., a serial message) that describes the quality of received satellite signals. In other words, this indication describes the precision of the received positional data. Different levels of precision could be required depending on the situation. In some examples, if National Marine Electronics Association (NMEA) standards are employed, the Horizontal Dilution of Precision (HDOP) field, the‘Fix Quality’ field, and/or the‘Number of Satellites Being Tracked’ field may be used.

[0025] If the train’s GNSS is attempting to obtain more precise location data, the process 200 returns to block 202 and determines whether all of the sensors are reporting. However, if the location data from the GNSS is within the precision threshold, the computer server and/or train’s control unit determines whether a remote database in (or in communication with) the computer server has a link available for communication in block 206. If not, the process 200 may return to determining whether the sensor(s) are reporting in block 202, or determining whether the train’s GNSS is reporting a fix in block 204.

[0026] If a link is available for communication, the process 200 then determines whether a remote database flag for a known location set is available in block 208. For example, the database may include a dataset from another or the same train at the same location (but at a different time). In such examples, the previously stored data may be used to calibrate the train’s sensors. As such, if the remote database flag for the particular location set is available, the control unit may request this data from the computer server to calibrate the train’s sensors in block 210. In other examples, the computer server may send this calibration data to the train’s sensors without a request. If, however, the remote database flag for the particular location set is not available, the process 200 may return to determining whether the sensor(s) are reporting in block 202, determining whether the train’s GNSS is reporting a fix in block 204, or determining whether a remote database in (or in communication with) the computer server has a link available for communication in block 206.

[0027] In some examples, the datasets received from the sensor(s) from one or more trains may be used to generate a new map of a track layout of the defined area, and/or update an existing map of the defined area. For example, Fig. 3 illustrates a process 300 including multiple steps for collecting and storing data for generating and/or updating a map. As shown in Fig. 3, the process 300 includes determining whether a new dataset has been received by the computer server in block 302. If so, the computer server determines whether the new dataset from a particular train passes a validity check in block 304.

[0028] For example, one or more data points from the new dataset may be compared to other data points in the new dataset. In other words, the computer server may collect data from the train multiple times over a period of time, and then validate this data in the new dataset by comparing the data from the train over the period of time. For instance, two or more consecutive data points may be compared to each other to ensure the data points are valid. If one data point represents a 3% grade on a first point on the track and the next data point represents a 3.1% grade at a second point near the first point on the track, the dataset may be deemed valid. However, if one data point represents a 3% grade on the first point on the track and the next data point represents a 97% grade at the second point near the first point on the track, the dataset may be deemed invalid. Additionally and/or alternatively, and as explained above, the new dataset from the train may be compared to other datasets obtained from the same train on the same rail path at different times and/or other datasets obtained from other trains on the same rail path at different times to determine if the new dataset is valid.

[0029] If the data from the new dataset is deemed invalid in block 304, the computer server returns to determining whether a new dataset has been received in block 302. If, however, the data from the new dataset is deemed valid in block 304, the computer server determines whether the new dataset includes data from a previously reported location in block 306. If no other data was reported for that particular location, the dataset is saved in the database and a new track map may be generated based on the new dataset in block 310.

[0030] If, however, the new dataset corresponds to a previously reported location, the data (e.g., location data, grade data, etc.) from the new dataset is added (e.g., recorded) to the database in block 312. In such examples, the new data and the existing data may be averaged. In some examples, the new data and the existing data may be averaged with the difference between new data and old data trended for further analysis if desired. The averaged the new data and the existing data may then be used to update an existing map (if necessary) as explained herein. As such, the computer server may generate a map based on data collected in one period of time, and then update the existing map based on the new data collected after the initial map was generated (e.g., in a later period of time).

[0031] Fig. 4 illustrates a process 400 including multiple steps for processing data received from the sensors. As shown in Fig. 4, the process 400 includes sorting data stored in the computer server’s database by location (e.g., the GNSS location) since the last averaging of this data in block 402, and then processing the sorted data (e.g., a next record) in block 404. The computer server then determines whether the data in the new dataset collected from the sensors is within a defined tolerance of a stored track profile corresponding to the same location in block 406. For example, the defined tolerance may be determined based on existing datasets from the same track and location (e.g., benchmark data). This defined tolerance may be continually updated based on received data. In some examples, different tolerances may be employed at different steps in the mapping process. For example, an initial collection of data may have a wider tolerance than a later collection of data. This wider tolerance allows the server to capture and use a larger amount data in the early stages of the track data average. Later collection(s) of data may have a decreased tolerance so that a change in data and/or trends in detected changes would be noticeable.

[0032] If the data is within the defined tolerance, the data from the dataset is recorded (e.g., stored) in the database by a train identification number (e.g., train 1234) in block 408. During this time, the track profile in the database for generating and/or updating the map is not changed.

[0033] If, however, the data is not within the defined tolerance in block 406, the computer server determines whether the variance from the stored track profile is deemed excessive in block 410. For example, the new dataset may be compared to other existing datasets from the same track and location (e.g., benchmark data) to determine whether a variation is greater than a defined threshold to determine if the variance is excessive. Similar to the defined tolerance explained above, the variance may be continually updated based on received data. In some examples, one variance may be employed at one point in the mapping process, and another variance may be employed at another point in the mapping process. For example, an initial collection of data may have a wider variance than a later collection of data. This wider variance allows the server to capture and use a larger amount data in the early stages of the track data average. Later collection(s) of data may have a decreased variance so that a change in data and/or trends in detected changes would be noticeable.

[0034] If the variance is not deemed excessive (but is outside the defined tolerance in block 406), the computer server may process a sensor calibration update for the sensors of the particular train in block 414. This sensor calibration update may be sent to the particular train to recalibrate its sensors. If the variance is deemed excessive in block 410, the computer server may flag the train’s sensors and track location for comparison to data from other trains of the same track and location in block 412.

[0035] In some example embodiments, when data variance from one or more trains is excessive, an alarm may be generated. For example, Fig. 5 illustrates a process 500 including multiple steps for processing flags ( e.g . the flags set in the process 400 of Fig. 4). As shown in Fig. 5, the process 500 begins by detecting whether data from other trains had an excessive variable at a particular location in block 502. For instance, once the flag is set in block 412 of Fig. 4, the computer server may continue collecting data on other (and/or the same) train on the same track and at the same location. If the variance in the collected data from the other trains and/or the same train is also excessive (e.g., as determined in block 410 of Fig. 4), an alarm may be generated to report track damage in block 504. This alarm may indicate the severity of the damage, the location of the damage, action items required, etc. The alarm may be sent to appropriate personnel (e.g., via text messaging, emails, push alerts, etc.), main control boards, etc.

[0036] If the variance in the collected data from the other trains and/or the same train is not excessive, the computer server may continue to monitor new datasets corresponding to the location in question. Specifically, the computer server may detect whether the same train or other trains report datasets having an excessive variance at this same location in block 506. If the computer server does not detect another dataset having an excessive variance at this same location, the new dataset flagged as excessive in block 412 of Fig. 4 may be considered an erroneous read in block 510 of Fig. 5. The computer server may continue to monitor datasets at this same location continually, for a defined period of time, for a defined number of datasets, etc. If the new dataset is considered erroneous, the dataset may be disregarded. [0037] If, however, the computer server does detect another dataset having an excessive variance at the same location in block 506, the computer server may determine whether the particular train provides similar excessive variances at other locations on the track in block 508. In some specific embodiments, the computer server may determine whether the particular train provides data of similar directional excessive variances at other locations (e.g., in the x-direction, y-direction, and/or z-direction). This may indicate a calibration issue with sensors on that particular train.

[0038] If so, the computer server may process a sensor calibration update for the sensors of the particular train in block 512 (and as explained above relative to block 414 of Fig. 4). If the computer server determines the train does not provide similar excessive variances at other locations on the track in block 508, the computer server may store the data and a warning for potential sensor issues relating to this particular train in block 514.

[0039] Any one or more of the methods disclosed herein may be implemented by one or more computer servers. For example, the computer servers may include memory for storing computer-readable instructions for performing the methods described above and one or more processors for executing the computer-readable instructions. Additionally and/or alternatively, the computer-readable instructions for performing the methods may be stored on a non-transitory computer-readable medium including, for example, disks, SD cards, DVD, CD-ROMs, ROMs, RAMs, EPROMs, EEPROMs, DRAMs, VRAMs, flash memory devices, or any other suitable medium for storing instructions. In some examples, the memory and/or the non-transitory computer-readable medium may include one or more databases to store data collected from the sensors as explained herein.

[0040] For example, Fig. 6 illustrates a system 600 including two trains (e.g., locomotives) 602, 604 having sensors 606, 608, 610, 612 and a computer server 616 remote from the trains 602, 604. The computer server 616 communicates (represented by dashed lines) with the trains 602, 604 via a network 622. Although the system 600 includes two trains 602, 604, it should be apparent to those skilled in the art that more or less trains may be in communication with the computer server 616.

[0041] The network 622 is a wireless network over which the computer server 616 wirelessly communicates with the train 602, 604. The wireless network 622 may be a Wi- Fi network, a cellular based network, Bluetooth, and/or any other suitable wireless network depending on, for example, the distance between the computer server 616 and the trains 602, 604. In some examples, wireless repeaters and/or extenders may be employed if necessary. This wireless capability allows for greater flexibility in placement of the computer server 616. For example, the computer server 616 may be located in a switchyard and/or at another suitable location outside the switchyard. Additionally and/or alternatively, the computer server 616 may communicate with the network 622 (and/or another network) with a wired connection.

[0042] The computer server 616 includes one or more databases 620 for storing data from the sensors 606, 608, 610, 612 and one or more processors 618 for implementing instructions for performing the methods described above. For example, the computer server 616 may include instructions to cause the server to collect data from the sensors 606, 608, 610, 612 of the trains 602, 604 at different locations in a defined area, and generate maps of tracks in the defined area based on the data collected from the sensors 606, 608, 610, 612, as explained above.

[0043] In the particular example of Fig. 6, the databases 620 are a part of the computer server 616. For example, the computer server’s memory (not shown) may include the databases 620. In other examples, the databases 620 and/or one or more other databases may be external to the computer server 616.

[0044] As shown, the trains 602, 604 are located on train tracks. The trains 602, 604 may be stationary and/or moving when the computer server 616 collects data from the sensors 606, 608, 610, 612. For example, the train 602 and/or the train 604 may be moving and/or stationary in a switchyard. Additionally and/or alternatively, one or both trains 602, 604 may be moving and/or stationary on a particular railroad track outside the switchyard. For example, one or both trains 602, 604 may be traveling between two cities, two switchyards, etc.

[0045] In the particular example of Fig. 6, the train 602 includes the sensor 606, and the train 604 includes the sensors 608, 610, 612. The sensors 606, 608, 610, 612 may be located at any suitable location onboard ( e.g ., inside, outside, on, in, etc.) the trains 602, 604 including, for example, inside a cab of the trains 602, 604, on an exterior surface of the trains 602, 604, etc. In some embodiments, the sensors 606, 608, 610, 612 may be located adjacent (and in communication with) a control unit or within a control unit of one or both trains 602, 604. For example, and as shown in Fig. 6, the train 604 includes a control unit 614 including the sensors 608, 610, 612. In such examples, the control unit 614 may collect data from the sensors 608, 610, 612, and then pass that data along to the computer server 616 via the wireless network 622.

[0046] In some embodiments, the control unit 614 may filter data collected from the sensors 608, 610, 612. For example, the control unit 614 may compare data from each of the sensors 608, 610, 612 over a period of time. For instance, two or more consecutive data points may be compared to each other from the sensor 608 to ensure the data points are valid as explained above. If the data is deemed invalid, the control unit 614 may filter that data ( e.g ., prevent the data from passing to the computer server 616). If the data is deemed valid, the control unit 614 may allow the data to pass to the computer server 616.

[0047] In other examples, the sensors may directly communicate with the computer server 616. For example, and as shown in Fig. 6, the sensor 606 on the train 602 may directly communicate with the computer server 616 via the wireless network 622.

[0048] The sensor data from the sensors 606, 608, 610, 612 may be provided to the computer server 616 continuously, periodically, randomly, and/or in response to a defined event. For example, the sensor 606 and/or the control unit 614 may push sensor data to the computer server 616 periodically (e.g., twice a day, at predetermined time intervals, etc.), the computer server 616 may pull data from the control unit 614 and/or the sensor 606 continuously, etc.

[0049] The sensors 606, 608, 610, 612 (and/or any other sensor disclosed herein) may be any suitable sensor. In some examples, each of the sensors 606, 608, 610, 612 may be or at least part of a kinematic sensor for sensing a rate of change (e.g., acceleration) in a three dimensional space. For example, the kinematic sensor may assist in determining a change in grade along a track based on gravity. In the specific example of Fig. 6, the sensors 608, 610, 612 on the train 604 represent a magnetometer, an accelerometer, and a gyroscope, respectively, of a kinematic sensor.

[0050] As explained above, one or more maps (e.g., virtual maps) may be generated and/or updated based on the collected data from the sensors 606, 608, 610, 612. For example, the maps may be created and/or updated based on kinematic sensor data and GNSS data provided by the trains 602, 604. As such, the computer server 616 may determine particular track layouts, elevation grades, severity of curves, etc. at particular points along a track based on the kinematic sensor data and the GNSS data.

[0051] Figs. 7 and 8 illustrate example maps 700, 800, respectively. As shown in Fig. 7, the map 700 includes a track layout 702 between two cities (City 1 and City 2), a line 704 representing elevation grades along a portion of the track, and a legend 706 indicating the severity of the curves (curve A and curve B) in the track. By way of example, the grade of the track is substantially constant near City 1, increases substantially linearly, is substantially constant at about the midpoint between City 1 and City 2, decreases substantially linearly, and is substantially constant near City 2. As shown in Fig. 7, curve A is about 87.3° and curve B is about 89.7°.

[0052] The map 800 of Fig. 8 includes a track layout 802 having multiple tracks inside a switchyard, and lines 804 representing elevation grades along different portions of the track. Specifically, the lines 804 represent the horizontal portions of the track shown in Fig. 8. For example, the top grade line represents the top most horizontal portion of the track, the bottom grade line represents the bottom most horizontal portion of the track, and the two middle grade lines represent the middle horizontal portions of the track.

[0053] In an exemplary embodiment, a system generally includes a non-transitory computer-readable storage media including computer-executable instructions for mapping one or more railroad tracks in a defined area, which when executed by at least one processor, cause the at least one processor to: collect data from one or more sensors onboard at least one train at a plurality of different locations in the defined area; and generate a map of the one or more tracks based on the data collected from the one or more sensors at the plurality of different locations in the defined area.

[0054] In an exemplary embodiment, one or more devices onboard a train (e.g., a locomotive) are configured to be operable for sensing track layout and conditions through the use of sensors such as redundant kinematic sensing arrays). Track data may be recorded along with corresponding positioning data from a global navigation satellite system and/or from other methods or means. This data may be collected at a remote location. At the remote location, data may also be collected from more than one of such systems. A map may be created from the collected data that defines track layout, grade, and other pertinent data points. Through the comparison of multiple sensor reads over multiple systems, a model may be built of the track profile. Additionally, a feedback loop may be created to detect system sensor deviation from the average values in order to compensate for minor differences in the sensor mounting, e.g., device calibration. The data may be used for various reasons, such as one or more of the following: preparation for locomotive automation systems that require detailed track profile information, backup/verification data to cross check provided track profile maps used in existing automation systems, detection of locations of wear or degradation in the roadbed, and/or detection of a catastrophic failure of track or roadbed.

[0055] Example embodiments are provided so that this disclosure will be thorough, and will fully convey the scope to those who are skilled in the art. Numerous specific details are set forth such as examples of specific components, devices, and methods, to provide a thorough understanding of embodiments of the present disclosure. It will be apparent to those skilled in the art that specific details need not be employed, that example embodiments may be embodied in many different forms and that neither should be construed to limit the scope of the disclosure. In some example embodiments, well- known processes, well-known device structures, and well-known technologies are not described in detail.

[0056] It should be appreciated that one or more aspects of the present disclosure transform a general-purpose computing device into a special-purpose computing device when configured to perform the functions, methods, and/or processes described herein. None of the elements recited in the claims are intended to be a means-plus-function element within the meaning of 35 U.S.C. § 112(f) unless an element is expressly recited using the phrase“means for,” or in the case of a method claim using the phrases “operation for” or“step for.”

[0057] The terminology used herein is for the purpose of describing particular example embodiments only and is not intended to be limiting. As used herein, the singular forms "a,” "an," and "the" may be intended to include the plural forms as well, unless the context clearly indicates otherwise. The terms "comprises," "comprising," “including,” and“having,” are inclusive and therefore 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, elements, components, and/or groups thereof. The method steps, processes, and operations described herein are not to be construed as necessarily requiring their performance in the particular order discussed or illustrated, unless specifically identified as an order of performance. It is also to be understood that additional or alternative steps may be employed.

[0058] When an element or layer is referred to as being "on," “engaged to,” "connected to," or "coupled to" another element or layer, it may be directly on, engaged, connected or coupled to the other element or layer, or intervening elements or layers may be present. In contrast, when an element is referred to as being "directly on,"“directly engaged to,” "directly connected to," or "directly coupled to" another element or layer, there may be no intervening elements or layers present. Other words used to describe the relationship between elements should be interpreted in a like fashion (e.g.,“between” versus“directly between,”“adjacent” versus“directly adjacent,” etc.). As used herein, the term "and/or" includes any and all combinations of one or more of the associated listed items.

[0059] Although the terms first, second, third, etc. may be used herein to describe various elements, components, regions, layers and/or sections, these elements, components, regions, layers and/or sections should not be limited by these terms. These terms may be only used to distinguish one element, component, region, layer or section from another region, layer or section. Terms such as “first,” “second,” and other numerical terms when used herein do not imply a sequence or order unless clearly indicated by the context. Thus, a first element, component, region, layer or section discussed below could be termed a second element, component, region, layer or section without departing from the teachings of the example embodiments.

[0060] Spatially relative terms, such as “inner,” “outer,” "beneath," "below," "lower," "above," "upper," and the like, may be used herein for ease of description to describe one element or feature's relationship to another element(s) or feature(s) as illustrated in the figures. Spatially relative terms may be intended to encompass different orientations of the device in use or operation in addition to the orientation depicted in the figures. For example, if the device in the figures is turned over, elements described as "below" or "beneath" other elements or features would then be oriented "above" the other elements or features. Thus, the example term "below" can encompass both an orientation of above and below. The device may be otherwise oriented (rotated 90 degrees or at other orientations) and the spatially relative descriptors used herein interpreted accordingly.

[0061] The foregoing description of the embodiments has been provided for purposes of illustration and description. It is not intended to be exhaustive or to limit the disclosure. Individual elements or features of a particular embodiment are generally not limited to that particular embodiment, but, where applicable, are interchangeable and can be used in a selected embodiment, even if not specifically shown or described. The same may also be varied in many ways. Such variations are not to be regarded as a departure from the disclosure, and all such modifications are intended to be included within the scope of the disclosure.