Epson 4990 - API

[Wojtek]

I'm trying to find API specification for new Epson 4990 scanner.
Google found nothing. There is also no information
at www.epsondevelopers.com website about this scanner.
Does it use ESC\I command set?
I will be gratefull for any information.
Wojciech Kowalczyk

 

[Don]

I'm trying to find API specification for new Epson 4990 scanner.
Google found nothing. There is also no information
at www.epsondevelopers.com website about this scanner.
Does it use ESC\I command set?
I will be gratefull for any information.
Wojciech Kowalczyk

Does that mean the scanner is no longer being made? (I'm not familiar
with the Epson line.)

You're unlikely to find a lot of information on the Net simply because
such information is usually restricted and only people who have an SDK
(software developer kit) would have access to it. However, they also
had to sign an NDA (non-disclosure agreement) preventing them from
revealing it publicly.

There may be some information from people who reverse-engineered the
calls, but your best bet would be to try writing to Epson and asking
for an SDK.

Don.

 

[Dances With Crows]

You could try it and see if you have an Epson 4990 sitting around. Why
do you need the specs, anyway? Epson is usually pretty good about
getting info to the SANE developers according to
http://sane-project.org/ , so if sane-epson or sane-snapscan or
sane-epkowa doesn't support the scanner, the next release of any of
those backends typically will.

Does that mean the scanner is no longer being made?

"New Epson 4990 scanner" doesn't suggest "no longer being made".

You're unlikely to find a lot of information on the Net simply because
such information is usually restricted and only people who have an SDK
(software developer kit) would have access to it. However, they also
had to sign an NDA (non-disclosure agreement) preventing them from
revealing it publicly.

Unlike most scanner manufacturers, Epson has historically given out
enough info for the open source community to develop SANE backends for
many of the Epson scanners. Since there's no common scanner protocol
(for hysterical raisins), this means Epson scanners are usually more
"future proof" than other scanners.

There may be some information from people who reverse-engineered the
calls, but your best bet would be to try writing to Epson and asking
for an SDK.

Try the SANE developers first, then try writing to Epson. Not all SDKs
are created equal; if Wojtek wants to write a scanner backend for
OpenBSD, a Windows SDK will not help nearly as much as a complete
description of the scanner's protocol. Then again, if the scanner came
with 'Doze kernel modules, Wojtek has 'Doze available, and the scanner
is USB, USBSnoopy or its derivatives could help a lot with figuring out
the protocol this scanner uses.

 

[Don]

You could try it and see if you have an Epson 4990 sitting around. Why
do you need the specs, anyway? Epson is usually pretty good about
getting info to the SANE developers according to
http://sane-project.org/ , so if sane-epson or sane-snapscan or
sane-epkowa doesn't support the scanner, the next release of any of
those backends typically will.

That's a good point! Depending on the requirements, SANE may be a good
source.

"New Epson 4990 scanner" doesn't suggest "no longer being made".

New is a relative term. Companies don't always simultaneously release
a product worldwide. "New" for some is "old hat" for others. It
wouldn't be the first time that a product discontinued in one market
is being dumped in another as "new".

The fact is, he couldn't find it on the web site.

Try the SANE developers first, then try writing to Epson. Not all SDKs
are created equal; if Wojtek wants to write a scanner backend for
OpenBSD, a Windows SDK will not help nearly as much as a complete
description of the scanner's protocol. Then again, if the scanner came
with 'Doze kernel modules, Wojtek has 'Doze available, and the scanner
is USB, USBSnoopy or its derivatives could help a lot with figuring out
the protocol this scanner uses.

His question appears to suggest he's on a Windows machine ("API
specs"). If that is the case, he probably wants to know how to talk to
the TWAIN driver. That's of little use to *nix users who only care
about the low level interface. On the other hand he does mention ESC/I
so maybe he is after a low level interface...

We'll have to wait to find out... ;o)

Don.