ScanSnap communication errors

[eN0ch]

Fujitsu/Ricoh ScanSnap S1300i document scanner with ScanSnap Home software. Since upgrade to Ventura, I’ve been getting regular communication / timeout errors during scanning, accompanied by the software crashing. I then need to power off > power on the scanner and relaunch the software.

I know there's VueScan and ExactScan. But for my purposes they're both much less functional than the OEM ScanSnap software. So I'd really rather be using ScanSnap Home if at all possible. The latest version of SSH claims to have fixed a communication issue, but it doesn't seem so from my usage.

I did find one comment somewhere about Ventura's system setting 'General > Login items > Allow in Background' being related. I turned off the 'PFU Limited' item in that list, and it did definitely reduce the communication errors. But not a fix; I still get them often (just less often).

Does anyone have any clues to offer?

 

[HDFan]

Probably not relevant but I have an IX 1600 which 1 or 2 OS versions ago refused to be recognized via USB. Fixed it by connecting via Wifi, which unfortunately isn't an option for you.

 

[Geoff777]

I'm using an iX 1600 with a 2017 iMac 27" / Ventura and it works flawlessly.
Have you been installing the ScanSnap updates? There have been 2 in the last month or so.

 

[eN0ch]

Have you been installing the ScanSnap updates? There have been 2 in the last month or so.

Thanks. Yes I'm right up to date. (See OP, second para).

I'm using an iX 1600 with a 2017 iMac 27" / Ventura and it works flawlessly.

I suspect the fact you're on an Intel system might be a critical factor of difference? (Although I have come across a few folk on Silicon, also working flawlessly). Or possibly the fact you have a more current model ScanSnap? But that seems less likely.

 

[Geoff777]

I suspect the fact you're on an Intel system might be a critical factor of difference?

Quite possibly. I have had the odd quirk with the Home software before, and I did like you did, powered down the scanner, quit the app and started again. I think there was an occasion where it didn't work so I shut the iMac down (not restart) and that seemed to fix it. But it happens very rarely, and never since I switched to Ventura.

 

[eN0ch]

Interesting. Thanks.