Special thanks to Metallic and Winteriscoming for making this possible.
@AbolishedEnigma I have analyzed your traffic and offer the following:
re: Inserted Previous...
I wrote a script to convert the hex to ascii and below are the results
Track 1 of the card shows
K3x00Gl Jane Glass Tiger Mountain High N gw f
Track 2 of the card shows
K3x00$ 1 # Ü .&1? )D B gw Î (Distorted hex to ascii conversion in my script so most was decipherable)
Track 3 of the card shows
K3x00SEGABEF0¨ 0 gw þ
After a quick analysis of the capture, my conclusion is:
- The player card contains 3 tracks and the capture contains 3 tracks
- Track 1, 2 and 3 of the card are identifiable in the capture and can somewhat be deciphered with a conversion from Hex to ASCII
- All tracks begin with what appears to be a header K3x... and trailer seems to be close on all(not sure if this is the checksum) - gw
May I trouble you for one more test and capture based upon a known capture of the card before inserting and attach the original horse card file captured from the msr206 into the reply?
My end goal is to validate the capture and determine if the sanwa protocol can be more understood. by comparing the data of the card before and after it is transmitted to the sanwa card.
One possible outcome would be to write custom horse names and other data on a card as specified by an operator.
As a follow up to Metallic's post from 2016, has anyone downloaded the sanwa pdf and dll sample code? I think this might make sense of the track 1, 2 and 3 strings in the capture.
