1. Home
  2. Knowledge Base
  3. IDWedge
  4. IDWedge M250
  5. Troubleshooting the Magstripe Reader on the M250 / M260
  1. Home
  2. Knowledge Base
  3. IDWedge
  4. IDWedge M260
  5. Troubleshooting the Magstripe Reader on the M250 / M260

Troubleshooting the Magstripe Reader on the M250 / M260

Requirements:

-TokenWorks DLL Sample app from one of the SDKs (M250/M260)

-M250/M260 and the supplied USB cable to connect to a PC

Procedure:

  1. Connect scanner to PC
  2. Launch the Tokenworks DLL Test App , Click the Select Port button to select/accept the comport for the scanner, then click on the  Open Port button, the Scanner output window should display OK!
  3. Swipe a magnetic stripe ID/Card, or use a credit card to test out the scanner, make sure it is oriented correctly, the scanner will beep if the card scans.  If the scanner does not beep, check the card oriented correctly, the card may be damaged, and can not be read.  Try another card if this is the case.
  4. Observe the results displayed
    1. When a Magstripe ID is swiped on the your scanner while in the Tokenworks DLL Test App, you should see the form populated as well as the raw data in the output window on the right. Credit cards only display the first/last/PAN and expiration fields at the bottom.
    2. In the output window you should see the Raw data, with each track surrounded by start and end sentinels.
    3. If the Scanner beeps when a card is scanned but nothing parses, try pressing the Program Scanner button to reprogram a scanner. The scanner must be registered at Tokenworks for use with the DLL Parsing test app. The scanner will triple beep upon successful programming .If the scanner still doesn’t output any data please call Tokenworks support at 800-574-5034 ext 2 for further assistance.

Magnetic DL scan

MagID

Credit card scan

CC scan

 

Example of Raw data for Magtripe:

Legend:
NR = No Read – problem reading data on track
ND = No Data on track

Credit card Scan:

Track1 %B4750130105293638^GAGLIOSTRI/PAUL^1001101000000000012400000000000?

Track2 ;4750130105293638=10011010000000000124?

Track3 %ND?

Note how a credit card only has two tracks of data (Tracks1,2), and the third track displays the no data message, surrounded by sentinels.
The three tracks will be bounded by the track sentinels, which are generated by the
reader.
Track 1 – Start Sentinel= % and End Sentinel= ?
Track 2 – Start Sentinel= ;  and End Sentinel= ?
Track 3 – Start Sentinel=% and End Sentinel= ?

Track 3 is not common – on credit cards – only on Drivers Licenses.
The magstripe scan may have good and bad tracks so there may be an indication of a
good read in the header but then there will be error messages for the individual tracks

Magnetic DL Scan:

Track1 %TXLEAGUE CITY^JARDAN$JERRICA$L^3850 FM 420 RD E 2806^?

Track2 ;63601505945042=140419830428?

Track3 %” 775730000  C               F503116BLOHZL                          5Q/$8A     ?

In order for the Parsing software to work, Track2 must read, if a card scan partially reads a card, but does not capture track2 the parsing software will not be able to identify the card.

Example of no read Mad DL on track2:

Track1 %TXLEAGUE CITY^JARDAN$JERRICA$L^3850 FM 420 RD E 2806^?

Track2 ;NR?

Track3 %” 775730000  C               F503116BLOHZL                          5Q/$8A     ?

The above scan will display in the output window, but will not parse because it is missing track2.

For Other types of Magstripe cards, like loyaty card, Casino Card, the parsing software does not recognize these cards, so the application will need to process the raw data from the reader.

If the error(s) persist, please call Tokenworks support at 800-574-5034 ext 2 for further assistance.

 

Updated on January 1, 2021

Was this article helpful?

Related Articles

Need Support?
Can't find the answer you're looking for? Don't worry we're here to help!
Open Support Ticket