Pioneer MIX with more than 2 possible prefix commands?

Post by **vickyg2003** » Tue Oct 09, 2012 3:07 pm

After reviewing this thread, I'm not quite sure I have a handle on this.

There are 3 variants of 007E handled in protocols.ini

The last time I looked there were 5 variants of 007e.

Certain options are not being presented.

007e Pioneer Mix 4 fixed variables
007e:2 Pioneer DVD
007e:3 Pioneer Mix with 6 fixed variables
007e:4 Pionere Mix with 6 fixed variables -not available in rm
007e:5 Pioneer Mix with 6 fixed variables - not available in RM

If there is no known variant listed, the remote is getting the pioneer mix, that takes 4 fixed bytes. This changes if the protocols are reordered in protocols. ini.

If there is a variant of 3: it gets the MIX protocol that handles 6 fixed bytes.

Neither variant 4, nor 5 is being offered as an option. They should be offered if the protocol is built in. Of these 6 fixed byte variants, Variant 3 uses much smaller code. So its probably more desirable than variant 4 or 5.

If there is a variant of 4 or 5, right now only the less desirable pioneer 4fixed byte mix with is being offered.

I noticed eariler in this thread, that if you reorder the protocols in the ini file it will offer the 6fixed byte variabe. It seems to me, that when RMIR was being heavily tested, that some of the protocols in protocols.ini were rearranged to facilitate recognition when being downloaded.

So there should probably be a protocols ini version that offers the variant 4 and 5 option so no executor needs to be added. Variant 3 should be offered up before variant 4 or 5.

I also wonder what the implications of renaming these protocols are on existing upgrades.

-------------------------------------------------------
In addition KM 9.22 doesn't handle this correctly either. If you pick RCA- RCRP05b, and pick pioneer mix, it offeres you the 4fixed byte device version, with no protocol upgrade, even though a 6fixed byte version is built in. In addition the Pioneer 4x4 and 4x4x4 mixes offer you the 6 bytes, but neither offers you a protocol upgrade. I'm assuming these somehow represent variant 4 and variant 5 although I have no clue.

Post by **The Robman** » Tue Oct 09, 2012 7:45 pm

I don't believe there's any logic difference between variants 3, 4 and 5, so from a protocols.ini POV they should all be variant 3.

I would like it if someone could confirm that they're all the same though.

Post by **vickyg2003** » Wed Oct 10, 2012 8:11 am

I split off oldabe's conversation, because this thread is getting more technical.
oldabes conversation is here.
https://www.hifi-remote.com/forums/viewtopic.php?t=14298

mr_d_p_gumby · Post by **mr_d_p_gumby** » Fri Oct 12, 2012 12:52 pm

The Robman wrote:I don't believe there's any logic difference between variants 3, 4 and 5, so from a protocols.ini POV they should all be variant 3.

I would like it if someone could confirm that they're all the same though.

There are differences, though backward compatibilty with variant 3 is possible if you don't use the newer capabiltities.

In all 3 variants, bit 0 of the 2nd cmd byte determines if the command is 1 or 2 part.

In variant 3, bits 2 & 1 select the command for the 1st part.

Variant 4 adds the ability to select the device for 1-part commands, using bits 2 & 1 of the 2nd command byte.

Variant 5 adds the ability to select the device for the second part of the command; when bit 5 of the 2nd cmd byte is 1, bits 4 & 3 select the device.

My PB files for all five variants were posted in the files section back in 2009.

Post by **The Robman** » Fri Oct 12, 2012 2:25 pm

Do you know how protocols.ini should be updated to handle this, so that people with newer remotes don't get forced to add a protocol upgrade when they select the Pioneer Mix protocol?

mr_d_p_gumby · Post by **mr_d_p_gumby** » Fri Oct 12, 2012 3:01 pm

In KM, I give the user a choice of which to use based on requirements (4, 4X4, 4X4X4). I would imagine protocols.ini should do something similar, but I'm not familiar enough with the various command translators to know if a new one is needed, or if an exisitng one could be used. I would think that variants 4 & 5 could start off by replicating variant 3 (except for the pcode), albeit sacrificing the extra capabilities until the command translator issue is worked out.

3FG · Post by **3FG** » Fri Oct 12, 2012 4:30 pm

I started work on this last night, and I will do the protocols.ini stuff. I'll also add 006A variant 4.

3FG · Post by **3FG** » Tue Oct 16, 2012 11:16 pm

I have committed new revisions of PioneerMixTranslator and protocols.ini to SourceForge, so I believe these will be incorporated in the forthcoming 2.02 release. Users of newer remotes that have variant 4 or 5 of 007E built in will see an appropriate RM interface.

The new revision of protocols.ini also has support for variant 4 of 006A. The original variant is properly called Pioneer 3DEV, and the 4 variant of 006A implements Pioneer 4DEV. The official 006A:4 version appears to have identical properties to our (I assume) unofficial 01D0 version.

Post by **The Robman** » Wed Oct 17, 2012 7:16 am

I wrote our 4DEV executor, so yeah, it's unofficial. I need to take a look at the official version to see how closely they copied our version.