I have a programming holder with a 8mhz oscilator where i program the chip with USBasp or Arduino with ISP software, then i move it to the real transponder hardware where it have a 20mhz crystal. And if i want to reprogram i just move the chip between.

I think I'll need to do the same (I'll have a search on Google later in the week when I get the time).

From what I've found, all I do for the programming board is add a 8Mhz crystal between pins 2 and 3, and two 22pf caps to ground. Does that sound correct?

I'm completely new to programming these chips.

Yes that sounds correct. I have had some chip that didn't work with crystal during programming, that needed a real oscillator (not the same thing as a crystal), don't know what happen to that chip. But in normal situations it will work.

I've just tried programming another chip with the simple programming board. Same result as previous efforts, AVRDUDESS reports a success, but verification fails. And now the chip is not responding when I click "detect" (I did not write any fuses this time).

Guess I'll have to sit down and properly learn about these devices (or go down the PIC route, I've successfully programmed those in the past).

Hello.

I Have being studing this post. I am from Spain and I Have built one transponder using the Condac's design, it works properly but I don't know how to solve the ghost id number. Has anyone solve this problem?
Does anyone find more unique id number apart from the 3 that are posted in this threat?

Thanks to all and congratulations to howardcano and condac. Great Job.

I should have stayed in school.

I have found this picture. did anyone tryed the other numbers from the list?

The system says to me that I can not post URL to other sites because I need to made a certain number of post before doing that.

Please Excuse me. But this is the only way to do this with my user. If any admin can post this picture please help me to do this.


You only have to write h t t p / / before the next text to watch it.



k31.kn3.net/2/D/A/B/E/8/7AF.jpg

Hola yo estoy trabajando sobre un transponder AMB compatible para un cliente mío y quisiera compartir con todos mi experiencia hasta el momento.
Actualmente mi desarrollo aún no puede ser captado por el decoder pero espero que compartiendo mi desarrollo con ustedes pueda a la vez encontrar el problema

Hi again, not sure to post my question here or in the Decoder-part...Let's see what comes out; I am in the process of building a same type of decoder as is used to decode the simple AMB-type transponders for which the whole threat was initiated: BSK-coded AMB-MX transponders used in motorcross events. I have my system operational for the regular AMB-transponders (see few posts of my implementation here as well as for my decoder in the other threat).
Using a Rohde&Schwarz FSIQ analyser and a AMB-MX transponder, we discovered a row of bits that appear in every burst. This seems to us as if it is the System-ID. The remaining bits in every burst is every time different. The FSIQ analyser can be programmed to trigger on this 'preamble', so we were able to log the complete burst. Sampling 10 bursts showed 10 different messages (but of coarse 10 times same preamble). We tried to match the transponderID to the 'message' bits, but did not succeed...
Our question is: In case an encryption is used, would the message be every time different despite the transponderID is every time the same? Is the coding probably the 'Convolution Code' that was meantioned earlier? If so, can someone share info how to decode the messages we have logged?
Thank you for taking time to answer, Gerrie

And finally, i understood, how the mylaps encryption protocol works.
I'ts not 100%, i mean, what i can't make ANY 7-digit number.
At this moment i have list of 9000+ brutforced numbers, some of them are very cool (like 7707077 or 6668885).
Numbers was brutforced at decoder with 4.4 software on board.

Like that:

That's excellent progress! Payalneg: The master of Viterbi!

Nice!!

This means that cross compatibility is near?