MagTek Bluetooth MagneSafe V5 Swipe Reader - Manual (Page 18)

Bluetooth MagneSafe V5 Swipe Reader
10
Example 4 – Host waits too long sending the Activation Challenge Reply command:
1. Reader Waiting (State = WaitActAuth:GoodSwipe). This is after a good
swipe. Application may send the Get Reader State Command to discover the
current state of the reader.
2. Host sends valid Activate Authenticated Mode command (State =>
WaitActRply:GoodSwipe). Reader responds with RC=0x00 inferring the
transition to the WaitActRply:GoodSwipe state.
3. Reader times out waiting for Host to send Activation Challenge Reply
command (State => WaitActAuth:TOAuth). Host doesn’t know because the
reader cannot/does not send any message.
4. Host finally sends Activation Challenge Reply command (State remains
WaitActAuth:TOAuth). Reader responds with RC=0x07 inferring the
previous transition to WaitActAuth:TOAuth state.
CHARGING THE BLUETOOTH READER BATTERY
As mentioned above (LED Indicator), the Bluetooth reader may indicate low battery at power up.
The first time this happens there will probably be sufficient battery available for several more
card swipes, but the battery should be charged soon. If the low battery warning is ignored and
the battery gets too low, the reader will refuse to power up until it has been charged.
Charge the reader by connecting it to any USB port on a running system or a compatible 5VDC
source. For best results, allow the battery to charge fully (until the LED goes to steady amber)
before using the reader again.