Your Universal Remote Control Center
RemoteCentral.com
Complete Control by URC Forum - View Post
Previous section Next section Up level
Up level
The following page was printed from RemoteCentral.com:

Login:
Pass:
 
 

Topic:
IRScrutinizer help
This thread has 3 replies. Displaying all posts.
Post 1 made on Friday February 5, 2021 at 17:58
dcapone
Long Time Member
Joined:
Posts:
January 2009
32
So, I have used IRScrutinizer to translate JP1 files into hex codes in the past to extract discrete codes to use on URC remotes. But, outside of this basic functionality, I am not overly familiar with the ins and outs of IRScrutinizer.

However, there is one file I found that has some discrete codes I would like that I cannot make work. The first issue was/is that I was getting a protocol unknown error. After some googling, this I resolved as I guess the protocol name changed from "Roku Official" to just "Roku".

I still get a NameUnassignedException: Name F not assigned error now when I attempt to import the signal for any button on the remote. I can use the import all/param option and the buttons all import into the scrutinizer remote panel. From there I can see a column "F". Every button has a blank in the "F" column.

Is this file worthless? Am I doing something wrong? Is there something I can fill into the F column to make it work?

Did something change from when the file was created using "roku official" to when it was renamed "roku" where the function name became required where maybe it wasn't required was the file was created?

Any assistance would be helpful.
Post 2 made on Saturday February 6, 2021 at 03:51
Barf
Long Time Member
Joined:
Posts:
August 2013
325
"JP1 files" are for the program RemoteMaster (sometimes called RMDU) supported in the JP1 forum [Link: hifi-remote.com] . Using a current version of RemoteMaster (2.12.*) try to load the file, then to make a Girr (Girr is the native format of IrScrutinizer) thruogh File -> Export as Girr or IrScope file. Then import the generated *.girr file in IrScrutinizer.

If that does not work, please post [a link to] the file.
OP | Post 3 made on Saturday February 6, 2021 at 09:50
dcapone
Long Time Member
Joined:
Posts:
January 2009
32
Awesome, I don't know why I didn't think of this. This mostly worked.

Only issue I am experiencing now is that a few of the codes I was hoping to grab and see if they work are giving domainviolationexceptions, Parameter F = is outside of the allowed domain 0...127.

Obviously this is happening on signals where F is greater than 127. Do you know of any workaround to this or are these signals not supported in hex?
Post 4 made on Sunday February 7, 2021 at 04:15
Barf
Long Time Member
Joined:
Posts:
August 2013
325
The protocol documentation (in IrScrutinizer) says:

This IR protocol is very similar to NEC2, except the repeat behavior is different. The second and additional frames of a repeating signal send the OBC + 128. [Reference]([Link: hifi-remote.com]).

so it appears to be worth a try just to "&127" the Fs >= 128 (i.e. just zero the highest bit).


Jump to


Protected Feature Before you can reply to a message...
You must first register for a Remote Central user account - it's fast and free! Or, if you already have an account, please login now.

Please read the following: Unsolicited commercial advertisements are absolutely not permitted on this forum. Other private buy & sell messages should be posted to our Marketplace. For information on how to advertise your service or product click here. Remote Central reserves the right to remove or modify any post that is deemed inappropriate.

Hosting Services by ipHouse