Free epson inkjet software for linux

Epson Photo Ink Levels uses the escputil program to access Epson printers.

Ive set it up for newer Epson photo printers as that suits my needs, but its a Kommander dialog so you can easily edit it for your needs.

It does allow you to set up the device using a dialog. I hope you find it useful.

GMSO measures ink levels of HP ve Epson inkjet printers. You can get a list of compatible printers from http://libinklevel.sourceforge.net.

If it works with a printer not in the list please contact me. Besides the ones in the list it worked with my printer (HP Deskjet 3550).

AcuLaser C900 CUPS backend provides a LINUX CUPS package (incl. PPD-file) for the EPSON AcuLaser C900.
It is built around the avasys pipsplus driver. The project supports i386 and 32-bit compatible x86_64 LINUX systems (deb/rpm/tgz/gentoo/slack)
There are positive feedbacks for:
- SuSE
- Mandriva
- Slackware
- Red Hat
- Fedora Core
- Debian, Ubuntu
- Gentoo
The included installer will:
- Check for missing packages
- download and install the mandatory epkowa packages automatically
- provide a dummy lpr-package to resolve dependencies
- account for the different Ditros (BSD - System V - Gentoo) and configure the run-levels accordingly
- give suggestions for appropriate URIs for the printer installation
- call the distribution specific CUPS tools (YaST2, printerdrake, kprinter, gnome-cups-config)
Main features:
- Bundling of pages (large documents sometimes "hang")
- generic multiple local printer support
- URI handling for proper interface (usblp) allocation
- installation of XML files for plain foomatic support
- better hotplugging behavior
- networking (IPP, SMB) support through a local pseudo-interface
Enhancements:
- The regular print mode will be selected with every reboot or runlevel change.

CUPS provides a portable printing layer for Unix(r)-based operating systems. Common UNIX Printing System has been developed to promote a standard printing solution for all Unix vendors and users.

CUPS provides the System V and Berkeley command line interfaces, and uses the Internet Printing Protocol ("IPP") as the basis for managing print jobs and queues. The Line Printer Daemon (LPD) Server Message Block (SMB), and AppSocket (a.k.a. JetDirect) protocols are also supported with reduced functionality.

CUPS adds network printer browsing and PostScript Printer Description ("PPD") based printing options to support real world printing under UNIX. It includes an image file RIP that supports printing of image files to non-PostScript printers.

A customized version of GNU Ghostscript 7.05 for CUPS called ESP Ghostscript is available separately to support printing of PostScript files within the CUPS driver framework. Sample drivers for Dymo, EPSON, HP, and OKIDATA printers are included that use these filters.

Image::ExifTool is a Perl module that can read and write meta information.

SYNOPSIS

use Image::ExifTool ImageInfo;

# ---- Simple procedural usage ----

# Get hash of meta information tag names/values from an image
$info = ImageInfo(a.jpg);

# ---- Object-oriented usage ----

# Create a new Image::ExifTool object
$exifTool = new Image::ExifTool;

# Extract meta information from an image
$exifTool->ExtractInfo($file, %options);

# Get list of tags in the order they were found in the file
@tagList = $exifTool->GetFoundTags(File);

# Get the value of a specified tag
$value = $exifTool->GetValue($tag, $type);

# Get a tag description
$description = $exifTool->GetDescription($tag);

# Get the group name associated with this tag
$group = $exifTool->GetGroup($tag, $family);

# Set a new value for a tag
$exifTool->SetNewValue($tag, $newValue);

# Write new meta information to a file
$success = $exifTool->WriteInfo($srcfile, $dstfile);

# ...plus a host of other useful methods...

ExifTool provides an extensible set of perl modules to read and write meta information in image, audio and video files, including the maker note information of many digital cameras by various manufacturers such as Canon, Casio, FujiFilm, JVC/Victor, Kodak, Leaf, Minolta/Konica-Minolta, Nikon, Olympus/Epson, Panasonic/Leica, Pentax/Asahi, Ricoh, Sanyo and Sigma/Foveon.

foo2qpdl is a Linux printer driver for QPDL protocol.
foo2qpdl is an open source printer driver for printers that use the QPDL wire protocol for their print data, such as the Samsung CLP-300 or the Samsung CLP-600. These printers are often erroneously referred to as winprinters or GDI printers. However, Microsoft GDI only mandates the API between an application and the printer driver, not the protocol on the wire between the printer driver and the printer. In fact, QPDL printers are raster printers which happen to use a very efficient wire protocol. QPDL is just one of many wire protocols that are in use today, such as Postscript, PCL, Epson, ZjStream, etc.
This driver uses Ghostscript to perform all of the heavy lifting (image processing). There are five major components to the foo2qpdl printer driver.
- foo2qpdl - the page image to protocol conversion engine of the driver.
- foo2qpdl-wrapper - a shell script (compatible with foomatic) which runs ghostscript and foo2qpdl in a pipeline.
- icc2ps - converts an ICM color profile to a Postscript CRD, which is then fed into Ghostscript before the users Postscript program.
- foomatic-db - foomatic database entries which describe the supported printers and their options so that printer spoolers know how to access the printer using foo2qpdl-wrapper.
- qpdldecode - a tool for developers to inspect QPDL streams.
Installation:
Click the link, or cut and paste the whole command line below to download the driver.
$ wget -O foo2zjs.tar.gz http://foo2zjs.rkkda.com/foo2zjs.tar.gz
Now unpack it:
Unpack:
$ tar zxf foo2zjs.tar.gz
$ cd foo2zjs
Now compile and install it. The INSTALL file contains more detailed instructions; please read it now.
Compile:
$ make
Install driver, foomatic XML files, and extra files:
$ su OR $ sudo make install
# make install
(Optional) If you use CUPS, restart the spooler:
# make cups OR $ sudo make cups
Now create printer entries for your spooler. Create at least one queue for monochrome, and another queue for color printing. Create the queues first, then edit them and set the device options as desired. See your operating system documentation for further details on creating a printer queue. Click any hyperlinks below for sample screenshots.
For Redhat 7.2/7.3/8.0/9.0 and Fedora Core 1-5 users:
# printconf-gui
For Fedora Core 6 users:
# system-config-printer
For Mandrake/Manrivia users:
# printerdrake
For Suse 10.0 users:
# yast2 printer
For Ubuntu 5.10/6.06/6.10 users:
$ sudo gnome-cups-manager
$ sudo make cups
For a networked Konica Minolta magicolor 2530 DL, I used a "Queue Type" "HP JetDirect" and set "Host:" to the IP address of the printer and "Port:" to 9100.
For low level testing, you can also create a "raw queue", which will accept QPDL files as-is and send them directly to the printer.
Enhancements:
- Samsung CLP-300, Samsung CLP-600, and Samsung CLX-3160 printers are supported.
- Only JBIG (type 0x13) compression is implemented and it is alpha quality.

Image::MetaData::JPEG::MakerNotes contains random information and details on MakerNotes.

Pieces of information available after parsing the MakerNote

The result of the process of parsing the maker note is stored in a directory in the internal data structure for the APP1 Segment, whose path is "IFD@SubIFD@MakerNoteData_$format", where $format is the specific note format; the MakerNote entry in IFD0@SubIFD is then removed. This translation happens always, because there is a catch-all unknown rule for a binary makernote with very broad acceptance rules. The maker note directory contains, in addition, a special subdir with some fields reporting about the parsing process.

key content
-------- -------
ORIGINAL the raw content of the maker note (unparsed)
SIGNATURE the first few bytes which allowed the format to be chosen
ENDIANNESS the byte order chosen during parsing
FORMAT the maker note format chosen during parsing
ERROR [optional] error details, in case of failure while parsing

Supported MakerNote formats

Maker note formats are specified in a special internal hash, with a key for each format (including the unknown format). Each format entry corresponds to an anonymous hash containing information for parsing the MakerNote; the "normal" format is considered to be an IFD-like MakerNote with a next_link pointer, offsets counted from the global TIFF header and no MakerNote internal TIFF header.

key meaning or effect
--------- -----------------
signature the MakerNote signature (a regular expression)
maker the Maker signature (i.e., its name, no regex)
tags a reference to a hash for tag translations
(A) mkntstart if set, offsets are counted from the maker note start
(B) mkntTIFF if set, offsets are counted from the internal TIFF header
(C) ignore if set, the format is to be ignored
(D) nonext if set, the maker note IFD does not have a next_link
(E) endianness if set, the byte order is fixed to this value
(F) nonIFD if set, the maker note is not IFD-like

Currently, "supported" formats are described in the following table; authoritative data is indeed kept in Tables_makernotes.pl, to which the reader should refer for tag definitions and translations. Remember that both the signature and the maker fields are regular expressions matching at the beginning (the real signature corresponds to $1).

A B C D E F Maker Signature
----------- --------- -----------------
Agfa AGFA (AGFA 00 01)
Canon Canon ()
Casio_1 CASIO ()[^Q]
Casio_2 CASIO (QVC 00{3})
Epson EPSON (EPSON 00 01 00)
Foveon FOVEON (FOVEON 00{2} 01 00)
Fujifilm x FUJIFILM (FUJIFILM 14 00{3})
HPackard x Hewlett-Packard (HP)
Kyocera x x KYOCERA (KYOCERA {12} 00{3})
Kodak B x KODAK (KDK INFO[a-zA-Z0-9]* )
Minolta_1 MINOLTA ().{10}MLT0
Minolta_2 Minolta ().{10}MLT0
Konica x Minolta|KONICA ((MLY|KC|(+M){4})| 01 00{5} 04)
Nikon_1 NIKON (Nikon 00 01 00)
Nikon_2 NIKON ()[^N]
Nikon_3 x NIKON (Nikon 00 02[ 20 00] 00{2})
Olympus OLYMPUS (OLYMP 00[ 01 02] 00)
Panasonic_1 x Panasonic (Panasonic 00{3})
Panasonic_2 x x Panasonic (MKED)
Pentax_1 x Asahi ()[^A]
Pentax_2 x x Asahi (AOC 00..)
Ricoh_1 x RICOH (Rv|Rev)
Ricoh_2 x RICOH ( 00)
Ricoh_3 RICOH ((Ricoh|RICOH) 00{3})
Sanyo SANYO (SANYO 00 01 00)
Sigma SIGMA (SIGMA 00{3} 01 00)
Sony x SONY (SONY (CAM|DSC) 00{3})
Toshiba x TOSHIBA ()
unknown x . ()

References

MakerNote format details are not usually released by vendors (well, this is an euphemism: no vendor ever, to my knowledge, released any detail on its format, exception made for Sigma/Foveon). All information used for this package was collected on the Internet (and its reliability is therefore limited) or through personal tests. Some interesting sites are (not an exhaustive list at all):

General: home.arcor.de/ahuggel/exiv2/makernote.html
.....: www.ozhiker.com/electronics/pjmt/jpeg_info/makernotes.html

Agfa: www.ozhiker.com/electronics/pjmt/jpeg_info/agfa_mn.html
Canon: www.burren.cx/david/canon.html
Casio: park2.wakwak.com/~tsuruzoh/Computer/Digicams/exif-e.html
...: www.dicasoft.de/casiomn.htm
Epson: www.ozhiker.com/electronics/pjmt/jpeg_info/epson_mn.html
Foveon: Foveon is the same as Sigma, see Sigma
Fujifilm: park2.wakwak.com/~tsuruzoh/Computer/Digicams/exif-e.html
......: www.ozhiker.com/electronics/pjmt/jpeg_info/fujifilm_mn.html
Kyocera: www.ozhiker.com/electronics/pjmt/jpeg_info/kyocera_mn.html
Kodak: my personal tests with my Kodak DX3900 (not IFD-like)
Minolta: www.dalibor.cz/minolta/makernote.htm
.....: www.ozhiker.com/electronics/pjmt/jpeg_info/minolta_mn.html
Nikon: park2.wakwak.com/~tsuruzoh/Computer/Digicams/exif-e.html
...: www.tawbaware.com/990exif.htm
...: www.ozhiker.com/electronics/pjmt/jpeg_info/nikon_mn.html
Olympus: park2.wakwak.com/~tsuruzoh/Computer/Digicams/exif-e.html
.....: www.ozhiker.com/electronics/pjmt/jpeg_info/olympus_mn.html
Panasonic: www.compton.nu/panasonic.html
Pentax: www.ozhiker.com/electronics/pjmt/jpeg_info/pentax_mn.html
Ricoh: www.ozhiker.com/electronics/pjmt/jpeg_info/ricoh_mn.html
Sanyo: www.exif.org/makernotes/SanyoMakerNote.html
Sigma: www.x3f.info/technotes/FileDocs/MakerNoteDoc.html
Sony: www.ozhiker.com/electronics/pjmt/jpeg_info/sony_mn.html

DX3900 MakerNote format

Kodak MakerNotes are written in a proprietary binary format, which is not IFD-like. So, there is no way to detect the beginning, end and type of a field; everything here was inferred through a careful comparison of the content of a set of Kodak JPEG files and their shot parameters. Fields seems to be aligned on four bytes boundaries. For the DX3900 model the endianness is always fixed to big endian. The signature regular expression is "^(KDK INFO[a-zA-Z0-9]* )", the maker is KODAK. The meaning of the tags is as follows:

BYTE ??? firmware version? This is always 3
BYTE Compression 1 = normal, 2 = 2160x1440 high compression
BYTE BurstMode 0 = off, 1 = on
BYTE MacroMode 0 = normal, 1 = close-up
SHORT PixelXDimension allowed 2160x1440, 1800x1200,
SHORT PixelYDimension / values: 1536x1024, 1080x720
SHORT Year the year value, with four digits
BYTE Month the month value (in [1,12])
BYTE Day the day value (in [1,31])
BYTE Hour the hour value (in [0,23])
BYTE Minute the minute value (in [0,59])
BYTE Second the second value (in [0,59])
BYTE SubSecond (in 130th of seconds?)
SHORT ??? ???
BYTE ??? ???
BYTE ShutterMode 0 = auto, 32 = manual
BYTE MeteringMode 0 = multi-pattern, 1=centre weight., 2=centre spot
BYTE BurstSequenceIndex index in [1,8], 0 if burst mode off
SHORT FNumber 100 times the Exif F-number
LONG ExposureTime in 10^-5 seconds
SSHORT ExposureBiasValue 1000 times the exposure bias in [-2,+2 step .5]
SHORT ??? ???
LONG ???
LONG ??? is this an estimate of the subject
LONG ??? / distance? If so, it is very rough.
LONG ??? /
BYTE FocusMode 0 = auto, 2 = close, 3 = infinity
BYTE ??? always 2
SHORT ??? ???
SSHORT PanoramaMode 0 = normal, -1 = focus at infinity
SHORT SubjectDistance (x-28)*2.54+7 looks like the distance in cm
BYTE WhiteBalance 0 = normal, 1 = fluor., 2 = tungsten, 3 = daylight
(27 bytes with unknown meaning here)
BYTE FlashMode 0 = auto, 1 = on, 2 = off, 3 = red-eyes
BYTE FlashFired 0 = yes, 1 = no
SHORT ISOSpeedMode the requested speed in {100,200,400} or zero
SHORT ??? ???
SHORT TotalZoomFactor 100 times the zoom factor in [+1,+6 step 0.1]
SHORT DateTimeStampMode 0 = none, [1,6] = the six modes
SHORT ColourMode 1 = black & white, 2 = sepia, 32 = colour
SHORT DigitalZoomFactor 100 times the zoom factor in [+1,+3 step 0.1]
BYTE ??? always zero
SBYTE Sharpness 0 = standard, 1 = sharp, -1 = soft
(808 bytes with unknown meaning here, maybe a thumbnail?)