[sane-devel] HP officejet: access scanner over the network

[gobo]

i think i see what he is asking for and the answer may not be known here.

as we know, the command i gave earlier uses the sane supplied command
line front end.  he substituted his model and ip address for mine and
it works.  however, the xsane front end does not know about the
scanner.  kooka, which suse installs by default and is what is on my
box, does not know about a network scanner either.

as pointed out earlier, he does not need saned in this instance.

xsane (and kooka) are not part of this project.  however, in case
anyone here knows the answer - how does one define a network connected
scanner to the xsane/kooka front ends?  i'm guessing it is set up by
udev, but sometimes those rules need some extra help.



On Tue, Jan 6, 2009 at 8:14 PM, Wouter van Marle
<wouter at squirrel-systems.com> wrote:
> Allan,
>
> The scanning part (hpaio) is working fine - there is no problem on that
> side.
>
> The problem is on the SANE side: how to install this command within SANE
> so I can access this scanner through xsane and saned. This is why I'm
> asking here again.
>
> Maybe I have to add something in the /etc/sane.d config dir? I don't
> know how saned finds it's scanners!
>
> Wouter
>
> On Tue, 2009-01-06 at 20:40 -0500, m. allan noah wrote:
>> maybe ask the guys that make the hpaio backend? it is part of the hplip project.
>>
>> allan
>>
>> On Tue, Jan 6, 2009 at 7:56 PM, Wouter van Marle
>> <wouter at squirrel-systems.com> wrote:
>> > Has anyone an idea on this issue?
>> >
>> > On Tue, 2008-12-30 at 10:17 -0600, gobo wrote:
>> >> you need to have hplip installed.  with hplip you can then use hpaio
>> >> to access the scanner across the network.  for example:
>> >>
>> >> scanimage -x 215.9 -y 297 -d
>> >> hpaio:/net/Officejet_J6400_series?ip=192.168.2.103 -pv --mode gray >
>> >> $FILE
>> >
>> > OK that part works after substituting my scanner name and ip of course.
>> > So the scanner can be addressed, and is scanning properly.
>> >
>> > But this is not the way I like to do my scanning of course, it's nice
>> > for testing and all. How can I integrate this into a saned server or
>> > whatever, so I can use xsane or another sane compliant software in the
>> > network to access this scanner?
>> >
>> > Previously the HP was connected to the server over USB, and the rest of
>> > the workstations could very easily access the scanner through the saned
>> > interfaces. The workstations are on Mandriva Linux by the way, and could
>> > easily add this scanner through the control panel. Just give the ip of
>> > the server, and the scanner was detected automatically.
>> >
>> > Wouter.
>> >
>> >>
>> >>
>> >>
>> >> On Tue, Dec 30, 2008 at 7:45 AM, Wouter van Marle
>> >> <wouter at squirrel-systems.com> wrote:
>> >>> Hi all,
>> >>>
>> >>> I am the happy owner of an HP Officejet Pro L7560 (an all-in-one
>> >>> device).
>> >>>
>> >>> Until recently I had this connected to my server through USB, and
>> >>> printing and scanning all worked fine. Of course using sane on the
>> >>> server to access the scanner from the workstations.
>> >>>
>> >>> Now I have a new office, all is rearranged, and the Officejet is
>> >>> connected directly to the network. It gets it's IP from the server by
>> >>> DHCP, which I configured to be fixed, so far so good. Printing (though
>> >>> Cups) works like a charm after some googling to get the correct way to
>> >>> address the printer, but now scanning! How can I do this? A couple of
>> >>> hours searching Google didn't give me a single clue... the scanner is
>> >>> not found automatically by Sane, and no idea on how to address it.
>> >>>
>> >>> I'm looking for one of two solutions:
>> >>> 1) server is talking to the scanner one way or another, and then
>> >>> shares
>> >>> the scanner with the workstations through the existing Sane interface.
>> >>> 2) the workstations (three only, it's a small network) talk to the
>> >>> scanner directly (they are all on the same 192.168.2.0/24 subnet) (if
>> >>> easy/automatically to configure on the workstations).
>> >>>
>> >>> Wouter.
>> >>>
>> >>>
>> >>> --
>> >>> sane-devel mailing list: sane-devel at lists.alioth.debian.org
>> >>> http://lists.alioth.debian.org/mailman/listinfo/sane-devel
>> >>> Unsubscribe: Send mail with subject "unsubscribe your_password"
>> >>>             to sane-devel-request at lists.alioth.debian.org
>> >>>
>> >>
>> >>
>> >
>> >
>> > --
>> > sane-devel mailing list: sane-devel at lists.alioth.debian.org
>> > http://lists.alioth.debian.org/mailman/listinfo/sane-devel
>> > Unsubscribe: Send mail with subject "unsubscribe your_password"
>> >              to sane-devel-request at lists.alioth.debian.org
>> >
>> >
>> >
>> > --
>> > sane-devel mailing list: sane-devel at lists.alioth.debian.org
>> > http://lists.alioth.debian.org/mailman/listinfo/sane-devel
>> > Unsubscribe: Send mail with subject "unsubscribe your_password"
>> >             to sane-devel-request at lists.alioth.debian.org
>> >
>>
>>
>>
>
>
> --
> sane-devel mailing list: sane-devel at lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/sane-devel
> Unsubscribe: Send mail with subject "unsubscribe your_password"
>             to sane-devel-request at lists.alioth.debian.org
>