I Need to Modify My Remote AGAIN
Moderator: Moderators
Jim has one 1067BX3 and one 1067BC4 remote. I'm trying to convert the BX3 (S3F80) remote image to work with the BC4 (MAXQ610). One of his upgrades is a Pioneer 4DEV, which was written by the JP1 community. I'm not able to convert that to MAXQ assembler, so I'm trying to use the built in PID 00 7E or 00 6A. But the Pioneer executors are somewhat scrambled in protocols.ini, and I'm confused.
Jim,
Try this RMIR file for your 2556 1067BC4 remote. You also need to use a slightly revised RDF file and a newer protocols.ini file.
Protocols.ini goes in the same folder as RemoteMaster.jar, and of course the RDF file goes in your RDF folder.
I also encourage you in RMIR to do a File\Set Directory\RDF folder to make sure it is pointed at the folder containing your RDFs and then do this again for the Image Folder, making sure it is pointed at where your images/maps are.
You can see a picture of the remote in the Device Editor Window, and looking at the Layout tab.
Try this RMIR file for your 2556 1067BC4 remote. You also need to use a slightly revised RDF file and a newer protocols.ini file.
Protocols.ini goes in the same folder as RemoteMaster.jar, and of course the RDF file goes in your RDF folder.
I also encourage you in RMIR to do a File\Set Directory\RDF folder to make sure it is pointed at the folder containing your RDFs and then do this again for the Image Folder, making sure it is pointed at where your images/maps are.
You can see a picture of the remote in the Device Editor Window, and looking at the Layout tab.
I don't seem to have a RemoteMaster.jar file.3FG wrote: Protocols.ini goes in the same folder as RemoteMaster.jar, and of course the RDF file goes in your RDF folder.
Done.I also encourage you in RMIR to do a File\Set Directory\RDF folder to make sure it is pointed at the folder containing your RDFs and then do this again for the Image Folder, making sure it is pointed at where your images/maps are.
Found it. The body shape and button layout in your latest upgrade file look correct, but the cosmetic appearance is very different and it says Comcast at the bottom instead of Xfinity.You can see a picture of the remote in the Device Editor Window, and looking at the Layout tab.
Jim,
Do you really mean that protocols.ini is C:\Program Files, and not in C:\Program Files\<whatever you call the RemoteMaster folder>? Protocols.ini has to be in the same folder as the RemoteMaster.jar, or if you installed the Jet version, in the same directory as the exe file.
Regarding the picture of the remote, the purpose is to allow you to graphically assign functions to buttons, so the positions and names of the buttons are the only thing that matters.
Finally, "no luck" doesn't help us troubleshoot the issue. Please tell us what does work and in detail what features of the Pioneer don't work.
Do you really mean that protocols.ini is C:\Program Files, and not in C:\Program Files\<whatever you call the RemoteMaster folder>? Protocols.ini has to be in the same folder as the RemoteMaster.jar, or if you installed the Jet version, in the same directory as the exe file.
Regarding the picture of the remote, the purpose is to allow you to graphically assign functions to buttons, so the positions and names of the buttons are the only thing that matters.
Finally, "no luck" doesn't help us troubleshoot the issue. Please tell us what does work and in detail what features of the Pioneer don't work.
As I mentioned earlier I do not have a RemoteMaster.jar file.
The full address of the directory containing Protocols.ini is C:\Program Files (x86)\RemoteMaster
I'm sorry, not understanding much about all this, I thought you would just move the existing coding to the new remote Like vickyg2003 did earlier in this Topic with the other new Comcast remote and didn't need to understand the functions.
The way it works is as follows:
The Cable selection works as normal.
The TV selection works as normal (I assume you can ignore this selection as I can program it using the ordinary programming codes).
The Aux selection operates a Toshiba D-R410KU Player/Recorder. But, this selection is combined with very limited functions of my Pioneer VSX-820 receiver.
These combined in functions switch the Pioneer HDMI channel as follows: The number buttons 1, 2, 3 select Aux, TV & Cable respectively when in AUX. (This may be done with some kind of macro from dv3, but here my understanding breaks down.)
The invisible dev3 selection is used to punch through the Volume up/down and the mute buttons to the other selections -- I think. But again having an invisible selection do this is something outside my understanding.
These last two functions ?may? be achieved by programing the invisible dev3 as the Pioneer and punching the sound through from there and making the 1, 2, & 3 buttons in AUX behave like shortcuts to the selection button changes in dev3.
Sorry if this isn't clear. Just ask and I'll try to explain.
Neither the audio punch through nor the Selection changing 1,2,3 buttons in AUX work. These are the only Pioneer functions I use on the remote and neither works.
Because it's messier to check the Toshiba DVD I haven't tried it at all. I stopped when the Pioneer functions didn't work and reported.
The full address of the directory containing Protocols.ini is C:\Program Files (x86)\RemoteMaster
I'm sorry, not understanding much about all this, I thought you would just move the existing coding to the new remote Like vickyg2003 did earlier in this Topic with the other new Comcast remote and didn't need to understand the functions.
The way it works is as follows:
The Cable selection works as normal.
The TV selection works as normal (I assume you can ignore this selection as I can program it using the ordinary programming codes).
The Aux selection operates a Toshiba D-R410KU Player/Recorder. But, this selection is combined with very limited functions of my Pioneer VSX-820 receiver.
These combined in functions switch the Pioneer HDMI channel as follows: The number buttons 1, 2, 3 select Aux, TV & Cable respectively when in AUX. (This may be done with some kind of macro from dv3, but here my understanding breaks down.)
The invisible dev3 selection is used to punch through the Volume up/down and the mute buttons to the other selections -- I think. But again having an invisible selection do this is something outside my understanding.
These last two functions ?may? be achieved by programing the invisible dev3 as the Pioneer and punching the sound through from there and making the 1, 2, & 3 buttons in AUX behave like shortcuts to the selection button changes in dev3.
Sorry if this isn't clear. Just ask and I'll try to explain.
Neither the audio punch through nor the Selection changing 1,2,3 buttons in AUX work. These are the only Pioneer functions I use on the remote and neither works.
Because it's messier to check the Toshiba DVD I haven't tried it at all. I stopped when the Pioneer functions didn't work and reported.
Last edited by i_am_jim on Thu May 23, 2013 10:15 pm, edited 1 time in total.
Here is the Topic with the previous modifications. In the first post I link to the previous Topics.
https://www.hifi-remote.com/forums/viewt ... highlight=
https://www.hifi-remote.com/forums/viewt ... highlight=
It looks like the RMIR file I uploaded doesn't have any buttons assigned for the Pioneer (dev3). Please go to the Layout or Buttons tab and assign at least Vol+/- and Mute.
When you press A, the remote should be switched to dev3 mode. Pressing most buttons (except ch+/- and the digits) should not light any of the LEDs, because there is no LED associated with dev3.
Can you check with a cell phone camera that Vol and mute does send an IR signal (and no LED lights)? The camera is sensitive to the IR light from the remote. That would tell us if the remote is trying to send a volume signal or if I have the punch through messed up.
Similarly, check if AUX 1, 2, or 3 does send an IR signal.
When you press A, the remote should be switched to dev3 mode. Pressing most buttons (except ch+/- and the digits) should not light any of the LEDs, because there is no LED associated with dev3.
Can you check with a cell phone camera that Vol and mute does send an IR signal (and no LED lights)? The camera is sensitive to the IR light from the remote. That would tell us if the remote is trying to send a volume signal or if I have the punch through messed up.
Similarly, check if AUX 1, 2, or 3 does send an IR signal.
Now that I have Assigned the Volume +/- and Mute they're working. Now how do I get the HDMI channel switching to work?
The red is the LED and reflections of it.
I first used the working remote to test what what I should expect to see. I don't see any light come from the IR transmitter. This picture shows what I see:3FG wrote:Can you check with a cell phone camera that Vol and mute does send an IR signal (and no LED lights)?
The red is the LED and reflections of it.
Last edited by i_am_jim on Fri May 24, 2013 8:33 am, edited 2 times in total.
You mention that the remote blinks rapidly in Cable mode. Does the 2556 remote control your cable box?
I'm not sure why your camera isn't seeing the IR flashes.
Regarding the input selectors, UEI remotes use 2 schemes for storing keymoves, and we don't know yet which the 2556 uses. I've edited the RDF file to use the other kind, and also uploaded a RMIR file prepared with the newer RDF. Please download both and try it.
I'm not sure why your camera isn't seeing the IR flashes.
Regarding the input selectors, UEI remotes use 2 schemes for storing keymoves, and we don't know yet which the 2556 uses. I've edited the RDF file to use the other kind, and also uploaded a RMIR file prepared with the newer RDF. Please download both and try it.