JP1 Remotes

Why do there appear to be two protocol numbers for StreamZap, is a fix imminent for the fixed data problem, and how do I get at the Com Skip button for 8910(ext) in KM?

I have one device (upgrade in File Section:Echostar UK "freeview" box) that uses the StreamZap protocol. KM states that this is protocol 01 23 but RM says it's 01 24. Both are, in fact, identical as far as I can see. My Device number is 34 and in KM I have to add 192 to this (see link) to correct the fixed data to be 1D - a minor flaw but no real problem. In KM, however, I can't get at the Com Skip buton to program an upgrade for my 8910(new, with extender) as it's greyed out. I switched to RM but there appears to be no ready way to correct the fixed data. I have managed a work-around by manually editing the device upgrade once it is in IR by altering the 8th hex pair to 1D but just wondered if this problem had already been sorted and I was missing something.

The official pid for this exec is $0123, so to sync up RM and KM you should edit the protocols.ini file.

To program a function to the COMM SKIP button in KM (for extended remotes only), you should assign a function to it in the Buttons sheet (it's on row 48). This is cause a keymove to be created.

The Robman wrote:To program a function to the COMM SKIP button in KM (for extended remotes only), you should assign a function to it in the Buttons sheet (it's on row 48). This is cause a keymove to be created.

Actually, I posted that after trying it first using KM v8.31, I just downloaded v8.33 and you're right, it is greyed out now. I just checked the version log and I see that Mark deliberately removed this button from the 8910 list, presumably because it was causing confusion for non-extender users.

Therefore, you should either use v8.31 or you should program the keymove in IR.exe

The Robman wrote:I just checked the version log and I see that Mark deliberately removed this button from the 8910 list, presumably because it was causing confusion for non-extender users.

IIRC, there was a discussion here regarding COMM SKIP in the unextended remote being unavailable, hence the change.

I'm not afraid to unprotect the sheet and make changes if you'll point me in the right direction (tried changes already, in fact, for other reasons just didn't understand it fully enough and kept coming across areas with hidden formulae).

As an aside, I have a KM tip - if you want to work on two upgrades at a time (perhaps when porting over to a different remote or to create two slightly different upgrades to try them out) you can create a copy of KM (call it "KM second instance" or something) and open you 2nd upgrade in that.

Mark Pierson wrote:IIRC, there was a discussion here regarding COMM SKIP in the unextended remote being unavailable, hence the change.

You are correct, in the un-extended remote you cannot re-program that button, but of course, with an extender you can re-program anything.

underquark wrote:I'm not afraid to unprotect the sheet and make changes if you'll point me in the right direction (tried changes already, in fact, for other reasons just didn't understand it fully enough and kept coming across areas with hidden formulae).

This should save you the trouble, here's a copy of v8.31...

http://www.hifi-remote.com/forums/dload ... le_id=2190

underquark wrote:I'm not afraid to unprotect the sheet and make changes if you'll point me in the right direction (tried changes already, in fact, for other reasons just didn't understand it fully enough and kept coming across areas with hidden formulae).

You should be afraid... be very afraid!

There's so much going on behind the scenes in KM that there's no easy way to modify it to do what you want. The easiest solution is to just create the keymove in IR. Alternatively, you can enter it on the Key Moves sheet using a raw hex button code of $2B as the Bound Key and "(upgrade)" as the Bound Device. Then copy the Keymove Code from the Setup sheet and use the Import button on the Key Moves tab in IR.

Mark Pierson wrote:You should be afraid... be very afraid! There's so much going on behind the scenes in KM that there's no easy way to modify it to do what you want.

I second that emotion, but what the heck, you can always download it again if you mess it up, so just for fun, take a look behind the curtain in KM and let us know what you thnk of it. I think most people here would run for the hills if they knew just how much work KM does. Not bad for something that's just a spreadsheet (to quote our friend Paul )

The Robman wrote:...take a look behind the curtain in KM and let us know what you thnk of it. I think most people here would run for the hills if they knew just how much work KM does. Not bad for something that's just a spreadsheet (to quote our friend Paul )

I thought that KM was just a spreadsheet and I thought I could use cells A18 thru D45 but I was wrong. Even the "space" to the left of the history comments is being used for some nefarious purpose . Basically I was trying to insert a bit of code that would time-stamp my upgrades e.g.: "Echostar T-101FTA for 8910x 916_2342" and found - to my peril - that there are really "no user sevicable parts inside" KM. Anyhow, it's been known for a while that 90% of spreadsheets with >150 rows (except, of course, mine) contain at least one error.
(q.v. http://www.uq.net.au/detective/EF-Error ... _1998.html)

I'm in the process of downloading the .WAV files for Echostar (there are 5 sets of several upgrades each) from the European OneForAll site. Would it be useful to group them all together (and then others can add to it with different upgrades)? What would be the best remote to download for (I don't mean that I actually have to possess the remote, just which one would give a download with the most meaningful button assignments without having to actually test the things)?

Oh, I feel quite confident that there are a good few errors lurking around in the mess that's behind the curtain of KM, and most of them have probably been there a while, but fortunately, fortunes are not being won or lost based on the results of KM.

As for the OFA downloads, I would suggest that you go with one of the Kameleons, probably the URC-8060, as they have the most buttons defined.

The Robman wrote:Oh, I feel quite confident that there are a good few errors lurking around in the mess that's behind the curtain of KM, and most of them have probably been there a while

Nah... I fixed all of them when I took over KM from you!

Actually, I'm pretty confident that KM is as bulletproof as we could get it. That's not saying it's perfect, but it's pretty damn close.

OK, so why have you put the same comment in cells H2/3 and H4? And how come the comment in cell F4/5 is so difficult to hover over? (like I bother to read the instructions most of the time anyway).

Go on Mark, put Scottie boy in his place.... !!!

underquark wrote:same comment in cells H2/3 and H4

I don't consider that a problem...

how come the comment in cell F4/5 is so difficult to hover over?

Because Mr. Gates & Co. made some sort of change to the button controls. Thay have a large transparent border that can't be modified. The trick with Excel is to hover over the comment indicator if you want to read the comment.

Mark Pierson wrote:

how come the comment in cell F4/5 is so difficult to hover over?

Because Mr. Gates & Co. made some sort of change to the button controls. Thay have a large transparent border that can't be modified. The trick with Excel is to hover over the comment indicator if you want to read the comment.

Mark, underquark is asking nicely for a special view, let's see how he likes it:
Tools/Options/View, click Comments and indicator