JP1 Remotes

1. Device: Parasound 2100 new Classic Preamp
2. Type of device: 2 Ch analog pre amp / Misc Audio
3. Year: 2007
4. JP1/UEI Remote model: URC 8910
5. Do you have a JP1 cable? Yes
6. Still have original remote? Yes
7. Checked the file section? Yes
8. Checked Pronto file section (at R/C)? Yes
9. Partially working setup code? Yes
I have created a new device upgrade for a recently purchased Parasound 2100 New Classic PreAmp. see below...
10. Learning remote question? ISO codes not on remote - please see below

I have created a new device upgrade for a recently purchased Parasound 2100 New Classic PreAmp. The device file is located here: http://www.hifi-remote.com/forums/dload ... le_id=5155

All works fine for the original remote buttons, but I am in search of some additional codes (not on the remote) to complete the device file.

The 2100 manual lists all available IR codes as RS-232 ASCII/Hex Codes. I am not sure how to convert these listed values to EFC/OBC values. The codes are listed on Page 17 in the online manual here: http://parasound.com/pdfs/2100Manual.pdf

The chart shows these additional codes that are not on the factory remote.
- Power Toggle
- Mute On
- Mute Off
- Next Input
- Prev Input
- Tone Toggle

I'd like to find power toggle, but the rest would be nice as well.

I tried a few random EFCs via km-> IR, with no success.

Anyone familiar with the ASCII codes showing in the online manual and know how to convert these to JP1 EFC/OBC values.

TIA

Don't try random EFCs. Instead, look at the used OBCs on the Code List page. You will see the they are all in a tightly-bunched group of OBCs 62-76. I would start any Code Search in that area.

Capn Trips wrote:Don't try random EFCs. Instead, look at the used OBCs on the Code List page. You will see the they are all in a tightly-bunched group of OBCs 62-76. I would start any Code Search in that area.

Ok random was a poor choice of words. I did exactly what you suggest, except I was looking around the EFCs closer to the power codes of 22 & 26, looking for power toggle, no luck.

I'd rather just find a way to convert the RS232 ASCII/Hex codes given to EFC values, then there is no searching required. I was hoping someone here may understand the conversion.

I've been a regular on this forum for years, and have never seen anybody convert RS232 command codes into IR codes. AFAIK, there is no relationship between the two.

I have, on the other hand, seen (and personally done) code searches uncover many previously unidentified codes. Code searches don't take a heck of a lot of time if you're using JP1 (build an upgrade using about 40 codes, try them all, repeat), and in particular in a case when the OBCs are so clearly bunched, you could have already done the obvious ones. (For that matter, you could have already tested EVERY one from 000 through 256).

I again suggest using OBCs rather than EFCs to anchor your search, but you can do what you think is most efficient.

Or continue waiting for someone to come up with the codes an alternative way.

Yeah I'll do the search. I just didn't know if someone already had a nifty utility to convert Ascii or understood the relationship.

rmassey wrote:Yeah I'll do the search. I just didn't know if someone already had a nifty utility to convert Ascii or understood the relationship.

Typically there is no relationship. The existence of an RS232 command for a specific function does not indicate there is an IR command for that function. If there happens to be an IR command for that function, the values in the RS232 command still tell you nothing about the values in the IR command.

It seems to make no sense, when designing a system that understands commands through two different mediums, to design two unrelated sets of commands. It would be easier for the customer if it were one set of commands encoded for the two mediums. That should also be easier for the programmers writing the firmware of the device itself.

Yet almost every company that make a consumer device understanding both RS232 and IR, makes the illogical choice to have two unrelated systems.

You can't have a "nifty utility" that converts or understands the relationship, when there is no actual relationship to understand or on which to base a conversion.

OK, good to know. I knew I'd learn something from this post.

I have tried several OBC codes above and below the used range of 62-76 with no success.

Not knowing RS232 vs IR codes, I had assumed that there would be equivalent IR codes for all given RS232 codes. They might be there, but I have not discovered them yet. They are certainly not located near the existing IR OBC codes. I will keep at it.