JP1 Remotes

Posted: **Fri Oct 22, 2010 8:48 am**

Gee Rob you sure are fast!

I was just getting the rounding done, and you already have the upgrade up.

I popped open the upgrade in RM 2.0 Preview 7, and think that there might be something wrong with the RDMU file. The upgrade is opening as a 2byte upgrade with byte1 always 0. I've worked behind you long enough to believe you would never throw extra bytes into an upgrade.

I did get some errors when I opened the file, so maybe the error is on my end, but something isn't looking right.

Edit: I opened the RDMU in notepad and sure enough every function is showing 2 bytes of hex with the first byte of 0. I also see that there are more than 8 bits of variable data in the signal..... So it definately is supposed to be a 2byte upgrade, the 1st byte just seems to have been lost.

Posted: **Fri Oct 22, 2010 10:13 am**

Btw, I got tired of all the manual work involved in copy/pasting data from ExportedUEI.txt over to IR.exe so I created a spreadsheet to do the work for you.

Here it is:
https://www.hifi-remote.com/forums/dload ... le_id=9051

Hopefully the comments in the file description, along with the comments in some of the cells make it self-explanatory, but if you have questions, please ask them.

Posted: **Fri Oct 22, 2010 10:55 am**

The_Robman wrote: Btw, I got tired of all the manual work involved in copy/pasting data from ExportedUEI.txt over to IR.exe so I created a spreadsheet to do the work for you.

I get really tired of that work too!!! It is really a tedious exercise so I was really looking forward to the automation via a spreadsheet. I tried opening your spreadsheet, but with or without the learns that I extported from IRScope, the "work" sheet has #Name? in columns C and D and the output area where the learned codes are supposed to go also says #Name?

I'm using an older version of Excel (2000), do you think that might be the problem?

I don't want to distract you from the Google project, but I'd really like to get the learns into IR so I could do the rounding!

Posted: **Fri Oct 22, 2010 11:17 am**

Yes, I do think that's the problem because I also use Excel 2000 at home and I often can't open spreadsheets that I create at work there too.

Here's how you can fix it up, or create a new one.

1) You need three tabs: Input, Work, Output

2) Work tab, cell A1, enter and repeat to cell A67:
=IF(ISERROR(FIND(":",OFFSET(Input!$A$1,((ROW()-1)*2),0))),"",LEFT(OFFSET(Input!$A$1,((ROW()-1)*2),0),FIND(":",OFFSET(Input!$A$1,((ROW()-1)*2),0),1)-1))

3) Work tab, cell B1, enter and repeat to cell B67:
=TRIM(OFFSET(Input!$A$1,((ROW()-1)*2)+1,0))

4) Work tab, cell C1, enter and repeat to cell C67:
=IF(TRIM(B1)="","",DEC2HEX(ROW(),2)&" 20 "&TRIM(MID(B1,7,999))&" ")

5) Work tab, cell D2 (two), enter and repeat to cell D67:
=D1&C2

6) Work tab, cell D1 (one), enter: =C1

7) Work tab, cell E1 (one), enter: =D67

8) Output tab, pre-populate the "A" column with the code data below.

9) Output tab, cell A65 enter and repeat to cell A256:
="F"&DEC2HEX(ROW()-65,2)&"0: "&LEFT(MID(Work!$E$1,((ROW()-65)*48)+1,48)&"FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF",48)

10) Output tab, cell A258, enter: [Notes]

11) Output tab, cell A259 enter and repeat to cell A341:
="$50"&DEC2HEX(ROW()-259,2)&"="&IF(TRIM(Work!A1)="","(no note)",TRIM(Work!A1))

Code: Select all

EC00: 31 30 36 33 31 30 36 33 4E B1 00 00 10 00 20 00
EC10: 30 00 40 00 50 00 50 00 50 00 50 00 50 00 00 00
EC20: 02 5C 00 FF FF FF FF FF FF FF FF FF FF FF FF FF
EC30: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
EC40: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
EC50: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
EC60: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
EC70: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
EC80: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
EC90: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
ECA0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
ECB0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
ECC0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
ECD0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
ECE0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
ECF0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
ED00: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
ED10: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
ED20: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
ED30: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
ED40: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
ED50: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
ED60: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
ED70: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
ED80: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
ED90: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
EDA0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
EDB0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
EDC0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
EDD0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
EDE0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
EDF0: FF FF FF FF FF FF FF FF FF FF FF FF FF 10 10 22
EE00: EE 04 EE 04 00 00 FF FF FF FF FF FF FF FF FF FF
EE10: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
EE20: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
EE30: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
EE40: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
EE50: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
EE60: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
EE70: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
EE80: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
EE90: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
EEA0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
EEB0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
EEC0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
EED0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
EEE0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
EEF0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
EF00: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
EF10: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
EF20: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
EF30: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
EF40: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
EF50: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
EF60: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
EF70: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
EF80: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
EF90: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
EFA0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
EFB0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
EFC0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
EFD0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
EFE0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
EFF0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF

Posted: **Fri Oct 22, 2010 11:52 am**

Btw, if I do create an Excel 2000 version of this, please post it so I can use it at home. Otherwise, I will create one myself either this evening or tomorrow and I'll post it.

Posted: **Fri Oct 22, 2010 12:23 pm**

vickyg2003 wrote:I popped open the upgrade in RM 2.0 Preview 7, and think that there might be something wrong with the RDMU file. The upgrade is opening as a 2byte upgrade with byte1 always 0. I've worked behind you long enough to believe you would never throw extra bytes into an upgrade.

I did get some errors when I opened the file, so maybe the error is on my end, but something isn't looking right.

Edit: I opened the RDMU in notepad and sure enough every function is showing 2 bytes of hex with the first byte of 0. I also see that there are more than 8 bits of variable data in the signal..... So it definately is supposed to be a 2byte upgrade, the 1st byte just seems to have been lost.

It's impossible to know when RM will import a Manual Settings upgrade properly. You're right, there should be something in that column. I just re-created the data and re-loaded the RMDU file.

Posted: **Fri Oct 22, 2010 12:43 pm**

The Robman wrote:Btw, if I do create an Excel 2000 version of this, please post it so I can use it at home. Otherwise, I will create one myself either this evening or tomorrow and I'll post it.

Rob your spreadsheet opens just fine, it was the Analysis ToolPak stuff that was giving me all the "#Name?" stuff. I had that turned off from some testing.

It works as advertised. I'm looking forward to using this spreadsheet to get past all the manual rounding.

It's impossible to know when RM will import a Manual Settings upgrade properly. You're right, there should be something in that column. I just re-created the data and re-loaded the RMDU file.

Yes, when I do a manual upgrade I do it directly in RM for exactly that reason.

Posted: **Fri Oct 22, 2010 1:55 pm**

vickyg2003 wrote:Yes, when I do a manual upgrade I do it directly in RM for exactly that reason.

I've never been able to start a manual upgrade in RM, plus I still don't trust that it won't blank out all my data if I press the wrong button or something, so I always start them in KM and then import them.

Posted: **Fri Oct 22, 2010 4:31 pm**

The Robman wrote:
vickyg2003 wrote:Yes, when I do a manual upgrade I do it directly in RM for exactly that reason.
I've never been able to start a manual upgrade in RM, plus I still don't trust that it won't blank out all my data if I press the wrong button or something, so I always start them in KM and then import them.

We'll I 'm equally uncomfortable in both RM and KM. I often start upgrades in RM, since RM lets me work directly with the hex so it is a lot easier, until of course you do something to get the whole thing to erase, but usually by the time I do that I have pasted all the data into a KM sheet.

I always create a KM sheet, since it is the "universal" upgrade form, and all of mine have imported into RM alright. But I've been around here long enough to know that quite often they will not import correctly.

Posted: **Fri Oct 22, 2010 5:29 pm**

I'm totally comfortable with RM when I'm creating an upgrade using a standard protocol and there's no chance that I'll want to switch to a combo version or change the selected protocol for any other reason. But if there's even the slightest chance that I'll need to change the selected protocol, I'll use KM because RM will often blank out all of the data in the Functions sheet when you change protocols, whereas KM won't.

But when it comes to manual settings, RM just isn't up to snuff yet, so I always create those in KM and then import them into RM.

Posted: **Fri Oct 22, 2010 5:54 pm**

The Robman wrote:I'm totally comfortable with RM when I'm creating an upgrade using a standard protocol and there's no chance that I'll want to switch to a combo version or change the selected protocol for any other reason. But if there's even the slightest chance that I'll need to change the selected protocol, I'll use KM because RM will often blank out all of the data in the Functions sheet when you change protocols, where as KM won't.

Since RM is so light weight that I usually open a second copy of the RM file so I have the function to repaste if things go blank. On my old system, KM just chugs and chugs before it will open.

But when it comes to manual settings, RM just isn't up to snuff yet, so I always create those in KM and then import them into RM.

Well there is the LSB/MSB thing in KM shines at. That kind of evens out the direct editing of the hex that RM lets me do.

Is there anything else that KM can do that RM can't when it comes to manual settings?

Posted: **Fri Oct 22, 2010 6:21 pm**

The first problem is that I don't know how to *start* a Manual Settings upgrade in RM. Then, to make any changes you have to mess around in the Advanced box, whereas in KM everything is out in the open.

Bottom line, it's just so easy to do a manual upgrade in KM so that's what I use.

Posted: **Fri Oct 22, 2010 9:21 pm**

The Robman wrote:The first problem is that I don't know how to *start* a Manual Settings upgrade in RM. Then, to make any changes you have to mess around in the Advanced box, whereas in KM everything is out in the open.

Well, I didn't find either KM or RM to be intuitive when it comes to Manual Settings. Getting started is pretty easy though. You go to the advanced menu and say Import from keyboard. In RMIR its a little easier, because it reads the PID from the upgrade, while in RM you need to type in the PID.

Bottom line, it's just so easy to do a manual upgrade in KM so that's what I use.

Well since you've had your hands in the guts of KM, I suspect you'll always be more comfortable with the Excel version. They both are mysterious to me. I don't know my way around excel or java.

I found RM to be just as easy in KM except for that LSB/MSB manipulation when you want to figure out if the OBC's would make more sense one way or the other.

Posted: **Fri Oct 22, 2010 9:51 pm**

vickyg2003 wrote:Getting started is pretty easy though. You go to the advanced menu and say Import from keyboard. In RMIR its a little easier, because it reads the PID from the upgrade, while in RM you need to type in the PID.

I suspect you mean File > Import from Clipboard

But even so, what exactly are you importing when you're starting a brand new manual upgrade. Same question for RMIR.

Posted: **Fri Oct 22, 2010 10:34 pm**

The Robman wrote:
vickyg2003 wrote:Getting started is pretty easy though. You go to the advanced menu and say Import from keyboard. In RMIR its a little easier, because it reads the PID from the upgrade, while in RM you need to type in the PID.
I suspect you mean File > Import from Clipboard

No I don't know what that one does,

I mean Advanced >Manual Settings [Import Protocol Upgrade]
That imports the clipboard and assigns it to the proper processor type. I thought it said import from clipboard, but it actually says Import Protocol Upgrade.

1)In RM, Select Advanced->Manual Settings from the Clipboard
2) In PB, you copy your protocol.
3)Switch over to RM and press [Import Protocol Upgrade],
4)In RMIR it pulls the protocol Id from the clipboard, in RM, you have to type in the protocol ID.
5)Check the appropriate boxes and press ok.
6)Switch to the Setup Tab
7)Select Manual Settings

JP1 Remotes

IRScope decoder spreadsheet