Re: [sane-devel] scanimage -L detects no scanners / sane-find-scanner does -- on MacOS
Hi, On 2021-05-08 3:49 p.m., m. allan noah wrote: > Chances are, you are wrong :) > > allan > > On Sat, May 8, 2021 at 4:50 AM Andrew Goodbody wrote: >> Chances are that rather than interfering with Sane, the proprietary >> software does something that made the scanner work the next time you ran >> Sane after having just run the ScanSnap app. >> >> Would this scanner require a firmware download? I know that some snapscan scanners do. Cheers, Ralph
Re: [sane-devel] scanimage -L detects no scanners / sane-find-scanner does -- on MacOS
Chances are, you are wrong :) allan On Sat, May 8, 2021 at 4:50 AM Andrew Goodbody wrote: > > Chances are that rather than interfering with Sane, the proprietary > software does something that made the scanner work the next time you ran > Sane after having just run the ScanSnap app. > > Andrew > > On 07/05/2021 22:12, Media Mouth wrote: > > Well noting yet. Any reason to think that using the proprietary > > software that comes with a Fujitsu scanner "ScanSnap.app" might do > > something that interferes with SANE. (I'm suspect SANE is their > > underlying engine) > > > > We are and have been able to scan using ScanSnap, and for a brief moment > > yesterday we were /also/ able to run `scanimage` and save a .pnm > > > >> On May 7, 2021, at 12:05 PM, m. allan noah >> <mailto:kitno...@gmail.com>> wrote: > >> > >> Unknown- look for OSX system logs that might include USB related errors. > >> > >> allan > >> > >> On Fri, May 7, 2021 at 2:09 PM Media Mouth >> <mailto:commun...@gmail.com>> wrote: > >>> > >>> So we're apparently back to the original question... > >>> > >>> "Re: [sane-devel] scanimage -L detects no scanners / > >>> sane-find-scanner does -- on MacOS" > >>> > >>> `sane-find-scanner` returns `found USB scanner (vendor=0x04c5 > >>> [Fujitsu], product=0x132b [ScanSnap iX500]) at libusb:000:002` > >>> and > >>> `scanimage -L` returns `No scanners were identified. If you were > >>> expecting something different` etc. > >>> > >>> It was after your request for the stdout of `SANE_DEBUG_FUJITSU=50 > >>> SANE_DEBUG_SANEI_CONFIG=10 scanimage -L` > >>> that it suddenly started working, so I wondered if by some magic that > >>> was waking something up, but running it again made not difference > >>> this go around. > >>> > >>> Any ideas? > >>> > >>> > >>> On May 7, 2021, at 6:26 AM, MediaMouth >>> <mailto:commun...@gmail.com>> wrote: > >>> > >>> It did ... and then it didn't. Right after successfully scanning a > >>> page, subsequent attempts, using the same command, failed with error > >>> "invalid argument". > >>> > >>> On May 7, 2021, at 05:14, m. allan noah >>> <mailto:kitno...@gmail.com>> wrote: > >>> > >>> "device `fujitsu:ScanSnap iX500:330189' is a FUJITSU ScanSnap iX500 > >>> scanner" > >>> > >>> looks like it works? > >>> > >>> > >> > >> > >> -- > >> "well, I stand up next to a mountain- and I chop it down with the edge > >> of my hand" > > > > -- "well, I stand up next to a mountain- and I chop it down with the edge of my hand"
Re: [sane-devel] scanimage -L detects no scanners / sane-find-scanner does -- on MacOS
RE > In general, you would not have both the factory software and sane on the > machine at the same time. Agreed. For that particular scanner / machine I'm not permitted to remove the existing Fujitsu software, but it does seem to be the very thing that's causing `scanimage -L` to fail to see it. I just tested the same printer (different machine, same model) on a Mac without the Fujitsu software, and it recognizes just fine, repeatedly when connected via USB, so I think the culprit is the Fujitsu software. Thanks for your help. Trying to move on to connecting via WiFi, will send in a separate thread. Thanks again. > On May 7, 2021, at 5:35 PM, m. allan noah wrote: > > I mean currently running and talking to the scanner. Perhaps something > like monitoring for button presses. In general, you would not have > both the factory software and sane on the machine at the same time. > > On Fri, May 7, 2021 at 7:26 PM MediaMouth wrote: >> >> Control, meaning 'currently scanning' or meaning it has run, therefore made >> some kind of a settings change, such that even when not launched retains >> "control" >> >>> On May 7, 2021, at 16:23, m. allan noah wrote: >>> >>> The proprietary software does not use sane, and if it currently has >>> control of the scanner, sane will not be able to work. >>> >>> allan >>> >>>> On Fri, May 7, 2021 at 5:12 PM Media Mouth wrote: >>>> >>>> Well noting yet. Any reason to think that using the proprietary software >>>> that comes with a Fujitsu scanner "ScanSnap.app" might do something that >>>> interferes with SANE. (I'm suspect SANE is their underlying engine) >>>> >>>> We are and have been able to scan using ScanSnap, and for a brief moment >>>> yesterday we were also able to run `scanimage` and save a .pnm >>>> >>>> On May 7, 2021, at 12:05 PM, m. allan noah wrote: >>>> >>>> Unknown- look for OSX system logs that might include USB related errors. >>>> >>>> allan >>>> >>>> On Fri, May 7, 2021 at 2:09 PM Media Mouth wrote: >>>> >>>> >>>> So we're apparently back to the original question... >>>> >>>> "Re: [sane-devel] scanimage -L detects no scanners / sane-find-scanner >>>> does -- on MacOS" >>>> >>>> `sane-find-scanner` returns `found USB scanner (vendor=0x04c5 [Fujitsu], >>>> product=0x132b [ScanSnap iX500]) at libusb:000:002` >>>> and >>>> `scanimage -L` returns `No scanners were identified. If you were expecting >>>> something different` etc. >>>> >>>> It was after your request for the stdout of `SANE_DEBUG_FUJITSU=50 >>>> SANE_DEBUG_SANEI_CONFIG=10 scanimage -L` >>>> that it suddenly started working, so I wondered if by some magic that was >>>> waking something up, but running it again made not difference this go >>>> around. >>>> >>>> Any ideas? >>>> >>>> >>>> On May 7, 2021, at 6:26 AM, MediaMouth wrote: >>>> >>>> It did ... and then it didn't. Right after successfully scanning a page, >>>> subsequent attempts, using the same command, failed with error "invalid >>>> argument". >>>> >>>> On May 7, 2021, at 05:14, m. allan noah wrote: >>>> >>>> "device `fujitsu:ScanSnap iX500:330189' is a FUJITSU ScanSnap iX500 >>>> scanner" >>>> >>>> looks like it works? >>>> >>>> >>>> >>>> >>>> -- >>>> "well, I stand up next to a mountain- and I chop it down with the edge >>>> of my hand" >>>> >>>> >>> >>> >>> -- >>> "well, I stand up next to a mountain- and I chop it down with the edge >>> of my hand" > > > > -- > "well, I stand up next to a mountain- and I chop it down with the edge > of my hand"
Re: [sane-devel] scanimage -L detects no scanners / sane-find-scanner does -- on MacOS
I mean currently running and talking to the scanner. Perhaps something like monitoring for button presses. In general, you would not have both the factory software and sane on the machine at the same time. On Fri, May 7, 2021 at 7:26 PM MediaMouth wrote: > > Control, meaning 'currently scanning' or meaning it has run, therefore made > some kind of a settings change, such that even when not launched retains > "control" > > > On May 7, 2021, at 16:23, m. allan noah wrote: > > > > The proprietary software does not use sane, and if it currently has > > control of the scanner, sane will not be able to work. > > > > allan > > > >> On Fri, May 7, 2021 at 5:12 PM Media Mouth wrote: > >> > >> Well noting yet. Any reason to think that using the proprietary software > >> that comes with a Fujitsu scanner "ScanSnap.app" might do something that > >> interferes with SANE. (I'm suspect SANE is their underlying engine) > >> > >> We are and have been able to scan using ScanSnap, and for a brief moment > >> yesterday we were also able to run `scanimage` and save a .pnm > >> > >> On May 7, 2021, at 12:05 PM, m. allan noah wrote: > >> > >> Unknown- look for OSX system logs that might include USB related errors. > >> > >> allan > >> > >> On Fri, May 7, 2021 at 2:09 PM Media Mouth wrote: > >> > >> > >> So we're apparently back to the original question... > >> > >> "Re: [sane-devel] scanimage -L detects no scanners / sane-find-scanner > >> does -- on MacOS" > >> > >> `sane-find-scanner` returns `found USB scanner (vendor=0x04c5 [Fujitsu], > >> product=0x132b [ScanSnap iX500]) at libusb:000:002` > >> and > >> `scanimage -L` returns `No scanners were identified. If you were expecting > >> something different` etc. > >> > >> It was after your request for the stdout of `SANE_DEBUG_FUJITSU=50 > >> SANE_DEBUG_SANEI_CONFIG=10 scanimage -L` > >> that it suddenly started working, so I wondered if by some magic that was > >> waking something up, but running it again made not difference this go > >> around. > >> > >> Any ideas? > >> > >> > >> On May 7, 2021, at 6:26 AM, MediaMouth wrote: > >> > >> It did ... and then it didn't. Right after successfully scanning a page, > >> subsequent attempts, using the same command, failed with error "invalid > >> argument". > >> > >> On May 7, 2021, at 05:14, m. allan noah wrote: > >> > >> "device `fujitsu:ScanSnap iX500:330189' is a FUJITSU ScanSnap iX500 > >> scanner" > >> > >> looks like it works? > >> > >> > >> > >> > >> -- > >> "well, I stand up next to a mountain- and I chop it down with the edge > >> of my hand" > >> > >> > > > > > > -- > > "well, I stand up next to a mountain- and I chop it down with the edge > > of my hand" -- "well, I stand up next to a mountain- and I chop it down with the edge of my hand"
Re: [sane-devel] scanimage -L detects no scanners / sane-find-scanner does -- on MacOS
Control, meaning 'currently scanning' or meaning it has run, therefore made some kind of a settings change, such that even when not launched retains "control" > On May 7, 2021, at 16:23, m. allan noah wrote: > > The proprietary software does not use sane, and if it currently has > control of the scanner, sane will not be able to work. > > allan > >> On Fri, May 7, 2021 at 5:12 PM Media Mouth wrote: >> >> Well noting yet. Any reason to think that using the proprietary software >> that comes with a Fujitsu scanner "ScanSnap.app" might do something that >> interferes with SANE. (I'm suspect SANE is their underlying engine) >> >> We are and have been able to scan using ScanSnap, and for a brief moment >> yesterday we were also able to run `scanimage` and save a .pnm >> >> On May 7, 2021, at 12:05 PM, m. allan noah wrote: >> >> Unknown- look for OSX system logs that might include USB related errors. >> >> allan >> >> On Fri, May 7, 2021 at 2:09 PM Media Mouth wrote: >> >> >> So we're apparently back to the original question... >> >> "Re: [sane-devel] scanimage -L detects no scanners / sane-find-scanner does >> -- on MacOS" >> >> `sane-find-scanner` returns `found USB scanner (vendor=0x04c5 [Fujitsu], >> product=0x132b [ScanSnap iX500]) at libusb:000:002` >> and >> `scanimage -L` returns `No scanners were identified. If you were expecting >> something different` etc. >> >> It was after your request for the stdout of `SANE_DEBUG_FUJITSU=50 >> SANE_DEBUG_SANEI_CONFIG=10 scanimage -L` >> that it suddenly started working, so I wondered if by some magic that was >> waking something up, but running it again made not difference this go around. >> >> Any ideas? >> >> >> On May 7, 2021, at 6:26 AM, MediaMouth wrote: >> >> It did ... and then it didn't. Right after successfully scanning a page, >> subsequent attempts, using the same command, failed with error "invalid >> argument". >> >> On May 7, 2021, at 05:14, m. allan noah wrote: >> >> "device `fujitsu:ScanSnap iX500:330189' is a FUJITSU ScanSnap iX500 scanner" >> >> looks like it works? >> >> >> >> >> -- >> "well, I stand up next to a mountain- and I chop it down with the edge >> of my hand" >> >> > > > -- > "well, I stand up next to a mountain- and I chop it down with the edge > of my hand"
Re: [sane-devel] scanimage -L detects no scanners / sane-find-scanner does -- on MacOS
The proprietary software does not use sane, and if it currently has control of the scanner, sane will not be able to work. allan On Fri, May 7, 2021 at 5:12 PM Media Mouth wrote: > > Well noting yet. Any reason to think that using the proprietary software > that comes with a Fujitsu scanner "ScanSnap.app" might do something that > interferes with SANE. (I'm suspect SANE is their underlying engine) > > We are and have been able to scan using ScanSnap, and for a brief moment > yesterday we were also able to run `scanimage` and save a .pnm > > On May 7, 2021, at 12:05 PM, m. allan noah wrote: > > Unknown- look for OSX system logs that might include USB related errors. > > allan > > On Fri, May 7, 2021 at 2:09 PM Media Mouth wrote: > > > So we're apparently back to the original question... > > "Re: [sane-devel] scanimage -L detects no scanners / sane-find-scanner does > -- on MacOS" > > `sane-find-scanner` returns `found USB scanner (vendor=0x04c5 [Fujitsu], > product=0x132b [ScanSnap iX500]) at libusb:000:002` > and > `scanimage -L` returns `No scanners were identified. If you were expecting > something different` etc. > > It was after your request for the stdout of `SANE_DEBUG_FUJITSU=50 > SANE_DEBUG_SANEI_CONFIG=10 scanimage -L` > that it suddenly started working, so I wondered if by some magic that was > waking something up, but running it again made not difference this go around. > > Any ideas? > > > On May 7, 2021, at 6:26 AM, MediaMouth wrote: > > It did ... and then it didn't. Right after successfully scanning a page, > subsequent attempts, using the same command, failed with error "invalid > argument". > > On May 7, 2021, at 05:14, m. allan noah wrote: > > "device `fujitsu:ScanSnap iX500:330189' is a FUJITSU ScanSnap iX500 scanner" > > looks like it works? > > > > > -- > "well, I stand up next to a mountain- and I chop it down with the edge > of my hand" > > -- "well, I stand up next to a mountain- and I chop it down with the edge of my hand"
Re: [sane-devel] scanimage -L detects no scanners / sane-find-scanner does -- on MacOS
Well noting yet. Any reason to think that using the proprietary software that comes with a Fujitsu scanner "ScanSnap.app" might do something that interferes with SANE. (I'm suspect SANE is their underlying engine) We are and have been able to scan using ScanSnap, and for a brief moment yesterday we were also able to run `scanimage` and save a .pnm > On May 7, 2021, at 12:05 PM, m. allan noah wrote: > > Unknown- look for OSX system logs that might include USB related errors. > > allan > > On Fri, May 7, 2021 at 2:09 PM Media Mouth wrote: >> >> So we're apparently back to the original question... >> >> "Re: [sane-devel] scanimage -L detects no scanners / sane-find-scanner does >> -- on MacOS" >> >> `sane-find-scanner` returns `found USB scanner (vendor=0x04c5 [Fujitsu], >> product=0x132b [ScanSnap iX500]) at libusb:000:002` >> and >> `scanimage -L` returns `No scanners were identified. If you were expecting >> something different` etc. >> >> It was after your request for the stdout of `SANE_DEBUG_FUJITSU=50 >> SANE_DEBUG_SANEI_CONFIG=10 scanimage -L` >> that it suddenly started working, so I wondered if by some magic that was >> waking something up, but running it again made not difference this go around. >> >> Any ideas? >> >> >> On May 7, 2021, at 6:26 AM, MediaMouth wrote: >> >> It did ... and then it didn't. Right after successfully scanning a page, >> subsequent attempts, using the same command, failed with error "invalid >> argument". >> >> On May 7, 2021, at 05:14, m. allan noah wrote: >> >> "device `fujitsu:ScanSnap iX500:330189' is a FUJITSU ScanSnap iX500 scanner" >> >> looks like it works? >> >> > > > -- > "well, I stand up next to a mountain- and I chop it down with the edge > of my hand"
Re: [sane-devel] scanimage -L detects no scanners / sane-find-scanner does -- on MacOS
Unknown- look for OSX system logs that might include USB related errors. allan On Fri, May 7, 2021 at 2:09 PM Media Mouth wrote: > > So we're apparently back to the original question... > > "Re: [sane-devel] scanimage -L detects no scanners / sane-find-scanner does > -- on MacOS" > > `sane-find-scanner` returns `found USB scanner (vendor=0x04c5 [Fujitsu], > product=0x132b [ScanSnap iX500]) at libusb:000:002` > and > `scanimage -L` returns `No scanners were identified. If you were expecting > something different` etc. > > It was after your request for the stdout of `SANE_DEBUG_FUJITSU=50 > SANE_DEBUG_SANEI_CONFIG=10 scanimage -L` > that it suddenly started working, so I wondered if by some magic that was > waking something up, but running it again made not difference this go around. > > Any ideas? > > > On May 7, 2021, at 6:26 AM, MediaMouth wrote: > > It did ... and then it didn't. Right after successfully scanning a page, > subsequent attempts, using the same command, failed with error "invalid > argument". > > On May 7, 2021, at 05:14, m. allan noah wrote: > > "device `fujitsu:ScanSnap iX500:330189' is a FUJITSU ScanSnap iX500 scanner" > > looks like it works? > > -- "well, I stand up next to a mountain- and I chop it down with the edge of my hand"
Re: [sane-devel] scanimage -L detects no scanners / sane-find-scanner does -- on MacOS
So we're apparently back to the original question... "Re: [sane-devel] scanimage -L detects no scanners / sane-find-scanner does -- on MacOS" `sane-find-scanner` returns `found USB scanner (vendor=0x04c5 [Fujitsu], product=0x132b [ScanSnap iX500]) at libusb:000:002` and `scanimage -L` returns `No scanners were identified. If you were expecting something different` etc. It was after your request for the stdout of `SANE_DEBUG_FUJITSU=50 SANE_DEBUG_SANEI_CONFIG=10 scanimage -L` that it suddenly started working, so I wondered if by some magic that was waking something up, but running it again made not difference this go around. Any ideas? > On May 7, 2021, at 6:26 AM, MediaMouth wrote: > > It did ... and then it didn't. Right after successfully scanning a page, > subsequent attempts, using the same command, failed with error "invalid > argument". > >> On May 7, 2021, at 05:14, m. allan noah wrote: >> >> "device `fujitsu:ScanSnap iX500:330189' is a FUJITSU ScanSnap iX500 scanner" >> >> looks like it works?
Re: [sane-devel] scanimage -L detects no scanners / sane-find-scanner does -- on MacOS
"device `fujitsu:ScanSnap iX500:330189' is a FUJITSU ScanSnap iX500 scanner" looks like it works? On Fri, May 7, 2021 at 8:03 AM Media Mouth wrote: > > RE: > > Could we see the output of this? > > SANE_DEBUG_FUJITSU=50 SANE_DEBUG_SANEI_CONFIG=10 scanimage -L > > > Sure thing. See below. Curiously, having run that command, I'm suddenly > (finally) seeing the scanner on `scanimage -L` alone. > > [23:20:21.769223] [sanei_debug] Setting debug level of sanei_config to 10. > [23:20:21.769482] [sanei_config] sanei_config_get_paths: using config > directories .:/usr/local/Cellar/sane-backends/1.0.32/etc/sane.d > [23:20:21.769564] [sanei_config] sanei_config_get_paths: using config > directories .:/usr/local/Cellar/sane-backends/1.0.32/etc/sane.d > [23:20:21.769576] [sanei_config] sanei_config_open: attempting to open > `./dll.conf' > [23:20:21.769594] [sanei_config] sanei_config_open: attempting to open > `/usr/local/Cellar/sane-backends/1.0.32/etc/sane.d/dll.conf' > [23:20:21.769653] [sanei_config] sanei_config_open: using file > `/usr/local/Cellar/sane-backends/1.0.32/etc/sane.d/dll.conf' > [23:20:21.769768] [sanei_config] sanei_config_get_paths: using config > directories .:/usr/local/Cellar/sane-backends/1.0.32/etc/sane.d > [23:20:21.769778] [sanei_config] sanei_config_open: attempting to open > `./dll.aliases' > [23:20:21.769788] [sanei_config] sanei_config_open: attempting to open > `/usr/local/Cellar/sane-backends/1.0.32/etc/sane.d/dll.aliases' > [23:20:21.769806] [sanei_config] sanei_config_open: could not find config > file `dll.aliases' > [23:20:21.785252] [sanei_config] sanei_configure_attach: start > [23:20:21.785275] [sanei_config] sanei_config_get_paths: using config > directories .:/usr/local/Cellar/sane-backends/1.0.32/etc/sane.d > [23:20:21.785290] [sanei_config] sanei_config_open: attempting to open > `./xerox_mfp.conf' > [23:20:21.785313] [sanei_config] sanei_config_open: attempting to open > `/usr/local/Cellar/sane-backends/1.0.32/etc/sane.d/xerox_mfp.conf' > [23:20:21.785374] [sanei_config] sanei_config_open: using file > `/usr/local/Cellar/sane-backends/1.0.32/etc/sane.d/xerox_mfp.conf' > [23:20:21.785419] [sanei_config] sanei_configure_attach: trying to attach > with 'usb 0x04e8 0x3324' > [23:20:21.785465] [sanei_config] sanei_configure_attach: trying to attach > with 'usb 0x04e8 0x3325' > [23:20:21.785472] [sanei_config] sanei_configure_attach: trying to attach > with 'usb 0x04e8 0x3326' > [23:20:21.785477] [sanei_config] sanei_configure_attach: trying to attach > with 'usb 0x04e8 0x3327' > [23:20:21.785482] [sanei_config] sanei_configure_attach: trying to attach > with 'usb 0x04e8 0x3331' > [23:20:21.785488] [sanei_config] sanei_configure_attach: trying to attach > with 'usb 0x04e8 0x3332' > [23:20:21.785493] [sanei_config] sanei_configure_attach: trying to attach > with 'usb 0x04e8 0x3409' > [23:20:21.785498] [sanei_config] sanei_configure_attach: trying to attach > with 'usb 0x04e8 0x340d' > [23:20:21.785503] [sanei_config] sanei_configure_attach: trying to attach > with 'usb 0x04e8 0x340e' > [23:20:21.785508] [sanei_config] sanei_configure_attach: trying to attach > with 'usb 0x04e8 0x340f' > [23:20:21.785513] [sanei_config] sanei_configure_attach: trying to attach > with 'usb 0x04e8 0x3412' > [23:20:21.785518] [sanei_config] sanei_configure_attach: trying to attach > with 'usb 0x04e8 0x3413' > [23:20:21.785523] [sanei_config] sanei_configure_attach: trying to attach > with 'usb 0x04e8 0x3419' > [23:20:21.785551] [sanei_config] sanei_configure_attach: trying to attach > with 'usb 0x04e8 0x341a' > [23:20:21.785574] [sanei_config] sanei_configure_attach: trying to attach > with 'usb 0x04e8 0x341b' > [23:20:21.785580] [sanei_config] sanei_configure_attach: trying to attach > with 'usb 0x04e8 0x341c' > [23:20:21.785585] [sanei_config] sanei_configure_attach: trying to attach > with 'usb 0x04e8 0x341d' > [23:20:21.785590] [sanei_config] sanei_configure_attach: trying to attach > with 'usb 0x04e8 0x341f' > [23:20:21.785595] [sanei_config] sanei_configure_attach: trying to attach > with 'usb 0x04e8 0x3420' > [23:20:21.785600] [sanei_config] sanei_configure_attach: trying to attach > with 'usb 0x04e8 0x3421' > [23:20:21.785605] [sanei_config] sanei_configure_attach: trying to attach > with 'usb 0x04e8 0x3425' > [23:20:21.785610] [sanei_config] sanei_configure_attach: trying to attach > with 'usb 0x04e8 0x3426' > [23:20:21.785615] [sanei_config] sanei_configure_attach: trying to attach > with 'usb 0x04e8 0x3427' > [23:20:21.785620] [sanei_config] sanei_configure_attach: trying to attach > with 'usb 0x04e8 0x3428' > [23:20:21.785625] [sanei_config] sanei_configure_attach: trying to attach > with 'usb 0x04e8 0x3429' > [23:20:21.785630] [sanei_config] sanei_configure_attach: trying to attach > with 'usb 0x04e8 0x342a' > [23:20:21.785635] [sanei_config] sanei_configure_attach: trying to attach > with 'usb 0x04e8 0x342b' > [23:20:21.785641]
Re: [sane-devel] scanimage -L detects no scanners / sane-find-scanner does -- on MacOS
Hi Ralph, thanks for the followup Platform: MacOS 11.3.1 Intel Core i9 SANE: scanimage (sane-backends) 1.0.32; backend version 1.0.32 RE > "only USB is currently supported" Understood. I read somewhere that adding the LAN IP of the scanner to file `net.conf` ( /usr/local/etc/sane.d/net.conf ) makes it possible to add WiFi functionality. For now USB is fine. > On May 6, 2021, at 8:45 PM, Ralph Little wrote: > > Hi, > According to our page here: > > http://www.sane-project.org/sane-mfgs.html > > ...only USB is currently supported. > > Could you tell us what the platform is (OS/architecture) and what > version of SANE you have installed (scanimage -V)? > > Cheers, > Ralph > > > On 2021-05-06 8:03 p.m., Media Mouth wrote: >> Trying to get scanimage working with a fujitsu:ScanSnap iX500 scanner over >> USB and WiFi. >> At the moment neither is working >> >> `sane-find-scanner` is able to see it and return `found USB scanner >> (vendor=0x04c5 [Fujitsu], product=0x132b [ScanSnap iX500]) at libusb:000:004` >> >> `scanimage -L` and `sudo scanimage -L` return `No scanners were identified. >> If you were expecting something different,` etc etc. > >
Re: [sane-devel] scanimage -L detects no scanners / sane-find-scanner does -- on MacOS
Hi, According to our page here: http://www.sane-project.org/sane-mfgs.html ...only USB is currently supported. Could you tell us what the platform is (OS/architecture) and what version of SANE you have installed (scanimage -V)? Cheers, Ralph On 2021-05-06 8:03 p.m., Media Mouth wrote: > Trying to get scanimage working with a fujitsu:ScanSnap iX500 scanner over > USB and WiFi. > At the moment neither is working > > `sane-find-scanner` is able to see it and return `found USB scanner > (vendor=0x04c5 [Fujitsu], product=0x132b [ScanSnap iX500]) at libusb:000:004` > > `scanimage -L` and `sudo scanimage -L` return `No scanners were identified. > If you were expecting something different,` etc etc.
