I dunno. but when I start guess at things like this, first I wonder if it is something wrong with the device that i’m using – because I’m what you call suspicious. So I test with a known device – a kodak i30 in simulation mode.
If the i30 in simulation mode reproduces the problem then I usually assume that it’s my code to fault (usually, no always, but really pretty close)
then if I think it is my code I start to look thru my log/output files and trace the triplets called and the twState changes that went along with them.
That said, what triplets did you call (and what parameters)?
What were the twRc and twCc returned for them?
Are you closing down the source completely between each scan?
.