JP1 Remotes

I'm still having some issues with the Atlas extender and the 1056 (likely user error ).
The default device macros on the Atlas extender didn't meet my needs. I was having problems getting them to work properly. After reading the extender documentation I set all device macros to the basic configuration in that documentation ...

CBL - M_CBL; C_CBL; V_CBL; T_CBL; O_CBL
TV- M_TV; C_TV; V_TV; T_TV; O_TV
(etc. for other three device macros)

Very strange results when uploaded to remote ...
CBL - blink CBL button and executes a CBL/Last action. M/C/T/V all set to CBL device ... couldnt test O
TV - blinks CBL .. V/T set to TV device, M/C set to CBL device
AUD - blinks DVD ... has strange results
etc.

What am I missing?

We really need to see your IR file to answer.

TheGMan wrote:
What am I missing?

Definitely need the IR file - but just to check - you are using the RDF that came with the extender right? (NOT the one in the big RDF zip file)

xnappo

Sweet ... and thanks for all the help, this community rocks!

I believe this is the link
https://www.hifi-remote.com/forums/dload ... le_id=8518

Well, I don't see anything obviously wrong. But I think I have the wrong RDF since I do see some strange key names (Key202?). Are you certain the extender version you loaded with extinstall matches your RDF version?

One thing you can do is delete most of those devices (and one protocol) that came pre-loaded (keep the extender related ones). That will free a ton of memory.

Well, I can't definitively state what's up, but when I try to open your file, I get a fixed data conflict, indicating that you still have an RDF problem. (I do NOT get that fixed data conflict when I open it it RMIR, however)

Further, your CBL device macro is weird - not like you described:
With nothing assigned to the DeActivate button (except in TV mode), and Phantoms 9 and 10 (no keymove is evident) that macro would not be expected to function properly.

Hard to tell what you may have done to get there.

Also, why do you have all of those Device Upgrades in there?! Holy cow they're eating up a lot of memory (although in principle that should not be causing your problems I as a general rule delete all unnecessary upgrades from my memory - you have them saved in your initial download, right?)

In particular, the TV/2202 upgrade calls on Protocol 01F9. This is the same protocol ID used by the LDKP Special protocol. Perhaps there is some weird interaction between that upgrade (even though you're not using it) and the protocol upgrade.

Capn,

I got the same weirdness when I open his file with my 2.03 RDF. However, when I got the 2.10 RDF, everything looked like he said.

I would look in your RDF folder and ensure that you have only ONE RDF for the 3A333A33 OCAP (version 2.10) and delete any other superfluous 3A333A33 RDFs that may have crept in there. Similarly there should be only one 30333033 RDF for the unextended OCAP (there should be another 30333033 and 3A333A33 RDF but NOT for the OCAP, but instead for the "Atlas 5 day". Those are OK. Just make sure that when IR asks you which RDF to use, you pick the OCAP one).

Then I would open the original saved virgin downloaded file in IR, and delete all of the Device and protocol upgrades and run Extinstall from the File menu in IR, saving it under a new name. Then add your upgrade and create your macros and give it a whirl.

mdavej wrote:Capn,

I got the same weirdness when I open his file with my 2.03 RDF. However, when I got the 2.10 RDF, everything looked like he said.

I have ONLY the 2.10 RDF on my machine and no other, so I cannot explain what's going on.

Thanks all ... back in business. It was some type of problem with me using the wrong RDF file. I did as instructed ... removed all incorrect ones and re-did everything. Seems to be functioning as designed.

*does happy dance*