JP1 Remotes

I've searched and read just about everything on this forum and slingmedia's forums about custom remote codes. And... I've understood about 1/4 of it. I consider myself a pretty fast learner, but you guys are way beyond me. I was trying to get away with not having purchase the IR widget to capture the remote for my Amino 125, but I may have to go that route. Anyway, details...

I have a Slingbox AV (not sure on the IR Blaster version, yet) and I want to control my Amino 125. I even tried Sling's beta-remote site. The Slingbox AV can't learn remotes. I have a startech USB IRDA I used to program some automatic emergency difibulators at work, but that was with the software from the AED manufacturer. I've tried to get it to work with IR Scope, but no luck. I can't find the right USB-Serial Driver. I also have an IR reciever with a 3.5mm stereo plug on it. I think it came with my old PC tuner card. I'm not sure if either of those would work to capture the remote signals.

Regaurdless, I'm over my head. I just need it to work. HELP!?!?

asusong wrote:I've searched and read just about everything on this forum and slingmedia's forums about custom remote codes.

Regaurdless, I'm over my head. I just need it to work. HELP!?!?

Have you tried searching the file section for Amino? There are quite a few bin files available that might be compatible with your set-top box.

There are indications that the Amino 110 and 124 and 125 are all controlled by the same remote, however we also have posts that say that the 124 doesn't use the 110 file. I'd start off with the 110 file.

Let us know if it works or partially works.

vickyg2003 wrote:There are indications that the Amino 110 and 124 and 125 are all controlled by the same remote, however we also have posts that say that the 124 doesn't use the 110 file. I'd start off with the 110 file.

Let us know if it works or partially works.

Incidentally, the Setup Assistant has an Amino 110 remote preinstalled.

During Setup Assistant you would make these choices:

Device Type: Cablebox
Manufacturer: TVB PayVision
Model: Amino 100

or

Device Type: Cablebox
Manufacturer: TVB PayVision or Other
Model: Other
Alternate/Custom Code: V1125

I can't help at this stage as the 125 is decoding as the 'Zaptor' IR Protocol.

I see that Rob figured this out last Feb and it was added to DecodeiR

https://www.hifi-remote.com/forums/viewtopic.php?t=12520

But it never made it into PROTOCOLS.INI so I can't build a BIN file.

Thanks. I've tried some of the amino bin files, but not all. I'm also going to try the setup assistant again with the preinstalled amino box. If those don't work... I'm going to trying putting the slingbox on the ADB pvr instead of the amino. I see there are alot more adb bin files.

I wouldn't bother personally. This is a unique IR Protocol not used on any of the ADB boxes. We have to hope Rob can build an entry for PROTOCOLS.INI.

Although you can always build a remote using betaremotes.slingbox.com as it is back on-line now.

I see that I created a zip file that contains IR, RMDU, KM, PB and other files, so if the 125 uses the same device code(s) as the Zaptor, you can indeed create a BIN file.

https://www.hifi-remote.com/forums/dload ... le_id=8016

The learns in the Zaptor files show us as device code 16, sub-device 0. What do the new learns show up as?

alanrichey wrote:I wouldn't bother personally. This is a unique IR Protocol not used on any of the ADB boxes. We have to hope Rob can build an entry for PROTOCOLS.INI.

Although you can always build a remote using betaremotes.slingbox.com as it is back on-line now.

I would love to try betaremotes.slingbox.com, but as I said originally, Slingbox AV isn't able to "learn" remotes. That's according the betaremotes.slingbox.com site. It pops up an error message to that affect. Guess I have to upgrade my slingbox!

The Robman wrote:I see that I created a zip file that contains IR, RMDU, KM, PB and other files, so if the 125 uses the same device code(s) as the Zaptor, you can indeed create a BIN file.

https://www.hifi-remote.com/forums/dload ... le_id=8016

The learns in the Zaptor files show us as device code 16, sub-device 0. What do the new learns show up as?

Thanks, just what I needed. Interestingly this one decodes with a 'double' signal, first Device 13 then Device 9.

Do I use them as Device 1 and Device 2 ? And where do I get 'Byte 2' from ?

Can I see your ICT file?

https://www.hifi-remote.com/forums/dload ... le_id=8898

Three learns for 'Power', '1' & 'Left'.

Let me know if you need more.

Cheers

Al

Your signals all show a sub-device code of zero (that's why the device codes display as 9.0 rather than just 9).

I'm guessing that there are 2 device codes because the OEM wants this remote to be able to control 2 different boxes, one that uses device code 9 and another that uses device code 13. If I'm right, your box should respond to one of those codes, but probably not the other, so try creating two upgrades, one using device code 13 and another using device code 9, and ask the user to test them both. You could make it even easier by calling them C2013 and C2009, so if one works, we know which one it is!

You didn't mention byte 2 on the function Tab in your RMDU file.

Important ?

I'd forgotten there was a checksum in there.

Actually, I just took a closer look at the signals and I don't think they're a close enough match to the Zaptor signals for you to be able to use that upgrade.

I'm about to head about of town, so this'll have to wait until next week.

In the meantime, could you put together a single ICT file (rather than multiple files zipped together) which contains all of the buttons from this STB. Use the NOTE feature to document which button each signal is.