343 views with no replies, must mean no-one has come across this before
after searching the web, i've come up with a few reasons:
V8 software before V128 can only make sense of 30bits, at 128 and after, IUM software is built into the firmware enabling up to 48bits.
IUM hardware can able to enable raw data up to 48bits if correct reader is used, but challenger is still limited in the bit limit.
even using a SDC will still only enable 27bits to be read, the rest of the data is ignored (tested)
as per previous, my H2tags (dogtags) were all over the place, so i connected a IUM to the panel and read the raw data
the only thing that stayed the same with my tags was the first piece of data (48.****)
if what limited information i found on 48bit data is correct, it follows the same pattern as 27bit with a few extras thrown in.. (bits, site code, security code, card id, card level and credit data)
since the challenger is really only interested in the first 37bits, card level and credit data is ignored and handled by the challenger it's self.
so from what i've found, the tags were never programmed correctly in the first place, not even the site id is uniform across all cards
Bookmarks