Fluidic die

A fluidic die may include a substrate supporting a fluid actuator address line and first and second groups of fluid actuators connected to the fluid actuator address line. The first group of fluid actuators may include first and second types of fluid actuators having different operating characteristics. The second group of fluid actuators may include the first and the second types of fluid actuators. The fluid actuators of the first and second groups have addresses such that a fluid actuator of the first type in the first group and a fluid actuator of the second type in the second group are both enabled in response to a single enabling event on the fluid actuator address line.

BACKGROUND

Fluidic dies may control the movement and ejection of fluid. Such fluidic dies may include fluid actuators that may be actuated to cause displacement of fluid. Some example fluidic dies may be printheads, where the fluid may correspond to ink.

DETAILED DESCRIPTION OF EXAMPLES

Examples of fluidic dies may comprise fluid actuators. The fluid actuators may include a piezoelectric membrane based actuator, a thermal resistor based actuator, an electrostatic membrane actuator, a mechanical/impact driven membrane actuator, a magneto-strictive drive actuator, or other such elements that may cause displacement of fluid responsive to electrical actuation. Fluidic dies described herein may comprise a plurality of fluid actuators, which may be referred to as an array of fluid actuators. Moreover, an actuation event, as used herein, may refer to concurrent actuation of fluid actuators of the fluidic die to thereby cause fluid displacement. Despite occurring in response to a single actuation event, concurrent actuation of fluid actuators, as used herein, may include slight time delays at and between each of the concurrently actuated individual actuators such that the fluid actuators are not actuated simultaneously, reducing peak voltage demands.

In example fluidic dies, the array of fluid actuators may be arranged in respective sets of fluid actuators, where each such set of fluid actuators may be referred to as a “primitive” or a “firing primitive.” A primitive generally comprises a group or set of fluid actuators that each have a unique actuation address. In some examples, electrical and fluidic constraints of a fluidic die may limit which fluid actuators of each primitive may be actuated concurrently for a given actuation event. Therefore, primitives facilitate addressing and subsequent actuation of fluid ejector subsets that may be concurrently actuated for a given actuation event. A number of fluid ejectors corresponding to a respective primitive may be referred to as a size of the primitive.

To illustrate by way of example, if a fluidic die comprises four primitives, where each respective primitive comprises eight respective fluid actuators (each eight fluid actuator group having an address 0 to 7), and electrical and fluidic constraints limit actuation to one fluid actuator per primitive, a total of four fluid actuators (one from each primitive) may be concurrently actuated for a given actuation event. For example, for a first actuation event, the respective fluid actuator of each primitive having an address of 0 may be actuated. For a second actuation event, the respective fluid actuator of each primitive having an address of 1 may be actuated. As will be appreciated, the example is provided merely for illustration purposes. Fluidic dies contemplated herein may comprise more or less fluid actuators per primitive and more or less primitives per die.

In example fluidic dies, the fluid actuators may be concurrently enabled by a single address enabling event caused by electric signals transmitted along a fluid actuator address line. As used herein, an address enabling event may refer to concurrent enablement of fluid actuators of different primitives having a same address to ready such fluid actuators for subsequent actuation in response to receiving other enabling signals. For example, actuation of a fluid actuator may occur in response to a fluid actuator receiving at least the address enabling signals transmitted across a fluid actuator address line and primitive enabling signals received across a data or primitive select line. As used herein, a fluid actuator address line may comprise a single electrically conductive line, such as a wire or trace, or a set of electrically conductive lines which cooperate to transmit a set of electrical signals to form the address enabling event.

In some examples, a fluid actuator may be disposed in a nozzle, where the nozzle may comprise a fluid chamber and a nozzle orifice in addition to the fluid actuator. The fluid actuator may be actuated such that displacement of fluid in the fluid chamber may cause ejection of a fluid drop via the nozzle orifice. Accordingly, a fluid actuator disposed in a nozzle may be referred to as a fluid ejector.

Some example fluidic dies comprise microfluidic channels. Microfluidic channels may be formed by performing etching, microfabrication (e.g., photolithography), micromachining processes, or any combination thereof in a substrate of the fluidic die. Some example substrates may include silicon based substrates, glass based substrates, gallium arsenide based substrates, and/or other such suitable types of substrates for microfabricated devices and structures. Accordingly, microfluidic channels, chambers, orifices, and/or other such features may be defined by surfaces fabricated in the substrate of a fluidic die. Furthermore, as used herein a microfluidic channel may correspond to a channel of sufficiently small size (e.g., of nanometer sized scale, micrometer sized scale, millimeter sized scale, etc.) to facilitate conveyance of small volumes of fluid (e.g., picoliter scale, nanoliter scale, microliter scale, milliliter scale, etc.). Example fluidic dies described herein may comprise microfluidic channels in which fluidic actuators may be disposed. In such implementations, actuation of a fluid actuator disposed in a microfluidic channel may generate fluid displacement in the microfluidic channel. Accordingly, a fluid actuator disposed in a microfluidic channel may be referred to as a fluid pump.

In some examples described herein, a fluidic die may include a substrate supporting a fluid actuator address line and first and second primitives or sets of fluid actuators connected to the fluid actuator address line. The first primitive or set of fluid actuators may include first and second types of fluid actuators having different operating characteristics. The second primitive or set of fluid actuators may include the first and the second types of fluid actuators. The fluid actuators of the first and second sets have addresses such that a fluid actuator of the first type in the first set and a fluid actuator of the second type in the second set are both concurrently enabled in response to a single enabling event on the fluid actuator address line.

In some examples described herein, the first type of fluid actuators in the first set and the second different type of fluid actuators in the second set each have a first set of addresses while the second type of fluid actuators in the first set and the first type of fluid actuators in the second set each have a second set of addresses. In some examples, the first set of addresses are even numbered addresses while the second set of addresses are odd numbered addresses.

In some examples described herein, the first type of fluid actuators has a first actuation energy demand, wherein the second type of fluid actuators has a second actuation energy demand different than the first actuation energy demand. In some examples, the first type of fluid actuators is to eject fluid through corresponding nozzles, wherein the second type of fluid actuators is to circulate fluid to a firing chamber. In some examples, fluid actuators of the first type alternate with the fluid actuators of the second type in the first and second sets of fluid actuators.

Disclosed herein are example methods, wherein a single address enabling event is transmitted on a fluid actuator address line of a fluidic die to each of a first set of fluid actuators and a second set of fluid actuators. The single address enabling event is to enable a single fluid actuator for actuation in each of the first set and the second set. The example method may include enabling a first fluid actuator of a first type of fluid actuators in the first set of fluid actuators in response to the single address enabling event and enabling a second fluid actuator of a second type of fluid actuators in the second set of fluid actuators, in response to the single address enabling event. The second type of fluid actuators each have an operational characteristic different than that of the first type of fluid actuators. The method may further include transmitting a fluid actuator enabling event to the first set of fluid actuators and the second set of fluid actuators. The first fluid actuator may be actuated in response to a combination of the first fluid actuator being enabled by the single address enabling event and the first fluid actuator receiving the fluid actuator enabling event. The second fluid actuator may be actuated in response to a combination of the second fluid actuator being enabled by the single address enabling event and the second fluid actuator receiving the fluid actuator enabling event.

FIG. 1is a schematic diagram illustrating portions of an example fluidic die20. Fluidic die20comprises substrate22, fluid actuator address line24and fluid actuators32A,32B (collectively referred to as fluid actuators32) and fluid actuators34A,34B (collectively referred to as fluid actuators34. Fluid actuator address line24comprises at least one electrically conductive wire or trace by which electrical signals are transmitted to logic associated with each of the fluid actuators32,34to enable actuators32,34for possible subsequent actuation during an actuation event. In one implementation, fluid actuator address line24comprises multiple electrically conductive wires or traces. For example, fluid actuator address line24may comprise at least three bits or three individual bit lines.

Fluid actuators32and34comprise devices or elements that cause displacement of a fluid in response to electrical actuation. The fluid actuators32,34may include a piezoelectric membrane based actuator, a thermal resistor based actuator, an electrostatic membrane actuator, a mechanical/impact driven membrane actuator, a magneto-strictive drive actuator, or other such elements.

Fluid actuators32have different operating characteristics as compared to fluid actuators34. In one implementation, fluid actuators32have different energy demands or utilize different voltage levels, current or energy during actuation than that of fluid actuators34. In one implementation, fluid actuators32are in the form of fluid ejectors whereas fluid actuators34are in the form of fluid pumps. A fluid ejector may comprise an actuator that displaces fluid in an ejection chamber through an orifice. A fluid pump may comprise an actuator that displaces fluid in a microfluidic channel. In one implementation, fluid actuators32and34may both comprise fluid ejectors, but where fluid actuators32and34have different drop weights or other different operational characteristics. In one implementation, fluid actuator32and34may both comprise fluid pumps, but where fluid actuators32and34have different energy voltage demands.

As indicated by broken lines inFIG. 1, fluid actuators32A and34A, collectively, form a first set40A of fluid actuators while fluid actuators32B and34B, collectively, form a second set408of fluid actuators. Sets40A and40B (collectively referred to as sets40) extend adjacent to one another or are consecutive on substrate22. Each of sets40comprises a subset42of fluid actuators32and a subset44of fluid actuators34. AlthoughFIG. 1illustrates such actuators32,34physically arranged in columns, in other implementations, actuators32,34may be in rows, arrays or other physical arrangements.

Sets40form what may be referred to as primitives of fluidic die20, each set having a same set of addresses. In other words, each fluid actuator in set40A has an address that is the same as the address of a fluid actuator in set40B. Although each of sets40has a same set of addresses, the addresses of the sets40A and40B are oppositely apportioned between the different types fluid actuators. In the example illustrated, the fluid actuators of each of sets40have a set of addresses comprising addresses A1,1to A1,nand addresses A2,1to A2,n. However, in set40A, fluid actuators32A have addresses A1,1, to A1,n, whereas in set40B, fluid actuators32B have addresses A2,1to A2,n. Likewise, in set40A, fluid actuators34A have addresses A2,1to A2,n, whereas in set40B, fluid actuators34B have addresses A1,1to A1,n.

Because the same sets of addresses in sets40are oppositely apportioned between the different types of fluid actuators32,34in each set40, a single address enabling event on address line24concurrently enables different types of fluid actuators in the different sets40. For example, a single address enabling event resulting in the transmission of address enabling signals across address line24to enable address A1,1may result in fluid actuator32A (of a first type T1) of set40A being enabled for a subsequent actuation event while also resulting in fluid actuator34B (of a second type T2) being enabled for the same subsequent actuation event. By way of another example, a single address enabling event resulting in the transmission of address enabling signals across address line24to enable address A2,1may result in fluid actuator34A (of the second type T2) of set40A being enabled for a subsequent actuation event while also resulting in fluid actuator32B (of the first type T1) being enabled for the same subsequent actuation event.

The example addressing scheme of fluidic die20may facilitate more flexibility in the actuation order of fluid actuators32,34. In examples where fluid actuators32,34have different energy demands, the example addressing scheme of fluid die20may facilitate reduced peak currents. For example, in one implementation where fluid actuator32comprise fluid ejectors which may have higher energy demands and fluid actuators34comprise fluid pumps having lower energy demands or peak currents, the number of fluid ejectors is spread out over the total number of addresses in each set40, resulting in half, rather than all, of the total number of fluid ejectors being enabled for possible actuation during a subsequent actuation event. In other words, the first half of the fluid ejectors may be enabled for possible actuation during a first actuation event while a second half of the fluid actuators may be enabled for possible actuation during a second actuation event.

Although fluid actuators32and34are each schematically illustrated as comprising fluid actuators that are clustered or grouped in each of sets40, it should be appreciated that the different fluid actuators32,34may be interspersed amongst one another in each set40. For example, in one implementation, fluid actuators32and34may alternate with one another in each set40. Fluid actuators32may have even addresses while fluid actuators34have odd addresses, or vice versa. Regardless of location or relative positioning on die20, each fluid actuator of a first type in set40A with a given address has a corresponding fluid actuator of a second type in40B with the same given address.

FIG. 2is a schematic diagram of portions of fluidic die120. Fluidic die120is similar to fluidic die20except that fluidic die120is illustrated as comprising at least four consecutive primitives or sets40of fluid actuators32,34. Those components of fluidic die120which correspond to components of fluidic die20are numbered similarly. AlthoughFIG. 2illustrates such actuators32,34physically arranged in columns, in other implementations, actuators32,34may be in rows, arrays or other physical arrangements.

As shown byFIG. 2, fluidic die120additionally comprises sets40C and40D of fluid actuators32C,34C,32D,34D, respectively. Fluid actuators32C,32D may be similar to fluid actuators32A and32B, respectively. Likewise, fluid actuators34C,34D may be similar to fluid actuators34A and348, respectively. With respect to fluidic die120, fluid actuators32A-32C and fluid actuators34A-34D are collectively referred to as fluid actuators32and fluid actuators34, respectively. Fluid actuators32and34are all connected to fluid actuator address line24which transmits address enabling signals as part of an address enabling event to enable a selected address long address line24for possible subsequent actuation during a subsequent actuation event.

As with fluidic die20, because the same sets of addresses in each of sets40are oppositely apportioned between the different types of fluid actuators32,34in each set40, a single address enabling event on address line24concurrently enables different types of fluid actuators in the different sets40. For example, a single address enabling event resulting in the transmission of address enabling signals across address line24to enable address A1,1 may result in fluid actuator32A (of a first type T1) of set40A being enabled for a subsequent actuation event, fluid actuator34B (of a second type T2) being enabled for the subsequent actuation event, fluid actuator32C (of the first type T1) of set40C being enabled for the subsequent actuation event and fluid actuator34D (of the second type T2) being enabled for the same subsequent actuation event. By way of another example, a single address enabling event resulting in the transmission of address enabling signals across address line24to enable address A2,1 may result in fluid actuator34A (of the second type T2) of set40A being enabled for a subsequent actuation event, fluid actuator32B (of the first type T1) being enabled for the subsequent actuation event, fluid actuator34C (of the second type T2) of set40C being enabled for the subsequent actuation event and fluid actuator32D (of the first type T1) being enabled for the same subsequent actuation event.

FIG. 3is a schematic diagram illustrating a portion of an example fluidic die220. Fluidic die220is similar to fluidic dies20and120except that fluidic die220is specifically illustrated as having different types of fluid actuators in the form of fluid ejectors and fluid pumps that alternate with one another along address line24. In one implementation, the fluid ejectors have different energy voltage demands as compared to the fluid pumps. Those components of fluidic die220which correspond to components of fluidic dies20and120are numbered similarly.

As shown byFIG. 3, fluidic die220comprises fluid actuators in the form of fluid ejectors232A,232B (collectively referred to as fluid ejectors232) and fluid actuators in the form of fluid pumps234A,234B (collectively referred to as fluid pumps234). Each fluid ejector232is part of a larger nozzle250, wherein each nozzle250has an orifice through which fluid is ejected through the displacement caused by the associated fluid ejector232. In the example illustrated, fluid ejectors232/nozzles250and fluid pumps234alternate along address line24, wherein fluid ejector232and fluid pumps234are paired, wherein a fluid pump234circulates fluid to and/or from a paired or associated fluid ejector232/nozzle250. In other implementations, the interspersed nozzles250and fluid pumps234may have other arrangements or patterns.

As indicated by broken lines, fluid ejectors232and fluid pumps234form two sets240A and240B (collectively referred to as sets240) of fluid actuators. Each of sets240comprises a subset242of fluid ejectors232and a subset244of fluid pumps234. Sets240form what may be referred to as primitives of fluidic die220, each set having a same set of addresses. In other words, each fluid actuator in set240A has an address that is the same as the address of a fluid actuator in set240B. Although each of sets240has a same set of addresses, the addresses of the sets240A and240B are oppositely apportioned between the different types fluid actuators. In the example illustrated, the fluid actuators of each of sets40have a set of addresses comprising addresses A1 to An. In the example illustrated, the fluid ejectors232A of set240A have even addresses (for example, 0, 2, 4 . . . n−1) while the fluid pumps234of set240A have the odd addresses (for example, 1, 3, 5 . . . n). Conversely, the fluid ejectors232B of set2408have odd addresses (for example, 1, 3, 5 . . . n) while the fluid pumps2348have even addresses (for example, 0, 2, 4 . . . n−1).

Because the same sets of addresses in sets240are oppositely apportioned between the fluid ejectors232and fluid pumps234in each set240, a single address enabling event on address line24concurrently enables different types of fluid actuators in the different sets240. For example, a single address enabling event resulting in the transmission of address enabling signals across address line24to enable address A3 may result in fluid ejector232A at address A3 of set240A being enabled for a subsequent actuation event while also resulting in fluid pump234B at address A3 of set240B being enabled for the same subsequent actuation event. By way of another example, a single address enabling event resulting in the transmission of address enabling signals across address line24to enable address A4 may result in fluid pump234A at address A4 of set40A being enabled for a subsequent actuation event while also resulting in ejector232B at address A4 of set2408being enabled for the same subsequent actuation event.

The example addressing scheme of fluidic die220may facilitate more flexibility in the actuation order of fluid ejectors232and fluid pumps234. In examples where fluid ejectors232and fluid pumps234have different energy demands, the example addressing scheme of fluid die220may facilitate reduced peak currents. For example, in one implementation where fluid ejectors232have higher energy demands and fluid pumps34have lower energy demands or peak currents, the number of fluid ejectors is spread out over the total number of addresses in each of sets240, resulting in half, rather than all, of the total number of fluid ejectors being enabled for possible actuation during a subsequent actuation event. In other words, the first half of the fluid ejectors may be enabled for possible actuation during a first actuation event while a second half of the fluid actuators may be enabled for possible actuation during a second actuation event.

FIGS. 4 and 5schematically illustrate portions of an example fluid ejection system300having a fluid ejection controller310and a fluidic die320with the same address scheme as described above with respect to fluidic die220. As with fluidic die220, fluidic die320comprises an array of fluid actuators in the form of fluid ejectors332and fluid pumps334connected to a fluid actuator address line24. Fluid ejectors332and fluid pumps334are paired along address line24, wherein each of the fluid pumps334circulates fluid to and/or from an associated fluid ejector332. Fluid ejectors332and fluid pumps334are arranged in primitives or sets340A,340B of fluid ejectors/fluid pumps. AlthoughFIG. 4, for ease of illustration, depicts a single pair of a fluid ejector332and an associated pump334for each of sets340A,340B, it should be appreciated that sets340A,340B may each include an array of fluid ejector332/fluid pump334pairs along address line24.

As further shown byFIG. 4, each fluid ejector332is part of a nozzle350having an ejection chamber352having an orifice354and in which the fluid ejector332is located. Each ejection chamber352is fluidly connected to a fluid supply356by a fluid input358and a microfluidic channel360. In the example illustrated, each fluid input358and microfluidic channel360facilitate circulation of fluid into ejection chamber352, through and across ejection chamber352and out of ejection chamber352back to fluid supply356. In the example illustrated, such circulation is facilitated by fluid pump334within microfluidic channel360.

In one implementation, fluid supply356comprises an elongate slot supplying fluid to each of the fluid ejectors332in each of the sets340of die320. In another implementation, fluid supply356may comprise an array of ink feed holes. In one implementation, fluid supply356further supplies fluid to primitives or sets340of fluid ejector332and fluid pumps334located on an opposite side of fluid supply356. In some implementations, fluidic die320may comprise multiple primitives are sets similar to the arrangement shown on fluidic die120.

In the example illustrated, each fluid ejector332and each fluid pump334comprises triggering logic (L)370which controls the firing or actuation of the fluid actuator, either in the form of fluid ejector332or in the form of fluid pump334.FIG. 5schematically illustrates one example of triggering logic370on fluidic die320and associated with a fluid actuator in the form of a fluid ejector332or a fluid pump334. As shown byFIG. 5, triggering logic370comprises a transistor372and logic element (LE)374. Transistor372is a switch selectively transmitting a voltage Vpp to fluid ejector332or fluid pump334in response to a signal received from logic element374.

The logic element374comprises electronic circuitry and components that pass and actuation or fire signal to transistor372in response to the primitive enabling line or address line378and the address line24both being active. In one implementation, logic element374comprises a gate or other AND logic circuitry (schematically illustrated) that transmits the control signals or fire pulse signal received from a fire pulse line376to the gate of transistor372in response to receiving an address signal from address line24and also receiving a primitive enabling data signal from a data, primitive select or primitive enabling line378. Although not shown inFIG. 4for ease of illustration, fire pulse line376and primitive enabling line378also reside on substrate22of fluidic die320. In other implementations, logic element374may comprise other forms of electrical circuitry. For example, in other implementations, primitive enabling data signals and fire pulse signals may be combined upstream (such as at the primitive level) or may be inverted.

It should be appreciated that in some implementations, the different types of fluid actuators, such as the fluid ejectors332and the fluid pumps334may have separate or dedicated fire pulse lines376that transmit fire pulse with different characteristics, such as fire pulses with different frequencies, amplitude and/or durations. For example, each of the fluid ejectors332may be connected to a first fire pulse line376while each of the fluid pumps334are connected to a separate and different fire pulse line376.

Primitive enabling line378receives a data signal when the particular primitive or set340to which the fluid ejector332, fluid pump334belongs, is to be enabled for firing. In the example illustrated, in response to receiving a combination of address enabling signals on address line24and primitive enabling signals or data signals on primitive enabling line378, the fluid ejector332, fluid actuator334is actuated in accordance with the fire pulse received on line376.

Fluid ejection controller310transmits packets of information to fluidic die320, wherein logic on die320parses out instructions pertaining to which address is to be enabled for a particular actuation event and which printers or sets340are to also be enabled such that those fluid ejector332and fluid pumps334of the different sets340that receive both address enabling signals and primitive enabling signals are actuated pursuant to the fire pulse signal received on line376.FIG. 6is a flow diagram of an example method400for actuating fluid actuators having different operating characteristics and arranged in different primitives are sets on a fluidic die. Although method400is described as being carried out by the example fluid ejection system300having different fluid actuators in the form of fluid ejectors and fluid pumps, method400may also be carried out with any sets of different fluid actuators having different operating characteristics. For example, method400may likewise be carried out with sets of different fluid ejectors, each set having at least two types of fluid ejectors, such as different types of fluid ejectors having different drop weights or other different operational characteristics. Method400may likewise be carried out with sets of different fluid pumps, each set having at least two types of fluid pumps having different energy demands

As indicated by block404, address line24transmits address enabling signals to each of a first set340A and a second set340B of fluid actuators332,334. The address enabling signals enable a single address on the fluid actuators line24of die20.

As indicated by block406, in response to the address enabling signals transmitted in block404, a first actuator of a first type of fluid actuators in a first set of fluid actuators340A and having the address enabled by the address enabling signals is enabled for actuation during a subsequent actuation event. With reference toFIG. 5, the address enabling signals are received by the logic element374of the first fluid actuator.

As indicated by block408, in response to the address enabling signals transmitted in block404, a second actuator of a second type of fluid actuators in a second set340B of fluid actuators and having the address enabled by the address enabling signals is enabled for actuation during a subsequent actuation event. With reference toFIG. 5, the address enabling signals are received by the logic element374of the second fluid actuator. The first fluid actuator and the second fluid actuator are different types of fluid actuators. With respect to the example fluidic die320, the first actuator may be in the form of fluid ejector332while the second actuator may be in the form of fluid pump334, or vice versa.

As indicated by block410, primitive enabling signals (also sometimes referred to as data signals) are transmitted to each fluid actuator, each fluid ejector332and each fluid pump334, of the first set340A of fluid actuators and of the second set340B of fluid actuators. With reference toFIG. 5, the primitive enabling signals are received by the logic element374across lines378of each fluid ejector332and each fluid pump334, of the first set340A of fluid actuators and of the second set340B of fluid actuators. Although blocks406and408are illustrated as occurring before block410, it should be appreciated that blocks406,408and410may be carried out in any order.

As indicated by block412, fire pulse signals are transmitted to the first set of fluid actuators and the second set of fluid actuators. The fire pulse signals control the timing, frequency and duration of each logical pulse transmitted to a fluid actuator during actuation. As indicated above, in some implementations, the fire pulse signals may be transmitted independent of the primitive enabling and address signals. In other implementations, the fire pulse signals may be combined upstream with the primitive enabling/data signals.

As indicated by block414, in response to the first fluid actuator receiving a combination of the address enabling signals on address line24and the primitive enabling signals on print enabling line378, the first actuator of the first type in the first set340A of fluid actuators is actuated pursuant to the fire pulse received associated fire pulse line376. As indicated by block416, in response to the first fluid actuator receiving a combination of the address enabling signals on address line24and the primitive enabling signals on primitive enabling line378, the second actuator of the second type in the second set340B of fluid actuators is actuated pursuant to the fire pulse received on the associated fire pulse line376. In some instances, the first actuator may receive an address enabling signal on address line24while not receiving primitive enabling signals on primitive enabling line378, result in the first actuator not being actuated or fired. Likewise, in some instances, the first actuator may receive a primitive enabling signal on primitive enabling line378while not receiving an address enabling signal on address line24, resulting in the first actuator not being fired. The same logic applies with respect to the second actuator.

FIG. 7is a schematic diagram of another example fluidic die520. Microfluidic die520is similar to microfluidic die320except that microfluidic die520is illustrated as comprising a fluid supply in the form of a fluid slot556that supplies fluid to 3136 fluid actuators, alternating between fluid pumps and fluid ejectors, on either side of slot556and arranged in primitives or sets540(1-391), each set including eight fluid actuators, four fluid ejectors and four fluid pumps. As schematically shownFIG. 7, the ejectors are associated with a nozzle orifice354while the pumps are contained within are associated with a microfluidic channel360.

FIG. 7illustrates the use of the addressing scheme described above with respect to fluidic dies20,120and320on a larger scale. As shown byFIG. 7, and each pair of adjacent or consecutive primitives on a side of slot556, the set of addresses in the sets are primitives540oppositely assigned to the ejectors332and pumps334. For example, in primitive 2, the ejectors have even addresses (0,2,4,6) while the pumps have odd addresses (1,3,5,7). Conversely, in the adjacent or consecutive primitive 4, the ejectors have odd addresses (1,3,5,7) while the pumps have even addresses (0,2,4,61,3,5,7) the same schemas apply with respect to primitives1,3, primitives390,392, primitive389,391and so on.

As with fluidic die220described above, the example addressing scheme of fluidic die520may facilitate more flexibility in the actuation order of fluid ejectors332and fluid pumps334. In examples where fluid ejectors332and fluid pumps334have different energy demands, the example addressing scheme of fluid die520may facilitate reduced peak currents. For example, in one implementation where fluid ejectors332have higher energy demands and fluid pumps334have lower energy demands or peak currents, the number of fluid ejectors is spread out over the total number of addresses in each of sets540, resulting in half, rather than all, of the total number of fluid ejectors being enabled for possible actuation during a subsequent actuation event. In other words, the first half of the fluid ejectors may be enabled for possible actuation during a first actuation event while a second half of the fluid actuators may be enabled for possible actuation during a second actuation event.

FIG. 8is a schematic diagram of a portion of another example fluidic die620having data pad621, data parser622and address line624. Fluidic die620additionally comprises each of those components illustrated and described above respect toFIGS. 4 and 5such as primitives or sets340of different fluid ejectors in the form of fluid ejectors332and fluid pumps334as well as fluid input358, microfluidic channel360and the components of nozzle350such as ejection chamber352and orifice354. In the example illustrated, each set340comprises eight fluid actuators, four fluid ejectors332and four fluid pump334. As should be appreciated, in other implementations, such as primitives or sets may comprise a greater or smaller number of such fluid actuators. Each fluid ejector332, fluid pump334may comprise the triggering logic370as illustrated and described above, but where fluid actuator address line24is replaced with fluid actuator address line624as illustrated inFIG. 8.

Data pad621comprise electric connections by which data packets are received from fluid ejection controller310(shown inFIG. 5) data parser622comprises electronics or logic that parses the data packet to identify a designated fluid actuator address to be enabled for a particular actuation event. Data parser622may transmit signals along address line624based upon the designated fluid actuator address.

FIG. 8illustrates fluid actuator address line624and its connection to fluid ejectors332and fluid pumps334of sets340A and340B. Fluid actuator address line624comprises address bit lines680, complementary address bit lines682and address decoding logic elements684. Address bit lines680comprise electrically conductive wires or traces on substrate22that represent three bits, Addr(0), Addr (1) and Addr(2) and which are connected to or not connected to respective address decoding logic elements684based upon the binary address of the fluid actuator332,334connected to the respective address decoding logic elements684. For example, as shown byFIG. 8, the topmost fluid ejector332of set340A with an address of “0” has an associated logic element684that is not connected to Addr(2) (a bit value of 0), that is not connected to Addr(1) (a bit value of 0) and that is not connected to Addr(0) (a bit value of 0), forming a binary value of 000 or zero. Likewise, the topmost fluid pump334of set340A with an address of “1” has an associated logic element684that is not connected to Addr(2) (a bit value of 0), that is not connected to Addr(1) (a bit value of 0) and that is connected to Addr(0) (a bit value of 1), forming a binary value of 001 or one. The next actuator, in the form of a fluid ejector having address “2”, has an associated logic element684that is not connected to Addr(2) (a bit value of 0), that is connected to Addr(1) (a bit value of 1) and that is not connected to Addr(0) (a bit value of 0), forming a binary address value of 010 or two. This binary connection scheme continues for the remaining addresses the 3-7 of the fluid ejectors332and fluid pumps334of set340A.

The same binary connection described above with respect to set340A is applied to set340B (and any other primitives or sets of fluidic die620). However, as shown byFIG. 8, the set of addresses 0-7 in set340B are oppositely assigned to the fluid ejectors332and fluid pump334. Instead of fluid ejectors332being assigned even addresses and the fluid pumps334being assigned odd addresses, the fluid pumps are assigned even addresses while the fluid ejectors are assigned odd addresses. As with set340A, the address bit line680of fluid actuator address line624are connected to the logic element684of each fluid ejector332or fluid pump334based upon the address of the fluid ejector332or fluid pump334. For example, the fluid ejector332having an address of “7” has an address decoding logic element684that is connected to Addr(2) (a bit value of 1), that is connected to Addr(1) (a bit value of 1), and that is connected to Addr(0) (a bit value of one), forming a binary address value of 111 or seven.

The complementary address bit lines682cooperate with address bit lines680to transmit signals such that an individual address decoding logic element684transmits an address enabling signal to its respective fluid ejector332or fluid pump334in response to an individual fluid ejector332or fluid pump334being addressed by line624. The complementary address bit lines682comprise electrically conductive wires or traces on substrate22that are connected to or not connected to the logic element682of the different fluid ejectors332and fluid pumps334based upon the address of the respective fluid ejector332, fluid pumps334. The complementary address bit lines682for a particular logic element684for a particular fluid ejector332or fluid pump334have connections that are the opposite of the connections of the respective address bit line680to the same particular fluid ejector332or fluid pump334. For example, in set340A, the fluid ejector332with an address of “4” has a logic element684connected to address bit line Addr(2) but not connected to the remaining address bit lines Addr(1) and Addr(2) to form a binary address of 100 with a value of 4. Accordingly, the same address decoding logic element682for the fluid ejector332having an address of “4” is connected to address bit lines682in a complementary or opposite fashion, not being connected to Addr(2) while being connected to Addr(1) and Addr(0). In one implementation, the connections between each of the logic element684and the address bit line680and complementary address bit line682is made on substrate22with metal 2 layer jumpers.

In the example illustrated inFIG. 8, the address to be enabled in each of the sets340of fluid ejector332and fluid pumps334is carried out by selectively connecting the different address bit line680and complementary address bit line682to a high “1” or a low “0” voltage level. Such selective connection may be made by actuation logic utilizing transistors or other switches. For example, to transmit the address “5” along line624to concurrently enable the fluid pump334in set340A having address “5” and the fluid ejector332in set340B having address “5”, the address bit lines Addr(2) and Addr(0) of the address bit lines680and the complementary address bit line N Addr(1) are connected to a high “1” voltage level. At the same time, the address bit line Addr(1) of the address bit line680and the address bit lines N Addr(2) and N Addr(0) of the complementary address bit lines682are connected to a low “0” voltage, either I a null or zero voltage or a negative voltage. The other fluid ejectors332and fluid pumps334may receive enabling signals via fluid actuator address line624in a similar fashion.

In the example illustrated, address decoding logic elements684comprise AND logic such as a gate or other electronic circuitry that provide AND logic, wherein the output results in response to all of the input lines being active or the signals. In other implementations, address decoding logic elements684may comprise other electronic circuitry that decodes the address being transmitted along bit lines680and682. Still other implementations, addresses may be transmitted along address data line624using other numbers or combinations of bit lines as well as other address encoding circuitry or elements.

In the examples shown inFIGS. 4-5andFIG. 8, examples of an embedded addressing scheme are described. It should be appreciated that in other implementations, other addressing schemes other than embedded addressing schemes may be employed. For example, addressing schemes employing the direct wiring of address lines may be employed, wherein the enabling or firing order of primitives of fluid actuators is alternated as described above.