US9939795B2

Dynamic simulated motor for controller testing

Summary by NHIP

Dynamic Motor Simulator

The apparatus uses a simulator unit to process control signals and generate feedback representing variable frequency drive and load operation. Distinctive elements include simulating DC bus voltage, transistor desaturation conditions, and temperature readings at specific nodes like inverter and rectifier heat sinks.

Claim Score by NHIP

Read claim 9, the broadest

Abstract

A controller is configured to generate control signals to control a variable frequency drive coupled with a load. A simulator receives the control signals and processes the control signals. The simulator simulates a variable frequency drive and a load by generating feedback signals based on a model and the control signals. The controller receives the feedback signals from the simulator.

US9939795B2, drawing sheet 1 — Sheet 1 of 10

Term

9.6 yearsleft in the term

Expires 17 April 2036, including 814 days of term adjustment.

26 claims: 4 independent, 22 dependent

1
An apparatus comprising:a microprocessor-based controller configured to output variable frequency drive (VFD) control signals and receive VFD feedback signals;a simulator unit including a processing device, a memory device structured to store a set of instructions, and an input/output device structured configured to receive the VFD control signals from the controller and output the VFD feedback signals to the controller;anda computer configured to communicate simulation parameters to the simulator unit and operation commands to the controller;wherein the simulator unit is configured to execute the set of instructions with the processing device so as to simulate operation of a variable frequency drive operatively coupled to a load, including: processing the VFD control signals to determine one or more simulated inverter output voltages;processing the simulated inverter output voltages using a load model to determine one or more simulated inverter output currents;processing the simulated inverter output voltages and the simulated inverter output currents to determine the VFD feedback signals;andproviding the VFD feedback signals to the controller;wherein the simulator unit is further configured to process the simulation parameters and the VFD control signals to simulate a DC bus voltage of the variable frequency drive and the VFD feedback signals include the simulated DC bus voltage.
9
Broadest claimClaim Score 53, average(NHIP)A method, comprising:generating, with a control unit, control signals configured to control a variable frequency drive;simulating operation of the variable frequency drive and the load with a simulator;receiving, at the simulator, the control signals from the control unit;determining simulated inverter output voltages based on the control signals;determining simulated output currents based on a simulation mode that uses the simulated inverter output voltages;generating simulated operational data that includes the simulated inverter output voltages and the simulated output current;providing the simulated operational data to the control unit;andcontrolling operation of the simulator and the control unit with a computer configured to provide simulation parameters to the control unit and provide output commands to the control unit;processing the simulation parameters and the control signals to simulate a DC bus voltage of the variable frequency drive and the simulated operational data include a simulated DC bus voltage.
15
A system, comprising:a controller configured to output control signals to a variable frequency drive, wherein the control signals include voltages configured to control one or more switching devices to output a pulse width modulated (PWM) signal;a simulator including a processing device and a memory device structured to store a set of instructions which, when executed by the processing device, are configured to simulate the variable frequency drive and the load, including: receiving the control signals;processing the control signals to determine first simulated operational data;determining second simulated operational data based on a load model and the first simulated operational data;determining feedback signals based on the first simulated operational data and the second simulated operational data;andtransmitting the feedback signals to the controller;anda computer configured to communicate simulation parameters with the simulator;wherein the simulator is further configured to process the simulation parameters and the control signals to simulate a DC bus voltage of the variable frequency drive and the feedback signals include the simulated DC bus voltage.
22
A method, comprising:generating control signals, with a first computing device, to control operation of a variable frequency drive and a load;receiving the control signals with a second computing device;selecting, with a third computing device, a simulation mode to be used by the second computing device;processing the control signals to determine one or more first simulated operational data with the second computing device;processing, with the second computing device, the first simulated operational data according to the simulation mode from the third computing device and a load model to determine one or more second simulated operational data:processing, with the second computing device, the first simulated operational data and the second simulated operational data to determine feedback signals including DC bus voltage;transmitting the feedback signals to the first computing device;andmonitoring performance of the first computing device and the second computing device with the third computing device.

Independent claims4

61 paragraphs in 5 sections, as filed

The present application claims the benefit of U.S. Provisional Patent Application No. 61/756,264, filed on Jan. 24, 2013, which is hereby incorporated by reference in its entirety.

BACKGROUND

Variable frequency drives may handle high voltages and high currents in a number of applications including, for example, heating, ventilation, air conditioning, or refrigeration (HVACR) systems. An individual may be seriously injured or other components of or connected to the variable frequency may be damaged during the testing of the control system for the variable frequency drive. There is a need to provide testing and evaluation of the control system of the variable frequency drive. Existing approaches suffer from various shortcomings relative to these and other needs such as the need for cumbersome and expensive equipment, computational complexity and inefficiency, failsafe shortcomings, inability to simulate various modes of operation and/or failure modes and others. There remains a need for the unique and inventive apparatuses, methods and systems disclosed herein.

SUMMARY

An exemplary embodiment includes a simulator that simulates operation of a variable frequency drive coupled with a load. The simulator receives control signals from a control unit being tested, such as a microprocessor-based controller. The simulator processes the control signals and transmits feedback signals to the control unit. Other embodiments include apparatuses, systems, devices, hardware, methods, and combinations for a simulator that simulate a variable frequency drive and a load and provide an interface for receiving drive control signals from a device under test and providing feedback signals to the device under test. Further embodiments, forms, features, aspects, benefits, and advantages of the present application shall become apparent from the description and figures provided herewith.

BRIEF DESCRIPTION OF THE FIGURES

The description herein makes reference to the accompanying figures wherein like reference numerals refer to like parts throughout the several views, and wherein:

<figref idref="DRAWINGS">FIG. 1</figref> is schematic block diagram of an exemplary simulation system.

<figref idref="DRAWINGS">FIG. 2</figref> is schematic flow diagram of an exemplary process for controlling and monitoring the testing of a controller.

<figref idref="DRAWINGS">FIG. 3</figref> is schematic flow diagram of an exemplary process for controlling a variable frequency drive operatively coupled with a load.

<figref idref="DRAWINGS">FIG. 4</figref> is a schematic flow diagram of an exemplary process for simulating a variable frequency drive operatively coupled with a load.

<figref idref="DRAWINGS">FIG. 5</figref> is a schematic flow diagram of an exemplary process for determining currents based on an inductive load model.

<figref idref="DRAWINGS">FIG. 6</figref> is a schematic flow diagram of an exemplary process for determining currents based on an induction motor.

<figref idref="DRAWINGS">FIG. 7</figref> is a schematic block diagram of an exemplary computing device.

DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS

For the purposes of promoting an understanding of the principles of the invention, reference will now be made to the embodiments illustrated in the drawings and specific language will be used to describe the same. It will nevertheless be understood that no limitation of the scope of the invention is thereby intended. Any alterations and further modifications in the described embodiments, and any further applications of the principles of the invention as described herein are contemplated as would normally occur to one skilled in the art to which the invention relates.

<figref idref="DRAWINGS">FIG. 1</figref> illustrates a system 10 for testing a controller 12. The controller 12 is configured to control a variable frequency drive and a load. The load may be an inductive load, an induction motor, and/or a permanent magnet motor. In addition, the motor simulated may be designed to drive a chiller that is part of a heating, ventilating, air-conditioning, or refrigeration (HVACR) system. The system 10 includes a simulator 14, which simulates the operation of a variable frequency drive and a load. This allows the controller 12 to be tested without connecting the controller 12 to an actual variable frequency drive and motor.

The system 10 also includes a computer 16 to control and monitor the testing of the controller 12. The computer 16 communicates with the controller 12 over a bus 18, which may be implemented using an inter-module communication protocol. The computer 16 may send commands to the controller 12. For example, the computer 16 may instruct the controller 12 when to turn on or turn off, which mode to operate in, and/or use certain parameters during operation, among other commands. The controller 12 may also report status information to the computer 16. The status information may include data about the testing and operation of the controller 12.

The computer 16 communicates with the simulator 14 over a bus 20. In one embodiment, the bus 20 is implemented using a modbus communication protocol. The computer 16 may select a particular load model and/or simulation mode 22 for the simulator 14 to utilize. Furthermore, the load model 22 may be stored on the computer 16 and then sent to the simulator 14 or the simulator 14 may store one or more load models and the computer 16 selects the particular one for use. The computer 16 may also send parameters 24 to the simulator 14, which may be stored in a parameter table. The parameters 24 are used by the simulator to simulate a variable frequency drive and load. The simulator 14 also sends status information to the computer 16 using the bus 20. The status information may include data about the simulation and testing of the controller 12. The computer 16 also may have an interface that allows a user to select and issue commands and/or parameters.

The controller 12 transmits one or more control signals 26 to the simulator 14. The control signals 26 are configured to control a variable frequency drive and a load such as a motor. In addition, the control signals 26 may be configured to provide a pulse width modulated (PWM) signal at an inverter output, for example, by providing switch control signals which are voltage boosted and provided to control switching devices operating in concert to generate the PWM signal. For simplicity of description, such control signals will be referred to herein as PWM control signals. The simulator 14 processes the control signals 26 and uses them with the selected model 22 and/or parameters 24 to simulate operation of a variable frequency drive and a load to generate one or more feedback signals. Moreover, the simulator 14 may simulate one or more of the following components of the variable frequency drive including a rectifier, a DC voltage bus, an inverter, a gate drive module, fault sensors, current sensors, voltage sensors, temperature sensors, and the like.

The simulator 14 may process the control signals 26, including a PWM control signal, to determine one or more simulated inverter output voltages 28 based on the control signals 26, the model 22, and/or parameters 24. The simulated inverter output voltages 28 may be sent to the controller 12 as feedback signals.

The simulator 14 may then use the selected load model 22 and the simulated inverter output voltages 28 to determine one or more simulated output currents 30. The parameters 24 may also be used in determining the simulated output currents 30. These output currents would typically be measured by current sensors at an output of the inverter of the variable frequency drive such as at a load or motor terminal. For example, the simulated output currents 30 may represent the current at a motor terminal for each phase, multiple phases, or all of the phases of the variable frequency drive. The simulated output currents 30 may also be provided to the controller 12 as feedback signals.

The simulator 14 is also configured to simulate a DC voltage bus of a variable frequency drive by determining one or more simulated DC bus voltages 32 based on the control signals 26, the model 22, and/or parameters 24. As one example, a DC voltage bus may include a positive DC voltage rail and a negative DC voltage rail. Thus, the simulated DC bus voltages 32 may include a simulated positive DC rail voltage and/or a simulated negative DC rail voltage. It shall be understood that the terms positive and negative in this context are relative and that the actual polarities may be both positive, both negative, positive and negative, positive and zero, or negative and zero in various embodiments. The simulated DC bus voltages 32 may also be provided to the controller 12 as feedback signals.

The simulator 14 is also configured to simulate one or more temperature sensors by determining one or more simulated temperature readings 34 of a variable frequency drive based on the control signals 26, the model 22, and/or parameters 24. For example, the simulator 14 may determine a simulated temperature or a simulated temperature reading for one or more of the following locations in the variable frequency drive: at the transistors at the output of each phase of the inverter, at a heat sink for the inverter, and at a heat sink for the rectifier. Other locations on a variable frequency drive or motor for generating simulated temperature readings are contemplated. The simulated temperature readings 34 may also be provided to the controller 12 as feedback signals.

The simulator 14 is also configured to generate simulated fault conditions 36. The simulated fault conditions 36 may be based on the control signals 26, model 22, and/or parameters 24. For example, the simulator 14 may determine that the control signals 26 are causing a fault condition 36 such as a desaturation of a transistor that is part of the inverter of a variable frequency drive. Another example of a fault condition 36 is setting a simulated voltage or simulated current high or low. Another example of a fault condition is adjusting the flux scaling. Other examples include a fault in the communication bus, such as ASCII bus, between the simulator 14 and the controller 12. Other examples of faults related to the motor include a current/ground fault and a current/missing phase. Other examples of faults related to the variable frequency drive include current, voltage, measured ambient temperature, transistor drive desaturation detection, system/safety interaction, measured heat sink temperature, and bus voltage. Other fault conditions 36 are also contemplated.

The simulator 14 may also generate a simulated fault condition 36 based on the model 22 and/or parameters 24. In this way, the computer 16 may initiate a particular fault condition 36 to determine whether the controller 12 can correctly identify the fault condition 36 and adjust the control signals 26 correctly in response to the identified fault condition 36. The simulated fault condition 36 may also be provided to the controller 12 as feedback signals. In one embodiment, the simulator 14 provides the simulated fault conditions 36 to the controller 12 regularly. However, it is also contemplated that the controller 12 may poll the simulator 14 for fault data and the simulator 14 responds to the poll with the simulated fault conditions 36.

Although the various feedback signals, such as simulated inverter output voltages 28, simulated output currents 30, simulated DC bus voltages 32, simulated temperature readings 34, and simulated fault conditions 36 are shown as separate feedback lines, these feedback signals may be provided to the controller 12 together or separately or a combination thereof. For example, some of the simulated data or feedback signals may be provided to the controller 12 in a digital format such as ASCII, while other simulated data or feedback signals are provided to the controller 12 in an analog format.

<figref idref="DRAWINGS">FIG. 2</figref> illustrates a process 40 that may be implemented by the computer 16 to control and monitor the operation of the simulator 14 and the controller 12. Operations illustrated for all of the processes in the present application are understood to be examples only, and operations may be combined or divided, and added or removed, as well as re-ordered in whole or in part, unless explicitly stated to the contrary.

Process 40 begins with operation 42 in which the computer 16 determines and sends commands to the controller 12 and/or the simulator 14. For example, the computer 16 may instruct the controller 12 and/or the simulator 14 to power on, begin operation, and/or start a testing sequence. Other commands in addition to or in place of those described are contemplated.

Process 40 proceeds from operation 42 to operation 44. At operation 44, the computer 16 sets various parameters in the controller 12 and/or the simulator 14. For example, the computer 16 may select a load model 22 to be used by the simulator 14. The computer 16 may also initiate simulated fault conditions 36 and/or set certain parameters that would cause a simulated fault condition 36 to be generated by the simulator 14. In addition the computer 16 may set parameters in the controller 12 that are used by the controller 12 in generating the control signals 26. Other parameters in addition to or in place of those described are contemplated.

Process 40 proceeds from operation 44 to operation 46. At operation 46, the computer 16 receives status information regarding the operation of the controller 12 and/or the simulator 14. For example, the controller 12 may report to the computer 16 whether the controller 12 has identified any simulated fault conditions 36 and how the controller 12 corrected the control signals 26 in response to the identified fault conditions 36. As another example, the simulator 14 may report to the computer 16 various simulated data generated that is included in the feedback signals. This would allow a user of the computer 16 to determine whether controller 12 is generating the correct control signals 26 to control a variable frequency drive and motor appropriately. Other status information in addition to or in place of those described are contemplated.

Process 40 then proceeds to operation 48 in which it is determined whether testing should end. If testing should end, process 40 proceeds to operation 49 in which shutdown or exit commands are sent to the controller 12 and/or the simulator 14. If testing should not end, then process 40 proceeds back to operation 42 where a new set of test commands may be issued. It is contemplated that a user of the computer 16 may use a computer interface to select and send commands and/or parameters to the controller 12 and/or simulator 14.

<figref idref="DRAWINGS">FIG. 3</figref> illustrates a process 50 that may be implemented by the controller 12 for controlling a variable frequency drive and a load such as a motor. At operation 52, the controller 12 receives one or more commands from the computer 16. The commands may instruct the controller 12 how to carry out a particular test sequence or execute a mode of operation. For example, one example of a test sequence may be powering the motor at full capacity for a period of time and then powering the motor at partial capacity over another period of time. The commands may also include a power on or shut down command. Other commands in addition to or in place of those described are contemplated.

Process 50 then proceeds from operation 52 to operation 54. At operation 54, the controller 12 determines whether the command is a shutdown or an end test command. If the command is a shutdown or an end test command, then process 50 proceeds to operation 56 in which the controller 12 exits from testing. Otherwise, process 50 proceeds to operation 58.

At operation 58, the controller 12 generates the control signals 26, which may include a PWM control signal. The control signals 26 may be tailored to the specific variable frequency drive and/or motor hardware that the controller 12 believes that it is controlling. For example, the commands and parameters received from the computer 16 may indicate the particular hardware of the variable frequency drive and/or motor to be driven, which allows the controller 12 to tailor the control signals 26 for that hardware. As another example, the commands and/or parameters may establish a test sequence or mode of operation to be executed by the controller 12. For example, the commands and/or parameters may establish a period of time that controller 16 should operate, whether to power the variable frequency drive and motor fully or partially, and the like.

Process 50 then proceeds to operation 60 in which the controller 12 receives feedback signals from the simulator 14. The controller 12 processes the feedback signals to determine whether the control signals 26 are producing the correct voltages and currents in the variable frequency drive and motor and whether any fault conditions 36 exist. If the controller determines that the voltages, currents, and/or temperature readings are not at approximately the target values or if there is a fault condition, the controller 12 will adjust the control signals 26 to correct the issue.

Process 50 then proceeds from operation 62 to operation 64 in which the controller 12 reports status information to the computer 16. The status information may include any information about the operation of the controller 12 including information about the control signals 26, information about any of the simulated data received in the feedback signals, and/or any information that indicates a fault condition. Process 50 then proceeds from operation 64 back to operation 52 in which controller 12 receives data such as a command from the computer 16.

<figref idref="DRAWINGS">FIG. 4</figref> illustrates a schematic flow diagram of a process 70 that may be implemented by the simulator 14 for simulating a variable frequency drive and a load such as a motor or an inductive test load. Process 70 begins with operation 72 in which the simulator 14 receives data in the form of commands and/or parameters from the computer 16. As discussed above, the commands and/or parameters from the computer 16 relates to the particular type of variable frequency drive and/or load that the simulator 14 will simulate as well as any fault conditions that are to be simulated. For example, the computer 16 may select a particular type of load to be simulated such as an inductive load, an induction motor, and/or a permanent magnet motor.

Process 70 proceeds from operation 72 to operation 74 in which it is determined whether the command is to exit the testing or shutdown the simulator 14. If the received command is a shutdown or exit command, then process 70 proceeds to operation 72 in which the testing is exited and/or the simulator 14 a shutdown. If the command is not a shutdown or exit command, then process 70 proceeds to operation 78.

At operation 78, the simulator 14 receives the control signals 26 from the controller 12. The control signals 26 include a PWM control signal, which is used by the switching devices, e.g., transistors, of the inverter to generate the output voltage and output current to power the load such as a motor.

Process 70 then proceeds from operation 78 to operation 80. In operation 80, the simulator 14 simulates the inverter of a variable frequency drive by determining one or more simulated inverter output voltages 28 based on the control signals 26, the model 22, and/or parameters 24. The simulator 14 may determine a simulated inverter output voltage 28 for some or all of the phases of the variable frequency drive being simulated. In addition, at operation 80, the simulator 14 may also increment a voltage counter that may be part of a parameters table. The voltage counter may be used by the simulator 14 for performing various voltage and/or current calculations.

Process 70 then proceeds from operation 80 to one of operations 82, 84, or 86, which relate to the various load models 22 that may be used by simulator 14. The simulator 14 will use the load model 22 selected by the computer 16. As shown in <figref idref="DRAWINGS">FIG. 4</figref>, there are three load models: an inductive load, an induction motor, or a permanent magnet motor. It is contemplated that other loads and models may be used with the present application other than the three shown in <figref idref="DRAWINGS">FIG. 4</figref>.

Process 70 then proceeds to operation 88 in which the simulated output currents 30 are determined based on the control signals 26, the model 22, parameters 24 and/or the simulated inverter output voltages 28. <figref idref="DRAWINGS">FIGS. 5 and 6</figref> and their accompanying description will describe the process for calculating the simulated output currents 30 in more detail.

Process 70 then proceeds to operation 90 in which the simulator 14 determines the simulated DC bus voltages 32 based on the control signals 26, the model 22, and/or parameters 24. Furthermore, the simulator 14 may determine a positive DC rail voltage and a negative DC rail voltage.

Process 70 then proceeds from operation 90 to operation 92 in which the simulator 14 determines one or more simulated temperature readings based on the control signals 26, the model 22, and/or parameters 24. The locations of the simulated temperature readings 34 may include at the transistors at the output of each phase of the inverter, at a heat sink for the inverter, and heat sink for the rectifier.

Process 70 then proceeds from operation 92 to operation 94 in which the simulator 14 generates simulated fault conditions 36 based on the control signals 26, the model 22, and/or parameters 24. One example of a fault condition is a desaturation of a transistor of the inverter being simulated. Other examples of faults include setting simulated voltages, simulated currents, and/or simulated temperature readings high or low, which may indicate a fault condition or failure to the controller 12. Other fault conditions in addition to or in place of those discussed are also contemplated.

Process 70 then proceeds from operation 94 to operation 96 in which the simulator 14 generates one or more feedback signals based on the simulated inverter output voltages 28, the simulated output currents 30, the simulated DC bus voltages 32, the simulated temperature readings 34, and the simulated fault conditions 36. The feedback signals are then provided by the simulator 14 to the controller 12.

Process 70 then proceeds from operation 96 to operation 98 in which simulator 14 updates its parameter tables based on data received from the computer 16, the control signals 26 from the controller 12, and/or based on the simulated data calculated such as the simulated inverter output voltages 28, the simulated output currents 30, the simulated DC bus voltages 32, the simulated temperature readings 34, and the simulated fault conditions 36. Process 70 then proceeds from operation 98 back to operation 72 and operation 74 in which the simulator 14 determines whether to exit testing or to continue.

<figref idref="DRAWINGS">FIG. 5</figref> illustrates a schematic flow diagram of a process 100 that may be implemented by the simulator 14 for determining the simulated output currents 30 according to an inductive load model as shown at operation 82 in <figref idref="DRAWINGS">FIG. 4</figref>. Process 100 begins at operation 102 in which the simulated inverter output voltages 28 are inputted and transformed from a three coordinate system ABC to a two coordinate system αβ. This transformation may be performed to simplify the calculations to determine the simulated output currents. It is contemplated that although a three-phase system is shown, other systems with a different number of phases may be used with the present application.

Process 100 then proceeds from operation 102 to operation 104. At operation 104, the simulator 14 solves the following equations to determine the currents where L is inductance, v is voltage, and i is current, and the subscripts a, b, c refer to the three phases:

After the equations are solved, process 100 then proceeds from operation 104 to operation 106. In operation 106, the data is transformed from a two coordinate system αβ to a three coordinate system ABC. The outputs of operation 106 are the simulated output currents 30.

<figref idref="DRAWINGS">FIG. 6</figref> illustrates a schematic flow diagram of a process 110 that may be implemented by the simulator 14 for determining the simulated output currents 30 according to an induction motor model as shown at operation 84 in <figref idref="DRAWINGS">FIG. 4</figref>. Process 110 begins at operation 112 in which the simulated inverter output voltages 28 are inputted and transformed from a three coordinate system ABC to a two coordinate system αβ. This transformation may be performed to simplify the calculations to determine the simulated output currents 30. It is contemplated that although a three-phase system is shown, other systems with a different number of phases may be used with the present application.

Process 110 then proceeds from operation 112 to operation 114. At operation 114, the simulator 14 converts the voltages from a stator frame of reference to a rotor frame of reference. Process 110 then proceeds from operation 114 to operation 116, which solves the following equations to determine the currents where L is inductance, v is voltage, i is current, ψ is flux, rs is linkage, ωb is rated frequency (rad/sec), Zb is 100% (normalized) impedance, Ci is a factor to allow 1.0 to represent an overcurrent condition, Cw is a factor to allow 1.0 to represent an overspeed condition M is normalized rotational inertia (units of seconds), and σLs is an induction motor parameter:

Process 110 then proceeds from operation 116 to operation 118. At operation 118, the simulator 14 converts the system from a rotor frame of reference to a stator frame of reference. Process 110 then proceeds to operation 120 in which the data is transformed from a two coordinate system αβ to a three coordinate system ABC. The outputs of operation 110 are the simulated output currents 30.

The process for determining the simulated output currents 30 in which a permanent magnet motor model is used is similar to the process 110 where an induction motor model is used. Moreover, the equations to be solved for a permanent magnet motor would been those known to persons of ordinary skill in the art.

<figref idref="DRAWINGS">FIG. 7</figref> is a schematic block diagram of a computing device 200. The computing device 200 is one example of a controller, simulator, and/or computer configuration which may be utilized in connection with the controller 12, simulator 14, and/or computer 16 shown in <figref idref="DRAWINGS">FIG. 1</figref>. Computing device 200 includes a processing device 202, an input/output device 204, memory 206, and operating logic 208. Furthermore, computing device 200 communicates with one or more external devices 210.

The input/output device 204 allows the computing device 200 to communicate with the external device 210. For example, the input/output device 204 may be a network adapter, network card, interface, or a port (e.g., a USB port, serial port, parallel port, an analog port, a digital port, a modbus interface, an ASCII interface, VGA, DVI, HDMI, FireWire, CAT 5, or any other type of port or interface). The input/output device 204 may be comprised of hardware, software, and/or firmware. It is contemplated that the input/output device 204 includes more than one of these adapters, cards, or ports.

The external device 210 may be any type of device that allows data to be inputted or outputted from the computing device 200. For example, the external device 210 may be a handheld computer or diagnostic tool, a controller, a simulator, a computer, a server, a printer, a display, an alarm, an illuminated indicator such as status indicator 152, a keyboard, a mouse, or a touch screen display. Furthermore, it is contemplated that the external device 210 may be integrated into the computing device 200. It is further contemplated that there may be more than one external device in communication with the computing device 200.

Processing device 202 can be of a programmable type, a dedicated, hardwired state machine, or a combination of these; and can further include multiple processors, Arithmetic-Logic Units (ALUs), Central Processing Units (CPUs), Digital Signal Processors (DSPs) or the like. For forms of processing device 202 with multiple processing units, distributed, pipelined, and/or parallel processing can be utilized as appropriate. Processing device 202 may be dedicated to performance of just the operations described herein or may be utilized in one or more additional applications. In the depicted form, processing device 202 is of a programmable variety that executes algorithms and processes data in accordance with operating logic 208 as defined by programming instructions (such as software or firmware) stored in memory 206. Alternatively or additionally, operating logic 208 for processing device 202 is at least partially defined by hardwired logic or other hardware. Processing device 202 can be comprised of one or more components of any type suitable to process the signals received from input/output device 204 or elsewhere, and provide desired output signals. Such components may include digital circuitry, analog circuitry, or a combination of both.

Memory 206 may be of one or more types, such as a solid-state variety, electromagnetic variety, optical variety, or a combination of these forms. Furthermore, memory 206 can be volatile, nonvolatile, or a combination of these types, and some or all of memory 206 can be of a portable variety, such as a disk, tape, memory stick, cartridge, or the like. In addition, memory 206 can store data that is manipulated by the operating logic 208 of processing device 202, such as data representative of signals received from and/or sent to input/output device 204 in addition to or in lieu of storing programming instructions defining operating logic 208, just to name one example. As shown in <figref idref="DRAWINGS">FIG. 7</figref>, memory 206 may be included with processing device 202 and/or coupled to the processing device 202.

The processes 40, 50, 70, 100, and 110 may be implemented in operating logic 208 as operations by software, hardware, artificial intelligence, fuzzy logic, or any combination thereof, or at least partially performed by a user or operator. In certain embodiments, modules represent software elements as a computer program encoded on a computer readable medium, wherein the controller 12, simulator 14, and/or computer 16 performs the described operations when executing the computer program.

The present application refers to some voltages, currents, and/or readings as being determined “approximately.” As used herein, “approximately” is to generally account for the error or impreciseness of measuring a voltage or current or they may change over small amounts of time. The number of volts or amps that are acceptable under “approximately” depends on the system. In some systems, less than one volt or one amp may be acceptable, but in other systems, several volts or several amps will be within “approximately.” In addition, even if a comparison or evaluation does not refer to “approximately,” the present application presumes that there is an accounting for the impreciseness in the system.

While the invention has been described in connection with what is presently considered to be the preferred embodiment, it is to be understood that the invention is not to be limited to the disclosed embodiment(s), but on the contrary, is intended to cover various modifications and equivalent arrangements included within the spirit and scope of the appended claims, which scope is to be accorded the broadest interpretation so as to encompass all such modifications and equivalent structures as permitted under the law. Furthermore it should be understood that while the use of the word preferable, preferably, or preferred in the description above indicates that feature so described may be more desirable, it nonetheless may not be necessary and any embodiment lacking the same may be contemplated as within the scope of the invention, that scope being defined by the claims that follow. In reading the claims it is intended that when words such as “a,” “an,” “at least one” and “at least a portion” are used, there is no intention to limit the claim to only one item unless specifically stated to the contrary in the claim. Further, when the language “at least a portion” and/or “a portion” is used the item may include a portion and/or the entire item unless specifically stated to the contrary.

Contents5

Every citation, both waysCites: the store holds 17 of 18

Citations
Document	Relation	Office	Cited during
CN107576518A	Cited by	China	Search report
US2022221849A1	Cited by	United States of America	Search report
WO2008006116A2	Cites	World Intellectual Property Organization (WIPO)	Applicant
US2009085572A1	Cites	United States of America	Search report
US2012133389A1	Cites	United States of America	Applicant
US2012191439A1	Cites	United States of America	Applicant
US2012232869A1	Cites	United States of America	Applicant
US5524498A	Cites	United States of America	Applicant
US7199549B2	Cites	United States of America	Search report
US7880460B2	Cites	United States of America	Search report
US8108191B1	Cites	United States of America	Applicant
US8249845B1	Cites	United States of America	Applicant
US8880250B2	Cites	United States of America	Search report
US9490682B2	Cites	United States of America	Search report
US20090085572A1	Cites	United States of America	Search report
US20120133389A1	Cites	United States of America	Applicant
US20120191439A1	Cites	United States of America	Applicant
US20120232869A1	Cites	United States of America	Applicant
WO2008006116	Cites	World Intellectual Property Organization (WIPO)	Applicant

6 priority claims, no other members on record

This recordMember, by publication datePriority claim

Priority claims6

Priority claims
Document	Office	Kind	Date
201361756264	United States of America	P	2013-01-24
201361756264	United States of America	P	2013-01-24
201414162924	United States of America	A	2014-01-24
61756264	–	–	–
US201361756264P	–	–	–
US201414162924	–	–	–

75 transactions on the USPTO file

Allowed after 2 non-final rejections, 1 final rejection and 1 RCE.

Non-final rejections: 2
Final rejections: 1
RCEs: 1
Appeals: 0

Over time

Point at a mark for the transaction

Transactions

Prosecution transactions, newest first
	Event	Code
2018-04-10	Recordation of Patent Grant MailedPGM/	PGM/
2018-04-10	Patent Issue Date Used in PTA CalculationAllowedPTAC	PTAC
2018-03-22	Email NotificationEML_NTR	EML_NTR
2018-03-21	Issue Notification MailedAllowedWPIR	WPIR
2018-03-06	Dispatch to FDCD1935	D1935
2018-03-06	Dispatch to FDCD1935	D1935
2018-03-02	Application Is Considered Ready for IssuePILS	PILS
2018-03-01	Issue Fee Payment VerifiedN084	N084
2018-03-01	Issue Fee Payment ReceivedIFEE	IFEE
2017-12-01	Electronic ReviewELC_RVW	ELC_RVW
2017-12-01	Email NotificationEML_NTF	EML_NTF
2017-12-01	Mail Notice of AllowanceAllowedMN/=.	MN/=.
2017-11-22	Notice of Allowance Data Verification CompletedAllowedN/=.	N/=.
2017-11-08	Reasons for AllowanceEX.R	EX.R
2017-10-24	Date Forwarded to ExaminerFWDX	FWDX
2017-10-18	Response after Non-Final ActionA...	A...
2017-07-18	Electronic ReviewELC_RVW	ELC_RVW
2017-07-18	Email NotificationEML_NTF	EML_NTF
2017-07-18	Mail Non-Final RejectionNon-final rejectionMCTNF	MCTNF
2017-07-13	Non-Final RejectionNon-final rejectionCTNF	CTNF
2017-06-07	Date Forwarded to ExaminerFWDX	FWDX
2017-06-07	Disposal for a RCE / CPA / R129AbandonedABN9	ABN9
2017-06-06	Request for Continued Examination (RCE)RCEX	RCEX
2017-06-06	Workflow - Request for RCE - BeginBRCE	BRCE
2017-05-26	Mail Interview Summary - Applicant Initiated - TelephonicMEXAT	MEXAT
2017-05-23	Interview Summary - Applicant Initiated - TelephonicEXAT	EXAT
2017-05-22	Miscellaneous Incoming LetterLET.	LET.
2017-05-18	Email NotificationEML_NTR	EML_NTR
2017-05-18	Mail Advisory Action (PTOL - 303)MCTAV	MCTAV
2017-05-14	Advisory Action (PTOL-303)CTAV	CTAV
2017-05-08	Date Forwarded to ExaminerFWDX	FWDX
2017-05-05	Response after Final ActionA.NE	A.NE
2017-05-05	Electronic request for Examiner InterviewM865E	M865E
2017-03-06	Electronic ReviewELC_RVW	ELC_RVW
2017-03-06	Email NotificationEML_NTF	EML_NTF
2017-03-06	Mail Final Rejection (PTOL - 326)Final rejectionMCTFR	MCTFR
2017-03-01	Final RejectionFinal rejectionCTFR	CTFR
2017-01-25	Date Forwarded to ExaminerFWDX	FWDX
2016-12-27	Response after Non-Final ActionA...	A...
2016-09-26	Electronic ReviewELC_RVW	ELC_RVW
2016-09-26	Email NotificationEML_NTF	EML_NTF
2016-09-26	Mail Non-Final RejectionNon-final rejectionMCTNF	MCTNF
2016-09-15	Non-Final RejectionNon-final rejectionCTNF	CTNF
2016-09-13	Information Disclosure Statement consideredIDSC	IDSC
2016-07-30	Case Docketed to Examiner in GAUDOCK	DOCK
2016-06-08	Close TICLTI	CLTI
2016-06-08	Case Docketed to Examiner in GAUDOCK	DOCK
2016-06-03	Transfer Inquiry to GAUTI1050	TI1050
2016-03-09	Case Docketed to Examiner in GAUDOCK	DOCK
2016-03-07	Case Docketed to Examiner in GAUDOCK	DOCK
2016-01-08	Oath or Declaration Filed (Including Supplemental)C602	C602
2015-10-29	Email NotificationEML_NTR	EML_NTR
2015-10-29	Change in Power of Attorney (May Include Associate POA)PA..	PA..
2015-10-28	Correspondence Address ChangeC.AD	C.AD
2015-09-28	Electronic Information Disclosure StatementEIDS.	EIDS.
2015-09-28	Information Disclosure Statement (IDS) FiledWIDS	WIDS
2015-08-31	Application ready for PDX access by participating foreign officesCCRDY	CCRDY
2014-08-08	Email NotificationEML_NTR	EML_NTR
2014-08-07	PG-Pub Issue NotificationPG-ISSUE	PG-ISSUE
2014-07-07	Case Docketed to Examiner in GAUDOCK	DOCK
2014-05-02	Email NotificationEML_NTR	EML_NTR
2014-05-02	Application Is Now CompleteCOMP	COMP
2014-05-02	Application Is Now CompleteCOMP	COMP
2014-05-02	Filing Receipt - UpdatedFLRCPT.U	FLRCPT.U
2014-05-01	Application Dispatched from OIPEOIPE	OIPE
2014-05-01	FITF set to NO - revise initial settingFTFI	FTFI
2014-02-19	Patent Term Adjustment - Ready for ExaminationPTA.RFE	PTA.RFE
2014-02-19	Additional Application Filing FeesADDFLFEE	ADDFLFEE
2014-02-07	Notice Mailed--Application Incomplete--Filing Date AssignedINCD	INCD
2014-02-07	Filing ReceiptFLRCPT.O	FLRCPT.O
2014-01-28	Cleared by OIPE CSRL194	L194
2014-01-24	Applicants have given acceptable permission for participating foreignAPPERMS	APPERMS
2014-01-24	IFW Scan & PACR Auto Security ReviewSCAN	SCAN
2014-01-24	Entity status set to undiscounted (initial default setting or status change)BIG.	BIG.
2014-01-24	Initial Exam Team nnIEXX	IEXX

3 legal events, as the office reported them to INPADOC

Over the term

Point at a mark for the event

Events

Legal events, newest first
	Event	Code
2021-09-23	Maintenance fee paymentMAFP	MAFP
2018-03-21	Information on status: patent grantGrantedSTCF	STCF
2015-10-15	AssignmentAS	AS

Dynamic simulated motor for controller testing

Summary by NHIP

Claim Score by NHIP

Abstract