JP1 Remotes

I looked at all of those learns and they all show a protocol and device code(s), so you shouldn't have any trouble converting them into upgrades. I had assumed that there were some signals in there that were unrecognized.

Here's a step by step...
http://www.hifi-remote.com/jp1/help/

Hi Robman and Binky,

I have successfully created .rmdu files using Remote Master for the Daytek and Insignia on the URC-8820 using the maps and rdf from the website.
I have tried the same thing on the Atlas using the 30003000 file from the file section and while the learned codes work, when replacing them with a Device upgrade (after deleting the learned keys) and assigning the appropriate device type the corresponding code, I am getting the functions on the wrong remote keys. It seems that the physical key mapping is completely screwed up. But at the same time, if I assign the learned keys manually in the learning section copying them over from a URC8820, they get mapped correctly in the Atlas. Any ideeas?

Thank you!

Hi Robman and Binky,

I have posted the DU and necessary files for the Insignia TV on an Atlas DVR Day that has the functions mapped to the improper buttons at:

https://www.hifi-remote.com/forums/dload ... le_id=3992

In addition, I've posted 2 upgrades that work fine, including the associated files, one for the same Insignia and one for a Daytek TV on the URC-8820 remote at:

https://www.hifi-remote.com/forums/dload ... le_id=3991

https://www.hifi-remote.com/forums/dload ... le_id=3990

Where did Binky get the codes for the buttons on your Atlas remote when he created the RDF? That information should have come from you. It sounds like the codes used for the button list in the RDF are incorrect.

Does this remote support macros? If so, you can use macros to determine the correct button codes.

Hi Robman,

If I use an URC-8820 to learn keys and I use ir to enter the codes in Atlas manually, using the learn section and entering the binary sequence, the keys get mapped correctly which makes me believe that the rdf contains the right addresses for the keys. I think the problems lays into how RM creates the upgrade and possibly the fact that it may use the wrong processor instructions. As Binky determined, the processor is a Samsung S3C8. I am not sure if RM can compile instructions for this processor. Any thoughts?

Thank you!

I know what Binky did to create most of the RDF, but the one part that is dependant on you is the list of codes used for the buttons, so I'd still like to know how the list was compiled.

Forget about the complicated process of transferring learned signals from one remote to another, just program a macro on the Atlas, download it and see if it displays correctly. If it does, great, if it doesn't, let's fix it.

Hi Rob,

I did what you suggested i.e.:

- Press <setup> till 2 blinks
- Enter 995
- Press macro key F1
- Press in a determined sequence 10 keys
- Press <setup> till 2 blinks
- Connect to JP1.2
- Download from remote with IR
- Inspect the macro section
- My F1 key shows the same key names exactly in the sequence I entered them.

The keys I chose do not work properly with the RM upgrade.

UPDATE: I've verified all the remote keys and they show correctly in the macro.

Thank you!

OK, it sounds like the button list is correct, so I'll double check the button map section. Actually, a more likely culprit is that the protocol you're using uses a different number of fixed bytes in the Atlas compared to what it uses in other remotes. Is it just the Insignia upgrade that isn't working properly? Does the Daytek one work OK? The Daytek uses the NEC1 protocol, so there's no chance that the fixed data has changed for that one, but the other one uses Aiwa which might have changed, I'll have to take a look.

Hi Robman,

I have tried the NEC1 on the Daytek and it has similar behavior. The keys are in the wrong position and most of the TV functions are missing.

Thank you!

Hi Robman,

Second post...

Something that may help would be the protocols below. These 2 protocols came in the Device section with the remote and correspond to standard protocols for Motorola cable boxes. I assume they added them later to the remote.

Protocol: 0476 / Cable

C4 00 FE FE FE E0 FF 00 80 40 C0 20 A0 60 E0 10
90 B0 70 F0 D0 30 50 98 88 2C AC 6C EC 48 C8 CC
0C 28 A8 5C DC 1C F8 78 B8 9C 8C 68 08 1C 9C E8
E4 14

Protocol: 1376 / Cable

C4 00 FE FE FE FE FE FD 00 80 40 C0 20 A0 60 E0
10 90 B0 70 F0 D0 30 50 98 88 2C AC 6C EC 48 C8
CC 0C 28 A8 5C DC D8 F8 78 B8 38 8C BC BC 3C 7C
68 02 1C 9C E8 E4 14 94 44 C4 24 A4 64

Thank you!

I just checked the Aiwa protcol and it hasn't changed, so there's something else up. I'll keep digging.

Hi Robman,

In addition to my previous 3 replies, please note that I have imported "RAW" the protocols above into RemoteMaster and it seems that the Protocol "GI Cable" is correctly identified but the Output is different than the original "RAW" so the algorithm does not revolve indicating an error somewhere on the way. I am not familiar with the structure of these upgrades so this is only ... my 2c

Thank you!

It appears that the RDF wasn't really complete. I have updated the digitmaps and buttonmaps sections. I doubt that this is the final version but it should get you alot closer.

https://www.hifi-remote.com/forums/dload ... le_id=3953

I've updated the RDF again to incorporate changes in the FixedData and Checksum sections.

Hi Robman,

Thank you for the update. I tried it and it doesn't work. From RM I added both new Device Upgrade Code and the Upgrade Protocol Code and the keys are now shuffled differently but not in the right position.

Thank you!