Home › Forums › TWAIN Classic › Fujitsu 5120 Dynamic Threshold
- This topic has 3 replies, 2 voices, and was last updated 16 years, 11 months ago by gabe.
- AuthorPosts
Hi all,
I’m new to writing scanning software. I used a .NET component from VintaSoft to help me more rapidly develop my app. I actually like a lot. I can set the capabilities for my scan rather easily and it has an enumeration for many common caps. My problem is that there is no built-in value for setting the SDTC (Simplified Dynamic Threshold) capability of my Fujitsu 5120.
I thought I would ask all you pros here how I would go about figuring out the capability code and possible values for that feature? Does anybody happen to know? I’ve searched all over the Internet for published specs but have had no luck.
Sorry if this all sounds newbish. Your advice is much appreciated.
Thanks,
JoeSDTC (Simplified Dynamic Threshold) isn’t defined in the twain spec. It is probably a custom capability for the device. Ask VintaSoft for information on setting custom capabilities. Or you could try using CustomDsData and hacking the stream you send back in… seach the forumn for ‘hack’. if you go with setting the custom cap directly you might need a little info from the device vendor, like the acceptable values and if you ever get someone from the device vendor to talk to you that seems to understand what a castom capability is ask them fór their twain header as it will be of use when you run into the next .custom cap.
Thanks Gabe. I do know how to set a custom cap with VintaSoft. My problem lies more with knowing which code to set and the acceptable values. I was hoping there was some other way to go about getting the code than hunting somebody down af Fujitsu. I can’t imagine that being an easy thing to do. I’ll give it a shot though. Thanks for the response.
…or, (and in my arrogant opinion this is a much design) skip setting caps one-by-one. Use EnablrDsUiOnly to prep a profile , capture the CustonDsData and when you want those setting replay the CustomDsData back to the device. It a two step approch and you’ll still use the vendor’s Ui for the profile setup but in the long run you skip tons of problems.
- AuthorPosts