I think this is also related to issue:
https://corryvreckan-forum.web.cern.ch/t/usbpix-ignores-resolution-setting
where we started looking at measurement errors for our USBPix device, because x and y seemed to be mixed up. We got round that by (i) ignoring the error issue and (ii) stopped swapping x and y when going from EUDAQ raw data to Corryvreckan Detector, and then replacing a 180 deg rotation by a 90 deg rotation.