JP1 Remotes

Protocol Device SubDev OBC EFC Misc Decode UDB Function Sequence Key Panel DevName TopFreq Once Rept

NEC1 132 60 41 089 LEARNED 2 Main TV 38.381 34 2
NEC1 132 60 32 213 LEARNED 5 Main TV 38.381 40 0
NEC1 132 60 42 087 LEARNED 8 Main TV 38.381 40 0
NEC1 132 60 57 025 LEARNED 3 Main TV 38.381 40 0
NEC1 132 60 56 021 LEARNED 6 Main TV 38.381 40 0
NEC1 132 60 34 215 LEARNED 9 Main TV 38.381 40 0
NEC1 132 60 51 155 LEARNED 0 Main TV 38.381 40 0
NEC1 132 60 48 149 LEARNED 1 Main TV 38.381 34 2
NEC1 132 60 40 085 LEARNED 4 Main TV 38.381 34 2
NEC1 132 60 50 151 LEARNED 7 Main TV 38.381 40 0
NEC1 132 60 47 090 LEARNED `B2 Main TV 38.381 34 2
NEC1 132 60 49 153 LEARNED AV Main TV 38.381 34 2
NEC1 132 60 33 217 LEARNED `Power_Toggle Main TV 38.381 34 2
Gap-547-1322-12? 3 202 A3.C LEARNED chU Main TV 38.381 13 0
NEC1 132 60 35 219 LEARNED YES Main TV 38.381 38 0
NEC1 132 60 43 091 LEARNED U Main TV 38.381 40 0
NEC1 132 60 36 212 LEARNED D Main TV 38.381 40 0
Gap-547-1322-26? 242 220 200 F2.DC.20.3 LEARNED chD Main TV 38.381 33 0
NEC1 132 60 52 148 LEARNED L Main TV 38.381 40 0
NEC 132 60 59 027 LEARNED R Main TV 38.381 34 0
Gap-547-1322-22? 143 11 209 8F.4B.34 LEARNED Guide Main TV 38.381 29 0

I edited your post to delete some of what you quoted from DecodeCCF and all of what you quoted from CCF2EFC. You shouldn't dump that much program output into a post.

If there were some reason for us to look at that much detail from your CCF file (which in this case I think there isn't) it would be better to post a URL for the CCF file itself. If the CCF file doesn't already have a URL, you can upload it to our diagnosis area and post its URL there.

I think your device uses the same commands as the ADB3100 and someone already posted Slingbox files for that at:
http://www.hifi-remote.com/forums/dload ... 710cb2baa8

If you need to use the information from the CCF (if the ADB3100 isn't as close as I'm guessing):

1) Forget about CCF2EFC. DecodeCCF is better.

2) You need to figure out which signals in a CCF are the correct device and which are correct learns. Even if I didn't know the ADB3100 uses NEC1 132.60, I would have guessed those were the correct decodes. The NEC1 125 and Sony signals (that I deleted from your post) must be other devices, and the "Gap" decodes are bad learns.

3) For individual signals, all you need is the function name and the OBC number. The ADB3100 upgrade is posted as an rmdu file as well as Slingbox files. If you open that in RemoteMaster, you can go to the functions tab and compare the OBC numbers it has to the OBC numbers in your decodes. If any of your NEC1:132.60 decodes have OBC numbers that are different or missing from the ADB3100 file, you probably will want to edit the functions sheet and regenerate the .bin files.

i loaded the file in RM , the "Export Binary" is grayed out
i took the .bin files , but the Sling SW wan't load it
so i want to generate a new bin file

ronif wrote:i loaded the file in RM , the "Export Binary" is grayed out

When I load that file, Export Binary isn't grayed out.

I'm not sure what is going wrong for you. But many problems with RM for Slingbox are caused by RM failing to find the rdf files:

BINJU (Slingbox with UEI JU Chip).rdf
BINPL (Slingbox with UEI PL Chip).rdf
BINRV (Slingbox with UEI RV Chip).rdf

You should make sure those files are in the directory where RM looks for rdf files.

If you don't know which directory that is, open the RemoteMaster.properties file in NotePad or WordPad and look for the line that starts:
RDFPath=
That tells you which directory RM looks in for rdf files.

If you think that is the wrong directory:
1) Make sure RM isn't now running.
2) Delete that line from the properties file and save.
3) Restart RM and it will ask you to browse to the directory you want it to use for rdf files.

ronif wrote: i took the .bin files , but the Sling SW wan't load it
so i want to generate a new bin file

I don't know enough about Slingbox to answer that one.

I don't think generating a new bin file would give you a different result.

So I hope someone who knows about Slingbox is still reading this thread, rather than assuming I will answer your questions.

Roni,

Are you using the latest version of RM? If you and John are seeing different things when you load a file, you may be using different versions. Keeping up to date with the tools here is important.

Vicky

it seems that my Slingbox is using the RV Chip
and i can't find the RV RDF File anywhere....
in my SBAV Directory i have
SBAV-RV.sbav
SBAV-PL.sbav

ronif wrote:it seems that my Slingbox is using the RV Chip
and i can't find the RV RDF File anywhere....

Where did you look exactly? I just checked the current RDF zip file and verified that the RV RDF is there.

RM shows you the folder it is using for the RDF Path on the About screen (Help -> About)

ronif wrote:it seems that my Slingbox is using the RV Chip
and i can't find the RV RDF File anywhere....
in my SBAV Directory i have
SBAV-RV.sbav
SBAV-PL.sbav

The file you need is:

BINRV (Slingbox with UEI RV Chip).rdf

Check the directory where your other rdf files are, or get another copy of it from the zip file that Rob linked.

I was looking for a "SLING..." file..
that's why i missed the BIN...
any how , Israel YES works fine now