Scanning from network connected Kycera Ecosys M5526cdw error

Budgie2 · September 25, 2024, 8:14pm

I am running TW on HP-Z640-1 workstation which is on my subnet and am trying to scan from the captioned printer which is in a different subnet but all within our network.
I have had no problems setting up and using the printer but so far I have not been able to scan. I have the Kyocera-sane driver installed and have been trying to use simple-scan for scanning. Simple-scan can see the device and I can access the limited settings in simple-scan but these have not made any difference.
Testing gives me:-

scanimage -L
device `airscan:e0:Kyocera ECOSYS M5526cdw' is a eSCL Kyocera ECOSYS M5526cdw ip=192.168.105.20

but there is an error in the communication between the machines:-

scanimage --format=png > test-scan.png
scanimage: open of device airscan:e0:Kyocera ECOSYS M5526cdw failed: Error during device I/O

using debug I have:-

alastair@HP-Z640-1:~> export SANE_DEBUG_AIRSCAN=255
alastair@HP-Z640-1:~> scanimage --format=png > test-scan.png
API: sane_init(): called
loading configuration file /etc/sane.d/airscan.conf
MDNS: AVAHI_CLIENT_S_RUNNING
WSDD: netif addresses update:
WSDD:  + 192.168.169.137@eno1, ifindex=2
WSDD:  + 192.168.169.184@br0, ifindex=4
WSDD: 192.168.169.137: started discovery, UDP port=47109
WSDD: 192.168.169.184: started discovery, UDP port=59789
API: sane_get_devices(): called
zeroconf: zeroconf_device_list_get: requested
zeroconf: device_list wait: requested
zeroconf: device_list wait: DNS-SD not finished...
MDNS: browse-ipv6@*("_ipp._tcp"): AVAHI_BROWSER_CACHE_EXHAUSTED
MDNS: browse-ipv6@*("_ipps._tcp"): AVAHI_BROWSER_CACHE_EXHAUSTED
MDNS: browse-ipv6@*("_uscan._tcp"): AVAHI_BROWSER_CACHE_EXHAUSTED
MDNS: browse-ipv6@*("_uscans._tcp"): AVAHI_BROWSER_CACHE_EXHAUSTED
MDNS: browse-ipv6@*("_scanner._tcp"): AVAHI_BROWSER_CACHE_EXHAUSTED
MDNS: browse-ipv6@*("_ipp._tcp"): AVAHI_BROWSER_ALL_FOR_NOW
MDNS: browse-ipv6@*("_ipps._tcp"): AVAHI_BROWSER_ALL_FOR_NOW
MDNS: browse-ipv6@*("_uscan._tcp"): AVAHI_BROWSER_ALL_FOR_NOW
zeroconf: ZEROCONF_USCAN_TCP: initial scan finished
MDNS: browse-ipv6@*("_uscans._tcp"): AVAHI_BROWSER_ALL_FOR_NOW
zeroconf: ZEROCONF_USCANS_TCP: initial scan finished
zeroconf: device_list wait: DNS-SD not finished...
MDNS: browse-ipv6@*("_scanner._tcp"): AVAHI_BROWSER_ALL_FOR_NOW
zeroconf: ZEROCONF_MDNS_HINT: initial scan finished
zeroconf: device_list wait: OK
zeroconf: zeroconf_device_list_get: building list of devices
zeroconf: zeroconf_device_list_get: resulting list:
zeroconf:   eSCL  "e0:Kyocera ECOSYS M5526cdw"
API: sane_get_devices(): done
API: sane_open("e0:Kyocera ECOSYS M5526cdw"): called
zeroconf: device_list wait: requested
zeroconf: device_list wait: OK
Kyocera ECOSYS M5526cdw: device created
Kyocera ECOSYS M5526cdw: added image decoder: "jpeg"
Kyocera ECOSYS M5526cdw: added image decoder: "tiff"
Kyocera ECOSYS M5526cdw: added image decoder: "png"
Kyocera ECOSYS M5526cdw: added image decoder: "bmp"
Kyocera ECOSYS M5526cdw: DEVICE_STM_OPENED->DEVICE_STM_PROBING
Kyocera ECOSYS M5526cdw: using protocol "eSCL"
Kyocera ECOSYS M5526cdw: HTTP GET http://192.168.105.20/ScannerCapabilities
Kyocera ECOSYS M5526cdw: HTTP using timeout: 5000 ms
Kyocera ECOSYS M5526cdw: HTTP resolving 192.168.105.20 80
Kyocera ECOSYS M5526cdw: HTTP trying 192.168.105.20:80
Kyocera ECOSYS M5526cdw: HTTP fdpoll: {--} -> {-w}
Kyocera ECOSYS M5526cdw: HTTP 78 bytes sent
Kyocera ECOSYS M5526cdw: HTTP done request sending
Kyocera ECOSYS M5526cdw: HTTP fdpoll: {-w} -> {rw}
Kyocera ECOSYS M5526cdw: HTTP fdpoll: {rw} -> {r-}
Kyocera ECOSYS M5526cdw: HTTP 192 bytes received
Kyocera ECOSYS M5526cdw: HTTP GET http://192.168.105.20/ScannerCapabilities: got response headers (500)
Kyocera ECOSYS M5526cdw: HTTP done response reception
Kyocera ECOSYS M5526cdw: HTTP GET http://192.168.105.20/ScannerCapabilities: 500 Internal Server Error
Kyocera ECOSYS M5526cdw: HTTP GET http://192.168.105.20/ScannerCapabilities: Internal Server Error
Kyocera ECOSYS M5526cdw: scanner capabilities query: Internal Server Error
Kyocera ECOSYS M5526cdw: DEVICE_STM_PROBING->DEVICE_STM_PROBING_FAILED
Kyocera ECOSYS M5526cdw: removed from device table
Kyocera ECOSYS M5526cdw: closed protocol "eSCL"
Kyocera ECOSYS M5526cdw: device destroyed
API: sane_open("e0:Kyocera ECOSYS M5526cdw"): Error during device I/O
scanimage: open of device airscan:e0:Kyocera ECOSYS M5526cdw failed: Error during device I/O
API: sane_exit(): called
zeroconf: ZEROCONF_WSD: initial scan finished
API: sane_exit(): OK

I have login access to the printer and have turned off the ssh defaults for the protocol settings as I do not need the secure connection yet but try as I might I cannot get anything to work.
Any help would be much appreciated please!

BTW what is 192.168.169.184 doing there?

marel · September 26, 2024, 5:15am

Based on the output it looks the driver is not happy with the output this command gives. Would be good to give it a try and see what it returns.

deano_ferrari · September 26, 2024, 6:31am

The 192.168.169.X addresses relate to the discovery (Web Services Discovery) protocol that the airscan backend supports. It’s trying the discovery via the en01 and br0 interfaces on your host. Anyway, not relevant to the issue you’re having here.

deano_ferrari · September 26, 2024, 7:04am

You may well need to search/submit a bug report for this.

Budgie2 · September 27, 2024, 10:07am

I am now using Leap 15.6 system and sane-airscan is not available. How should I install it using Yast please?

Budgie2 · September 27, 2024, 10:18am

Similarly I cannot find sane-escl, it seems scanning is a problem still. Can anybody please help?

deano_ferrari · September 28, 2024, 12:17am

The sane-escl backend is included as part sane-backends. Check with
rpm -ql sane-backends | grep escl
You may need to subscribe to the openSUSE graphics repo to access a later SANE version. (No promises that your particular device is supported though.)

deano_ferrari · September 28, 2024, 12:34am

I haven’t needed to use sane-airscan myself, but if you upgrade SANE using the graphics repo, you can install that package as well.

https://download.opensuse.org/repositories/graphics/15.6/

Budgie2 · September 28, 2024, 9:16pm

I have wrestled with sane-airscan for more than a day. I have not been successful.
I have eSCL working but not WSD. I am not sure if it is a bug in the machine firmware but I have the latest drivers from Kycera and this includes their version of sane.
Driving me in-sane comes to mind.
I am now going to try and get saned to work but the yast installation “helper” is little help either.
I shall press on but do you have any thoughts on reverting to saned?

Budgie2 · September 28, 2024, 9:18pm

BTW I had it, I think from TW repo originally and it is the same version
as on the graphics.repo.

deano_ferrari · September 28, 2024, 10:25pm

Yes, it is.

deano_ferrari · September 28, 2024, 11:49pm

The Kyocera drivers are not relevant if you’re trying to use the driverless scanner protocols.

You say you have eSCL working but not WSD. What do you mean by that. Why do you need both? They’re two different protocols for achieving the same purpose. Not all vendors support both.

deano_ferrari · September 28, 2024, 11:50pm

There should be no need to use YaST at all.

deano_ferrari · September 29, 2024, 12:36am

Why you think using saned will help here? AFAIU, that daemon is used to allow remote network clients to access scanner (SANE) devices available on a local host. Do you have a Linux host connected to the scanner via USB?

Budgie2 · September 29, 2024, 8:16am

Hi Dean,
The new Kyocera is connected on the office subnet and I am working on my “private” subnet. The machine is network connected not USB.
I thought saned might be an alternative route because I have had so much difficulty with using eSCL and WSD. For some reason the printer seems to want both. The printer configuration panels are all new to me and it could be that some protocols need to be turned off at the printer which was set up by supplier but of course using Windows.
I had tried YaST as another option as I use it with my HP devices.

I have lost too much time on this and must catch up on work but shall resume when I can. When I have something intelligent to post I shall ask.

deano_ferrari · September 29, 2024, 8:26am

Then saned is not relevant here. It is for connecting two or more hosts so that a scanner connected to one of them can be shared.

With respect to Airscan (using eSCL or WSD protocls), my understanding is that discovery requires being within the same broadcast domain. Maybe that is why you’re having difficulties with this approach.

deano_ferrari · September 29, 2024, 8:36am

I assume that you’ve already reviewed man sane-airscan
but I would go through it again. As the openSUSE host and scanner are connected on different networks, discovery is not an option, but you should still be able to configure /etc/sane.d/airscan.conf with the appropriate entry in the ‘[devices]’ section for your remote network scanner device.

Did you ever have this working? In the end it may just not be a supported device and you’ll have to accept that.

deano_ferrari · September 29, 2024, 8:55am

Referring to your initial post in this thread, you have since moved to using Leap 15.6. You haven’t shared your airscan.conf configuration.

What happens if you invoke
scanimage -d 'escl:http://192.168.105.20:80' > test.pnm
*Assuming port 80 is the right one for this machine. Maybe it is something else?

Budgie2 · September 29, 2024, 9:07am

Hi Dean,
I see that you are on line as you more recent post arrived while I was writing this.
Many concepts to think through here and no I have not digested man air-scan yet.
Broadcast domain is an unfamiliar issue so will read up on this.

I had switched to my TW workstation for trying to get the Kyocera working and have been using that machine so as not to interrupt the office.

I had set up the route in NM and static IPs throughout rather than relying on the dhcp from the UTM. I have configured /etc/sane.d/airscan.conf with every option I could think of including using trace and debug and reviewing many logs but to no avail so far.

Can I resume this later as I am still playing catchup in the office! I will post the results of my tests when I am back at that machine.
Regards,
Alastair

Budgie2 · September 29, 2024, 1:27pm

I have been using:

[devices]
Kyocera eSCL = http://192.168.105.20:9095/eSCL, eSCL
#Kyocera WSD = http://192.168.105.20:5358/WSDScanner, WSD
Kyocera WSD = disable

I have it working now and using simple-scan.
Still a couple of issues, the Kyocera Ecosys goes to sleep very quickly and inserting paper into the ADF does not wake it up.

Once awake it works well and also works with simple-scan.
I think the wakeup issue is something I may need to ask suppliers about as I have not found why putting paper in the ADF does not wake it up. Meanwhile I shall look at timer adjustments.

Thanks for your encouragement. Since eCSL is working I have no need for WSD.
All good for now.