RM question: duration control urc 3990RJ0-04

Post by **vickyg2003** » Sat Feb 07, 2009 11:31 am

is it possible that my remote is to "stupid" to handle device combiner?

I think that the HCS08 Device Combiner is the problem. I popped open the IR file that mike posted, and it doesn't look like a valid protocol to me. Protocols almost always end with a JMP or a RET or some other kind of instruction to stop the remote from falling into data. I'll bet this protocol was missing a few bytes. When the remote executes data it will eventually puke and reset, (double blink).

Post by **The Robman** » Sat Feb 07, 2009 12:00 pm

stabilo555 wrote:One more thing: the working upgrade uses panasonic combo protocol. In device combiner i can only select panasonic. Could this be the problem?

The upgrade uses the combo protocol because some of the TV functions use a different sub-device code. The device combiner only works with protocols that use 1 variable byte of data, and the combo uses 2 variable bytes. However, all of the power codes for your TV use the same sub-device code, so I used the standard Panasonic protocol in the device combiner upgrade that I created.

If the upgrade didn't work, I can only assume that we have the wrong device combiner settings for your remote. Could you do me a favor and go to the Raw Data tab in IR and verify that the signature for your remote is "10381038".

mr_d_p_gumby · Post by **mr_d_p_gumby** » Sat Feb 07, 2009 2:32 pm

vickyg2003 wrote:I think that the HCS08 Device Combiner is the problem. I popped open the IR file that mike posted, and it doesn't look like a valid protocol to me. Protocols almost always end with a JMP or a RET or some other kind of instruction to stop the remote from falling into data. I'll bet this protocol was missing a few bytes. When the remote executes data it will eventually puke and reset, (double blink).

Vicky, the device combiner protocol stores the PIDs & fixed data at the end of the protocol code, so you won't see a normal JMP or RET, etc. there. At this point I can only think of two other things that might be wrong. First, as Rob mentioned, the RDF may not have the right DC settings for this remote. Or, maybe these Dreambox remotes have some pecuiliar quirk that is preventing the DC from executing correctly.

Post by **vickyg2003** » Sat Feb 07, 2009 3:06 pm

Sorry Mike.

I didn't realize data would be stored at the end of the protocol, and didn't see anything to keep it from falling in there in IR.

stabilo555 · Post by **stabilo555** » Sun Feb 08, 2009 4:05 am

@ the robman: The signature displayed in the raw data tab is 10381038

stabilo555 · Post by **stabilo555** » Sun Feb 08, 2009 8:47 am

First, as Rob mentioned, the RDF may not have the right DC settings for this remote.

I also tried this rdf

http://www.hifi-remote.com/forums/dload ... le_id=6214

with device combiner. This rdf doesnt work for my tv, but this way i wanted to find out if mr_d_p_gumby is right with his assumption. The problem stays the same-blinking dream button. So I think the RDF isnt the problem...

gfb107 · Post by **gfb107** » Sun Feb 08, 2009 9:24 am

That isn't an RDF (Remote Definition File), which describes the details of the remote you are programming.

It's a RMDU (Remote Master Device Upgrade) which describes the details of the IR signals used to control a device. The device in this case is a TV.

stabilo555 · Post by **stabilo555** » Tue Feb 10, 2009 12:40 pm

So, what shall I do? Forget it? Wait? Pray?

stabilo555 · Post by **stabilo555** » Wed Feb 25, 2009 1:00 pm

solved the probem, but dont know how. Maybe anyone could help this sometime:

I´ve earlier tried to send the discrete code for power on (phantom key) several times, this didnt work. Now I found out, that button green also turns on the tv. No idea why, cause i didnt make a keymove for this button and i also think, that i didnt apply the discrete power on to it (but i'm not sure!). Anyway. Creating a macro, which pushes the green button three times turns the tv on.

So at least, my mega power on works: one button pressed turns on sat, amp, tv, correct input on tv, three different lights and pulls the window shade down. GREAT!

THX for your help!!!!!!

edit:
Was a mistake, only works if the tv was turned on before and was running for some time. so could anyone have a look on this rdf?

sigue · Post by **sigue** » Sat Apr 11, 2009 2:26 am

I have nearly the same problem.

I try with my URC-39930 BJ0-03 dreambox remote, witch signature is 10381038, to program a long keypress for a BigBen DVD Remote to turn of a PS3
I'm using the NECx2 protocol witch works very fine.

I tried to build a device combiner for the PS-Home key, but when i push the key, the red light of the device remote key stay on, I have to put off the batteries to witch it off.
I have 31 3D 35 for fixed data
I tried durations of 0, 1 2 3 4, same probleme.
I tried the update protocole from RemoteMaster, and the one from this thread, but the probleme is still here.

To continu with this thread, here is the RDF I use :
http://www.hifi-remote.com/forums/dload ... le_id=6535

note: I first used last RemoteMaster 1.90, but as the duration column was missing, i had to take the RemoteMaster 1.87b version back.

binky123 · Post by **binky123** » Sat Apr 11, 2009 6:59 pm

I believe there was a bug in how RM generated the Device Combiner code for a HCS08 remote(10381038) which was fixed in RM 1.89. You will have to post your .IR file so someone can look at the generated device upgrade and protocol code and see if there are any errors. This remote has a hidden upgrade area but I don't think that should affect the device combiner.

I think the default RDF and your RDF are pretty much the same and use the same device combiner values.

sigue · Post by **sigue** » Sun Apr 12, 2009 3:02 am

That was it !
It's working with RM 1.89.

I hope futur versions of RM will include back the duration column, witch miss RM 1.90.

Thanks a lot binky123.