I have a System76 Darter Pro laptop (darp5) with Pop! OS 22.04. I'm trying to print wirelessly to my Epson Artisan 810 all-in-one printer, which I've been able to do in the past using an earlier version of Pop! OS. The printer settings say that it's connected to the correct network, with excellent signal strength, and it's pingable.
The problem I have is that in spite of being pingable and connected, I can't print anything because my laptop/applications can't find the printer. The OS and applications, (in this case, Libreoffice Calc or Writer) recognize the presence of my Epson printer and it's automatically in the list of printers I can print to, except I can't.
I'm not sure what to check at this point and would surely appreciate any tips and pointers.
Thx!
Related
Well, never mind. I rebooted the system and now the printer is working fine!
I'm a bit embarrassed, in that it's been years since I asked a "simple" Windows question, and I've forgotten where to ask it.
I have my home computer, a Dell laptop running Windows 10. Attached is a Epson ET-3760 printer. Except that the printer is no longer attached. When I try to print the printer isn't found and Windows instead wants to do a print-to-file of one sort or another.
How can I diagnose this? Where should I be asking?
I have several Zebra ZM400 printers connected to the network and am working on customizing our printing application. The program uses the ~HS command to check the status of the printer before printing. Most of the printers work but some of them just hang when I type ~HS I get no response. I've used telnet to access the printer via 9100 and confirmed that it is indeed not working properly. As far as I can tell both printers are configured identically. I'm looking any ideas to help figure out why it is not working on all printers.
Model: Zebra ZM400
Firmware: V53.17.13Z
Stumbled upon the answer the other day. The output port of the print server had to be change to bidirectional communication.
My Bixolon SRP-350II is not shown in the list of available devices given by
posExplorer.GetDevices();
All I see are Microsoft's simulated devices. The printer itself works, I can print on it and, using raw printing, send commands such as "cut". I've installed the OPOS driver for the printer, but nothing changed.
Is it necessary to do some further configuration? Is the order of installing POS.NET, the OPOS-driver and the Windows driver important?
Alright, figured out the Printer had to be configured with PSPLauncher.exe and now it shows up. Still, I am not sure I understand where exactly the benefit of POS .NET lies. I want the customers to plug-in new printers and when using Raw Printing and EscPos-commands, this seems to be much easier.
Plug printer in, install windows driver, set to main printer and then cut-commands etc. are being send in the raw stream.
I can't say directly for printers, but where we get the benefits out of POS.NET is the standard code we wrote for the scanners, or MSRs or cash drawers. All we have to do is install the driver, and configure the device in OPOS configuration (which is probably the step you were missing and resolved with the "PSPLauncher.exe") and we know that it's code-compatible and just works.
We have hundreds of terminals across the country (Australia) and they all use a variety of models and brands for the devices (within a range of tolerance) but because of POS.NET they're all supported.
I'm trying to get a very old, but working great C2001A/J4100A (HP LaserJet 4) to work with the HP Linux Imaging and Printing library, but I'm having an awful time of it.
1) There's no entry in /usr/share/hplip/data/models/models.dat for [hp_laserjet_4]. This is the first problem so far when I used Bonjour discovery through an avahi.service file I put on my OpenWRT router. I don't currently have an iPhone I want it to discover with AirPrint, but this is how I started off and helps CUPS finds printers anyways.
2) SLP discovery is a complete bomb. I've traced it down to the UDP packet the JetDirect sends off in response to the broadcast discovery request. The part that is 'x-hp-p1=0' should be something like 'x-hp-p1=MFG:HP;MDL:LaserJet4;etc..' and it causes hp-probe to fail to see what printer the JetDirect is plugged into.
I can't seem to force HPLIP to bypass the bad discovery methods and it's too smart and wants to verify.
I've posted to the HPLIP help area, but they seem to run a week slow.
Instead of doing JetDirect, try LPR directly to the IP address. And any of the older PCL drivers should work against that printer.
I'm developing a virtual printer to accept print jobs and route them to real printers in a LAN. I'm hoping to create a postscript printer to act as a shared virtual printer to accept print jobs from the LAN, I hope to develop it through ghostscript and redmon.
If you can please let me know any online resources, examples or any tutorials on hows to create a postscript printer on windows 7.
Thank you very much, please let me know if you know anything.
It will be easier to use an existing PostScript printer driver (such as a generic one provided with Windows), and then instead create a port monitor. You will need to use the Windows Driver Development Kit (freely available) in order to create a port monitor. Once you have created your port monitor, you can install a printer using any driver, but tell it to communicate via a port that your monitor will intercept.
You will end up getting the exact data that would have been sent directly to the printer had it been configured to use an IP or other port instead of your port. For example, you can create a port called “ZERONE:” which is monitored by a port monitor called “Zerone Port Monitor”.
MSDN has a sample for a port monitor that interacts with infrared devices, although it will give you an idea on what you need to do so that you can communicate with other devices on a network.
Alternatively, and perhaps more hackishly, you can create a port called “C:\doc.prn”, and any document that is printed will be saved as PostScript to “C:\doc.prn” (provided that the printer driver is a PostScript driver).