JP1 Remotes

OK, I added a JP1 connector, jumper wire and EEPROM to a 6000 series remote. The EEPROM I had handy was a 256 byte device, 34C02 stolen from an old SDRAM memory module.

<Setup> 981 gives four LED blinks.

The IR program recognizes the remote, but keeps complaining about the wrong EEPROM size and an invalid checksum. I keep attempting to purge the memory, but still get this checksum error. The EEPROM still probably has data in it from the memory module.

Questions:

1. Is a 256 byte EEPROM supported, or do I need to get a 2K byte device?
2. Does <Setup> 981 erase the EEPROM?
3. Does "Purge Memory" erase the EEPROM?
4. Should Raw Data be all "FF"s after Purge Memory?
5. Is there a document of blink codes? (After attempting an operation in IR, the remote gives two short blinks and one long one. )

Note: The 34C02 EEPROM has a software write protect feature in it. It is possible that the EEPROM was write protected before I got it. I can pull another 256 byte EEPROM from a module, but if 256 byte is not supported then its a wasted effort.

Thanks.

---- Steve

banjo wrote: 1. Is a 256 byte EEPROM supported, or do I need to get a 2K byte device?

You can't do anything useful with a 256 byte EEPROM in a 6011. I don't know whether an edited RDF file and maybe some checksum tricks would be enough to store basic settings in that eeprom, or whether it's totally nonfunctional. But in any case it isn't useful.

The only size that gives you simple access to all the JP1 capabilities is 2K byte. You can have everything but the extender with 1K byte. You can have more KeyMove and upgrade capacity with an eeprom larger than 2K byte, but there is some extra work required in initial setup.

banjo wrote: 2. Does <Setup> 981 erase the EEPROM?

It just initializes some fields within the eeprom.

banjo wrote: 5. Is there a document of blink codes? (After attempting an operation in IR, the remote gives two short blinks and one long one. )

That one means the remote has reinitialized and is working, but has decided the eeprom is defective and has switched to a non eeprom mode of operation.

It can mean that the eeprom merely has invalid contents. It doesn't necessarily mean the eeprom is defective. But the remote has made the operating decision it would make if the eeprom were defective.