If the reader is OSDP 2.0 compliant, then how is it "Axis Locked"?
A controller can decide not to talk to a reader based on its identity, but it is much stranger for an OSDP reader not to talk to certain controllers. Do you know how they are enforcing this? I suppose they could swing this through the use of manufacturer-specific commands, but I think that would make them non-compliant.