SYSTEMS AND METHOD FOR CHANGING THE SPEED OF A BELT DRIVE SYSTEM
The belt drive system addresses the challenge of detecting belt tension and adjusting operating speed by using a load sensor to automatically control gear shifts, enhancing system durability and reducing load-related issues.
Patent Information
- Application Number
- DE102024124694
- Authority / Receiving Office
- DE · DE
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-10-31
- Filing Date
- 2024-08-29
- Publication Date
- 2025-04-30
AI Technical Summary
Existing belt drive systems in agricultural machines lack efficient mechanisms for detecting belt tension and automatically adjusting the operating speed to match changing loads, leading to potential slipping, wear, and abrupt load changes.
A belt drive system equipped with a load sensor connected to a sheave on the tight side of the belt, which generates a signal indicative of belt tension, allowing for automatic control of gear shifts in the transmission to maintain optimal operating speed and reduce load-related issues.
The system effectively detects belt tension and adjusts the transmission gear shifts accordingly, reducing the risk of slipping, wear, and abrupt load changes, thereby improving the durability of the belt drive system and reducing driver discomfort.
Smart Images

Figure 00000000_0000_ABST
Abstract
Description
Area of Revelation
[0001] The present disclosure generally relates to belt drive systems. Background of the Revelation
[0002] Agricultural machinery, such as combine harvesters, contains belt drive systems used to transfer power from one rotating component to another. Power is transferred from one rotating component to another via an endless belt. The tension in the endless belt is selected to transmit power through one or more pulleys in the belt drive system without slippage of the endless belt. Fixed-speed belt drive systems are pulley-less, adjustable-speed belt drive systems that change the speed ratio of the endless belt based on a change in the speed of a drive pulley. Brief description of Revelation
[0003] One aspect of the present disclosure relates to a belt drive system operatively capable of detecting belt tension. The belt drive system may include a drive pulley operatively coupled to a drive device for rotating the drive pulley; a driven pulley; an endless belt engaged with the drive pulley and movable in response to movement of the driven pulley and engaged with the driven pulley; an idler pulley engaged with the endless belt and positioned on a taut side of the belt drive system; and a load sensor connected to the idler pulley. The driven pulley is rotatable in response to movement of the endless belt.The load sensor may be operative to generate a signal in response to a load applied by the endless belt to the idler pulley, and the load may be representative of a tension in the endless belt.
[0004] Another aspect of the present disclosure relates to a computer-implemented method for automatically controlling the change in an operating speed of a belt drive system that supplies power to the agricultural harvesting header. The method may include receiving, via a speed sensor, a current operating speed of the agricultural harvesting header; determining whether the current operating speed is within a selected range of operating speeds; receiving, from a load sensor, a current operating load on the belt drive system in response to the current operating speed being outside the selected range of operating speeds; determining whether the current operating load on the belt drive system meets or exceeds a selected load threshold;and performing a gear change operation of a transmission coupled to the belt drive system in response to the current operating speed being outside the selected range of operating speeds and the current operating load being below a selected load threshold, and not performing a gear change operation if the current operating load meets or exceeds the selected load threshold;
[0005] The various aspects may include one or more of the following features. At the position of the idler pulley along the endless belt, the endless belt may include a first portion extending on a first side of the idler pulley in a first direction and a second portion extending on a second side of the idler pulley in a second direction, and the load sensor is oriented in a direction that is not parallel to the first direction or the second direction. The first portion of the endless belt and the second portion of the endless belt may define an angle, and the orientation of the load sensor may be in a direction that bisects the angle. The load sensor may include a hydraulic pressure sensor. The hydraulic pressure sensor may be a hydraulic pressure transducer. The idler pulley may be slidably mounted and movable in response to a tension level in the endless belt.The movement of the idler pulley in response to the tension level in the endless belt can change a pressure in the hydraulic pressure sensor, indicating the tension level. The load sensor can include a load cell. The signal generated by the load sensor in response to the load exerted on the idler pulley by the endless belt can be generated in response to a displacement of the idler pulley in response to the load exerted by the endless belt.
[0006] The various aspects of the present disclosure may include one or more of the following features. Determining whether the current operating speed is within a selected range of operating speeds may include determining a current gear setting of a transmission operably coupled to the belt drive system and determining a selected range of operating speeds of the transmission corresponding to the current gear setting. Determining a current gear setting of the transmission operably coupled to the belt drive system may include receiving an output from a gear selection sensor. The output of the gear selection sensor may represent the current gear setting of the transmission.Determining the selected range of operating speeds of the transmission corresponding to the current gear setting may include referring to a lookup table containing a selected range of operating speeds for at least one gear setting of the transmission. Receiving, from the load sensor, the current operating load on the belt drive system in response to the current operating speed being outside the selected range of operating speeds may include sensing a characteristic indicative of a tension in an endless belt, wherein the tension in the endless belt is representative of the load on the belt drive system. The load sensor may be coupled to an idler pulley of the belt drive system and configured to sense a load applied to the idler pulley by the endless belt.Detecting the property indicative of tension in the endless belt may include detecting an output from the load sensor. The output may represent a load applied by the endless belt to the idler pulley. The load sensor may include a hydraulic cylinder coupled to an idler pulley of the belt drive system and a hydraulic pressure sensor configured to detect a hydraulic pressure of the hydraulic pressure sensor. Detecting the property indicative of tension in the endless belt may include detecting the hydraulic pressure of the hydraulic sensor using the hydraulic pressure sensor. The load sensor may include a load cell coupled to an idler pulley of the belt drive system, and detecting the property indicative of tension in the endless belt may include detecting an output of the load cell. The load sensor may be located on the tight side of the belt drive system.Performing a gear change operation of a transmission coupled to the belt drive system in response to the current operating speed being outside the selected range of operating speeds and the current operating load being below the selected load threshold may include actuating an actuator operably coupled to the transmission.
[0007] Further features and aspects will become apparent upon consideration of the detailed description and the accompanying drawings. Brief description of the drawings
[0008] The detailed description of the drawings refers to the enclosed figures; where: Fig. 1 is a side view of an exemplary fixed speed belt drive system according to some implementations of the present disclosure. Fig. 2 is a detailed view of an exemplary fixed speed belt drive system showing an exemplary load sensor coupled to an idler pulley, according to some implementations of the present disclosure. Fig. 3 is a flowchart of an example method for controlling the timing of a transmission gear change for a fixed speed belt drive system according to some implementations of the present disclosure. Fig. 4 is a flowchart of another example method for controlling a gear change of a transmission connected to a fixed speed belt drive system, according to some implementations of the present disclosure. Fig. 5 is a schematic view of an exemplary electronic control system for automatically controlling the operation of a transmission used to drive a fixed speed belt drive system, according to some implementations of the present disclosure. Fig. 6 is a block diagram illustrating an example computer system used to provide computational functionality associated with the described algorithms, methods, functions, processes, flows, and procedures described in the present disclosure, according to some implementations of the present disclosure. Detailed description
[0009] To promote an understanding of the principles of the present disclosure, reference will now be made to the implementations illustrated in the drawings, and specific language will be used to describe them. It should be understood, however, that these are not to be construed as limiting the scope of the disclosure. Any changes and further modifications to the described devices, systems, and methods, as well as any further applications of the principles of the present disclosure, that may be conceived by one skilled in the art to which the disclosure relates are fully contemplated. In particular, it is entirely contemplated that the features, components, and / or steps described with respect to one implementation may be combined with the features, components, and / or steps described with respect to other implementations of the present disclosure.
[0010] The present disclosure relates to belt drive systems and methods. In particular, the present disclosure describes fixed-speed belt drive systems that include a load sensor whose output indicates the tension in an endless belt of the belt drive system. However, the scope of the disclosure is not so limited, and accordingly, the devices, systems, and methods described herein are applicable to other belt drive systems. The belt tension sensed via the load sensor is used to control a shift of a transmission connected to the belt drive system. To reduce harsh shifting of the transmission during operation of the belt drive system (as well as to reduce wear and sudden, abrupt loading during shifting), the present disclosure also includes methods, including automated methods, for controlling the shift using belt tension.In some implementations, the belt tension is determined using the load sensor.
[0011] This description includes examples related to agricultural combine harvesters. However, these examples are not intended to limit the scope of the devices, systems, and methods described herein. Rather, these devices, systems, and methods are applicable to other types of devices, including other types of agricultural equipment as well as other types of devices in other industrial sectors.
[0012] Fig. 1 is a side view of an exemplary belt drive system 100. In this example, the belt drive system 100 is a fixed-speed belt drive system. However, as previously mentioned, other belt drive systems, such as adjustable-speed ones, are also within the scope of the present disclosure. The belt drive system 100 includes a drive pulley 102, a driven pulley 104, an idler pulley 106, an idler pulley 108, and an endless belt 110 engaged with each of the pulleys 102, 104, 106, and 108. Other fixed-speed belt drive systems within the scope of the present disclosure may include other configurations. In other implementations, a belt drive system within the scope of the present disclosure may, for example, include additional driven pulleys.Each of the pulleys 102, 104, 106, and 108 has a fixed diameter, so the belt drive system 100 is a fixed-speed belt drive system. Consequently, the belt drive system 100 lacks one or more pulleys that change an effective diameter of the pulley, e.g., in response to an input to change the speed, e.g., to change the effective diameter of one or more pulleys of the belt drive system. Consequently, in a fixed-speed belt drive system, the speed ratio between the drive and driven pulleys remains constant regardless of the speed of the belt drive system. That is, the speed ratio between the drive pulley and the driven pulley remains constant regardless of the speed of the drive pulley. Further, each of the pulleys 102, 104, 106, and 108 is rotatable about a respective axis 103, 105, 107, and 109.
[0013] The drive pulley 102 is driven by a power source, such as an internal combustion engine, a motor (such as an electric motor or hydraulic motor), or a shaft driven directly or indirectly by a power source. In some implementations, the drive pulley 102 is coupled to a transmission that allows a speed of the drive pulley 102 to be adjusted, such as by shifting the transmission, resulting in a change in the gear setting of the transmission. The driven pulley 104 is connected to another component or system for which power is to be transmitted from the drive pulley 102. For example, in some cases, a driven pulley 104 is connected to the drive system of the feedhouse of a combine harvester.The power transmitted to the driven pulley 102 is used to drive a conveyor belt in a combine harvester's elevator to transport crops from an agricultural header into the combine for further processing. In other cases, other types of components or systems that require power to operate may be connected to the driven pulley 104 via the endless belt 110.
[0014] In the example shown, the drive pulley 102 rotates in the direction of arrow 112, ie in the context of Fig. 1 counterclockwise. The endless belt 110 therefore has a tight side 114 extending between the drive pulley 102 and the driven pulley 104, and a loose side 116 extending between the drive pulley 102 and the driven pulley 104 on a side of the belt drive system 100 opposite the tight side 114. The idler pulley 106 is located on the tight side 114.
[0015] The belt drive system 100 also includes a load sensor 118 connected to the idler pulley 106. The load sensor 118 detects a load exerted by the endless belt 110 on the idler pulley 106. This detected load is related to, and thus indicative of, the belt tension on the taut side 114 of the endless belt 110. Thus, with the load detected by the load sensor 118, the tension on the taut side 114 of the endless belt 110 can be determined. In some implementations, the determined load is used to determine the torque or power of the belt drive system. In other implementations, the load is used. Thus, the disclosure encompasses the use of the load or the torque or power determined using the load.
[0016] Example sensors within the scope of load sensor 118 include a hydraulic cylinder including a pressure sensor configured to detect the pressure of a hydraulic fluid within the hydraulic cylinder, as shown in Fig. 2 shown. Fig. 2 shows a load sensor 200, which may be similar to load sensor 118 and includes a hydraulic cylinder 202 and a pressure sensor 204. The hydraulic cylinder 202 includes a cylinder body 206, a piston 208 movable within the cylinder body 206, and a piston rod 210 connected to the piston 208. One of the piston rod 210 or the cylinder body 206 is connected to a pulley 212, which may be similar to the pulley 106, and the other of the piston rod 210 or the cylinder body 206 is stationary (e.g., prevented from moving relative to the drive pulley). Although in Fig. 2, the cylinder housing 206 is shown as rigidly mounted. In other embodiments, the cylinder housing 206 (or the piston rod 210, as the case may be) is attached to a pin connection that allows rotation but prevents displacement. The pressure sensor 204 detects the pressure of the hydraulic fluid 213 inside the cylinder body 206.
[0017] When the tension in an endless belt 214 changes, the load exerted on the idler pulley 212 also changes. For example, the change in load on the idler pulley 212 is proportional to the change in the tension of the endless belt 214. When the tension in the endless belt 214 increases, the idler pulley 212 is pushed in the direction of arrow 216. Since the piston rod 210 is connected to the idler pulley 212, the piston rod 210 is also pushed in the direction of arrow 216, compressing the hydraulic fluid 213 between the cylinder housing 206 and the piston 208. The pressure sensor 204 detects the pressure of the compressed hydraulic fluid 213. The tension of the endless belt can be determined based on the detected pressure of the hydraulic fluid 213.A reduction in tension in the endless belt 214 causes the idler pulley 212 to be pushed in the direction of arrow 218, thereby reducing the pressure exerted by the piston 208 on the hydraulic fluid 213. The reduced pressure is also sensed by the pressure sensor 204 and can be used to determine the tension in the endless belt 214. In some cases, a spring may be applied to push the piston rod 210 in the direction of arrow 218 when a release of tension in the endless belt 214 occurs. However, because a hydraulic fluid (i.e., a liquid) is essentially incompressible, the idler pulley 212, and thus the piston rod 210, will not actually be displaced by any appreciable amount in the directions of arrows 216 and 218 in response to changes in tension in the endless belt 214.
[0018] With further reference to Fig. 2, the endless belt 214 includes a first portion 220 extending away from the idler pulley 212 in a first direction 222 and a second portion 224 extending away from the idler pulley 212 in a cross-sectional direction 226. The first portion 220 and the second portion 224 form an angle θ. In some implementations, the directions indicated by arrows 216 and 218 in which the piston rod 210 is pushed lie on a line that bisects (i.e., equally divides) the angle θ. In other implementations, the line along which the piston rod is moved may lie on a line that does not bisect the angle θ.
[0019] As explained above, in some implementations, the load sensor 118 includes a hydraulic cylinder and a pressure sensor. However, the load sensor 118 also includes other types of sensors. For example, in some implementations, the load sensor 118 may include a load cell, a hydraulic pressure transducer, a strain sensor on a component loaded by the idler pulley 212 as a function of the tension of the endless belt 214, a spring in combination with a linear position sensor, and a spring in combination with a proximity sensor. In some implementations, one or more of these other types of load sensors are oriented so that the load sensor is aligned with the line bisecting the angle θ. In other implementations, the load sensors may be oriented in a different direction.
[0020] The tension in an endless belt, such as endless belts 110 and 214, may increase as a result of a higher load through the driven pulley, such as driven pulley 104 or 212. This increased load may occur, for example, when the component or system driven by the driven pulley experiences increased resistance. For example, in some cases, an example fixed-speed belt drive system is used to power the drive system of a combine harvester's feederhouse. In some cases, as the speed at which the combine moves across a field during harvesting increases, so does the throughput of crop fed into the feederhouse. This increased throughput of crop results in a higher load on the feederhouse drive system. This increases the load on the driven pulley and, in turn, increases the tension in the endless belt driving the driven pulley.Therefore, as the speed of the combine harvester increases during a harvesting operation, the load on the endless belt generally increases.
[0021] Even at a constant combine speed, the load on the feederhouse drive system can increase. For example, the crop size or density distribution across a field can vary. When a combine harvester traveling at a constant speed encounters a larger crop volume, e.g., because the crop is larger or there is more crop present, the amount of crop entering the feederhouse also increases, increasing the load on the feederhouse drive system. As a result, the tension in the endless belt that transmits power to the feederhouse drive system increases. As the load on the belt drive system increases, the operating speed of the belt drive system may need to be increased.
[0022] Therefore, generally, as the combine harvester speed increases, the operating speed of the feederhouse drive system should also increase to accommodate the increase in crop input into the feederhouse. Since a fixed-speed belt drive system has a constant gear ratio, as explained above, a gearbox is used to change the operating speed of the belt drive system. Shifting the gearbox changes the speed of the drive pulley, thereby increasing or decreasing the operating speed of the belt drive system. However, it is desirable to change the gears of the gearbox when the load on the belt drive system is within a desired range.Since the load on a belt drive system corresponds to, and is thus representative of, the tension of the endless belt of the belt drive system, the tension of the endless belt can be used to determine when the gears of the transmission need to be changed. Using the tension in the endless belt as an indicator of the load on the belt drive system and thus controlling a speed of the belt drive system to adapt the load on the feederhouse drive system is also beneficial to prevent damage to the endless belt. Therefore, it is desirable to change the gear setting of a transmission when the tension in the endless belt, for example, reaches or falls below a certain value.By controlling the shift timing during combine speed changes, gear changes are less abrupt, smoother, and less prone to wear, reducing abrupt load changes experienced by the belt drive system, the power source, and the driven components or systems. This can improve the service life of the endless belt, other parts of the belt drive system, and the transmission. Furthermore, the shift timing control described here can also reduce the operator discomfort associated with sudden or harsh gear shifts.
[0023] Fig. 3 is a flowchart of an example method 300 for controlling the timing of a transmission gear change for a fixed-speed belt drive system. As discussed above, controlling the shift timing of a transmission driving a fixed-speed belt drive system provides improved shift performance (e.g., smooth shifting with less harshness) and reduced wear on the belt drive components, e.g., the endless belt. At 302, a current operating speed of an agricultural header (e.g., a corn header or a belt header) is received. For example, an electronic controller, such as electronic controller 502 (described in more detail below), receives a current operating speed of the agricultural header. The current operating speed of the agricultural header may be determined by a sensor, e.g., a speed sensor (e.g.,a speed sensor). At 304, it is determined whether the current operating speed of the agricultural header is within an operating range of the current gear setting of a transmission coupled to the belt drive system, e.g., the fixed speed belt drive system 100. As previously explained, a transmission is connected to the belt drive system and serves to change the operating speed of the belt drive system. If the current operating speed is within the operating range of the current gear setting, method 300 proceeds to 302, and method 300 continues from there. If the current operating speed is not within the operating range of the current gear setting, method 300 proceeds to 306, where a current load is received on the belt drive system.At 308, it is determined whether the current load on the belt drive system meets or exceeds a selected load threshold. If the current load on the belt drive system meets or exceeds the selected load threshold, a transmission gear shift is not permitted, and method 300 proceeds to 302, from which method 300 continues. If the current load on the belt drive system is below the selected load threshold, a transmission gear shift is performed at 312, causing the transmission to change gear. This changes the operating speed of the belt drive system.
[0024] In some implementations, the current load on the belt drive system is determined using a load sensor, which may be similar to load sensor 118 or 200, which detects a load acting on an idler pulley, which may be similar to idler pulley 106 or 212, provided on a taut side of the belt drive system by an endless belt, such as endless belt 114 or 214 of the belt drive system. As previously explained, the load acting on the idler pulley corresponds to the tension in the endless belt of the belt drive system. This belt tension, in turn, is representative of the load on the belt drive system. The load on the belt drive system is generally caused by the amount of crop being collected by the agricultural header.This load on the agricultural header generally increases with increasing combine speed or with increasing size or quantity of crop being collected by the header (e.g., due to variations in crop size across a field), even if the combine speed remains constant. However, a change in load on the agricultural header is typically the result of a change in the speed at which the combine travels across a field during a harvesting operation.
[0025] Fig. 4 is a flowchart of another example method 400 for controlling a gear change of a transmission connected to a belt drive system. In some implementations, the method 400 is applicable to fixed-speed belt drive systems. However, in other implementations, the method 400 is also applicable to other types of belt drive systems. The following discussion with respect to Fig. 4 is carried out in connection with an agricultural harvesting vehicle. The scope of protection of the example method 400 of Fig. 4, however, also encompasses other vehicle types, such as other types of agricultural vehicles that include or are connectable to an implement. At 402, a current ground speed of an agricultural harvesting vehicle (i.e., a speed across the ground of the agricultural harvesting vehicle) is received. The speed of the agricultural harvesting vehicle may be determined, for example, using a global navigation satellite system (GNSS) or a speed of a transmission of the driveline of the agricultural harvesting vehicle. At 404, an ideal operating speed of an agricultural header connected to the agricultural harvesting vehicle is determined based on the current ground speed. The operating speed of the agricultural header may be changed based on the ground speed of the agricultural harvesting vehicle.For example, if the ground speed of an agricultural harvesting vehicle in a field increases during a harvesting operation, the operating speed of the agricultural header will increase accordingly. The increase in the operating speed of the header is necessary to balance the larger amount of crop being collected by the header with the increase in the ground speed of the agricultural harvesting vehicle over the ground. In some cases, an ideal operating speed is an operating speed of the agricultural header at which the agricultural header is able to harvest harvested crops without issues, such asTo process blockages or buildup of crop material on the agricultural header or at any interface between the agricultural header and the agricultural harvesting vehicle's conveyor house, at the speed at which the agricultural harvesting vehicle moves across the field during a harvesting operation. In some cases, the ideal operating speed is determined empirically. In some implementations, the ideal operating speed may be determined using a lookup table, a mathematical relationship, a graph of operating speed versus ground speed, or another approach.
[0026] At 406, it is determined whether the ideal operating speed is within a range of operating speeds corresponding to a current gear setting of a transmission connected to and operatively capable of driving the fixed-speed belt drive system. For example, the transmission connected to the fixed-speed belt drive system includes a plurality of existing gear settings, and each gear setting is associated with a speed range. That is, each gear setting can support a range of operating speeds of the header. In some cases, the speed ranges of adjacent gears may overlap. In other cases, the speed ranges of adjacent gear settings do not overlap. In some implementations, the gear setting is sensed, for example, using a gear selection sensor.
[0027] If the ideal operating speed is within the range of operating speeds of the current gear setting, a gear change is not required, and method 400 proceeds to 408 where an error sum value is reset to zero. If the ideal operating speed is outside the range of operating speeds associated with the current gear setting, the method proceeds to 410 where an error value is determined. The error value represents the deviation between the ideal operating speed and the range of operating speeds associated with the current gear setting. At 410, the error value is determined based on the amount by which the ideal operating speed is outside the range of operating speeds associated with the current gear setting.For example, if a range of operating speeds of the current gear setting is 400 revolutions per minute (rpm) to 500 rpm and the ideal operating speed is 350 rpm, the current ideal operating speed is outside the range of operating speeds of the current gear setting. In some implementations, the error value is determined from the difference between the end of the range of operating speeds closest to the ideal operating speed and the ideal operating speed. In this example, the error value is 50 rpm, i.e., 400 rpm minus 350 rpm. If the ideal operating speed were 600 rpm, the error value would be 100 rpm, i.e., 600 rpm minus 500 rpm. In some implementations, determining the error may be more complex.The size or magnitude of the determined error value may depend, for example, on the absolute difference between the ideal operating speed and the operating speed range. In some cases, the generated error value increases with increasing difference between the ideal operating speed and the operating speed range. This progressive increase can be achieved using a multiplier multiplied by the determined difference between the ideal operating speed and the operating speed range associated with the current gear setting.
[0028] At 412, the error sum value is determined. The error sum value is a summation of the error determined in the current run of method 400 and the error values generated in previous runs of method 400. Method 400 then proceeds to 414, where the error sum value is compared to a selected threshold.
[0029] If the value of the error sum exceeds the selected threshold, a change in the gear setting is necessary.
[0030] As in Fig. As shown in Figure 4, the error sum value is set equal to zero if the ideal operating speed is within the range of operating speeds. Method 400 proceeds to 412, and the error sum value remains equal to zero regardless of an error value generated in a previous pass through method 400. Thus, if it is determined that the ideal operating speed is within the range of operating speeds of the current gear setting, the error sum value is reset to zero.
[0031] If a gear setting change is required, the method proceeds to 416, where the load on the fixed-speed belt drive system is determined. In some cases, the load on the fixed-speed belt drive system is determined by determining the tension in an endless belt of the belt drive system, as previously described. For example, an output from a load sensor, such as load sensor 118 or 200, represents the tension in the endless belt. In some implementations, the output of the load sensor is used to determine the tension in the endless belt, such as by means of a mathematical formula, lookup table, chart, or other method. At 418, a determination is made as to whether the output of the load sensor (representative of the load on the belt drive system) is within an allowable load range or below a selected load value.As explained above, the determined load may be used to determine the torque or power, and the torque or power may be compared to an appropriately selected torque or power range or a selected torque or power value. In some cases, the allowable load range is a manufacturer-selected range. In some implementations, an allowable load range or a selected load value is selected to produce a gear change with, for example, a desired smoothness, a selected vibration level, a selected acceleration level for the belt drive system, the transmission, the harvester head, or a component of the harvester head, or a combination thereof. If the load on the belt drive system is within the allowable load range, method 400 proceeds to 420 where the transmission is shifted to change the gear setting.If the load on the belt drive system is outside the allowable load range, no gear setting change is commanded and the method returns to 402.
[0032] It should be understood that the present disclosure is not limited to example methods 300 and 400. For example, in some implementations, methods 300 or 400 may include additional or fewer features. For example, in some implementations, a transmission gear setting may be received and the operating speed range associated with the gear setting may be determined, e.g., using a lookup table, an algorithm, a graphical relationship, or another approach.
[0033] Fig. 5 is a schematic view of an exemplary electronic control system 500 for automatically controlling the operation of a transmission used to drive a fixed-speed belt drive system, e.g., by controlling a gear shift of the transmission. The control system 500 automatically shifts a gear setting of the transmission according to the methods described herein or other methods within the scope of the present disclosure, such as methods 300 or 400. The control system 500 includes an electronic controller 502, a ground speed sensor 504 of an agricultural machine, such as aan agricultural harvesting vehicle; a GNSS receiver 506; a gear setting sensor 508; an actuator 510 operable to shift a gear setting of a transmission connected to the belt drive system; a load sensor 512; a display 514; an input device 516; and a speed sensor 517 operable to detect a speed of an agricultural harvesting header. The ground speed sensor 504 and the GNSS receiver 506 are used to determine the ground speed of the agricultural machine over the ground. Thus, in some implementations, one of the ground speed sensor 504 and the GNSS receiver 506 may be omitted. The controller 502 is operable to control actuation of the actuator 510 to control shifting of the transmission. Shifting the transmission changes the gear setting and thus the speed of the fixed-speed belt drive system.Load sensor 512 may be similar to load sensors 118 or 200 and is used to determine the tension in an endless belt of the fixed-speed belt drive system. This belt tension corresponds to, represents, or is an indicator of the load acting on the fixed-speed belt drive system.
[0034] The speed sensor 517 detects the operating speed of an agricultural harvesting header. The speed sensor 517 detects the operating speed of the agricultural harvesting header, e.g., by detecting the speed of a component of the agricultural harvesting header. In some cases, for example, the speed sensor detects the speed of a power take-off shaft of the agricultural harvesting header or another rotating component of the agricultural harvesting header. In other implementations, the speed sensor detects a speed of another component or system representative of the operating speed of the agricultural harvesting header. In some cases, for example, the speed sensor detects the operating speed of a belt drive system or a speed of a transmission that drives the belt drive system at the current gear setting of the transmission.In some cases, the speed sensor detects the speed of a drive pulley, such as drive pulley 102.
[0035] The control system 500 may also include or be communicatively coupled to a remote database 518, which may be configured in the form of cloud storage, a remote server, or other type of electronic storage for storing information.
[0036] The various components of the control system 500 are communicatively coupled to the control device 502, e.g., via a wired or wireless connection.
[0037] In some implementations, the controller 502 is an electronic computer, such as the computer 602 described in more detail below. The controller 502 includes a processor 520 and a memory 522 communicatively coupled to the memory processor 520. Additional details of the controller 502, such as the processor 520 and the memory 522, are described below in connection with the computer 602. In some implementations, the controller 502 is, for example, in a manner described below in connection with Fig. 6, communicatively coupled to a network. Memory 522 communicates with processor 520 and is used to store programs and other software, information, and data. Processor 520 is capable of executing programs and software and of sending and receiving information to and from memory 522. Although a single memory 522 and processor 520 are illustrated, other implementations may use a plurality of memories, processors, or both. Although processor 520 and memory 522 are shown as local components of controller 502, other implementations may remotely locate processor 520 and / or memory 522. Software 524, such as in the form of an application or program, is executed by processor 520 to control the operation of control system 500 as described herein.In particular, software 524 includes executable instructions that control the operation of the various components coupled to controller 502 and, as a result, control a shift of a transmission to control an operating speed of a fixed-speed belt drive system. In some implementations, software 524 includes instructions that cause processor 520 to perform method 300 or 500, or another process within the scope of the disclosure, to control a shift of a transmission coupled to a belt drive system, such as a fixed-speed belt drive system.
[0038] The input device 516 is communicatively coupled via a wired or wireless connection. Example input devices 516 include a keyboard, a keypad, one or more buttons, a slider, a dial, a button, a mouse, or a joystick. The display 514 is communicatively coupled to the controller 502 via a wired or wireless connection. Information is displayed on the display 514, such as information about the operation of the control system 500. The information displayed on the display 514 may include, for example, the gear setting of a transmission connected to a belt drive system, the load on the belt drive system, the ground speed of the agricultural harvesting vehicle, or other information related to the control system 500 or other aspects of the agricultural harvesting vehicle.In some cases, the information displayed on display 514 is presented via a graphical user interface (GUI) 526. Example displays include cathode ray tubes (CRTs), liquid crystal displays (LCDs), or plasma displays. Other types of displays are also within the scope of the present disclosure. In some implementations, display 514 is a touch-sensitive screen that accepts input from a user via touch. In some implementations where display 514 is a touch-sensitive screen, input device 516 may be omitted.
[0039] Without limiting the scope, interpretation, or application of the following claims in any way, one technical effect of one or more of the example implementations disclosed herein is to improve the shifting performance of a transmission connected to a belt drive system. Another technical effect of one or more of the example implementations disclosed herein is to reduce wear and the risk of damage to components of a belt drive system or components associated with the belt drive system.
[0040] Fig. 6 is a block diagram illustrating an exemplary computer system 600, according to some implementations of the present disclosure, used to provide computational functionality in connection with described algorithms, methods, functions, processes, operations, and procedures described in the present disclosure. The illustrated computer 602 is intended to include any computing device, such as a server, a desktop computer, a laptop / notebook computer, a wireless data port, a smartphone, a personal data assistant (PDA), a tablet computing device, or one or more processors within these devices, including physical instances, virtual instances, or both. The computer 602 may include input devices such as keypads, keyboards, and touch-sensitive screens that can accept user information.Computer 602 may also include output devices that can convey information related to the operation of computer 602. The information may include digital data, visual data, audio information, or a combination of information. The information may be presented in a graphical user interface (UI).
[0041] Computer 602 may function as a client, a network component, a server, a database, a persistence component, or a component of a computer system for performing the subject matter described in the present disclosure. The illustrated computer 602 is communicatively coupled to a network 630. In some implementations, one or more components of computer 602 may be configured to operate in various environments, including cloud computing-based environments, local environments, global environments, and combinations of environments.
[0042] At a higher level, computer 602 is an electronic data processing device capable of receiving, transmitting, processing, storing, and managing data and information related to the described subject matter. According to some implementations, computer 602 may also include or be communicatively coupled to an application server, an email server, a web server, a caching server, a streaming data server, or a combination of servers.
[0043] Computer 602 may receive requests from a client application (e.g., executing on another computer 602) over network 630. Computer 602 may respond to the received requests by processing the received requests using software applications. Requests may also be sent to computer 602 by internal users (e.g., from a command console), external (or third) parties, automated applications, facilities, people, systems, and computers.
[0044] The components of computer 602 may each communicate with each other via a system bus 603. In some implementations, any or all components of computer 602, including hardware or software components, may be connected to each other or to interface 604 (or a combination of both) via system bus 603. Interfaces may use an application programming interface (API) 612, a service layer 613, or a combination of API 612 and service layer 613. API 612 may include specifications for routines, data structures, and object classes. API 612 may be either independent of or dependent on a computer language. API 612 may refer to an entire interface, a single function, or a set of APIs.
[0045] The service layer 613 may provide software services to the computer 602 and other components (whether depicted or not) communicatively coupled to the computer 602. The functionality of the computer 602 may be accessible to all service users through this service layer. Software services provided by the service layer 613 may provide reusable, defined functionality through a defined interface. The interface may, for example, be software written in JAVA or C++ or in a language that exposes data in Extensible Markup Language (XML) format. Although depicted as an integrated component of the computer 602, in alternative implementations, the API 612 or the service layer 613 may be a standalone component with respect to other components of the computer 602 and other components communicatively coupled to the computer 602.Furthermore, any or all portions of the API 612 or the service layer 613 may be implemented as child modules or sub-modules of another software module, enterprise application, or hardware module without departing from the scope of the present disclosure.
[0046] The computer 602 includes an interface 604. Although in Fig. 6, two or more interfaces 604 may be used depending on the particular needs, desires, or particular implementations of the computer 602 and the functionality described. The interface 604 may be used by the computer 602 to communicate with other systems connected to the network 630 (whether depicted or not) in a distributed environment. In general, the interface 604 may include, or be implemented using, logic encoded in software or hardware (or a combination of software and hardware) that may be used to communicate with the network 630. In particular, the interface 604 may include software that supports one or more communication protocols associated with communication.Thus, the network 630 or the interface hardware can be operated to transmit physical signals inside and outside the depicted computer 602.
[0047] The computer 602 includes a processor 605. Although in Fig. 6, two or more processors 605 may be used depending on the need, desire, or particular implementations of the computer 602 and the functionality described. In general, the processor 605 may execute instructions and manipulate data to perform the operations of the computer 602, including operations using algorithms, methods, functions, processes, histories, and workflows as described in the present disclosure.
[0048] The computer 602 also includes a database 606 in which data for the computer 602 and other components connected to the network 630 can be stored (whether mapped or not). The database 606 can be, for example, an in-memory, a conventional, or a database in which data is stored within the meaning of the present disclosure. In some implementations, the database 606 can be a combination of two or more different database types (e.g., hybrid in-memory and conventional databases), depending on the particular needs, desires, or particular implementations of the computer 602 and the described functionality. Although in Fig. 6 illustrates a single database 606, two or more databases (of the same type, different types, or a combination of different types) may be used depending on the particular needs, desires, or implementations of computer 602 and the functionality described. Although database 606 is illustrated as an internal component of computer 602, in alternative implementations, database 606 may be external to computer 602.
[0049] The computer 602 also includes a memory 607 in which data for the computer 602 or a combination of components connected to the network 630 can be stored (whether depicted or not). Any data consistent with the present disclosure can be stored in the memory 607. In some implementations, the memory 607 may be a combination of two or more different memory types (e.g., a combination of semiconductor and magnetic memory), depending on the particular needs, desires, or particular implementations of the computer 602 and the described functionality. Although in Fig.6, a single memory 607 is illustrated, two or more memories 607 (of the same type, different types, or a combination of different types) may be used depending on the particular needs, desires, or particular implementations of the computer 602 and the functionality described. Although the memory 607 is illustrated as an internal component of the computer 602, in alternative implementations, the memory 607 may also be external to the computer 602.
[0050] The application 608 may be an algorithmic software engine that provides functionality according to the particular needs, desires, or particular implementations of the computer 602 and the described functionality. The application 608 may, for example, serve as one or more components, modules, or applications. Further, although the application 608 is depicted as a single application 608, it may be implemented as multiple applications 608 on the computer 602. Furthermore, although the application 608 is depicted as internal to the computer 602, in alternative implementations it may also be external to the computer 602.
[0051] The computer 602 may also include a power supply 614. The power supply 614 may include a rechargeable or non-rechargeable battery, which may be configured to be either user-replaceable or non-user-replaceable. In some implementations, the power supply 614 may include power conversion and management circuitry, including recharging, standby, and power management functions. In some implementations, the power supply 614 may include an AC power plug to allow the computer 602 to be connected to an electrical outlet or power source, for example, to power the computer 602 or to charge a rechargeable battery.
[0052] There may be any number of computers 602 connected to or external to a computer system including a computer 602, with each computer 602 communicating via the network 630. Furthermore, the terms "client," "user," and other suitable expressions may be used interchangeably without departing from the scope of the present disclosure. Furthermore, the present disclosure contemplates that multiple users may use one computer 602, and one user may use multiple computers 602.
[0053] Implementations of the subject matter and functional operations described in this specification may be implemented in digital electronic circuits, in tangible computer software or firmware, in computer hardware, including the structures disclosed in this specification and their structural equivalents, or in combinations of one or more of the foregoing. Software implementations of the described subject matter may be implemented as one or more computer programs. Each computer program may include one or more modules of computer program instructions encoded on a tangible, non-transitory, computer-readable computer storage medium for execution by a data processing device or for controlling the operation of such a device. Alternatively or additionally, the program instructions may be encoded in / on an artificially generated, propagated signal.The signal may, for example, be a machine-generated electrical, optical, or electromagnetic signal generated to encode information for transmission to suitable receiving devices for execution by a data processing device. The computer storage medium may be a machine-readable storage device, a machine-readable storage substrate, a random or serial access storage device, or a combination of computer storage media.
[0054] The terms "data processing device," "computer," and "electronic computing device" (or equivalents known to those skilled in the art) refer to data processing hardware. For example, a data processing device may include all types of devices, devices, and machines for processing data, including, for example, a programmable processor, a computer, or multiple processors or computers. The device may also include special-purpose logic circuitry, such as a central processing unit (CPU), a field-programmable gate array (FPGA), or an application-specific integrated circuit (ASIC). In some implementations, the data processing device or special-purpose logic circuitry (or a combination of the data processing device or special-purpose logic circuitry) may be hardware-based or software-based (or a combination of hardware and software-based).The device may optionally include code that provides an execution environment for computer programs, for example, code representing processor firmware, a protocol stack, a database management system, an operating system, or a combination of execution environments. The present disclosure contemplates the use of data processing devices with or without conventional operating systems, for example, LINUX, UNIX, WINDOWS, MAC OS, ANDROID, or IOS.
[0055] A computer program, which may also be called or described as a program, software, software application, module, software module, script, or code, can be written in any programming language. Examples of programming languages include compiled languages, interpreted languages, declarative languages, or procedural languages. Programs can be provided in any form, such as stand-alone programs, modules, components, subroutines, or units for use in a computing environment. A computer program may, but need not, correspond to a file in a file system.A program may be stored in a portion of a file that also contains other programs or data, for example, one or more scripts stored in a markup language document, in a single file dedicated to the program in question, or in multiple coordinated files storing one or more modules, subroutines, or portions of code. A computer program may be deployed for execution on one computer or on multiple computers, located, for example, at one site or distributed across multiple sites interconnected by a communications network.While parts of the programs illustrated in the various figures can be represented as individual modules implementing various features and functions through different objects, methods, or processes, the programs may instead comprise a number of submodules, third-party services, components, and libraries. Conversely, the features and functions of different components may be combined into individual components, if necessary. Thresholds used for data processing can be determined statically, dynamically, or both statically and dynamically.
[0056] The methods, processes, or logic flows described in this specification may be performed by one or more programmable computers executing one or more computer programs to perform functions by operating on input data and generating output. The methods, processes, or logic flows may also be performed by special-purpose logic circuitry, such as a CPU, FPGA, or ASIC, and devices may also be implemented as such.
[0057] Computers suitable for executing a computer program may be based on one or more general-purpose or special-purpose microprocessors and other types of CPUs. The elements of a computer are a CPU for executing instructions and one or more memory devices for storing instructions and data. In principle, a CPU can receive instructions and data from (and write data to) memory. A computer may also include or be operatively coupled to one or more mass storage devices for storing data. In some implementations, a computer can receive data from and transfer data to the mass storage devices, such as magnetic, magneto-optical, or optical disks.In addition, a computer may be embedded in another device, such as a mobile phone, a personal digital assistant (PDA), a mobile audio or video player, a game console, a GPS (Global Positioning System) receiver, or a portable storage device such as a USB (Universal Serial Bus) flash drive.
[0058] Computer-readable media (volatile or non-volatile) suitable for storing computer program instructions and data can include all forms of permanent / non-permanent and volatile / non-volatile memory, media, and storage devices. Computer-readable media can include, for example, semiconductor storage devices such as random-access memory (RAM), read-only memory (ROM), phase-change memory (PRAM), static random-access memory (SRAM), dynamic random-access memory (DRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), and flash memory devices. Computer-readable media can also include, for example, magnetic devices such as tapes, cartridges, and internal / removable disks.Computer-readable media may also include magneto-optical disks and optical storage devices and technologies, including, for example, Digital Video Disc (DVD), CD-ROM, DVD+ / -R, DVD-RAM, DVD-ROM, HD-DVD, and Blu-ray. Memory may store various objects or data, including caches, classes, frameworks, applications, modules, backup data, jobs, web pages, web page templates, data structures, database tables, repositories, and dynamic information. The types of objects and data stored in memory include parameters, variables, algorithms, instructions, rules, constraints, and references. Memory may also include protocols, policies, security or access data, and report files. The processor and memory may be supplemented by or integrated with special-purpose logic circuitry.
[0059] Implementations of the subject matter described in the present disclosure may be implemented on a computer having a display device to enable interaction with a user, including displaying information to (and receiving input from) the user. Display devices may include, for example, cathode ray tubes (CRTs), liquid crystal displays (LCDs), light-emitting diodes (LEDs), and plasma monitors. Display devices may include a keyboard and pointing devices, such as a mouse, trackball, or trackpad. User input may also be provided via a touchscreen, such as a pressure-sensitive surface of a tablet computer or a multi-touch screen using capacitive or electrical sensing.Other types of devices may also be used to enable interaction with a user, such as obtaining user feedback, including sensory feedback such as visual, audio, or tactile feedback. User input may be in the form of auditory, verbal, or tactile input. In addition, a computer may interact with a user by sending and receiving documents to and from a device used by the user. For example, the computer may send web pages to a web browser on a user's client device when the web browser requests them.
[0060] The term "graphical user interface" or "GUI" can be used in the singular or plural to describe one or more graphical user interfaces and each of the displays of a particular graphical user interface. Therefore, a graphical user interface (GUI) can represent any graphical user interface, including but not limited to a web browser, a touchscreen, or a command-line interface (CLI), that processes information and efficiently presents the information results to the user. In principle, a GUI can contain a variety of user interface (UI) elements that are partially or fully related to a web browser, such as interactive fields, pull-down lists, and buttons. These and other UI elements can be related to or represent the functionality of the web browser.
[0061] Implementations of the subject matter described in this specification may be implemented in a data processing system that includes a backend component, such as a data server, or a middleware component, such as an application server. Furthermore, the data processing system may include a frontend component, such as a client computer with a graphical user interface or a web browser, through which a user can interact with the computer. The components of the system may be interconnected by any form or medium of wired or wireless digital data communication (or a combination of data communications) in a communications network.Examples of communications networks include a local area network (LAN), a radio access network (RAN), a metropolitan area network (MAN), a wide area network (WAN), Worldwide Interoperability for Microwave Access (WIMAX), a wireless local area network (WLAN) (e.g., using 802.11 a / b / g / n or 802.20 or a combination of protocols), all or part of the Internet, or any other communications system or systems at one or more locations (or a combination of communications networks). The network can communicate using, for example, IP (Internet Protocol) packets, Frame Relay frames, ATM (Asynchronous Transfer Mode) cells, voice, video, data, or a combination of communication types between network addresses.
[0062] Wireless connections within the scope of this disclosure include wireless protocols such as 802.15 protocols (e.g., BLUETOOTH®), 802.11 protocols, 802.20 protocols (e.g., WL-FI®), or a combination of different wireless protocols.
[0063] The data processing system can comprise clients and servers. A client and a server can, in principle, be located far apart and communicate with each other via a communications network. The relationship between client and server can arise from computer programs running on the respective computers, creating a client-server relationship.
[0064] Clustered file systems can be any file system type that can be accessed for reading and updating from multiple servers. Locking or consistency tracking may not be required because locking an Exchange file system can be done at the application level. Furthermore, Unicode data files can be different from non-Unicode data files.
[0065] While this specification includes many specific implementation details, these should not be construed as limitations on the scope of what may be claimed, but rather as descriptions of features that may be specific to particular implementations. Certain features described in this specification in the context of separate implementations may also be realized in combination in a single implementation. Conversely, various features described in the context of a single implementation may also be implemented in multiple implementations, individually or in any suitable subcombination.Furthermore, although previously described features are described as operating in certain combinations and even originally claimed as such, one or more features from a claimed combination may in some cases be dropped from the combination, and the claimed combination may be directed to a sub-combination or a variant of a sub-combination.
[0066] Specific implementations of the subject matter have been described. Other implementations, modifications, and permutations of the described implementations are within the scope of the following claims, as would be obvious to one of ordinary skill in the art. Although operations are illustrated in the drawings in a particular order, this should not be understood to imply that these operations must be performed in the order shown or in any particular order, or that all of the operations shown must be performed (some operations may be considered optional) to achieve the desired results. Under certain circumstances, multitasking or parallel processing (or a combination of multitasking and parallel processing) may be advantageous and may be performed as needed.
[0067] Furthermore, the separation or integration of various system modules and components in the previously described implementations should not be understood to mean that such separation or integration is required in all implementations, and it should be assumed that the described program components and systems can generally be integrated into a single software product or packaged into multiple software products.
[0068] Accordingly, the example implementations described above do not define or limit the present disclosure. Other changes, substitutions, and modifications are also possible without departing from the spirit and scope of the present disclosure.
[0069] Furthermore, each claimed implementation is deemed applicable to at least one computer-implemented method; a non-transitory, computer-readable medium storing computer-readable instructions for performing the computer-implemented method; and a computer system including computer memory interoperably coupled to a hardware processor configured to execute the computer-implemented method or the instructions stored on the non-transitory, computer-readable medium.
[0070] While the foregoing describes exemplary implementations of the present disclosure, these descriptions are not intended to be limiting. Rather, other variations and modifications may be made without departing from the scope and spirit of the present disclosure as defined in the appended claims.
Claims
[1] A belt drive system operatively capable of detecting belt tension, the belt drive system comprising: Drive pulley operatively coupled to a drive device for rotating the drive pulley; a driven pulley; an endless belt engaged with the drive pulley and movable in response to movement of the driven pulley and engaged with the driven pulley; wherein the driven pulley is rotated in response to movement of the endless belt; a pulley engaged with the endless belt and positioned on a taut side of the belt drive system; and a load sensor connected to the idler pulley, the load sensor being operative to generate a signal in response to a load applied to the idler pulley by the endless belt, the load being representative of a tension in the endless belt. [2] The belt drive system of claim 1, wherein at the position of the idler pulley along the endless belt, the endless belt includes a first portion extending on a first side of the idler pulley in a first direction and a second portion extending on a second side of the idler pulley in a second direction, and wherein the load sensor is oriented in a direction that is not parallel to the first direction or the second direction. [3] The drive pulley of claim 1, wherein the load sensor includes a hydraulic pressure sensor. [4] The drive pulley of claim 3, wherein the idler pulley is slidably mounted and movable in response to a tension level in the endless belt, and wherein movement of the idler pulley in response to the tension level in the endless belt changes a pressure in the hydraulic pressure sensor indicative of the tension level. [5] The belt drive system of claim 1, wherein the signal generated by the load sensor in response to the load applied by the endless belt to the idler pulley is generated in response to a displacement of the idler pulley in response to the load applied by the endless belt. [6] A computer-implemented method for automatically controlling the change in an operating speed of a belt drive system that supplies power to an agricultural harvesting header, the method comprising: Receiving, via a speed sensor, a current operating speed of the agricultural header; Determining whether the current operating speed is within a selected range of operating speeds; Receiving, from a load sensor, a current operating load on the belt drive system in response to the current operating speed being outside the selected range of operating speeds; Determining whether the current operating load on the belt drive system meets or exceeds a selected load threshold; and Performing a gear change operation of a transmission coupled to the belt drive system in response to the current operating speed being outside the selected range of operating speeds and the current operating load being below a selected load threshold, and not performing a gear change operation when the current operating load meets or exceeds the selected load threshold. [7] The computer-implemented method of claim 6, wherein determining whether the current operating speed is within a selected range of operating speeds includes: determining a current gear setting of a transmission operatively coupled to the belt drive system; and determining a selected range of transmission operating speeds according to the current gear setting. [8] The computer-implemented method of claim 7, wherein determining a current gear setting of the transmission operably coupled to the belt drive system includes receiving an output from a gear selection sensor, the output of the gear selection sensor representing the current gear setting of the transmission. [9] The computer-implemented method of claim 7, wherein determining the selected range of operating speeds of the transmission corresponding to the current gear setting includes referring to a lookup table containing a selected range of operating speeds for at least one gear setting of the transmission. [10] The computer-implemented method of claim 6, wherein receiving, from the load sensor, the current operating load on the belt drive system in response to the current operating speed being outside the selected range of operating speeds includes sensing a characteristic indicative of a tension in an endless belt, the tension in the endless belt being representative of the load on the belt drive system. [11] The computer-implemented method of claim 10, wherein the load sensor is coupled to an idler pulley of the belt drive system and is configured to detect a load applied to the idler pulley by the endless belt, wherein detecting the property indicative of tension in the endless belt includes detecting an output from the load sensor, the output representing a load applied to the idler pulley by the endless belt. [12] The computer-implemented method of claim 10, wherein the load sensor includes: a hydraulic cylinder coupled to a pulley of the belt drive system; and a hydraulic pressure sensor configured to detect a hydraulic pressure of the hydraulic pressure sensor, and wherein detecting the property indicative of tension in the endless belt includes detecting the hydraulic pressure of the hydraulic sensor using the hydraulic pressure sensor. [13] The computer-implemented method of claim 10, wherein the load sensor includes a load cell coupled to an idler pulley of the belt drive system, and wherein sensing the property indicative of tension in the endless belt includes sensing an output of the load cell. [14] The computer-implemented method of claim 6, further comprising positioning the load sensor on the tight side of the belt drive system. [15] The computer-implemented method of claim 6, wherein performing a gear change operation of a transmission coupled to the belt drive system in response to the current operating speed being outside the selected range of operating speeds and the current operating load being below the selected load threshold includes actuating an actuator operably coupled to the transmission.