Implement automation system

Abstract

An automated operational mission planning system for power unit operation and implement operation is provided. The system supports operational control of a complex machine system by generating a connection profile based on a power unit profile and an implement profile. The mission planning system generates a plan for a selected project using operation commands based on the implement. An operation system installed in the power unit executes the mission plan while adjusting the connection profile to drive the implement work.

Description

[Technical Field]

[0001] The present invention relates generally to machine activity using automated vehicles and implements. [Background technology]

[0002] Autonomous machines exist in off-highway and other off-road applications (e.g., agriculture, turf, construction, mining) where a single machine performs a task autonomously or semi-autonomously with human supervision. Machine automation systems (e.g., vehicle automation systems) use on-board operating systems to operate and control a machine (e.g., a vehicle). The systems may also include on-board sensors to identify potential obstacles and provide feedback for driving and operating the machine.

[0003] Machine automation has been adapted to work within a field or at a specific work site. The field or work site includes pre-planned lines for traversing the field, including waypoints (reference points) and boundary markers. In some embodiments, the system has helped identify turning and headland movements to manage movement between work paths, such as parallel mowing lines. Machine automation is designed for a given project work on a specified field.

[0004] In a machine system having a power unit and implements, machine automation and planning are tailored to each combination of machine systems. The system accepts a selection of existing machine systems. Mission planning provides pre-configured control commands for specific machine systems based on mission commands for the specific machine systems. Summary of the Invention [Problem to be solved by the invention]

[0005] Automated planning and operations do not support the generation of variably generated mission plans from the perspective of the implement. Mission plans must be regenerated for different machine system configurations, even if the scope of work remains the same. For example, if the system starts with a mission plan for an implement at the front of a skid steer loader, the mission planning system must generate an entirely new mission plan for a machine system with an implement performing the same task at the rear of a tractor. Therefore, each mission plan is applicable to a limited set of machine systems with the same performance, operational control, and physical orientation. [Means for solving the problem]

[0006] The present disclosure provides an automated system for allocating and managing machine system operations through the generation of mission plans designed to improve efficiency and planning flexibility. Implement-based mission planning allows for the definition of implement planning paths compatible with any implement with a similar scope of work. Additionally, the mission planning process can build mission plans in a modular process based on modular component selection. This can improve the efficiency of the planning system and reduce overall network storage. In some embodiments, modular plan generation using individual profiles can support simplified mission planning and be performed by translating profiles within an on-board electronic control unit.

[0007] In some embodiments, the mission plan provides motion commands for the implement, which can be executed by the machine system using the transformation information to command the operation of the power unit, thereby increasing versatility in project mission planning and execution.

[0008] The present disclosure provides a system for generating independent profiles for power units and implements. The system also generates connection profiles to support operations when the power units and implements are combined into a machine system. The present disclosure creates the ability to increase the efficient generation of mission plans with the flexibility to achieve diverse operations.

[0009] Embodiments of the automation planning and operation system may include one or more machine systems. Each machine system may include a power unit and an implement. In some embodiments, the implement is a subordinate unit, relying on the power unit to provide motive and work power. In some embodiments, the implement may include one or more smart implement features, such as a communication system, a sensor system, or task-specific controls.

[0010] In some embodiments, the power unit may include a communications device configured to transmit machine system information and receive machine system commands and a set of profile information. The machine system commands may be mission plans for execution with the implement. These updates and commands may be transmitted via any available communications corresponding to available communications modules provided in the power unit.

[0011] The power unit may also include a controller that controls the operation of the power unit and any implements attached thereto. The controller may be a system with a computer for processing and driving control actuators for the entire power unit. The controller may also collect real-time operation information by receiving feedback about the operation through various operation sensors, such as on-board sensing systems, proximity sensors, position systems, workload sensors, and other sensor systems. In some embodiments, the implement may include a sensor system for outputting further feedback to the controller.

[0012] In some embodiments, the power unit may send status updates to the remote system and receive updated machine system commands from the remote system. The remote system may process and send a mission plan, which may include the machine system commands, to the power unit. In some embodiments, the mission plan may include applicable implement profile information and connection profile information. In some embodiments, the implement profile information and connection profile information may already be stored in the power unit along with the power unit profile information. In some embodiments, a temporary operating profile may be generated from and utilized in place of the power unit profile, implement profile, and connection profile.

[0013] Some embodiments of the planning and operations system include a remote cloud management system and a control system. The remote cloud management system may receive communications from machine systems. In some embodiments, the remote cloud management system may also receive communications from other sources, such as power unit data sources, implement data sources, and project request data sources.

[0014] In some embodiments, the remote cloud management system includes storage for holding and managing profile information, mission planning rules, constraints, and command sets. In some embodiments, the cloud management system includes a profile generation system that builds profiles for power units, implements, and connections between the power units and implements.

[0015] In some embodiments, a cloud management system assists in generating a mission plan. The cloud management system may receive a mission plan request from the control system that frames the mission plan project to be accomplished. The control system may include a dedicated user interface. In some embodiments, the remote user interface accesses the control system via a wireless network connection, such as a mobile phone application.

[0016] In some embodiments, framing a project for mission planning may include identifying account information, project location or boundaries, available materials, power units and implements, project goals, project constraints, and other information. In some embodiments, a control system may be used to define a mission plan using information from a cloud management system, including profile information.

[0017] In some embodiments, the remote cloud management system may include an automation system that generates a mission plan based on the power unit profile, the implement profile, and the mission activity. [Brief explanation of the drawings]

[0018] Embodiments will now be described, by way of example only, with reference to the accompanying drawings, in which:

[0019] [Figure 1] 1 illustrates an embodiment of a machine system with a tow implement. [Figure 2] 1 illustrates an embodiment of a machine system with a leading implement. [Figure 3] 1 is an embodiment of the implement. [Figure 4] 10 is another embodiment of the implement. [Figure 5] 1 shows a planned route including specific examples of movement in a field. [Figure 6]FIG. 1 is an embodiment of a system block diagram. [Figure 7] 10 is an embodiment of an operational flowchart for generating a connection profile. [Figure 8] 1 illustrates one embodiment of an operational flowchart for generating a mission plan. [Figure 9] 10 is an embodiment of a system flowchart for a power unit to load a mission. [Figure 10] 1 is an embodiment of a system flowchart for executing a mission plan. DETAILED DESCRIPTION OF THE INVENTION

[0020] While the present invention can be embodied in many different embodiments, preferred embodiments of the present invention will be described in detail, with the understanding that the present disclosure should be considered as an exemplification of the principles of the invention and is not intended to limit the broad aspects of the invention to the illustrated embodiments. It will be understood that the present invention can be embodied in other specific embodiments without departing from its spirit or central characteristics. The present embodiments, therefore, are to be considered in all respects as illustrative and not restrictive, and the invention is not to be limited to the details set forth herein.

[0021] Figures 1 and 2 show the machine system with the power unit and attached implement. Illustrated is an example of a power system. A power unit can be any type of machine that drives an implement to move and provide power. The power unit can be designed for projects such as agriculture, mining, construction, turf, logistics, etc. The power unit can include one or more power connections, such as an electrical connection, a hydraulic connection, or a power take-off connection. An implement can be any detachable component that provides one or more options for performing a movement. The implement can be designed for projects such as agriculture, mining, construction, turf, logistics, etc.

[0022] 1 shows a shredder system 100 that includes a tractor 102 that operates as a power unit and a rotary cutter 104 that is an implement used for shredding. In this system, the implement (rotary cutter 104) follows behind the power unit (tractor 102) during operation.

[0023] The rotary cutter 104 connects to the tractor 102 via an implement connection 106. The implement connection 106 may include a physical support connection and a power transfer connection. As used herein, a physical support connection includes a hitch on the power unit side and a hitch frame on the implement side. As will be understood by those skilled in the art, a hitch and hitch frame refer to any structure for providing a physical support connection between a power unit and an implement. A power transfer connection, as used herein, refers to any power supply connection from the power unit to the implement. As used herein, a power transfer connection includes a power output or power drive on the power unit side and a corresponding power takeoff or power drive on the implement side.

[0024] In this embodiment, the implement connection 106 includes a three-point hitch frame for supporting the front of the rotary cutter 104. This connection also allows the tractor 102 to raise and lower the rotary cutter 104 for use, height adjustment, and transport positioning. The implement connection 106 also includes a power take-off connection, which may include a driveline universal joint that adaptably connects to a power take-off shaft. A second end of the driveline connects to a gearbox 108 of the rotary cutter 104, where rotation of the driveline is converted into rotation of the rotary cutter blade.

[0025] In some embodiments, the tractor 102 includes an automated control system that may include an electronic control unit 110 operatively connected to actuators, sensors, and other equipment to operate the machine autonomously. The electronic control unit 110 may include a computer system with a processor, microcontroller, memory, and other structural components for managing and operating the autonomous control. For example, the electronic control unit 110 may control the direction and speed of the tractor 102 by driving a machine actuator system having multiple actuators and motion controls to control steering and speed. The machine actuator system may control power output. The electronic control unit 110 may also control additional functions associated with the implement attachment 106 and power transfer, such as lifting and lowering the implement attachment 106 and controlling a power take-off system. In some embodiments, the control system may be connected to a sensor system associated with the implement attachment 106 to determine operating conditions, such as drag adjustment, speed adjustment, or other implement conditions.

[0026] FIG. 2 shows a shredder system 200 having a skid steer loader 202 operating as a power unit and a skid cutter 204, which is an implement used for shredding. In this system, during operation, the implement (skid cutter 204) is powered by The skid cutter 204 is located in front of the skid steer loader 202 and is pushed forward. The skid cutter 204 connects to the skid steer loader 202 via an implement connection 206. The implement connection 206 may also include a physical support connection and a power transmission connection. In this embodiment, the implement connection 206 includes a hitch frame of the skid cutter 204 that corresponds to a hitch plate on the front of the skid steer loader 202. This connection may allow the skid steer loader 202 to raise and lower the skid cutter 204 for use, height adjustment, and travel position. Additionally, the implement connection 206 may include a hydraulic connection, allowing the hydraulic system of the skid steer loader 202 to power the skid cutter 204.

[0027] The implementation of the implement connections 106 and 206 may vary depending on the choice of implement and power unit. Additionally, the connection system may be modified with intermediate components such as quick hitch connections or other accessory connection systems.

[0028] The skid steer loader 202 includes a lift arm 212 and a hitch control unit 210. Both of these are driven by the hydraulic system of the skid steer loader 202, and the lift arm 212 controls the lifting and lowering of the implement, and the hitch control unit 210 controls the rotation of the implement.

[0029] In some embodiments, the skid steer loader 202 includes an automated control system that may include an electronic control unit 214 operatively connected to actuators, sensors, and other equipment for autonomously operating the machine. The electronic control unit 214 may have a computer system including a processor, microcontroller, memory, and other structural components for managing and operating the autonomous control. As described above with respect to the electronic control unit 110, the electronic control unit 214 of the skid steer loader 202 may drive multiple actuators and motion controls to control the operation of the skid steer loader 202, including the drive, arm control hydraulics, and skid cutter 204. In some embodiments, the control system may be connected to a sensor system associated with the implement interface 206 to determine operating states and conditions.

[0030] Figures 3 and 4 show a rotary cutter 104 and a skid cutter 204 according to the prior art. These figures provide a clearer view of the implement connections. Figure 3 shows a three-point hitch frame including a top connection 122 and side pins 124, 126. A corresponding three-point hitch on a power unit, such as a tractor 102, attaches to each of these points. Also shown is a universal joint 120 for connecting a power take-off.

[0031] 4 shows a hitch frame for the skid cutter 204 with a first top angle bar 220 and a second top angle bar 222. The hitch frame includes corresponding slots below the top angle bars 220 and 222 to securely connect to the hitch of the skid steer loader 202 and provide movement, angle, and elevation control functions for the skid cutter 104. Additionally, a number of hydraulic hoses 208, including end couplers, are shown for connecting the control 216 of the skid cutter 204 to the hydraulic system of the skid steer loader 202.

[0032] 5 illustrates a field representation of a planned path 310 with example transitions (movement examples) for discussion purposes. In this illustration, a power unit 302 leads an implement 304, and this machine system is shown in different positions along the planned path 310. The various positions of the machine system indicate movement behavior associated with the mission.

[0033] The planned path 310 is shown to follow a serpentine path from start to finish, including multiple parallel traverses through the field and multiple headland turns 312 to transition from each leg of the planned path 310. Alternative planned paths may be constructed, as will be appreciated by those skilled in the art.

[0034] For purposes of discussion, this planned path 310 illustrates mowing operations in the area of ​​the field covered by the parallel legs of planned path 310. Thus, the mission plan, in this example, commands the machine system to mow the parallel legs of planned path 310 and not mow during headland turn 312. The example move begins with operation 320, in which power unit 302 lowers implement 304 to a selected mowing height and provides work power to implement 304. Using machine system 100 as an example, electronic control unit 110 of tractor 102 signals the three-point hitch to lower rotary cutter 104. Electronic control unit 110 then signals the power take-off to operate at the operating speed of rotary cutter 104.

[0035] The power unit 302 continues along the planned path 310 with the implement 304 mowing. As the power unit 302 approaches the end of the first leg of the planned path 310, it reaches the next transition operation 322. In this operation 322, the automation system raises the implement 304 so that it does not mow while turning the headland 312. In some embodiments, the automation system may also disconnect the power output driving the implement 304.

[0036] The power unit 302 passes through the headland turn 312. In operation 324, the automated control system causes the power unit 302 to lower the implement 304 and resume mowing along a different path. This pattern continues until the power unit 302 reaches the end of the last leg of the planned path 310.

[0037] In operation 326, the automated control system disconnects the power supplied from the power unit 302 to the implement 304 so that the implement 304 finishes mowing. The automated control system also causes the power unit 302 to lift the implement 304 for transition to the next operation or for moving to a staging area.

[0038] In other embodiments, the implement 304 may travel ahead of the power unit 302. In such embodiments, the timing of the implement 304 engaging (driving) / disengaging (disengaging) and raising / lowering to cover the same space in the operation remains substantially the same as in the previous embodiment. While the operation remains the same from the implement 304's perspective, the power unit 302 following the implement 304 will be in a different position in the field when the operation occurs than the leading power unit 302 shown in FIG. 5.

[0039] FIG. 6 illustrates an embodiment of a networked ecosystem using a cloud system 400 for managing and generating mission plans and component profiles for an automated system of multiple work vehicles, including a machine system using a power unit and implements. In this embodiment, the cloud system 400 includes a mission planning system 402, a profile storage 404, and a profile generation system 406. In some embodiments, the mission planning system 402 manages one or more of the mission plans. It may also include subsystems that manage the creation of components, for example, some embodiments may include a machine information analysis system, a profile control analysis system, an activity program analysis system, a path planning system, or other system components.

[0040] In some embodiments, these system components may be separate components or one or more dedicated servers within cloud system 400. In other embodiments, multiple system components may be integrated. In some embodiments, some system components are provided internal to mission planning system 402, while other system components are operably connected to provide services to mission planning system 402 via wireless connections, wired network connections, or direct wired connections such as a bus interface.

[0041] Profile storage 404 may be any type of electronic storage structure or memory device. Additionally, the profiles stored in profile storage 404 may be stored in a variety of formats within the memory structure, such as a database, an indexed file system, or other formats. In some embodiments, cloud management system 400 may include additional storage for storing additional machine information, mission data, user information, operational assets, command scripts, and other information. In some embodiments, cloud management system 400 may include a script selection database containing power unit commands for integrating into a mission plan and instructing the power unit control system on how to operate. These scripts are modifiable based on the profile information.

[0042] The mission planning system 402 may access or receive information from the profile storage 404 or other storage sources. In some embodiments, the mission planning system 402 may also send information to the profile storage 404 or other storage options.

[0043] In some embodiments, the profile storage device 404 maintains profiles for multiple components and multiple connections. These profiles include power unit profiles, implement profiles, connection profiles, and other profiles. The component profile for each power unit, implement, or other component may include detailed identification information, operational information, and other component-specific characteristics. Identification information may include component manufacturer and model data, serial numbers, owner or user information, and / or other identification information.

[0044] The power unit profile may function as a configuration or information file utilized by the power unit or mission planning system 402. In some embodiments, the power unit profile may include mission plan translation control instructions and may be utilized by the power unit in combination with the mission plan to execute the mission plan instructions. For example, the power unit profile may include control instructions to identify and control specific components, such as the front hitch and rear hitch.

[0045] The implement profile may function as a configuration or information file utilized by the power unit or the mission planning system 402. In some embodiments, the implement profile may include mission plan translation control commands and may be utilized by the power unit in conjunction with the mission plan to execute the mission plan commands. For example, the implement profile for a smart implement may include a configuration file for a smart implement. The profile may include control commands for the power unit to communicate with the implement. Additionally, the implement profile may include operational information for smart features, including version information, that may affect the functionality of the components (features). For example, the implement profile may specify that the implement includes a version 1 sensor array. The mission planning system 402 may determine the functionality that the version 1 sensor array provides to the implement.

[0046] The connection profile may function as a configuration or information file utilized by the power unit or the mission planning system 402. In some embodiments, the connection profile may include mission plan translation control instructions and may be utilized by the power unit in conjunction with the mission plan to execute the mission plan instructions. For example, the connection profile may specify modifications to power unit operations to account for connected implements. As another example, the connection profile may associate power unit controls to perform tasks.

[0047] In some embodiments, the connection profile may further provide compatibility limitations or characteristics based on smart features available on the implement, such as precision control, sensor systems, or other capabilities. For example, the connection profile may limit the availability of an implement sensor system based on the version and feedback capabilities of the sensor system. As another example, the connection profile may support high-precision operation based on advanced systems available on the implement.

[0048] The cloud management system 400 also includes a profile generation system 406 that can generate new profiles and update existing profiles. The profile generation system 406 may generate a power unit profile from information about the characteristics, performance, and automatic control system of the power unit. Similarly, the profile generation system 406 may create an implement profile from information about the characteristics, performance, and control system of the implement. The profile generation system 406 may generate a connection profile based on the implement profile information and the power unit profile information. An example of a process for generating a connection profile is shown in FIG. 7.

[0049] The profile generation system 406 can access and receive information from the profile storage device 404 and other storage sources. In some embodiments, the profile generation system 406 can also send information to the profile storage device 404 or other storage options.

[0050] In some embodiments, the mission planning system 402 operates on the same structure, such as a server, as the profile storage device 404 and other storage. In some embodiments, the profile generation system 406 also operates on the same structure as the mission planning system 402. Within the cloud architecture 400, the mission planning system 402 may be connectable to the profile storage device 404 via one or more communication systems, depending on the underlying server array architecture. For example, the mission planning system 402 may be implemented on a first server using a processor and program memory connected via a wired bus. When evaluating a profile, the mission planning system 402 may use the first server's communication card to access the Internet or other network when connecting to the profile storage device 404. Similar communication options may be implemented to connect the profile generation system 406 to the profile storage device 404.

[0051] In some embodiments, the speed of evaluation can be increased through parallel processing operations by sharing the processing operations among multiple processors or separate computers. For example, When identifying applicable profiles, mission planning system 404 may perform parallel processing of assigned sections of profile storage 404 to identify applicable power unit profiles, implement profiles, and connectivity profiles. As another example, mission planning system 402 may assign separate computers to process two independent project requests in parallel.

[0052] In this embodiment, the profile generation system may receive data from a power unit data source 418 and an implement data source 422. This system embodiment may include any number of power unit data sources 418 and implement data sources 422. These data sources 418, 422 may include external user interfaces, such as phones, computers, server systems, tablets, etc., utilized by manufacturers, mechanics, machine users, aftermarket suppliers, etc. Additionally, the profile generation system 406 may receive information directly from the power units 410, 412. In some embodiments, the smart implement may include communications capabilities to enable the implement 420 to send implement information directly to the profile generation system. In other embodiments, the power unit 410 may receive information from communications with the implement 420 or from machine-readable data provided on the implement 420. The power unit 410 may then forward information about the implement 420 to the profile generation system 406.

[0053] In some embodiments, power unit data source 418 and implement data source 422 provide information to cloud management system 400 via information collection storage accessible to profile generation system 406. In some embodiments, mission planning system 402 may output feedback or other information regarding the power unit or implement to profile generation system 406.

[0054] In this embodiment, a single project request source 414 is identified. In other embodiments, the system may have multiple project request sources. The project request source 414 may be an external user interface, such as a phone, a computer, a server system, a tablet, etc. In some embodiments, the project request source 414 may be an operator of the cloud management system 400.

[0055] Mission planning system 402 may receive requests from project request sources 414. In some embodiments, mission planning system 402 may translate the project requests into a standard format for parsing and analysis. For example, a project request received from project request source 414 may be a natural language request from a project manager, such as a request received in a voice format. Mission planning system 402 may convert the voice to text and identify a definition of the project.

[0056] The mission planning system 402 may generate scripts necessary to realize the project based on the project requirement analysis, profile information, and command scripts. In some embodiments, the mission planning system 402 may generate a mission plan that provides commands that direct the operation of implements and the execution of path plans. The power unit may convert the operation and movement timing of the implements into executable commands based on modifications to the power unit profile and connection profile.

[0057] The mission planning system 402 may then transmit the mission plan to each power unit 410, 412. Communication of the mission plan may be performed via a communications system network card. may be used to transmit the signal to the communication module and electronic control unit in each power unit 410, 412 via one or more communication channels.

[0058] There may be any number of power units 410, 412. In some embodiments, the power units may communicate with smart implements, such as power unit 410 and implement 420. In other embodiments, all communication is limited to power units, such as power unit 412, which does not have a communication device. It is worth noting that power unit 412 may be connected to implements that do not communicate, such as the prior art cutter shown in Figures 3 and 4.

[0059] In some embodiments, power units 410 and 412 may be the same type of machine. For example, power units 410 and 412 may both be tractors. In other embodiments, power unit 412 may be a different type of machine than power unit 412. For example, power unit 410 may be a tractor designed to pull a shredder, and power unit 412 may be a skid steer loader designed to push the shredder.

[0060] One embodiment of a flow chart for creating a connection profile is shown in Figure 7. The connection profile provides a translation framework to account for specific implement and power unit configurations.

[0061] At decision box 502, the system determines whether an implement profile is available. For example, the profile generation system 406 may access the profile storage device 404 to determine whether an implement profile for the identified implement is stored in the profile storage device 404. Alternatively, the profile generation system 406 may send a query signal to the profile storage device 404 to determine whether an applicable implement profile is available. In some embodiments, the implement profile may be stored in a third-party storage device that the system can access to obtain the implement profile.

[0062] If an implement profile is available, the system proceeds to decision box 504 to determine whether a power unit profile is available. Similar to determining the availability of an implement profile, the system may access storage or send a query to obtain availability information. While decision boxes 502 and 504 are shown in order, in other embodiments, these decisions may be made in either order or in parallel.

[0063] If a power unit profile is available, the system proceeds to box 506, which in this embodiment receives the implement profile and the power unit profile. In some embodiments, the step of receiving the implement profile and the power unit profile may be integrated into the determining step(s). For example, when profile generation system 406 accesses profile storage 404 to determine the availability of an implement profile or a power unit profile, profile generation system 406 may download copies of the profiles once these profiles are identified. Similarly, an inquiry regarding the availability of a profile may include a request for a profile identified as available.

[0064] In this example, the implement profile and the power unit profile are received in this process. Instead of receiving a copy of the profile, the embodiment Those skilled in the art will appreciate that receipt and access may rely on accessing information in a stored profile. Management of receipt and access may depend on the architectural configuration of cloud management system 400 with respect to storage options, processing power, communication speeds, and bandwidth. In some embodiments, cloud management system 400 may be designed to be flexible to support different options based on the current situation.

[0065] If it is determined in decision box 502 that an implement profile is not available, the system may proceed to box 508 and generate and save a new implement profile. The system may obtain information about the implement's features, specifications, operating options, capabilities, constraints, connection formats, and other information. This information may come from an implement data source 422, such as an implement manufacturer's system.

[0066] Using this information, the system may generate an implement profile that includes information required for the job, including size, steering and propulsion effects, activity definition, implement function definition, implement capabilities and constraints, and other information that may affect the operation of the machine system by the power unit, and the system may save the implement profile.

[0067] Similarly, if a power unit profile is not available, the system proceeds to box 510 to generate and store a power unit profile. This system follows a similar pattern to generating an implement profile. Specifically, the system collects power unit information, including power unit operation, characteristics, controls, constraints, connections, automation systems and commands, and other information. This information is used to generate and store the power unit profile.

[0068] Once the implement and power unit profiles are generated and available, the system receives the new implement and power unit profiles in box 506. As will be appreciated by those skilled in the art, in some embodiments, the newly generated profiles may already reside in the profile generation system, skipping the receiving step. In other embodiments, different profile generation systems may be utilized for different types of profiles. For example, a system may include an implement profile generation system, a power unit profile generation system, and a connectivity profile generation system. In such cases, the profiles, regardless of their generation or storage source, must be received by the connectivity profile generation system.

[0069] Once the system receives the implement profile and power unit profile, it proceeds to box 512 and generates a geometric definition of a combined machine system using the selected power unit and implement. The system evaluates the power unit profile and implement profile to determine the applicable connection system and geometric effect when the implement is attached to the power unit. For example, the system may determine the length of the machine system as the sum of the length of the implement and the length of the power unit, minus the overlap caused by the connection. As another example, the system may determine the travel width based on the widths of the implement and power unit, and the working width based on the working range of the implement.

[0070] As will be appreciated by those skilled in the art, geometric information is required to control the motion of the combined machine system. The information may determine the options and constraints for the operation, the field extent of the operation, the options and constraints for the route, and other information.

[0071] In some embodiments, the power unit profile, implement profile, and shape (geometric) information may be used to generate integrated telematics data for a combined unit that combines the power unit and implement. The integrated telematics data may be selected or converted from a collection of power unit telematics data and implement telematics data. In some embodiments, if the implement does not have separate telematics data, the integrated telematics data may be based on a conversion to power unit telematics data. The conversion or selection process for obtaining the integrated telematics data may be defined in the connection profile.

[0072] In box 514, the system defines system operational functions by associating implement functions with power unit functions. The system may analyze the implement profile and power unit profile to determine which implement functions are compatible with the power unit. Compatible functions may be associated with power unit operation to drive the implement. For example, a fertilizer applicator driven from a power take-off (PTO) may provide various fertilizer application range options based on the PTO revolutions per minute (RPM). The power unit's automated controls may be associated with the PTO requirements for each option. This correlation allows the power unit to know the PTO speed to apply to the option for the implement function. The system associates the implement options with the selected power unit's output control.

[0073] Additionally, various functions related to different power unit systems may be provided. For example, one implement may have a function that operates using mechanical power from the power unit's hydraulic system and a second function related to electrical connections. The automated control of the power unit for these implement functions may be related to the automated control of the outputs of the hydraulic and electrical systems.

[0074] Similarly, connection controls may also relate to effects on the implement. For example, an implement height condition may relate to a hitch control on a power unit.

[0075] In box 516, the system defines capabilities and constraints based on the combined options, including omitting unsupported features. The defined capabilities and constraints include those related to steering and propulsion (driving), as well as work control. The system may define, for example, turning radius constraints, speed constraints (minimum and maximum speeds), implement working envelope, and other information. In some embodiments, the system defines capabilities and constraints for non-work and work operations. For example, during work, the power unit may be limited to a certain driving speed and require a set PTO power output.

[0076] As an example of defining capabilities and constraints, a PTO-driven fertilizer application implement may offer different fertilizer application range options based on the PTO's revolutions per minute. If a power unit offers a limited revolutions per minute range to the PTO, the power unit may only be able to drive a subset of the implement's application range options. The system associates the options that a selected power unit supports as features with the unsupported ranges as unsupported features.

[0077] In some embodiments, unsupported features are simply features that the system can select. In other embodiments, unsupported functions may be included in the connection profile as disabled options. When defining the capabilities and constraints, the system may identify the work provided by the implement that performs the associated control actions required from the power unit.

[0078] In box 518, the system generates and saves a connection profile based on the combined definitions and correlations. The connection profile may include modifications to, replacement information for, or additional information to the power unit profile. In this embodiment, because the automated control is part of the power unit, the connection profile converts the implement information used by the power unit based on the power unit profile. In some embodiments, when a combined machine system is used, the connection profile may be designed as a working profile to be used in place of the power unit profile. The connection profile may be stored in a profile store for use by the mission planning system or updated by the profile generation system.

[0079] FIG. 8 illustrates one embodiment of a process for generating a mission plan. The process begins in box 602, when the system receives mission identification data, including a work area and operational activity. In some embodiments, a mission request signal (request signal) may be received via a remote user interface on a computer, smartphone, tablet, or other device. A user may select a work area and operational activity via the user interface. For example, a user may select a field and a crushing operation as the activity. In some embodiments, these may be presented as selectable options in the user interface. In some systems, a user may enter information via a form or other input option. The user input is received and parsed into project information for the mission, including work area locations and activity definitions that correspond to operations available in the system.

[0080] In box 604, the system receives identification information for implements that support the identified operational activity. In some embodiments, a user may select an implement from the system that can perform the task. The system may already have a list of implements available for the user to select from. In some embodiments, the system may narrow the set of available implements to those that have functionality corresponding to the selected operational activity. The user may then select an implement from the narrowed list.

[0081] In box 606, the system receives the identification of a power unit that supports the implement. Similar to selecting an implement, here the user may select from a broad or filtered list. For example, after an implement is selected, the power unit options available for selection may be limited to those that support the physical and power connection types required by that implement.

[0082] In some embodiments, the system may automatically identify implements and power units for a selected mission. The system may evaluate performance, condition, and other information to select appropriate implements and power units for the mission. Once selected, the system may transmit identification of the selected implements and power units to the user. The user may then approve or change the system's selection.

[0083] Once the mission, power unit, and implement information is selected, the system determines whether a connection profile for the selected power unit and implement combination is available in decision box 608. For example, mission planning system 402 may access or send a query to profile storage 404 to determine whether an appropriate connection profile is available. If a connection profile is available, the system receives the connection profile for the implement and power unit combination in box 610. As with the other receiving steps, other embodiments may utilize the connection profile without receiving a copy. For example, the mission planning system may access and retrieve only the necessary information from the connection profile stored in profile storage 404.

[0084] If a connection profile is not available, the process proceeds to box 612, where the system generates and saves a connection profile. By way of example, the connection profile may be generated as shown in Figure 7. Once generated, the process returns to box 610, where the process receives the connection profile.

[0085] In another embodiment, mission planning system 402 may determine that a connection profile for the selected power unit and implement does not exist in profile storage 404. Mission planning system 402 may send a request signal to profile generation system 406 to create a connection profile. Profile generation system 406 may generate a new connection profile and send the connection profile to mission planning system 402 to continue the process.

[0086] In box 614, the system generates a planned path for the mission using the connectivity profile. The system may determine the work path required to move and operate the implement to perform the operational activity in the selected work area. The planned path may provide a preliminary driving plan for the power unit to move the implement required for the project. The system may analyze the connectivity profile to identify the work area of ​​the implement and the operating conditions of the composite machine system (combining the power unit and implement). These conditions and constraints allow the system to define a planned path for this combination.

[0087] In box 616, the system generates implement operations for the planned path. As a first part of this step, the mission planning system 602 defines the implement's operations along the planned path. For example, the implement may mow along the active area of ​​the planned path, but may not mow a particular headland in the field and may instead turn. The mission planning system 602 may identify the active area as a work area and the inactive area as a non-work area. As will be appreciated by those skilled in the art, operations in a work area can be more complex. Some implement operations require more detailed instructions regarding their operations; for example, a hay baler may require a change of schedule between collecting hay and releasing the hay bale.

[0088] In some embodiments, the mission planning system 602 may further define operational control of the power unit to operate the identified implement operation. For example, when the mission plan identifies that the implement operation is active on the planned path, the mission planning command may use the connection profile information to command a specific PTO rotation speed to drive the rotary cutter implement at an appropriate rotational speed. For other machine systems, the mission planning command may define a hydraulic flow rate for a hydraulically driven rotary cutter.

[0089] As will be appreciated by those skilled in the art, the same implement task and path may be translated into planned paths and power unit motion control commands for different machine systems, allowing for versatility that can be achieved through modification information incorporated into the connection profile. This also allows for user project selection to correspond to implement task definitions that can be translated by the system into automation control commands.

[0090] In box 618, the system generates and saves a mission plan using the planned path and implement operations. The generated mission plan can comprise a specific machine system compiled from individual power units and implements. The generated mission plan is flexible for implementation on other systems based on the implement operations, and can be generated for connection profiles that convert general implement operations into automated commands for the actual machine system.

[0091] The system may store the mission plan for later use or transmit the mission plan to the power unit for future execution. In some embodiments, the mission plan is transmitted to a user for uploading to the power unit. Implements may be, or are to be, installed prior to executing the mission plan at a set staging area. In some embodiments, the mission plan may include a pre-assembly command set. In some embodiments, the pre-assembly command set may include automated implement connection.

[0092] Figure 9 shows the loading process for the power unit's electronic control unit to describe the attached implement. The data loading process and operation again uses the connection profile to guide the modifications and ancillary performance of the power unit and implement combination.

[0093] In box 702, the process begins by loading the power unit profile, implement profile, and connectivity profile into the power unit's electronic control unit. In some embodiments, the loading of the profiles occurs via a local connection, such as a wired system or a portable memory device, or via short-range communication, such as Bluetooth®, Wi-Fi, or other communication standards. In some embodiments, the loading process may occur directly and remotely via a remote communication system. For example, a power unit with long-range communication capabilities, such as a cellular connection, may receive a download directly to the power unit from a cloud management system via a cellular network. In some embodiments, the loading process may occur via a remote communication system and a local communication hub. For example, a garage where the power unit is stored may be equipped with a wired internet communication system that transmits information to a local Wi-Fi hub in the garage. A download signal is received at the hub from the internet communication system and processed by the power unit via a Wi-Fi communication signal.

[0094] The loading process may depend on the power unit's available connections and communication systems, as well as the availability of communications at the power unit's location. For example, even if the power unit has cellular communication options, portable memory may be required in remote locations without cellular connectivity.

[0095] In box 704, an electronic control unit in the power unit uses a connection profile to map (associate) implement operations with corresponding machine operations. For example, a connection profile may be used to map (associate) the operation of a fracturing implement to a hydraulic system at a specified flow rate. A connection profile may be defined to correspond to a machine operation for controlling a particular line of equipment. Similarly, an implement operation may include preset height conditions that must be translated via a connection profile into hitch control commands to raise, lower, and level the hitch as needed. These controls and adjustments may be mapped to an electronic control unit for operation of the machine system using the implement.

[0096] In box 706, the electronic control unit disables machine selection for unsupported implement tasks and machine operations based on the connection profile. Some combinations of machine systems may not support all implement functions or may exclude certain power unit functions. As an example, an implement with multiple operational settings requiring different power outputs may include one or more power outputs that the power unit cannot accommodate. In such machine systems, the electronic control unit indicates that the unsupported settings are disabled.

[0097] In this step, the electronic control unit disables the option to select such a feature during operation. This option may be disabled by removing it from the options of the electronic control unit. In other embodiments, the electronic control unit may generate a flag indicating that the feature is unavailable. As will be appreciated by those skilled in the art, the process for disabling such a feature may vary from system to system.

[0098] In box 708, the electronic control unit applies operational scaling between the implement and the power unit based on the connection profile. In this step, the electronic control unit performs the necessary scaling between the power unit and the implement to ensure that the power unit's operation corresponds to the required operational output of the implement. For example, if a rotary cutter requires a certain rotational speed to mow a standard field at a predetermined speed, the electronic control unit scales (adjusts) the power unit's travel speed to the PTO speed required to properly drive the rotary cutter. As another example, the electronic control unit may change the control output to raise or lower the implement to a set height. In the connection profile, scaling may relate the height of the hitch to the height of the corresponding implement. This scaling may also include adjustments to the power unit's turning radius, working pattern, etc.

[0099] 10 illustrates one embodiment of a mission execution process. The process begins in box 802 with selecting a mission to execute. In some embodiments, a user may select a mission to execute via an on-board or remote user interface. In some embodiments, the selection may be automatic by the system based on prior scheduling or system evaluation. Remote selection is available for any power unit available via one or more communication configurations, such as direct and indirect remote communication options.

[0100] In some embodiments, once a user selects a mission, the mission is queued for execution. The system may send the user pre-requisite meeting points, configuration, or other information to verify pre-execution requirements. For example, the system may send the user a meeting point and ask questions to verify that mixed fertilizer is loaded for a fertilizer project. In some embodiments, the system may also provide projected fuel to avoid refueling or request that a tanker aircraft be available based on the scope of the project.

[0101] In box 804, the power unit and implement are assembled based on the initial conditions of the selected mission plan. Some embodiments may require the machine system to be in an assembly area and installed for operation. In other embodiments, the mission plan may be configured to automatically connect the power unit to the selected implement, so long as the implement and power unit are in a known location and properly pre-configured. In some embodiments, the system receives a signal confirming that the machine system is assembled and ready to begin execution.

[0102] In box 806, the system initiates the mission within the power unit's electronic control unit. In some embodiments, the system initiates the mission in response to a user's initiation signal. In other embodiments, the system may automatically initiate the mission based on the occurrence of one or more initiation triggers (events). For example, the system may initiate the mission within the electronic control unit upon verifying that the power unit is connected to an implement and positioned in a staging area. In some embodiments, the system may wait for a scheduled operating window or other auxiliary trigger. These triggers or requirements may be user-selected or determined by the system during mission setup. For example, the system may automatically check weather reports for suitable weather conditions prior to a hay bale mission.

[0103] In box 808, the power unit proceeds to execute operations along a planned path consistent with the mission plan. The power unit proceeds based on an automated control system in response to the electronic control unit executing the mission plan.

[0104] When executing an operation from the mission plan, the electronic control unit determines whether the operation in the mission plan is affected by the implement in decision box 810. The electronic control unit may check whether the operation source is from the power unit profile or the connection profile to determine whether the implement has affected the standard operation of the power unit. In some embodiments, the storage device of the electronic control unit into which the profile is loaded may include an index indicating the available operations and operation sources for efficient determination.

[0105] In some embodiments, the electronic control unit may utilize an operation profile that is a combination (compiled) of the power unit profile and the connection profile, and in such embodiments, the operation profile may provide all of the operational instructions that are to be applied to the assembled and connected machine system.

[0106] If operation is affected by the implement, the electronic control unit references the operation of the mapped power unit in box 812. For example, if the throttle for the selected speed is greater than the throttle required by the power unit alone, the operation of the mapped power unit may include adjusting the throttle to achieve the speed selected in the mission plan. As will be appreciated by those skilled in the art, the throttle system is one example of a propulsion system, and alternative propulsion systems may be utilized in some embodiments.

[0107] Once the power unit operation is determined by the mapping, the electronic control unit proceeds to box 814. If the power unit operation is not affected by the implement, the electronic control unit also proceeds to box 814. In box 814, the electronic control unit translates the operations of all implements to apply using the power unit operation. For example, The electronic control unit may execute a mission plan calling for mowing operations at a particular location by rotating the PTO at a set number of revolutions per minute to drive a rotary cutter implement. The electronic control unit translates the mowing operations into PTO drive requirements for the power unit for the attached implement. This translation may be provided by a connection profile loaded into the electronic control unit as an implement operation translation for the particular power unit.

[0108] In some embodiments, specific terms (language) for an implement may be translated into corresponding terms (language) for the power unit. For example, an implement profile may identify the term "PowerControl" that specifies the operation of the implement, while a power unit profile may refer to this control as "PTOControl." The connectivity profile associates modifications with power unit operation terms to correspond to the operation instructions of the implement.

[0109] As another example, another implement connected to the hydraulic drive system requires the electronic control unit to provide power through appropriate lines in the power unit's hydraulic system to drive the implement. In this example, the mission plan similarly defines an operation as mowing grass, and the electronic control unit translates this implement operation into the applicable control system of the power unit. For example, if the implement profile identifies the term "PowerControl" for the implement's operation and the power unit profile uses the term "Aux1Control," the connectivity profile associates the term and control for the power unit's operation to correspond to the implement's operational command.

[0110] In box 816, the electronic control unit determines whether the mission plan is complete. In some embodiments, the electronic control unit evaluates completion based on the presence or absence of further operational commands. In such cases, the mission plan may include ongoing operations to ensure that the position along the planned path has been reached. In some embodiments, the electronic control unit's determination evaluates the position along the planned path, enumerated additional tasks, emergency commands, and other information that may determine whether the mission plan is complete or aborted.

[0111] If the mission plan is not complete, the power unit continues processing the power unit and implement operations based on the loaded profile, which outputs any necessary modifications or translations, and the electronic control unit returns to box 808 to perform further operations consistent with the mission plan.

[0112] Once mission planning is complete, the electronic control unit terminates mission execution in box 818. In some embodiments, terminating mission execution may include post-mission automated actions. For example, if mission planning is completed at a location other than the assembly area or designated location, the electronic control unit may execute control commands to move the machine system to the designated location. In some embodiments, post-mission actions may also require applying modifications to operations via the connection profile.

[0113] In some embodiments, the power unit and / or implements may collect telematics data during operation. Such collection may occur periodically throughout operation, or when a specific action occurs that triggers data collection. In some embodiments, telematics data from the power unit and implements is collected by the power unit before being sent to the cloud management system. The telematics data is stored in the electronic control unit of the vehicle. Separate telematics data may be transmitted for the power unit and the implement.

[0114] In some embodiments, the electronic control unit may send a consolidated set of telematics data for the combined unit based on telematics data collection management information in the connection profile. For example, if the connection profile defines the power unit's telematics data as associated data, the consolidated telematics data sent to the server may match the power unit's telematics data. As another example, the connection profile may identify certain telematics data as power unit data and other telematics data as implement data, in which case the consolidated telematics data would be a selected combination of telematics data from the power unit and the implement. As yet another example, the connection profile may include a transformation analysis based on one or both sets of telematics data to generate consolidated telematics data for the combined unit.

[0115] As a general example, a user may remotely sign in to an account on the cloud management system 400 via the user's smartphone running an app for mission planning and selection. Once the user signs in to the account, the cloud management system 400 may guide the user through the mission request process based on information about the location of operation, power unit, and implement already loaded into the account. For example, the app may begin with a location selection option to enter an address, picture, name, or other information to identify available locations. For example, the user may select the farm field shown in FIG. 5.

[0116] Once the user selects a location, the system may present a selection of work activities for that location, such as mowing, fertilizing, terraforming, seeding, etc. For example, the user may select the mowing activity.

[0117] Once a location and activity are selected, the app may provide implementation options that support the selected work activity. For example, the app may present a series of mowers and chippers, including the rotary cutter 104 shown in FIG. 3 and the skid cutter 204 shown in FIG. 4. As an example, the user may select the rotary cutter 104.

[0118] Once an implement is selected, the app presents a selection of power units that support the implement. In this example, if the user selects a tractor 102, a range of power units with rear hitch and PTO drives may be presented.

[0119] If, at one or more stages of the selection process, the desired location or component has not yet been loaded, the user has the option to enter a new location or component. In this situation, the user must enter the corresponding profile or additional information in order for the system to generate a profile or field definition.

[0120] In some embodiments, the app may present options for additional restrictions or information to be selected or entered by the user, such as schedule information, meeting contacts, designated meeting or completion locations, weather requirements or other information.

[0121] Once the user has entered their requirements, the mission planning system 402 generates a mission plan based on the connection profile for the selected power unit and implement. As described above, the mission planning system 402 generates a mission plan based on the connection profile for the selected power unit and implement. If a connection profile for the power unit and implement is not available from the profile storage device 404, it may be determined that a connection profile is needed. The mission plan may include a planned route 310 for the selected power unit and implement. The planned route may include a work area where mowing is performed and a non-work area used for headland turns. The mission plan may further include implement work to be performed within the operational area. For example, the mission plan may output a mowing start command at the start of each leg of the planned route within the operational area. Furthermore, the mission plan may output a mowing stop command at the end of each leg within the operational area. The mission plan may output operation commands for the position and operation of the implement along the planned route instead of the position and operation of the power unit.

[0122] After the mission plan is completed, the cloud management system 400 may send the mission plan, power unit profile, implement profile, and connection profile to a local user at the field, who may be different from the planning user, for loading into the electronic control unit 110 of the tractor 102. In some embodiments, the power unit may be pre-loaded with one or more of the power unit profile, implement profile, and connection profile. This may be the case if the same machine system has been used previously and no updates are necessary. In such a situation, the mission plan may be all that needs to be loaded into the power unit. In some embodiments, the planning user or the local user may select the files to load to reduce unnecessary transfers.

[0123] In this example, the local user may connect the rotary cutter 104 to the tractor 102 as needed and move the machine system 100 to the assembly area. The mission is then executed according to the output planned path. When executing the mission, the electronic control unit 110 translates tractor 102 operations, such as steering control and propulsion (movement) control, as instructed by the connection profile. The electronic control unit 110 also translates implement operations, such as implement height setting and mowing, from the mission plan into corresponding tractor 102 operations, such as adjusting the height of the three-point hitch and engaging the PTO drive. When moving along the planned path 310, the tractor 102 covers the work area by entering the work area before driving the rear-mounted rotary cutter 104 and stopping the rotary cutter 104 before exiting the work area.

[0124] In an alternative example of the execution process, the local user may determine that the tractor 102 is unavailable and select to utilize the machine system 200 instead of the tractor 102 because the skid cutter 204 is the same width as the rotary cutter 104. To switch to the machine system 200, the local user may output a request to update the connection profile of the machine system 200 and a mission plan check to verify that the same mission plan is available for the machine system 200. The planned path from the mission plan may be applicable to the machine system 200 based on the similar motion and geometry of the two implements. For this swap, the system may verify that the non-working space can be set up and swiveled in the headland space in the first stage to use the same planned path.

[0125] From an operational standpoint, the connection profile of the machine system 200 modifies the motion of the skid steer loader 202 and helps translate the motion of the skid cutter 204 into the motion of the skid steer loader 202. This can be achieved based on a mission plan from the perspective of the implement. A mission plan that outputs a command to start a mowing operation at a predetermined position of the implement can be achieved by an alternative machine system 200. The electronic control unit 214 controls the skid steer loader 202 and the hitch control. The height of the skid cutter 204 is set by adjusting the height and level of the arm 212 with the control wheel 210. The electronic control unit then controls the hydraulic system of the skid steer loader 202 to operate the skid cutter 204. When the skid cutter 204 reaches the edge of the work area, the skid steer loader 202 either causes the skid cutter 204 to stop mowing or raises the skid cutter 204 to stop mowing.

[0126] Some embodiments of the power unit include an on-board obstacle avoidance system that modifies the operation of the power unit based on an obstacle. In some embodiments, the obstacle may be detected by a sensor system in the power unit or a sensor array in an attached implement. Once the obstacle is bypassed or processed by the obstacle avoidance system, the electronic control unit returns to the mission planning process. During operation, the obstacle avoidance system in the machine system may identify the obstacle based on one or more signals from the sensor or sensor array. The obstacle avoidance system may determine an avoidance action for the machine system to avoid the obstacle and return to the mission planning. The control unit in the power unit can implement the avoidance action by modifying the mission planning app. In some embodiments, the modification for the avoidance action can depend on the connection profile, as well as the movement behavior of the power unit, to adjust the implement work.

[0127] Most of the devices described above are comprised of hardware and associated software. For example, a typical work machine includes one or more processors and software executable on those processors to perform the operations described above. The term software is used herein in its commonly understood sense to refer to programs or routines (e.g., subroutines, objects, plug-ins, etc.) and data available to a machine or processor. As is well known, computer programs generally consist of instructions stored on a machine-readable or computer-readable storage medium. Some embodiments of the present invention may include executable programs or instructions stored on a machine-readable or computer-readable storage medium, such as a digital memory. The term "computer" in the traditional sense is not intended to imply that a particular embodiment requires a "computer." For example, various processors, both embedded and non-embedded, may be used in devices such as the components described herein.

[0128] Memory for storing software is well known. In some embodiments, memory associated with a given processor may be stored on the same physical device as the processor ("on-board" memory), such as RAM or FLASH memory located within an integrated circuit microprocessor. In other examples, memory may include a separate device, such as an external disk drive, a storage array, or a portable flash key fob. In such cases, memory is "associated" with a digital processor when the two are operatively coupled or able to communicate with each other, such as by an I / O port or a network connection, so that the digital processor can read files stored on the memory. Associated memory may or may not be "read-only" by design (ROM) or permission settings. Other examples include, but are not limited to, WORM, EPROM, EEPROM, and FLASH. These technologies are often implemented in solid-state semiconductor devices. Other memory may consist of moving parts, such as a conventional rotating disk drive. All such memory is "machine-readable" or "computer-readable" and may be utilized to store executable instructions for performing the functions described herein.

[0129] "Software Product" means a memory product containing a set of executable instructions stored in machine-readable form. The software product is intended for a remote device, and any suitable machine or processor with suitable access to the software product can execute the instructions to perform the process implemented by the instructions. The software product may also be used for software distribution. Any type of machine-readable memory can be used to create the software product, including but not limited to those described above. However, it is also known for software to be distributed by electronic transmission ("download"), in which case there will typically be a software product associated with the sender, receiver, or both.

[0130] While the invention has been described above and is further claimed, it will be apparent that the same may be varied in numerous ways. Such variations are not to be regarded as departing from the spirit and scope of the invention, and all such modifications which would be obvious to those skilled in the art are intended to be included within the scope of the described apparatus.

Claims

1. An autonomous machine system including a power unit and an implement, The power unit is a locomotion system including a steering system and a propulsion system; an implement connection system including a hitch and a power output; a control unit including a control unit processor and a control unit memory storing a power unit profile, a connectivity profile, and a mission plan; a machine actuator system including steering control, speed control, and power output control; an automatic sensor; the implement has an implement connection system including a hitch frame; the mission plan includes a planned route, a power unit operation command, and an implement work command; The connection profile includes modifications to the power unit operation commands, and the connection profile includes translations of implement operations, which in turn convert the implement operation commands into operation commands for the power unit to perform the implement; the control unit processor executes the mission plan using the power unit profile and the connectivity profile; When the control unit identifies one of the power unit operation commands from the mission plan and determines that the connection profile includes a corresponding implement modification, the control unit executes the modified power unit operation command based on the modification of the corresponding one of the power unit operation commands; When the control unit identifies one of the implement work instructions, the control unit applies the corresponding one of the implement work instructions to execute the corresponding one of the operation instructions for the power unit, an autonomous machine system.

2. the connection profile is received from a networked server system via a communications network; The autonomous machine system of claim 1 , wherein the connection profile is generated based on an analysis of the power unit profile and an implement profile corresponding to performance and characteristics of the implement.

3. the power unit is selected from a plurality of power units; The autonomous machine system of claim 1 , wherein the implement is selected from a plurality of implements.

4. The autonomous machine system of claim 1 , wherein the implement connection system has a power input that connects to a power output of the power unit.

5. The implement includes an on-board control; The autonomous machine system of claim 1 , wherein the connection profile includes a control command for the power unit to communicate with the implement.

6. The autonomous machine system of claim 1 , wherein the control unit generates integrated telematics data based on the connection profile.

7. An automation management system for a machine system, comprising a networked server system and a machine system, The networked server system includes: a server communications card configured to communicate over a communications network; A server memory drive; a server controller operatively connected to the server communication card and the server memory drive and configured to control communications via the server memory drive and the server communication card; The machine system includes one power unit selected from a plurality of power units and one implement selected from a plurality of implements, Each of the plurality of power units a locomotion system including a steering system and a propulsion system; an implement connection system including a hitch and a power output; a control unit including a control unit processor and a control unit memory storing a power unit profile, a connectivity profile, and a mission plan; a machine actuator system including steering control, speed control, and power output control; an automatic sensor; Each of the plurality of implements has an implement connection system including a hitch frame; the networked server system includes a mission planning system operated by the server controller in communication with the server memory drive; the mission planning system receives a mission request including a work area and a specified operational activity, and receives a selection of the power unit and the implement; the server controller operates the mission planning system to generate a mission plan from the mission request, the power unit, and the implement, along with the connection profile of the machine system including the power unit attached to the implement; the mission plan includes a planned path and an implement task; An automation management system, wherein the mission plan is readable into the control unit of the power unit and executable by the control unit using modification and translation information in the connection profile.

8. the networked server includes a profile generation system operated by the server controller in communication with the server memory drive; 8. The automation management system of claim 7, wherein the profile generation system receives and analyzes a power unit profile and an implement profile to determine the modification information for a power unit operation and the translation information for converting the implement work into the power unit operation to drive the implement work.

9. the machine system includes an obstacle avoidance system including at least one sensor; the obstacle avoidance system identifies an obstacle based on signals from the at least one sensor and determines an avoidance action for the machine system; The automated management system of claim 7 , wherein the control unit modifies the application of the mission plan based on the avoidance maneuver.

10. The automation management system according to claim 7 , wherein the implement connection system has a power input that connects to a power output of the power unit.

11. The implement includes an on-board control unit, The automation management system according to claim 7 , wherein the connection profile includes a control command for the power unit to communicate with the implement.

12. the networked server system receives the integrated telematics data from the control unit; The automation management system of claim 7 , wherein the control unit generates integrated telematics data based on the connection profile.

Images