11.07.2015 Views

I/O Interface for TTL Magnetic Stripe Readers, Technical ... - MagTek

I/O Interface for TTL Magnetic Stripe Readers, Technical ... - MagTek

I/O Interface for TTL Magnetic Stripe Readers, Technical ... - MagTek

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

I/O <strong>Interface</strong> <strong>for</strong> <strong>TTL</strong> <strong>Magnetic</strong> <strong>Stripe</strong> <strong>Readers</strong>It is necessary to write a program that will:1) go through memory, starting from the end that has the start sentinel, and2) decode the characters (which may be <strong>for</strong>ward or backwards depending on which way the cardwas swiped and not on a byte boundary), and3) check <strong>for</strong> errors then transmit the characters <strong>for</strong>ward back To the host.Another problem is that the LRC will assume the same value as the Start Sentinel some of thetime, and when it does, then the character adjacent to it has to be tested to see if it is an endsentinel. If it is an end sentinel, then this character is an LRC otherwise it is a Start Sentinel. Inthis way you can make sure which end is really the beginning. See Appendix D, BidirectionalReading.CARD READBACK AMPLITUDE VARIATIONSCauses of readback amplitude variations are as follows:• Speed of the card - the faster, the more amplitude• Head contact, head pressure, smoothness of stripe, bumps• Quality of oxide• Orientation of oxide (polarization)• Thickness of oxide• Type of oxide, low or high coercivityTo check the amplitude variations, connect a scope between ground (pin 5) and drive or gain set(pin 9 or 11), on the F2F read/decode IC. Swipe an encoded card, and check the scope <strong>for</strong> thevariations above.The waveshape should be similar to Figure 2-1. For pin locations refer to Appendix B,Connection diagram (Pin Outs).20

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!