Motor Drive
The modular motor drive system addresses the challenge of integrating ELV and NELV modules by using isolated digital communication, ensuring safe and efficient operation through secure data transfer and control, enhancing module compatibility and safety.
Patent Information
- Application Number
- GB2024018049
- Authority / Receiving Office
- GB · GB
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2024-12-10
- Publication Date
- 2026-11-11
AI Technical Summary
Existing modular motor drives face challenges in ensuring safe and efficient configuration and operation due to the difficulty in connecting non-extra low voltage (NELV) drive modules, which are unsafe for direct user interaction, with extra low voltage (ELV) drive modules that are safe.
A modular motor drive system is designed with an ELV drive module and an NELV drive module connected via an isolated digital communications device, allowing safe data transfer and control between the modules using an ELV digital interconnect, ensuring electrical isolation and efficient operation.
The system enables safe and efficient configuration and operation of modular motor drives by allowing ELV and NELV modules to communicate securely, ensuring compatibility and safety through isolated digital communication, thereby preventing unsafe operations and facilitating seamless module integration.
Smart Images

Figure 00000000_0000_ABST
Abstract
Description
FIELD OF THE INVENTION The present invention relates to a motor drive. BACKGROUND Motor drives are known. Such motor drives are used to control the speed and operation of a motor to which the motor drive is connected. Motors of different configurations, sizes and operating characteristics are typically coupled with an appropriate motor drive suitably configured to control the speed and operation of that motor. To simplify the provision of a motor drive suited to a particular motor, it is known to provide a motor drive which is assembled from individual different drive modules having different characteristics to create a motor drive suitable for that particular motor. However, providing a modular motor drive can have unexpected consequences. Accordingly, it is desired to provide an improved motor drive. SUMMARY According to a first aspect, there is provided a modular motor drive, comprising: an extra low voltage ELV drive module; and a non-extra low voltage NELV drive module having an isolated digital communications device configured to transmit data relating to the NELV drive module to the extra low voltage ELV drive module, the ELV drive module being configured to process the data relating to the NELV drive module and to generate a signal for transmission over the isolated digital communications device to control the NELV drive module. The first aspect recognises that a problem with existing arrangements is that it can be difficult to ensure a safe configuration of the modular motor drive. Accordingly, a modular, segmented or separate component motor drive is provided. The modular motor drive may comprise an extra low voltage ELV drive module. The ELV drive module may be a module that is compliant with ELV requirements meaning that it would be safe for direct interaction with a user. The modular motor drive may comprise a non-extra low voltage NELV drive module. The NELV drive module may be a module that is not compliant with ELV requirements meaning that it would be unsafe for direct interaction with a user. The NELV drive module may have an isolated digital communications device. The isolated digital communications device may be configured to transmit data or information relating to the NELV drive module to an extra low voltage ELV drive module of the modular motor drive. The ELV drive module may be configured to process the data relating to the NELV drive module. The ELV drive module may be configured to generate a signal for transmission over the isolated digital communications device to control the NELV drive module. In this way, the NELV drive module may be safely connected in an efficient way to the ELV module to facilitate the transfer of data or information between the ELV module and the NELV module. This enables information relating to the configuration or operation of the modular motor drive to be safely transferred between the ELV module and the NELV module. The information may be processed by the ELV drive module and signals transmitted to NELV module to help ensure a safe configuration or operation of the modular motor drive. The isolated digital communications device may comprise a processing device coupled with a series pair of devices comprising an ELV isolator device and a digital communications device. The combined ELV isolator device and digital communications device provides for safe connection between the ELV module and the NELV module, while the processing device enables data to be encoded appropriately for transmission over an ELV digital interconnect. The NELV drive module may comprise an ELV digital interconnect coupled with the isolated digital communications device. The ELV digital interconnect may be couplable with the ELV drive module to convey the data. The ELV digital interconnect may comprise a twisted pair. Using a twisted pair facilitates simply electrical isolation between the ELV module and the NELV module. The ELV digital interconnect may comprise a bus. Providing a bus facilitates the transmission of data between the ELV module and the NELV module. Such data is encoded for transmission and typically packetized for efficient transmission. The data may comprise telemetry or operational data or parameters related to an operation of the NELV drive module. The isolated digital communications device may be configured to receive the telemetry or operational data or parameters related to an operation of the NELV drive module. The isolated digital communications device may be configured to transmit the telemetry or operational data or parameters over the ELV digital interconnect to the ELV drive module. The data may comprise telemetry data from at least one sensor on the NELV drive module. The isolated digital communications device may be configured to receive the telemetry data from at least one sensor on the NELV drive module. Hence, sensors on the NELV drive module may be used to collect data related to the operation of the NELV drive module. The data may comprise configuration data related to a configuration of the NELV drive module. The isolated digital communications device may be configured to receive the configuration data related to a configuration of the NELV drive module. The isolated digital communications device may be configured to transmit the configuration data over the ELV digital interconnect to the ELV drive module. Hence, a configuration of or information relating to a type of the NELV drive module may be provided to the ELV drive module. This may enable the ELV drive module determine that the NELV drive module is suitable for use and indicate how the NELV drive module is to be configured and / or driven and / or which operational parameters the NELV drive module is likely to provide. The data may comprise the configuration data from storage on the NELV drive module. The isolated digital communications device may be configured to receive the configuration data from storage on the NELV drive module. Hence, the configuration data may be pre-stored on the NELV drive module. The storage may comprise non-volatile memory associated with the processing device. The NELV drive module may comprise a NELV interconnect coupled with the isolated digital communications device and couplable with at least one secondary NELV drive module. Hence, other NELV drive modules may also connect with the NELV drive module. Those other NELV drive modules do not require an ELV digital interconnect but instead may be coupled using NELV digital interconnects. The data may comprise telemetry data related to an operation of the least one secondary NELV drive module. The isolated digital communications device may be configured to receive the telemetry data related to an operation of the least one secondary NELV drive module. The isolated digital communications device may be configured to transmit the telemetry data to the ELV drive module. Hence, the isolated digital communications device may also convey data related to any secondary NELV drive modules. The data may comprise telemetry data from at least one sensor on the least one secondary NELV drive module. The isolated digital communications device may be configured to receive the telemetry data from at least one sensor on the least one secondary NELV drive module. The data may comprise configuration data related to a configuration of the least one secondary NELV drive module. The isolated digital communications device may be configured to receive the configuration data related to a configuration of the least one secondary NELV drive module. The isolated digital communications device may be configured to transmit the configuration data to the ELV drive module. The data may comprise configuration data from storage on the least one secondary NELV drive module. The isolated digital communications device may be configured to receive the configuration data from storage on the least one secondary NELV drive module. The processing device may be configured to transmit the data in response to a request received from the ELV drive module. The NELV drive module may comprise a NELV interconnect coupled with the isolated digital communications device and couplable with a motor. The data may comprise telemetry data related to an operation of the motor. The isolated digital communications device may be configured to receive the telemetry data related to an operation of the motor. The isolated digital communications device may be configured to transmit the telemetry data to the ELV drive module. The data may comprise telemetry data from at least one sensor on the motor. The isolated digital communications device may be configured to receive the telemetry data from at least one sensor on the motor. The data may comprise configuration data related to a configuration of the motor. The isolated digital communications device may be configured to receive the configuration data related to a configuration of the motor. The isolated digital communications device may be configured to transmit the configuration data to the ELV drive module. The data may comprise configuration data from storage on the motor. The isolated digital communications device may be configured to receive the configuration data from storage on the motor. The processing device may be configured to transmit the data in response to a request received from the ELV drive module. The processing device may be configured to transmit the data in response to a request received from the ELV drive module over the ELV digital interconnect. The processing device may be configured to request the data in response to a request received from the ELV drive module over the ELV digital interconnect. The processing device may be configured to transmit a warning indicator over the ELV digital interconnect when the telemetry data is outside normal operating parameters. Hence, local processing of the telemetry data may be performed by the processing device. The telemetry data may comprise at least one of temperature data and coolant flow data. The temperature data may comprise an indication of a temperature measured by a temperature sensor. The temperature data may comprise an indication of a plurality of temperatures measured by a plurality of temperature sensors. The coolant flow data may comprise an indication of a flow rate of a coolant measured by a flow rate sensor. The coolant flow data may comprise an indication of a plurality of flow rates measured by a plurality of flow rate sensors. The configuration data comprises at least one of an identifier, a type identifier, a sensor identifier, calibration data, voltage scaling data, current scaling data, voltage offset data, current offset data and power rating data. The modular motor drive may comprise the at least one secondary NELV drive module. The modular motor drive may comprise the motor. The ELV drive module may comprise a control processor configured to send the request to the NELV drive module over the ELV digital interconnect. The control processor may be configured to provide a warning indication and / or generate a change indication as the signal to cause the NELV drive module to cease or reduce operation when the telemetry data is outside normal operating parameters. The control processor may be configured to utilise at least one of the calibration data, the voltage scaling data, the current scaling data, the voltage offset data and the current offset data when generating signals to drive the ELV drive module. The control processor may be configured to utilise the sensor identifier when analysing the telemetry data. The control processor may be configured to provide a warning indication and / or generate a change indication as the signal to cause the NELV drive module to cease or reduce operation when the configuration data indicates incompatible modules. The data may comprise temperature data related to at least one temperature of a plurality of power devices and / or a motor and the control processor may be configured to utilise the temperature data to determine whether a variation in a rate of temperature change between the plurality of power devices exceeds a threshold amount and, if so, to at least one of provide a warning indication and to generate a change indication as the signal to cause the NELV drive module to cease or reduce operation. The data may comprise temperature data related to at least one temperature of a plurality of power devices and / or a motor and the control processor may be configured to utilise the temperature data to determine whether a variation in a temperature between a power device indicated as closest to a cooling device and a power device indicated as further from a cooling device fails to exceed a threshold amount and, if so, to at least one of provide a warning indication and to generate a change indication as the signal to cause the NELV drive module to cease or reduce operation. The data may comprise temperature data related to at least one temperature of a plurality of power devices and / or a motor and the control processor may be configured to utilise the temperature data to determine whether a variation in temperature between the plurality of power devices exceeds a threshold amount and, if so, to at least one of provide a warning indication and to generate a change indication as the signal to cause the NELV drive module to cease or reduce operation. The data may comprise temperature data related to at least one temperature of a plurality of power devices and / or a motor and the control processor may be configured to utilise the temperature data to determine whether a temperature of the motor falls outside of at least one of an upper and a lower threshold and, if so, to at least one of provide a warning indication and to generate a change indication as the signal to cause the NELV drive module to cease or reduce operation. The data may comprise a resistance value of at least one resistance temperature sensor and the control processor may be configured to utilise the resistance value to determine whether a resistance of the temperature sensor exceeds a threshold value and, if so, to at least one of provide a warning indication and to generate a change indication as the signal to cause the NELV drive module to cease or reduce operation. The data may comprise an indication of a lack of appropriate calibration data for the NELV drive module and / or the at least one secondary NELV drive module and the control processor may be configured to: utilise the data to determine whether appropriate calibration data is available to the control processor and, if so, to provide the calibration data to the at least one of the NELV drive module and the at least one secondary NELV drive module. The control processor may be configured to otherwise at least one of provide a warning indication and to generate a change indication as the signal to cause the at least one of the NELV drive module and / or the at least one secondary NELV drive module to cease or reduce operation. The data may comprise an indication of an identifier for at least one of the NELV drive module, the at least one secondary NELV drive module and / or the motor and the control processor may be configured to: utilise the data to determine whether the at least one of the NELV drive module, the at least one secondary NELV drive module and / or the motor are incompatible and, if so, at least one of provide a warning indication and to generate a stop indication as the signal to cause the at least one of the NELV drive module and the at least one secondary NELV drive module to cease or reduce operation. The data may comprise an indication of a fault for at least one of the NELV drive module, the at least one secondary NELV drive module and / or the motor and the control processor may be configured to: utilise the data to determine whether the at least one of the NELV drive module, the at least one secondary NELV drive module and / or the motor have a fault and, if so, at least one of provide a warning indication and to generate a change indication as the signal to cause the at least one of the NELV drive module and the at least one secondary NELV drive module to cease or reduce operation. The NELV drive module may comprises a gate drive module. The secondary NELV drive module may comprise a power module. The ELV drive module may comprise a control module. According to a second aspect, there is provided a method comprising: providing a modular motor drive, comprising a non-extra low voltage NELV drive module; transmitting data relating to the NELV drive module to an extra low voltage ELV drive module of the modular motor drive using an isolated digital communications device; processing the data relating to the NELV drive module; and generating a signal for transmission over the isolated digital communications device to control the NELV drive module. The data may comprise telemetry or operational data or parameters related to an operation of the NELV drive module. The method may comprise receiving the telemetry or operational data or parameters related to an operation of the NELV drive module. The method may comprise transmitting the telemetry or operational data or parameters over the ELV digital interconnect to the ELV drive module. The data may comprise telemetry data from at least one sensor on the NELV drive module. The method may comprise receiving the telemetry data from at least one sensor on the NELV drive module. The data may comprise configuration data related to a configuration of the NELV drive module. The method may comprise receiving the configuration data related to a configuration of the NELV drive module. The method may comprise transmitting the configuration data over the ELV digital interconnect to the ELV drive module. The data may comprise the configuration data from storage on the NELV drive module. The method may comprise receiving the configuration data from storage on the NELV drive module. The data may comprise telemetry data related to an operation of the least one secondary NELV drive module. The method may comprise receiving the telemetry data related to an operation of the least one secondary NELV drive module. The method may comprise transmitting the telemetry data to the ELV drive module. The data may comprise telemetry data from at least one sensor on the least one secondary NELV drive module. The method may comprise receiving the telemetry data from at least one sensor on the least one secondary NELV drive module. The data may comprise configuration data related to a configuration of the least one secondary NELV drive module. The method may comprise receiving the configuration data related to a configuration of the least one secondary NELV drive module. The method may comprise transmitting the configuration data to the ELV drive module. The data may comprise configuration data from storage on the least one secondary NELV drive module. The method may comprise receiving the configuration data from storage on the least one secondary NELV drive module. The method may comprise transmitting the data in response to a request received from the ELV drive module. The data may comprise telemetry data related to an operation of a motor. The method may comprise receiving the telemetry data related to an operation of the motor. The method may comprise transmitting the telemetry data to the ELV drive module. The data may comprise telemetry data from at least one sensor on the motor. The method may comprise receiving the telemetry data from at least one sensor on the motor. The data may comprise configuration data related to a configuration of the motor. The method may comprise receiving the configuration data related to a configuration of the motor. The method may comprise transmitting the configuration data to the ELV drive module. The data may comprise configuration data from storage on the motor. The method may comprise receiving the configuration data from storage on the motor. The method may comprise transmitting the data in response to a request received from the ELV drive module. The method may comprise transmitting the data in response to a request received from the ELV drive module over the ELV digital interconnect. The method may comprise requesting the data in response to a request received from the ELV drive module over the ELV digital interconnect. The method may comprise transmitting a warning indicator over the ELV digital interconnect when the telemetry data is outside normal operating parameters. The telemetry data may comprise at least one of temperature data and coolant flow data. The temperature data may comprise an indication of a temperature measured by a temperature sensor. The temperature data may comprise an indication of a plurality of temperatures measured by a plurality of temperature sensors. The coolant flow data may comprise an indication of a flow rate of a coolant measured by a flow rate sensor. The coolant flow data may comprise an indication of a plurality of flow rates measured by a plurality of flow rate sensors. The configuration data comprises at least one of an identifier, a type identifier, a sensor identifier, calibration data, voltage scaling data, current scaling data, voltage offset data, current offset data and power rating data. The method may comprise providing a warning indication and / or generate a change indication as the signal to cause the NELV drive module to cease or reduce operation when the telemetry data is outside normal operating parameters. The method may comprise utilising at least one of the calibration data, the voltage scaling data, the current scaling data, the voltage offset data and the current offset data when generating signals to drive the ELV drive module. The method may comprise utilising the sensor identifier when analysing the telemetry data. The method may comprise providing a warning indication and / or generate a change indication as the signal to cause the NELV drive module to cease or reduce operation when the configuration data indicates incompatible modules. The data may comprise temperature data related to at least one temperature of a plurality of power devices and / or a motor and the method may comprise utilising the temperature data to determine whether a variation in a rate of temperature change between the plurality of power devices exceeds a threshold amount and, if so, to at least one of provide a warning indication and to generate a change indication as the signal to cause the NELV drive module to cease or reduce operation. The data may comprise temperature data related to at least one temperature of a plurality of power devices and / or a motor and the method may comprise utilising the temperature data to determine whether a variation in a temperature between a power device indicated as closest to a cooling device and a power device indicated as further from a cooling device fails to exceed a threshold amount and, if so, to at least one of provide a warning indication and to generate a change indication as the signal to cause the NELV drive module to cease or reduce operation. The data may comprise temperature data related to at least one temperature of a plurality of power devices and / or a motor and the method may comprise utilising the temperature data to determine whether a variation in temperature between the plurality 11 of power devices exceeds a threshold amount and, if so, to at least one of provide a warning indication and to generate a change indication as the signal to cause the NELV drive module to cease or reduce operation. The data may comprise temperature data related to at least one temperature of a plurality of power devices and / or a motor and the method may comprise utilising the temperature data to determine whether a temperature of the motor falls outside of at least one of an upper and a lower threshold and, if so, to at least one of provide a warning indication and to generate a change indication as the signal to cause the NELV drive module to cease or reduce operation. The data may comprise a resistance value of at least one resistance temperature sensor and the method may comprise utilising the resistance value to determine whether a resistance of the temperature sensor exceeds a threshold value and, if so, to at least one of provide a warning indication and to generate a change indication as the signal to cause the NELV drive module to cease or reduce operation. The data may comprise an indication of a lack of appropriate calibration data for the NELV drive module and / or the at least one secondary NELV drive module and the method may comprise utilising the data to determine whether appropriate calibration data is available to the control processor and, if so, to provide the calibration data to the at least one of the NELV drive module and the at least one secondary NELV drive module. The method may comprise otherwise at least one of provide a warning indication and to generate a change indication as the signal to cause the at least one of the NELV drive module and / or the at least one secondary NELV drive module to cease or reduce operation. The data may comprise an indication of an identifier for at least one of the NELV drive module, the at least one secondary NELV drive module and / or the motor and the method may comprise utilising the data to determine whether the at least one of the NELV drive module, the at least one secondary NELV drive module and / or the motor are incompatible and, if so, at least one of provide a warning indication and to generate a stop indication as the signal to cause the at least one of the NELV drive module and the at least one secondary NELV drive module to cease or reduce operation. The data may comprise an indication of a fault for at least one of the NELV drive module, the at least one secondary NELV drive module and / or the motor and the method may comprise utilising the data to determine whether the at least one of the NELV drive module, the at least one secondary NELV drive module and / or the motor have a fault and, if so, at least one of provide a warning indication and to generate a change indication as the signal to cause the at least one of the NELV drive module and the at least one secondary NELV drive module to cease or reduce operation. The NELV drive module may comprises a gate drive module. The secondary NELV drive module may comprise a power module. The ELV drive module may comprise a control module. The method may comprise optional method features corresponding to the optional features of the first aspect. According to a third aspect, there is provided a computer program product operable, when executed on a computer, to cause the modular motor drive to perform the method of the second aspect. The computer program product may comprise optional features corresponding to the optional features of the first and / or second aspect. Further particular and preferred aspects are set out in the accompanying independent and dependent claims. Features of the dependent claims may be combined with features of the independent claims as appropriate, and in combinations other than those explicitly set out in the claims. Where an apparatus feature is described as being operable to provide a function, it will be appreciated that this includes an apparatus feature which provides that function or which is adapted or configured to provide that function. BRIEF DESCRIPTION OF THE DRAWINGS Embodiments of the present invention will now be described further, with reference to the accompanying drawings, in which: FIG. 1 illustrates a modular motor drive, according to one embodiment; and FIG. 2 illustrates a modular motor drive, according to one embodiment. DESCRIPTION OF THE EMBODIMENTS Before discussing the embodiments in any more detail, first an overview will be provided. Some embodiments provide an arrangement of a modular motor drive which separates an Extra Low Voltage (ELV) drive module from Non Extra Low Voltage (NELV) module(s) while allowing data such as configuration data and operational parameters or other telemetry data to be communicated between the ELV drive module and the NELV module(s). Such communication occurs over an electrically isolated ELV digital communication link. In some embodiments, data transmission between the other NELV module(s) and the ELV drive module is aggregated and also communicated over the (single) an electrically isolated ELV digital communication link. The provision of an electrically isolated ELV digital communication link helps to simplify electrical isolation between the ELV drive module and the NELV module(s) while still allowing different data to be transmitted conveniently between the ELV drive module and the NELV module(s). This allows the ELV drive module to detect and determine the particular configuration and operation of the NELV module(s) and to take steps to adjust operation by supplying control signals to the NELV module(s) and ensure the safety and / or efficient operation of the modular motor drive, particularly when the configuration of the modular motor drive is changed. Modular Motor Drive - 1st Embodiment FIG. 1 illustrates a modular motor drive 10, according to one embodiment. The modular motor drive 10 has a first drive module 20 and a second drive module 30. The first drive module 20 is a so-called Extra Low Voltage (ELV) drive module. ELV drive modules are considered to be electrically “safe” for direct contact by an operator. Examples of such ELV drive modules include Separated or Safety Extra Low Voltage (SELV), Protected Extra Low Voltage (PELV), Functional Extra Low Voltage (FELV), Reduced Low Voltage (RLV) modules, or the like. Such modules are typically defined by standards such as the International Electrotechnical Commission (IEC) 61800-5-1 with ELV, SELV, PELV, FELV, RLV falling within class A of IEC 61800. The second drive module 30 is a Non Extra Low Voltage (NELV) drive module. NELV drive modules are considered to be electrically “unsafe” for direct contact by an operator. Examples of such NELV drive modules include unprotected, live, hazardous or the like modules falling within classes B-D of IEC 61800. To enable the first drive module 20 to retain its ELV classification while connected to the second drive module 30 (which does not have an ELV classification), they are coupled by an ELV digital interconnect 40. The first drive module 20 has a control microprocessor 50 which has storage 60 for storing programs and data utilized by the control microprocessor 50. Typically, the first drive module 20 acts as a controller for other drive modules, providing appropriate control signals and / or configuration information typically in response to configuration information and / or telemetry or operational data provided by the other drive modules. The second drive module 30 has an isolated digital communications device 70. The isolated digital communications device 70 comprises a microprocessor 80 which is coupled with an electrical isolator 90 which, in turn, is coupled with a transceiver 100. The microprocessor 80 has storage 110 for storing programs and data utilized by the microprocessor 80. The electrical isolator 90 provides for NELV-ELV electrical isolation which meets the requirements for connecting the second drive module 30 to the first drive module 20 while ensuring that the first drive module 20 maintains its ELV status. Although the embodiment shown in FIG. 1 has the microprocessor 80 coupled in series with the electrical isolator 90 and then the transceiver 100, it will be appreciated that the series arrangement may be reversed and the microprocessor may instead be coupled in series with the transceiver 100 and then the electrical isolator 90. The electrical isolator 90 is typically a safely isolating transformer, as specified in the standards, for providing appropriate electrical isolation between the second drive module 30 and the first drive module 20. This arrangement enables the second drive module 30, which is potentially unsafe or hazardous, to be safely coupled with the first drive module 20, which is classified as safe for user contact and allows that safe classification to be maintained whilst allowing data and instructions to be transferred between the control microprocessor 50 and the microprocessor 80. The second drive module 30 has one or more sensors 120 that provide data related to measurements made by the sensors 120 to Analogue to Digital Converter (ADC) inputs and / or to a port provided by the microprocessor 80. The microprocessor 80 may access the storage 110 to obtain configuration information and / or calibration information related to the configuration and / or calibration of the second drive module 30 and / or its sensors 120. The microprocessor 80 may access the storage 110 to store and / or retrieve data related to the operation of the second drive module 30 and / or its sensors 120. The microprocessor 80 may provide and / or receive configuration information and / or calibration information related to the configuration and / or calibration of the second drive module 30 and / or its sensors 120 and / or operational or telemetry data related to the operation of the second drive module 30 and / or its sensors 120 over the ELV digital interconnect 40 with the control microprocessor 50 autonomously and / or in response to requests made by the control microprocessor 50. The microprocessor 80 may do likewise for other drive modules or motors (not shown) connected with the second drive module 30. In operation, the first drive module 20 couples with the second drive module 30 using the ELV digital interconnect 40. Typically, the control microprocessor 50 executes a program stored on the storage 60 and communicates with the microprocessor 80 over the ELV digital interconnect 40 to obtain information about the second drive module 30. For example, the control microprocessor 50 may request information about the second drive module 30 type, capabilities, serial number and the like (together with information about any other drive modules or motors coupled with the second drive module 30). That information may also include information about the type of any sensors 120, together with any calibration data. The microprocessor 80 responds (requesting the information from any other drive modules or motors coupled with the second drive module 30 as appropriate) and provides that information over the ELV digital interconnect 40. The control microprocessor 50 may determine from this information whether the second drive module 30 (and any other drive modules or motors coupled with the second drive module 30) is / are compatible and appropriate to be activated, driven or controlled by the first drive module 20. If not, then the second drive module 30 (and / or any other drive modules or motors coupled with the second drive module 30) may be instructed to remain in an inactive mode and an error or warning may be issued to an operator. Should the control microprocessor 50 determine that the second drive module 30 (and / or any other drive modules or motors coupled with the second drive module 30) is / are compatible, then the control microprocessor 50 may generate control signals used to control the second drive module 30 (and / or any other drive modules or motors coupled with the second drive module 30) based on the configuration information received from the second drive module 30. Data collected by the sensors 120 (and / or sensors on any other drive modules or motors coupled with the second drive module 30) may be conveyed by the microprocessor 80 to the control microprocessor 50. That information may be analysed by the control microprocessor 50 and any changes in the signals provided to the second drive module 30 may be generated and transmitted to the second drive module 30. The control microprocessor 50 may determine whether the data received from the sensors 120 (and / or sensors on any other drive modules or motors coupled with the second drive module 30) indicates that the operating conditions of the second drive module 30 (and / or any other drive modules or motors coupled with the second drive module 30) are out of range and appropriate ameliorative action such as further changes to the signals being transmitted to the second drive module 30 made, or any appropriate warnings provided to the operator. In some arrangements, the microprocessor 80 may determine when the parameters measured by the sensors 120 are out of range and an appropriate warning signal may be sent to the control microprocessor 50. Modular Motor Drive - 2nd Embodiment FIG. 2 illustrates a modular motor drive 1000, according to one embodiment which operates in a similar manner to the arrangement shown in FIG. 1 above. Typically, different multiple so-called ‘frame’ sizes of motor drive need to be manufactured for different motors and / or different applications. That is to say, different configurations of modular cards may be assembled together to provide a particular frame size motor drive. A particular build of a motor drive will have a known set of cards or boards (measurement card, gate driver card, etc.) which make up a particular frame size and a control card requires knowledge of whether each of the cards are, for example, frame 1 cards, frame 2 cards, etc. This can be recorded at manufacture and the combination of cards will be tested and known to work. If the cards are changed, then the control card may need to be aware of this, as it could be attached cards associated with a different frame size and be unaware of this. This potentially could lead to unexpected operation or damage of the drive and / or a risk to the user. Also, each frame size is likely to involve different power devices and motor configurations as well as different sensors for voltage, current, temperature, coolant flow, and the like. Those devices typically require the voltages and / or currents to be scaled to suit the different devices. The control card therefore typically requires knowledge of this scaling and typically has a control processor which is common to all frame sizes. The control card also typically needs to know what the true voltage and current is, so it can be displayed to the enduser. Temperature or other telemetry or operational parameter feedback from power or other devices in the motor drive is typically required. Typically, there can be 9 power modules in total on a 22kW frame 1 size drive. Each of these devices typically has a temperature sensor in, and a temperature measurement for the motor is also typically required. To route all of this temperature information back to the control card would require a large number of interconnects. In addition, the temperature sensors require isolation as they will only have basic isolation to the power devices (it is dangerous for the end-user if isolation is not provided). Analogue isolation is expensive and introduces offset and scaling errors. In existing arrangements, the control card could be moved between different motor drives of different frame sizes, potentially causing issues. It makes it difficult for traceability if the motor drive comes in for repairs, and it could potentially cause unexpected operation as the control card is paired with unexpected hardware. The control card will just assume the right hardware is connected. Also, the scaling values are usually recorded during manufacture and test, and then stored centrally on the control card. This means that the motor drive must always be a “set” and if there is a failure in the field of the control card, knowledge of the calibration data has to be obtained and written to the new control card. Furthermore, typically only one device’s temperature will be measured, and it is assumed that the others will be a similar temperature. Or only the heatsink will be measured. This will then give a limited set of information, and could mean missing a device failing, a fault in assembly or manufacture of a power device etc. Hence, the modular motor drive 1000 comprises a control card 1020 which is a class A ELV device in a similar manner to the first drive module 20 mentioned above. The control card 1020 has a control microprocessor 1050 and a storage 1060 for storing programs and data utilized by the control microprocessor 1050. Typically, the control card 1020 acts as a controller for other drive modules, providing appropriate control signals and / or configuration information typically in response to configuration information and / or telemetry or operational data provided by the other drive modules. The control card 1020 is coupled with a gate drive card 1030 which is a NELV class B-D device in a similar manner to the second drive module 30 mentioned above using an ELV digital interconnect 1040. The gate drive card 1030 provides signals to drive a motor 1400. In particular, the gate drive card 1030 controls a set of power devices 1055 which generate signals to drive the motor 1400. The gate drive card 1030 comprises an isolated digital communications device 1070 which is similar in configuration to the isolated digital communications device 70 mentioned above. In particular, the isolated digital communications device 1170 comprises a microprocessor 1080 coupled with a series arrangement of an isolator 1090 and a transceiver 1100 (although these may be reversed as mentioned above). The microprocessor 1080 is coupled with a storage device 1110 for storing programs and data utilized by the microprocessor 1080. The gate drive card 1030 has one or more thermistors 1120 that provide data related to the temperature of an associated power device to an Analogue to Digital Converter (ADC) input provided by the microprocessor 1080. In this example, temperature is measured, but it will be appreciated that other sensors may be provided which measure parameters other than temperature. The microprocessor 1080 may access the storage 1110 to obtain configuration information and / or calibration information related to the configuration and / or calibration of the gate drive card 1030 and / or its sensors 1120. The microprocessor 1080 may access the storage 1110 to store and / or retrieve data related to the operation of the gate drive card 1030 and / or its sensors 1120. The microprocessor 80 may provide and / or receive configuration information and / or calibration information related to the configuration and / or calibration of the gate drive card 1030 and / or its sensors 1120 and / or data related to the operation of the gate drive card 1030 and / or its sensors 1120 over the ELV digital interconnect 1040 with the control microprocessor 1050 autonomously and / or in response to requests made by the control microprocessor 1050. The microprocessor 1080 may do likewise for other cards 1200, 1300 or motor 1400 connected with the gate drive card 1030. The microprocessor 1080 couples using NELV interconnects 1510, 1520, 1530 with the motor 1400, the card 1200 and the card 1300, respectively. The microprocessor 1080 may also or instead couple with a motor thermistor and power devices via Analogue to Digital Converter ports. The motor 1400 has one or more sensors 1425 and storage 1410. The card 1200 has sensors 1220 and storage 1210. The card 1300 has one or more sensors 1320 and storage 1310. The storage 1410; 1210; 1310 may store configuration information and / or calibration information related to the configuration and / or calibration of the associated card 1400; 1200; 1300 and / or its sensors 1425; 1220; 1320. The microprocessor 1080 may access the storage 1410; 1210; 1310 to store and / or retrieve data related to the operation of the associated card 1400; 1200; 1300 and / or its sensors 1425; 1220; 1320. The microprocessor 1080 may provide and / or receive configuration information and / or calibration information related to the configuration and / or calibration of the associated card 1400; 1200; 1300 and / or its sensors 1425; 1220; 1320 and / or data related to the operation of the associated card 1400; 1200; 1300 and / or its sensors 1425; 1220; 1320 over the associated NELV interconnects 1510, 1520, 1530 with the microprocessor 1080 autonomously and / or in response to requests made by the microprocessor 1080. Hence, the control card 1020 contains the control microprocessor 1050 (be this a microcontroller, microprocessor or FPGA). A local microcontroller or FPGA is based locally on each of the separate card(s) that requires the sensors (temperatures or other operational parameters) to be read, and calibration data and serial numbers or configurations are stored in storage associated with that microcontroller. A communication protocol such as universal asynchronous receiver / transmitter (UART) or Controller Area Network protocol (CAN) is then used to communicate between the processors over the ELV digital interconnect 1040, this requires a total of two physical connections. This is also a digital connection, and thus is more noise immune than an analogue signal. By using a digital communication protocol isolating the signal becomes more straightforward than isolating an analogue signal. It also avoids the offset and scaling issues. There will also be fewer connections, as a processor can easily take 10+ analogue signals and have multiple digital inputs and outputs. The analogue signals (such as temperature sensors) can be sampled locally by the local processor, then transmitted digitally back to the control processor 1050 on the control card 1020. The calibration data for any current sensors or voltage sensors local to that particular card can be stored by the processor. Most processors have non-volatile memory that can be used for this purpose, rather than needing an additional component to provide the non-volatile memory. This means at the manufacturing / testing stage of the card or board, the calibration data can be stored. Then, when a card is connected to the control card 1020, the control processor 1050 can request the calibration information. This makes the control card 1020 agnostic to the card(s) or board(s) that is connected, making it easier to swap out the control card 1020 or other cards 1200; 1300 for a new one if that card fails. The non-volatile memory can also be used to store serial numbers and the particular card type (information on frame size or the like). This will then allow the control microcontroller 1050 to be aware if a card has been changed and flag this to the end-user, and also prevent operation with the incorrect card(s), if put into the wrong frame size. In operation, the control card 1020 couples with the gate drive card 1030 using the ELV digital interconnect 1040. In particular, the control microprocessor 1050 connects with the microprocessor 1080 placed on the gate drive card 1030. Isolation (reinforced insulation) is provided as the control card 1020 must be at SELV (Safe Electrical Low Voltage) and the temperature sensors 1120 and / or other sensors only have functional insulation from the power devices that are at high voltage. Typically, UART is used to communicate between the boards, requiring only two wires to connect the two. The modular motor drive 1000 is a 22kW drive. There are 9 temperatures to measure from the power devices using sensors 1120, and a temperature to measure from the motor 1400 using sensor 1425. Typically, the sensors are sampled by the microprocessor 1080 on the gate drive card 1030 once a second. The motor temperature sensor 1425 is also sampled once a second. In addition, information related to the gate drive card 1030 and / or the cards 1200, 1300 serial number, and what frame size it is for, is needed. Calibration data is also contained for the sensors 1120 and the ability to select what kind of motor temperature sensor 1425 is required. Similar information is required for the cards 1200, 1300. The serial number, frame size and any calibration data is stored in the flash memory of the gate drive card 1030 and / or the cards 1200, 1300. This information can be requested by the gate drive card 1030 using a MODBUS protocol layered onto the UART. This same MODBUS protocol can be used to set the type of motor temperature sensor used, and read the serial number / frame size of the gate drive card 1030 and / or the cards 1200, 1300. Typically, the control microprocessor 1050 executes a program stored on the storage 1060 and communicates with the microprocessor 1080 over the ELV digital interconnect 1040 to obtain information about the gate drive card 1030. For example, the control microprocessor 1050 may request information about the gate drive card 1030 frame type, capabilities, serial number and the like (together with information about any other drive modules or motors coupled with the gate drive card 1030). That information may also include information about the type of any sensors 1120; 1220; 1320; 1425, together with any calibration data. The microprocessor 1080 responds (requesting the information from any other drive modules or motors coupled with the gate drive card 1030 as appropriate) and provides that information over the ELV digital interconnect 1040. The control microprocessor 1050 may determine from this information whether the gate drive card 1030 (and any other drive modules or motors coupled with the gate drive card 1030) is / are compatible and appropriate to be activated, driven or controlled by the control card 1020. If not, then the gate drive card 1030 (and / or any other drive modules or motors coupled with the gate drive card 1030) may be instructed to remain in an inactive mode and an error or warning may be issued to an operator. Should the control microprocessor 1050 determine that the gate drive card 1030 (and / or any other drive modules or motors coupled with the gate drive card 1030) is / are compatible, then the control microprocessor 1050 may generate control signals used to control the gate drive card 1030 (and / or any other drive modules or motors coupled with the gate drive card 1030) based on the configuration information received from the gate drive card 1030. Data collected by the sensors 1120 (and / or sensors on any other drive modules or motors coupled with the gate drive card 1030) may be conveyed by the microprocessor 1080 to the control microprocessor 1050. That information may be analysed by the control microprocessor 1050 and any changes in the signals provided to the gate drive card 1030may be generated and transmitted to the gate drive card 1030. The control microprocessor 1050 may determine whether the data received from the sensors 1120 (and / or sensors on any other drive modules or motors coupled with the gate drive card 1030) indicates that the operating conditions of the gate drive card 1030 (and / or any other drive modules or motors coupled with the gate drive card 1030) are out of range and appropriate ameliorative action such as further changes to the signals being transmitted to the gate drive card 1030 made, or any appropriate warnings provided to the operator. In some arrangements, the microprocessor 1080 may determine when the parameters measured by the sensors 1120 are out of range and an appropriate warning signal may be sent to the control microprocessor 1050. In some embodiments, external ADC chips can be provided and communicated to via Inter-Integrated Circuit (I2C) Protocol or Serial Peripheral Interface (SPI). In some embodiments, on the power board, an Electrically Erasable Programmable Read-Only Memory (EEPROM) has been placed to capture the calibration data for the current sensors, voltage sensors and the serial number / frame size information. The EEPROM is read using i2c when the drive is first powered up, so no noise from the drive switching affects the reading. A microcontroller was not required for this. The additional temperature measurements could allow for local processing of the data and determining if there are any thermal issues within the drive. This takes the processing load off the control processor on the control card. This could be used to determine if the cooling fan has failed, or a device has not been seated properly with the heatsink. More temperature sensors could be added, such as one for the heatsink temperature or other components of concern, as additional ADC channels will be available. It could also be used to provide additional digital inputs or outputs if required for user use. On larger drives that might have separate gate driver boards for each bi-directional switch a bus structure could be used, so each gate driver has its own address and only a single connection to the control board is required. The embodiments set out above can be operated in a variety of different ways. For example, some embodiments provide for temperature-based diagnostics. This may be performed by a control processor on an ELV module and / or by a local processor on a NELV module (which can help to off-load processing from the control processor). The control processor typically then sends control signals to control the operation of the NELV module. Such control signals may cause the drive to cease operation or reduce its performance or operating parameters to prevent a complete stop. Should the temperature data indicate that the conditions that caused a fault have 22 passed, then the control signals may be reversed to enable the drive to resume normal operation. Local non-volatile memories can be used to store data specific to that module or board. This can then be sent directly to the control processor, or via the processor of the module having the ELV digital interconnect. Routing via the processor of the module having the ELV digital interconnect helps to reduce the number of connections on the ELV module, as routing directly from the module takes up pins (which are limited and takes up processing time reading multiple communications ports - it is better to have just one if you can). In one embodiment, during factory calibration, temperature signals received by the local processor and / or conveyed to the control processor may be analysed to detect a variation in a temperature rise of any power devices. This may typically be performed with any fan off and used to confirm that thermal paste is present and / or an effective connection to a heat sink. In particular, during factory calibration, when the drives are first assembled in the factory, a powered test is run to confirm that the assembled drive works correctly. It can also be used to confirm that the power devices have thermal paste present and have a good connection to the heatsink. In existing approaches, typically only a single temperature sensor is present on the heatsink itself, so it is very difficult to determine if any of the power module packages are not connected correctly. With a temperature readback of all of the power modules, it can be confirmed (given known operating conditions and loading of the devices, and their temperature rise) whether the devices are fitted correctly and the thermal paste is applied correctly. Should a temperature rise be detected in a device that is higher than the others by more than a threshold amount, then this may indicate that that device is not fitted to the heat sink correctly and / or that the thermal paste is not applied correctly. Likewise, should a device run hotter by more than a threshold amount than another device, then this could suggest an imminent failure of a power device. These calculations can be done locally to offload processing from the control processor and just faults / warnings reported back over the communication interface. Likewise, the calculations can be done by the control processor which may send faults / warnings control signals to control and potentially cease the operation of the power modules. One embodiment confirms the operation of the fan. Typically, the power devices are placed in a line or other distributed arrangement, with device 1 being closest to the fan and device 9 being furthest away. With no fan(s) running, the power devices will all heat-up / cool down at similar rates. When the fan(s) are running, the closest device (device 1) to the fan(s) will cool down faster or heat-up slower than those furthest from 23 the fan(s) (device 9). After X minutes, a delta or difference should appear between device(s) closest to fan and those furthest away. Should a closer device run hotter than a further device then this could suggest an imminent failure of a power device. Temperature signals received by the local processor and / or conveyed to the control processor may be analysed. The local processor typically analyses this delta and reports when the temperature data indicates that the fans are running. Likewise, the calculations can be done by the control processor which may send faults / warnings control signals to control and potentially cease the operation of the power modules. One embodiment detects motor temperature sensor disconnection. Typically, the temperature sensors used on the motor will be resistance based so, based on this, if the resistance detected exceeds a set level then it can be assumed that a motor temperature sensor is disconnected. The local processor typically analyses this resistance data and reports when the resistance data indicates that the motor temperature sensor is disconnected. For example, should the motor temperature sensor become disconnected it will typically be viewed as very high impedance, so it will give an “at-the-rails” reading which indicates that the motor is either very cold (below a minimum threshold) or very hot (above a maximum threshold) and these extreme (and typically rapidly changed) values are readily detectable as a fault. Likewise, the calculations can be done by the control processor which may send faults / warnings control signals to control and potentially cease the operation of the power modules and / or motor. In one embodiment, the temperature data indicates that the temperatures go up on the power devices because the fan is blocked or failed, and the control processor uses that information to go into a reduced operation or limp home mode (based on information from the gate card). Control signals are sent by the control processor which changes the switching to the gate driver board to reduce the current flowing through the power devices. For example, the current may be reduced to change the operation from a 22kW operation to a 10kW or less operation. This might be preferable to it attempting to run, overheating, stopping then attempting to start again once cooled down. Some embodiments provide configuration management through use of serial numbers and / or calibration data. In one embodiment, each module or board can electronically have their identifier or a serial number reported by the local processor to the control processor. The control processor can then identify if any boards are changed. The control processor can also check the type of the board, and only allow operation if it matches the correct version / type for that frame size / hardware version. In particular, each board has an electronically stored identifier or serial number. This can be stored on local non-volatile memory. This enables the control processor to determine if a board has changed. If an identifier is used then that identifier may encode type, configuration or version information. This enable this information to be extracted from the identifier itself, rather than needing to store a lookup of serial numbers against type, configuration or version information. For example, if drives are built in “frame” sizes then frame 1 may be 15kW to 22kW, frame 2 might be 30kW to 45kW, etc. From this identifiers may be encoded as Identifier “1015” for a 15kW frame 1, Identifier “1022” for a 22kW frame 1, Identifier “2045” for a 45kW frame 2, and so on. Compatibility information may indicate that identifiers “1xxx” are compatible with any frame 1 item no matter power level, identifiers “2xxx” are compatible with any frame 2 item no matter power level, and so on. It will be appreciated that other identifier encoding and compatibility information may be used. In a serial number is used, then a type number and version number could be stored. Alternatively, the serial number may indicate a type number and version number. The type number can then be used to ensure that boards cannot be mixed between frame sizes, and the version number allows the control processor to determine if the board(s) are compatible. It may be newer boards become incompatible with their older versions. Should the control processor determine that there are incompatible boards then the control processor may send faults / warnings control signals to control and potentially cease the operation of the power modules and / or motor. In one embodiment, the modules or boards (such as the measurement and power board) can be calibrated individually and hold calibration data locally. This then allows the boards to be added to a unit at final assembly, and no overall calibration of the full unit is required. If each board has an EEPROM or local processor with flash, then it can store calibration data specific to that board. This means that a final calibration stage is not needed when everything is assembled. Doing calibration when the unit is fully assembled can be challenging due to accessing sensors to apply calibrated test signals (especially the power board which will be underneath 3 other boards). This also means boards can be “mixed” rather than having to keep particular boards together. This helps with spares, as these can be stored in the own, rather than as a set. It also means that each drive unit does not need to be recalibrated every time a board is changed. Alternatively, calibration data for boards may be associated with a unique serial number and stored by storage associated with the control processor. That calibration data may be provided to the local processor in response to the control processor receiving the unique serial number. The local processor may utilise that calibration data to facilitate operation. In embodiment provides for local control. For example, with a clamp control circuit, the local processor can be used to do some control mechanisms locally, and report back to the control processor based on what occurs. In particular, a local processor may reside with non-volatile memory on a measurement board (in NELV). This can be used to store calibration data, but also do some local control functions. The control is improved when done locally (in NELV), as the response of control must be rapid as it must detect rapid voltage rises and apply a crow-bar circuit if the voltage gets too high. The local processor will report back to the control process any faults with the circuit, and if the crowbar circuit is active. Alternatively, providing the data can be transmitted quickly enough the calculations can be done by the control processor which may send faults / warnings control signals to control the operation of the power modules. A similar isolation and transmission can be used back to the control process on the control board, or can be done via the local processor on the gate driver board. Although illustrative embodiments of the invention have been disclosed in detail herein, with reference to the accompanying drawings, it is understood that the invention is not limited to the precise embodiment and that various changes and modifications can be effected therein by one skilled in the art without departing from the scope of the invention as defined by the appended claims and their equivalents. Reference Signs Modular Motor Drive 10; 1000 First Drive Module 20 Second Drive Module 30 ELV Digital Interconnect 40; 1040 Control Microprocessor 50; 1050 Storage 60; 1060 Isolated Digital Communications Device 70; 1070 Microprocessor 80; 1080 Electrical Isolator 90; 1090 Transceiver 100; 1100 Storage 110; 1110;1210; 1310; 1410 Sensors 120; 1120; 1220; 1320; 1425 Control Card 1020 Gate Drive Card 1030 Power Devices 1055 Thermistors 1120; 1420 Cards 1200, 1300 Motor 1400 NELV Interconnects 1510, 1520, 1530
Claims
1. A modular motor drive, comprising:an extra low voltage ELV drive module; anda non-extra low voltage NELV drive module having an isolated digital communications device configured to transmit data relating to said NELV drive module to said extra low voltage ELV drive module, said ELV drive module being configured to process said data relating to said NELV drive module and to generate a signal for transmission over said isolated digital communications device to control said NELV drive module.
2. The modular motor drive of claim 1, wherein said isolated digital communications device comprises a processing device coupled with a series pair of devices comprising an ELV isolator device and a digital communications device.
3. The modular motor drive of claim 1 or 2, wherein said NELV drive module comprises an ELV digital interconnect coupled with said isolated digital communications device and couplable with said ELV drive module to convey said data.
4. The modular motor drive of claim 3, wherein said ELV digital interconnect comprises at least one of:a twisted pair; and a bus.
5. The modular motor drive of claim 3 or 4, wherein said data comprises at least one of:telemetry data related to an operation of said NELV drive module;telemetry data from at least one sensor on said NELV drive module;configuration data related to a configuration of said NELV drive module; and configuration data from storage on said NELV drive module.
6. The modular motor drive of claim 5, wherein said storage comprises nonvolatile memory associated with said processing device.
7. The modular motor drive of any preceding claim, wherein said NELV drive module comprises a NELV interconnect coupled with said isolated digital communications device and couplable with at least one secondary NELV drive module.
8. The modular motor drive of claim 7, wherein said data comprises at least one of:telemetry data related to an operation of said least one secondary NELV drive module;telemetry data from at least one sensor on said least one secondary NELV drive module;configuration data related to a configuration of said least one secondary NELV drive module; andconfiguration data from storage on said least one secondary NELV drive module.
9. The modular motor drive of any one of claims 2 to 9, wherein said processing device is configured to transmit said data in response to a request received from said ELV drive module.
10. The modular motor drive of any preceding claim, wherein said NELV drive module comprises a NELV interconnect coupled with said isolated digital communications device and couplable with a motor.
11. The modular motor drive of claim 10, wherein said data comprises at least one of:telemetry data related to an operation of said motor;telemetry data from at least one sensor on said motor;configuration data related to a configuration of said motor; and configuration data from storage on said motor.
12. The modular motor drive of any one of claims 3 to 11, wherein said processing device is configured to transmit said data in response to at least one of:a request received from said ELV drive module; anda request received from said ELV drive module over said ELV digital interconnect.
13. The modular motor drive of any one of claims 3 to 12, wherein said processing device is configured to at least one of:request said data in response to a request received from said ELV drive module over said ELV digital interconnect; andtransmit a warning indicator over said ELV digital interconnect when said telemetry data is outside normal operating parameters.
14. The modular motor drive of claim 13, wherein said telemetry data comprises at least one of temperature data and coolant flow data.
15. The modular motor drive of claim 14, wherein said temperature data comprises at least one of:an indication of a temperature measured by a temperature sensor; and an indication of a plurality of temperatures measured by a plurality of temperature sensors.
16. The modular motor drive of claim 14 or 15, wherein said coolant flow data comprises at least one of:an indication of a flow rate of a coolant measured by a flow rate sensor; and an indication of a plurality of flow rates measured by a plurality of flow rate sensors.
17. The modular motor drive of any one of claims 8 to 16, wherein said configuration data comprises at least one of an identifier, a type identifier, a sensor identifier, calibration data, voltage scaling data, current scaling data, voltage offset data, current offset data and power rating data.
18. The modular motor drive of any one of claims 7 to 17, comprising at least one of:said secondary NELV drive module; and said motor.
19. The modular motor drive of any one of claims 3 to 17, wherein said ELV drive module comprises a control processor configured to send said request to said NELV drive module over said ELV digital interconnect.
20. The modular motor drive of claim 19, wherein said control processor is configured to at least one of:provide at least one of a warning indication and generate a change indication as said signal to cause said NELV drive module to cease or reduce operation when said telemetry data is outside normal operating parameters;utilise said sensor identifier when analysing said telemetry data; and provide at least one of a warning indication and generate a change indication as said signal to cause said NELV drive module to cease or reduce operation when said configuration data indicates incompatible modules.
21. The modular motor drive of any preceding claim, wherein said data comprises temperature data related to at least one temperature of at least one of a plurality of power devices and a motor and said control processor is configured to at least one of: utilise said temperature data to determine whether a variation in a rate of temperature change between said plurality of power devices exceeds a threshold amount and, if so, to at least one of provide a warning indication and to generate a change indication as said signal to cause said NELV drive module to cease or reduce operation;utilise said temperature data to determine whether a variation in a temperature between a power device indicated as closest to a cooling device and a power device indicated as further from a cooling device fails to exceed a threshold amount and, if so, to at least one of provide a warning indication and to generate a change indication as said signal to cause said NELV drive module to cease or reduce operation;utilise said temperature data to determine whether a variation in temperature between said plurality of power devices exceeds a threshold amount and, if so, to at least one of provide a warning indication and to generate a change indication as said signal to cause said NELV drive module to cease or reduce operation; andutilise said temperature data to determine whether a temperature of said motor falls outside of at least one of an upper and a lower threshold and, if so, to at least one of provide a warning indication and to generate a change indication as said signal to cause said NELV drive module to cease or reduce operation.
22. The modular motor drive of any preceding claim, wherein said data comprises a resistance value of at least one resistance temperature sensor and said control processor is configured to utilise said resistance value to determine whether a resistance of said temperature sensor exceeds a threshold value and, if so, to at least one of provide a warning indication and to generate a change indication as said signal to cause said NELV drive module to cease or reduce operation23. The modular motor drive of any preceding claim, wherein said data comprises an indication of a lack of appropriate calibration data for at least one of said NELV drive module and said at least one secondary NELV drive module and said control processor 31is configured to: utilise said data to determine whether appropriate calibration data is available to said control processor and, if so, to provide said calibration data to said at least one of said NELV drive module and said at least one secondary NELV drive module, and otherwise at least one of provide a warning indication and to generate a change indication as said signal to cause said at least one of said NELV drive module and said at least one secondary NELV drive module to cease or reduce operation.
24. The modular motor drive of any preceding claim, wherein said data comprises an indication of an identifier for at least one of said NELV drive module, said at least one secondary NELV drive module and said motor and said control processor is configured to: utilise said data to determine whether said at least one of said NELV drive module, said at least one secondary NELV drive module and said motor are incompatible and, if so, at least one of provide a warning indication and to generate a stop indication as said signal to cause said at least one of said NELV drive module and said at least one secondary NELV drive module to cease or reduce operation.
25. The modular motor drive of any preceding claim, wherein said data comprises an indication of a fault for at least one of said NELV drive module, said at least one secondary NELV drive module and said motor and said control processor is configured to: utilise said data to determine whether said at least one of said NELV drive module, said at least one secondary NELV drive module and said motor have a fault and, if so, at least one of provide a warning indication and to generate a change indication as said signal to cause said at least one of said NELV drive module and said at least one secondary NELV drive module to cease or reduce operation.IntellectualPropertyOfficeApplication GB2418049.9Search report under Section 17 of the Patents Act 1977Date search completed: 29 May 2025Claims searched: 1-25International classificationSubclass and subgroup Valid from G05B15 / 02 01 / 01 / 2006 H02K11 / 30 01 / 01 / 2016Field of searchWorldwide search of patent documents classified in the following areas of the IPC: H02K, G05BDatabases used in the preparation of this search report:SEARCH-PATENTDocuments considered to be relevantPatent literatureCategory Relevant claims Document of relevance A - EP 3739742 A1 (INTEA ENG TECNOLOGIE ELETTRONICHE APPLICATE S R L), See whole document.Intellectual Property Office is an operating name of the Patent Office www.gov.uk / ipoA - US 2022 / 0231505 A1 (GERHARDT et al.), Whole document relevant. A - US 2023 / 0198412 A1 (PEARCE et al.), Whole document relevant. Non-patent literature Category Relevant claims Document of relevanceCategoriesLetter or DescriptionsymbolX Document indicating lack of novelty or inventive step.Y Document indicating lack of inventive step, if combined with anotherdocument of the same category.& Member of the same patent family. A Document indicating technological background. P Document published on or after the priority date but before the fling date of the present application. E Earlier application published on or after the filing date of the present application.
Citation Information
Patent Citations
ViewUS2023/0198412A1onEspacenetopensinnewtab
ViewUS2022/0231505A1onEspacenetopensinnewtab
ViewEP3739742A1onEspacenetopensinnewtab
