The present disclosure relates to marine propulsion systems for use on marine vessels, and more specifically to systems and methods for setting an engine speed of an internal combustion engine of a marine propulsion device in a marine propulsion system.
Each of the below U.S. Patents and Patent Applications are hereby incorporated by reference herein in their entirety.
U.S. Pat. Nos. 8,762,022 and 9,156,536 disclose systems and methods for efficiently changing controlled engine speed of a marine internal combustion engine in a marine propulsion system for propelling a marine vessel. The system responds to the operator changing the operator-selected engine speed, from a first-selected engine speed to a second-selected engine speed, by predicting throttle position needed to provide the second-selected engine speed, and providing a feed forward signal moving the throttle to the predicted throttle position, without waiting for a slower responding PID controller and/or overshoot thereof, and concomitant instability or oscillation, and then uses the engine speed control system including any PID controller to maintain engine speed at the second-selected engine speed.
Unpublished U.S. patent application Ser. No. 14/570,760, filed Dec. 15, 2014, discloses a method for controlling a position of an electronic throttle valve of an internal combustion engine. The method includes determining a desired throttle valve position; determining a first feed forward signal based on a rate of change between a previous throttle valve position and the desired throttle valve position; and determining a second feed forward signal based on a comparison of the desired throttle valve position to a limp home position of the throttle valve, in which the throttle valve is biased open by a spring. A summation of the first and second feed forward signals is used to actuate the throttle valve. After the throttle valve has been actuated according to the first and second feed forward signals, the position of the throttle valve is controlled with a feedback controller to obtain the desired throttle valve position.
Unpublished U.S. patent application Ser. No. 14/573,202, filed Dec. 17, 2014, discloses a method for setting an engine speed of an internal combustion engine in a marine propulsion system to an operator-selected engine speed. The method includes predicting a position of a throttle valve of the engine that is needed to provide the operator-selected engine speed, and determining a feed forward signal that will move the throttle valve to the predicted position. After moving the throttle valve to the predicted position, the method next includes controlling the engine speed with a feedback controller so as to obtain the operator-selected engine speed. The feed forward signal is determined based on at least one of the following criteria: an operator-selected control mode of the marine propulsion system and an external operating condition of the marine propulsion system. A system for setting the engine speed to the operator-selected engine speed is also described.
Unpublished U.S. patent application Ser. No. 14/610,377, filed Jan. 30, 2015, discloses a method for setting an engine speed of an internal combustion engine in a marine propulsion device of a marine propulsion system to an engine speed setpoint. The method includes determining the engine speed setpoint based on an operator demand and predicting a position of a throttle valve that is needed to achieve the engine speed setpoint. The method also includes determining a feed forward signal that will move the throttle valve to the predicted position, and after moving the throttle valve to the predicted position, adjusting the engine speed with a feedback controller so as to obtain the engine speed setpoint. An operating state of the marine propulsion system is also determined. Depending on the operating state, the method may include determining limits on an authority of the feedback controller to adjust the engine speed and/or determining whether the operator demand should be modified prior to determining the engine speed setpoint.
This Summary is provided to introduce a selection of concepts that are further described below in the Detailed Description. This Summary is not intended to identify key or essential features of the claimed subject matter, nor is it intended to be used as an aid in limiting the scope of the claimed subject matter.
One example of the present disclosure is of a method for temporarily elevating a speed of an engine in a marine propulsion system in response to a decrease in helm demand. The method includes receiving, with a controller, a command to decrease the helm demand from a first helm demand to a second helm demand and comparing a demand difference between the second helm demand and the first helm demand to a threshold demand delta. In response to the demand difference exceeding the threshold demand delta, the method includes tabulating a time since the demand difference exceeded the threshold demand delta and determining an engine speed offset based upon the second helm demand and the time. The controller determines a non-elevated engine speed setpoint corresponding to the second helm demand and calculates an elevated engine speed setpoint based on the non-elevated engine speed setpoint and the engine speed offset. The method includes decreasing the engine speed to the elevated engine speed setpoint.
According to another example of the present disclosure, a method for temporarily elevating a speed of an engine in a marine propulsion system in response to a decrease in helm demand is disclosed. The method includes receiving, with a controller, a command to decrease the helm demand from a first helm demand to a second helm demand and comparing a demand difference between the second helm demand and the first helm demand to a threshold demand delta. The controller determines if the marine propulsion system is operating in a given mode. In response to the demand difference exceeding the threshold demand delta and the marine propulsion system operating in the given mode, the controller then tabulates a time since the demand difference exceeded the threshold demand delta. The controller determines an engine speed offset based upon the second helm demand and the time and determines a non-elevated engine speed setpoint corresponding to the second helm demand. The method includes calculating an elevated engine speed setpoint based on the non-elevated engine speed setpoint and the engine speed offset and decreasing the engine speed to the elevated engine speed setpoint.
Another method for temporarily elevating a speed of an engine in a marine propulsion system in response to a decrease in helm demand is disclosed as a further example. A controller receives a command to decrease the helm demand from a first helm demand to a second helm demand and compares a demand difference between the second helm demand and the first helm demand to a threshold demand delta. In response to the demand difference exceeding the threshold demand delta, the method includes tabulating a time since the demand difference exceeded the threshold demand delta and determining an engine speed offset based upon the second helm demand and the time. The method also includes determining a non-elevated engine speed setpoint corresponding to the second helm demand. The controller calculates an elevated engine speed setpoint based on the non-elevated engine speed setpoint and the engine speed offset and decreases the engine speed to the elevated engine speed setpoint. The method includes subsequently determining if the helm demand remains at the second helm demand and, as long as the helm demand remains at the second helm demand, filtering the engine speed offset and re-calculating the elevated engine speed setpoint based on the non-elevated engine speed setpoint and the filtered engine speed offset. In response to a command to increase the helm demand to a subsequent helm demand, the controller determines when to transition from setting the engine speed to the elevated engine speed setpoint to setting the engine speed to the non-elevated engine speed setpoint based on whether the second helm demand is above or below an idle threshold.
The present disclosure is described with reference to the following Figures. The same numbers are used throughout the Figures to reference like features and like components.
In the present description, certain terms have been used for brevity, clarity, and understanding. No unnecessary limitations are to be inferred therefrom beyond the requirement of the prior art because such terms are used for descriptive purposes only and are intended to be broadly construed. Each of the examples of systems and methods provided in the figures and in the following description can be implemented separately, or in conjunction with one another and/or with other systems and methods.
A controller such as an electronic control unit (ECU) 22 receives the helm demand from the input device 20 and includes appropriate read only memory (ROM) 24 and random access memory (RAM) 26, computer code, and a processor for determining an engine speed setpoint based on the helm demand and processing the engine speed setpoint with a feedback controller 28, such as a proportional integral derivative (PID) controller or a PI controller. By way of example, the helm demand as determined by a transducer in the base of a throttle lever can be sent to a lookup table to look up an engine speed setpoint. The difference between the engine speed setpoint and the actual engine speed is then provided to feedback controller 28, which outputs a control signal to input-output (I/O) interface 30, which in turn supplies a control signal to internal combustion engine 12, including throttle valve 32, which controls engine speed according to throttle position. By way of control with the feedback controller 28, the ECU 22 maintains engine speed at the operator-selected engine speed.
In response to the operator changing the helm demand/operator-selected engine speed at input device 20 from a first helm demand/first-selected engine speed to a second helm demand/second-selected engine speed, the ECU 22 makes a prediction as to the position of the throttle valve 32 needed to provide the second-selected engine speed. For example, the engine speed setpoint can be provided to another lookup table to look up a feed forward signal. The ECU 22 then provides the feed forward signal at 34 to the I/O interface 30, which feed forward signal 34 bypasses feedback controller 28 and moves throttle valve 32 to the predicted throttle valve position. For example, the ECU 22 outputs the feed forward signal 34 to a throttle valve actuator, such as a motor geared to the throttle valve 32.
After movement of the throttle valve 32 to the predicted throttle valve position, the feedback controller 28 corrects the position of the throttle valve 32 as needed so as to obtain and maintain the engine speed at the second operator-selected engine speed. The throttle valve 32 is therefore moved to the predicted throttle position in response to the feed forward signal 34, without waiting for the input of the feedback controller 28 to move the throttle valve 32, thereby decreasing or eliminating overshoot. The system thereby enables reduction of amplification gain of the feedback controller 28 that would otherwise be needed to accommodate the change from the first-selected engine speed to the second-selected engine speed from input device 20, and instead accommodates such change by the predicted throttle position provided by the feed forward signal 34. Such reduced amplification gain provides enhanced stability of the feedback controller 28 and reduces oscillation of the system 10.
The ECU 22 may include a memory (ROM 24, RAM 26) and a programmable processor. As is conventional, the processor can be communicatively connected to a computer readable medium that includes volatile or nonvolatile memory upon which computer readable code is stored. The processor can access the computer readable code, and the computer readable medium upon executing the code carries out functions as described herein below. In other examples of the system 10, more than one controller is provided, rather than the single ECU 22 as shown herein. For example, a first controller could be provided in order to interpret signals sent from the helm of the marine vessel 14, and a second controller could be provided for the marine propulsion device 36. It should be noted that the lines shown in
Prior art systems have been used in discreet idle PID regions for shift stall abatement and other scenarios where a temporary elevation of engine idle speed versus vessel speed (real or inferred) is desired. Such prior art systems can apply an engine speed offset when traditional idle control is enabled. Adding an offset to the engine speed is important when the user chops the throttle from a first, relatively higher helm demand to a second, relatively lower helm demand. When a throttle chop occurs, it is assumed that the vessel operator will likely shift into reverse soon thereafter. In other words, it is assumed that a throttle chop is made in order to avoid an obstacle nearing the marine vessel. In such a “panic shift” situation, the engine speed would first drop from that associated with the first helm demand to that associated with the second helm demand (which is likely at idle or near idle), then would jump up to a relatively higher engine speed as the throttle lever is shifted through neutral into reverse. Dropping the engine speed down to idle or near-idle and then increasing it as the system is subsequently shifted into reverse will likely cause the engine to stall. Therefore, during such a panic shift, it is helpful to retard spark while keeping the throttle valve 32 relatively open, in order to maintain a volume of air in the intake plenum that is capable of handling an instantaneous load change from neutral to reverse gear. By maintaining the throttle valve 32 in a position that is more open than it would normally be, once the spark is in fact ignited, there will be a higher torque available from the engine 12 for operation in reverse gear. Commanding an artificially high engine speed when in idle or near-idle (or even in higher engine speed ranges) after a significant throttle chop allows a larger volume of air to be maintained in the intake plenum.
Some prior art systems apply the offset versus a calculated (i.e., “pseudo”) boat speed. The offset is determined using a one dimensional table with the look up value being controlled by a calibrated first order filter. In other words, an input pseudo boat speed will return an output engine speed offset. The offset can be abruptly discontinued when the system exits idle. For example, referring to
Such prior art methods work well in systems where the command from the input device 20 translates directly to a position of the throttle valve 32, and engine speed is a result of throttle valve position, in contrast to the system described herein above with respect to
The method may next include adding the offset to an engine speed corresponding to the current helm demand in order to obtain an elevated engine speed setpoint, as shown at 912. Note that the “elevated” engine speed setpoint will be higher than what the current helm demand would otherwise dictate, but will still be lower than the engine speed associated with the original helm demand. As shown at 914, the method may then continue with filtering the offset. Meanwhile, the method may include determining whether the helm demand has increased, as shown at 916. As shown at 918, the method may include determining whether the engine speed corresponding to the new, increased helm demand is greater than or equal to the current elevated engine speed (which includes the offset), as shown at 918. The method may also include determining whether a timer has expired on the filter, as shown at 920. If either of 918 or 920 is true, the method may include discontinuing offsetting the engine speed setpoint, as shown at 922. If either of 916 or 920 is not true, the offset may be filtered until, for example, the engine speed reaches the base engine speed corresponding to the helm demand.
As noted at 902 in
In response to the demand difference exceeding the threshold demand Δ, the method further includes tabulating a time since the demand difference exceeded the threshold demand Δ, as shown at 506. The input of this tabulated time to the system is shown at 46 in
The method may next include, as shown at 512, calculating an elevated engine speed setpoint based on the non-elevated engine speed setpoint (from box 510) and the engine speed offset (from box 508). For example, the non-elevated engine speed setpoint 52 and the engine speed offset 50 may be added together at summer 86 to determine the elevated engine speed setpoint 72. The controller 22 may thereafter manipulate the throttle valve 32 in order to decrease the engine speed to the elevated engine speed set point, as shown at 514. Feedback control over the elevated engine speed setpoint can thereafter be carried out so long as the helm demand has not changed. For example, the method may include, as described herein above with respect to
Returning to the decision made at box 504 regarding whether the demand difference exceeds the threshold demand Δ, if the answer is no, the method may further include decreasing the engine speed to the non-elevated engine speed setpoint corresponding to the second helm demand, as shown at 518. (Recall that the non-elevated engine speed setpoint is determined at box 510, which can be performed before or simultaneously with steps 502 and/or 504.) In other words, if the threshold demand Δ has not been met, the engine speed offset strategy is not enabled, and the engine speed is set to that corresponding to the second helm demand from input device 20. In this instance, it is assumed that a panic shift is not occurring, because the decrease in helm demand is not great enough (i.e., has not met the threshold).
Alternatively, after determining that the demand difference does not exceed the threshold demand Δ (box 504), the method may further comprise determining if the marine propulsion system 10 is operating in a given mode, as shown at 520. If the marine propulsion system 10 is not operating in the given mode, the method may further include setting the engine speed to the non-elevated engine speed setpoint corresponding to the second helm demand, as shown at 518. Note that the determination made at 520 could alternatively be made before the determination made at 504, as either condition not being met is enough to prevent the engine speed offset strategy from continuing, resulting in the engine speed being decreased to the non-elevated engine speed setpoint. Requiring the system to be in a given mode before the engine speed offset strategy is enabled allows for discreet application of the strategy when desired and/or needed. This is important because advanced control modes, such as but not limited to joysticking mode, electronic anchoring mode, waypoint tracking mode, autopilot mode, docking mode, etc., can interact in both good and bad ways with the engine speed offset strategy. Whether a particular mode mentioned herein above is one of the given modes required for operation of the engine speed offset strategy can be programmed by the calibrator. Because some modes transition between helm demand sources while the particular mode is active, the method may include a latching strategy to latch a given mode for a specified period of time.
For example, the system may normally be in an unlatched state. The system may transition to a “non-wheel” mode anytime the helm demand is commanded by an input device 20 that is not the throttle lever. The system will latch the current non-wheel helm demand source if the mode thereafter transitions to “wheel” mode, in which the helm demand is commanded by the throttle lever. It will remain in the latched state until the mode transitions back to a non-wheel mode or until a predetermined threshold latch time is exceeded, whichever occurs first. Thus, the method includes decreasing the engine's speed to the non-elevated engine speed setpoint corresponding to the second helm demand (i.e., discontinuing the engine speed offset strategy) in response to the marine propulsion system 10 not operating in the given mode (in this example, non-wheel) for longer than a threshold latch time after having previously operated in the given mode. Note that the latching logic does not disable a currently-enabled instance of the engine speed offset strategy. This is purposeful, because as mentioned above, certain systems may change the source of helm demand with activation and deactivation of certain types of input devices. For example, activation and deactivation of a joystick would not necessarily result in the system transitioning out of the wheel mode. The output of the entire determination of whether the system is in a given mode that will allow or prevent activation of the engine speed offset strategy is shown in
If the method included decreasing the engine speed to the elevated engine speed setpoint as shown at 514, the method thereafter continues to box 516 of
If the second helm demand is below the idle threshold, as shown at 608, and the helm demand thereafter increases, the method further comprises continuing to recalculate the elevated engine speed setpoint based on the non-elevated engine speed setpoint and the filtered engine speed offset (see
If the second helm demand is above the idle threshold, as shown at 614, and the helm demand thereafter increases, the method further comprises continuing to recalculate the elevated engine speed setpoint based on the non-elevated engine speed setpoint and the filtered engine speed offset (see
In other words, boxes 608, 610, and 612 describe how if the helm demand transitions from off-idle to on-idle and back to off-idle, the engine speed offset strategy is discontinued upon exceeding the idle threshold when transitioning from on-idle to off-idle. In contrast, boxes 614, 616, and 612 describe how if the engine speed setpoint is decreased from a higher off-idle value to a lower off-idle value and then subsequently increased, the engine speed offset strategy will be discontinued once the subsequent engine speed setpoint is greater than the elevated engine speed setpoint (which includes the engine speed offset). This provides a strategy in which the engine speed offset is “melted out,” thus preventing the operator from noticing a speed discontinuity were the offset otherwise to be continued even after the subsequent engine speed exceeded the elevated engine speed.
How the system determines whether the offset needs to be melted out is described with respect to the logic diagram shown in
The filter 56 is triggered upon input of the demand Δ being met, as shown at 58, i.e., the helm demand has been decreased by greater than the threshold demand Δ. On line 60, the filter 56 outputs an engine speed setpoint that includes an offset, and represents what the second helm demand's engine speed setpoint plus the offset would be. Meanwhile, the engine speed setpoint corresponding to the second helm demand (the non-elevated engine speed setpoint, not including the offset) is output on line 62. The setpoint plus offset on line 60 is subtracted from the setpoint without offset on line 62 at a subtractor 64. If the output from subtractor 64 is negative, the output is saturated to 0 and the engine speed offset strategy remains engaged. In other words, the setpoint plus offset on line 60 is greater than the setpoint without offset on line 62, and there is no need yet to melt out the offset. On the other hand, if the output from subtractor 64 is positive, the output along line 66 is added to the subsequent helm demand setpoint, shown at 68, by summer 70. The summation is compared to the elevated engine speed setpoint, shown at 72, by comparator 74. If the output of summer 70 is greater than the elevated engine speed setpoint 72, this means that the operator is now requesting an engine speed that is greater than what the engine speed offset strategy is outputting. The engine speed offset strategy will therefore be disabled (melted out) and the system will transition back to utilizing the base operator-requested engine speed setpoint. If the output of summer 70 is less than the elevated engine speed setpoint 72, the engine speed offset strategy will continue.
Therefore, the method disclosed herein includes comparing the elevated engine speed setpoint on line 60 to the non-elevated engine speed setpoint on line 62 and, in response to the elevated engine speed setpoint (line 60) being greater than the non-elevated engine speed setpoint (line 62), continuing to re-calculate the elevated engine speed setpoint based on the non-elevated engine speed setpoint and the filtered engine speed offset and setting the engine speed to the elevated engine speed setpoint. In other words, the engine speed offset strategy remains enabled. The method further includes calculating a difference between the elevated engine speed setpoint (line 60) and the non-elevated engine speed setpoint (line 62), and in response to the elevated engine speed setpoint (line 60) being less than the non-elevated engine speed setpoint (line 62), adding the difference between the elevated and non-elevated engine speed setpoints (line 66) to the subsequent engine speed setpoint 68. The subsequent engine speed setpoint 68 plus the difference between the elevated and non-elevated engine speed setpoints (line 66) is then compared with the elevated engine speed setpoint 72. In response to the subsequent engine speed 68 plus the difference between the elevated and non-elevated engine speed setpoints (line 66) (see summer 70) being greater than the elevated engine speed setpoint 72 (see comparator 74), the method includes setting the engine speed to the subsequent engine speed setpoint. In other words, the offset has been melted out.
One example of the result of using the melt out strategy is shown in
Returning to
Any of the above-described requirements for entry into the engine speed offset strategy could be used alone or in conjunction with one another in different sets. In one example, in order to enter the engine speed offset strategy, the helm demand must decrease by greater than the threshold demand Δ, the gear state must be in-gear (i.e., in forward gear or reverse gear), and the marine vessel must be operating in a given mode. Additionally, the subsequent helm demand must not be greater than the elevated engine speed setpoint. Any of the above-described requirements for exit from the engine speed offset strategy could also be used alone or in conjunction with one another in different sets. For example, the filter time may have expired, the gear state may not be in-gear, or the subsequent helm demand may be greater than the elevated engine speed setpoint. Alternatively, the system may be operating in other than the given mode, and the latch time may have expired. The example of the present method provided herein above responds not only when throttle is chopped to idle or near-idle speeds, but also in higher speed ranges, in response to throttle chops greater than a given threshold. Other exemplary methods may require that the throttle is chopped to a threshold near-idle speed before the engine offset strategy will run.
In the above description, certain terms have been used for brevity, clarity, and understanding. No unnecessary limitations are to be inferred therefrom beyond the requirement of the prior art because such terms are used for descriptive purposes and are intended to be broadly construed. The different systems and method steps described herein may be used alone or in combination with one another and with other systems and methods. It is to be expected that various equivalents, alternatives and modifications are possible within the scope of the appended claims.
Number | Name | Date | Kind |
---|---|---|---|
4244336 | Fitzner | Jan 1981 | A |
4505169 | Ganoung | Mar 1985 | A |
4939660 | Newman et al. | Jul 1990 | A |
4986776 | Hensel et al. | Jan 1991 | A |
5080064 | Buslepp et al. | Jan 1992 | A |
5171172 | Heaton et al. | Dec 1992 | A |
5836851 | Ruman | Nov 1998 | A |
5848582 | Ehlers et al. | Dec 1998 | A |
6009371 | Kobayashi | Dec 1999 | A |
6152102 | Ruman | Nov 2000 | A |
6152104 | Vorih et al. | Nov 2000 | A |
6273771 | Buckley et al. | Aug 2001 | B1 |
6298824 | Suhre | Oct 2001 | B1 |
6425370 | Kramer | Jul 2002 | B1 |
6561016 | Suhre et al. | May 2003 | B1 |
6587765 | Graham et al. | Jul 2003 | B1 |
6701890 | Suhre et al. | Mar 2004 | B1 |
6757606 | Gonring | Jun 2004 | B1 |
7163000 | Ishida et al. | Jan 2007 | B2 |
7357120 | Kaji | Apr 2008 | B2 |
7422501 | Mizushima et al. | Sep 2008 | B2 |
7473149 | Mizokawa | Jan 2009 | B2 |
7549407 | Krupadanam | Jun 2009 | B2 |
7556547 | Kaji | Jul 2009 | B2 |
7917283 | Kado | Mar 2011 | B2 |
7976354 | Kubota et al. | Jul 2011 | B2 |
8340847 | Sako et al. | Dec 2012 | B2 |
8439800 | Bazan et al. | May 2013 | B1 |
8762022 | Arbuckle | Jun 2014 | B1 |
9039468 | Arbuckle et al. | May 2015 | B1 |
9145839 | Andrasko | Sep 2015 | B1 |
9156536 | Arbuckle et al. | Oct 2015 | B1 |
9248898 | Kirchhoff et al. | Feb 2016 | B1 |
9381989 | Poirier | Jul 2016 | B1 |
20020086593 | Shidara et al. | Jul 2002 | A1 |
20030000500 | Chatfield | Jan 2003 | A1 |
20030019414 | Borrett | Jan 2003 | A1 |
20030027468 | Into | Feb 2003 | A1 |
20030054704 | Kanno | Mar 2003 | A1 |
20030109184 | Kanno | Jun 2003 | A1 |
20030120360 | Yasui et al. | Jun 2003 | A1 |
20040069271 | Kanno et al. | Apr 2004 | A1 |
20040069272 | Allen et al. | Apr 2004 | A1 |
20050161022 | Kishi et al. | Jul 2005 | A1 |
20060047406 | Chatfield et al. | Mar 2006 | A1 |
20060118086 | Schwulst et al. | Jun 2006 | A1 |
20060166573 | Vetta et al. | Jul 2006 | A1 |
20080051979 | Yasui et al. | Feb 2008 | A1 |
20080124989 | Sturdy et al. | May 2008 | A1 |
20080280511 | Kado | Nov 2008 | A1 |
20090037073 | Jung et al. | Feb 2009 | A1 |
20100191397 | Nose et al. | Jul 2010 | A1 |
20110202258 | Fukushima et al. | Aug 2011 | A1 |
20110297462 | Grajkowski et al. | Dec 2011 | A1 |
20120191275 | Clever et al. | Jul 2012 | A1 |
20130035009 | Kuriyagawa et al. | Feb 2013 | A1 |
20130047957 | Breuer | Feb 2013 | A1 |
20140244130 | Filev | Aug 2014 | A1 |
20150000636 | Stockbridge | Jan 2015 | A1 |
Number | Date | Country |
---|---|---|
0068744 | Nov 2000 | WO |
Entry |
---|
Andrasko et al., “Systems and Methods for Controlling an Electronic Throttle Valve,” Unpublished U.S. Appl. No. 14/570,760, filed Dec. 15, 2014. |
Arbuckle et al., “Systems and Methods for Setting Engine Speed Using a Feed Forward Signal,” Unpublished U.S. Appl. No. 14/573,202, filed Dec. 17, 2014. |
Arbuckle et al., “Systems and Methods for Setting Engine Speed in a Marine Propulsion Device,” Unpublished U.S. Appl. No. 14/610,377, filed Jan. 30, 2015. |
Newport, Motion Control Coordinate System, www.newport.com, pp. 7-2 through 7-25, website visited Nov. 18, 2014. |