Open GasStationWeenie opened 5 months ago
I'll dig through the code (and once I get the testing hardware set up again, I'll attempt to replicate), but on intuition I wonder if this is attributable to oddities of the reader's parsing.
To narrow things down in the interim, a few Qs for you:
I have done testing in the past and was unable to send track 2 with lengths of less than 17 characters. When sending for example a 16-digit ID number, the application would require padding prior to the start sentinel to see a result from the reader.
i.e.
;1234123412341234? = failure 0;1234123412341234? = successfully sends 1234123412341234