JP1 Remotes

t4_ravenbird · Joined: 01 Jan 2014 Posts: 38

Here is the rmir :
http://www.hifi-remote.com/forums/dload.php?action=file&file_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/kundeservice/brukerveiledninger
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_library/get_file?uuid=b7c49758-0f35-49eb-b55c-6278e3764933&groupId=10327

3FG · Expert Joined: 19 May 2009 Posts: 3367

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

t4_ravenbird · Joined: 01 Jan 2014 Posts: 38

t4_ravenbird · Joined: 01 Jan 2014 Posts: 38

t4_ravenbird · Joined: 01 Jan 2014 Posts: 38

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 · Expert Joined: 19 May 2009 Posts: 3367

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 · Joined: 01 Jan 2014 Posts: 38

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 · Joined: 01 Jan 2014 Posts: 38

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 · Expert Joined: 19 May 2009 Posts: 3367

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.