Systems and methods for controller update and configuration of emissions certification level performance

Abstract

A system includes an exhaust aftertreatment system coupled to an engine and a controller. The controller includes at least one processor coupled to at least one memory device storing instructions that, when executed by the at least one processor, cause the controller to perform operations including determining an expected emissions level calibration parameter; receiving a new emissions level calibration parameter; comparing the expected emissions level calibration parameter to the new emissions level calibration parameter; and generating an alert based on a result of the comparison.

Description

[0001] Cross-reference to related applications

[0002] This application claims the benefit and priority of Indian Provisional Patent Application No. 202141005492, filed on February 9, 2021, the entire contents of which are incorporated herein by reference. Technical Field

[0003] This disclosure relates to configuring and updating controllers for detecting emissions tampering in various systems (e.g., vehicles including after-treatment systems) and enforcing emissions compliance. Background Technology

[0004] Many engines are coupled with exhaust aftertreatment systems that reduce harmful emissions such as nitrogen oxides (NOx), sulfur oxides, particulate matter, etc. For example, a reducing agent can be injected into the exhaust stream to chemically bind with particles in the exhaust. This mixture interacts with a selective catalytic reduction (SCR) catalyst, which initiates a reaction in the mixture at a specific temperature, converting harmful NOx particles into pure nitrogen and water. Emission levels are strictly regulated across various markets. Therefore, emissions from each vehicle must be monitored and validated during normal operation to ensure compliance or near-compliance.

[0005] Diesel engine manufacturers operate in a global market with varying emission regulations across different regions. Some markets have stricter regulations than others. A common approach to save costs and ensure compliance is to create and maintain numerous variants of similar engines. While this may reduce the selling price of individual products, it requires additional research and development for each. Furthermore, part proliferation occurs, necessitating complex parts sourcing and storage systems. Significant effort must be invested to ensure that each of these products meets internal standards, all of which have potentially unique guidelines. Therefore, the cost of correcting orders can be substantial when an incorrect product is sent to a customer. Moreover, it is difficult to ensure that various engine exhaust aftertreatment systems do not accidentally or maliciously receive updates that cancel the emission regulations originally used for that system. Summary of the Invention

[0006] One embodiment relates to a system including an exhaust aftertreatment system coupled to an engine and a controller. The controller includes at least one processor coupled to at least one memory device storing instructions that, when executed by the at least one processor, cause the controller to perform operations including: storing expected emission level calibration parameters; receiving new emission level calibration parameters; comparing the expected emission level calibration parameters with the new emission level calibration parameters; and generating an alarm based on the comparison result.

[0007] Another embodiment relates to an apparatus including one or more processing circuits, each including one or more memory devices coupled to one or more processors. The one or more memory devices are configured to store instructions thereon that, when executed by the one or more processors, cause the processors to: receive raw emission level calibration parameters; store the raw emission level calibration parameters in a secure location on the one or more memory devices; receive a flash or erase data command; and restore the raw emission level calibration parameters after receiving the flash or erase data command.

[0008] Another embodiment relates to a system including an exhaust aftertreatment system and a controller coupled to the exhaust aftertreatment system. The controller is configured to: receive raw emission level calibration parameters; store the raw emission level calibration parameters in a secure location on the controller; receive a requested recalibration parameter; determine the requested emission level calibration parameter associated with the requested recalibration parameter; compare the requested emission level calibration parameter with the raw emission level calibration parameter; induce when the requested emission level calibration parameter does not conform to the raw emission level calibration parameter; induce when the requested emission level calibration parameter conforms to the raw emission level calibration parameter; receive a flash or erase data command; and restore the raw emission level calibration parameter after receiving the flash or erase data command.

[0009] Another embodiment relates to a method comprising receiving raw emission level calibration parameters and storing the raw emission level calibration parameters in a secure location on a controller; receiving a requested recalibration parameter; determining the requested emission level calibration parameter associated with the requested recalibration parameter; comparing the requested emission level calibration parameter with the raw emission level calibration parameter; inducing a process based on the comparison between the requested emission level calibration parameter and the raw emission level calibration parameter; implementing the requested recalibration parameter when the requested emission level calibration parameter conforms to the raw emission level calibration parameter; receiving a flash or erase data command; and restoring the raw emission level calibration parameter after receiving the flash or erase data command.

[0010] Various aspects of this disclosure may be implemented in one or more of the following embodiments:

[0011] Project 1): A system comprising:

[0012] An exhaust aftertreatment system coupled to the engine; and

[0013] A controller, comprising at least one processor coupled to at least one memory device storing instructions, which, when executed by the at least one processor, cause the controller to perform operations including:

[0014] Store calibration parameters for expected emission levels;

[0015] Receive new emission level calibration parameters;

[0016] Compare the expected emission level calibration parameters with the new emission level calibration parameters; and

[0017] An alert is generated based on the comparison.

[0018] Project 2): According to the system described in Project 1), wherein the controller performs further operations, the further operations including: saving the expected emission level calibration parameters to the at least one memory device, and restoring the expected emission level calibration parameters based on power-on and power-off of the controller.

[0019] Project 3): According to the system of Project 2), saving the expected emission level calibration parameters to the at least one memory device includes: configuring the expected emission level calibration parameters as non-erasable, such that the expected emission level calibration parameters can be retained through multiple recalibrations.

[0020] Project 4): The system according to Project 1), wherein the controller performs further operations, the further operations including: adjusting the operating point of the engine in response to the alarm indicating a mismatch between the expected emission level calibration parameter and the new emission level calibration parameter.

[0021] Project 5): According to the system described in Project 4), adjusting the operating point of the engine includes at least one of the following: limiting the speed of the engine, limiting the torque of the engine, or shutting down the engine.

[0022] Item 6): An apparatus comprising:

[0023] One or more processing circuits, comprising one or more memory devices coupled to one or more processors, said one or more memory devices being configured to store instructions thereon, said instructions, when executed by said one or more processors, causing said one or more processors to:

[0024] Receive raw emission level calibration parameters;

[0025] The original emission level calibration parameters are stored in a secure location in one or more of the memory devices;

[0026] Receive flash memory or erase data commands; and

[0027] Upon receiving the flash memory or erase data command, the original emission level calibration parameters are restored.

[0028] Item 7): The apparatus according to Item 6), wherein the one or more memory devices are further configured to store instructions thereon, the instructions, when executed by the one or more processors, causing the one or more processors to:

[0029] Receive the requested recalibration parameters;

[0030] Determine the emission level calibration parameters for the request that are associated with the recalibration parameters of the request;

[0031] Compare the requested emission level calibration parameters with the original emission level calibration parameters; and

[0032] Induction is performed based on a comparison between the requested emission level calibration parameters and the original emission level calibration parameters.

[0033] Item 8): The apparatus according to Item 7), wherein the induction includes at least one of the following: degrading engine performance, forcing engine shutdown, or generating a fault code.

[0034] Item 9): The apparatus according to Item 8), wherein the induction is gradual and increases over time.

[0035] Item 10): The apparatus according to Item 7), wherein the one or more memory devices are further configured to store instructions thereon, the instructions, when executed by the one or more processors, causing the one or more processors to:

[0036] After receiving the requested recalibration parameters, receive the corrected recalibration parameters;

[0037] Determine the corrected emission level calibration parameter associated with the corrected recalibration parameter;

[0038] The corrected emission level calibration parameters are compared with the original emission level calibration parameters; and

[0039] When the corrected emission level calibration parameters match the original emission level calibration parameters, the inducement is removed and the original function is restored.

[0040] Item 11): The apparatus according to Item 7), wherein the requested recalibration parameters include at least one of fine-tuning parameters or operating system parameters.

[0041] Item 12): The apparatus according to Item 6), wherein the flash memory or erase data command includes shutting off power to the one or more processors, and

[0042] Specifically, after power is restored to one or more processors, the original emission level calibration parameters are restored.

[0043] Item 13): The apparatus according to Item 6), wherein the one or more memory devices are further configured to store instructions thereon, the instructions, when executed by the one or more processors, causing the one or more processors to:

[0044] Receive the requested recalibration parameters;

[0045] Determine the emission level calibration parameters for the request that are associated with the recalibration parameters of the request;

[0046] Compare the requested emission level calibration parameters with the original emission level calibration parameters; and

[0047] When the requested emission level calibration parameters conform to the original emission level calibration parameters, the requested recalibration parameters are implemented.

[0048] Item 14): The apparatus according to Item 6), wherein the secure location of the one or more memory devices is non-erasable.

[0049] Project 15): A system comprising:

[0050] Exhaust aftertreatment system; and

[0051] A controller, coupled to the exhaust aftertreatment system, is configured to:

[0052] Receive raw emission level calibration parameters;

[0053] The original emission level calibration parameters are stored in a safe location on the controller;

[0054] Receive the requested recalibration parameters;

[0055] Determine the emission level calibration parameters for the request that are associated with the recalibration parameters of the request;

[0056] Compare the requested emission level calibration parameters with the original emission level calibration parameters;

[0057] Induction is performed based on a comparison between the requested emission level calibration parameters and the original emission level calibration parameters;

[0058] When the requested emission level calibration parameters conform to the original emission level calibration parameters, the requested recalibration parameters are implemented;

[0059] Receive flash memory or erase data commands; and

[0060] Upon receiving the flash memory or erase data command, the original emission level calibration parameters are restored.

[0061] Item 16): The system according to Item 15), wherein the induction includes controlling at least one of the actuators of the exhaust aftertreatment system or the engine to impair normal engine or aftertreatment system behavior.

[0062] Project 17): The system according to Project 15), wherein the requested recalibration parameters include at least one of fine-tuning parameters or operating system parameters.

[0063] Item 18): The system according to Item 15), wherein the flash memory or erase data command includes shutting off power to the controller, and

[0064] Specifically, after power is restored to the controller, the original emission level calibration parameters are restored.

[0065] Item 19): The system according to Item 15), wherein the secure location of the controller includes the controller's non-erasable memory device.

[0066] Project 20): According to the system described in Project 15), the controller is further configured to:

[0067] An alarm is generated when the requested emission level calibration parameters do not conform to the original emission level calibration parameters.

[0068] This overview is illustrative only and is not intended to be limiting in any way. Other aspects, features, and advantages of the apparatus or process described herein will become apparent from the detailed description set forth herein in conjunction with the accompanying drawings, wherein like reference numerals refer to like elements. Numerous specific details are provided to give a thorough understanding of embodiments of the subject matter of this disclosure. Features of the subject matter of this disclosure described may be combined in any suitable manner in one or more embodiments and / or implementations. In this respect, one or more features of one aspect of the invention may be combined with one or more features of different aspects of the invention. Furthermore, additional features that may not be present in all embodiments or implementations may be recognized in some embodiments and / or implementations. Attached Figure Description

[0069] Figure 1This is a schematic diagram of a transportation system according to an example embodiment.

[0070] Figure 2 According to the example embodiment Figure 1 Block diagram of the controller.

[0071] Figures 3A-3E According to the example embodiment, it can be made by Figures 1-2 A block diagram illustrating the calibration logic of the controller and the process of implementing the engine circuit.

[0072] Figure 4 This is a flowchart of a method for implementing emission certification levels for vehicles according to an example embodiment. Detailed Implementation

[0073] The following is a more detailed description of various concepts related to methods, apparatuses, and systems for detecting emissions tampering and enforcing emissions regulations in various systems, as well as embodiments of such methods, apparatuses, and systems. Before turning to the accompanying drawings, which illustrate certain exemplary embodiments in detail, it should be understood that this disclosure is not limited to the details or methods set forth in the specification or shown in the drawings. It should also be understood that the terminology used herein is for descriptive purposes only and should not be considered limiting.

[0074] The current system includes different control modules and different hardware for different regulations (e.g., emissions regulations). Typically, each new emissions regulation requires different hardware, which creates difficulties when users operate engines in areas with regulations different from those initially calibrated for the engine. In such cases, users of engines without emissions regulations need to submit formal requests for verification and authorization to operate the engine with an uncertified electronic control unit (ECU) calibration, and then download that calibration to an approved, authorized ECU. It is understood that limiting these calibrations to specific serial numbers is only feasible for small batches.

[0075] Referring generally to the accompanying drawings, systems and methods for detecting emissions tampering and enforcing emissions regulations in various systems are shown and described herein according to various embodiments. A controller is provided, coupled to an engine and various other components in the system. When the engine is manufactured at the factory, labels (e.g., emissions level calibration parameters, first or expected emissions parameters, data packets or packets, or values, etc.) are written or programmed into the controller. The emissions level calibration parameters indicate the expected emissions tier compliance level for the engine (these tiers correspond to different permissible emissions levels, such as NOx emissions below tier 1 or NOx emissions below tier 2, which is above tier 1). However, one issue is that recalibration may render emissions from the engine system less stringent, potentially allowing non-compliance with one or more regulations. When the engine is in the field, the controller monitors the emissions level calibration parameters. For example, if a user attempts to recalibrate the controller and change the emissions level calibration parameters, the controller checks whether the new calibration is at the same emissions level as the original engine configuration (e.g., by comparing the originally written emissions level calibration parameters with the emissions labels in the new calibration packet). If the emissions label matches, the controller enables recalibration (i.e., allows normal engine operation with the new calibration). If the emissions label does not match, the controller can prescribe one or more actions to prevent normal engine operation (e.g., derating, etc.). By utilizing emissions calibration labels or values ​​permanently or substantially permanently stored in the controller's memory, the controller can prevent tampering even in the event of a complete controller reboot or reflash by comparing the new emissions level calibration parameters with the stored emissions level calibration values.

[0076] The systems and methods disclosed herein simplify the manufacturing process (e.g., assembly line) by providing engines at multiple emission certification levels using the same base engine hardware. Furthermore, the controller detects emission tampering and enforces emission regulations by allowing only application-authorized calibrations. Therefore, this disclosure advantageously provides a product that can meet multiple emission regulations and a protection mechanism to prevent customers from (intentionally or unintentionally) downloading non-compliant calibrations into their equipment. Moreover, this disclosure enables engines to be certified for different emission levels and exported to alternative markets using the same base engine hardware. A single chassis can be developed for multiple markets with different emission regulations. Having a common base engine, controller (e.g., ECU), and wiring harness is highly beneficial to users during both the manufacturing and operational phases.

[0077] Now for reference Figure 1The diagram illustrates a system 100 according to an exemplary embodiment. System 100 includes an engine 101, an aftertreatment system 120, an operator I / O device 130, a controller 140, and a telematics unit 150. According to one embodiment and as shown, system 100 is embodied in a vehicle. In various alternative embodiments, as described above, the controller 140 can be used with any engine system and / or any engine exhaust aftertreatment system (e.g., a generator). The vehicle can include on-road vehicles or off-road vehicles, including but not limited to long-haul trucks, mid-size trucks (e.g., pickup trucks), sedans, coupes, etc. Additional off-highway applications can include tanks, aircraft, ships, generators or generator sets, construction equipment (e.g., excavators, wheel loaders, cranes, forklifts, etc.), agricultural equipment (e.g., tractors, combine harvesters, sprayers, etc.), and the like. However, the system can also be implemented with stationary equipment (such as generators or generator sets). In the example shown, system 100 is embodied in a long-haul truck.

[0078] Furthermore, in the illustrated example, engine 101 is configured as a compression ignition internal combustion engine utilizing diesel fuel. However, in various alternative embodiments, engine 101 may be configured as another type of engine (e.g., spark ignition) utilizing a different type of fuel (e.g., gasoline, natural gas). In other example embodiments, engine 101 may be or include an electric motor (e.g., a hybrid powertrain). Engine 101 includes one or more cylinders and associated pistons. Atmospheric air combines with fuel and burns, thereby powering engine 101. The combustion of fuel and air in the compression chamber of engine 101 produces exhaust gas, which is operatively discharged to an exhaust pipe and aftertreatment system 120.

[0079] The aftertreatment system 120 is coupled to the engine 101. It should be understood that... Figure 1 The schematic diagrams depicted herein are merely one embodiment of an engine exhaust aftertreatment system. Many different configurations utilizing the systems and methods described herein can be implemented. In some embodiments, this disclosure can be used with general internal combustion engines (e.g., including and excluding exhaust aftertreatment systems). Therefore, while the systems and methods described herein relate primarily to engine exhaust aftertreatment systems, it should be understood that the systems and methods of this disclosure can be used in various configurations, including and excluding aftertreatment systems, such that… Figure 1 The embodiments described herein are not intended to be limiting.

[0080] Aftertreatment system 120 is configured to treat exhaust gas from engine 101, which enters the aftertreatment system 120 via an exhaust pipe, in order to reduce emissions of harmful or potentially harmful elements (e.g., NOx emissions, particulate matter, SOx, CO, greenhouse gases, etc.). Aftertreatment system 120 may include various components and systems such as a diesel engine oxidation catalyst (DOC) 121, a diesel engine particulate filter (DPF) 122, and a selective catalytic reduction (SCR) system 123. SCR 123 converts nitrogen oxides present in the exhaust gas produced by engine 101 into diatomic nitrogen and water through oxidation within the catalyst. DPF 122 is configured to remove particulate matter, such as soot, from the exhaust gas flowing in the exhaust duct system. In some embodiments, DPF 122 may be omitted. Furthermore, the spatial order of the catalytic converter elements may differ.

[0081] The aftertreatment system 120 may also include a reducing agent delivery system, which may include a decomposition chamber (e.g., a decomposition reactor, reactor pipe, decomposition tube, reactor tube, etc.) to deliver a reducing agent (e.g., urea, diesel exhaust fluid (DEF)). Urea aqueous solution (UWS), aqueous urea solution, etc., are converted into ammonia. Diesel exhaust fluid (DEF) 124 is added to the exhaust stream to aid catalytic reduction. The reducing agent can be injected through an injector upstream of the SCR catalytic converter component, allowing the SCR catalytic converter component to receive the mixture of reducing agent and exhaust gas. The reducing agent droplets undergo evaporation, pyrolysis, and hydrolysis processes to form non-NOx substances within the decomposition chamber, SCR catalytic converter component, and / or exhaust duct system. x Emissions (e.g., gaseous ammonia, etc.), which are non-NO x The emissions exit the aftertreatment system 120. The aftertreatment system 120 may also include an oxidation catalyst (e.g., DOC 121) fluidly coupled to the exhaust duct system to oxidize hydrocarbons and carbon monoxide in the exhaust gas. To properly facilitate this reduction, the DOC 121 may need to be at a specific operating temperature. In some embodiments, this specific operating temperature is between 200°C and 500°C. In other embodiments, this specific operating temperature is the temperature at which the conversion efficiency of the DOC 121 (e.g., the conversion of NOx to less harmful compounds, referred to as NOx conversion efficiency) exceeds a predefined threshold.

[0082] As shown, multiple sensors 125 are included in the aftertreatment system 120. The number, placement, and type of sensors included in the aftertreatment system 120 are shown for illustrative purposes only. In other configurations, the number, placement, and type of sensors may differ. Sensors 125 may be NOx sensors, temperature sensors, particulate matter (PM) sensors, and / or other emission component sensors. NOx sensors are configured to acquire data indicating the amount of NOx at each location where the NOx sensor is located. Temperature sensors are configured to acquire data indicating the temperature at their location. PM sensors are configured to monitor particulate matter flowing through the aftertreatment system 120. As shown, sensors 125 may be positioned after the engine 101, after the aftertreatment system 120, and between aftertreatment system components; however, it should be understood that the sensor positions may vary. Controller 140 is communicatively coupled to each sensor 125 in the aftertreatment system 120. Therefore, controller 140 is configured to receive data from one or more of the sensors 125. The received data can be used by the controller 140 for one or more components of the control system 100 and / or for monitoring and diagnostic purposes.

[0083] Sensors can be real or virtual (i.e., non-physical sensors configured to make various estimates or determinations within the controller's program logic). For example, emissions sensors can be real or virtual sensors arranged to measure or otherwise acquire data, values, or information indicating the emission levels of the aftertreatment system 120. Sensors are coupled to the engine (when configured as real sensors) and configured to send signals to the controller 140. When configured as virtual sensors, the controller 140 can use at least one input in algorithms, models, lookup tables, etc., to determine or estimate engine parameters (e.g., power output, etc.). Other sensors can also be real or virtual. As will be described herein, sensor 125 and additional sensors can provide data about how a particular vehicle system operates.

[0084] Still refer to Figure 1 Operator input / output (I / O) device 130 is also shown. Operator I / O device 130 can be communicatively coupled to controller 140, allowing information to be exchanged between controller 140 and I / O device 130, wherein the information may involve... Figure 1 The determination of one or more components or controllers 140 (described below). Operator I / O device 130 enables the operator of system 100 to communicate with controller 140 and... Figure 1The system 100 communicates with one or more components. For example, operator input / output device 130 may include, but is not limited to, an interactive display, a touchscreen device, one or more buttons and switches, a voice command receiver, etc. In various alternative embodiments, the controller 140 and components described herein may be implemented with non-vehicle applications (e.g., generators). Therefore, the I / O device may be application-specific. For example, in these cases, the I / O device may include a laptop computer, tablet computer, desktop computer, telephone, watch, personal digital assistant, etc. Via the operator I / O device, the controller 140 may provide diagnostic information, fault, or service notifications based on one or more measurements. For example, in some embodiments, the controller 140 may display the temperature of DOC 121, the temperature of engine 101 and exhaust gas, and various other information via the operator I / O device.

[0085] Controller 140 is configured to control the operation of system 100 and associated subsystems such as post-processing system 120 (and various components of each system) and operator input / output (I / O) devices 130. Communication between and within components can be via any number of wired or wireless connections. For example, wired connections may include serial cables, fiber optic cables, CAT5 cables, or any other form of wired connection. In contrast, wireless connections may include the Internet, Wi-Fi, cellular, radio, etc. In one embodiment, a controller local area network (CAN) bus provides the exchange of signals, information, and / or data. The CAN bus includes any number of wired and wireless connections. Because controller 140 is communicatively coupled to... Figure 1 The system and components, so the controller 140 is configured to... Figure 1 One or more components shown receive data. Regarding... Figure 2 The structure and function of controller 140 are further described.

[0086] The telematics unit 150 may include, but is not limited to, one or more memory devices for storing tracking data, one or more electronic processing units for processing tracking data, and a communication interface for facilitating data exchange between the telematics unit 150 and one or more remote devices (e.g., providers / manufacturers of telematics devices, etc.). The telematics unit 150 may facilitate remote updates to the controller 140 (e.g., calibration parameters, fine-tuning parameters, complete operating system software / packages, etc.). In this regard, the communication interface can be configured as any type of mobile communication interface or protocol, including but not limited to Wi-Fi, WiMax, Internet, radio, Bluetooth, Zigbee, satellite, cellular, GSM, GPRS, LTE, etc. The telematics unit 150 may also include a communication interface for communicating with the controller 140 of the system 100. The communication interface for communicating with the controller 140 may include any type and number of wired and wireless protocols (e.g., any standard under IEEE 802, etc.). For example, wired connections may include serial cables, fiber optic cables, SAE J1939 buses, CAT5 cables, or any other form of wired connection. In contrast, wireless connectivity may include the Internet, Wi-Fi, Bluetooth, Zigbee, cellular, radio, etc. In one embodiment, a Controller Area Network (CAN) bus comprising any number of wired and wireless connections provides the exchange of signals, information, and / or data between controller 140 and telematics unit 150. In other embodiments, a local area network (LAN), wide area network (WAN), or external computer (e.g., via the Internet through an Internet service provider) may provide, facilitate, and support communication between telematics unit 150 and controller 140. In yet another embodiment, communication between telematics unit 150 and controller 140 is implemented via the Unified Diagnostic Services (UDS) protocol. All such variations are intended to fall within the spirit and scope of this disclosure.

[0087] Now for reference Figure 2 This illustrates an example embodiment. Figure 1A schematic diagram of the controller 140 of system 100. The controller 140 may be configured as one or more electronic control units (ECUs). The controller 140 may be separate from or included in at least one of a transmission control unit, an exhaust aftertreatment control unit, a powertrain control module, an engine control module, etc. In one embodiment, the components of the controller 140 are combined into a single unit. In another embodiment, one or more components may be geographically distributed throughout the system. All these variations are intended to fall within the scope of this disclosure. The controller 140 is shown as including a processing circuitry 202 with a processor 204 and a memory device 206, calibration logic 210, engine circuitry 212, and a communication interface 216.

[0088] In one configuration, engine circuitry 212 is embodied as a machine- or computer-readable medium storing instructions executable by a processor, such as processor 204. As described herein and in other uses, the machine-readable medium facilitates the performance of certain operations to achieve the reception and transmission of data. For example, the machine-readable medium can provide instructions (e.g., commands, etc.) to, for example, acquire data. In this respect, the machine-readable medium may include programmable logic defining the frequency of data acquisition (or data transmission). The computer-readable medium may include code, which can be written in any programming language, including but not limited to Java and any conventional procedural programming language, such as the "C" programming language or similar programming languages. The computer-readable program code can be executed on one processor or multiple remote processors. In the latter case, the remote processors can be interconnected via any type of network (e.g., CAN bus, etc.).

[0089] In another configuration, engine circuitry 212 is embodied as a hardware unit, such as an electronic control unit. Therefore, engine circuitry 212 can be embodied as one or more circuit components, including but not limited to processing circuitry, network interfaces, peripherals, input devices, output devices, sensors, etc. In some embodiments, engine circuitry 212 can take the form of one or more analog circuits, electronic circuits (e.g., integrated circuits (ICs), discrete circuits, system-on-a-chip (SoC) circuits, microcontrollers, etc.), telecommunication circuits, hybrid circuits, and any other type of "circuit". In this respect, engine circuitry 212 can include any type of component for performing or facilitating the implementation of the operations described herein. For example, the circuitry described herein can include one or more transistors, logic gates (e.g., NAND, AND, NOR, OR, XOR, NOT, XNOR, etc.), resistors, multiplexers, registers, capacitors, inductors, diodes, wiring, etc. Engine circuitry 212 can also include programmable hardware devices, such as field-programmable gate arrays, programmable array logic, programmable logic devices, etc. Engine circuit 212 may include one or more memory devices for storing instructions executable by one or more processors. The memory devices and processors may have the same definitions provided below regarding memory device 206 and processor 204. In some hardware unit configurations and as described above, components of engine circuit 212 may be geographically distributed across various locations within the system. Alternatively, and as shown, engine circuit 212 may be embodied in or within a single unit / housing, shown as controller 140.

[0090] In the illustrated example, controller 140 includes processing circuitry 202 having a processor 204 and a memory device 206. Processing circuitry 202 may be constructed or configured to execute or implement the instructions, commands, and / or control processes described herein with respect to engine circuitry 212. The depicted configuration represents engine circuitry 212 as a machine- or computer-readable medium. However, as stated above, this illustration is not intended to be limiting, as other embodiments of engine circuitry 212 configured as hardware units are contemplated in this disclosure. All such combinations and variations are intended to fall within the scope of this disclosure.

[0091] Processor 204 may be implemented as one or more processors, application-specific integrated circuits (ASICs), one or more field-programmable gate arrays (FPGAs), digital signal processors (DSPs), a set of processing units, or other suitable electronic processing units. In some embodiments, one or more processors may be shared by multiple circuits (e.g., engine circuitry 212 and other circuitry of system 100 may include or otherwise share the same processor, which in some example embodiments may execute instructions stored or otherwise accessed via different regions of memory). Alternatively or additionally, one or more processors may be configured to perform or otherwise perform certain operations independently of one or more coprocessors. In other example embodiments, two or more processors may be coupled via a bus to enable independent, parallel, pipelined, or multithreaded instruction execution. All these variations are intended to fall within the scope of this disclosure.

[0092] Memory device 206 (e.g., memory, memory cell, storage device) may include one or more devices (e.g., RAM, ROM, flash memory, hard disk storage) for storing data and / or computer code used to perform or facilitate the various processes, layers, and modules described herein. Memory device 206 may be communicatively connected to processor 204 to provide processor 204 with computer code or instructions for performing at least some of the processes described herein. Furthermore, memory device 206 may be or include tangible, non-transient volatile memory or non-volatile memory. Therefore, memory device 206 may include database components, object code components, scripting components, or any other type of information structure for supporting the various activities and information structures described herein.

[0093] Communication interface 216 may include any combination of wired and / or wireless interfaces (e.g., jacks, antennas, transmitters, receivers, transceivers, wired terminals) for data communication with various systems, devices, or networks configured to enable in-vehicle communication (e.g., communication between and within vehicle components) and out-of-vehicle communication (e.g., communication with a remote server via a telematics unit). For example, regarding out-of-vehicle / system communication, communication interface 216 may include Ethernet cards and ports for sending and receiving data via an Ethernet-based communication network and / or Wi-Fi transceivers for communication via a wireless communication network (via a telematics unit). Communication interface 216 may be configured to communicate via a local area network or a wide area network (e.g., the Internet) and may use various communication protocols (e.g., IP, LON, Bluetooth, ZigBee, radio, cellular, near-field communication). The communication interface 216 can facilitate coupling to computing devices, such as OBD tools, which enables updates / changes to calibration parameters, fine-tuning parameters, and / or the operating system used by the controller 140.

[0094] Communication interface 216 facilitates communication between and within one or more components of controller 140 and system 100 (e.g., engine 101, aftertreatment system 120, sensor 125, etc.). Communication between and within the components of controller 140 and system 100 can be via any number of wired or wireless connections (e.g., any standard under IEEE). For example, wired connections can include serial cables, fiber optic cables, CAT5 cables, or any other form of wired connection. In contrast, wireless connections can include the Internet, Wi-Fi, cellular, Bluetooth, ZigBee, radio, etc. In one embodiment, a controller local area network (CAN) bus provides the exchange of signals, information, and / or data. The CAN bus can include any number of wired and wireless connections providing the exchange of signals, information, and / or data. The CAN bus can include a local area network (LAN) or a wide area network (WAN), or can be connected to an external computer (e.g., via the Internet provided by an Internet service provider).

[0095] Calibration logic 210 is configured to facilitate updating, adjusting, and changing one or more calibration parameters, fine-tuning parameters, and / or software operating system (or other software features) of the controller. Calibration logic 210 may be configured to store one or more programs or instructions in memory device 206. Calibration logic 210 facilitates refreshing the controller 140, changing fine-tuning parameters, calibration parameters, and / or performing various software updates. Calibration logic 210 is configured to receive one or more calibration parameters (e.g., emission level calibration parameter 208) and fine-tuning parameters. “Fine-tuning parameters” refer to electronic operating settings for components of, for example, the engine or system, which can be adjusted by an operator or technician. In contrast, “calibration parameters” are typically settings that are not adjustable by either an operator or technician. An example of a calibration parameter is the permissible engine temperature before triggering at least one of engine shutdown, derating events, and trigger indicator lights. Another example of a calibration parameter may include operating conditions prescribed by local, state, or federal law (e.g., acceptable emission levels before triggering engine derating conditions). The non-exhaustive list of fine-tuning parameters includes: various parameters related to cruise control (e.g., upper droop amount, lower droop amount, etc.); road governor limits (i.e., the maximum permissible road speed of the vehicle); idle shut-off parameters (e.g., the amount of time before the idle engine shuts off); load-based speed control parameters (e.g., predefined engine speeds for certain operating conditions, such as load); downshift protection parameters for light-load and heavy-load vehicle speeds (e.g., maintaining the vehicle at light-load or heavy-load vehicle speeds to promote increased fuel economy by minimizing downshifts to facilitate operation in the highest gear); and vehicle acceleration management characteristics (e.g., limiting acceleration under certain conditions to improve fuel economy). Calibration logic 210 is configured to receive one or more calibration parameters (e.g., emission level calibration parameter 208) and fine-tuning parameters and store them in memory for execution / use / implementation by controller 140. Parameters can be received from the remote information processing unit 150 (e.g., by recalibrating one or more parameters over the air) or directly from one or more manufacturing computing devices.

[0096] Calibration logic 210 is configured to receive emission level calibration parameters 208. During system manufacturing, calibration logic 210 may write emission level calibration parameters 208 into a memory device. Alternatively, calibration logic 210 may receive emission level calibration parameters 208 from a manufacturing computing device and facilitate storage within controller 140 (e.g., in a memory device).

[0097] Emission level calibration parameter 208 (also known as expected or first emission calibration parameter, value, data package, label, etc.) refers to the emission level or grade assigned to a specific engine, aftertreatment system, and / or engine aftertreatment system (e.g., an indicator of the emission regulatory level to which calibration software has been adjusted or designed). "Emission grade" refers to the emission standards / regulations and certification requirements assigned or specified to a vehicle or system. This includes permitted emission outputs, which can be based on the type of vehicle, the year of the vehicle, the area in which the vehicle is intended to operate, etc. Emission level calibration parameter 208 can be programmed to different emission levels currently existing and for future expansion should any additional regulations become available. Emission level calibration parameter 208 can be associated with one or more algorithms, lookup tables, logic, etc., that define the operating parameters of system 100 to help the system conform to a specified emission level or grade. For example, the California Air Resources Board (CARB) may define emission regulations different from those of, for example, Wisconsin. Therefore, emission level calibration parameter 208 may differ for a system intended for use in California from that intended for use in Wisconsin. Therefore, emission level calibration parameter 208 is adjusted or calibrated to a specific engine and emission grade. Emission level calibration parameter 208 is published to the system, which identifies calibrations for specific purposes and can be used during manufacturing as a calibration option to meet emission requirements of a specific market (e.g., the market in which the system is intended for use). Parameters (e.g., labels, values, etc.) can take different states, which can be calibrated before engine manufacturing to identify the emission level associated with the engine.

[0098] Calibration logic 210 stores emission level calibration parameters 208 in a secure location in memory (e.g., a tamper-proof trusted execution environment). Emission level calibration parameters 208 may be permanently stored in this secure location in memory, making them unadjustable unless, for example, by the manufacturer or a representative of the manufacturer. Therefore, even in the event of recalibration, emission level calibration parameters 208 remain retrievable (e.g., unerasable). In this respect, emission level calibration parameters 208 may be more permanent / immutable than typical calibration parameters. In this respect, and relative to other calibration parameters of controller 140, emission level calibration parameters 208 may include a forced save and restore attribute. The forced save and restore attribute of emission level calibration parameters 208 indicates that emission level calibration parameters 208 are saved during recalibration cycles and restored during refresh / new downloads (e.g., of other parameters). In other alternative embodiments, emission level calibration parameters 208 may be similar to typical calibration parameters. In other words, controller 140 has two calibration parameters; the first calibration parameter is a constant parameter indicating the emission levels saved and restored since manufacturing, and the second calibration parameter is a recalibrable parameter that can be periodically updated to change over time. Emission level calibration parameter 208 is of the first type with the attribute of saving and restoring functionality. This attribute allows emission level calibration parameter 208 to always reflect the expected emission level compared to the new emission level upon power-up, which, among other benefits, prevents tampering. In operation, and as described herein, updated emission level calibration parameters should match the parameters set at manufacturing (e.g., saved and restored values), and if they do not match, the mismatch is flagged as non-compliant. Emission level calibration parameter 208 and its associated attributes can be determined / specified during engine manufacturing.

[0099] As described herein, controller 140 may store certain data fragments during calibration updates, which are typically used for service and warranty purposes. During a calibration update, even in the event of an attempt to refresh / erase the data and procedures stored by controller 140, the data is restored to its previous values ​​after the calibration download is complete. For example, emission level calibration parameter 208 may be stored in a memory fragment that cannot even be accessed by the recalibration sequence. Calibration logic 210 is configured to store or facilitate the storage of emission level calibration parameter 208 in memory during power loss and to restore it even after the calibration is erased and downloaded (i.e., it is not deleted and it is able to be located). When read by controller 140 (i.e., calibration logic 210), this emission level calibration parameter identifies the expected calibrated emission level to which the calibration has been adjusted. This is the emission level that the system is expected to meet.

[0100] In operation, calibration logic 210 is configured to receive updates, such as from a telematics unit or directly from manufacturing computing equipment (e.g., a service tool), to change one or more calibration parameters, fine-tuning parameters, and software packages (e.g., an operating system). These updates (changes, etc.) may affect the emissions of system 100 (e.g., changes when a reduction occurs, changes when a regeneration event occurs, etc.). Some operators may want to prioritize system performance over emissions (even if this means non-compliance with one or more standards). To prevent this and maintain or attempt to maintain compliance, calibration logic 210 is configured to check the emission level calibration parameter 208 against the new emission calibration parameter. If these values ​​match, calibration logic 210 communicates with engine circuitry 212 to allow the engine to operate normally. If these values ​​do not match, calibration logic 210 sets a fault code and triggers an inducement required by the emissions regulatory agency, which will be described further herein. For example, the inducement is designed to provide reduced engine performance (e.g., reduced torque, locking the engine speed to idle) to impair normal behavior and induce the operator to take corrective action.

[0101] In some embodiments, calibration logic 210 receives a new emission level calibration parameter, causing it to compare the stored emission level calibration parameter 208 with the new parameter. In other embodiments, the calibration logic may receive a fine-tuning parameter or other values ​​associated with the emission level calibration parameter (even though no new emission level calibration parameter is received). In this case, calibration logic 210 compares the associated stored parameter (e.g., the fine-tuning parameter) with the newly received parameter (i.e., an emission level calibration parameter comparison performed by a proxy). In still other embodiments, multiple emission level calibration parameters may exist associated with various emission levels (e.g., increasing stringency). In these scenarios, calibration logic 210 performs a comparison where the newly received emission level calibration parameter is considered to "match" the stored emission level calibration parameter 208 if it is consistent with an emission level that is as stringent or more stringent than the emission level associated with emission level calibration parameter 208. Therefore, a match can be considered and calibration updates enabled without requiring an exact match.

[0102] As an example, when controller 140 (e.g., system 100, such as a key-on event embodying system 100) is powered on, controller 140 (i.e., calibration logic 210) compares emission level calibration parameter 208 with received calibration level parameters (e.g., via a telematics unit, etc.) to detect whether the controller's calibration software has been tampered with. Calibration logic 210 is configured to determine a tampering event if the emission level calibration parameter received from the downloaded calibration does not match emission level calibration parameter 208. In the event of a mismatch, the controller can set a fault code that will subsequently trigger emission induction / action, as described below. This fault will be logged as a tampering fault; however, the user has the opportunity to download the appropriate calibration before the induction can begin. These inductions may prevent the operator from properly operating the equipment to ensure certain emissions from the system.

[0103] As another example, operators can send their vehicles for maintenance. Technicians can determine what adjustments have been made based on emission level calibration parameter 208. Based on emission level calibration parameter 208, technicians can then determine whether specific settings in the controller are suitable for a particular engine market. Furthermore, when the calibration is uploaded to the cloud before being sent to the controller via telematics unit 150, the calibration can have a corresponding emission level calibration parameter 208 indicating which level it will meet, ensuring that newly published calibrations transmitted to the controller via the cloud match the values ​​stored in the controller.

[0104] Engine circuit 212 is configured to communicate with and at least partially control engine 101 based on feedback from calibration logic 210. Specifically, engine circuit 212 is configured to control one or more operating points (speed, torque, etc.) of engine 101 when sensor 125 provides information indicating emission levels. Engine circuit 212 is configured to send commands to specify a desired operating point of engine 101 (e.g., target torque and / or speed output) in response to data / information regarding emission calibration. Engine circuit 212 can command air handling actuators, turbocharger positions, EGR positions (e.g., EGR valves), etc. Additionally, engine circuit 212 can determine that no adjustments to engine 101 are required. Engine circuit 212 is coupled to sensor 125.

[0105] Engine circuit 212 is configured to communicate with calibration logic 210 to modulate the engine operating point (as described above) in response to comparisons performed by calibration logic 210. Engine operating point commands at least partially control engine 101 and may include one or more of torque, speed, fuel rail pressure, fueling commands, etc. As an example, and in response to a determined mismatch, engine circuit 212 controls other components of the engine or system 100 to limit or reduce emissions (e.g., reduce the engine's maximum permissible power output). In this example, engine circuit 212 modulates the engine operating point, specifically the engine's power output, in response to a tampering alarm. Engine operating point commands may be commands controlling engine torque (e.g., desired torque output), engine speed (desired engine speed), fueling commands (e.g., injector quantity and timing), exhaust gas recirculation quantity, combinations thereof, etc. Such modulation of the engine operating point may include completely shutting down the engine. As another example, in the event of a determined tampering event, engine circuit 212 may control EGR quantity, feed rate, and other parameters besides the "engine".

[0106] Therefore, engine circuit 212 can issue various commands to various components in response to comparisons and identified mismatches made by calibration logic 210. These actions may be designed to help comply with one or more emission regulations. These actions include derated events occurring under certain conditions, forced engine shutdown, etc. For example, engine power can be derated (maximum power output is limited to the power output allowed under normal operation) in the event of an incorrect emission rating detected. As a remedy for the mismatch, engine circuit 212 can gradually reduce the power output that can be drawn from the engine until the fault is rectified. This power-down parameter can be set using manufacturing tools. Once the correct controller calibration software is reprogrammed to the controller, the device can resume normal operation. Engineering tools may also exist to override the power-down parameter (e.g., not restoring the parameter during software recalibration).

[0107] Now for reference Figures 3A-3E According to the example embodiment, it is shown that it can be made by Figures 1-2 A graphical description of the calibration logic of the controller and the process implemented in the engine circuitry. Figures 3A-3E In the diagram, "ECU" refers to controller 140. These diagrams illustrate example processes for checking emission level calibration parameters, detecting tampering events, and controlling various components based on comparisons and detected tampering events. Figures 3A-3B In this process, controller 140 is programmed with specific emission level calibration parameters during the initial parameter download (i.e., the memory in this respect changes from blank to include parameters for the expected emission level). Figures 3A-3BAs illustrated in the calibration example, the controller is programmed at the engine factory by downloading the expected calibration (e.g., Stage V) to a blank controller. Stage V refers to a specific European emission standard for engines used in off-highway applications. After downloading, the emission level calibration parameters for Stage V engines in this case are stored in the controller (e.g., memory device 206). Figure 3B Subsequent calibration updates were made in [date / time]. Figure 3C As shown, the programmed / stored emission level calibration parameters remain unchanged. In the case of a software update, controller 140 (i.e., calibration logic 210) checks whether the new software meets its initial market expectations by comparing the new parameters with the stored emission level parameters. This is before the calibration refresh. Figure 3D As shown, this refers to updating the calibration parameters. Here, the new calibration parameters are used for Stage 0 engines, while the existing emission level calibration parameters are used for Stage V engines. If calibration logic 210 determines that these parameters match, calibration logic 210 takes no action (no fault code is set and no notification is provided to the engine circuitry to, for example, derating the engine). If calibration logic 210 determines that these parameters do not match, various actions as described above can be implemented (e.g., fault code, engine derating, engine shutdown, etc.). In one embodiment, notification can also be provided to the operator in the form of a malfunction indicator light, alarm, etc. At this point, in Figures 3D-3E An example of tampering is shown. When a non-compliant calibration (e.g., Stage 0) is downloaded as part of a calibration refresh, controller 140 checks and detects a mismatch after the calibration refresh, and the controller restores the emission level calibration parameter 208. Therefore, a fault code can be set, and engine performance can be limited. Figure 3E ).

[0108] Therefore, this process can be used for various engine types. For example, a Stage V base engine with a controller can be adjusted to meet Stage IIIa (EPA Level 3) regulations for use in machines in the Stage IIIa emissions market. Stage V base engines with Stage IV (EPA Level 4F), Stage IIIb (EPA Level 4i), Stage IIIa (EPA Level 3), Stage II (EPA Level 2), or Level 0 (unregulated) calibration adjustments may exist. In a further example, a Chinese Stage IV base engine with Chinese Stage III, Stage IV (EPA Level 4F), Stage IIIb (EPA Level 4i), Stage IIIa (EPA Level 3), Stage II (EPA Level 2), or Level 0 (unregulated) calibration adjustments may exist. There may be base engines with more recent products (exceeding Stage V emissions regulations) whose calibration / software is adjusted to any of the lower emissions regulations discussed above. The embodiments and innovations described herein can be applied to all of these and other engine types.

[0109] Emission level calibration parameter 208 or the label allows multiple products with the same product ID / label to be issued because the engine configuration from a hardware perspective remains identical. Once the expected emission level of the controller is determined, a technician downloading a specific updated calibration will be able to select an emission level that matches the emission level stored in controller 140. Furthermore, calibration logic 210 additionally verifies that the service technician is correctly downloading the calibration to the controller. For example, if an incorrect calibration is issued, the feature will generate an alert (e.g., malfunction indicator light, alarm, text display notification on the display device, etc.) when the product is updated, informing the operator that the calibration process has an error and a new calibration needs to be downloaded. For example, if there is a North American emissions-compliant product, but the technician accidentally selects a European regulatory calibration available online and downloads it to the engine's controller, this specific feature will mark it as problematic. Additionally, if these units are exported to other emissions markets, the serial number of that specific engine may be certified for a new emission level. Therefore, the verification function can be disabled for that specific engine's serial number. For example, if an operator wants to obtain higher rated power from the engine when installing a larger turbocharger, they must make new emissions adjustments to match the higher power demand. Meanwhile, if they obtain a calibration that is also adjusted for that market, calibration logic 210 will not flag it as a problem. However, if the operator can download a calibration with that higher adjustment power and better performance, but it is designed for a lagging emissions market, then it will be flagged as tampering and mismatch in the emissions rating (by controller 140). Therefore, as long as the critical parts list matches, it will not prevent the operator from switching from a lower power rating to a higher rated power, but it will prevent the operator from placing a lower-rated emissions calibration at a higher level.

[0110] Now for reference Figure 4 The illustration shows a method 400 for performing emission certification levels according to an exemplary embodiment. This method can be... Figure 1The components in Figure 3 are executed so that they can be referenced to help explain method 400. At process 402, the controller is configured with the expected emission level calibration parameters. For example, calibration logic 210 may set the emission level calibration parameters to the expected emission level based on one or more inputs from the telematics unit (or directly during the manufacturing process). At process 404, the controller receives a request to recalibrate the calibration logic (e.g., the emission level calibration parameters) with specified parameters. For example, the new emission level calibration parameters may be updated emission regulatory requirements. However, calibration refreshes may also include other updates due to performance and / or product improvements. The new emission level calibration parameters can be sent from the telematics unit or from a service tool to the vehicle. This can be initiated by a service provider, a user, a manufacturer, etc. Once received, controller 140 compares the expected emission level calibration parameters with the new emission level calibration parameters. At process 406, the controller determines whether the new emission level calibration parameters match the expected emission level calibration parameters. Based on this determination, the controller generates an alarm at process 408. For example, if a mismatch between emission level calibration parameters is detected, an alarm is generated by controller 140 (e.g., a fault code, a malfunction indicator light on the vehicle's dashboard, etc.). However, if the new emission level calibration parameters match the expected emission level calibration parameters, no alarm is generated, and the engine and system can continue to operate normally. If an alarm is generated, the controller can modulate the engine (or another component) at process 410 to help comply with emission regulations. Therefore, the engine's operating point is adjusted. As discussed herein, this can include reducing the power output of engine 101 or shutting down the engine as an incentive for the operator to remedy the fault and meet the appropriate emission levels (e.g., emission level calibration parameters). At process 412, compliant emission level calibration parameters are downloaded. Once the controller has been updated with compliant emission level calibration parameters that match the emission level calibration parameters programmed in the controller, the controller modulates the engine again at process 414. For example, the engine will resume normal operation.

[0111] As used herein, the terms “approximately,” “about,” “substantially,” and similar terms are intended to have a broad meaning consistent with common and accepted usage by those skilled in the art to which the subject matter of this disclosure relates. Those skilled in the art who consult this disclosure will understand that these terms are intended to allow for the description of certain features described and claimed, without limiting the scope of those features to the precise numerical ranges provided. Therefore, these terms should be interpreted as indicating that non-substantial or irrelevant modifications or alterations to the described and claimed subject matter are considered to be within the scope of this disclosure as set forth in the appended claims.

[0112] It should be noted that the term “exemplary” and its variations, as used herein to describe various embodiments, are intended to indicate that these embodiments are possible examples, representations and / or illustrations of possible embodiments (and the term is not intended to imply that such embodiments are necessarily extraordinary or superlative examples).

[0113] As used herein, the term "coupled" and its variations refer to two components being joined together, directly or indirectly. This joining can be fixed (e.g., permanent or immutable) or movable (e.g., removable or releasable). Such a joining can be achieved by directly coupling two components together, by coupling two components together using one or more separate intervening members, or by coupling two components together using an intervening member that forms a single whole with one of the two components. If "coupled" or its variations are modified by an additional term (e.g., directly coupled), the general definition of "coupled" provided above is modified by the simple linguistic meaning of the additional term (e.g., "directly coupled" means the joining of two components without any separate intervening member), resulting in a narrower definition than the general definition of "coupled" provided above. This coupling can be mechanical, electrical, or fluid. For example, circuit A being "coupled" to circuit B could mean that circuit A communicates directly with circuit B (i.e., without an intermediary) or indirectly with circuit B (e.g., through one or more intermediaries).

[0114] Despite Figure 2 Various circuits with specific functions are shown, but it should be understood that controller 140 may include any number of circuits for performing the functions described herein. For example, the activities and functions of calibration logic 210 and engine circuit 212 may be combined into multiple circuits or a single circuit. Additional circuits with additional functions may also be included. Furthermore, controller 140 may further control other activities beyond the scope of this disclosure.

[0115] As described above, and in one configuration, the "circuit" can be implemented in a machine-readable medium for use by various types of processors (e.g., Figure 2The processor 204 executes the executable code. The identified circuitry may, for example, comprise one or more physical or logical blocks of computer instructions, which may be organized, for example, into objects, processes, or functions. However, the executable of the identified circuitry need not be physically located together, but may include different instructions stored in different locations that, when logically connected, comprise the circuitry and implement its stated purpose. In practice, the circuitry of computer-readable program code may be a single instruction or multiple instructions, and may even be distributed across several different code segments, between different programs, and across several memory devices. Similarly, operational data may be identified and represented within the circuitry herein, and may be embodied in any suitable form and organized within any suitable type of data structure. Operational data may be collected as a single dataset, or may be distributed across different locations, including different storage devices, and may exist at least in part simply as electronic signals within a system or network.

[0116] Although the term "processor" has been briefly defined above, the terms "processor" and "processing circuit" are intended to be interpreted broadly. In this respect, and as stated above, a "processor" can be implemented as one or more general-purpose processors, application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), digital signal processors (DSPs), or other suitable electronic data processing components configured to execute instructions provided by memory. One or more processors can take the form of a single-core processor, a multi-core processor (e.g., a dual-core processor, a triple-core processor, a quad-core processor, etc.), a microprocessor, etc. In some embodiments, one or more processors can be external to the device; for example, one or more processors can be remote processors (e.g., cloud-based processors). Alternatively or additionally, one or more processors can be internal to the device and / or local. In this regard, a given circuit or its components can be located locally (e.g., as part of a local server, a local computing system, etc.) or remotely (e.g., as part of a remote server such as a cloud-based server). Therefore, the term "circuit" as used herein can include components distributed in one or more locations.

[0117] Although the accompanying drawings and descriptions may show a specific order of method steps, this order may differ from the order depicted and described unless otherwise specified above. Furthermore, two or more steps may be performed simultaneously or partially simultaneously unless otherwise specified above. For example, such variations may depend on the chosen software and hardware system and the designer's choices. All such variations are within the scope of this disclosure.

[0118] For purposes of illustration and description, the foregoing description of embodiments has been presented. These descriptions are not intended to be exhaustive or to limit this disclosure to the precise forms disclosed, and modifications and variations are possible or available from this disclosure in accordance with the foregoing teachings. The embodiments were chosen and described to explain the principles of this disclosure and its practical application, enabling those skilled in the art to utilize various embodiments and make various modifications suitable for the particular purpose intended. Other substitutions, modifications, alterations, and omissions may be made in the design, operating conditions, and arrangement of the embodiments without departing from the scope of this disclosure as set forth in the appended claims.

[0119] Therefore, this disclosure may be practiced in other specific forms without departing from its spirit or essential characteristics. The described embodiments should be considered illustrative rather than restrictive in all respects. Therefore, the scope of this disclosure is defined by the appended claims rather than by the foregoing description. All variations in the meaning and scope of equivalent forms of the claims are included within its scope.

Claims

1. A system for detecting emissions tampering, comprising: An exhaust aftertreatment system coupled to the engine; as well as A controller, comprising at least one processor coupled to at least one memory device storing instructions, which, when executed by the at least one processor, cause the controller to perform operations including: The first emission level calibration parameters are stored in a portion of the at least one memory device that is not accessible to the recalibration sequence; Receive the second emission level calibration parameters; Compare the first emission level calibration parameter with the second emission level calibration parameter; An alert is generated based on the comparison; as well as Based on the comparison indicating a mismatch between the first emission level calibration parameter and the second emission level calibration parameter, an induction is implemented, the induction including at least one of the following: limiting the engine speed, limiting the engine torque, or shutting down the engine.

2. The system according to claim 1, wherein, The controller performs further operations, including restoring the first emission level calibration parameters based on the power-on and power-off of the controller.

3. The system according to claim 2, wherein, Saving the first emission level calibration parameter to the at least one memory device includes configuring the first emission level calibration parameter as non-erasable, such that the first emission level calibration parameter can be retained through multiple recalibrations.

4. An apparatus for detecting emissions tampering, comprising: One or more processing circuits, comprising one or more memory devices coupled to one or more processors, said one or more memory devices being configured to store instructions thereon, said instructions, when executed by said one or more processors, causing said one or more processors to: Receive the first emission level calibration parameters; The first emission level calibration parameters are stored in a secure location in one or more memory devices that are inaccessible to the recalibration sequence; Receive flash memory or erase data commands; Upon receiving the flash memory or erase data command, restore the first emission level calibration parameters; receive the requested recalibration parameters; Determine the emission level calibration parameters for the request that are associated with the recalibration parameters of the request; Compare the requested emission level calibration parameters with the first emission level calibration parameters; as well as Based on the comparison indicating a mismatch between the first emission level calibration parameter and the requested emission level calibration parameter, an inducement is implemented, the inducement including at least one of the following: limiting engine speed, limiting engine torque, or shutting down the engine.

5. The apparatus according to claim 4, wherein, The inducement also includes generating fault codes.

6. The apparatus according to claim 4, wherein, The induction is gradual and increases over time until the fault is remedied.

7. The apparatus according to claim 5, wherein, The induction is gradual and increases over time until the fault is remedied.

8. The apparatus according to any one of claims 4-7, wherein, The one or more memory devices are further configured to store instructions thereon, which, when executed by the one or more processors, cause the one or more processors to: After receiving the requested recalibration parameters, receive the corrected recalibration parameters; Determine the corrected emission level calibration parameter associated with the corrected recalibration parameter; The corrected emission level calibration parameter is compared with the first emission level calibration parameter; and When the corrected emission level calibration parameter matches the first emission level calibration parameter, the inducement is removed and the original function is restored.

9. The apparatus according to any one of claims 4-7, wherein, The requested recalibration parameters include at least one of fine-tuning parameters or operating system parameters.

10. The apparatus according to claim 8, wherein, The requested recalibration parameters include at least one of fine-tuning parameters or operating system parameters.

11. The apparatus according to any one of claims 4-7 and 10, wherein, The flash memory or erase data command includes shutting off power to the one or more processors, and Specifically, after power is restored to the one or more processors, the first emission level calibration parameters are restored.

12. The apparatus according to claim 8, wherein, The flash memory or erase data command includes shutting off power to the one or more processors, and Specifically, after power is restored to the one or more processors, the first emission level calibration parameters are restored.

13. The apparatus according to claim 9, wherein, The flash memory or erase data command includes shutting off power to the one or more processors, and Specifically, after power is restored to the one or more processors, the first emission level calibration parameters are restored.

14. The apparatus according to claim 4, wherein, The one or more memory devices are further configured to store instructions thereon, which, when executed by the one or more processors, cause the one or more processors to: When the requested emission level calibration parameters conform to the first emission level calibration parameters, the requested recalibration parameters are implemented.

15. The apparatus according to any one of claims 4-7, 10, and 12-14, wherein, The secure location of the one or more memory devices is non-erasable.

16. The apparatus according to claim 8, wherein, The secure location of the one or more memory devices is non-erasable.

17. The apparatus according to claim 9, wherein, The secure location of the one or more memory devices is non-erasable.

18. The apparatus according to claim 11, wherein, The secure location of the one or more memory devices is non-erasable.

19. A system for detecting emissions tampering, comprising: Exhaust aftertreatment system; as well as A controller, coupled to the exhaust aftertreatment system, is configured to: Receive the first emission level calibration parameters; The first emission level calibration parameters are stored in a secure location on the controller that is inaccessible during the recalibration sequence; Receive the requested recalibration parameters; Determine the emission level calibration parameters for the request that are associated with the recalibration parameters of the request; Compare the requested emission level calibration parameters with the first emission level calibration parameters; Based on the comparison indicating a mismatch between the requested emission level calibration parameter and the first emission level calibration parameter, an induction is implemented, the induction including at least one of the following: limiting the engine speed, limiting the engine torque, or shutting down the engine; When the requested emission level calibration parameters conform to the first emission level calibration parameters, the requested recalibration parameters are implemented; Receive flash memory or erase data commands; as well as Upon receiving the flash memory or erase data command, the first emission level calibration parameters are restored.

20. The system according to claim 19, wherein, The requested recalibration parameters include at least one of fine-tuning parameters or operating system parameters.

21. The system according to claim 19, wherein, The flash memory or erase data command includes shutting off power to the controller, and Specifically, after power is restored to the controller, the first emission level calibration parameters are restored.

22. The system according to claim 20, wherein, The flash memory or erase data command includes shutting off power to the controller, and Specifically, after power is restored to the controller, the first emission level calibration parameters are restored.

23. The system according to any one of claims 19-22, wherein, The secure location of the controller includes the controller's non-erasable memory device.

24. The system according to any one of claims 19-22, wherein, The controller is also configured to: An alarm is generated when the requested emission level calibration parameters do not conform to the first emission level calibration parameters.

25. The system according to claim 23, wherein, The controller is also configured to: An alarm is generated when the requested emission level calibration parameters do not conform to the first emission level calibration parameters.

Images