Calling the attribute 'tmit', 'x', 'y', from the bpm class uses a caget on a PV that can return incorrect values. BPMS:AREA:UNIT#:TMIT is not the PV we should be using as this is a slow read back software calculated value. (That is always calibrated alongside the firmware values). A better PV would be a BSA scalar version of these for example BPMS:AREA:UNIT#:TMITSCD10H or something along those lines. It is not exactly clear what the best way to go about making this change is.
Calling the attribute 'tmit', 'x', 'y', from the bpm class uses a caget on a PV that can return incorrect values. BPMS:AREA:UNIT#:TMIT is not the PV we should be using as this is a slow read back software calculated value. (That is always calibrated alongside the firmware values). A better PV would be a BSA scalar version of these for example BPMS:AREA:UNIT#:TMITSCD10H or something along those lines. It is not exactly clear what the best way to go about making this change is.