JP1 Remotes

mr_d_p_gumby · Posted: Fri Oct 08, 2010 11:49 am Post subject: keymap-master v9.21 available!

The latest version of KM (v9.21) is available.
Changes include:

Added NEC 4Dev Yamaha Combo to allow for Yamaha custom signals(pcode for S3C8 and HCS08).
Added RC16/18 pcode for NEC 4Dev Yamaha Combo; revised HCS08 pcode.
Fixed bug in pcode for XMP (JP1) on older S3C8 remotes.
Modified Fujitsu protocol to correct fixed data.

_________________
Mike England

JP1 Group at Yahoo!, JP1 Files Area

andyross · Joined: 13 Jun 2004 Posts: 261 Location: Aurora, IL

Noticed a quirk with updating "XMP JP1" on a 6131nw and 8811. I noticed that the actual protocol is stored in the .txt file, but when I load it, KM updated it to the new version. When I go to save, it says nothing was changed and do I really want to save?

Why does it store it in the TXT file if it will change it automatically without warning? And if it does change, why not catch it so it's saved in an updated file?

mr_d_p_gumby · Posted: Sat Oct 09, 2010 10:56 am Post subject:

KM might save it in the TXT file, but it does not use that saved information when presenting a protocol upgrade. I don't specifically know why it saves the protocol in the TXT file, but there are a number of items saved that are never retrieved from the file. I suspect this was done originally to help in debugging. In any case, since it does not use the information, it does not consider it as a valid change to be flagged for saving.
_________________
Mike England

JP1 Group at Yahoo!, JP1 Files Area

The Robman · Posted: Sat Oct 09, 2010 11:29 am Post subject:

The two upgrade blocks are saved in the text file so that someone can, as a short cut, grab the upgrade without needing to load it into KM first. This is not meant for a regular user, it's meant for an expert that is trying to zero in on something quickly.
_________________
Rob
www.hifi-remote.com
Please don't PM me with remote questions, post them in the forums so all the experts can help!

ElizabethD · Advanced Member Joined: 09 Feb 2004 Posts: 2348

(1) Somewhat OT: I need a refresher.
The buttons list is red, till a function is assigned, correct?
On the buttons sheet, in the list for 6131+extender, is a button name "slow" in red. Prey tell where is it on 6131?

(2) What is the XMP fix? does it have to do with the need for some change for extenders and repeated digits discussed here
http://www.hifi-remote.com/forums/viewtopic.php?t=12462&start=15
or some other fix? Is the 9.21 protocol changed from 9.21beta? I'm just curious, we're doing fine as is, not important to change.

(3) I asked for this once before: Not terribly important, but on the keymap sheet it would be great if the OBC column could be made first. Best if we could decide which column should be after Function.
_________________
Liz
Tweeking 8910, HTPro/9811, C7-7800, 6131o, 6131n, AtlasOCAP-1056B01, RCA-RCRP05B and enjoying the ride Smile

mr_d_p_gumby · Posted: Tue Oct 19, 2010 3:03 pm Post subject:

ElizabethD · Advanced Member Joined: 09 Feb 2004 Posts: 2348

The Robman · Posted: Wed Oct 20, 2010 7:36 am Post subject:

Eh-hem, that's why they explained what the button is in the manual! Smile

ElizabethD · Advanced Member Joined: 09 Feb 2004 Posts: 2348

Ouch. Yes, and it even works Smile

_________________
Liz
Tweeking 8910, HTPro/9811, C7-7800, 6131o, 6131n, AtlasOCAP-1056B01, RCA-RCRP05B and enjoying the ride Smile

vickyg2003 · Posted: Thu Mar 03, 2011 6:35 pm Post subject:

There appears to be a problem with the JP1.2 Atlas keymaps in KM 9.21.
When I paste an upgrade into IR the Settings key loses its mapped value. RM maps this remote correctly.
_________________
Remember to provide feedback to let us know how the problem was solved and share your upgrades.

Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.

ElizabethD · Advanced Member Joined: 09 Feb 2004 Posts: 2348

Vicky, do all buttons get messed up?
I just had an issue with shift-phantoms and discrete power in Atlas jp1.3 when add KM upgrade into IR. Also keymoves making in IR. Mike suggested to make keymoves to other devices on the Keymoves sheet in KM. And then absorb them in IR by typing in the values KM makes. That works for me.

Bill once mentioned that KM is't ready for extended version. I suspect this is what he meant. I suspect it's a similar situation as the 6131 keymove format.
_________________
Liz
Tweeking 8910, HTPro/9811, C7-7800, 6131o, 6131n, AtlasOCAP-1056B01, RCA-RCRP05B and enjoying the ride Smile

vickyg2003 · Posted: Fri Mar 04, 2011 8:50 am Post subject:

ElizabethD · Advanced Member Joined: 09 Feb 2004 Posts: 2348

I see. I just tried it. Settings button did not get mapped evn though it's mapped in KM. I used Atlas with sig 1025, jp1.2 which I think is what you used. I setup both KM and IR for the same remote, far as I can tell.

just FYI, Settings is being mapped for Atlas OCAP 1056.
_________________
Liz
Tweeking 8910, HTPro/9811, C7-7800, 6131o, 6131n, AtlasOCAP-1056B01, RCA-RCRP05B and enjoying the ride Smile

vickyg2003 · Posted: Sat Aug 20, 2011 7:40 pm Post subject:

Minor Bug

URC 8206 is having a problem with NEC 2Dev Combo. Its using the wrong variant, the 8206 has variant 011A:2
_________________
Remember to provide feedback to let us know how the problem was solved and share your upgrades.

Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.

3FG · Expert Joined: 19 May 2009 Posts: 3367

For the 8206, I think the KM files in the 3rd post in this thread show that the 8206 upgrade is assigning hex data incorrectly to buttons.
Edited to say: Vicky has explained to me that the incorrect assignment is caused by the difference in size of the fixed dat for the two executors, so this is just a symptom of the 2DEV/4DEV confusion.