Originally posted by Roadboat24 The V6II with the X-TTL variant (PEN.A.001) would not trigger the V5 or V6.
Yes, I get the same result.
Originally posted by Roadboat24 As you say, multi-brand Cactus V6II firmware (I believe its V1.1.013 ) would, But as Mcgreni stated you lose some V6II functions.
One could say "lose", one could alternatively say "stops one from winning additional functionality that the V6II did not offer when it was introduced".
The point I'm trying to make is that there is a difference between inconsiderately breaking backward compatibility and not including older protocols in a brand new and separate branch of firmware variants.
If V6II firmwares had kept supporting the original V6II (multi-brand) functionality (with some refinements and additions) and had at one point simply dropped backward compatibility to the V5 and V6 then I think a word of caution would be in order. Personally, I'd say such a decision would be bad in terms of customer support and would demonstrate bad business sense.
The situation is different though, as the firmware variant in question is rather different in nature. It does not support cross-brand HSS anymore, but solely focuses on P-TTL and making some P-TTL functionality available. Apparently, the technical challenges involved made it impossible to still maintain backward compatibility to the V5/V6. I'd say it is a difficult choice as to when no longer supporting backward compatibility is appropriate. On the one hand, backward compatibility is very desirable. On the other hand, one does not want backward-compatibility to stifle future developments. In other words, personally, I'd say it is better to have the option of using the V6II as P-TTL triggers compared to not having been given that opportunity due to the fact that couldn't be realised while maintaining backward-compability.
Long story short, I think if Cactus hadn't made the X-TTL functionality available as a free firmware upgrade but had instead bundled it with a new hardware product (V7, or whatever) then people probably wouldn't take issue with the fact that products like the V5/V6 are no longer supported by the new products. At some point in time, it is no longer feasible to maintain backward compatibility. So all I'm saying is that one shouldn't hold it against Cactus that they didn't charge for new hardware when they made the X-TTL variant available.
To be clear, I'm not saying you are unduly criticising Cactus. I just wanted to express that I personally feel that the current situation -- while not being ideal -- is quite defensible.
Originally posted by Roadboat24 The V6II with the V1.1.013 variant would not fire the RF60X with the most recent firmware (A03 as I remember), I think It also needed the older firmware to function ( I did not test this), which I think loses some functionality.
Yes, unfortunately, the multi-brand vs X-TTL firmwares do not mix and match. You'd have to run a multi-brand variant on the RF60X as well. Again, you wouldn't "lose" functionality doing that, you just wouldn't be able to upgrade your RF60X to a P-TTL flash while at the same time maintaining full backward-compatibility.
FWIW, during the V6II X-TTL firmware beta testing, I suggested that any RF60X firmware should be made compatible with any other V6II firmware variant, because I don't think it is practical to keep re-flashing your firmware versions all the time. As it is, one is pretty much forced to make a decision for either multi-brand or X-TTL and then stick with that, but apparently Cactus found no easy way to implement my suggestion.
Originally posted by Roadboat24 I had thought (Incorrectly) the V6 firmware would bring the V6 trigger comparability up-to the V6II. My mistake.
Well, the V6 and V6II are compatibility, as long as one sticks to the multi-brand firmware variant.
The V6 cannot support HSS due to hardware limitations, but it does support PowerSync in combination with a V6II.
Potentially, some barriers could be removed in the future. It is for instance conceivable that the V6 may receive a firmware that makes it compatible even to the X-TTL firmware variants, but I wouldn't count on that. My expectation is that the multi-brand and X-TTL universes will be kept separate and that only the multi-brand versions will keep backward compatibility to the V5/V6.