A Printer that Delivers 1,000 Pages a Minute?


Recommended Posts

Two researchers from The College of Judea and Samaria in Israel have designed an ink-jet printer head that could lead to printers capable of chugging out 1,000 pages per minute ? or even more.

The innovative printer head created by engineers Moshe Einat and Nissim Einat works in a similar way as a liquid crystal display (LCD). But while an LCD emits tiny pixels of light, collectively forming the picture on your laptop or television, their print head emits pixels of ink. Their basic design is small, but it can be reproduced and the copies combined into one large printer head.

?Unlike traditional printer heads that are small and have to move back and forth across the page, our print head can be enlarged into one that is the size of a sheet of paper or larger. One can think of it as an 'ink-emitting screen',? Moshe Einat told PhysOrg.com. ?This means it could print one page almost instantly, and hundreds of pages in just seconds.?

Current ink-jet printer heads work by channeling ink from a main reservoir to a series of nozzles, which are negatively pressurized to eject equal-sized ink drops. But when the number of nozzles increases, the pipe manifold connecting the reservoir to the nozzles becomes complicated and stable ink-flow conditions are harder to maintain. For example, shock waves in the ink can create ?cross-talk? problems between nozzles. Another issue is the drop-ejection rate, which must be limited in order to mainstain system stability and print quality. This, in turn, stunts the print speed. The motion of standard print heads presents additional problems.

?Our design avoids these physical limitations,? said Einat.

The design's building block is a micro-reservoir of ink that feeds four nozzles. The reservoir is square, one millimeter (mm) on each side, and is 0.5 mm deep. The ink enters the nozzles via capillary action (the way water naturally creeps up a plant stem, for instance). To refill, an ink-coated ?wiper? slides over the top of the reservoir, depositing a layer of ink. The small amount of ink in each reservoir and the natural capillary force between the ink and the reservoir walls make pressure regulation fairly simple.

Einat and Einat combined many of these basic stand-alone segments into a 12x12 cm2 printer head matrix with a total of 57,600 nozzles. They subjected it to several tests to confirm proper ink flow within the system.

This design, which the researchers dub JeTrix, has many potential applications. Says Einat, ?The future applications of JeTrix will be traditional, such as extremely high-speed printers for industry, offices, and homes. But we also anticipate brand-new, pioneering applications. One example is in-store book printing ? where the book is printed instantly for the customer. This could enable small bookshops or even airport kiosks to carry a huge variety of books. There's also personalization ? newspapers or journals printed with a customer's name, favorite topics, and suitable advertisements.?

He continues, ?The JeTrix project is still in an early stage. The concept was proofed in a laboratory prototype, but we expect that a commercial product will be ready after two years of development, which will include additional funding and product engineering.?

Source

not possible. thats approximately 16.67 pages a second, and there is no paper feeding technology or rollers that can operate at the required RPM without massive weardown after 30 seconds without overheating the rollers themselves.

and imagine how the paper will fllllllllllly..... :shifty:

not possible. thats approximately 16.67 pages a second, and there is no paper feeding technology or rollers that can operate at the required RPM without massive weardown after 30 seconds without overheating the rollers themselves.

The key word here is "have designed", surely you read the article tho? :pinch:

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • If you actually used it instead of responding like a petulant child you might be surprised. I switched from Google some time ago and have been very satisfied.
    • I am one of the first people to use the DXVK technology. In the channel below you can see some videos that I have made using this technology, including Assassin's Creed Odyssey. https://www.youtube.com/@nahum7995/videos Assassin's Creed Odyssey experienced several bugs and technical issues during its first months after release. It launched with its own fair share of funny but frustrating glitches. I ran it on DXVK 9 days after its release and I played it for many hours but didn't see a single significant bug on Linux. Assassin's Creed Odyssey is widely celebrated for pushing the franchise in bold new directions and specifically for nailing several elements better than any other title in the AC series: Player Choice & Branching Narrative, The Mercenary & Cultist System, Mythological Integration, Overpowered Combat Abilities, Open World Exploration But what I'm trying to point out is that this game wasn't quite playable on most windows systems, until a few months after its release when most of the bugs were fixed. However, on Linux it ran completely flawless from day one, although DXVK had seen little development and refinement at the time. What do you think the situation will be in 2026 now that most bugs and glitches of DXVK have been completely eliminated? This is information from Google about these situations that I am quoting. In many cases, using DXVK (a translation layer that converts DirectX 9, 10, or 11 into Vulkan) can result in more stable frame times and higher performance than native Windows rendering. This happens primarily by bypassing driver overhead and multithreading draw calls that were previously restricted to a single CPU core. Older APIs (like DirectX 9 and 11) are largely single-threaded on the CPU side. DXVK translates these calls to Vulkan, which is highly multi-threaded. This reduces CPU-bound stuttering on weaker processors. In certain cases, GPU manufacturers (especially AMD) have significantly better and more modern Vulkan drivers than they do for legacy DirectX. Vulkan gives developers—and in this case, the translation layer—closer control over how resources are held in VRAM. This can prevent micro-stutters and sudden frame drops during chaotic gameplay. Yes, certain games, particularly older DirectX 9 to 11 titles, can run with fewer crashes on DXVK than on native Windows. By intercepting DirectX draw calls and translating them into the modern, highly efficient Vulkan API, DXVK bypasses the limitations and poor driver support that cause instability in aging game engines. PlayStation 1, PlayStation 2 and PlayStation 3 can be easily and perfectly emulated on Linux. In fact, modern Linux emulators offer high-performance upscaling, widescreen patches, and automatic controller mapping out of the box.                                                                                                                                                                                                                                                                                                                                 PlayStation 1/2/3 games look drastically better on Linux thanks to resolution upscaling. Furthermore, it is also a fact that you cannot play many fun games on Windows either, isn't it? - The Nintendo Switch has an extensive library of exclusive games. - PlayStation has an extensive library of exclusive games - Android has "mobile-exclusive" games, meaning they are exclusive to mobile devices (iOS and Android) and aren't available on PC or consoles. And finally, it is also the case that in the next five years there will be games that millions of people will say you absolutely must play and that they want to play this specific game that released a few days ago. However, the other side of this story is that currently, absolutely no one cares that they cannot play these upcoming games right now.
    • Flameshot 14.0 RC3 by Razvan Serea Flameshot is a free and open-source, cross-platform tool to take screenshots with many built-in features to save you time. Using Flameshot is as simple as launching, dragging the selection box to cover the area you want to capture, making annotations as needed in on-screen and saving the shot to your computer, all with a very simple and straightforward interface. Flameshot allows users to simply upload their screenshots directly to the cloud in order to easily share it with others. You can upload your image directly to Imgur with a single click and share the URL with others. In-app screenshot editing - You can choose to add an arrow mark, highlight text, blur a section (blur or pixelate an area), add a text, draw something, add a rectangular/circular shaped border, add an incrementing counter number, and add a solid color box with Flameshot's built-in editing tools. Command-line interface (CLI) - Flameshot has several commands you can use in the terminal without launching the GUI via a command line interface. The command line interface lets you script Flameshot and use it as the subject of key binds. Flameshot 14.0 RC3 changelog: Translations update from Hosted Weblate by @weblate in #4612 Translations update from Hosted Weblate by @weblate in #4619 Fix pin position on Windows for scaled screen by @ElTh0r0 in #4614 Cmake Analyzers by @ElTh0r0 in #4613 Translations update from Hosted Weblate by @weblate in #4632 fix(macos): prevent config tab content from rendering behind tab bar by @Mitnitsky in #4627 fix(macos): use CGRequestScreenCaptureAccess instead of grabWindow for permission request by @Mitnitsky in #4617 Fix KDE Plasma keyboard shortcut config file by @ElTh0r0 in #4637 fix(macos): fix clipboard copy failing from tray and GUI by @Mitnitsky in #4629 feature(macos): show dock icon when config window is open by @Mitnitsky in #4628 Option to disable tray icon on Windows by @ElTh0r0 in #4634 Translations update from Hosted Weblate by @weblate in #4642 fix(macos): make fullscreen capture overlay configurable by @Mitnitsky in #4622 Update GH actions using Node.js 24 by @ElTh0r0 in #4660 fix issue with screen selection in non interactive mode by @borgmanJeremy in #4667 Uniformize both spec files + ninja build openSUSE by @QuentiumYT in #4658 screengrabber: pass non-empty parent_window to xdg-desktop-portal by @artefaktor93 in #4664 Allow multiple flameshot GUI instances (fix for #3177) by @ElTh0r0 in #4680 Unify Linux ARM CI into Linux CI (also drop QEMU) by @theofficialgman in #4702 respect system proxy settings by @borgmanJeremy in #4674 Replace ifdef LINUX with UNIX to include BSD systems by @ElTh0r0 in #4700 Download: Flameshot 14.0 RC3 | 18.1 MB (Open Source) Download: Flameshot Portable | 53.0 MB Links: Flameshot Home Page | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • I found that stability back then was really down to the motherboard manufacturer. Back then i stuck with Microstar motherboards and VIA chipsets as they were ultra reliable. Most stuff was done with jumpers and left little room for user created problems 👍
  • Recent Achievements

    • One Month Later
      nothanks earned a badge
      One Month Later
    • One Month Later
      B2Proxy earned a badge
      One Month Later
    • One Year In
      MadMung0 earned a badge
      One Year In
    • Week One Done
      jefred earned a badge
      Week One Done
    • Apprentice
      JoeyNeo went up a rank
      Apprentice
  • Popular Contributors

    1. 1
      +primortal
      490
    2. 2
      PsYcHoKiLLa
      232
    3. 3
      Skyfrog
      78
    4. 4
      FloatingFatMan
      68
    5. 5
      Michael Scrip
      58
  • Tell a friend

    Love Neowin? Tell a friend!