[sane-devel] scanbd with Fujitsu fi-7260 Scanner: need help

[Simon Matter]

Hi,

> On Tue, Jun 10, 2025 at 11:58:14AM -0700, Dirk Meier wrote:
>> Maybe I understand. Not pressing scan button or pressing to fast scan
>> button.
>> Attached a file with switch is set to 1 and multiple pressing scan
>> button (min
>> 10 times) with sometimes longer than 2 seconds. Nothing happens. Then
>> setting
>> switch to 0 and pressing short scan button and scanner goes in action.
>>
>> In log I miss "SCANBD_FUNCTION=1", only last press with switch was
>> setting to
>> 0 is logged.
>
> I see what you mean. I'm not familiar enough with everything involved to
> know for sure what's going on here, but one hypothesis is that the
> actual device firmware is doing something different when buttons are
> pressed based on the setting of the function switch. I think you

>From my experience with these devices, the firmware doesn't change
anything depending on the function number chosen. Were are using the
Fujitsu scanners with our own button monitor (scanmonitord) and never
found evidence that the scanner changes depending on the buttons.

Regards,
Simon

> mentioned that the function switch has multiple positions, perhaps it
> would be interesting to try them all and observe whether the "scan"
> button works in each position, or only some of them.
>
> - Tricia
>
>> scanbd: polling thread for fujitsu:fi-7280:1201263, before cancellation
>> point
>> scanbd: polling thread for fujitsu:fi-7280:1201263, after cancellation
>> point
>> scanbd: polling device fujitsu:fi-7280:1201263
>> scanbd: get_sane_option_value
>> scanbd: checking option scan number 91 (0) for device
>> fujitsu:fi-7280:1201263: value: 1
>> scanbd: value trigger: numerical
>> scanbd: trigger action for scan for device fujitsu:fi-7280:1201263 with
>> script scan-function-handler.script
>> scanbd: get_sane_option_value
>> scanbd: Value of mode as string (len 7, hash -621353420): Lineart
>> scanbd: setting env: SCANBD_FUNCTION_MODE=Lineart
>> scanbd: get_sane_option_value
>> scanbd: setting env: SCANBD_FUNCTION=0
>> scanbd: setting env: PATH=/usr/sbin:/usr/bin:/sbin:/bin
>> scanbd: No PWD, setting env:
>> PWD=/mnt/netshare/Service_Unterlagen/EDV_Hardware/Fujitsu/fi-7260
>> scanbd: setting env: USER=root
>> scanbd: setting env: HOME=/root
>> scanbd: setting env: SCANBD_DEVICE=fujitsu:fi-7280:1201263
>> scanbd: setting env: SCANBD_ACTION=scan
>> scanbd: append string fujitsu:fi-7280:1201263 to signal scan_begin
>> scanbd: now sending signal scan_begin
>> scanbd: append string SCANBD_FUNCTION_MODE=Lineart to signal trigger
>> scanbd: append string SCANBD_FUNCTION=0 to signal trigger
>> scanbd: append string PATH=/usr/sbin:/usr/bin:/sbin:/bin to signal
>> trigger
>> scanbd: append string
>> PWD=/mnt/netshare/Service_Unterlagen/EDV_Hardware/Fujitsu/fi-7260 to
>> signal trigger
>> scanbd: append string USER=root to signal trigger
>> scanbd: append string HOME=/root to signal trigger
>> scanbd: append string SCANBD_DEVICE=fujitsu:fi-7280:1201263 to signal
>> trigger
>> scanbd: append string SCANBD_ACTION=scan to signal trigger
>> scanbd: now sending signal trigger
>> scanbd: now flushing the dbus
>> scanbd: unref the signal
>> scanbd: using relative script path: scan-function-handler.script,
>> expanded to: /etc/scanbd/scan-function-handler.script
>> scanbd: waiting for child: /etc/scanbd/scan-function-handler.script
>> scanbd: child /etc/scanbd/scan-function-handler.script exited with
>> status: 0
>> scanbd: append string fujitsu:fi-7280:1201263 to signal scan_end
>> scanbd: now sending signal scan_end
>
>