JP1 Remotes

UEI have recently updated their internet download upgrades and I've come across the Nokia32 protocol. It has an ID of 0173h and is already incorporated in some of the newer OFA remotes.

Whilst someone on this forum had developed a Nokia32 protocol, it was a bit fiddly to use because the fixed data ...

I have a couple of devices that use the Nokia32 Protocol. As yet, both RM and KM do not support Nokia32.

However, someone has written a device upgrade for a Galaxis satellite receiver, which also works with several UK DTT freeview boxes.

UEI have made a setup code 1111, but this only works with ...

Ube,

Is your remote a 7544-B01? Mine is, with a 2K EEPROM, and works with the limitations I mentioned earlier. Just wondering if yours is a newer or different version.

Duncan

I tried to alter the Nokia 32 protocol to have two fixed bytes and three variable bytes. I learned it back in to another remote and it didn't see it as a recognised protocol. I have learned numbers 0-9 on my OFA5 and uploaded the file https://www.hifi-remote.com/forums/dload.php?action=file&file_id ...

Ube,

When I received my 7544 it had no JP1 connector or EEPROM fitted. I put in a connector and 2K EEPROM myself. Did you have to do this or did yours already have them fitted? I ask because I think with this model they usually come without the connectors/EEPROM and only get fitted if it has been ...

The guy who started the original thread on this never responded to my last post , maybe you could do the experiment requested instead.


Actually Rob, the guy did respond and its on page 2 in the thread

https://www.hifi-remote.com/forums/viewtopic.php?t=5010&postdays=0&postorder=asc&&start=15

So ...

Been looking around the forum, and found this post https://www.hifi-remote.com/forums/viewtopic.php?p=21195#p21195 which explains how to convert the fixed data and obcs to the required hex for the upgrade. I've used this info successfully before when converting obcs from the learned data to the 4 ...

I've just bought a PVR and I learned the signals. It uses the Nokia32 protocol which I have used before either using the Galaxis sat protocol or using setup code 1111. The signals I have learned have exactly the same Device, Sub-Device, OBC, HEX and EFC, but the Misc data is different. On the ...

Deleted the [DigitMaps] section in the RDF. Using RM the numbers now work, but some other functions are incorrect. When I earlier used KM, all the other functions were fine.

Also I have found that sometimes after doing keymoves, uploading to remote and downloading again causes the keymove/macro ...

Thanks Rob,

I checked all the keycodes are they're fine.

I made a new upgrade, this time using KM rather than RM, because RM also uses the RDF file and wasn't sure whether this would confuse things further.

First I made a simple upgrade, assigning 1, 2 & 3 to the corresponding buttons on the ...

Just created a full device upgrade and it doesn't work properly. Some keys are OK, some in the wrong places and some just don't work.

It was created in RM 1.30. The upgrade is a NEC1, Dev 4, Sub 123 and the upgrade code is;

Upgrade code 0 = 27 cd (SAT/1997) TM5000CI (RM v1.30)
5a 17 36 fe ff 20 ...

That's made it work! I've done a keymove and a basic device upgrade and they're both OK. I'll do a full program up of the remote and report back.

I notice you changed the AdvCodeAddr, EepromSize, FixedData and removed the SpecialProtocols. The [Checksums] was set as [Checksums2] in the OD4LOD40 ...

Rob,

I altered the NAME in the GENERAL section in your RDF so that I would be sure which RDF was being used.

I followed your instructions as above and the first two bytes have changed in the raw data.

Step 2 data first 32 bytes;

5E A1 4F 44 34 4C 4F 44 34 30 02 2C 10 51 23 4F
31 F7 00 00 0F 14 ...

underquark,

No, I've tried it. My remote has a B01 chipset. I assume the RDF was written for the B00 version.

Rob,

I've double checked the RDF and I was using yours.

If I make any changes on the remote (setup codes or key moves) it works fine. If you do the same from IR and upload it to the remote, the remote always ignores it.

I did a key move on the remote, which worked, examined the raw data and saw ...