Page 1 of 3
Grundig DTR 1560 Micro
Posted: Fri Feb 02, 2007 10:31 am
by zbrarm
1. Device: Grundig DTR 1560 Micro
2. Type of device: Digital Terrestrial Receiver
3. Year: 2006
4. JP1/UEI Remote model: URC-39720 (Force ETPSTPS0)
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)? No
9. Partially working setup code? No
10. Learning remote question?
I recently bought a
Grundig Digital Terrestrial Receiver and wanted to make an upgrade for it for my Force Remote (ETPSTPS0). Problem is the protocol regonized in the learned functions is Blaupunkt (or Blaupunkt{body}) protocol (dev 0), but its not working when I try to make the setup code in RM (OBC does not match with EFC/Hex).
I uploaded my IR file with a bunch of learned functions from the grundig remote
here in diagnosis area.
Any chance to get a working protocol on this one ?
Re: Grundig DTR 1560 Micro protocol
Posted: Fri Feb 02, 2007 10:56 am
by johnsfine
zbrarm wrote:Problem is the protocol regonized in the learned functions is Blaupunkt
Blaupunkt is the correct protocol.
zbrarm wrote:
but its not working when I try to make the setup code in RM (OBC does not match with EFC/Hex).
You are saying the OBC/EFC translation rules in the decoder aren't consistent with the rules in RM. That might be a bug, or it might be legitimate behavior. I'll try to find time later to check that.
Is that your only reason for say "its not working"? Or did you finish making an upgrade and transfer to IR.exe and upload to your remote and test?
When the translation rules are inconsistent, it is usually best to just use OBC and ignore EFC.
Re: Grundig DTR 1560 Micro protocol
Posted: Fri Feb 02, 2007 11:51 am
by zbrarm
johnsfine wrote:Is that your only reason for say "its not working"? Or did you finish making an upgrade and transfer to IR.exe and upload to your remote and test?
When the translation rules are inconsistent, it is usually best to just use OBC and ignore EFC.
Yes, i have made several upgrades and I tried both with the OBC and with EFC and I cant seem to get any of them working.
Posted: Fri Feb 02, 2007 12:08 pm
by Mark Pierson
Did you remember to copy the Protocol Upgrade into IR in addition to the Device Upgrade?
Posted: Fri Feb 02, 2007 12:13 pm
by zbrarm
yep
Posted: Fri Feb 02, 2007 12:31 pm
by johnsfine
Sorry. I should have looked earlier at your learned signals rather than relying on my memory of other Grundig devices.
The structure of your signals is Blaupunkt, but the frequency is 36Khz. Blaupunkt is usually 30Khz.
There is a simple change to an upgrade protocol (assuming one is required/provided, as your last post implies) to change the frequency.
I don't have that handy. I expect some other expert will tell you. Otherwise I'll get that for you later.
Posted: Fri Feb 02, 2007 12:46 pm
by zbrarm
When i choose Blaupunkt in RM it actually says NEC 36.7 kHz in protocol notes.
Posted: Fri Feb 02, 2007 1:01 pm
by Mark Pierson
johnsfine wrote:There is a simple change to an upgrade protocol (assuming one is required/provided, as your last post implies) to change the frequency.
Try changing the first 2 bytes of the protocol code from "54 AD" to "45 95".
Posted: Fri Feb 02, 2007 1:02 pm
by johnsfine
zbrarm wrote:When i choose Blaupunkt in RM it actually says NEC 36.7 kHz in protocol notes.
I just did a "CVS annotate" on protocols.ini at sourceforge. Greg added the Blaupunkt protocol on April 1, 2003. I assume the Notes section was an editing accident. Hopefully the rest is more reasonable.
I'm rather surprised that entry in protocols.ini hasn't been edited more than that.
But anyway, that comment in the Notes has nothing to do with reality.
Posted: Fri Feb 02, 2007 1:12 pm
by zbrarm
Mark Pierson wrote:Try changing the first 2 bytes of the protocol code from "54 AD" to "45 95".
Just tried this (for both OBC and EFC). Sadly still not working.
Posted: Fri Feb 02, 2007 1:14 pm
by zbrarm
johnsfine wrote:But anyway, that comment in the Notes has nothing to do with reality.
Ok, ill ignore the notes

Posted: Fri Feb 02, 2007 1:31 pm
by zbrarm
I just updated the IR file (link in first post) to include both upgrades i made (OBC and EFC).
Posted: Fri Feb 02, 2007 2:24 pm
by johnsfine
1) Did you understand Mark's instructions to change the first two bytes of the protocol upgrade? Those bytes are not changed in the .ir file you just indicated.
In Ir.exe in the protocols tab, you can select the right protocol (00A5) then click the Edit button, then change those first two bytes.
2) There are many old models in which having a protocol upgrade and learned signals in the same device mode causes serious malfunction. I don't know if the "Force" is such a model, but I suspect it is.
Either delete all the learned signals from the .ir file you use to test the upgrade or assign the upgrade to a different device button for testing.
Posted: Fri Feb 02, 2007 3:01 pm
by Mark Pierson
I'm starting to wonder if perhaps the Force RDF is wrong? It wants the Blaukpunkt protocol upgrade but the Dreambox 1k doesn't. I would assume those two remotes are similar based on them sharing the same signature. Perhaps you should try removing the protocol upgrade and see what happens (in addition to John's comments about the learned signals/upgrade problem).
Posted: Fri Feb 02, 2007 3:14 pm
by johnsfine
Mark Pierson wrote:I'm starting to wonder if perhaps the Force RDF is wrong? It wants the Blaukpunkt protocol upgrade but the Dreambox 1k doesn't. I would assume those two remotes are similar based on them sharing the same signature. Perhaps you should try removing the protocol upgrade and see what happens (in addition to John's comments about the learned signals/upgrade problem).
But if the frequency is the problem (or both the frequence and learned signals are problems) then the built-in protocol would be wrong.
Trying the built-in protocol, even assuming it exists, would only help if the frequency is not a problem and either the learned signals are the problem or the protocol upgrade itself is wrong.