Motorola vip 1853 kpn the netherland

[t4_ravenbird]

Here is the rmir :
http://www.hifi-remote.com/forums/dload ... e_id=12258

The upgrade from UEI is for Altibox VIP 1963 but this box uses same remote as VIP 1853.

Altibox has been around for some time and has revised their box several times, check bottom of this page : http://www.altibox.no/privat/kundeservi ... iledninger
I came to think of something; all (or most) of those boxes uses same remote so it could be they have made an effort to make the IR signature of the VIP 1853 similar and compatible to some older box (and thereby deviating from other VIP 1853's, just speculating..)
Actually, the OEM remote also comes in 2 or 3 flavors (compatible of course) but with slight variations in keys. I have learned the keys from this : http://www.altibox.no/c/document_librar ... upId=10327

[3FG]

OK, the box uses Zaptor instead of CanalSatLD. Zaptor can be sent at either 57KHz or 36KHz. The upgrade from UEI shoots Zaptor at 57KHz, while your learns were at 36KHz.

There a couple of ways to change the frequency. One is to edit the upgrade you've called "Altibox UEI", and which is shown as Manual Settings: 01CD. Change Device 3 from 80 to 81. That will tell the executor to send 36KHz.

Another way, which is the way we usually do things, is to add the following entry to protocols.ini

Code: Select all

[Zaptor Official]
PID=01 CD
DevParms=Device:8=0, Subdevice:7=0, E:4=5, Freq=1:36KHz|57KHz
DeviceTranslator=Translator(0,8) Translator(1,7,9) Translator(2,4,16) Translator(comp,3,1,23) 
FixedData=0D 00 50
CmdParms=OBC:8=0
DefaultCmd=00 
CmdTranslator=Translator(0,8) 
Code.S3C80=2c 5c 31 8b 15 87 80 10 08 08 00 a5 00 94 00 a5 00 94 91 f9 05 0a 03 9e 01 4a 76 05 01 6b 09 e6 0e 47 e6 0f 92 f6 01 55 08 06 e4 05 06 09 05 f6 dc fc f6 dc e9 7b fb 46 04 80 f6 dc fc f6 01 73 1c 1e f6 01 4c 1c 22 f6 01 64 f6 01 70 8d 01 0a 56 06 f0 b0 c0 5c 04 87 15 02 f6 dd 12 5a f8 56 c0 0f 44 c0 06 af 28 c1 f0 c1 02 12 02 01 af
Code.MAXQ610=21 46 31 ac 00 44 13 00 13 00 00 00 13 00 13 00 00 00 b1 10 93 00 6c 00 26 00 00 00 0c 00 0c 00 00 00 0c 00 0c 00 00 00 8f 0a 5d 00 44 00 18 00 00 00 00 80 44 56 08 d2 01 5e 35 6f 00 16 d2 d2 f0 16 d1 d1 7f 51 df d0 00 03 d5 df d0 51 df d1 00 03 d5 d5 df 03 d5 d5 d1 51 df d3 00 03 d5 d5 df 03 d5 d5 d3 16 d5 d5 0f 51 d5 d5 00 03 d5 d5 d2 15 d6 d1 80 13 d7 d5 80 42 50 25 70 71 73 32 35 42 40 05 70 76 73 32 37

I expect that if you use RMIR to download from the Xsight Lite, RMIR should recognize the UEI upgrade as Zaptor Official. An you should also be able to create from scratch a new upgrade using this executor. However, I have an ARXX12G 8011, which is configured in firmware as 12 device remote, similar to the Xsight Plus. I haven't been able to add any new upgrades via RMIR 2.03 Alpha 21e, but I think mathdon did all of his development using a Lite, so it may go better for you. I'd appreciate it if you would try.

I tested this Zaptor Official executor using an Atlas 1056B03, which also has a MAXQ610 processor.

[t4_ravenbird]

... I expect that if you use RMIR to download from the Xsight Lite, RMIR should recognize the UEI upgrade as Zaptor Official.

It did! And there was now a field at 57kHz that I could change into 36 and upload again to the remote and it now works beautifully!

An you should also be able to create from scratch a new upgrade using this executor.

Yes, it seems to work too. However, I run into some questions when I try to fill in the Functions tab (since I am very new at this stuff)
Like ; what values should I use in the 'KeyGID' column? I suspect these have special meaning but dont know where to find the assignements.
And are there some best practices howto map functions/buttons that I should be familiar with?

*

Thanks a lot for the brilliant support on this forum!

[t4_ravenbird]

An you should also be able to create from scratch a new upgrade using this executor.

Yes, managed to do so.
I found some good info in the sticky post http://www.hifi-remote.com/forums/viewtopic.php?t=12103
I uploaded my rmdu to http://www.hifi-remote.com/forums/dload ... e_id=12260
I still dont know what KeyGID column is so I left it at zero.

[t4_ravenbird]

I now tried the Altibox with URC-7130 Essence 3 but that failed. It uploads OK but the remote seems to send signals that does not work. Is this about missing CPU-support in the new ZaptorOfficial protocol maybe?

[3FG]

Yes, I didn't include the code for Samsung processors. I edited my post (4 posts above this) to include it, and you should replace the entry in protocols.ini with the new version in the code block. I haven't tested it, so let us know how it works.

There is no official executor for HCS08 remotes.

[t4_ravenbird]

Hmm, no it does not seem to work.
There seems to be no change at all - I have tried to generate new rmir with protocol.ini containing only MAXQ610 and then with protocol.ini containing only S3C80 entry. Strangely, it seems to behave identical, that is ; some keys does hit a function, but the wrong one.
I would expected that with only MAXQ610 that RMIR was unable to create an upgrade at all for this remote but that is not the case?

I notice that on the upgrade editor/output tab it says "upgrade protocol not required" and then I notice that in the rdf for the remote the protocol "01 cd" is listed and this seems to be same id same as the new "zaptor official"?

[t4_ravenbird]

Sorry, my bad. After fiddling some more I got it to work. I messed up with the 'device' and 'subdevice' settings and it took a while before I found it.
So ; the settings you have provided seems to work just fine, thanks again!

[3FG]

I failed to notice that the 7130 has 01CD built in. So for that remote RMIR doesn't need the S3C80.code, since it is already built in. However, it does need the rest of the Zaptor Official entry so that it knows how to translate the device numbers, etc into Hex data for the executor.

Nice to know it is working.