New Inteset / Insignia / Sanyo / Nexus JP1 remote

If you have a new remote that isn't recognized by RMIR, post the details here so we can help create a new RDF for it. Or, if there is an issue with an existing RDF or map, this is the place.
sirjp1
Posts: 42
Joined: Wed Oct 29, 2014 3:33 pm

Post by sirjp1 »

mdavej wrote:Too many discrepancies coming to light, so I'm going to roll back to the old version which I'll repost shortly. If you have an old copy, just go ahead and use that. Hopefully that will fix the issues.

Also, all this upload/download activity may have drained your batteries and contributed to the error, so might be time for a fresh set.

Infinite download is a bug in 2.02, later fixed. Error is the correct behavior if it can't make sense of the data, either caused by the learned address change in the RDF or a communication error, IMO. Rmaster.err file should give us more clues.

Sorry for the trouble.
I see this stacktrace in Rmaster.err though not sure if this is the problem:
Checking SAT/1272 (null)
It's a match!
Moving keymove on C:Shift-PIP-On/Off to device upgrade CBL/SAT/1272
Download error: null
java.util.concurrent.ExecutionException: java.lang.NullPointerException
at java.util.concurrent.FutureTask.report(FutureTask.java:122)
at java.util.concurrent.FutureTask.get(FutureTask.java:192)
at javax.swing.SwingWorker.get(SwingWorker.java:602)
at com.hifiremote.jp1.RemoteMaster$DownloadTask.done(RemoteMaster.java:607)
at javax.swing.SwingWorker$5.run(SwingWorker.java:737)
at javax.swing.SwingWorker$DoSubmitAccumulativeRunnable.run(SwingWorker.java:832)
at sun.swing.AccumulativeRunnable.run(AccumulativeRunnable.java:112)
at javax.swing.SwingWorker$DoSubmitAccumulativeRunnable.actionPerformed(SwingWorker.java:842)
at javax.swing.Timer.fireActionPerformed(Timer.java:313)
at javax.swing.Timer$DoPostEvent.run(Timer.java:245)
at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:311)
at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:744)
at java.awt.EventQueue.access$400(EventQueue.java:97)
at java.awt.EventQueue$3.run(EventQueue.java:697)
at java.awt.EventQueue$3.run(EventQueue.java:691)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.ProtectionDomain$1.doIntersectionPrivilege(ProtectionDomain.java:75)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:714)
at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:201)
at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:116)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:105)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:93)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:82)
Caused by: java.lang.NullPointerException
at com.hifiremote.jp1.RemoteConfiguration.findDeviceUpgrade(RemoteConfiguration.java:4149)
at com.hifiremote.jp1.RemoteConfiguration.migrateKeyMovesToDeviceUpgrades(RemoteConfiguration.java:4490)
at com.hifiremote.jp1.RemoteConfiguration.importIR(RemoteConfiguration.java:3869)
at com.hifiremote.jp1.RemoteConfiguration.parseData(RemoteConfiguration.java:4264)
at com.hifiremote.jp1.RemoteMaster$DownloadTask.doInBackground(RemoteMaster.java:591)
at com.hifiremote.jp1.RemoteMaster$DownloadTask.doInBackground(RemoteMaster.java:1)
at javax.swing.SwingWorker$1.call(SwingWorker.java:295)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at javax.swing.SwingWorker.run(SwingWorker.java:334)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
mdavej
Expert
Posts: 4631
Joined: Wed Oct 08, 2003 7:08 am

Post by mdavej »

Is this from RM 2.02a or 2.03?
sirjp1
Posts: 42
Joined: Wed Oct 29, 2014 3:33 pm

Post by sirjp1 »

mdavej wrote:Is this from RM 2.02a or 2.03?
2.03 alpha 25c
sirjp1
Posts: 42
Joined: Wed Oct 29, 2014 3:33 pm

Post by sirjp1 »

Back to the Record button double-push safety feature... Is there a way to disable this "feature"?

I tried some tests:
1. Learned open/close command from original remote onto the Record button. That seems to make it work, the function is sent on the first press, no double press required.
Maybe the double-press feature kicks in only when the function is assigned from a device setup code or device upgrade file?

2. Then I tried to use setup code 21516 (Sony bluray player) and set an EFC 00081 (OBC 22) on the Record button via 994. Nothing happened. I thought OK, maybe Record is special. Tried it on two other buttons, even though the light blinks twice at the end of the 994, the buttons don't do anything after. Is EFC 00081 not the right open/close command for setup code 21516?
I looked at the learned commands in RMIR and they do have OBC 22.
mdavej
Expert
Posts: 4631
Joined: Wed Oct 08, 2003 7:08 am

Post by mdavej »

Extenders don't have this feature. A macro or keymove might also work. Here's something else you can try. Edit your Sony upgrade and change the device type to TV. I tried this on a similar remote and it makes the Rec button work on the first press.

You have the right code for open/close using 21516. Perhaps you have to press record twice when assigning the code. When you assign the EFC to other keys, are you tapping Setup before the code?

Mathdon needs to take a look at your IR file. I'll let him know.
sirjp1
Posts: 42
Joined: Wed Oct 29, 2014 3:33 pm

Post by sirjp1 »

mdavej wrote:Extenders don't have this feature. A macro or keymove might also work. Here's something else you can try. Edit your Sony upgrade and change the device type to TV. I tried this on a similar remote and it makes the Rec button work on the first press.
Interesting ideas, I will try them and report back.
You have the right code for open/close using 21516. Perhaps you have to press record twice when assigning the code. When you assign the EFC to other keys, are you tapping Setup before the code?
Yes, I followed the instructions below and got the blink twice at the end, so it's strange none of the keys work with the EFC. I tried it on the Blue button, on the FRS button, nothing.
http://www.hifi-remote.com/wiki/index.p ... gle_device

I tried starting clean after a 981. Still none of the EFCs work. I downloaded with RMIR, and here's what I have under Key Moves:

Code: Select all

B	Blue	DVD/VCR	1516	25 EC 68 51	68 51	35220
B	PIP-Frs	DVD/VCR	1516	25 EC 68 51	68 51	35220
B	PIP-Ch-	DVD/VCR	1516	25 EC DC AC	DC AC	58473
First two are supposed to be open/close, the last one "left arrow". None work. Any ideas? Is my remote somehow messed up that not even a 981 can fix?
mdavej
Expert
Posts: 4631
Joined: Wed Oct 08, 2003 7:08 am

Post by mdavej »

Yeah, those codes ended up being way off. 1516 in the Inteset must use a Sony combo protocol instead of Sony20. That makes the EFC codes completely different. There's no point in reverse engineering it when my upgrade and EFCs work if you forget about trying to use the built in code. This file has a known working upgrade with open/close on Blue and Record of device B.

http://www.hifi-remote.com/forums/dload ... e_id=12892
sirjp1
Posts: 42
Joined: Wed Oct 29, 2014 3:33 pm

Post by sirjp1 »

mdavej wrote:Yeah, those codes ended up being way off. 1516 in the Inteset must use a Sony combo protocol instead of Sony20. That makes the EFC codes completely different. There's no point in reverse engineering it when my upgrade and EFCs work if you forget about trying to use the built in code. This file has a known working upgrade with open/close on Blue and Record of device B.

http://www.hifi-remote.com/forums/dload ... e_id=12892
Oh I was not trying to make 21516 work. I was just trying to see whether programming an EFC on the Record button would make the button work on the first press. Just as a test. I have my own working device upgrade but I will take a look at yours too of course.
Just wanted to make sure that my remote is not somehow messed up now and doesn't like EFC codes anymore.

As a side note, this JP1 stuff is addictive :)
sirjp1
Posts: 42
Joined: Wed Oct 29, 2014 3:33 pm

Post by sirjp1 »

Just want to confirm that your file with the bluray device type set to TV solves the Record button problem. I also changed it back to DVD type and the problem was back, just wanted to make sure. Thank you very much, excellent advice.
I reverted back to the v4 RDF, now I have to go back and fix my rmir file again :-) Hopefully I'll have a working remote soon so I can actually start using it, though I have to admit messing with it like this is a lot more fun.
3FG
Expert
Posts: 3434
Joined: Mon May 18, 2009 11:48 pm

Post by 3FG »

mdavej wrote:1516 in the Inteset must use a Sony combo protocol instead of Sony20.
I can confirm that the Inteset does use Sony Combo 12/15/20. So does the 1067BC4 version of the Comcast remote, Simpleset remotes, and many other MAXQ processor remotes. The 7340 and the Inteset are two examples of S3F80 remotes which use PID 0027 also. The effect of this is that the Lookup Tool provides incorrect info for these newer remotes.
mdavej
Expert
Posts: 4631
Joined: Wed Oct 08, 2003 7:08 am

Post by mdavej »

So, sirjp1, 3FG has solved the mystery of the broken EFC. Your remote is fine. If you want to prove this to yourself, the appropriate open/close EFC for 21516 on an Inteset is probably 35228. You can always test an EFC without assigning it to a button by simply tapping Setup followed by the code. When you press the last digit, the command is sent.
sirjp1
Posts: 42
Joined: Wed Oct 29, 2014 3:33 pm

Post by sirjp1 »

mdavej wrote:So, sirjp1, 3FG has solved the mystery of the broken EFC. Your remote is fine. If you want to prove this to yourself, the appropriate open/close EFC for 21516 on an Inteset is probably 35228. You can always test an EFC without assigning it to a button by simply tapping Setup followed by the code. When you press the last digit, the command is sent.
Thank you, I will give it a try.

What device upgrade file did you start with to make the rmir file above? I think I started with an older KM file for my Bluray device upgrade but perhaps there's a better one out there, though at the end of the day I don't think it matters as long as the file has the codes I need and they work.
sirjp1
Posts: 42
Joined: Wed Oct 29, 2014 3:33 pm

Post by sirjp1 »

I tried this and it works. The Rec button sends the command on the first press if I use the EFC above. So the mystery continues, why is it that when I use a device upgrade file I have to press Rec twice, but with a learned command or EFC code it works on the first press?

Btw, is there a post that describes how you figure out these EFC codes? How did you find 35228 for example?
mdavej
Expert
Posts: 4631
Joined: Wed Oct 08, 2003 7:08 am

Post by mdavej »

sirjp1 wrote:What device upgrade file did you start with to make the rmir file above?
I made that one myself quite a while ago and slowly added functions to whenever I got a new Sony model. Sony BD codes haven't really changed except for a few additional functions here and there. Hamsterman's upgrade below looks pretty good to me.

http://www.hifi-remote.com/forums/dload ... e_id=11069

I'd post mine, but it would just be redundant.
mdavej
Expert
Posts: 4631
Joined: Wed Oct 08, 2003 7:08 am

Post by mdavej »

sirjp1 wrote:I tried this and it works. The Rec button sends the command on the first press if I use the EFC above. So the mystery continues, why is it that when I use a device upgrade file I have to press Rec twice, but with a learned command or EFC code it works on the first press?

Btw, is there a post that describes how you figure out these EFC codes? How did you find 35228 for example?
No mystery. We're simply getting around UEI's rules. They're trying to protect you from recording over something by accident (probably a relic of the old VCR days). If you learn or reassign, then it's no longer the original record function, hence no reason to protect you anymore. When we change to a TV device type, since TVs can't record anyway, then the protection is also bypassed. In your case just leave it as a TV type. That doesn't hurt a thing.

We know from experience those big EFC values are used in complex protocols. That was our first clue. 3FG worked his magic and confirmed this hunch was correct. So to get the right EFCs, we just open the upgrade (Hamsterman's for example), note the device and subdevice, and pick the new protocol (changing from Sony20 to Sony Combo (12/15/20)). Enter the original device code back into the first subdev1 field (226). Then on the functions tab, change every Device and Subdevice to 26 and 226. Now we have all the original functions setup to work with the new protocol. All the new EFCs are calculated automatically. This doesn't come up a lot, so there is no documented procedure. Just make the new parameters to match the original ones. This only works going between different versions of the same protocol (from Sony20 to Sony Combo (12/15/20) for example). It wouldn't work going from Sony to Panasonic because they're entirely different and incompatible by design.

Note that if you type 00081 in the EFC5 column for the Eject function, it immediately changes to 35220, the same number you saw in your download. But also note that everything else is wrong (protocol, device and EFC). Hence entering 00081 on your remote resulted in all those being wrong as well, resulting in a function that didn't work. In the combo protocol, EFC 00081 means something entirely different than is does in the simple protocol.
Post Reply