[sane-devel] Neat NM-1000
Stef: this scanner has been identified as a gl846 based scanner. See https://alioth.debian.org/tracker/?func=detailgroup_id=30186aid=312366atid=410369 Much thanks for the link. The most recent comments seem to indicate the chip is actually a GL123. (Some relation to the GL846?) Unfortunately SANE only has support for the GL124. What is a good basic approach to try to add the GL123? My best ideas: - Search for a GL123 datasheet (Baidu, etc.) - Adapt the GL124 backend. - Reverse engineer Windows or OS X drivers. I'm not sure which, if any, of those ideas are likely to lead to any success. Thanks, Kentrell
[sane-devel] Neat NM-1000
On 15/01/2014 13:13, Kentrell Johnson wrote: Stef: this scanner has been identified as a gl846 based scanner. See https://alioth.debian.org/tracker/?func=detailgroup_id=30186aid=312366atid=410369 Much thanks for the link. The most recent comments seem to indicate the chip is actually a GL123. (Some relation to the GL846?) Unfortunately SANE only has support for the GL124. What is a good basic approach to try to add the GL123? My best ideas: - Search for a GL123 datasheet (Baidu, etc.) - Adapt the GL124 backend. - Reverse engineer Windows or OS X drivers. I'm not sure which, if any, of those ideas are likely to lead to any success. Thanks, Kentrell Hello, if you can find the GL123 datasheet, I'd be interested to know where. I haven't been able to find it up to now. For the rest, adapting existing code by reversing the driver through USB logs is how I work. The genesys backend is the result of these 3 axes of work. Regards, Stef
[sane-devel] Neat NM-1000
On 11/01/2014 04:23, Kentrell Johnson wrote: Hello, I have a Neat NM-1000 scanner that I would like to try to get working with SANE. Someone previously tried to get it working, but ultimately could not determine which chipset it uses: http://lists.alioth.debian.org/pipermail/sane-devel/2011-June/028637.html The chipset is still not detected with the latest SANE backends (1.0.24). 'sane-find-scanner -v -v' reports: Couldn't determine the type of the USB chip (result from sane-backends 1.0.24) The e-mail linked above suggested using usbsnoop on Windows to capture a log, from which it might be possible to determine the chipset. I installed usbsnoop from http://sourceforge.net/projects/usbsnoop/, but it does not seem to be functional in Windows 7. Is there another USB sniffer that might capture the relevant information? Would it be possible to determine the chipset from taking it apart and examining the internals? There seem to be no accessible screws on the device, so I am not sure I can open it without breaking it (but am willing to do that as a last resort). Is reverse engineering the Windows or Mac drivers a possibility for determining the chipset? Maybe running them through 'strings' would be revealing? Thanks, Kentrell Hello, this scanner has been identified as a gl846 based scanner. See https://alioth.debian.org/tracker/?func=detailgroup_id=30186aid=312366atid=410369 . Regards, Stef
[sane-devel] Neat NM-1000
Hello, I have a Neat NM-1000 scanner that I would like to try to get working with SANE. Someone previously tried to get it working, but ultimately could not determine which chipset it uses: http://lists.alioth.debian.org/pipermail/sane-devel/2011-June/028637.html The chipset is still not detected with the latest SANE backends (1.0.24). 'sane-find-scanner -v -v' reports: Couldn't determine the type of the USB chip (result from sane-backends 1.0.24) The e-mail linked above suggested using usbsnoop on Windows to capture a log, from which it might be possible to determine the chipset. I installed usbsnoop from http://sourceforge.net/projects/usbsnoop/, but it does not seem to be functional in Windows 7. Is there another USB sniffer that might capture the relevant information? Would it be possible to determine the chipset from taking it apart and examining the internals? There seem to be no accessible screws on the device, so I am not sure I can open it without breaking it (but am willing to do that as a last resort). Is reverse engineering the Windows or Mac drivers a possibility for determining the chipset? Maybe running them through 'strings' would be revealing? Thanks, Kentrell
[sane-devel] Neat NM-1000
On Sat, Jan 11, 2014 at 4:23 AM, Kentrell Johnson kentrell.johnson at yandex.com wrote: Would it be possible to determine the chipset from taking it apart and examining the internals? There seem to be no accessible screws on the device, so I am not sure I can open it without breaking it (but am willing to do that as a last resort). This should be your last resort; if you are unlucky chips are unmarked or just one big ASIC. Is reverse engineering the Windows or Mac drivers a possibility for determining the chipset? Maybe running them through 'strings' would be revealing? You won't know until you try it. :) Sometimes, the *.inf files provided with Windows drivers has clues about chipsets and so on. Worth a look (.inf files are text files) HTH -- Regards, Torfinn Ingolfsen
