Page 1 of 2
BIN file needed for Sagemcom DCI85HD KD
Posted: Fri Oct 24, 2014 2:55 am
by Youngtimer
Dear all,
I posted my request here:
https://www.hifi-remote.com/forums/viewt ... 213#p116213
However, I don't know how to make a BIN file.
I appreciate any help

Posted: Sat Oct 25, 2014 3:09 am
by alanrichey
Posted: Sat Oct 25, 2014 11:27 am
by vickyg2003
Aian, Don't forget to update your non-repeating protocol sheet.
https://www.hifi-remote.com/forums/dload ... e_id=11416
Posted: Sat Oct 25, 2014 3:12 pm
by alanrichey
Decided it might make more sense to simply post the PROTOCOLS.INI that I use, which includes all the newer protocols and all the 'no repeat' protocols. Acts as a back up for me if I ever lose the original

Posted: Mon Oct 27, 2014 5:05 am
by Youngtimer
Wonderful - thanks a lot! I will give it a try tonight. In the readme.txt I am encouraged to communicate if a particular remote image matches well. In the Sling device directory, the "Kabel Deutschland AG" device called "DVR20" has an image of the exact remote that sits on my coffee table.
Not sure if that info helps but I thought I'd put it out there.,
Cheers,
Youngtimer
Posted: Mon Oct 27, 2014 7:49 am
by alanrichey
Posted: Mon Oct 27, 2014 2:35 pm
by Youngtimer
I tried it just now and observe the following:
- In principle it works (yay!)
- Instead of jumping one item of the list when pressing an arrow key, I now have to press each arrow key twice to have an effect. This is much more workable than the situation with the jumps so if that's what it takes to get it to work, I'm perfectly happy. If you have the ambition to get it 100% right, I'm happy to do further testing
- Not sure what to expect from the "realistic image" in the 2nd post. Should I be looking for an RC that looks exactly like the one on my coffee table (and in the DVR20 of the Slingbox directory)? That is not the case. To me, it looks as generic as the previous one (V2010_PL) and works just as well. Both files work fine with the above constraint.
Cheers and thanks!
Posted: Mon Oct 27, 2014 4:17 pm
by alanrichey
It should show the realistic image. Are you following the instructions exactly ? I just installed it on my Pro-HD and the correct image appeared.
If you are installing on a 350/500/M1 are you entering the manufacturer ?
Posted: Tue Oct 28, 2014 1:50 pm
by Youngtimer
Thanks for the pointers. I have a 350 and made sure I selected the manufacturer correctly. Thought I had done that yesterday but I tried again today and it works: I now have the realistic image.
Everything works now with the constraint that I have to press each arrow button twice to jump one item (before, pressing once jumped 2 items). Not sure if you'd like to do anything about it. In any case: I appreciate your help!
Posted: Wed Oct 29, 2014 1:05 am
by alanrichey
Well all this started with me building you a non-repeating remote to cure a double skip. So why don't we try reversing that and going back to a repeating protocol ?
https://www.hifi-remote.com/forums/dload ... e_id=12858
Better ?
Posted: Wed Oct 29, 2014 1:59 pm
by Youngtimer
I hate to say it, but this version does the skipping thing again (press arrow key twice, move 2 rows or columns in the navigation). As mentioned before, yesterday's version requires pressing an arrow button twice to yield a move by 1. Some sort of middle ground would be the ultimate behavior but as I said before: I am happy with yesterday's version as well.
By the way, I made an interesting observation just now: As I mentioned, e.g. pressing down twice moves the cursor down one step. Out of curiosity, I tried down/up to see if the commands cancel each other out or something along those lines. What actually happened, was that the cursor always moved in the direction of the 2nd push. Pressing down/up moves it up one step, pressing right/down moves it down one step - you get my drift. It is almost like the first push initializes something and the second one executes it. Forgive my certainly amateurish lingo but I thought that the observation is somewhat systematic and may be able to help you pinpoint what's going on.
Cheers,
Youngtimer
Posted: Wed Oct 29, 2014 2:20 pm
by 3FG
In a couple of days, I'll have time to make an executor that sends exactly two frames. That may fix your problem, or the problem may actually be related to the toggle bit in the Nokia protocol. Depending on everybody's patience, we should eventually be able to tame this.
Posted: Wed Oct 29, 2014 2:55 pm
by alanrichey
Fascinating stuff

Posted: Thu Oct 30, 2014 4:28 am
by Youngtimer
alanrichey wrote:Fascinating stuff

Indeed

Looking forward to hear from you guys!
Posted: Thu Oct 30, 2014 11:32 pm
by 3FG
Code: Select all
[Nokia32 one repeat]
PID=01 FF
DevParms=Device,Sub Device,X:7
DeviceTranslator=Translator(0,8,0) Translator(1,8,8) Translator(2,7,17)
FixedData=00 00 00
CmdParms=OBC=0
CmdTranslator=Translator()
Code.S3C80=47 93 31 8B 12 87 44 00 00 00 54 9C 2C 00 54 00 22 9C 40 00 CE 00 76 F6 FF 1E F6 FF 1E AF 1C 1E F6 01 4C 4C 00 87 64 03 5C 04 F6 FF 37 4E 37 44 F4 1C 14 F6 01 4C AF 1C 18 F6 01 4C 90 C6 90 C6 28 C6 56 C2 03 2E C6 F8 00 4F F6 01 58 2A F7 5A E6 AF