Seca-keys confusion



[font size="1" color="#FF0000"]LAST EDITED ON 13-Feb-01 AT 09:29 AM (GMT) by chris (admin)[/font][p][font size="1" color="#FF0000"]LAST EDITED ON 12-Feb-01 AT 03:08 PM (GMT)[/font]


How can I ever know which keys are the right ones for my "auto-updating" card? If each author has his/hers very own conversion system?

By the way this way of doing business, has already cost me a lot of headaches:

Many key sites are not current, and those which claim to be are not( at least for my card) applicable.

Why is it that an eight 2-byte hexadecimal code is converted into a nine 4-digit remote code?

In my case only an eight 4-digit remote code did work.

How can the right keys be found, and what do 0C-, 0D-, 0E-codes mean? What are service keys for?

Is the hex-key component universal , and do the remote-key converters produce different remote codes?

For example:

Key 0D: xx xx xx xx xx xx xx xx converts into

xxxx xxxx xxxx xxxx xxxx xxxx xxxx xxxx xxxx

For my card I can not apply this information, it does not function.

What did work was: xxxx xxxx xxxx xxxx xxxx xxxx xxxx xxxx

So where am I able to find the right keys, converter for my card.

Cheers, JBP



I am looking for eight 2-byte hex hex files.
Can someone help me?
I have the following problem:
I can't use Secanix formatted files they give as a result a empty provider list!
I am using a Mob Dick Programmer and various software.
At the moment I am workiing with pic.exe for the pic and winphoenix for gw for the eeprom!