 |
JP1 Remotes
|
| View previous topic :: View next topic |
| Author |
Message |
KenL
Joined: 22 Nov 2006
Posts: 14
|
 Posted: Wed Nov 22, 2006 4:36 pm Post subject: Samsung DTB-H260F ATSC tuner |
 |
|
Protocol not recognized:
1. Device: Samsung DTB-H260F ATSC tuner
2. Type of device: STB
3. Year: 2006
4. UEI Remote model: 15-1994
5. Do you have a JP1 cable? yes
6. Still have original remote? yes
7. Checked the file section? yes
8. Checked Pronto file section (at R/C)? yes
9. Partially working setup code? no
10. Learning remote question? file is here
While it would be handy to have a device upgrade for this unit, it's far more important to convert the (working) learned functions into ReplayTV blaster rid format. Only need digits, power and enter.
Doable?
Frequency is known, so is it possible to translate (kludge) these learned blasts into a ReplayTV rid file format without needing DecodeIR support for the protocol?
This is the only current standalone ATSC tuner readily available and it's near perfect for use with the ReplayTV 5K/4K, if we can add blaster support for changing channels. I easily generated blaster rid files for several other HD tuners (with the help of IR.exe and a 15-1994) but those STBs used IR protocols known to DecodeIR. |
|
| Back to top |
|
 |
The Robman
Site Owner
Joined: 01 Aug 2003
Posts: 21238
Location: Chicago, IL
|
| Posted: Thu Nov 23, 2006 4:44 pm Post subject: |
|
|
I just took a look at your file and here's the format of the signals...
freq: 38k
style: LSB
1st leadin (LI): +4488 -4492
last leadout (LO): +498 -59154
gap1: +498 -4498
gap2: -68
1 = +498 -1498
0 = +498 -498
| Code: | dev1 dev2 obc comp OBC Function
LI: 00000100 00000000 <gap1> 1000 01111000 <gap2> 10000111 LO: 30 - power
LI: 00000100 00000000 <gap1> 1000 00000000 <gap2> 11111111 LO: 00 - 1
LI: 00000100 00000000 <gap1> 1000 10000000 <gap2> 01111111 LO: 01 - 2
LI: 00000100 00000000 <gap1> 1000 01000000 <gap2> 10111111 LO: 02 - 3
LI: 00000100 00000000 <gap1> 1000 11000000 <gap2> 00111111 LO: 03 - 4
LI: 00000100 00000000 <gap1> 1000 00100000 <gap2> 11011111 LO: 04 - 5
LI: 00000100 00000000 <gap1> 1000 10100000 <gap2> 01011111 LO: 05 - 6
LI: 00000100 00000000 <gap1> 1000 01100000 <gap2> 10011111 LO: 06 - 7
LI: 00000100 00000000 <gap1> 1000 11100000 <gap2> 00011111 LO: 07 - 8
LI: 00000100 00000000 <gap1> 1000 00010000 <gap2> 11101111 LO: 08 - 9
LI: 00000100 00000000 <gap1> 1000 10010000 <gap2> 01101111 LO: 09 - 0
LI: 00000100 00000000 <gap1> 1000 01010000 <gap2> 10101111 LO: 10 - vol+
LI: 00000100 00000000 <gap1> 1000 11010000 <gap2> 00101111 LO: 11 - vol-
LI: 00000100 00000000 <gap1> 1000 00110000 <gap2> 11001111 LO: 12 - ch+
LI: 00000100 00000000 <gap1> 1000 10110000 <gap2> 01001111 LO: 13 - ch-
LI: 00000100 00000000 <gap1> 1000 00101000 <gap2> 11010111 LO: 20 - enter
LI: 00000100 00000000 <gap1> 1000 00001000 <gap2> 11110111 LO: 16 - up
LI: 00000100 00000000 <gap1> 1000 10001000 <gap2> 01110111 LO: 17 - down
LI: 00000100 00000000 <gap1> 1000 01001000 <gap2> 10110111 LO: 18 - left
LI: 00000100 00000000 <gap1> 1000 11001000 <gap2> 00110111 LO: 19 - right |
I don't know whether the -64 gap between the last two bytes is actually required (my guess is that the signal would work without it), I'm just reporting that it's there. You'll also notice that the last byte is the complement of the previous byte. Generating a new executor for this using PB won't be difficult, but it might be time consuming as it'll take a fair bit of assembler.
_________________
Rob
www.hifi-remote.com
Please don't PM me with remote questions, post them in the forums so all the experts can help! |
|
| Back to top |
|
|
KenL
Joined: 22 Nov 2006
Posts: 14
|
| Posted: Thu Nov 23, 2006 9:00 pm Post subject: |
|
|
Thanks for the prompt expertise.
So we may be close to generating a rid file for this Samsung?
Wants something like this: (from .rid for LG STB)
| Code: | Frequency: 38
Duty cycle:30
0 is 80150040
1 is 80150015
= is 815700ac
+ is 80150689
* is 81570056
# is 80150e94
Initial bits Repeated bits
0 =00010000111011110110000110011110+ *#
1 =00010000111011110111011110001000+ *#
2 =00010000111011111011011101001000+ *#
3 =00010000111011110011011111001000+ *#
...
Enter =00010000111011110110000110011110+ *# |
Not sure how much you helped with Ridgen but I included the above (unrelated) snippet just as an example of format.
Or perhaps enough to make an .IRP file for this Samsung protocol? Looks like Ridgen uses makehex (with IRP file and OBCs) to generate strings like above.
Feels like it's close but of course I may be way off base. 
Need another nudge for achieving the conversion to .rid... and something to test in a Replay. |
|
| Back to top |
|
|
johnsfine
Site Admin
Joined: 10 Aug 2003
Posts: 4766
Location: Bedford, MA
|
| Posted: Fri Nov 24, 2006 8:40 am Post subject: |
|
|
| KenL wrote: | | Or perhaps enough to make an .IRP file for this Samsung protocol? |
Again, I don't understand what that link is supposed to tell me.
| KenL wrote: | | Looks like Ridgen uses makehex (with IRP file and OBCs) to generate strings like above. |
But a .irp file from Rob's description above is easy. So if that's what you need, copy paste the text below into an .irp file:
Device=32.0
E=1
Function=0..255
Frequency=38000
One=498,-1498
Zero=498,-498
Form=;4488,-4492,d:8,s:8,498,-4498,e:4,f:8,-68,~f:8,498,-59154
In the MakeHex output, the "Function" number is the same number as obc number in the list of hand decodes Rob posted above. |
|
| Back to top |
|
|
The Robman
Site Owner
Joined: 01 Aug 2003
Posts: 21238
Location: Chicago, IL
|
| Posted: Fri Nov 24, 2006 10:47 am Post subject: |
|
|
Hey Ken,
I found the user manual for this STB and it appears there are several more buttons on the original remote than just the ones you included in your IR file. I know you don't need them for the RID file, but could you learn them and post the new IR file anyway please because when we get around to creating a JP1 upgrade for this box, we will want to include all the buttons.
Also, if we do create an upgrade for it, would you be willing to test it for us?
_________________
Rob
www.hifi-remote.com
Please don't PM me with remote questions, post them in the forums so all the experts can help! |
|
| Back to top |
|
|
KenL
Joined: 22 Nov 2006
Posts: 14
|
| Posted: Fri Nov 24, 2006 11:54 am Post subject: |
|
|
| johnsfine wrote: |
But a .irp file from Rob's description above is easy. So if that's what you need, copy paste the text below into an .irp file:
Device=32.0
E=1
Function=0..255
Frequency=38000
One=498,-1498
Zero=498,-498
Form=;4488,-4492,d:8,s:8,498,-4498,e:4,f:8,-68,~f:8,498,-59154
In the MakeHex output, the "Function" number is the same number as obc number in the list of hand decodes Rob posted above. |
Thanks, I believe that's what I needed. I used the IRP to generate a .rid with the OBCs but unfortunately it didn't control the box. Tried it several times, no go.
I learned the unworking blaster output and sure enough it differs from the original... not sure if this can tell us what is going wrong in this process. I captured the *unworking* blast twice, it looked the same in IR both times, but of course no way to test.
ridgen has worked well in the past with established protocols. The original I posted does control the Samsung (from the 15-1994 learned buttons) so hopefully there is a way to make this work. |
|
| Back to top |
|
|
KenL
Joined: 22 Nov 2006
Posts: 14
|
| Posted: Fri Nov 24, 2006 11:57 am Post subject: |
|
|
| The Robman wrote: | | ...Also, if we do create an upgrade for it, would you be willing to test it for us? |
Definitely. 
I'll post the rest of those buttons soon. |
|
| Back to top |
|
|
johnsfine
Site Admin
Joined: 10 Aug 2003
Posts: 4766
Location: Bedford, MA
|
| Posted: Fri Nov 24, 2006 3:03 pm Post subject: |
|
|
All I can guess is we have results from three different versions of MakeHex.exe:
I don't know how you got the incorrect results you got. I don't recall there being a version of MakeHex that acted that way.
I'm also not quite sure why I got the correct results I got on the computer I was using this morning. In the .irp file I gave before, I forgot the word "define" on the line that defines E. I don't recall making MakeHex understand that.
To get it right with the MakeHex that I'm using now I needed to change the .irp to
Device=32.0
define E=1
Function=0..255
Frequency=38000
One=498,-1498
Zero=498,-498
Form=;4488,-4492,d:8,s:8,498,-4498,e:4,f:8,-68,~f:8,498,-59154
But I don't think that would work for you. Because the one you used got "s" wrong, as if it didn't see the ".0" in the 32.0. I don't know how that happened.
Try getting a new copy of MakeHex from
http://john.fine.home.comcast.net/ir/makehex.zip
as well as adding the word "define" as I did above. |
|
| Back to top |
|
|
KenL
Joined: 22 Nov 2006
Posts: 14
|
| Posted: Fri Nov 24, 2006 6:24 pm Post subject: |
|
|
Used the fresh copy of MakeHex and the new IRP. Looks slightly different but still doesn't work.
Learned blast of it is here and I included the .rid file in case someone wants to look at that.
Could be something I'm doing or something ridgen is doing, but it looks like MakeHex is doing all the converting. Probably some user input error but it must be related to the protocol because the STB isn't seeing anything of the blast, and the output still doesn't match the original working learn. |
|
| Back to top |
|
|
johnsfine
Site Admin
Joined: 10 Aug 2003
Posts: 4766
Location: Bedford, MA
|
| Posted: Fri Nov 24, 2006 8:51 pm Post subject: |
|
|
I don't know how to read a .rid file.
The subdevice portion of the signal is still wrong.
We can at least find out whether MakeHex got that right or wrong. Just post one of the Pronto Hex strings generated by MakeHex.
When I test MakeHex with either of those .irp files it gets the subdevice right. |
|
| Back to top |
|
|
KenL
Joined: 22 Nov 2006
Posts: 14
|
| Posted: Fri Nov 24, 2006 11:35 pm Post subject: Thanks for sticking with this for so long... |
|
|
| johnsfine wrote: | I don't know how to read a .rid file.
|
Open it with ridgen editor.
For which the usage is:
| Quote: | Here is the procedure for going from a JP1 file (for KeymapMaster or RemoteMaster) to a RID file which can be uploaded to your ReplayTV:
1) Download RIDGen, MakeHex, and DecodeIR using the links in my previous post. Put all files in the same directory
2) Get RemoteMaster (a Java program) and the RDF files from the file section at http://www.hifi-remote.com/forums/d...egory&cat_id=81
3) Get the file for your device, from the files sections of either http://www.hifi-remote.com/forums/d...tegory&cat_id=4 or http://groups.yahoo.com/group/jp1/
4) Load that file into RM. Note that RM will load KeymapMaster configurations (.txt files) if you change the file type dropdown box in the file open dialog.
5) Run RIDGen. Copy the "Protocol" and "Device Number" fields from RM to RIDGen
6) Select the "Functions" tab in RM. Copy the EFC code for digit 0 to the EFC column in RIDGen for digit 0.
7) Click the "MakeHex" button to verify that the RID code gets created in RIDGen for digit 0. You should get a string of 0's and 1's and other symbols in the Initial bits and Repeated bits columns.
8 ) If that worked, then copy EFC codes all digits 0-9, Enter (if available), and Power from RM to RIDGen.
9) Click the "MakeHex" button again to convert all of the codes
10) Click "Save" in RIDGen, and save as C1000fi.rid (for cable code 1000 - if you change the code number, the file name will be different)
Notes:
- if the MakeHex button isn't available, or doesn't work, you need to download the MakeHex program, and extract all files into the same directory as RIDGen.exe
- There must be a .irp file for the Protocol you use. Not all protocols have .irp files. If your protocol doesn't have an .irp file, then check on the hifi-remote forum for assistance. |
I ran MakeHex alone and get strings but have no correlation for the rid fields needed. Normally what I get from IR.exe (DecodeIR.dll) is the frequency, protocol, device number, and OBC or EFC. Enter those into ridgen and it apparently uses MakeHex to generate Initial bits and Repeated bits (defined by 0,1,=,+,*,#) for the .rid which is saved and loaded into the ReplayTV.
In this case I'm evidently not getting those "bits" into the form needed by the Replay or not able to usefully capture needed parameters using the 15-1994/IR.exe/DecodeIR.dll?
But it's not for not getting the most expert help. |
|
| Back to top |
|
|
KenL
Joined: 22 Nov 2006
Posts: 14
|
| Posted: Sat Nov 25, 2006 12:33 am Post subject: Re: Thanks for sticking with this for so long... |
|
|
| johnsfine wrote: | | ...Just post one of the Pronto Hex strings generated by MakeHex. |
| KenL wrote: | | ...I ran MakeHex alone and get strings but have no correlation for the rid fields needed. |
Just at the darkest hour... finally got it!
That was a good hint. I'm pretty sure ridgen must have a bug with subdevices (never had to use one before) but it has legacy provisions for clipboard copy of working pronto hex. Manually copied all those and now it works!
WooHoo. 8)
Thanks a bunch for the IRP and verifying the hex. And thanks Robman for the OBCs. |
|
| Back to top |
|
|
johnsfine
Site Admin
Joined: 10 Aug 2003
Posts: 4766
Location: Bedford, MA
|
| Posted: Sat Nov 25, 2006 7:34 am Post subject: |
|
|
I'm confused by ridgen's use of EFC number.
I wonder why the author of ridgen chose to use EFC rather than OBC, since EFC is much harder and leads to errors.
As near as I can tell, ridgen does only lsb-comp translation of the EFC number so it will work only for protocols at use lsb-comp.
It seems to let you type in the OBC instead of the EFC, but then it doesn't seem to use it.
If so, I guess it is good that there is a legacy provision for using output from your own run of MakeHex. |
|
| Back to top |
|
|
DougP
Joined: 29 Nov 2006
Posts: 1
|
| Posted: Wed Nov 29, 2006 11:25 am Post subject: |
|
|
Ken,
Would you mind sharing your final working .rid file? I also have the Samsung DTB-H260F and ReplayTV.
- Doug |
|
| Back to top |
|
|
The Robman
Site Owner
Joined: 01 Aug 2003
Posts: 21238
Location: Chicago, IL
|
| Posted: Wed Nov 29, 2006 12:27 pm Post subject: |
|
|
And Ken, don't forget to post an IR file with the rest of the buttons.
_________________
Rob
www.hifi-remote.com
Please don't PM me with remote questions, post them in the forums so all the experts can help! |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
Powered by phpBB © 2001, 2005 phpBB Group
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
File Section
Wiki
