This is the JP1 beginners forum. There's no such thing as a stupid question in here, so post away, but this forum is just for JP1 users and people considering JP1, non-JP1 users please use the appropriate forum above!
begin remote
name daytek.lvm37
bits 16
flags SPACE_ENC|CONST_LENGTH
eps 30
aeps 100
header 9059 4427
one 619 1628
zero 619 502
ptrail 620
repeat 9048 2185
pre_data_bits 16
pre_data 0xF7
gap 107799
toggle_bit_mask 0x0
begin codes
Power 0x8877
Mute 0xC837
Tv 0xC03F
Line 0xD02F
Display 0x50AF
Caption 0x609F
PIPon/off 0x6A95
PIPswap 0x5AA5
PIPsource 0xE01F
PIPsound 0x52AD
One 0xB847
Two 0x38C7
Three 0x629D
Four 0xA857
Five 0x28D7
Six 0xA25D
Seven 0x00FF
Eight 0xF807
Nine 0xD827
Zero 0x7887
Vol+ 0x10EF
Vol- 0x7A85
Ch+ 0x12ED
Ch- 0xB24D
MTS 0x1AE5
Freeze 0x2AD5
Sleep 0x3AC5
TVMenu 0xF20D
Up 0xE21D
Down 0xD22D
Left 0xEA15
Right 0xCA35
Enter 0x20DF
P.STD 0xC23D
S.STD 0x0AF5
Aspect 0x4AB5
Exit 0x9A650
end remote
Using this information, and the help from people here, I determined the hex to use in RM. This is what I came up with:
The problem is, it doesn't work. I copy it over to my Atlas remote and give it a try and nothing -- I haven't tried to re-capture it with LIRC yet but I wanted to make sure that what I had done was correct? Can someone check this please?
Please edit your post above to remove the files. If you think other experts should look at those files replace them with URLs. But I already looked at your .ir file:
I see nothing wrong with it. I don't know why it doesn't duplicate the signals recorded in that LIRC file. If no other expert quickly spots the problem, you should capture the signals from your TV/0162 upgrade into LIRC and post that. Hopefully that will tell us what went wrong.
I think it is OK to post .lirc files in the thread, especially if they're not much bigger than the one you posted above. But .ir files and .rmdu files should not be posted into the thread (even if they aren't bigger than your .lirc file. We look at .ir files and .rmdu files by loading them into the appropriate programs, so posting them into a threads forces us to do extra work to copy them out of the thread without triggering the reformatting that our browser might do (because it thinks the file is human readable text not program readable data). If this were an LIRC forum, we might also use a program to read .lirc files, but in a JP1 forum, most of those who understand lirc files do so without having a copy of lirc installed.
Hi Norm. I'm sorry. I should have said post them in the diagnosis area and put the links here. I should have been more precise. I'll be more careful in my wording in the future.
Ok so further diagnosis shows that when I upgrade the remote with a new device, I can't actually assign that device to the TV button on the Atlas. When I download from the remote after uploading, the device assignments change -- specifically the tv always goes to 0047. When I try to set it using the remote, I get a long led indicating the code is invalid but starting from fresh, and doing a download shows the code was upgraded to it.
I did attempt to set the aux button to tv/0672 (I tried a few that weren't already in the remote) but again, it wouldn't change the device to a TV, reverted back to vcr/dvd and 0060, which I assume is the first available code for that device.
Am I missing something? Do I need to set an option to allow these codes to be changed?
Your remote is coming up with an error and doing a RESET.
A lot of errors were recently discovered in the Atlas RDF's and they've been updated but are not in the official RDF's yet.
Check here and see if a new RDF is available for your Atlas.
Also with the Atlas its best to start with a downloaded file instead and adding your upgrade because there are a lot of settings involved.
Last edited by vickyg2003 on Tue Jan 08, 2008 2:19 pm, edited 1 time in total.
It sounds like Vicky knows more about the status of our Atlas support than I do. But I'll add some details:
As Vicky said, your results pretty clearly suggest IR.exe was using an RDF file that is not compatible with your Atlas.
Since you uploaded garbage to your Atlas, the current contents of its eeprom shouldn't be trusted. You should do a factory reset on the Atlas and download and save the result of that to a .ir file.
If there are remaining questions about what is correct for the RDF file, one of the RDF experts here will need to look at that (factory reset) .ir file and maybe some other .ir files downloaded from your remote, so be prepared to upload that to the diagnosis area and provide its URL.
As Vicky said, that factory reset .ir file should be your starting point in IR.exe. You should not use the File/New command in IR.exe to produce a starting point. File/New requires a higer level of perfection in the RDF file than other operations require. If you had used File/New before, it is possible your RDF file is already good enough to use if you start with the factory reset image rather than with File/New.
On reread of this thread, I'm a bit confused about why we were talking about "Kameleon" in the first post, but your .ir file was For Atlas_5-device_PVR...(30333033) and your later post is about "Atlas". (But then I don't know anything about Atlas nor Kameleon).
I should have asked that. So your backup may be a better starting point than a factory reset image (comparing the two might also be informative).
I just wanted to make sure your next starting point wasn't already corrupted by a bad RDF.
Since you didn't use File/New it is becomming even clearer that the RDF file you used isn't good enough. I hope a better one is already posted somewhere.
- I will restore to factory default, look for new file and upload my backup and start fresh again.