JP1 Remotes

cba123 · Joined: 09 Aug 2015 Posts: 9

I am having trouble adding pauses to my device specific macros on my 1056B03 remote.

I am using RMIR from RemoteMaster v2.03 on an old Pentium laptop with 98MB ram running Java6 under Win2000 (it has a parallel port for my old JP1 cable for my older URC-8810B00).

Using RMIR, I downloaded from my 1056B03 remote.
Under the devices tab, I created a new device, which opened the Device Upgrade Editor window.
On the Setup tab, I selected Pause Protocol (Special), with type Cable
On the Functions tab, I set Duration to 250 for name "0"
On the Buttons/Layout tab, I mapped button 0 to function 0
I clicked OK, to close the Device Upgrade Editor window to return back to the RMIR window, and mapped the Unassigned Device Upgrade to VCR.

Under Special Functions tab, I created a new DSM for device TV, Key D
Under keys, I added TV,1,VCR,0,TV,2, and clicked OK

I uploaded to my 1056B03 remote, and when I test the D macro, there is no noticeable pause between sending the TV key 1 and TV key 2 signals. Using duration 250 on VCR button 0 should have had a noticeable delay before TV key 2 was sent.

In the Output tab on the Device Upgrade Editor, there is a REQUIRED Upgrade Protocol Code, but there is no Protocol tab in RMIR for the 1056B03 remote to paste the new protocol (there is a Protocol tab for my older URC-8810B00), so does the Upgrade Protocol Code get added automatically by adding the new Pause Protocol device on the device tab?

User 3FG indicated in an older 2015 posts that the pause protocol does work on the 1056B03 remote, so I am sure I am missing something.

The Robman · Posted: Sun Mar 07, 2021 2:25 pm Post subject:

As well as you described what you did, it's quite possible there's some small detail that you missed or did wrong, and most experts won't be able to tell that just from your description, but they would be able to tell from looking at your RMIR file, so I recommend that you upload it to the Diagnosis Area and then post a link to it here.

As for RMIR, the version that you are using is several versions out of date, so I would recommend downloading the latest version, which is v2.12.8 at the moment. (I'm not saying that it will fix your issue though).
_________________
Rob
www.hifi-remote.com
Please don't PM me with remote questions, post them in the forums so all the experts can help!

mathdon · Posted: Sun Mar 07, 2021 6:22 pm Post subject:

Rob, he can't update RMIR to the latest version, as recent versions need Java 8 and he has Java 6. He has Win2000 which does not support Java 8.
_________________
Graham

The Robman · Posted: Sun Mar 07, 2021 6:57 pm Post subject:

mathdon · Posted: Mon Mar 08, 2021 8:05 am Post subject:

From your description, cba123, I have tried to understand how you are using the Pause Protocol and think you are using it in the same way that I am in my setup. The intention of the Pause Protocol is that you use it in a key move but I, and I think you also, are creating a device with this as its protocol. For this to work, you need to delete the line

KeyMovesOnly=1

from the entry for Pause Protocol (Special) in protocols.ini. Please give this a try and report back.
_________________
Graham

cba123 · Joined: 09 Aug 2015 Posts: 9

Thanks, I retried again last night and got it to work.

I didn't edit anything in the protocols.ini file. I deleted/overwrote the original bad rmir saved test file so I am not sure what was different this time around.

Last night, I started with my original factory 981 reset base image with 1056b03 extender v1.00 installed, and just added the pause protocol (special) device, as per my steps noted in the OP, and tested using just the factory default devices, and it worked; the VCR device key stayed lit for the duration of the pause. Then, I added all my devices back on, one by one, retesting as I went to see that the test pause macro still worked, until it was completely reprogrammed. My final version does not have the pause protocol attached to any device key, and uses a shift-pause keymove used in my DSM macros.

When I had the problem, I already had all my devices, macros, etc already working on the remote, and downloaded that image from the remote before I attempted to add the pause protocol to the remote, but the sequence of steps shouldn't have caused the problems.

With the older parallel port JP1 cable, I never had any problems, and I only started using a FTDI JP1.x cable with the 1056b03 remotes, and it may have been that I was pulling the JP1 cable off the remote too soon after the RMIR upload finished.

Last night, I delayed pulling the cable by a few seconds and noticed that the lights on the FTDI board started flashing again. Previously, I was pulling the cable after the lights stopped flashing. But, now I noticed that during uploads, the lights on my FTDI board flashes for a few seconds, then stops flashing for a few seconds, and then starts flashing again for a few more seconds before stopping a second time.

My earlier uploads to this remote before adding the pause protocol worked, so I didn't think pulling the cable would be the cause, but maybe the pause protocol itself is saved nearer the end of the upload (during the second lights flashing part)?

Anyways, I will chalk this up to user error; either by using a bad/corrupted image as a starting point or was pulling the cable off the remote too quickly after uploading.

cba123 · Joined: 09 Aug 2015 Posts: 9

The Robman · Posted: Mon Mar 08, 2021 7:22 pm Post subject:

Do you still have a lot of older EEPROM based remotes that work with the parallel cable? I see that you're using an FTDI constructed cable now, so why are you still using the old PC? That FTDI cable should work on your latest PC too. I use an FTDI cable on my Lenovo Yoga 730, which is running 64-bit Windows 10 and Java 14.0.2. And I do have plenty of old EEPROM remotes, so I have an EEPROM adapter for those, which means I can use my FTDI cable for them too.
_________________
Rob
www.hifi-remote.com
Please don't PM me with remote questions, post them in the forums so all the experts can help!

cba123 · Joined: 09 Aug 2015 Posts: 9

The Robman · Posted: Tue Mar 09, 2021 9:14 am Post subject:

I wasn't suggesting that you buy an adapter, I was asking if you still have EEPROM based remotes. You mentioned using an FTDI cable, which won't work with EEPROM remotes without an adapter, so I assume you use it to program JP1.x remotes, and I was just attempting (and apparently failing) to point out that the FTDI cable will work on the most modern PCs. So, bottom line, while you should keep your old PC around for the EEPROM remotes and the parallel cable, you can use your more modern PC for the FTDI cable with your JP1.x remotes.

Hope that's a little bit more clear this time.
_________________
Rob
www.hifi-remote.com
Please don't PM me with remote questions, post them in the forums so all the experts can help!