ICAP_XRESOLUTION and ICAP_YRESOLUTION are TW_FIX32, which when I wrote my wrapper were tricky (yeah I’m slow). If I were to guess, I’d say your TW_FIX32 logic isn’t quite right ot the vendor is misbehaving. If you want to post the code or logic you use to read the take pointer and get a TW_FIX32 out of it, someone here might be able to help. Also, if you let us know what vendor and driver (and version) you see this on someone (probably spike, as Dosadi _must_ have to have a massive library of scanner properties and quirks) may know if the driver is odd across platforms.
rc= failure and cc=success I’ve seen. I treat those as a success. Double check that you aren’t calling the cc twice as the cc is (should be if the vendor follows the api, but.. well that isn’t always or even usually the case) reset after you call it and if you’re checking the second read instead of the first then you’re looking in the wrong place.