Patent Description:
For example, motor drives often include hardware and software components that provide the motor drive with a high degree of versatility. Before putting the motor drive into service, it may be custom programmed with desired operating characteristics. Furthermore, during its lifetime, the motor drive may be updated or re-programmed several times. Such programming can be accomplished via an external human interface module (HIM) or personal computer. As such, a motor drive can support a first connection to an HIM, with this type of connection providing a means for the drive to supply power to the HIM as well as for bi-directional data flow between the drive and the HIM. Additionally, a motor drive can support a second connection to a personal computer, with this type of connection providing a means for the personal computer to supply power to the drive as well as for bi-directional data flow between the drive and the computer. <CIT> relates to diagnostic and/or control techniques for variable frequency drives. The variable frequency drive may be controlled by a controller that may conduct one or more tests or evaluations. The tests or evaluations may include determining whether a switching device in the variable frequency drive is open-circuited, short-circuited, or operating normally. The tests may include determining whether current provided at an inverter output of the variable frequency drive is within a predetermined range. An exemplary embodiment evaluates the drive for a short circuit condition, an open circuit condition, and a sensor error or failure condition, controls operation of the drive based upon these one or more evaluations, may abort operation of the drive based upon one or more evaluations, and may set a fault code indicative of the type of error encountered. <CIT> relates to an electronic device having a universal serial bus (USB) type-C interface and a power management method thereof. In the method, when the electronic device is connected with another electronic device through a USB cable, the electronic device recognizes a USB port through a configuration channel. Also, the electronic device recognizes a connection direction of the USB cable and receives power information from the other electronic device through the configuration channel. Then, based on the received power information, the electronic device determines whether to enter a downstream facing port (DFP) mode or an upstream facing port (UFP) mode. UMC100: "Technical Description", retrievable from the internet URL: https://library. com/public/00c5e886fce94931a3a2f18627421813/2CDC135032D0203. pdf is a technical manual for UMC100. The Universal Motor Controller (UMC) is an intelligent motor controller for <NUM>-phase AC induction motors combining the two classical functions of motor protection and motor management in a single device plus offering diagnostic and fieldbus communication. The device functions can be adjusted in a wide range to cover the needs of different industries. UMC100 is a further development of the UMC22. <CIT> relates to a USB fan, in particular to a USB fan with an anti-motor interference system. The utility model uses the principle that a diode is cut off by the reverse current and is conducted by the positive current. A USB interface of a computer is connected, two power wires which supply direct current supply are reversely intervened into a diode, and then the power wires are connected with a motor and the fan.

In the description, reference is made to the accompanying drawings which form a part hereof, and in which there is shown by way of illustrations one or more embodiments of the present disclosure. Such embodiments do not necessarily represent the full scope of the present disclosure, however, and reference is made therefore to the claims and herein for interpreting the scope of the present disclosure.

The present disclosure will be better understood and features, aspects and advantages other than those set forth above will become apparent when consideration is given to the following detailed description thereof.

Before any embodiments of the invention are explained in detail, it is to be understood that the embodiments are not limited in its application to the details of construction and the arrangement of components set forth in the following description or illustrated in the following drawings. Aspects of the present disclosure are capable of other embodiments and of being practiced or of being carried out in various ways.

The following discussion is presented to enable a person skilled in the art to make and use embodiments of the present disclosure. Various modifications to the illustrated embodiments will be readily apparent to those skilled in the art, and the generic principles herein can be applied to other embodiments and applications without departing from embodiments of the present disclosure. Thus, embodiments of the present disclosure are not intended to be limited to embodiments shown, but are to be accorded the widest scope consistent with the principles and features disclosed herein. The following detailed description is to be read with reference to the figures, in which like elements in different figures have like reference numerals. The figures, which are not necessarily to scale, depict selected embodiments and are not intended to limit the scope of embodiments of the present disclosure. Skilled artisans will recognize the examples provided herein have many useful alternatives and fall within the scope of embodiments of the present disclosure.

Disclosed herein are systems and methods for a motor drive including a dual-role universal serial bus (USB) port that supports dual-role data and/or dual-role power such that: (<NUM>) when a Human Interface Module (HIM) is connected to the dual-role USB port, the motor drive functions as a USB host providing power to the HIM and controlling data flow to and from the HIM; and (<NUM>) when a computer is connected to the dual-role USB port, the motor drive functions as a USB device receiving power from the computer and allowing the computer to control data flow to and from the motor drive. Additionally, in some embodiments, the motor drive can take one or more mitigation actions to prevent common mode noise between the motor drive and a connected computer when the motor drive is running.

For example, some current drives support connections with external HIMs via proprietary cables and protocols having data communication rates that require significant time for updates and may be too slow to provide a satisfactory customer experience. Additionally, some current drives may support connection to a personal computer for "mains-free programming" (that is, when DC bus power of the drive is not present), but do so by requiring the power structure of the motor drive to be physically disconnected from the control structure. On the other hand, embodiments described herein use a USB dual-role port as a single, standard connection port for both HIM and personal computer connections without requiring drive power structures to be disconnected. In this manner, the motor drive can act as a USB dual-role power (DRP) device, providing the ability to negotiate power flow such that the motor drive operates as a source to provide power to an HIM or operates as a sink to receive power from a computer. Furthermore, the motor drive can act as a USB dual-role data (DRD) device, providing high-speed data communication rates with the ability to negotiate control of data flow such that the USB port operates as a downstream facing port (DFP), where the motor drive acts as a USB host, when connected to an HIM and operates as an upstream facing port (UFP), where the motor drive acts as a USB device, when connected to a computer.

Accordingly, <FIG> is a schematic view of a motor drive <NUM> and an external device <NUM>, according to some embodiments. The motor drive <NUM> can include an outer housing <NUM> that houses power and control circuitry such as, for example, a power module <NUM> and a control module <NUM>. The motor drive <NUM> can be connected to a power source <NUM> and configured to drive a motor <NUM>. More specifically, in some embodiments, the motor drive <NUM> is adapted to receive three-phase power from the power source <NUM> and convert this fixed frequency input power to a controlled frequency output power to be applied to the motor <NUM>, as controlled by the power and control modules <NUM>, <NUM>. In some embodiments, the motor drive <NUM> can be a PowerFlex drive manufactured by Rockwell Automation.

According to some embodiments, the control module <NUM> is programmed according to a specific programming configuration desired for a particular application. That is, operating characteristics of the motor drive <NUM> may be determined, in part, by the programming configuration of the motor drive <NUM>. For example, the programming configuration may include any data, software, or firmware that is used to define the performance of the motor drive <NUM>, the appearance or performance of any user interfaces of the motor drive <NUM>, or the performance or user interface appearance of any peripheral devices communicatively coupled to the motor drive <NUM>. The programming configuration may include operating parameters, parameter customization data, and firmware for the motor drive <NUM> or any peripherals. Often, certain aspects of the programming configuration will be determined by a manufacturer, OEM, system integrator, or other service provider and transferred to the motor drive <NUM> from an external source. Furthermore, periodic updates of the programming configurations or operational codes may take place, such as when a motor drive <NUM> is replaced, the motor drive <NUM> application is altered, or firmware is updated. Accordingly, programming of the control module <NUM> may be accomplished through software configuration or firmware code that is loaded onto an internal computer-readable memory <NUM> of the control module <NUM> and accessed and/or executed by a microprocessor <NUM> (and/or one or more other processing devices, not shown) of the control module <NUM>.

Furthermore, the motor drive <NUM> can be coupled to the external device <NUM>, which can enable programming, monitoring, feedback, and/or control of the motor drive <NUM>. According to some embodiments, the external device <NUM> can include a display <NUM>, such as an LCD or other display device that may be used to provide feedback to the operator regarding the setting, performance or configuration of the motor drive <NUM>. The external device <NUM> can also include an input structure <NUM>, such as buttons, switches, touch pads, and/or a keypad, allowing input by a user. For example, the input structure <NUM> may be used to provide operator control of the motor drive <NUM>. As further described below, the external device <NUM> may be a human interface module <NUM> (HIM, such as a remote user interface or handheld user interface), as shown in <FIG>, or a computer <NUM> (such as a personal computer, laptop, tablet, etc.), as shown in <FIG>.

Referring still to <FIG>, the motor drive <NUM> can include a communications port <NUM> on the outer housing <NUM> that enables electronic communications between the motor drive <NUM> and the external device <NUM>. For example, the external device <NUM> can be coupled to the communications port <NUM> via a connector <NUM> (e.g., a cable), as shown in <FIG>, or directly coupled to the communications port <NUM>, e.g., via a plug (not shown) on the external device <NUM>. Generally, the communications port <NUM> can support high data communication rates, such as a rate greater than <NUM> kilobits per second (kbps), a rate from <NUM> kbps up to <NUM> megabits per second (Mbps), a rate greater than <NUM> Mbps, a rate from <NUM> kbps up to <NUM> gigabits per second (Gbps), or a rate from <NUM> kbps up to <NUM> Gbps. Furthermore, the communications port <NUM> can include dual-role power (DRP) features that support bi-directional power flow, therefore permitting the motor drive <NUM> to act as a source, providing power to the external device <NUM>, or permitting the motor drive <NUM> to act as a sink, being powered by the external device <NUM>, with the ability to alternate between the source and sink roles. Additionally, the communications port <NUM> can include dual-role data (DRD) features that support bi-directional data flow, acting as a downstream facing port (DFP), permitting the motor drive <NUM> to act as a host relative to the external device <NUM>, or acting as an upstream facing port (UFP), permitting the motor drive <NUM> to act as a device relative to the external device <NUM> (e.g., an external host), with the ability to alternate between the DFP and UFP roles.

In some embodiments, the communications port <NUM> can be a USB port. The communications port <NUM> can thus provi de a standard connector with means to allow USB endpoints (e.g., the motor drive <NUM> and/or the external device <NUM>) to detect and negotiate host/device behavior, as further described below. For example, the communications port <NUM> can be a USB Type-A port, a USB Type-B port (including a micro USB port or a mini USB port), or a USB Type-C port. Furthermore, in some embodiments, the communications port <NUM> can be a USB <NUM> dual-role port. For example, in one embodiment, the USB <NUM> standard can support data rates up to <NUM> Gbps, or data rates up to <NUM> Mbps. Accordingly, the USB port <NUM> can be used for data and power transfer between the motor drive <NUM> and the external device <NUM> when the motor drive <NUM> is coupled to the external device <NUM> via a direct connection, e.g., where the external device <NUM> includes a mating USB plug that can be plugged into the USB port <NUM>. As another example, as shown in <FIG>, the USB port <NUM> can be used for data and power transfer between the motor drive <NUM> and the external device <NUM> when the motor drive <NUM> is coupled to the external device <NUM> via a USB cable connection <NUM> between the USB port <NUM> and a corresponding USB port <NUM> on the external device <NUM>.

In light of the above, <FIG> illustrate various examples of the motor drive <NUM> coupled to external devices <NUM>, according to some embodiments. More specifically, <FIG> illustrates a motor drive <NUM> directly connected to an HIM <NUM>; <FIG> illustrates a motor drive <NUM> connected to an HIM <NUM> via a connector cable; <FIG> illustrates a motor drive <NUM> connected to a personal computer <NUM> via a connector cable; and <FIG> illustrates a motor drive <NUM> connected to a personal computer <NUM> via an isolating connector cable. It should be noted that any of the configurations illustrated in <FIG>, or any other configurations described herein comprising a motor drive <NUM> and an external device <NUM>, may be generally referred to as a motor drive system.

Referring now to <FIG>, an HIM <NUM> can be directly connected to the motor drive <NUM>. For example, as described above, the motor drive <NUM> includes a USB port <NUM> on its outer housing <NUM>. The HIM <NUM> can include a USB plug (not shown), for example along a rear side of its outer housing <NUM>, of the same type as the USB port <NUM> on the motor drive <NUM>, enabling a user to plug the HIM <NUM> into the motor drive <NUM> such that a USB cable is not required. In some embodiments, the motor drive <NUM> may also include a receptacle <NUM> to hold or support the HIM <NUM> when it is plugged into the USB port <NUM>. With this configuration, the motor drive <NUM> sources power to the HIM <NUM> (as shown by arrow <NUM>) when the motor drive <NUM> is powered, and data flow is bi-directional (as shown by arrow <NUM>) controlled by the motor drive <NUM>. More specifically, with this configuration, the motor drive <NUM> acts as the power source and the communications port <NUM> is a USB DFP, while the HIM <NUM> acts as the power sink and includes a USB UFP. The motor drive <NUM> may be powered to supply power to the HIM <NUM> using the external power source <NUM>, shown in <FIG>, which powers a DC power bus of the power module <NUM>, or an auxiliary power supply (such as an auxiliary <NUM>-volt power supply, not shown, that can be plugged into the motor drive <NUM>).

Referring now to <FIG>, an HIM <NUM> can be connected to the motor drive <NUM> via a connector cable <NUM>, such as a USB cable, that plugs into the USB port <NUM> on the outer housing <NUM> of the motor drive <NUM> and into a corresponding USB port <NUM> on the HIM <NUM>. Thus, the USB cable <NUM> can include USB plugs of a type that mates with the USB ports <NUM>, <NUM> on the motor drive <NUM> and the HIM <NUM>, respectively. In some embodiments, the USB cable <NUM> is a USB Type-C cable. However, in other embodiments, the USB cable <NUM> can include different respective USB plugs for the motor drive <NUM> and/or the HIM <NUM>. For example, USB <NUM> is backward compatible with previous USB speeds (such as USB <NUM>). Thus, while the motor drive <NUM> may include a USB <NUM> Type-C port <NUM>, it may still be compatible with a HIM <NUM> including a USB <NUM> port <NUM> or other older USB ports. With this configuration, the motor drive <NUM> sources power to the HIM <NUM> (as shown by arrow <NUM>) when the motor drive <NUM> is powered, and data flow is bi-directional (as shown by arrow <NUM>) controlled by the motor drive <NUM>. More specifically, with this configuration, the motor drive <NUM> acts as the power source and the communications port <NUM> is a USB DFP, while the HIM <NUM> acts as the power sink and includes a USB UFP. The motor drive <NUM> may be powered to supply power to the HIM <NUM> using the external power source <NUM>, shown in <FIG>, which powers a DC power bus of the power module, or an auxiliary power supply.

Referring now to <FIG>, a computer <NUM> can be connected to the motor drive <NUM> via a connector cable <NUM>, such as a USB cable, that plugs into the USB port <NUM> on the outer housing <NUM> of the motor drive <NUM> and into a corresponding USB port <NUM> on the computer <NUM>. Thus, the USB cable <NUM> can include USB plugs of a type that mates with the USB ports <NUM>, <NUM> on the motor drive <NUM> and the computer <NUM>, respectively. In some embodiments, the USB cable <NUM> is a USB Type-C cable. However, in other embodiments, the USB cable <NUM> can include different USB plugs, as discussed above. With this configuration, the computer <NUM> sources power to the motor drive <NUM> (as shown by arrow <NUM>), and data flow is bi-directional (as shown by arrow <NUM>), controlled by the computer <NUM>. More specifically, with this configuration, the motor drive <NUM> acts as the power sink and the communications port <NUM> is a USB UFP, while the computer <NUM> acts as the power source and includes a USB DFP. Accordingly, the computer <NUM> provides power to the motor drive <NUM>, or at least to the control module <NUM>, to enable "mains-free programming," which may be considered programming of the motor drive <NUM> when power is not provided to the motor drive <NUM> (e.g., via the power source <NUM> of <FIG> or an auxiliary power source). That is, the motor drive <NUM> may not be able to power a motor <NUM> if the motor drive <NUM> is not receiving power from the power source <NUM> (or an auxiliary power source), but can still be powered by the computer <NUM> at least for programming, monitoring, feedback, and/or control.

Thus, generally, the motor drive <NUM> may power a motor <NUM> when the computer <NUM> is coupled to the motor drive <NUM> for programming, monitoring, feedback, and/or control. However, the power module <NUM> need not be physically separated from the control module <NUM> to perform such programming, monitoring, feedback, and/or control. For example, in some embodiments, power may still be provided to the motor drive <NUM> via the power source <NUM> to run a connected motor <NUM> when the computer <NUM> is coupled to the motor drive <NUM>. Furthermore, as further described below, in some embodiments, USB communication between the motor drive <NUM> and the computer <NUM> may be disabled when power to the motor drive <NUM> (e.g., via the power source) is detected.

Referring now to <FIG>, a computer <NUM> can be connected to the motor drive <NUM> via an isolating connector cable <NUM>, such as a USB isolating cable, that plugs into the USB port <NUM> on the outer housing <NUM> of the motor drive <NUM> and into a corresponding USB port <NUM> on the computer <NUM>. Thus, the USB isolating cable <NUM> can include USB plugs of a type that mates with the USB ports on the motor drive <NUM> and the computer <NUM>, respectively. In some embodiments, the USB isolating cable <NUM> is a USB Type-C isolating cable. However, in other embodiments, the USB isolating cable <NUM> can include different USB plugs. Generally, the isolating cable <NUM> can provide high-voltage isolation between two connected devices. Thus, with this configuration, the motor drive <NUM> and the computer <NUM> can each power their respective side of the isolating cable <NUM> (as shown by arrows <NUM>), and data flow is bi-directional (as shown by arrows <NUM>), controlled by the computer <NUM>. More specifically, with this configuration, the motor drive <NUM> acts as a power source and the communications port <NUM> can be a USB UFP, while the computer <NUM> also acts as a power source and includes a USB DFP. Accordingly, power may still be provided to the motor drive <NUM> when the computer <NUM> is coupled to the motor drive <NUM> (e.g., via the power source of <FIG> or an auxiliary power source). Additionally, in some embodiments, this configuration can include a first USB cable <NUM> connected from the motor drive <NUM> to a separate USB isolator device (not shown) and a second USB cable <NUM> connected from the USB isolator device to the computer <NUM>.

In some embodiments, the communications port <NUM> on the motor drive <NUM> can be coupled to other USB devices. For example, in one embodiment, the communications port <NUM> can be connected to a wireless USB dongle (not shown), which may be wirelessly connected to an external device <NUM>. Accordingly, the USB dongle can act as a connector between the motor drive <NUM> and the external device <NUM>. With this configuration, the motor drive <NUM> and the external device <NUM> are each respectively powered, and data flow is bi-directional, controlled by the motor drive <NUM> or the external device <NUM>. As a result, the motor drive <NUM> and the external device <NUM> can communicate wirelessly, such as for wireless programming, monitoring, feedback, and/or control.

In light of these above examples, power direction and data control between the motor drive <NUM> and the external device <NUM> can be dependent on the type of external device <NUM>. Thus, generally, the motor drive <NUM> can power the external device <NUM> when the external device is of a first type and the motor drive <NUM> receives power from the external device <NUM> when the external device <NUM> is of a second type. Additionally, the motor drive <NUM> can control data transmission to the external device <NUM> when the external device <NUM> is of a first type and the motor drive <NUM> can allow the external device <NUM> to control data transmission when the external device <NUM> is of a second type. It should also be noted that power delivery and control of data flow can be independent. As a result, in some embodiments, the following power and data flow configurations can be achieved: (<NUM>) the motor drive <NUM> can supply power and control data flow; (<NUM>) the motor drive <NUM> can receive power and control data flow; (<NUM>) the external device can supply power and control data flow; and/or (<NUM>) the external device can receive power and control data flow.

Accordingly, as described above, in some embodiments, the motor drive <NUM> includes a USB <NUM> dual-role communications port <NUM> on its outer housing <NUM> for connection to an external device <NUM>. For example, <FIG> illustrates a block diagram of control circuitry of the motor drive <NUM> and the communications port <NUM>, according to some embodiments. Such control circuitry can be part of the control module <NUM>, in some embodiments. As shown in <FIG>, the control circuitry can include the microprocessor <NUM>, voltage regulators <NUM>, a drive voltage detection circuit <NUM>, a computer voltage detection circuit <NUM>, a USB power multiplexor <NUM>, and a configuration channel (CC) logic controller <NUM>.

Still referring to <FIG>, the USB power multiplexor <NUM> can provide control over sourcing power to or receiving power from the external device <NUM>. The CC logic controller <NUM> can manage monitoring and negotiation of connections with the external device <NUM>. The CC logic controller <NUM> can also provide partial control of the USB power multiplexor <NUM> to enable drive power-up for mains-free programming. The voltage regulators <NUM> can be used for logic and communications functions of the motor drive <NUM> and can be supplied by external power from the external device <NUM> and power from the power module <NUM> of the motor drive <NUM>. The microprocessor <NUM> can, among other things, monitor a connection status of potential power sources, via the drive voltage detection circuit <NUM> and the computer voltage detection circuit <NUM>, transmit and receive data with the USB-connected external device <NUM>, control the USB power multiplexor <NUM>, communicate with the CC controller <NUM>, e.g., to receive connection status, and provide indicator control, for example, to an indicator <NUM> (such as a light-emitting diode, LED) on the outer housing <NUM>, as further described below.

Additionally, <FIG> is a schematic illustration of connector pins of a USB <NUM> connection port <NUM> according to some embodiments. With reference to <FIG> and <FIG>, D+ and D-pins can be used for data transmission, connected to the microprocessor <NUM>. VBUS and GND pins can be used for power delivery, where VBUS pins (e.g., cable bus power) are connected to the USB power multiplexor <NUM>. CC1 and CC2 pins can be used for connection and orientation detection, connected to the CC controller <NUM>. That is, the CC pins can be monitored to determine what is connected to the communications port <NUM>, e.g., based on pull-up resistors (indicating a USB host or DFP), pull-down resistors (indicating a USB device or UFP) on the CC pins, or an ability to configure either pull-up or pull-down (indicating a dual-role data (DRD) device). As such, changes in data or power delivery roles can be communicated over the CC line.

It should be noted that, while USB <NUM> Type-C connections are shown and described above with respect to the motor drive communications port <NUM>, certain features may be utilized with older USB versions. Furthermore, as noted above, the external device <NUM> may include a different USB type port <NUM>. In such cases, data speeds may be governed by the older USB type port and connector cable <NUM>. For example, USB <NUM> is backward compatible with previous USB speeds, such as USB <NUM> speeds (e.g., up to <NUM> Mbps), via the D+/D- data lines. Furthermore, while single communications ports are shown and described herein, in some embodiments, the motor drive <NUM> may include multiple USB ports <NUM> and/or the HIM <NUM> and/or the computer <NUM> may include multiple USB ports <NUM> (e.g., to connect to multiple motor drives <NUM>). For example, in one embodiment, the motor drive <NUM> may include multiple USB ports <NUM> and, as a result, maybe connected to an HIM <NUM> and a personal computer <NUM> simultaneously.

Accordingly, via the control circuitry and physical cable interconnection logic, the motor drive <NUM> is able to determine what type of external device <NUM> is connected so that it may operate as a power source or power sink, or UFP or DFP, as described above. For example, as described above, the motor drive <NUM> can monitor USB connection status, e.g., via the CC controller <NUM>, and the motor drive <NUM> can monitor its DC bus to determine power supply status, e.g., via the voltage detection circuits, as further described below. In some embodiments, common mode noise is generated by a motor drive <NUM> powering (e.g., running or operating) a motor <NUM>. Such common mode noise can interfere with proper operation of connected chassis-grounded external devices <NUM>, such as a computer <NUM> (though, generally, such noise may not cause safety issues as the control module <NUM> of the motor drive <NUM> may also be chassis grounded to earth ground). As a result, in some embodiments, the motor drive <NUM> may be further programmed to take actions when a computer <NUM> is connected to the communications port <NUM> and the motor drive <NUM> is operating. According to the invention, one action is to inhibit motor start until the computer <NUM> is disconnected from the communications port <NUM>. As another example, one action may be to inhibit USB communication when a computer <NUM> is connected to the communications port <NUM> while the motor drive <NUM> is already running. As yet another example, one action may be to provide an alert when a computer <NUM> is connected to the communications port <NUM> while the motor drive <NUM> is already running, or when a computer <NUM> is connected to the communications port <NUM> and the motor drive <NUM> is instructed to start the motor <NUM>. Such alerts may be a visual warning message or audio warning through a user interface on the motor drive <NUM> (e.g., the motor drive <NUM> may include an embedded HIM with a display <NUM> and/or speaker), a visual warning through an LED <NUM> located on the outer housing <NUM>, such as by the communications port <NUM>, on the user interface, or at another location on the housing <NUM>, and/or a warning through the display <NUM> of the computer <NUM>.

In light of the above, <FIG> illustrates a method <NUM> according to some embodiments. Generally, one or more steps of the method <NUM> can be executed by the motor drive <NUM> or, more specifically, the control module <NUM> or, more specifically, the microprocessor <NUM>. Thus, any of the steps described herein may be considered to be carried out by the motor drive <NUM>, the control module <NUM>, and/or the microprocessor <NUM>. For example, one or more steps of the method <NUM> may be part of a program stored in memory <NUM> and executed by the microprocessor <NUM>. Additionally, while the steps of the method <NUM> are shown in a particular order, in some embodiments, the method <NUM> may not include all steps shown, may include additional steps, or may include the steps in a different order.

Referring still to <FIG>, generally, at step <NUM> the motor drive <NUM> can determine whether an external device is connected. If not, at step <NUM>, normal drive operation can be enabled and the method returns to step <NUM>. If, at step <NUM>, an external device connection is detected, the USB-connected device type can be determined at step <NUM>. The external device type can be a USB host, such as a computer <NUM> or a USB device, such as an HIM <NUM>, a wireless dongle, etc..

If, at step <NUM>, a USB device is detected, the motor drive <NUM> can act as a host with a DFP. Accordingly, at step <NUM>, power can be provided from the motor drive <NUM> to the USB device. By determining external device connection prior to enabling USB bus power to the external device <NUM>, the motor drive <NUM> (via the USB <NUM> port <NUM>) can help prevent short circuits from occurring, for example, if two hosts were connected. At step <NUM>, the motor drive <NUM> and the USB device can communicate, with data communication controlled by the motor drive <NUM>. Power and/or data communication between the motor drive <NUM> and the USB device can continue until the USB device is disconnected, as determined at step <NUM>. When the USB device is disconnected, the motor drive <NUM> returns to step <NUM> to again look for an external device connection.

If, at step <NUM>, a USB host is detected, the motor drive can act as a device with a UFP. Accordingly, at step <NUM>, the connection type may be determined. If, at step <NUM>, the USB host is connected to the motor drive <NUM> via an isolated connection, then isolated power is provided by both the motor drive <NUM> and the USB host at step <NUM>. At step <NUM>, the motor drive <NUM> and the USB host can communicate, with data communication controlled by the USB host. Power and/or data communication between the motor drive <NUM> and the USB host can continue until the USB host is disconnected, as determined at step <NUM>. When the USB host is disconnected, the motor drive <NUM> returns to step <NUM> to again look for an external device connection.

If, at step <NUM>, the USB host is connected to the motor drive <NUM> without an isolated connection, motor drive power supply status is determined at step <NUM>. That is, at step <NUM>, the microprocessor <NUM> can determine whether the motor drive <NUM> is running a connected motor <NUM> or received instruction to start running a connected motor <NUM>. If the motor <NUM> is not running and no motor start instruction is received, as determined at step <NUM>, power is provided from the USB host to the motor drive at step <NUM>. At step <NUM>, the motor drive <NUM> and the USB host can communicate, with data communication controlled by the USB host Power and/or data communication between the motor drive <NUM> and the USB host can continue until the USB host is disconnected, as determined at step <NUM>. When the USB host is disconnected, the motor drive <NUM> returns to step <NUM> to again look for an external device connection.

Thus, if the USB host remains connected, the motor drive <NUM> can return to step <NUM>, or return to step <NUM>. If, at step <NUM> (e.g., following step <NUM> or step <NUM>), the motor <NUM> is running or a motor start instruction is received, common mode noise mitigation actions are be taken at step <NUM>. In some embodiments, such actions at step <NUM> may include inhibiting power and/or data communication between the motor drive <NUM> and the USB host, such that steps <NUM> and/or <NUM> are skipped. According to the invention, such actions at step <NUM> includes inhibiting the motor <NUM> from being started, such that power and/or data communication between the motor drive <NUM> and the USB host at step <NUM> and <NUM>, respectively, are still enabled. Additionally, in some embodiments, such actions at step <NUM> may include providing an alert or warning only (e.g., via a display or LED indicator), such that power and/or data communication between the motor drive <NUM> and the USB host at step <NUM> and <NUM>, respectively, are still enabled. Accordingly, in such embodiments, the motor drive <NUM> may be able to run while the USB host is connected and communicating with the motor drive <NUM>, but a user may be alerted and, for example, encouraged to disconnect the USB host from the motor drive <NUM> during motor operation.

Additionally or alternatively, in some embodiments, at step <NUM>, motor drive power supply status can be determined by sensing a DC bus line of the motor drive <NUM>. The DC bus in the motor drive <NUM> can be monitored to determine whether an isolated connection is necessary to the USB host. For example, if DC bus is present, isolation may be required to the USB host and, if isolation is not present, firmware algorithms in the motor drive <NUM> can prohibit any motor operations from any source. If DC bus is not present, USB power from the USB host can be used to operate various low voltage parts of the motor drive <NUM> including, but not limited to, processors to flash the drive <NUM> or to read/write the configurations of the drive <NUM> (e.g., at steps <NUM> and <NUM>).

Claim 1:
A method performed by a motor drive (<NUM>) of operating the motor drive, the method comprising:
determining (<NUM>) a USB host is connected to the motor drive via a USB port (<NUM>) on the motor drive;
enabling (<NUM>) the USB host to provide power to the motor drive when the USB host is connected to the motor drive; and
taking (<NUM>) a common mode noise mitigation action when a motor connected to the motor drive is to be run,
wherein taking the common mode noise mitigation action includes preventing the motor from starting until the USB host is disconnected from the motor drive.