The field of this invention relates to a single line communication path between a driver and slave device, for example a solenoid actuated fluid control valve manifold assembly and more particularly to a multi-station circuit board for use with the manifold assembly having a single communication line.
Fluid control systems for controlling flow of hydraulic or pneumatic fluid have been used in automated manufacturing equipment, production lines and numerous industrial applications. Many of these fluid control systems take the form of a valve manifold that has a series of manifold valve blocks assembled together. Some manifold blocks house a single solenoid that has a spring return for moving the valve when the solenoid is deactuated or on the other hand, some manifold blocks house a double solenoid valve that has a first solenoid when actuated that moves the valve to the on position and a second solenoid when actuated that moves the valve to the off position.
Each valve manifold block houses a circuit board which has circuitry printed thereon to allow actuation of the valve unit or units mounted to the valve manifold block. The circuit board also has circuits printed thereon to carry voltage to other circuit boards for the other valves mounted on other valve manifold blocks.
What is needed is a single line system between a driver and slave devices that provides information therebetween that can be used for smart slave devices or other slave devices. In particular, it is desired that a circuit board that can pass through a valve manifold block and has a serial or single communication line for each respective valve unit and/or supplementary control, programming or parameterization. With the advent of smart slave devices, for example solenoid valves, proportional devices or pressure switches, it is desirable to transfer data between a driver and the slave device.
In accordance with one aspect of the invention, driver device drives a valve manifold block for a fluid valve manifold that has a plurality of fluid pathways and ports therein controlled by a slave device in the form of a valve unit operably mounted thereto. A passage passes through the valve manifold from a first side to a second side of the valve manifold block. A printed circuit board that is received in the passage has a first edge in proximity to the first side with a plurality of first electrical connectors and a second edge in proximity to the second side with a plurality of second mating electrical connectors to connect to respective first electrical connectors in another printed circuit board in another valve manifold block.
The circuit board has a set of conductive valve control lines connected to and extending between a respective set of first electrical connections and a set of respective second mating electrical connectors. The circuit board also has at least one conductive valve control line extending from a respective first electrical connection to a third connector on the circuit board operably leading to one voltage side of a valve unit. A conductive common line is connected to the third connector operably connected to an opposite voltage side of the valve unit and also connected to a respective first electrical connector and a respective second mating electrical connector. A serial communication line has a respective first electrical connector at the first edge and a respective second mating electrical connector at the second edge for connection to a respective serial communication line in another valve manifold block for communicating information relating to the valve unit.
In one embodiment, the serial communication line extends to and is connected to a low voltage side of the valve unit. Optionally, the circuit board serves a second valve unit on the valve manifold block. The serial communication line extends to and is connected to a low voltage side of the second valve unit.
In one embodiment, the serial communication line is used as a detection circuit line to detect if the valve unit mounted to the valve manifold block uses a single solenoid valve unit or double solenoid valve unit. The circuit board serves a second valve unit on the valve manifold block. The set of conductive valve lines extend from a set of first electrical connectors at the first edge and extend to and shifted to a staggered relative position at a set of second mating electrical connectors. A leg line is preferably connected from the third connector to the detection circuit line through a diode to only allow current to pass in the direction from the leg line to the detection circuit line.
According to another aspect of the invention, fluid control system has a fluid valve manifold with a plurality of valve manifold blocks fastened to each other so as to form fluid pathways extending through the manifold and a passage through each valve manifold that aligns with each other to collectively form a continuous electrical conduit for receiving a series of connected circuit boards that actuate a respective valve unit mounted to a respective valve manifold block. Each circuit board has a set of conductive valve control lines connected to and extending between a respective set of first electrical connectors and a respective set of second mating electrical connectors. A conductive common line is connected to a third connector operably connected to one voltage side of the valve unit and also is connected to a respective first electrical connector and respective second mating electrical connector for connection to a respective conductive line in another valve manifold block. A serial communication line in each circuit board has a respective first electrical connector at of the first edge and a respective second mating electrical connector at the second edge for connection to a respective serial communication line in another valve manifold block.
At least one circuit board serves at least one double solenoid valve unit having two conductive valve lines for each double solenoid valve unit extending from the first electrical connector to a third connector at an opposite voltage side of each double solenoid valve unit at the valve manifold block for actuating each double solenoid valve unit. At least one circuit board serves at least one single solenoid valve unit having a conductive valve line for each single solenoid valve unit extending from the first electrical connector to a third connector at an opposite voltage side of each single solenoid valve unit at the respective valve manifold block for actuating each single solenoid valve unit. The serial communication line for the at least one circuit board serves the at least one single solenoid valve unit by extending to and connecting to a low voltage side of each single solenoid valve unit for communicating information relating thereto.
Preferably, a leg line is connected from the third connector to the detection circuit line through a diode to only allow current to pass from the leg line to the detection circuit line.
Also preferably, the set of conductive valve lines extend from the respective set of first electrical connectors at the first edge and extend and are shifted to a staggered relative position at the set of second mating connectors.
In accordance with one aspect of the invention, a serial communication circuit line includes a master, e.g. a driver device, which is normally used to energize a load through an operating circuit; e.g. a power circuit. The master drive circuit is designed in such a way that it not only turns the load on or off through a power circuit, but also sends data to the load through a single wire for reading and/or writing various parameters which can be used for diagnostic information or to change the functionality of the load. The load can be in the form of a smart slave device, (e.g. “smart” solenoid valve, proportional device, pressure switch or other component that requires monitoring, control or parameterization), which has appropriate circuitry to decipher and interpret the data sent from the master driver and can also report back information from the slave device to the master driver through the same single wire.
The single wire communication system usually in a form of a trace on the slave device board uses a bias voltage to power the electronic circuitry within the slave device. The master then modulates the current to the single wire trace in order to create voltage pulses that are greater than the bias potential thereby allowing the slave to identify that data is coming from the master.
The slave can only respond to a master's request or command, it cannot initiate communication. When responding to a master's request, the slave modulates the current to the single wire trace in order to create voltage pulses that are less than the bias potential thereby allowing the master to identify that data is coming back from the slave.
The handshaking routine can be comprised of data frames which has a start bit, 8 data bits and one stop bit. The complete data frame has 8 bytes, an address byte, a command byte, five data bytes and one checksum byte. The checksum byte is simply the sum of the preceding seven bytes and is used for error detection.
Addressing the slaves is required since the single wire communication trace is usually connected to a plurality of slave devices. Thus, it is important to identify which slave device is being addressed. This addressing function is done on initial power-up, or is initiated by the user when appropriate, and is achieved by the utilization of the existing “coil output” signals which are typically used to energize solenoid coils of conventional valves.
Upon power-up, the “coil output” signals are configured to sequentially strobe each coil trace with a very fast pulse, which is too fast to energize the coil of an attached valve. A sensing circuit in the slave is then triggered by the strobe pulse to allow that specific slave to receive an address.
Once the first slave gets an address from the master, the strobing sequence is incremented so the next slave device can be assigned sequential addresses. The system continues this addressing routine until all possible slave devices get a sequential address.
After all slave devices are addressed, the master can communicate to each individual slave device without affecting any other slave devices.
For example, the driver device is a smart valve driver device uses “active high” or PNP driver ICs to drive each of 32 coils on the valve manifold. The common for all 32 coils is 0 VDC. An isolated “switched” power is used to drive the manifold coils and is completely isolated from the “unswitched” power when used to power the logic and input sections of the manifold. Like a conventional valve driver, the smart valve driver receives its output data from the communication module. The valve driver then updates the drive ICs every 2 milliseconds with the output data which turns the coils on or off depending on the I/O data sent from the communication module.
Reference now is made to the accompanying drawings in which:
Referring now to
Preferably, each valve manifold block 12 may accommodate two single solenoid valve units 13 or two double solenoid valve units 14. Each valve manifold block 12 has a passage 28 that receives a single circuit board assembly 30 or a double circuit board assembly 32. Referring now to
Each circuit board 30 and 32 has pin connectors 38 and 39 mounted on a respective board 34. Each board has a first edge 40 and second edge 42 with respective trace contacts 44 and 46. As shown in
Referring now to
At first edge 40, the conductive valve line 66 corresponding to position A4 and operating the first valve V1, i.e. the valve on the present manifold block 12 leads to pin connector 38. Another conductive valve line 76 corresponding to position B4 and operating the second valve, i.e. the second single solenoid valve on the present manifold block 12 leads to pin connector 39. The pin connectors 38 and 39 are connected to the respective valve units 13. Each valve solenoid unit 13 is also respectively connected to pin connectors 38 and 39 which are connected to legs 91 and 92 that lead to a common voltage line 86 labeled Vcomn at each face 52 and 54. The Vcomn lines 86 at each face are connected to each other. The lines 86 are normally connected to a 24 volt supply to power all of the valve units 12 and 13.
Conductive lines 56 and 66 corresponding to V1 and V2 also both have legs 58 and 59 leading to a respective diode 60 and 62 in diode assembly 48. Each diode has its output connected to a leg 64 as clearly shown in
Referring now to
The board 32 has conductive valve lines 66 for V1 and V2 connected to pin connector 38 and conductive valve lines 76 for V3 and V4 are connected to pin connector 39 to power the two double solenoid valve units 14. Similar to the single circuit board 30, the double board 32 has a common voltage line 86 labeled Vcomn at each face 50 and 52 to power all the valve units, detection line 96, auxiliary power circuit lines 72 labeled 24 VDC and its return line 74 at 0 VDC, and protective earth line 82 PE or ground line that are not decremented. The detection line 96 at position A1 is not connected to the connectors 38 or 39 or the double valve units associated with this double circuit board 32.
In this valve operation, there is a sinking driver, i.e. power line which is supplied to along conductive power line 86 which is connected to all solenoids. In order to actuate the valve, each line 56, 66, or 76 must individually be grounded. This is usually done through an IC chip or driver at the end of the line, e.g. at the communication module 15 and connected to all of the conductive lines 56, 66 and 76. When a selected line is grounded, electrical current is then able to flow from the common power line 86 labeled Vcomn and through the selected solenoid and to ground to actuate an individual valve V1-V32. However, it is also foreseen that a sourcing driver can also work, i.e. a grounding common is connected to all solenoids and to actuate a valve, a voltage, for example 24V is individually connected.
The detection line 96 can be used to determine if the circuit board is a single board 30 or a double board 32. In one method, all the conductive valve lines 56, 66, and 76 are actuated. In the shown system this actuation is done by grounding the valve lines V1-V32 through an IC component or driver connected at one end from the first board. The power supply line 86 Vcomn is then able to provide current through each solenoid and down through the individual lines V1-V32. In operation, all the solenoid valves are actuated and the V1-V32 lines are grounded, thus the voltage detected on the detection line 96 is 0V.
Each contact is selectively and individually deactuated, i.e. turned off in sequence by the driver IC circuit usually housed in communication module 15. When the V1 line in the shown circuit board 30 is turned off, the V1 line is no longer grounded so V1 line reads 24V, in other words it now has the same voltage as the Vcomn line. The leg 58 which is directly connected to the V1 line also reads 24V and passes through the diode 60 as shown in
The V1 line is then re-actuated, and the V2 line is deactuated. Similarly, the V2 line will then read 24V when the V2 line is deactuated. The detection leg 94 downstream of diode 62 again reads 24V. Thus when V1 and V2 lines both are sequentially deactuated and the detection lines reads 24V for both deactuations, it is thus determined that the circuit board associated with V1 and V2 for this board is a single solenoid circuit board 30.
On the other hand, if the four voltage lines i.e. V1-V4 of double board 32 are actuated and deactuated in sequence, the detection line 96 as shown in
The process of the driver sinking (or sourcing) the voltage charge for this detection is very fast, so as not to change the position of the valve. For example, a sinking pulse or strobe connected by the driver to 0V can be 0.2 milliseconds. This is substantially too short to mechanically move the valve from its previous position. Furthermore, when the strobe is sent to valve status V1, none of the other valve lines V2-V32 are affected, because they did not received this strobe.
Other logical mapping and communications can be used with this single detection line 96 that passes through all the circuit boards 30 and 32. For example, if only one line V2 reads 24 V when deactuated but V1 remains at 0V when deactuated, it may be deduced that there is a no coil or solenoid valve in the valve unit associated with V1.
It is also foreseen that instead of a detection line, a single serial communication line may be used in other embodiments and for other purposes than detecting the presence of single and double solenoid circuit boards and the presence or absence of single or double solenoid valve units mounted on the valve manifold units of a fluid control system. Referring now to
In an alternative embodiment, in order to transmit data from the driver master 108 to the slave (valve) on the same connecting trace 100 that is also used to power the electronic circuitry and micro controller 104, the master device 108 then modulates the current to create voltage pulses that are greater than the bias potential allowing the slave device to identify that the data is coming from the master driver. The slave can only respond to a master's request or command, it cannot initiate communication. When responding to a master's request, the slave modulates the current to the single wire trace 100 in order to create voltage pulses that are less than the bias potential, allowing the master to identify that data is coming back from the slave.
This handshaking routine is comprised of data frames which consist of a start bit, 8 data bits and one stop bit. The complete data frame consists of 8 bytes, an address byte, a command byte, five data bytes and one checksum byte. The checksum byte is simply the sum of the preceding seven bytes and is used for error detection. Circuitry 106 and 104 on the slave valve is able to decode these data pulses for parameter and/or diagnostic functions.
Addressing the slaves is required since the single wire communication trace is connected to the entire set of 32 valves. Thus, it is important to identify which slave valve is being addressed. This addressing function for each smart valve is done on initial power-up, or is initiated by the user when appropriate, and is achieved by the utilization of the existing “coil output” signals which are typically used to energize solenoid coils of conventional valves.
Upon power-up, the “coil output” signals are configured to sequentially strobe each coil trace 110 and 112 with a very fast pulse from coil driver 115, which is too fast to energize the coil 116, 118 of an attached valve 102. The common voltage is along line 113. A detect circuit 114 in the slave is then triggered by the strobe pulse to allow that specific slave to receive an address.
Once the first slave obtains an address from the master, the strobing sequence is incremented so the next slave can be assigned sequential addresses. The system continues this addressing routine until all 32 possible slaves are assigned a sequential address. After all slaves are addressed, the master can communicate to each individual slave without affecting any other slave's function. Because each of the slaves receives a sequential address (1-32), the smart driver can then communicate with each slave individually at any time during operation. Smart slaves may be mixed on the same manifold with regular (Non-smart) valves.
Each of the smart valves (slaves) connected to the one wire is able to communicate with the smart driver through its transmit and receive circuit 120. Commands and data are sent from the smart driver to the smart slaves along line 100. Data and slave type is sent from the smart slaves to the smart driver along line 100.
One function that the smart valve may have is counting the number or times it has been energized. The smart valves will detect the activation of both the “A” and “B” coils 116, 118 and will record the total counts into non-volatile memory located on the smart valve circuitry. Additional slave types such as “smart pressure transducer” (Detect and report air pressure) or “smart pressure regulator” (regulate air pressures) are also possible.
In this fashion, communication through the valve manifold block assembly of a fluid control system is achieved by using a single serial communication line that is in direct contact with individual valve units throughout the manifold block assembly.
Other variations and modifications are possible without departing from the scope and spirit of the present invention as defined by the appended claims.
Filing Document | Filing Date | Country | Kind |
---|---|---|---|
PCT/US2013/032277 | 3/15/2013 | WO | 00 |
Publishing Document | Publishing Date | Country | Kind |
---|---|---|---|
WO2014/143002 | 9/18/2014 | WO | A |
Number | Name | Date | Kind |
---|---|---|---|
4161655 | Cotic et al. | Jul 1979 | A |
4744006 | Duffield | May 1988 | A |
4815496 | Nishitani | Mar 1989 | A |
4889164 | Hozumi | Dec 1989 | A |
4896700 | Stoll | Jan 1990 | A |
4950170 | Miller, Jr. | Aug 1990 | A |
5000226 | Stoll et al. | Mar 1991 | A |
5234033 | Stoll et al. | Aug 1993 | A |
5348047 | Stoll et al. | Sep 1994 | A |
5406260 | Cummings et al. | Apr 1995 | A |
5522431 | Bonacorsi | Jun 1996 | A |
5640995 | Packard et al. | Jun 1997 | A |
5706858 | Miyazoe | Jan 1998 | A |
5823071 | Petrosky et al. | Oct 1998 | A |
5884664 | Nagai et al. | Mar 1999 | A |
5887623 | Nagai et al. | Mar 1999 | A |
5918629 | Hayashi | Jul 1999 | A |
6053198 | Atkin et al. | Apr 2000 | A |
6056908 | Petrosky et al. | May 2000 | A |
6142182 | Akimoto | Nov 2000 | A |
6164323 | Smith et al. | Dec 2000 | A |
6164335 | Hayashi et al. | Dec 2000 | A |
6170527 | Hayashi et al. | Jan 2001 | B1 |
6173731 | Ottliczky | Jan 2001 | B1 |
6173745 | Hayashi et al. | Jan 2001 | B1 |
6206045 | Hayashi et al. | Mar 2001 | B1 |
6213153 | Hayashi et al. | Apr 2001 | B1 |
6216740 | Hayashi et al. | Apr 2001 | B1 |
6382257 | Mead et al. | May 2002 | B2 |
6427723 | Bogdanowicz et al. | Aug 2002 | B2 |
6513547 | Endo et al. | Feb 2003 | B2 |
6604555 | Blatt et al. | Aug 2003 | B2 |
6636782 | Morikawa et al. | Oct 2003 | B2 |
6701962 | Latino et al. | Mar 2004 | B2 |
6704815 | Morikawa et al. | Mar 2004 | B1 |
6734020 | Lu | May 2004 | B2 |
6812590 | Lee et al. | Nov 2004 | B2 |
6901794 | Zobel et al. | Jun 2005 | B2 |
6972955 | Pleskach et al. | Dec 2005 | B2 |
7011113 | Gandrud | Mar 2006 | B2 |
7061142 | Marshall | Jun 2006 | B1 |
7204273 | Zub | Apr 2007 | B1 |
7328720 | Miyazoe | Feb 2008 | B2 |
7383851 | Jacobsen et al. | Jun 2008 | B2 |
7441562 | Segawa et al. | Oct 2008 | B2 |
7457250 | Austermann, III et al. | Nov 2008 | B2 |
7545057 | Roo et al. | Jun 2009 | B1 |
7616453 | Bergmann | Nov 2009 | B2 |
7622824 | Orr et al. | Nov 2009 | B2 |
7653442 | Dalby et al. | Jan 2010 | B2 |
7798174 | Ford et al. | Sep 2010 | B2 |
7849880 | Herges | Dec 2010 | B2 |
7849881 | Lee et al. | Dec 2010 | B2 |
7896030 | Shinohara et al. | Mar 2011 | B2 |
7921314 | Schindler et al. | Apr 2011 | B2 |
7930568 | Schindler | Apr 2011 | B2 |
7978845 | Caveney et al. | Jul 2011 | B2 |
8074680 | De Carolis et al. | Dec 2011 | B2 |
8076797 | Kramer et al. | Dec 2011 | B2 |
8082457 | Randall et al. | Dec 2011 | B2 |
8094808 | Molenda et al. | Jan 2012 | B2 |
20010003289 | Mead et al. | Jun 2001 | A1 |
20010022191 | Bogdanowicz | Sep 2001 | A1 |
20010027813 | Endo | Oct 2001 | A1 |
20020000257 | Mead | Jan 2002 | A1 |
20040099314 | Hayashi | May 2004 | A1 |
20040112440 | Bramley et al. | Jun 2004 | A1 |
20050199305 | Webber | Sep 2005 | A1 |
20060011240 | Berner | Jan 2006 | A1 |
20070133155 | Zub | Jun 2007 | A1 |
20070137708 | Kuhbauch | Jun 2007 | A1 |
20090112151 | Chapman | Apr 2009 | A1 |
20110036424 | Oike et al. | Feb 2011 | A1 |
Number | Date | Country |
---|---|---|
WO 9404831 | Mar 1994 | DE |
1 014 273 | Jun 2000 | EP |
1094228 | Apr 2001 | EP |
2000283313 | Oct 2000 | JP |
2000283324 | Oct 2000 | JP |
2001032956 | Feb 2001 | JP |
2001254859 | Sep 2001 | JP |
WO 9115037 | Oct 1991 | SE |
Entry |
---|
European International Search Report; International Application No. 13878143.0; Filing Date Oct. 7, 2015; dated Nov. 2, 2016; 8 Pages. |
International Search Report and Written Opinion—International Application No. PCT/US2013/032277, Filing Date: Mar. 15, 2013, dated Jun. 5, 2013, 16 pages. |
Number | Date | Country | |
---|---|---|---|
20150369380 A1 | Dec 2015 | US |