Alternate PID assignment?

Tbone03045 · Post by **Tbone03045** » Mon Dec 07, 2020 9:41 am

Hello,

Back into this after being away for about 15 years...

So what exactly is happening when you get the message, "Protocol ID conflicts with a built-in protocol. To use both this and the built-in protocol in device upgrades, this one needs to be given an Alternate PID."?

What is the procedure used to select and assign an Alternate PID?

I'm using both an AR Xsight Touch and AR Xsight Color, if it makes a difference. And they both seem to work fine even with this message coming up, and me not doing anything about it...

Thanks in advance,
Tbone

Post by **The Robman** » Mon Dec 07, 2020 10:09 am

Which upgrade file are you trying to load? I forget, does RMIR give you a box to enter an alternate PID? If so, try entering something like 01FF. If it doesn't, we'll need to fix it in the back-end.

Tbone03045 · Post by **Tbone03045** » Mon Dec 07, 2020 10:28 am

Hi Rob,

The upgrade started as a NEC 4DEV Combo (which did not have this issue), but I changed it to NEC 4DEV Yamaha Combo after adding some learned commands (Bass, Treble, Presets) that require YStyle inputs. The original protocol is 01 1A, and I added 01 FF to the "Alternate PID" window, and the same warning is still appearing.

The unit I'm controlling is a Yamaha R-S202 Receiver. Could not find any entries at all anywhere in the forum for this model...

An option is to go back to learning those commands again and just using them as learned commands, but there's no challenge in that!

Thanks again,
TBone

Post by **The Robman** » Mon Dec 07, 2020 11:31 am

Post a link to the exact RMIR file that you are using and the exact upgrade that you are trying to add, and I'll see if I can fix it.

Tbone03045 · Post by **Tbone03045** » Mon Dec 07, 2020 3:47 pm

I'm at work now so can't do much more on this until around midnight.

Hey, I don't wanna make you put a lot of effort into this for me, like I said, I can just revert back to using the learned signals, if it's too much hassle.

Thanks,
Tom

Post by **The Robman** » Mon Dec 07, 2020 6:50 pm

I think I have stumbled onto this problem before, so if it's a problem with our software (and I think it is), we should fix it.

Tbone03045 · Post by **Tbone03045** » Mon Dec 07, 2020 10:45 pm

Not sure how to link to the file, I posted it in the Diagnosis area with the title PID Conflict. Here's a copy of the address bar, will that work?

http://www.hifi-remote.com/forums/dload ... e_id=26183

Thanks again,
TBone

Tbone03045 · Post by **Tbone03045** » Mon Dec 07, 2020 11:03 pm

Just to reiterate, this setup DOES work (apparently, and so far...), so I'm not sure if it really even IS a problem? Just being anal, I guess. Let me know whatcha think.

And I just have to add, what you guys have done with all of this stuff over the years is AMAZING! Many many people out here are eternally thankful and appreciative of all of the work all of you experts have put into this whole JP1 effort. Blows my mind.

Thanks again,
TBone

Post by **The Robman** » Tue Dec 08, 2020 8:39 am

I've got your file and am trying to re-create the problem. When I click edit on the Yamaha device and change something, including wiping out the alt pid, when I save I'm not getting a conflict. What do I have to do to re-create it?

Tbone03045 · Post by **Tbone03045** » Tue Dec 08, 2020 8:52 am

Beats me? Was the warning there when you first opened the file? It still comes up for me...

I realize this is probably a stupid question, but - I am still using Windows 7, could that have anything to do with it?

Thx,
Tom

Post by **The Robman** » Tue Dec 08, 2020 10:39 am

Windows 7 shouldn't be an issue, more relevant is what version of RMIR you are using (get it from Help > About).

Tbone03045 · Post by **Tbone03045** » Tue Dec 08, 2020 11:00 am

I'm using RMIR v2.12.1.

I just tried entering 01 AD as an alternate PID (which I got from looking at the file pointed to at

http://www.hifi-remote.com/forums/dload ... e_id=25742

which RMIR did not like at all. So I removed it, and now the warning no longer exists? Problem fixed???

Time to head off to work............

Thx,
TBone