You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Epson ET-2850 works but its DPI settings aren't recognized #95
Hi thank you for developing this project. I want to signal that after querying my printer, I only have a grayed-out 300 DPI setting. However, with AmiAirPrint, I can switch between 360 and 720 DPI. It's not a big deal, as 720 DPI on a 68030 50 MHz is pretty prohibitive.
Hi here it is the full log. I'm not good at reading it but maybe those high resolutions are only for urf or scanning. Have you considered adding support for media-types and scanners? Thank you for your time and help.
Yeah so there was a hard code in for 300 and 600 dpi printers.... the Epson being a 360dpi and 720dpi printer stops them being offered.
We had a hardcode in for 300dpi as some printers don't offer there 300dpi out, but support it - that becomes 300* - so we need some options to match these type of DPI's in the gui. - working on it now
Patch is up in #96, built directly on top of the current slow-Canon PR #94.
The ET-2850 probe was useful here: it reports generic 360/720 DPI, but PWG Raster only 360 and URF RS360, so the fix now keeps those capability lists separate instead of treating every reported resolution as safe for every engine.
For this printer, PWG/Apple Raster should therefore show reported 360 dpi (plus MintPRINT's marked 300 compatibility* option); an engine using the generic printer resolution list can expose 360/720 dpi. I have deliberately not enabled 1440x720 yet because the current driver only represents one DPI value for both axes.
The full host-side make check regression suite passes on the patch. A real ET-2850 test of 360 DPI would be very useful before closing this one.
I will test tomorrow, but I don't understand what my printer actually supports. It reports 360 and 720, but PWG and URF only support 360. For normal printing should I use 300* or 360?
Hi LiskoFINAL, Try the 300* - your printer might except the standard 300dpi - if not 360 would be the recommended one.
there is a canon that's been reported with a simular problem, it only offers 600dpi but works fine with the 300dpi sent to it.
Activity
boingball commentedon Sep 3, 2026
Hi @LiskoFINAL
Thanks for logging the issue. it's really appreciated.
Would it be possible to run the python script https://github.com/boingball/MintPRINT/blob/main/windows_ipp_probe.py
as follows
python windows_ipp_probe.py http://printer-ip:631/ipp/print --alland attach the output of this to the issue.
This should show what your printer is offering and why MintPRINT can't do it yet.
LiskoFINAL commentedon Sep 3, 2026
Hi here it is the full log. I'm not good at reading it but maybe those high resolutions are only for urf or scanning. Have you considered adding support for media-types and scanners? Thank you for your time and help.
ipp-probe.log
boingball commentedon Sep 3, 2026
Yeah so there was a hard code in for 300 and 600 dpi printers.... the Epson being a 360dpi and 720dpi printer stops them being offered.
We had a hardcode in for 300dpi as some printers don't offer there 300dpi out, but support it - that becomes 300* - so we need some options to match these type of DPI's in the gui. - working on it now
boingball commentedon Sep 3, 2026
and I'm working on MintSCAN - it's another repo - nearly at release version (I need to draw an icon and get the installer done etc)
boingball commentedon Sep 3, 2026
Patch is up in #96, built directly on top of the current slow-Canon PR #94.
The ET-2850 probe was useful here: it reports generic 360/720 DPI, but PWG Raster only 360 and URF
RS360, so the fix now keeps those capability lists separate instead of treating every reported resolution as safe for every engine.For this printer, PWG/Apple Raster should therefore show reported 360 dpi (plus MintPRINT's marked 300 compatibility* option); an engine using the generic printer resolution list can expose 360/720 dpi. I have deliberately not enabled 1440x720 yet because the current driver only represents one DPI value for both axes.
The full host-side
make checkregression suite passes on the patch. A real ET-2850 test of 360 DPI would be very useful before closing this one.boingball commentedon Sep 3, 2026
release1.3.0b.zip
Could you test the epson with this version please? 1.3.1 - with PR96 (sorry I named the zip wrong)
Many Thanks
LiskoFINAL commentedon Sep 3, 2026
I will test tomorrow, but I don't understand what my printer actually supports. It reports 360 and 720, but PWG and URF only support 360. For normal printing should I use 300* or 360?
boingball commentedon Sep 3, 2026
Hi LiskoFINAL, Try the 300* - your printer might except the standard 300dpi - if not 360 would be the recommended one.
there is a canon that's been reported with a simular problem, it only offers 600dpi but works fine with the 300dpi sent to it.
Merge pull request #96 from boingball/fix/engine-aware-dpi