Flow control assembly having localized non-volatile memory - Patents.com

Localized non-volatile memory in HPLC systems addresses the inefficiencies of reinitialization and component wear by storing data for predictive maintenance, enhancing operational efficiency and component longevity.

JP7584220B2Active Publication Date: 2024-11-15IDEX HEALTH & SCIENCE LLC
View PDF 5 Cites 0 Cited by

Patent Information

Application Number
JP2019560645
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Priority Date
2017-05-08
Filing Date
2018-04-23
Publication Date
2024-11-15
Estimated Expiration
2038-04-23

AI Technical Summary

Technical Problem

High pressure liquid chromatography (HPLC) systems face challenges in managing component wear and maintenance due to the need for reinitialization after power down and lack of portable data storage for valve positions, leading to inefficiencies and potential component failure prediction.

Method used

Implementing localized non-volatile memory, such as FRAM, in flow control components to store data related to component usage, wear, and position, allowing for predictive failure analysis and reducing the need for reinitialization.

Benefits of technology

Enables efficient operation by maintaining valve position data independently of the host system, improving maintenance efficiency, and predicting component failure, thus extending the life of HPLC components and reducing downtime.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007584220000001
    Figure 0007584220000001
  • Figure 0007584220000002
    Figure 0007584220000002
  • Figure 0007584220000003
    Figure 0007584220000003
Patent Text Reader

Abstract

An apparatus for controlling fluid flow, and in particular, fluid flow through a microfluidic multiport control valve assembly in a high-pressure liquid chromatography (HPLC) unit, is described. The flow control device has a localized data repository for storing cumulative wear indicators of components of the apparatus. The stored information travels with the apparatus, enabling more reliable prediction of failure of the apparatus components.
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] This application claims the benefit of and priority to U.S. Provisional Patent Application No. 62 / 502,853, filed May 8, 2017, the contents of which are incorporated herein by reference in their entirety.

[0002] Federal funding Not applicable

[0003] joint research agreement Not applicable

[0004] The present invention relates generally to fluid flow control assemblies, and more particularly to a microfluidic multiport control valve assembly in a High Pressure Liquid Chromatography (HPLC) unit having a localized data repository for storing identification data corresponding to the valve control assembly. In some embodiments, the stored data corresponds to the last known valve position, thereby eliminating the need to reinitialize the valve after every power outage. The localized data repository travels with the valve regardless of the environment in which the valve is used. Furthermore, in some embodiments, the identification data stored in the localized data repository may include data corresponding to cumulative usage and wear characteristics of components of the microfluidic multiport control valve assembly for predictive failure. The present invention further relates to a method of evaluating a flow control device, and more particularly to a method of evaluating a microfluidic multiport control valve assembly in a High Performance Liquid Chromatography (HPLC) unit having a localized cumulative wear indicator for predictive failure of components of the microfluidic multiport control valve assembly. [Background technology]

[0005] Conventionally, high pressure liquid chromatography (HPLC) units use multiple pumps and valves to control the flow of sample fluids through the HPLC unit. A host computer system is typically electrically coupled to the HPLC unit and to various components within the HPLC unit with microprocessor controlled pumps and valves. The host system can control the components within the HPLC and stores information related to the control of the components. Various components within the HPLC unit exhibit wear characteristics at various rates. For example, an HPLC pump may require repair or replacement at a different pace than an HPLC control valve operating within the same HPLC unit. Additionally, in some cases, it is desirable to repair or replace only a portion of the pump or valve rather than replacing the entire component.

[0006] While the host computer may record in memory data relating to repair and replacement events associated with consecutively ordered components, in some cases various components from one HPLC unit are swapped out and placed into another unit. Unless the two host computers are dithered, the second host computer will not have a history of the replaced components and must therefore reinitialize all replaced components. Also, the current flow control components must have tags or labels attached to the exterior portions of the components, but the indicia contained on the labels are limited and fixed. Furthermore, if the second host computer does not have a usage history for these components, it may be that the user of the HPLC unit is unaware that the HPLC unit may have one or more components that may be near the end of their life or may require maintenance, for example.

[0007] It would therefore be desirable to provide a flow control component that can store in a non-volatile memory updated information and data related to the flow control component, such as may be suitable for use in an HPLC unit, such as, for example and without limitation, component information related to the repair status of the component, the geometrical arrangement of the subcomponents of the component, the geometrical arrangement of the component within its environment, the serial number of the component, the part number of the subcomponent, the manufacturer of the component, the date of manufacture, the configuration of the component, the life / usage, the operating specifications, material compatibility, values ​​related to the movement of the component, values ​​related to the accumulated amount of component motion, the last known position of the component, the optimum position of the component, component errors, repair information for the component, maintenance requirements for the component, or information related to the environment to which the component is exposed. [Prior art documents] [Patent documents]

[0008] [Patent Document 1] U.S. Patent No. 8,201,185(B2) [Patent Document 2] U.S. Patent No. 7,201,185(B2) Summary of the Invention [Means for solving the problem]

[0009] An embodiment according to an aspect of the present invention includes a flow control component having one or more localized data repositories for storing a wide variety of information related to the use of the component. The data repositories preferably include, but are not limited to, FRAM® type non-volatile memory. Although FRAM is described herein as a preferred localized data repository memory, those skilled in the art will recognize that other machine readable and writable memories may be utilized as the localized data repository, including non-volatile memories such as MRAM, NAND, or EEPROM.

[0010] In certain embodiments, the flow control component may be a direct drive flow control valve with the motor, drive train, and fluid path assembly housed as a single unit. A printed circuit board (PCB) and motor drive are installed in the direct drive valve. The fluid path assembly of the valve may have a cover or stator and a diaphragm or rotor with ports formed therein. The diaphragm may be rotated by the motor, thereby controlling the desired flow through the valve. In some cases, the fluid path assembly may be repaired or replaced by replacing only the rotor and stator components. A record of the rebuild of the fluid path assembly may be stored in the data repository. Additionally, the amount of rotation of the diaphragm or rotor may be determined and a record of the amount of rotation may be stored in the data repository. Additionally, the cumulative or total amount of rotor motion and motor motion may also be recorded in the data repository. When the fluid path assembly is rebuilt, the cumulative amount of rotation of each rotor may be stored separately in the data repository. In this manner, information is retained corresponding to each rebuild throughout the life of the entire "single unit." Data relating to the total movement or rotation of the drive train and motor may also be retained and stored as a separate value from the rotation of the rotor.

[0011] In certain embodiments, the flow control components may include a flow control valve assembly having a motor, an actuator, and a modular pod. The valve or diaphragm is housed in the modular pod. One or more PCBs may be mounted on the valve assembly. For example, PCBs may be mounted on both the actuator and the motor. A drive controller, microprocessor, and resident non-volatile memory may be mounted on the PCB. A fluid path assembly may be housed in the pod, and the fluid path assembly may be "serviced" by quickly replacing the entire pod or by replacing one or more components in the POD. The ease of simply replacing the entire POD reduces down time of the HPLC system. Data related to servicing the POD may be stored in a non-volatile memory fixed to the POD itself. Alternatively, the POD may be removed and rebuilt in a manner similar to rebuilding direct drive rotor and stator components. Once rebuilt, information related to the rebuild is stored in the POD's memory, making the POD ready for a new quick replacement when another POD requires service. A data repository may be maintained both on the POD and on the actuator or motor. A data repository on the POD may be utilized to maintain data corresponding to valve count or rotation, rebuild #, and other data specific to the POD. The data repository may be, for example, an FRAM. A pcb attached to the actuator may have position sensors and drivers for the valves. A PCB may support a separate FRAM, IC, and microprocessor responsible for managing the FRAM on the POD.

[0012] One skilled in the art will recognize that one or more localized data repositories are utilized to ensure that data associated with the valve is not lost when untethering the entire valve assembly (fluid valve, actuator, and motor), when untethering the actuator and POD (valve, actuator, and motor in the POD), or when untethering the POD (valve in the POD) from the actuator and host system. When the data repository is secured to the POD (e.g., a PCB supporting the FRAM and IC on the POD [valve]), power will be provided to and controlled by the IC via the actuator's PCB and IC. The PCB on the actuator will further have its own FRAM, and will further have a microprocessor to manage both the actuator and the FRAM and IC on the POD separately. Although FRAM is described herein as a preferred localized data repository memory attached to the POD, one skilled in the art will recognize that other machine readable and writable memories may be utilized as the localized data repository, including non-volatile memories such as MRAM, NAND, or EEPROM.

[0013] In a particular embodiment of the present invention, the position of the valve within the valve housing or within the POD is determined and stored in a localized memory. Position sensors of known suitable configuration may be utilized to determine the position and amount of rotation. Incremental encoders may be useful or absolute position sensing may be useful to determine the position and rotation of the valve. Current encoder solutions may be categorized into two main types: incremental and absolute. Incremental encoders require the host system to initialize the incremental movement device to determine a starting position when powered on. After initialization, the movement of each of the devices is monitored for relative position changes. Absolute position encoders do not require an initialization sequence since the position is always known. Both encoder types may be expensive depending on the precision and accuracy required.

[0014] While not intending to be limiting of the types of suitable valve position sensors, by way of example, an encoder will be described in the context of determining the position of a valve that defines port-to-port connectivity. The use of an encoder can reduce the form factor and cost of each valve unit, as incremental encoders can be compact and less costly than absolute position sensors. However, the encoder requires an initialization process each time the valve is actuated. Actuating the valve requires valve motion and shortens the useful life of the valve. It is believed that allowing the valve to be used without requiring reinitialization will extend the life of the valve.

[0015] Although the description in this document refers to an encoder, the functionality of the valve is not determined by the type of encoder (incremental vs. absolute concept). Additionally, while it may be desirable to optimize the encoder transition to align with the port location in a range of evenly spaced port configurations (e.g., 60 windows spaced equally so that the window transition always lies at the port location), it is not necessary to align the windows to the port locations. That said, storing the preferred port locations in memory can improve repeatability and accuracy of the motion, since the locations between the windows are maintained using electrical signals that "balance" between the physical windows or detents.

[0016] Combining an incremental encoder with non-volatile memory can provide a low cost, small form factor solution that matches the advantages of absolute position sensors while offering the added benefit of storing information related to the valve, such as port configuration, manufacturing data, life / frequency of use, operating specifications, material compatibility, etc. Specific information related to valve use can travel with the valve, rather than being stored and managed on the host computer. By moving the valve and / or reconfiguring the valve components, the host system can recognize valve use information with minimal data management effort. After the first initialization, the valve stores all motions in memory. Whenever the valve is powered up, the last known position can be determined from memory and the valve is actuated without initialization.

[0017] Even if nominally positioned based on encoder feedback, the valve ports may not be optimally aligned due to mechanical variations within the assembly. The optimal positioning of the port locations may be stored in memory as a look-up table. The actual encoder feedback may be interpreted via the look-up table and corrections may be made to the valve position. The look-up table may be constructed using a variety of methods. One method involves measuring back pressure with the goal of finding the most "open" port alignment.

[0018] Additionally, the ability to remember the last known valve position improves efficiency of operation and reduces the need to spend useful motion initializing the valve multiple times. Once the valve position is known, the valve position stored in memory will not change unless the valve is actuated. During valve initialization, the starting point of the valve's initial state can be designed as the home position. If a system failure occurs during valve motion, the "successful motion" flag will not be set and the controller system will know that the "successful motion" flag is not valid. The valve can actively tell the host system that it has not completed its motion but the valve position is still known. Although the control system can query the host system for where it should move, there is no need for the control system to initialize the valve to the home position because the control system is constantly recording its movements. Even if the valve motion is not accomplished, the valve position is known both before and after the system failure.

[0019] The incremental encoder of the present invention can employ any number of incremental counting stations, or windows, appropriate for a given application, with a 60 window incremental encoder providing broad applicability to a variety of common valve variations including 6-port, 8-port, 10-port, and 12-port valves.

[0020] In certain embodiments of the invention having actuators with removable PODs, memory may be located in multiple separate locations, but connected to allow communication and sharing of information. An actuator may have a record of all PODs used throughout the life of the actuator, along with POD replacement dates and total number of POD replacements. A POD may maintain its own associated information and may be separated from a particular actuator without losing its unique data.

[0021] With regard to the functionality of the encoder, when the valve is initialized, the last known valve position can be stored in non-volatile memory. When the valve is actuated, a value indicating a successful movement can be written to the on-board memory, meaning the host system can determine the positioning of the valve. When the valve is initialized, the most recent position is saved to local memory, and the controller can determine the last known position of the valve from the memory. In the event that the valve cannot be moved, the system will know the position of the valve. This is because a value related to the position is always written to memory when the valve is moved. For example, whenever a pulse or control signal is sent to a stepper motor, the pulse count, or other increment such as an encoder transition, can be written to memory before a motion request. Thus, an unsuccessful movement means that the last increment stored in memory indicates the last physical position of the valve.

[0022] An added benefit of local storage of valve movement information is that it maintains an updated actuation count for the valve that can be used to predict valve failure when the valve is approaching the end of its useful life, regardless of where and when the valve is in use. Because the valve information can be read from the valve memory, the host system can ensure compatibility with a given HPLC process, and the valve can be considered "portable" between various processes and systems. In addition to being integrated with the valve as a complete unit, memory can be located in multiple locations on the valve assembly (e.g., actuator vs. replacement POD) and managed and maintained as a separate entity.

[0023] With regard to encoder functionality, when the valve is initialized, the last known valve position can be stored in non-volatile memory. When the valve is actuated, a value indicating successful movement can be written to on-board memory so the host system can determine the valve positioning or know if reinitialization is required. Interpretation and execution of commands specific to other valve configurations are possible, for example, different types or configurations of physical encoders, various drive system ratios, and step counts.

[0024] The valve electronics that support the flow control components can be integrated into the valve and appropriately sized. For example, a direct drive valve can have the memory, processor, motor drive, and encoder sensor integrated into a single PCB and mounted at the bottom of the valve motor, or the memory, processor, and encoder sensor can be mounted at the rear of the motor and electrically coupled to an external motor drive. Alternatively, the actuator and POD can have separate FRAM (memory) dedicated to tracking their respective individual life data. Various information can be entered into the memory unit during assembly and testing of the valve, including information related to the date of manufacture, component serial numbers, component and subcomponent part numbers, valve port configuration, operating conditions (e.g., maximum temperature, maximum pressure, chemical compatibility, valve fluid path materials, etc.), maximum number of expected motions, last known position of the valve, or zero motion count. During use of the valve, additional information may be collected and stored in a localized data repository; these additional information may include successful movement flags, last known position, accumulated number of motor and valve motions or total rotational travel distance; and a value for the maximum number of motions before valve maintenance or service.

[0025] The localized data repository can preferably utilize a local memory unit such as FRAM, since this type of non-volatile memory has a high endurance that allows (almost) unlimited read / write operations, a simple form of data management, and eliminates the need for externally supplied power to store data "indefinitely". Furthermore, data corresponding to the following events can be easily stored: serial number, part number, manufacturer, manufacturing date, drive system ratio, encoder type, accumulated shaft motion, last known position of the valve, optimal position of port location, motor motion errors, repair / replacement information, or application specific information, as stored in the valve memory.

[0026] In a specific embodiment, the flow control component has data information to identify expected maintenance events and projected life. The flow control component has a processor, a position sensor, FRAM, and a motor controller. The system uses the position sensor (encoder counts) to track the total motion of the valve. The encoder counts and torque can also be used to calculate the total work. Additionally, motion errors can be recorded and compared to predict valve failure.

[0027] The data stored may include separate tracking of total motion, number of rebuilds, rebuild dates, and paired serial number history. The translation or interpretation of the various possibilities of the motor and encoder by the host computer (processor, encoder, FRAM, motor controller) allows the valve to be integrated with a wide variety of host computers with software specific to one type of drive or encoder system. Although the host system may store information related to motion, the valve "state" is not portable because the most recent valve information is stored in a database on the host computer, which cannot be portable. Advantages of the present invention include low cost, new efficiencies in (portable) data management, and the introduction of a portable history record of valve usage. Additional advantages include minimization of valve motion by avoiding repeated initialization of valve position as is currently required with valves equipped with incremental encoders. Multiple FRAM ICs may be used on a single valve to separately track the history of the actuator and any replacement fluid path components (PODs). The life of the actuator can be significantly longer than the replaceable fluid path subassemblies of the valve (PODs). For example, improved tracking can be achieved by recording the usage history of the actuator, such as a list of the POD serial numbers that have been installed on the actuator throughout its life.

[0028] The present invention represents an improvement over prior systems at least because the valve's on-board memory can be bidirectional, thus providing both read and write capabilities in a portable memory configuration. Furthermore, rather than simply reporting maximum expected life, valve configuration, etc., the system of the present invention can store information related to current valve usage, which can be compared to the maximum expected life of the valve, thereby eliminating the need for the instrument controller to store and track details of the population of valves that will be installed on the controller system throughout the life of the controller system. In other words, data management is simplified through the present invention with data portability.

[0029] In a particular embodiment, the motor driver chip detects when the motor fails to take a step, indicating that the torque has exceeded its design limits. The present invention further detects when the motor occasionally misses a step, or when the motor is unable to move at all, indicating a more serious motion problem. Thus, the controller can attempt to free a stuck motor by increasing the drive current up to a determined maximum limit.

[0030] The number of failed steps, whether the motor fault was resolved by increasing the motor current, and whether the motor can return to normal operation at normal current can all be kept in local memory. Shaft motion can be detected using a magnetic detector (on-axis or off-axis), an optical detector using multiple windows to determine movement. The encoder count is correlated to degrees of rotation. After each motion, the memory will be updated by incrementing the rotations over the lifespan by the last motion, and by incrementing the total movement count by one. In this way, a cumulative total of total rotations or intermediate totals (which can be correlated to angles) and the number of individual motions are saved. A 60 degree move counts as 1, a 120 degree move (or any other angle change) also counts as 1, as long as each is a continuous motion. In addition, the number of failed steps can be recorded (the motor drive commands a step but detects that the shaft was not moving). This can be considered a "soft error" that can be quickly corrected by driving the motor until the target position is reached. Additionally, failure to reach the desired position may also be logged and saved. These errors are "hard errors" and require notification to the host system.

[0031] Another example of this "lifetime partitioning" is when rotors and stators are tested to some degree of total number of motions. One rotor / stator fixture combination may sustain 30k of motions at a specified maximum pressure, while another may sustain 60K of motions. An actuator and motor (usually together) may be required to sustain 800k of motions, but this is an excerpt from a particular product requirement; these limits may vary with application or design.

[0032] Maximum limits, life limits, maintenance requirements, and other pre-defined limits are set based on reliability testing. For example, through testing it may be determined that the POD will exhibit greater wear than the actuator. Thus, the POD is replaced at a different interval than the actuator or motor. With direct drive valves, the rotor and stator are replaced every X number of motions. The drive train and motor are serviced at different intervals, e.g., every y and z number of motions, respectively. The drive train of a direct drive valve can be easily separated from the motor and quickly replaced. Motor life may exceed 5 million motions and require only a minimal amount of maintenance.

[0033] The HPLC valve of the present invention actively communicates valve life and anticipated maintenance requirements to the HPLC unit or units based on continuous monitoring of motion and torque feedback at the valve component level. The HPLC of the present invention actively updates valve information at the valve level, making the valve portable and independent of the host system. Portability allows the valve to be untethered from the host system and used elsewhere without loss of identification information, life history, and initialized position of the valve fluid path configuration.

[0034] An embodiment according to an aspect of the present invention includes a microfluidic multiport control valve assembly of a high pressure liquid chromatography (HPLC) unit having a localized repository for stored indications of cumulative wear moving with the valve assembly for predictive failure of components of the microfluidic multiport control valve assembly. The valve assembly includes a multiport valve, a data storage repository, an actuator assembly, a position sensing member, and a computational controller. The multiport control valve includes a valve housing that encloses the multiport control valve. The data storage repository is secured to the valve housing. The actuator assembly is coupled to the multiport control valve, the actuator assembly including an actuator that actuates the multiport control valve. The position sensing member is coupled to both the multiport control valve and an actuator of the actuator assembly, where the position sensing member generates signals corresponding to positions and movements of the actuator of the multiport control valve and the actuator assembly. The computational controller is electrically coupled to the actuator assembly, the position sensing member, and the data storage repository. Data related to the signals corresponding to positions and movements of the actuator of the multiport control valve and the actuator assembly is stored in the data storage repository.

[0035] An embodiment according to an aspect of the present invention may further include a data storage repository having a non-volatile memory for storing data. Furthermore, the non-volatile memory may be FRAM. Also, the position sensing member may be in the form of an encoder housed within the valve housing. The valve housing may be a modular pod or may be integrated into the actuator assembly. Data corresponding to the amount of rotation of the multiport control valve is stored in the non-volatile memory of the data storage repository. Alternatively, data corresponding to the amount of rotation of the multiport control valve is stored in the non-volatile memory resident in the computational controller. Alternatively, data corresponding to the amount of rotation of the multiport control valve may be stored in both the non-volatile memory of the data storage repository and the non-volatile memory resident in the computational controller. The stored data may correspond to a wear characteristic indicator selected from the group consisting of cumulative rotation of the valve, cumulative rotation of the actuator, and failed actuator activation. The stored data may further correspond to valve rebuild status, valve position, serial number, part number, manufacturer, manufacture date, drive system ratio, encoder type, accumulated shaft motion, last known position of the valve, optimum position of the port location, motor motion errors, repair information, maintenance requirements, or the type of fluid used in the valve.

[0036] An embodiment according to an aspect of the present invention includes a flow control device having a localized memory for fault prediction. The flow control device includes a flow control component, a data repository, a position sensing member, and a computational controller. The data storage repository is mechanically secured to the flow control component. The position sensing member is coupled to the flow control component, where the position sensing member generates a signal corresponding to a position and movement of the flow control component. The computational controller is electrically coupled to the flow control element and the data storage repository. Data relating to the signals corresponding to the position and movement of the flow control component is stored in the data storage repository.

[0037] The data storage repository of the flow controller of the present invention includes a non-volatile memory, which may be, for example, a non-volatile FRAM memory. Data corresponding to the amount of motion of the flow controller is stored in the non-volatile memory of the data storage repository and in the inherent non-volatile memory of the computational controller. In addition, unique valve identification data may be stored in the data storage repository, where the identification data may correspond to a repair condition of the device, a location of a component within the device, a serial number, a part number, a manufacturer, a date of manufacture, an accumulated amount of component motion, a last known location of a component, an optimum location of a component, a component error, repair information, a maintenance request, or a type of environment in which the flow controller is used.

[0038] An embodiment according to an aspect of the invention may further include a method of evaluating a microfluidic multiport control valve assembly of a high performance liquid chromatography (HPLC) unit having a localized cumulative wear indicator for predictive failure of a component of the assembly, the method including initializing a microfluidic multiport control valve assembly coupled to a high pressure liquid chromatography (HPLC) unit, where movement of the multiport control valve assembly is performed by an actuator assembly, controlling movement of the valve assembly and the actuator assembly, acquiring position data corresponding to a position of the multiport control valve, acquiring movement data corresponding to the movement of the multiport control valve and the actuator assembly, determining an accumulated value corresponding to a total cumulative movement of the multiport control valve and the actuator assembly, storing the position data, the movement data, and the accumulated value in a localized data storage repository fixed to the valve assembly for movement with the valve assembly, and comparing the accumulated value to a predefined limit value.

[0039] The method according to an aspect of the invention may further include storing data corresponding to an amount of rotation of the multi-port control valve. The localized data storage repository may include a non-volatile memory. Additionally, the step of storing the movement data may include storing data corresponding to an amount of rotation of the actuator assembly. The method may further include storing actuator data corresponding to an actuation of the failed actuator. Additionally, the method may include storing identification data corresponding to a rebuild status of the valve, a valve position, a valve serial number, a part number, a manufacturer, a manufacturing date, a drive system ratio, an encoder type, a last known position of the valve, an optimum position of the valve port location, a motor motion error, repair information, a maintenance request, or a type of fluid used with the valve.

[0040] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments of the present invention and, together with the detailed description, serve to further explain the invention. The embodiments shown herein are presently preferred. It should be understood, however, that the invention is not limited to the precise arrangements and instrumentalities shown. For a more complete understanding of the nature and advantages of the present invention, reference should be made to the detailed description in conjunction with the accompanying drawings.

[0041] In the various figures, which are not necessarily drawn to scale, like reference numbers indicate substantially similar elements throughout the figures. [Brief description of the drawings]

[0042] [Figure 1] FIG. 1 is a front perspective view of a microfluidic microport direct drive control valve assembly according to the present invention. [Diagram 2] FIG. 1 is a rear perspective view of a microfluidic microport direct drive control valve according to the present invention. [Diagram 3] FIG. 1 is a front perspective view of a microfluidic microport modular control valve assembly according to the present invention. [Figure 4]4 is a partial cross-sectional side view of a microfluidic microport modular control valve assembly of the type shown in FIG. [Diagram 5] FIG. 1 is a partial cross-sectional perspective view of a portion of a microfluidic microport modular control valve assembly showing a localized data storage repository secured to a modular pod of the assembly in accordance with the present invention. [Figure 6] FIG. 2 is a partial exploded perspective view of a microfluidic microport modular control valve assembly according to the present invention showing the modular valve pod separated from the actuator. [Figure 7] FIG. 2 is a partially exploded perspective view of a microfluidic microport modular control valve assembly according to the present invention showing the modular valve pod separated from the actuator and the PCB cover attached to the actuator assembly removed. [Figure 8] FIG. 1 is a partial exploded perspective view of a microfluidic microport modular control valve assembly according to the present invention, showing the modular valve pod separated from the actuator, a localized data storage repository separated from the modular pod, and the PCB separated from the actuator assembly. [Figure 9] FIG. 1 is a rear perspective view of a modular valve pod according to the present invention shown with a localized data storage repository secured to a valve housing of the modular valve pod. [Figure 10] FIG. 2 is a schematic block diagram showing the electrical coupling of a host computer to the controller of an HPLC unit and to the subcomponents of the unit, in accordance with the present invention. [Figure 11] FIG. 13 illustrates an example of a portion of a circuit diagram of an on-board non-volatile memory unit coupled to a controller of a flow control component that is coupled to a host computer. [Figure 12]1 is a flow diagram illustrating control of a replaceable flow control component with localized data storage to enable predictive failure of the component independent of the host system. [Figure 13] 4 is a flowchart describing an example operation of an incremental encoder of the present invention in conjunction with an incremental motion controller for a valve. [Figure 14] 4 is a flowchart describing an example operation of an incremental encoder of the present invention in conjunction with an incremental motion controller for a valve. [Figure 15] 1 is a flow chart describing an exemplary control of an incremental motor of the present invention in relation to incremental motion of a valve. [Figure 16] 1 is a flow chart describing an example operation of an incremental encoder of the present invention coupled to a host computer in association with an incremental motion controller of a valve. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0043] The following description provides details of various embodiments of the present invention, and one or more examples of the various embodiments are described below. Each of these embodiments is provided as an explanation of the present invention and is not intended to limit the present invention. Moreover, those skilled in the art will recognize that various modifications and variations can be made within the present invention without departing from the scope or spirit of the present invention. For example, those skilled in the art will recognize that features illustrated or described as part of one embodiment can be used in another embodiment to produce yet another embodiment. Thus, the present invention is further intended to cover such modifications and variations that are within the scope of the appended claims and their equivalents.

[0044] The flow control component 10 of the present invention generally comprises a valve assembly 14, an actuator assembly 16, and a motor 18. Although the flow control component 10 is shown as a microfluidic control valve assembly, those skilled in the art will recognize that the flow control component can comprise a variety of other valves and pumps in suitable configurations. The direct drive control valve assembly and the modular pod control valve assembly will be described in more detail in conjunction with the description of the figures.

[0045] 1 and 2, the direct drive valve assembly of the present invention is shown. The direct drive valve assembly 20 is mainly composed of a valve assembly 22 and an actuator assembly 24. The valve assembly has a valve housing 34 and a rotor housed within the valve housing 34. The actuator assembly 24 has an actuator housing 36 having a stepper motor and a drive assembly that transfers rotational motion from the motor to the rotor element within the housing. The drive assembly couples the motor to the valve assembly 22. The drive assembly can have a valve shaft and a planetary gear system. Alternatively, the drive system can have a valve shaft that is directly engaged to the motor without the use of intermediate gears. In this configuration, the reduction in motor torque due to the absence of a gear system can be compensated for by applying a motor with a larger torque. For example, the Model EZ670-000-4 Rheodyne Titan EZ valve manufactured by IDEX Health & Science combines a 42mm tin can stepper motor with an injection-molded planetary gear system to achieve a maximum force of 0.79 Nm (7 in-lb).

[0046] The valve housing 34 is generally cylindrical in shape and defines a central passageway therethrough axially extending from the distal mounting end to the port end thereof. The rotor element may be mechanically coupled to the actuator assembly via a shaft adapter that is rotatably engaged to the drive valve shaft, thereby enabling rotation of the rotor element. The valve shaft may be keyed such that any torque and rotation of the valve shaft about its longitudinal axis is transmitted to the shaft adapter and ultimately to the rotor element. Various other components and details of acceptable embodiments of the valves, position sensors, actuators, and motors are further described in U.S. Pat. No. 8,201,185 (B2), the disclosure of which is incorporated herein by reference in its entirety.

[0047] The direct drive valve 20 of the present invention further includes a PCB 26 with a corresponding local non-volatile FRAM memory 28 secured to the valve housing 34. In addition, a motor controller 38, electrical connections 46, integrated circuitry, and a local non-volatile FRAM memory 44 are coupled to a motor PCB 40 that is coupled to an end of the actuator assembly housing 36. Control of the direct drive valve 20 is described in more detail below.

[0048] 3-9, a modular microfluidic microport controlled valve assembly 60 of the present invention is shown. Generally, the multi-position microfluidic valve system includes an actuator assembly 66 coupled to a drive motor 64 at one end of the actuator assembly and removably receiving a valve pod 68 at the other end. The actuator assembly includes a housing and a drive assembly rotatably disposed within the housing for rotational displacement of a drive shaft about its drive axis. One end of the drive shaft is configured to be coupled to the drive motor 64 for selectively rotating the drive shaft about the drive axis. A multi-position fluid valve pod 68 is removably mounted to the actuator assembly and has a corresponding valve shaft configured for rotational movement about its valve rotation axis between a plurality of distinct fluid delivery positions. The valve pod further includes a quick connect coupling device 70 configured to selectively removably mount the pod 68 relative to the actuator 66, thereby enabling selective placement of the valve device in a discrete one of the plurality of distinct fluid delivery positions.

[0049] Thus, a microfluidic valve system is provided that allows one or more multi-position valves to be removably installed on a single actuator assembly, with each of the multi-position valves functioning as a differently reconfigured liquid end system as a whole. Unlike other valve systems, a six-position microfluidic valve system may be replaced with an eight-position microfluidic valve system or even a fifteen-position microfluidic valve system without modifying the structure of the actuator assembly. As will be described in more detail below, once a selected valve pod 68 is aligned and installed on the actuator assembly 66, and once a valve device has been identified, the valve system may be operated to control two or more types of multi-position microfluidic valves. Furthermore, in the event that a valve device requires repair and / or replacement, the valve may be easily removed for repair or replacement without requiring removal of the entire valve system affixed within the analytical instrument. As a result, the microfluidic valve system is highly versatile and, in addition, significantly less costly due in part to the reduced number of overall components.

[0050] An actuator assembly 66 is shown comprising a housing having a rectangular shaped proximal portion mounted to the drive motor 64 and a cylindrical shaped distal barrel portion removably mounted to the valve pod 68. The housing is provided by a shell structure preferably constructed from a relatively stiff composite material designed to have high strength. An inner wall of the housing defines a central through chamber extending axially through the housing from the proximal portion to the distal barrel portion. An annular bearing structure extends radially inward from the inner wall near the center of the through chamber. The bearing structure has an inner annular bearing wall forming a central passageway and a first bearing race portion distal to the bearing structure. As best seen in FIGS. 4 and 5, the annular first bearing race portion is disposed about the drive shaft and is generally semi-donut shaped. A plurality of ball bearings are disposed within the first bearing race portion and cooperate with the annular bearing wall to provide pivotable support for the drive assembly 26 about the drive shaft.

[0051] The drive assembly has a drive shaft and a gear carrier platform disposed at a proximal end of the drive shaft. The drive shaft is essentially an elongated splined shaft having a plurality of splines extending radially outward from its shaft axis. The gear carrier platform, on the other hand, is generally disk-shaped and is affixed to the drive shaft in such a manner that the carrier platform and the drive shaft are substantially coaxial along the drive axis and function together as a single unit. When the drive assembly is assembled within the actuator housing, the carrier platform is coupled to a gear train assembly, which mates with a drive motor that drives the drive shaft.

[0052] In accordance with the present invention, the valve system includes a position sensor assembly 72 for determining the precise rotatable switching position of the installed valve. By precisely switching the rotatable switching position, the valve device may be precisely actuated and the amount of rotation may be determined and stored in a local data repository memory. Thus, regardless of which valve pod 68 is installed in the actuator assembly 66, once the pod is initially initialized, the position of the valve may be precisely controlled and positioned without the need for reinitialization.

[0053] In a particular embodiment of the invention, the sensor assembly 72 includes one or more encoder wheels mounted on a rotating encoder spool that cooperate with a corresponding fixed optical sensor to determine the absolute rotational position and orientation of the encoder wheel relative to the drive shaft. By using a combination of an optical sensor and two encoder wheels designed to cooperate with each other, multi-position porting scenarios (of the mated valve pod 68) can be determined with absolute position feedback.

[0054] Each encoder wheel includes a set of inner diameter windows and a set of outer diameter notches to allow an optical signal to be transmitted therethrough. A pair of adjacent sensors mounted on the sensor PCB board 76 straddles each rotating wheel in a geometric arrangement to determine if a notch or window is sensed. The encoder wheels work with the optical sensors to absolutely position the valve at discrete positions. By using the encoders, incremental positioning of the valve is achieved. Thus, the valve device can range from having two distinct incremental positions to having fifteen or more discrete positions for its precise control and operation.

[0055] To strategically position the encoder wheel around the outer diameter of the distal barrel section of the encoder spool, the barrel section has a slot configured to receive a corresponding tooth portion extending radially inward from the inner wall of the wheel. These axially spaced encoder wheels can be mounted on the distal barrel section of the spool only in a discrete geometry to ensure proper installation alignment. By aligning and placing a selected valve device relative to the actuator assembly through the coupling device, the positioning of the valve device can be precisely controlled via a control unit (not shown) located between the sensor assembly and the stepper drive motor. In essence, this configuration allows for precise geometry and positioning of the drive shaft via the encoder wheel. Thus, by first determining which multi-position valve pod 68 is properly aligned and seated within the actuator housing, the control unit can be programmed and operated to correspond to that detected valve, so that precise operation of any valve can be achieved.

[0056] As described above, the optical sensor is located on a PCB that is mounted to the actuator assembly. A coupling device has a coupling member that is strategically oriented and affixed to the end of the valve shaft of the valve device for rotation about the valve rotation axis. A board receiving slot in a side wall of the actuator housing provides an access port therethrough into the through chamber. This port allows sensor access for up to two encoders when the drive assembly is operatively mounted relative to the housing. Thus, when the encoder spool / drive assembly is assembled, the actuator PCB can be mounted into the board receiving slot in a manner that allows the sensors to straddle the edges of the corresponding encoder wheels, as mentioned. Various other components and details of acceptable embodiments of the POD, position sensor, actuator, and motor are further described in U.S. Pat. No. 7,201,185 (B2), the disclosure of which is incorporated herein in its entirety by reference.

[0057] The modular microfluidic microport-controlled valve assembly 60 of the present invention further includes electrical conduits 78 for coupling the valve pod 68, actuator 66, and motor 64 to an external system. Additionally, a localized data repository in the form of FRAM memory 82 is contained within a housing 84 and coupled to the pod 68. Electrical leads 80 extend from the actuator PCB and electrically interconnect the local memory 82 to the actuator and motor controller 86.

[0058] Referring to FIG. 10, a microfluidic microport controlled valve assembly 100 is shown diagrammatically with an HPLC unit 104 and an external host computer 110. The valve assembly includes a valve 114 with its own localized memory 116 mounted in a valve housing, an actuator 118 with its memory 120 mounted in an actuator housing, and a motor 122 with a processor 124 coupled to a drive controller and motor. The valve memory 116, actuator memory 120, and controller 124 are all electrically coupled to the host computer 110. The HPLC may have an internal controller 106 that acts as an intermediary between the host computer 110 and the valve memory 116, actuator memory 120, and controller 124. The control and use of the valve assembly will be further described in conjunction with the description of FIGS. 11-16.

[0059] 11 shows a portion of a circuit diagram of an on-board non-volatile memory unit 130 coupled to a flow control component controller 132 that is coupled to a host computer 138. The controller is coupled to a motor driver 134 and a position sensor 136, thereby providing valve and motor motion control and motion analysis. Data or values ​​related to motor motion and valve motion are stored in the non-volatile memory and may also be communicated to the host computer 138 via a system controller 140.

[0060] A typical use of a flow control component or more specifically a microfluidic microport controlled valve assembly is shown in FIG. 12. For example, the first time the valve is used in an HPLC, the valve assembly must be initialized (160). Initialization of the valve assembly includes determining the valve port position (162) and storing the valve position in a local or resident memory (164). The valve controller may further perform a calibration sequence to determine an optimal position for the valve, which is further stored in the local memory (166). Once the valve is initialized, it may be used to control the flow of fluids in the system. The valve may receive a control signal that controls the movement or actuation of the valve (168). A position sensor coupled to the valve and to the controller detects the movement of the valve and communicates a signal corresponding to the detected movement to the controller. The signal is then processed and the controller may store a value characterizing the valve movement in the local memory (170). The position sensor may further be used to communicate a signal corresponding to the detected movement of an actuator (drive shaft) coupled to a motor to the controller. The signals are then processed and the controller may store values ​​characterizing the detection and movement of the actuator 172 in a local memory (172). Alternatively, the motor driver may be utilized to determine whether a command sent to the motor causes the motor to move. The controller and mode driver may further be utilized to detect one or more motion errors (174). The controller may then determine accumulated values ​​associated with the valve movement, the motor movement, and the motor errors (176). Values ​​associated with the accumulated values ​​are stored in a local memory (178). The control further analyzes and compares the accumulated values ​​against predetermined limit values ​​(180). Values ​​associated with the predetermined limit values ​​are also stored in the local memory and may be adjusted or modified by a user. If any of the accumulated values ​​exceed the predetermined limit values, a corresponding action is initiated. For example, the controller may send a signal to a host system indicating that one or more of the valve components require repair or replacement.Additionally, the results of the comparison of the accumulated value to a predetermined limit value may be further utilized to predict possible failure of the component 182. If no failure is predicted, the valve continues to receive a control signal 186. If failure is predicted, the necessary component is repaired or replaced 184 and the valve is returned to service so that the valve continues to receive a control signal from the controller 188.

[0061] FIG. 13 illustrates a process or routine utilized by the controller and motor driver in actuating the valve to a new position (200). Initially, the controller sets a successful motion flag to false (202) and initiates valve movement by sending a motion input to the motor (204). Signals from the position sensor are then evaluated to determine the valve movement. The signals may be evaluated in real time to control stepwise valve motion (206). The controller analyzes the position sensor signals to determine whether the motion was successfully completed (208). If the motion is successfully completed (210), the controller sets a successful motion flag to true (214) and updates the valve position in memory (216). A successfully completed motion may be determined during a step of the entire motion sequence, i.e., the condition may be checked after each pulse of a multi-pulse motion that constitutes the port-to-port "total motion." The controller further updates in memory (218) data or values ​​related to the cumulative motion or total distance traveled corresponding to the valve and motor. The controller then indicates (220) that the valve motion is complete. If the controller determines (212) that the motion is not completed successfully, the controller sets (222) the restored data state for the valve and stores (224) in memory that these controls have a successful motion flag false. The controller further does not update (226) the valve position and the signal from the position sensor is analyzed to determine (228) the approximate position of the valve. The valve is then initialized to an unknown state (230). However, the last known position is known and accessible from memory because the positions for each individual step level or for the encoder count level are stored in memory. The valve position may not be at the home position and the valve position may be between port positions, but the absolute position of the valve is known because the last position prior to the attempted movement is stored in memory.

[0062] FIG. 14 illustrates the analysis and control of motor motion. The motor drive receives motion input (240) and the controller calculates the amount of motor movement. The amount of motor movement may be characterized as steps, as well as the number of steps and the step rate (242), and both the number of steps and the step rate may be stored in local memory. The signal from the position sensor may be analyzed and compared to a correction table stored in local memory (244). The motor drive then generates phase currents for the motor motion (246) and the signal from the position sensor is monitored to determine the amount of movement (248). The controller then analyzes the signals and determines whether the motion is permitted (250). If the motion is not permitted (254), the motion data, motion error, and error type are stored in local memory (256), and the controller and motor drive can generate corrected phase currents for the motor. If the motion is permitted (252), the controller determines whether the valve motion is complete (258). If the motion is not complete (260), the motor drive generates phase current and the motor motion is repeated (loop 260). If the motion is complete (262), values ​​corresponding to the amount of motion and the final position of the valve are recorded in local memory (264) and the controller indicates that the motion is complete (266).

[0063] FIG. 15 shows a controller and motor process sequence for monitoring and predicting valve faults. When the motor driver sends a signal to the actuator to initiate valve motion (300), the controller compares the calculated torque from the motor driver feedback to a predefined torque limit stored in local memory (302). The controller then determines if the predefined torque limit has been exceeded (304). If the limit has been exceeded (306), the controller generates a signal indicating that maintenance is required (308) to check for position error (312) and that maintenance continues (310). If the controller determines that the torque limit has not been exceeded (314), the controller continues to check for position error 312 (312). The controller then determines if the position error is at a warning level (316). If the warning level is reached (318), the information is stored in local memory and the controller sends a signal conveying the warning information (320). The controller then continues to analyze (322) the data to determine if the cumulative motion exceeds a predetermined limit (324 and 328). If the warning level has not been reached (326), the controller proceeds to analyze the data to determine if the cumulative motion exceeds a predetermined limit (324 and 328). If the cumulative motion exceeds a preset limit (330), the controller generates a signal which may be sent to a host computer or otherwise communicated to a user (332) and the controller proceeds (334), thereby completing the monitoring mode (336). If the cumulative motion does not exceed a preset limit (338), the information is recorded in local memory and the controller completes the monitoring mode (336).

[0064] FIG. 16 illustrates an alternative motor motion analysis and control. A motor drive receives motion input from a host system (400). A controller interprets the host command and sends the command to the position sensor and motor (402). The controller then calculates the amount of motor movement. The amount of motor movement may be characterized as steps, as well as the number of steps and the step rate (404), and both the number of steps and the step rate may be stored in local memory. A signal from the position sensor may be analyzed and compared to a correction table stored in local memory (406). The motor drive then generates phase currents for the motor motion (408), and the signal from the position sensor is monitored to determine the amount of movement (410). The signal from the position sensor is transformed, and data related to the transformation is sent to the host system (412). The controller then analyzes the signal and determines whether the motion is permitted (416). If the motor is not permitted (418), the motion data, motion error, and error type are stored in local memory (420) so that the controller and motor drive can generate corrected phase currents for the motor. If the motion is permitted (422), the controller determines whether the valve motion is complete (426). If the motion is not complete (428), the motor drive generates phase currents and the motor motion is repeated (loop 428). If the motion is complete, values ​​corresponding to the amount of motion and the final position of the valve are recorded in local memory (430) and the controller indicates that the motion is complete (432).

[0065] These and various other aspects and features of the invention are described in an illustrative and not limiting manner. The invention has been described in detail herein for the purposes of complying with the patent laws and for the purposes of providing those skilled in the art with the necessary information to apply the novel principles and to construct and use the specialized components necessary. It is to be understood, however, that the invention may be practiced in specific alternative configurations and that various modifications, both as to configuration and as to the sequence of operation, may be accomplished without departing from the scope of the invention. Moreover, in the appended claims, transitional phrases such as "comprising" and "including" are used in a non-limiting sense because there may be elements in addition to those recited. Other examples will be apparent to those skilled in the art upon reading this document.

Claims

1. A host computer including a memory unit for digitally storing valve information, a motor controller, and a processor is connected via a computational control device, a localized data storage repository that travels with the microfluidic multiport control valve assembly for predicting failures of components of the valve assembly; 1. A microfluidic multiport control valve assembly for a high pressure liquid chromatography (HPLC) unit, the valve assembly comprising: a multiport control valve surrounded by a valve housing, the localized data storage repository being secured to the valve housing; an actuator assembly coupled to the multiport control valve, the actuator assembly having an actuator that actuates the multiport control valve; a position sensor for generating signals related to the position and movement of the multiport control valve and to the movement of the actuator. the actuator assembly, the position sensor, and the localized data storage repository are communicatively coupled to a computing controller; A microfluidic multiport control valve assembly, wherein an accumulated value, which is a total accumulated movement amount determined from signals related to the movement of the multiport control valve and the actuator by the position sensor, is stored in the localized data storage repository as an indicator of cumulative wear, and the computational control device is adapted to convert the data to be compatible with the host computer.

2. The control valve assembly of claim 1 , wherein the data storage repository comprises a non-volatile memory.

3. The control valve assembly of claim 1 , wherein the data storage repository comprises a non-volatile FRAM memory.

4. The control valve assembly of claim 1 , wherein the position sensor is in the form of an encoder.

5. The control valve assembly of claim 1 , wherein the valve housing is a modular pod.

6. The control valve assembly of claim 1 , wherein data corresponding to an amount of rotation of the multiport control valve is stored in a non-volatile memory of the localized data storage repository.

7. 2. The control valve assembly of claim 1, wherein the stored data may correspond to a valve rebuild status, a valve position, a serial number, a part number, a manufacturer, a manufacturing date, a drive system ratio, an encoder type, an accumulated amount of shaft motion, a last known position of the valve, an optimum position of the port location, an error in motor motion, repair information, a maintenance request, or a type of fluid used in the valve.

8. A host computer including a memory unit for digitally storing valve information, a motor controller, and a processor is connected via a computational control device, a localized data storage repository that travels with the microfluidic multiport control valve assembly for predicting failures of components of the valve assembly; 16. A method for evaluating a microfluidic multiport control valve assembly of a high pressure liquid chromatography (HPLC) unit, the method comprising: initializing the microfluidic multiport control valve assembly removably coupled to a high pressure liquid chromatography (HPLC) unit, wherein movement of a multiport control valve of the multiport control valve assembly is performed by an actuator assembly; controlling movement of the multiport control valve and the actuator assembly; obtaining position data corresponding to a position of the multiport control valve from a position sensor coupled to the multiport control valve and to the computational and controller; obtaining movement data from the position sensor corresponding to movement of the multiport control valve and the actuator assembly; determining an accumulation value that is a total cumulative movement of the multiport control valve and the actuator assembly; storing said location data, said movement data, and said accumulated value as an indicator of cumulative wear in a localized data storage repository fixed to said valve assembly for movement therewith; determining whether the accumulation value exceeds a predetermined limit value; converting the location data, the movement data, and the accumulated values ​​from the localized data storage repository for compatibility with the host computer; A method comprising:

9. The method of claim 8 , wherein the localized data storage repository comprises non-volatile memory.

10. 9. The method of claim 8, further comprising storing identification data corresponding to a rebuild status of the valve, the valve position, a valve serial number, a part number, a manufacturer, a manufacturing date, a drive system ratio, an encoder type, a last known position of the valve, an optimum position of the valve port location, an error in motor motion, repair information, a maintenance request, or a type of fluid used with the valve.

Citation Information

Patent Citations

  • Multi-position microfluidic valve system with detachable encoder assembly, microfluidic valve actuator assembly and encoder assembly

    JP2013500452A

  • Flow passage switching valve and liquid chromatography device using the same

    JP2015152033A

  • Apparatus and method for detecting valve mechanical effectiveness in a chemical composition analyzer

    US20070185659A1

  • Coupled drive multi-position fluid valve apparatus and method

    US7201185B2

  • COM object and managed code object interoperability

    US8201185B2