rfidtool / esp-rfid-tool Goto Github PK

Price: $19.00
April Brother's Tindie store:
https://www.tindie.com/products/aprbrother/esp-rfid-tool/

I connected it to a 125khz ID wg26 reader but when it read i first converted the hex number to decimal and it didn't match the real number. I also tried to get some number of the binary data with no luck as well. I don't know, maybe my device is faulty. It restarts every time i read and i have to connect the wifi again. Or i don't know how to get the decimal number of the card. This is my log file. The last (underlined) reads are of a card with the number 0008617284. I will be very thankful if someone could give me some much needed help.

The ESP RFID Tool was able to read several test cards from the HID multiCLASS reader to a UHPPOTE controller. The successful reads/captures can be observed below. However, the ESP RFID Tool is unable to read the same cards, also observed below. Would gladly welcome any troubleshooting ideas...

37 bit card,7 bit preamble,Binary:0000000 0010110010110111001000110010011011111,HEX:596E464DF
37 bit card,7 bit preamble,Binary:0000000 0010110010110111001000110010011011111,HEX:596E464DF
37 bit card,7 bit preamble,Binary:0000000 0010110010110111001000110010011011111,HEX:596E464DF
37 bit card,7 bit preamble,Binary:0000000 0010110010110111001000110010011011111,HEX:596E464DF
37 bit card,7 bit preamble,Binary:0000000 0010110010110111001000110010011011111,HEX:596E464DF
32 bit card,12 bit preamble,Binary:000000100001 00111101010001110011110111101100,HEX:213D473DEC
Unknown 2 bit card,Binary:10
Unknown 1 bit card,Binary:1
Unknown 1 bit card,Binary:1
Unknown 1 bit card,Binary:1
Unknown 2 bit card,Binary:11
Unknown 1 bit card,Binary:1
Unknown 6 bit card,Binary:111111
Unknown 2 bit card,Binary:11
Unknown 1 bit card,Binary:1
Unknown 17 bit card,Binary:00000000000000000
Unknown 17 bit card,Binary:00000000000000000
Unknown 17 bit card,Binary:00000000000000000
Unknown 17 bit card,Binary:00000000000000000

Log entry:

34 bit card,10 bit preamble,Binary:0000001001 0000001000110101100101000000100101,HEX:2408D65025

This is full wiegand data, but card number is not 2408D65025, correct card number can be calculated, if we eliminate first and last bit from card number part:

• 0000001000110101100101000000100101 -> 00000100011010110010100000010010
• 00000100011010110010100000010010 -> 046B2812

I changed the settings of the unit to connect to another network, it did not connect to the network and now the device is undetectable via WIFI. I have attempted to factory default the unit using the jumpers as detailed in the "Read Me" I have the version without the button only having the 4 jumpers. any assistance on this would be appreciated as I was using this for checking outputs from custom data maps on readers.

Hi, I am attempting to test some modifications to the code (will PR when ready). However, I have been unable to get any image that I compile to run successfully. When I compile even master (unchanged) from this repo, the resulting flash attempt results in a "bricked" RFID Tool. I can use esptool.py to flash the last release bin and it works without issue. I assume the settings in my Arduino IDE are not accurate, but in spite of tweaking these settings a bunch of times, I can't seem to get something that works. Was hoping you could provide more information on what settings you are using to compile the official releases. I'm currently using Arduino IDE 1.8.15. I am using the board definition "NodeMCU 1.0 (ESP-12E Module)" from https://arduino.esp8266.com/stable/package_esp8266com_index.json.

Leaving all other settings as default (though I've also tried tweaking the FS/OTA settings).

One thing I've noticed, the last official bin from this repo looks like this when I look at the image with esptool.py:

python esptool.py image_info esprfidtool.bin
esptool.py v3.0
Image version: 1
Entry point: 4010f29c
1 segments

Segment 1: len 0x00568 load 0x4010f000 file_offs 0x00000008 []
Checksum: 2d (valid)

Whenever I generate an image it has two segments:

python esptool.py image_info esprfidtool.ino.nodemcu.bin
esptool.py v3.0
Image version: 1
Entry point: 4010f494
2 segments

Segment 1: len 0x00d84 load 0x4010f000 file_offs 0x00000008 []
Segment 2: len 0x00028 load 0x3fff20b8 file_offs 0x00000d94 [DRAM]
Checksum: c9 (valid)

Hi!

Do anyone know why i could have problems with esp-rfid-tools not logging properly?

Sometimes it manages to read a card but after I have checked the log and then tries to read a new card it does not work. I have tried to both clear the log and keep it. but that doesn't seem to make a difference.

Does anyone have a tip?

Thanks in advance for your help!

I am new to the ESPKEY.
Initial setup via 192.168.1.1 went good. Scanned a few cards successfully. I tried to load the latest firmware but after reboot, the device creates an access point ESPKey-xxxxxx where x=mac and this time up address 192.168.4.100
When I try to open the index at 192.168.4.1
I get a window that says "file not found"

Question - How do I reload a good config as a reset or default only loads the config I updated.

Do I need a programming device connected via serial to reflash?

Thankyou

If the number of bits is not a multiple of 4, strange results occur, because the conversion does not extend the start of the BIN value with zeroes, like most other conversion tools would.
See

Hello,
Is ESP RFID Tool able to replay or clone 13.56 MHz and 125 kHz RFID cards/tokens? Or it's used for different things. I am interested into buying one if so.
Best regards,
Ben.

See title. I'm assuming the module that started burning is the step-down converter. Had 3x4 battery packs with 1,5V batteries connected in series.

Board gets quite hot overall even when running with 12V - probably due to the WiFi module and the small board not being able to dissipate heat.

Just wanted to bring it up, as I think it should be mentioned in the README.md - in case someone plans to build this to carry in e.g. their backpack.

I've used this in the past and in the initial out of the box setting (1.02 I think) it works like a champ. When I upgrade to firmware 1.21 I get constant random data in the logs. Anyone else have this issue?

im not able to configure settings to capture Wiegand 34 bit. I cant get the whole DATA of EM4100.

If i convert Wiegand 26 bit i get only xxxxA1A2A3, (A1A2A3 = HEX DECIMAL) which u need to know the unkown hexdecimal (xxxx) the 4 first hex decimal, in order to clone EM4100 u need 10 HEXDECIMAL digits. its a shame that u cannot capture EM4100 in ESPRFIDTOOL.

and one thing buggy is that u need to ignore the parity bit and even parity like the first bit and the last bit should be ignored to get the correct of HEX DECIMAL. i have been studied this like 3 days in a row.

closed