or Connect
AVS › AVS Forum › Gaming & Content Streaming › ReplayTV & Showstopper PVRs › Adding new IR Blaster codes to the Replay unit (4k/5k)
New Posts  All Forums:Forum Nav:

Adding new IR Blaster codes to the Replay unit (4k/5k) - Page 3

post #61 of 454
Ah....
Don't worry about "incompatence," the main point is to try. It took Edison how many thousand attempts to come up with a viable filament for the electric bulb? (Not meant to discourage you in any way
post #62 of 454
Quote:
Originally Posted by whirly View Post

Then search Remote Central for the CCF files that include your particular device.

Here is a list of CCF files organized by brand. I don't see any Accurian stuff there, though.

http://www.remotecentral.com/cgi-bin...evices&br=&fc=

I did try out a couple CCF file codes, and made my ReplayTV change channels on my TV through the IR blaster. Not a very useful function, but it provides proof of concept and made me smile.

The quality of the learned code does matter. You may run out of symbols and get "?" in the decode for low quality learned codes. (for example, encodings 801600a3 and 801700a3 might both show up on a poor quality recording, but they are functionally equivalent). In such a case you can manually fix things up by remapping the 1-offs back to 0 or 1 as appropriate. A properly learned code should typically include a lead-in symbol (= is appropriate) followed by a string of 1's and 0's, followed by a lead-out symbol. Repeated sections typically do not have a lead-in code, as the lead-in would be part of the initial (fixed) sequence.

To summarize:

1) Find a CCF file with your device from the above link
2) load the CCF file into ProntoEdit4
3) double-click the panels to find the number keys and enter and power
(note also the "Properties" has some hard key mappings which may include power)
4) double-click a number on the panel, then click the "Set IR".
(May also need to click "View IR" if the "IR code" isn't already visible)
5) Select and copy (Ctrl+C) the "IR code" from that box
6) Click the two cancel buttons to close the two dialog boxes
7) Go to the RID File Editor program, and click "HEX" button next to the corresponding digit
8) Repeat steps 4-7 for all 10 digits and Enter and Power
9) Set "unknown" to 30 and type to "Cable" and enter a code number (1000 is appropriate)
10) Save this to a RID file.

Enter and Power are not always necessary. Enter is only used if "send enter" is selected on the ReplayTV, and power is only used during testing/code assignment.

Once a RID file is created, you can use the WiRNS GetShellCmds function to copy the files to the ReplayTV, as described in http://www.avsforum.com/avs-vb/showthread.php?t=477427
post #63 of 454
I created a code for the Accurian based on the KM configuration file. Not sure if this will actually work, so could someone with this tuner give it a try?

To install this code:

1) Use DVArchive to create a photo folder called "install" on the ReplayTV.
2) Put the "ircodes", "ircodesRaw", and "C1000fi.rid" files from the accurian.zip file into that photo folder.
(right-click on "install" and select "import photos" from the menu)
3) Install WiRNS using the "custom" setting, and also install the "GetShellCmds" pluging
4) copy the "shellcmds" file from the accurian.zip file into the same folder as wirns.exe (typically would be c:\\wirns)
5) Start up WiRNS - the "W" in the windows notification bar should be green when it is ready.
6) On your ReplayTV, switch the network configuration to static, and set both DNS server settings on your ReplayTV to match the "WiRNS IP" (be sure to note what your previous settings were)
7) Menu..Setup..Connect to ReplayTV Service Now on your ReplayTV to force it to connect through WiRNS.

If all goes well, you should get a clock and a CPU meter pop up on the screen. These are done at the beginning and end of the script just so you can see that the script began and completed. Use 243-Zones to toggle these back off.

Now you should be able to set your Accurian device up using IR code "1000"

Once things are working, restore the ReplayTV network configuration to your previous settings. Or, if you normally use WiRNS, you just need to delete the "shellcmds" file. You can also safely remove the "install" photo directory you created.

For another description of how this is done, see http://www.avsforum.com/avs-vb/showthread.php?t=477427

To download WiRNS, see http://www.users.qwest.net/~bolenbaughryan2/WiRNS.html

For details and help for WiRNS, see http://www.avsforum.com/avs-vb/showthread.php?t=504981

For details and to download DVArchive, see http://www.dvarchive.org

EDIT: the Encoding values in the attached file aren't correct, so this copy doesn't work. Scroll down about 12 posts to download one that does work
post #64 of 454
Here is how I created the Accurian RID file. This should work for any NEC1 protocol, but I'm not that familiar with the variants of the protocol, so maybe Robman will weigh in to correct any mistakes I've made.

The Accurian appears to use 41.7kHz NEC1 protocol with fixed data 0x7F, as shown on the 'setup' tab. Also in the KM configuration file are the hex values for each of the digits, shown on the 'functions' tab.

The format for NEC1 protocol is (fixed data) (inverted fixed data) (key code) (inverted key code)

So, for example, the hex code for "0" is listed as "8F" so this gets coded as:

0x7F808F70

(note that, in hex arithmetic, 7F + 80 = FF and 8F+70 = FF)

So, enter this code "0x7F808F70" in the "initial bits" line for the number 0 and press tab. It gets converted automatically to "=01111111100000001000111101110000+".

Repeat for all 10 digits, and Enter (if available) and Power (if desired)

Set all repeat codes to "*#" for any codes with the initial bits defined

Set the encodings as follows:

Code: 1000
Type: Cable
Frequency: 41.7
Unknown value: 33

0 : 8016003f
1 : 80160014
= : 815400aa
+ : 801605e5
* : 81540054
# : 80160e32

[EDIT: these encodings don't appear to be correct for all NEC1 protocols - more details later]

(it is easiest to just start from the accurian RID file, or some other NEC1 protocol code to get these data pre-set)

Then save the code and upload to your ReplayTV as described in my previous post (the accurian data set)

Attached is a new revision, v1.2, of the RIDGen.exe program. This one has some subtle enhancements, like accepting command-line arguments so you can associate .rid files with the program, and double-click to open them.

(Note: the 0 and 1 encodings may get reversed, in which case the entire bit stream would be inverted from what is shown above. Also, the =, +, *, # symbols may get reordered. This is because these symbols aren't saved in the RID file, the encodings are. The RIDGen program tries to automatically assign the symbols in order based on how often each appears (0 = most often). In the case of NEC1 format there are always exactly the same number of 0's as 1's, so it can be random which encoding gets which symbol. You can artifically force the case by setting Power to simply "0" so that the 0 is the more frequent symbol over all.)

Edit: Go to post #106 for an updated version of RIDGen
post #65 of 454
Is the "Unknown Value" always = 33 and, if not, how is this number computed??
post #66 of 454
Quote:
Originally Posted by whirly View Post

Is the "Unknown Value" always = 33 and, if not, how is this number computed??

I don't know what that number is. It doesn't seem to have much, if any, effect, so it probably doesn't matter what you use. My working theory is it is a time delay, in ms, but that is just a wild guess. I picked 33 because that was the most common value in the pre-defined codes. (see the "unknown4" column in the table.xls spreadsheet in the 4504_blaster_codes.zip file posted earlier in this thread)

This is the entry at the +8 byte offset in the code table as documented earlier:

Quote:


+8 2 unknown (values seen: 33, 30, 100, 50, 42)
(possibly a ms delay before or after the transmission?)
post #67 of 454
Thanks!

Clear as MUD

However, I figure if YOU don't know then I can't be THAT stupid
post #68 of 454
The instructions from FlipFlop above worked great.

I have a Pansat 3500S and a Pronto which I used to create the rid. (calvin940 should be able to use it if he follows the instructions above for the Accurian.) I used the same ircodes and ircodesRaw files for the file I generated - C1000fi.rid.

Thanks,

 

3500S_RID.zip 1.9453125k . file
post #69 of 454
ok. I am pretty damned psyched to try this puppy out. I will give it a shot at home tonight and see how this sucker works.

I thank everyone for their input so far. I was hunting around town for friends that may have a pronto to see if I could get those suckers learned and hand't found one yet. I will post back this evening.

CHeers and thanks
Calvin
post #70 of 454
Well, that was stupid of me.
I didn't notice the lack of line breaks in FlipFlop's shellcmd file before I net-connected.
My Replay is now stuck on the "replay guide, channel guide, menu" screen.
post #71 of 454
Yoyo, thanks for the link - unfortuately the site is down for maintenance.

Okay, I have an idea now of how to get the file back on using wirns and the shell dll. Now, can I use the shell commands to extract the file that I need to modify for my Samsung 360 or are they located somewhere else on the net?

Essentially all I need to do is take the Samsung RID file, make a change to the command issued during an 'enter'.

Can I overwrite the existing RID file with the new version? Would a future connect to Replay overwrite that file?

Thanks for the help,
Ron
post #72 of 454
Quote:
Originally Posted by sixt7gt350 View Post

Well, that was stupid of me.
I didn't notice the lack of line breaks in FlipFlop's shellcmd file before I net-connected.
My Replay is now stuck on the "replay guide, channel guide, menu" screen.

The shellcmds file has Unix-style line breaks, but that shouldn't matter, other than Windows Notepad gets confused. I don't think this could cause the unit to get stuck as you described.

When you did the net connect, did you get the clock and/or cpu meter show up on the top of the screen? Does the 1000 code appear as an IR blaster code now? (In other words, did the shellcmds script start, complete, do what it was supposed to do, when you did the net connect).

If you hold down the power button 10 seconds to reboot the unit, does it come back to normal?

ReplayTVs do get stuck as you describe due to network configuration problems. The solution is to disconnect the network cable from the replaytv, and reset the unit. Once it comes up and is responding to the remote you can go ahead and re-connect the cables. See http://www.replaytvupgrade.com/#swirl for more details.
post #73 of 454
Quote:
Originally Posted by rkundla View Post

Okay, I have an idea now of how to get the file back on using wirns and the shell dll. Now, can I use the shell commands to extract the file that I need to modify for my Samsung 360 or are they located somewhere else on the net?

There is a .zip file with all of the RID files from a 4504 at post#38 of this thread. These should be nearly the same as what is on the 5xxx units, although I know they did add some codes since then.

You can also reverse the copy operation in the "shellcmds" script, like the following, to copy existing codes from the system directory to the photo directory, and then export them from there to your computer using DVArchive. Just change both "C1000fi.rid" to your desired code number. Sat codes start with "S", cable box codes start with "C", and the code numbers are always 4 digits with leading zeros, if necessary.

Code:
AppShell ToggleClock
cp -f /name/system/user/mirror/sys-setup-gaea/data/irCodeset/C1000fi.rid /name/storage/Photo/install/C1000fi.rid 
AppShell ToggleCpuMeter
post #74 of 454
WOOHOO!!!

Yes, FlipFlop, the lockup was due to the network situation from the manual setting, but I did make the mistake of using Notepad to copy/paste. It missed your Unix breaks.

I tried the first RID file I made and it didn't work. I tried the one you made for me from the KM file and it didn't work. I went back to my IR learned data and used the OBC (not EFC) codes into makehex, then RIDgen.

The WORKING!!! Accurian RID file is attached, along with a Notepad-modified shellcmds file to upload just the revised RID file.

Replay guys: If you want to control your Accurian HDTV receiver, here's your chance!

A HUGE thanks to FlipFlop for all the help, creating RIDgen, and the CCF prodding. Another big thank you to johnsfine on the JP1 forum for sending me in the direction of makehex, since I'm Pronto-less.

 

accrid.zip 0.537109375k . file
post #75 of 454
Excellent! I looked at the differences, and the bit strings are identical between your file an mine, so my interpretation of the KM data was correct. The difference was in the Encoding and frequency values, so my timing was not correct. I guess that is not too surprising since I kind of guessed at those values based on other similar codes.

Bottom line is my description above of how to go from KM to RID for NEC1 protocols is correct except for the timing. I don't understand the subleties of the protocols, so I'm not sure how to pick the encoding values from the KM file. I thought it would be one-size-fits-all, but apparently not.
post #76 of 454
Quote:
Originally Posted by sixt7gt350 View Post

WOOHOO!!!

Replay guys: If you want to control your Accurian HDTV receiver, here's your chance!

A HUGE thanks to FlipFlop for all the help, creating RIDgen, and the CCF prodding. Another big thank you to johnsfine on the JP1 forum for sending me in the direction of makehex, since I'm Pronto-less.


So do the codes make Accurian work seemlessly with a RTV now (out-of-the-box so to speak)? or is there a lot of cleanup and praying still involved?
post #77 of 454
Quote:
Originally Posted by T-Test View Post

The instructions from FlipFlop above worked great.

I have a Pansat 3500S and a Pronto which I used to create the rid. (calvin940 should be able to use it if he follows the instructions above for the Accurian.) I used the same ircodes and ircodesRaw files for the file I generated - C1000fi.rid.

Thanks,

Ok, let me start off by saying that you rock! FlipFlop Rocks! Everyone in this damn AVS haus rocks! I am happy of course because I have my Replay controlling my pansat 3500S.

A couple of notes. Using the files you provided, I could not get it to work. Specifically, I went through the process of transferring the fles to my replay as per the forum instructions using WiRNs (I had already done it last week for the pansat 2500A code at code 2000 thinking there was a chance those might work, but alas I didn't realize at the time that those units were different from an IR perspective).

You had set the .rid file as cable, which I thought was the reason it wasn't showing up in the list. I changed the .rid to be sat instead of cable leaving it at 1000, but it still would not show up in the code list for my device. So, I altered your file to be at 2000 instead of 1000 and change it from cable to sat, saved it as S2000fi.rid, and uploaded it with the files (ircodes and ircodesRaw) that were included with the pansat 2500A remote zip (I gather that the ircodes and irccodesRaw are just to add the 2000 to the list of codes). Presto, code 2000 now uses your .rid for the 3500 and it controls the 3500 just perfectly.

Thanks all for the help (or really just doing it all for me - I wish I could have helped more).

Calvin
post #78 of 454
Quote:
Originally Posted by calvin940 View Post

You had set the .rid file as cable, which I thought was the reason it wasn't showing up in the list. I changed the .rid to be sat instead of cable leaving it at 1000, but it still would not show up in the code list for my device.

If you add a RID file, you need to add that number to both of the ircodesRaw and ircodes files for it to show in the list. It appears that the same set of codes are available for both cable and sat, regardless of the type defined in the file.

BUT, sometimes the added code does not show up in the list until you reboot. I'm not sure why this happens, and sometimes the code does show up right away. I think once you go to the input settings the list gets loaded into memory, and doesn't get re-loaded until after a reboot.
post #79 of 454
Here's a very basic CCF (learned codes) file derived from the Samsung T351. Hope this helps

Q

 

accurian.zip 4.76953125k . file
post #80 of 454
Quote:
Originally Posted by quang777 View Post

Here's a very basic CCF (learned codes) file derived from the Samsung T351. Hope this helps

Q

This file has codes learned a little too well. It recognized the protocols used and store the protocol data instead of the IR timings, so it won't work with RIDGen. RIDGen will only take Pronto data starting with "0000" which indicates raw timing data.

Attached is an updated version of RIDGen which fixes a bug when loading in RID files where not all of the buttons have the same length. Also made it ignore spaces and any other non-symbols, so you can add spaces to the bit strings to help see the structure better. For example:

0xFF 00 D0 2F

or

=11111111 00000000 11010000 00101111+

Edit: Go to post #106 for an updated version of RIDGen
post #81 of 454
Quote:
Originally Posted by FlipFlop View Post

If you add a RID file, you need to add that number to both of the ircodesRaw and ircodes files for it to show in the list. It appears that the same set of codes are available for both cable and sat, regardless of the type defined in the file.

BUT, sometimes the added code does not show up in the list until you reboot. I'm not sure why this happens, and sometimes the code does show up right away. I think once you go to the input settings the list gets loaded into memory, and doesn't get re-loaded until after a reboot.

The ircodes and ircodesRaw that T-Test provided in his zip along with the 3500S rid file had the 1000 code in both files and I did hard reboots of the replay as well. No go on the 1000 no matter what I did.

Calvin
post #82 of 454
Quote:
Originally Posted by icecow View Post

So do the codes make Accurian work seemlessly with a RTV now (out-of-the-box so to speak)? or is there a lot of cleanup and praying still involved?

With the RID file I uploaded, Replay controlled the Accurian without problem. I went through all numbers, using a mix of direct entry and channel up/down.
Depending on how the signal is broadcast, there can be some wide vs. zoom vs. 4:3 issues. I have yet to receive spousal approval for an HDTV monitor, so it would be more of an issue for me than someone with a widescreen having aspect control. I've wowed her a few times with LCD and plasma displays, but never enough to approve the purchase.
I haven't dropped cable yet, but when I do, I expect I'll be using WiRNS to create a custom channel guide, since the HDTV receiver needs the IR blast of a cable box and the channel map of OTA. I might remap the sub-channels to make everything available as a three digit channel. PBS usually carries decent stuff on sub-channels. We'll see when the time comes.
It sure would be nice if cable companies actually put channel numbers the same as the OTA broadcast channel. I could just tell Replay I still have cable and it would eliminate the need for remapping. Why do they do that?

I will probably build a dedicated WiRNS/DVA/HT PC if I use WiRNS full-time for a remapped channel guide.
post #83 of 454
So... 1000 on our part will be designated as a custom control number? Everyone should use 1000 for their custom rid files?
post #84 of 454
Thread Starter 
Quote:
Originally Posted by FlipFlop View Post

Here is how I created the Accurian RID file. This should work for any NEC1 protocol, but I'm not that familiar with the variants of the protocol, so maybe Robman will weigh in to correct any mistakes I've made.

Here's some additional info about the NEC signal. First off, it's carrier frequency is 38kHz, not 41.7 kHz. Secondly, while the 2nd byte of fixed data certainly used to be the compliment of the 1st, this is not usually the case anymore. The 2 bytes can have totally independant values now.

As for the "unknown value", seeing as how the value is 33 I'm going to make a wild guess that this is the Duty Cycle (ie, it's 33%). In a remote control, if you used a larger value it would make the signal stronger, but it would also drain the batteries alot quicker, so if you ever find that the IR blaster signals are not strong enough to be read reliably by the device in question, try increasing this value (but you probably shouldn't go above 50%).

As for getting the burst times from KM, your best bet is to create a file that documents the times for each protocol, using the protocol names that KM uses, and simply have your program look them up. The only other option is to grab the copy of the protocol assember clode that KM always stores in the upgrade files, and get the times from that, but in order to do that you would need some help from me (or one of the other JP1 experts, like John Fine) to know how to read the data.
post #85 of 454
Quote:
Originally Posted by sixt7gt350 View Post

It sure would be nice if cable companies actually put channel numbers the same as the OTA broadcast channel. I could just tell Replay I still have cable and it would eliminate the need for remapping. Why do they do that?

Try "spoofing" the HD receiver as a satellite receiver. The satellite companies usually have local channel listings that map to the same analog broadcast channel numbers for your area. If you are lucky, the corresponding HD channels will have PSIP channel numbers that correspond the the local analog channel numbers (i.e. HD channel "2-1" has same content as analog channel "2").

This works for all channels except one in my area (PBS), but it keeps me from having to do any channel remapping using WiRNS.
post #86 of 454
sixt7gt350, What are the aspect ratio issues you mentioned before. Like you, I do not yet have approval to upgrade the set, and recently returned the SIR-T351 to sears since I couldn't stand how it stretched faces horizontally when viewing hdtv material. Everyone looked a little fat (yes, I am picky...why else would I be using an hdtv tuner on a non-hdtv set ...

Does it stretch or distort in 4:3? Can you watch in letterbox? If so, does it have black bars on the unused screen area (or grey like the samsung)?

Thanks!
post #87 of 454
Quote:
Originally Posted by Loren Kruse. View Post

So... 1000 on our part will be designated as a custom control number? Everyone should use 1000 for their custom rid files?

You can use any number you want, but you need to add the number to both ircodes and ircodesRaw. If you use 1000, then you can simply use the files posted above, so it is easier.

I picked 1000 because is was not previously used for anything else. It may be prefered to use a low (and unused) number instead so you don't have to page down 20 times to get to 1000.

If you overwrite an existing code number, then there is a chance that the ReplayTV will update and restore the original RID file.
post #88 of 454
I would think everyone creating these custom IR codes should use a single default number. The only time a person would need a code different is if he had multiple brand of receivers on one ReplayTV that would need different IR codes.
post #89 of 454
Also, is the Accurian at Radio Shack a discontinued product?
post #90 of 454
Guys/ Flip Flop I have an FTA receiver called Coolsat 4000 pro, but i want to use this with my ReplayTV. I found the Coolsat 4000 IR codes for a TIVO. Can anyone here help me get the information from the TIVO file and use it to create a ReplayTV IR Code?

Thanks
dUc

 

TIVO_Coolsat 4000 pro IR Codes.zip 1.2802734375k . file
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: ReplayTV & Showstopper PVRs
AVS › AVS Forum › Gaming & Content Streaming › ReplayTV & Showstopper PVRs › Adding new IR Blaster codes to the Replay unit (4k/5k)