Open Source Hitag Programmer

[nico2786]

nico2786

The data from the first readings the previous post are read first time without error and without any wasted ISRcnt, please see the IDE taken from the ISRcnt data.
11111 0000 1010 1000 0111 0000 1110 0001 0010

AES Hitager version 1.0.1.26848
arduino version 2

Sending: o
adapt target:1A adapt samplingT:B6 adapt readval:FF RFON
Sending: i05C0
transfer
ISRcnt:3D

1______1_____1_____1_____ 1__0_____0_____ 0_____0_ _1__0__1__0__1__ 0_____0_____0____

38, 25, 38, 27, 36, 27, 36, 27, 42, 57, 32, 31, 34, 29, 32, 39, 64, 63, 64, 63, 66, 59, 32, 33, 30, 33, 30,

_0__1_____1_____1__0_____0______0_____0__1_____1__ ____1__0_____0_____0______0__1__0_

37, 60, 31, 32, 31, 40, 59, 34, 29, 32, 33, 30, 39, 58, 33, 32, 31, 40, 59, 32, 29, 32, 31, 30, 39, 64, 61,

____0__1__0_____STOP

30, 37, 66, 57, 40, 241, 0,
X
RESP:0A870E12
EOF

The second set of data from the newer software is correct up to 321 (stop) but carries on collecting nonesense interrupts.

The 2 tests were done using same tag in fixed position, same iprog reader, same arduino, only arduino ino was changed and original/ newest AES Hitager versions.
Everything the same, but the adapt_samplingT values are very different, someone has changed the samplingT program, why?.

This may be causing your error.

I use a software from the official mirror https://github.com/kivijakola/hitage...tager-hardware

For the test I load arduino project and execute the Hitager

If you suggest other version please share...

I'm available if I can be of help

Thanks

[nico2786]

I did a series of tests. Maybe it's useful.
Using multiple arudino mega cards and multiple iprog I noticed that the delay function went crazy, for example delay(1000) is maybe less than 50ms and not fix time.

Configuration as per specification in https://github.com/kivijakola/hitage...tager-hardware

arduino mega + iprog

[GlennGlenn]

nico2786
I'm sorry I can't help with your Mega setup, I only ever used Arduino Nano with AES Hitager and iProg v1.2 reader.
Have you tried reverting to the early versions of Arduino ino and AES Hitager with your Mega and iProg???.
If the problem is cured then the software has error, if not cured then problem is Mega (any Mega).
You should try this simple test to pinpoint fault.
Glenn

[checcogame]

BMW Hitag2 eeprom read/write should now be working! Test version attached.

Hello i ve to ask something of your software...can you reply me please?

[GlennGlenn]

Hi
I am not the maker of the AESHitager software but if you post your question about the software other users can maybe help you.

[cclaireadrianne]

I'm glad to see the interest in Open Source Hitag Programmers! It's a fascinating project. While you're delving into this, I thought you might find this blog post on satisfaction guarantees useful: https://claspo.io/blog/satisfaction-...-attention-to/. It's not directly related, but it's always essential to ensure that any development or programming project aims to satisfy users' needs and expectations.

[GlennGlenn]

This is not directly related as you stated, it is not even indirectly related, it is a business policy and a ridiculous ploy to sell something on a hobbyist forum.
MODERATOR, PLEASE REMOVE THIS MARKETING POST.

[pispo]

Hi!!

First of all thanks to @rellullapaasee for all!! (design + dev +...)
I need some help. I am programming a VVDI Key with RF capabilities (Super Remote series, XEMQB1EN). My original key is a PCF7946.
First I change the UID in mem and set the type (ID7946). Then I write with the programmer (write all pages) and leave it as the original one.
The transponder part is working superb but the RF not. I am doing captures with RTL-SDR hardware and no transmission happens.

Is there any step needed to activate/sync/... in VVDI key to load such info? I have tried to remove the battery as well but it does solve anything.

Thanks to all contributors for your work!

[pispo]

Hi!!

First of all thanks to @rellullapaasee for all!! (design + dev +...)
I need some help. I am programming a VVDI Key with RF capabilities (Super Remote series, XEMQB1EN). My original key is a PCF7946.
First I change the UID in mem and set the type (ID7946). Then I write with the programmer (write all pages) and leave it as the original one.
The transponder part is working superb but the RF not. I am doing captures with RTL-SDR hardware and no transmission happens.

Is there any step needed to activate/sync/... in VVDI key to load such info? I have tried to remove the battery as well but it does solve anything.

Thanks to all contributors for your work!

In Xhorse App there is a "Special Function" called "Set type of VVDI wireless remote" with values "ID11, ID12, ID13, ID7936, ID7946, ID47/ID38". So I need to replicate such functionality in hitager. Anyone that can help me with a new ComboBox+Button that "Set Wireless Type"?

[wakawaka]

Wonder would this work reading a Mazda key... with details of PCF7952A / HITAG 2 / 46 CHIP.
FCC ID KR55WK49383
Some listings specify it as crypto chip id 46, some say 4D63 80 bit.

[GlennGlenn]

Hi
I think further development of Hitager is long gone.
For your problem;
Page 2, high 4 hex bits should determine the wireless remote type.
Simply transfer the page 2 (****4F4E) from your XEMQB1EN to the superchip.
GlennGlenn

[AudiS4]

Anyone know if this would work with a pcf7991at? I have a 2015 audi q7 EIS that I want to copy the data over from one bad unit onto a used unit.

[GlennGlenn]

Hi
Not quite sure what you are trying to do.
The PCF7991AT is the NXP receiver chip that is in the IMMO.
The Hitager system has the same function as the PCF7991AT but speaks to all Hitag2 transponders.
If you mean, will the Hitager work with your PCF7991AT chip connected so it can speak to transponders, yes definately.
There are many other interfaces that are ready to connect without any building.
Glenn