Help with EFC5 and Panasonic

Carl · Post by **Carl** » Wed Apr 14, 2010 4:09 pm

I am having trouble with a Panasonic device upgrades.
I import the data from the clipboard with remote master and everytime that I change to the atlas URC-1056 it adds an EFC5 column...

Why is that?

The remote is not working and I know the upgrades file is ok because I have checked some EFC with learning and it was fine.

What am I missing?

Capn Trips · Post by **Capn Trips** » Wed Apr 14, 2010 5:01 pm

EFC5 is not the problem. The Atlas uses EFC5's so RM automatically calculates them from the data in the upgrade. As fro why it is not working, we'd have to have a look at your files.
What data are you importing to RM from the clipboard?
How have you "checked" EFCs with learning?

Provide links to the source of the data you are "importing", as well as upload all of your Rm and IR files that you are using (IR with learned signals, RM with source, RM modified fro your Atlas, IR you are uploading to your remote) and provide links to them here and someone will have a look.

Carl · Post by **Carl** » Wed Apr 14, 2010 6:56 pm

I have checked some of the button with a URC-8820 and the EFC matched the files from the website.

Here is the upgrade for the Panasonic SA-HT900:

https://www.hifi-remote.com/forums/dload ... ile_id=338

I'd like to upload my files but I'm not sure how...

I have 4 devices on the atlas and none of them have EFC5 so I'm just wondering why the panasonic multidevice(hacked) has EFC5.
All the other devices are working fine.

Capn Trips · Post by **Capn Trips** » Wed Apr 14, 2010 7:10 pm

Carl wrote:I have checked some of the button with a URC-8820 and the EFC matched the files from the website.

Here is the upgrade for the Panasonic SA-HT900:

https://www.hifi-remote.com/forums/dload ... ile_id=338

I'd like to upload my files but I'm not sure how...

I have 4 devices on the atlas and none of them have EFC5 so I'm just wondering why the panasonic multidevice(hacked) has EFC5.
All the other devices are working fine.

All of your upgrades - if properly prepared in RM - should have an EFC5 column, but that's immaterial. You say that your Atlas OCAP is sending the correct signals as learned by your 8820? Then they should work.

Upload all of those files I mentioned above, as well as the 8820 IR file with the learns from your Atlas for comparison.

Zip all of the files together.
Then go to the File section.
Navigate to the Diagnosis area.
Click on the "Upload" button near the top of the page.
The rest should be self-explanatory.
Then provide a link to your zip file here.

Carl · Post by **Carl** » Wed Apr 14, 2010 8:27 pm

I have checked the EFC5 column and you are right.
All my other devices have this column in remote master.
When it's transfered to IR I see the the 3 digits EFC number but for the Panasonic I see 5 digits instead of 3 in IR.

Here is the link for my files...

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

Sorry I don't have the file one learned from the remote because my friend took it home with him.I hope that what I gave you will suffice.

3FG · Post by **3FG** » Wed Apr 14, 2010 9:24 pm

Carl,
The IR file is missing the protocol for the upgrade. When you copy the upgrade in RM and paste it into the Devices tab of IR, you also need to copy the protocol from RM to the Protocol tab in IR.

May I suggest that you use this upgrade Panasonic HT instead? It uses a protocol that is already built into the Atlas remote, so you don't have to copy it over, and it saves space in the remote.

jimdunn · Post by **jimdunn** » Wed Apr 14, 2010 9:33 pm

RM 1.98 beta 7 doesn't give a protocol upgrade for Atlas 1056 with the OPs file (for me)

KM 9.19 does.

I'm guessing it's because RM thinks the PID is already in the Atlas 1056, which it is - so doesn't offer to upgrade it to this "hacked" version.

Regardless, I agree, using a resident protocol is better if it works.

Post by **vickyg2003** » Wed Apr 14, 2010 9:34 pm

Carl, is it a problem that the code doesn't work or that you don't like seeing the 5 digit codes. You are getting 5 digit codes because the device uses 2 hex digits.

If things are not working as advertised, the first thing is to see that the hex is the same as it was showing in RemoteMaster.

Also I am VERY suspicious that the protocol says "Hacked" but there is no protocol upgrade.

There is a PID 0042 in the remote, but is it the same pid as in this hacked protocol?

3FG · Post by **3FG** » Wed Apr 14, 2010 10:17 pm

Ah...
Somebody (that would be me!) was playing around with RDF files, and that's why pid 0042 didn't show up.

However, as Vicky and jimdunn suggest, it appears that the 0042 that is built into the Atlas is probably different than expected by the upgrade file. The Lookup Tool shows different EFCs, and the listed brands are MGA and Mitsubishi.

I'm pretty sure that it will be worthwhile to use a more modern upgrade.

Carl · Post by **Carl** » Thu Apr 15, 2010 6:14 am

I will put the protocol upgrade tonight and see if it works.
KM gives me the protocol so I can copy it to IR.

I may also try the one proposed by 3FG.

By the way, how do you know that 0042 is built into the Atlas?

Post by **vickyg2003** » Thu Apr 15, 2010 7:10 am

Carl wrote:By the way, how do you know that 0042 is built into the Atlas?

We read that in the RDF, but another clear clue was that there wasn't a "required protocol" in the Output Tab.

The latest versions of IR have a little icon in the toolbar has an Icon that looks like a magnifying glass with a piece of paper, or from the File Menu, you can select "Open RDF" and look at the Protocols section. While being clear as to whether the Protocol actually resides in the Remote is pretty easy, there is a more subtle problem. That's when the version of the protocol is differnt. In the protocols section you'll see a lot of entries with a colon( : ) next to a PID. The info after the : shows us which variant needs to be built. Often RDF's get out there without the proper variant being identified. This can give us some really "interesting" errors

.

I've addressed this problem a little clearer in this thread

Carl · Post by **Carl** » Thu Apr 15, 2010 7:23 pm

I have copied the protocol upgrade from KM and it's working now.
Thanks a lot for all your help.