"Conflicts with built-in protocol" message for dev

chileboy · Post by **chileboy** » Mon Aug 31, 2020 12:18 pm

I'm seeing this on my Laserdisc device, and no tabs are accessible:

It's a Pioneer Elite CLD-97 and I used the upgrade file PioneerLaserDiscs.txt. The upgrade functions work just fine on the player from my Xsight.

Yes, I still use a laserdisc player, don't judge me!

Post by **The Robman** » Mon Aug 31, 2020 1:57 pm

Just FYI, whenever you make a post about a specific file, please include a link to the file to save folks having to search for it, and it confirm that we're looking at the right file.

i believe this is the file that you are trying to use:
http://www.hifi-remote.com/forums/dload ... ile_id=315

There's something funny going on with the Pioneer MIX protocol, not sure why it's not loading for this remote, but regardless, in this case the solution is to use a different Pioneer LD file, such as the following, which should load without issue.

http://www.hifi-remote.com/forums/dload ... le_id=4817

chileboy · Post by **chileboy** » Mon Aug 31, 2020 2:14 pm

The Robman wrote:Just FYI, whenever you make a post about a specific file, please include a link to the file to save folks having to search for it, and it confirm that we're looking at the right file.

i believe this is the file that you are trying to use:
http://www.hifi-remote.com/forums/dload ... ile_id=315

My apologies (I seem to be saying that a lot) - I will be sure to include links going forward...but yes, that's the file.

The Robman wrote: There's something funny going on with the Pioneer MIX protocol, not sure why it's not loading for this remote, but regardless, in this case the solution is to use a different Pioneer LD file, such as the following, which should load without issue.

http://www.hifi-remote.com/forums/dload ... le_id=4817

OK, I will give that a go...thank you, as always.

mdavej · Post by **mdavej** » Mon Aug 31, 2020 3:24 pm

Rob, if you look at the Xsight RDF, the 007E protocol is actually 007E:4, so not the exact match RM is looking for. Not sure what's different about that version.

Post by **The Robman** » Mon Aug 31, 2020 3:38 pm

mdavej wrote:Rob, if you look at the Xsight RDF, the 007E protocol is actually 007E:4, so not the exact match RM is looking for. Not sure what's different about that version.

I did see that, and I expected it to sync up with this...

[Pioneer MIX]
PID=00 7E
VariantName=4
DevParms=Device 0=165, devOBC1=91,devOBC2=94,devOBC3=89,devOBC4=92, DevP2=175
DeviceTranslator=Translator(lsb,comp,0,8,0) Translator(lsb,comp,1,8,8) Translator(lsb,comp,2,8,16) \
Translator(lsb,comp,3,8,24) Translator(lsb,comp,4,8,32) Translator(lsb,comp,5,8,40)
FixedData=9A 7A FA 00 00 0A
DefaultCmd=00 00
CmdIndex=0
CmdParms=Prefix Device:none|dev1,Prefix Command:none|Cmd1|Cmd2|Cmd3|Cmd4,Device:dev0|dev1|dev2|dev3|dev5,OBC=0
CmdTranslator=Translator(lsb,comp,3) PioneerMixTranslator(4)
CmdParmInit=PickInitializer(0,,0) PickInitializer(1,,1,2,3,4) PickInitializer(2,0,1,2,3,5)
ImportCmdTranslator=Translator(0,2,14) Translator(lsb,comp,1,8,0)
Notes=For single-style signals, you may select any of the 4 device numbers entered in Device 0, devOBC1, devOBC2, or devOBC3 \n\n\
For double-style signals, the prefix device number must be entered in Device 0. Prefix OBCs may be selected from devOBC1 through devOBC4\n\
The main device number must be entered in DevP2
Code.S3C80=40 84 62 8B 14 A5 54 08 08 01 12 00 F0 01 12 03 02 32 B4 10 B0 08 39 00 02 08 0A C0 C0 56 C0 0B 7B 0B 87 10 03 19 03 46 29 01 8D 01 46 87 10 04 19 04 56 29 EF 0C 03 A6 0D 02 EB 02 0C 05 09 0D B0 01 E6 10 01 F6 FF 56 FB 06 F6 FF 50 7B F1 AF E6 01 05 E6 10 06 F6 01 46 8D 01 0A
Code.HCS08=20 17 21 43 62 A5 54 08 08 01 11 01 04 01 11 03 16 32 C8 10 AF 08 4D 00 02 8C B6 67 44 A4 03 97 00 67 09 E6 60 B7 60 10 A3 CC FF 5F E6 61 B7 61 19 A3 B6 B2 A1 02 27 03 6E 01 B2 3F AC 6E 01 A9 AD E7 6E 05 AC 6E 06 A9 AD DF CD FF 92 25 EC 81