Dear marshmellow,
In this thread, you indicated block zero is 0x903E1042. But I'm missing 'how to ' build B1/B2/B3 from the FC and UC of Indala.
I have developed my own prog bench for 26 bits/35/37 bits for HID emualtion, and need to add Indala for a new - but old - facility my company has bought.
Could you please help ?
Thanks a lot.
John.
Hi John,
did you manage to find an encoding order for the bits ? I need to do the same, given a FC and UC, program a card to give those out. We are looking to do batches of 100 at a time to issue to new users, with T5577 as this is much cheaper for our door access system than getting the 'proper' Indala cards/fobs issued.
On other posts you mentioned having an excel spreadsheet, is this available ?
Many thanks for any help
Nigel
In this thread, you indicated block zero is 0x903E1042. But I'm missing 'how to ' build B1/B2/B3 from the FC and UC of Indala.
I have developed my own prog bench for 26 bits/35/37 bits for HID emualtion, and need to add Indala for a new - but old - facility my company has bought.
Could you please help ?
Thanks a lot.
John.
Great work, Cheers.
]]>there is a pull request open on github to fix the indala commands and their incorrect binary offset. pull that or pull my fork to test the commands.
also t5577's come in many many shapes and sizes, so what size is it?
the multiclass readers can each be configured differently and can have technologies turned off. normally upon deployment they are always configured the same, but depending on who did it... ...
Cool, I'll check it out.
The t5577 came from the ELECHOUSE Proxmark3 V2 kit.
You're probably right about the configuration, that's interesting.
]]>also t5577's come in many many shapes and sizes, so what size is it?
the multiclass readers can each be configured differently and can have technologies turned off. normally upon deployment they are always configured the same, but depending on who did it... ...
]]>The building has a few tenants so it uses both the LF Indala clamshell and the HF Iclass.. hence the multiclass readers. which is why I was able to use the T5577 clone of the indala card to open the door.. It was just odd that only a single reader didn't accept the card (beeped but didn't open).
I placed the indala card belonging to another building onto my building reader and it beeped so there shouldn't be a reason why the cloned t5577 of the other building card couldn't be read.
Might make a lua script and upload, going to read the indala clone command and see how that works and why it doesn't work.
]]>Block 0 would be either of the earlier block zero (sets config of the tag)
Other blocks don't matter (aren't used)
Ok so I tested this method and it worked but noticed something odd.
Test1
----------------------------------------------------------------------
load a dumped indala card -> run rawdemod inverse -> run printdemod -> write block 1,2,0 to t5577.
----------------------------------------------------------------------
I tried the card on the elevator and multiple multiclass SE readers, It managed to open the door for everything except a single multiclass SE reader. Have you ever heard of this before? There are 2 doors on opposite sides when you step out of the elevator to get into the office, 1 worked and 1 didn't. Found that interesting.
Test2
----------------------------------------------------------------------
load a dumped indala card from another building -> run rawdemod inverse -> run printdemod -> write block 1,2,0 to t5577.
----------------------------------------------------------------------
I ran the same commands on another indala card that belongs to a different building. The multiclass readers didn't even beep.. Strange?
just saw this thread:
"the printer reader is able to read the card" is that a mistake?
Nope. There is a lf/hf reader on my company printer where employees can scan their pass to print.
]]>"the printer reader is able to read the card" is that a mistake?
]]>Dmanufacturer wrote:Is the point to get these numbers and write to the t5577? I guess I'm not fully grasping what's going on here.
lf t55xx wr b 1 d A0000000
lf t55xx wr b 2 d C2C436C1Am I on the right track there?
Yes. As the current indala implementation doesn't use this bit order but your multicast reader needs it. So use those blocks instead of the indala clone cmd.
Great, how many blocks are needed to write to? Just blocks 1 and 2? what would block 0 be?
]]>Is the point to get these numbers and write to the t5577? I guess I'm not fully grasping what's going on here.
lf t55xx wr b 1 d A0000000
lf t55xx wr b 2 d C2C436C1Am I on the right track there?
Yes. As the current indala implementation doesn't use this bit order but your multicast reader needs it. So use those blocks instead of the indala clone cmd.
]]>lf t55xx wr b 1 d A0000000
lf t55xx wr b 2 d C2C436C1
Am I on the right track there?
I also found that loading the card dump will only work on the printer reader and not the multiclass reader for whatever reason. I ran the following commands
Test
----------------------------------------------------------------------
lf read
data samples 16000
data save filename
data load filename
-> loaded 16000 samples
lf indala demod
-> Bitlen: 64
-> Indala UID=000000000000000
-> XXXXXXXXXXXXXX
-> XXXXXXXXXXXXXX
-> XXXXXXXXXXXXXX
-> (67d64f905)
lf indala clone 67d64f905
-> Cloning 64bit tag with UID 67d64f905
-> #db# DONE!
----------------------------------------------------------------------
After running those commands the printer reader is able to read the card but the multiclass reader is NOT able to read it at all (no beeps).
Suggestions?
]]>