Hi,
I have a Canon MF264dw. When I choose the airscan/eSCL from the devices list, the scan works, but at a maximum of 300dpi. If I choose the pixma entry, I can choose the 600 dpi option, but no matter what resolution I choose, I get the error: "Error during device I/O" reported through my front end Skanlite. My scanner is connected via ethernet on my lan.
Here is the output of scanimage -L
device `v4l:/dev/video0' is a Noname Integrated Camera: Integrated C virtual devicedevice `pixma:MF260_Canon58871c' is a CANON Canon i-SENSYS MF260 Series multi-function peripheraldevice `airscan:e0:Canon MF260' is a eSCL Canon MF260 ip=192.168.1.120
My OS is Garuda Linux (Arch basically)
uname -a
Linux Legion5 6.8.7-zen1-1-zen #1 (closed) ZEN SMP PREEMPT_DYNAMIC Wed, 17 Apr 2024 15:20:00 +0000 x86_64 GNU/Linux
Any help is greatly appreciated. Thank you.
Edited
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Child items
...
Show closed items
Linked items
0
Link issues together to show that they're related or that one is blocking others.
Learn more.
—
Reply to this email directly or view it on GitLab.
You're receiving this email because you have been mentioned on gitlab.com. Unsubscribe from this thread · Manage all notifications · Help
@skelband, I don't know what to make of this ticket: this device is supported by sane-pixma and sane-escl.
The user uses sane-airscan, which automatically switches to the WSD protocol.
Either the user uses eSCL with the sane-airscan backend (to be configured) or sane-escl.
Or use sane-pixma.
What I'm trying to get to 600 dpi. It is my understanding from opening a ticket with airscan project that they only support what the device reports as it's capabilities. He told me that often times the full capability of the device isn't reported. For this reason I'd like to use the pixma back end, but it generates an error every time I try to scan. So what I'm wondering is if that error can be addressed so that I can use the pixma back end instead of the airscan back end? I can choose either from the Skanlite software in KDE, it presents both.
Thanks you.
...
On 4/23/24 11:54 AM, ThierryFR (@ThierrtyFR) wrote:
ThierryFR commented:
@skelband, I don't know what to make of this ticket: this device is supported by sane-pixma and sane-escl.
The user uses sane-airscan, which automatically switches to the WSD protocol.
Either the user uses eSCL with the sane-airscan backend (to be configured) or sane-escl.
Or use sane-pixma.
—
Reply to this email directly or view it on GitLab.
You're receiving this email because of your account on gitlab.com. Unsubscribe from this thread · Manage all notifications · Help
Sorry for the late response. Yes the log might tell us something interesting about why we get the error. We might need to get a capture off the network, but let's see what we can get from the log.
No idea why Airscan and eSCL offers such a restricted set of features. Seems lame.
I think when using the pixma back end, the scanner does offer 600 dpi. It's just that no matter what I ask the scanner to do, even just a "preview" results in a communication error.
File: capabilities.log
All options specific to device `escl:https://192.168.1.120:443':
--mode Gray|Color [Gray]
Selects the scan mode (e.g., lineart, monochrome, or color).
--resolution 75|150|300dpi [75]
Sets the resolution of the scanned image.
--source Flatbed|ADF [Flatbed]
Selects the scan source (such as a document-feeder).
-l 0..215.815mm [0]
Top-left x position of scan area.
-t 0..296.926mm [0]
Top-left y position of scan area.
-x 0.0846558..215.9mm [215.9]
Width of scan-area.
-y 0.0846558..297.011mm [297.011]
Height of scan-area.
--preview[=(yes|no)] [no]
Request a preview-quality scan.
--preview-in-gray[=(yes|no)] [no]
Request that all previews are done in monochrome mode. On a
three-pass scanner this cuts down the number of passes to one and on a
one-pass scanner, it reduces the memory requirements and scan-time of
the preview.
--brightness 29571..-353084946 (in steps of 29571) [inactive]
Controls the brightness of the acquired image.
--contrast -1207174560..32765 (in steps of 408116936) [inactive]
Controls the contrast of the acquired image.
--sharpen 29571..-353084958 (in steps of 29571) [inactive]
Set sharpen value.
--threshold 0..0 (in steps of -354412888) [inactive]
Select minimum-brightness to get a white point
...
On 4/24/24 12:44 PM, ThierryFR (@ThierrtyFR) wrote:
Send us the logs you've requested below, and we'll get an idea. Please attach the files mf260.log and MF260_Canon.pcap.
I remind you that we don't necessarily have the devices.
Hi, and thank you for looking at this. I've attached the files you requested. Yes, I'm aware that you don't have these devices which must be frustrating at times.
Send us the logs you've requested below, and we'll get an idea. Please attach the files mf260.log and MF260_Canon.pcap.
I remind you that we don't necessarily have the devices.
By using the command line, and specifying jpeg as a file type, the scan did complete without errors, however the image contains two vertical lines. I seem to recall this issue from a few years back with a similar scanner in this MF series. It was the model available before this one, but used the same driver. I've attached that image as well.
Please see the resulting image attached and the log files. They are large so I've uploaded them to my Nextcloud server and I am providing links for you to download them:
Hi, I uploaded the requested logs a few days ago. They were links because of the size. Has anyone had a chance to look at them? Is there more information I can provide?
Thank you.
...
On 4/26/24 1:44 PM, CompTechTalk wrote:
Hello,
looking at the logs, I see an error at the end when specifying either tiff or pnm file formats. The error doesn't occur when specifying png or jpeg.
By using the command line, and specifying jpeg as a file type, the scan did complete without errors, however the image contains two vertical lines. I seem to recall this issue from a few years back with a similar scanner in this MF series. It was the model available before this one, but used the same driver. I've attached that image as well.
Please see the resulting image attached and the log files. They are large so I've uploaded them to my Nextcloud server and I am providing links for you to download them:
In short, the Scan went well, but the number of bytes read did not match the number of bytes in the image.
Why you don't get the image is a warning is a mystery.
The image received in JPEG or TIF (according to me) is of the same format, it's the encoding in JPEG (the line in the middle) and in TIF that are buggy.
Ralph Littlechanged the descriptionCompare with previous version
changed the description
ThierryFRchanged title from Canon MF264dw, works with airscan, but limits resolution to 300dpi to Canon MF264dw, works with eSCL, but limits resolution to 300dpi
changed title from Canon MF264dw, works with airscan, but limits resolution to 300dpi to Canon MF264dw, works with eSCL, but limits resolution to 300dpi