TTL Passthrough (Pentax X-TTL)
I have not been able to get TTL Passthrough working : The flash will not fire, however the flash zoom works in response to lens zooming.
TTL Passthrough worked for me previously using the Multi-brand firmware on the same V6II unit and the exact same equipment.
This is the equipment : V6II with PEN.A.001 (mounted on the camera in Tx mode) / Pentax K7 camera / Pentax AF-540FGZII (mounted on the V6II) / Pentax D-FA type autofocus lens
The V6II is set with TTL Passthrough activated (long press on the Menu button, TTL symbol shows on the left side of display) ..... this is confirmed by checking the menu item within the Function Menu ... "On".
All connections between camera, V6II and flash are tight and secure . I have been using this equipment for nearly a year now with no communication problems, so I don't believe it is anything like that. The flash head zooms when I zoom the lens, and this is consistent and works correctly. however the flash never fires. It is charged and the ready light illuminated. This flash works normally when mounted directly on the camera, plus its Test button produces a full flash pop.
I wonder if this problem exists for others, or is it perhaps restricted to the K7 camera ?
Comments
On the contrary, you mentioned that the V6II mounted flash still keeps adjusting its zoom setting despite TTL pass-through being inactive. I wouldn't expect that to happen and it may point to a wider issue.
I think it furthermore helps to share the settings you used (which you reported elsewhere):
===
V6II Menu “Camera & Flash Setup” :
Camera System, Pentax .......
Flash System, Pentax .......
Custom Setting, Off ......
Flash Profile, Pentax AF540F2.
===
These provide support for the presence of a bug as opposed to incorrect usage.
McGregNi found out more about the issue he reported. He got the on-camera flash to work, but had to take some hurdles.
I have already asked R&D to consolidate all the bugs reported so far and release a new firmware version.
But as you know, they are pretty full on their hands right now, with updating X-TTL firmware to "A" versions for Fujifilm, Sigma and Sony, simultaneously working on Canon X-TTL, and last but not least, RQ250 firmware.
Hopefully we can pull it off soon(er) on releasing PEN.A.002.
Thank you!
Brand Manager
I can't speak for others but personally I don't think releasing PEN.A.002 is super urgent, given your other commitments.
Obviously there will be many eager to see Canon support completed, but personally I'm most eager to see the RQ250 come to life!
Will there be two firmware variants for the RQ250, i.e., multi-brand & X-TTL? I guess an X-TTL compatible firmware variant would be very popular, but I guess there will also be many who prefer running the multi-brand firmware on their V6II units due to the gear that it supports.
FYI most of previously reported bug have already been updated to an internal firmware but we just need to run it through out tests. This is the most time consuming phase. So in any case we would like to release a newer Pentax version as soon as we can.
Canon X-TTL, it's difficult. It's taking longer than we anticipated... hope we can get through this.
RQ250, probably just one firmware, like the RF60X.
We can't wait to roll it out too!
Brand Manager
I hope the same can be done for the RQ250 because otherwise one would be forced to use the X-TTL variant for the V6II. For Pentax users that would mean that they couldn't mix the RQ250 with speedlights from other flash systems like Canon, Nikon, etc.
There may be further consequences from being forced to use the X-TTL variant for the V6II, e.g., regarding TTL pass-through behaviour, etc.
I am glad you bring this up because what you described is true for the current situation.
But very soon, this will be on the plate.
V6 II / V6 IIs: X-TTL firmware versions:
V6 II: Multi-brand HSS firmware versions: (Date available: after FUJ, SIG and SON are released)
V6: New "A" firmware version: (Date available: 2018/2019.)
RF60 firmware version:
- A06 (replacing 205)
RF60X firmware version:Hopefully this will make it much more straight forward when people update their firmware between various Cactus devcies.
The existing "1" firmware versions (latest only) will still be kept for sometime (until further notice) for any possible future compatibility issues and / or working with other Cactus devices running on firmware versions.
Thanks!
Brand Manager
thanks a lot for the clarification.
I have a couple of questions:
Why use "V62.A.001" to replace "V1.1.013"?
Previously, it was easy to distinguish the multi-brand variants from the X-TTL variants due to the letter "A" being used only in the X-TTL variants.
With your future plan, there is an unnecessary similarity between "V62.A.001" and "PEN.A.001", i.e., the "A". Does the "A" have a particular meaning? Is it ever expected to change?
I'd say "PEN.X.001" would be nice for the X-TTL version ("X" for "X-TTL) and "V62.M.013" or "M.013" would be nice for the multi-brand variant ("M" for multi-brand).
I would continue the numbering from the "V1.1." scheme, because otherwise someone may think that "V1.1.13" is newer than "V62._.001".
I guess you probably don't want to change "PEN.A.001" to "PEN.X.001", but "V62.M.001" or "M.001" still strikes me as better than "V62.A.001".
BTW, regarding consistency, I think either all firmware versions should lead with the device name (as in "V62") or none. I think "none" would be sufficient, as the Firmware Updater won't offer a firmware that doesn't fit the connected device anyhow.
I think whatever you do, it should be possible to refer to all X-TTL variants easily and all multi-brand versions easily. Currently one can say "choose a firmware with an 'A' in it" and thus refer to any "X-TTL" firmware variant. Currently, one can also say "choose a 'V1. ...' firmware" and thus refer to any multi-brand version.
I don't see how distinguishing between the two major branches (X-TTL vs multi-brand) would still be possible based on the version name.
Currently A05 and 104 cannot be used interchangeably. Only 104 works with V1.1.013. Will A06 work with both V1.1.013 and all "_.A.___" (X-TTL) variants? If so, that would be great!
I guess you are planning to still support the multi-brand variant in the future, correct? However, to make the V6II multi-brand variant work with the RF60X, the latter needs a firmware that is compatible with the former.
So if A06 is both "multi-brand" and "X-TTL" compatible then all is fine. But if it is just "multi-brand" compatible then it would be most confusing (as A05 is only X-TTL compatible). If A06 is only "X-TTL" compatible, then there would be no multi-brand support for the RF60X anymore (within the updated firmware naming scheme).
"A" and "1" are actually the denotation of the wireless protocol. Nothing fancy, there isn't a special meaning to them.
In short, the Multi-brand HSS firmware will be "upgraded" to the "A" wireless protocol from the current "1". Everything will operate in "A" in the future, including RF60, RF60X and RQ250 firmware versions. Meaning both X-TTL firmware and Multi-brand HSS firmware can simultaneously trigger other V6 II as well as Cactus flashes and monolight when they all are also running "A" firmware versions. A Multi-brand HSS TX will also trigger a X-TTL RX, but of course limited to manual power and zoom controls.
Wireless protocol "1" will be phased out eventually - but it will be retained for people who actively mix in a V5 and LV5 in their setup together with V6 II / V6 IIs.
For the future Cactus V7, we do not want to drag down its performance when working with the V6, V6 II, RF60, RF60X, RQ25 so we have to drop the support of V5 and LV5. Those who needs this backward compatibility will have to use V6 II and all other Cactus devices running on "1" firmware.
Hope this helps!
Brand Manager
While this means leaving the V5 / LV5 behind, using all of the properly group aware products (V6, V6II, RF60(X), RQ250) with each other will be very simple with no more firmware re-flashing required when changing between multi-brand and X-TTL.
I see, thanks for the clarification.One consolation factor for the LV5 and V5 is that one can still use them in "conjunction" with the more modern triggers, if one has a V5 as a receiver to trigger a camera when instructed so by an LV5. It will no longer be possible to directly trigger flashes with the LV5 but triggering the camera is probably the more common application anyhow.
I think that is a much better solution than the current divide between multi-brand and X-TTL.Thanks a lot for the clarifications. Very helpful indeed.
I can't imagine having people to keep on re-flashing their Cactus devices when they go between Multi-brand HSS and X-TTL firmware versions. So,thankfully this is only a transitional phase and we apologize for all the inconveniences caused during this time.
Speaking of which, Fujifilm, Sigma and Sony "A" X-TTL versions will be available real soon. Then we will have the Canon X-TTL version and the Multi-brand HSS "A" version finish it off.
The very last one would be the original V6 (MK1). Considering what we already have on our plate, I suspect this would come late 2018 / early 2019.
Thanks!
Brand Manager
- TTL is working fine while the flash is in bounce/rotated/tilted positions (this said, I have not assessed over- or underexposure, and can only attest that TTL works satisfactorily and responds to exposure compensation).
- There is no firing in the straight front position
- If the head of the flash is moved from a bounced/rotated/tilted position to the front one, the flash stops firing. And it takes lifting/tilting/rotating the flash's head and resetting (switching off/on) the V6II to get it firing back again.
The test bench:
Pentax K-1
AF-360FGZII
V6II with the PEN.A.001 firmware.
Flash profiles for AF-306FGZII and Pentax Auto
NB. AF 201 FG, by the way, refused to fire on-camera at all so far...
Hope a solution will come with the firmware update... Looking forward to updating to PEN.A.002. ))
.
. The Petax AF201FG, if you don't mind sending your unit to us for investigation that would be great as it is very difficult to find one in Hong Kong, if at all possible.
Scroll to bottom on this page to see our mailing address.
By the way, PEN.A.002 was released earlier this month. Give that a try.
Thanks!
Brand Manager
Thanks for the tip on udating to PEN.A.002 - I had received my V6II units a day or so before this version was released, and somehow have never checked for updates since then...
Try as I might with PEN.A002, the news is not good, I am afraid - AF-360FGZII does NOT fire on the K-1 and V6II on-camera at all - in ANY position of its head.
V6II shows 'On- camera TTL on', 'HSS normal sync" and the specific flash profile but no light comes out... The flash zoom works.
Got back to PEN.A.001, for the time being, which sports stable TTL and HSS paththrough in all positions except the front one with this setup.
The fash in the straight front position is rarely used on-camera, and the on-camera fill flash in a group with off-camera flashes could even be used tilted down with a diffuser. When the front position is indispensable, the flash can always be put on the camera directly. So not a big deal, just curious where the bug may be...
Thanks for the tip on udating to PEN.A.002 - I had received my V6II units a day or so before this version was released, and somehow have never checked for updates since then...
Try as I might with PEN.A002, the news is not good, I am afraid - AF-360FGZII does NOT fire on the K-1 and V6II on-camera at all - in ANY position of its head.
V6II shows 'On- camera TTL on', 'HSS normal sync" and the specific flash profile but no light comes out... The flash zoom works.
Got back to PEN.A.001, for the time being, which sports stable TTL and HSS paththrough in all positions except the front one with this setup.
The fash in the straight front position is rarely used on-camera, and the on-camera fill flash in a group with off-camera flashes could even be used tilted down with a diffuser. When the front position is indispensable, the flash can always be put on the camera directly. So not a big deal. Just curious where the bug may be...
Or you manually selected the flash system and flash profile on the TX (Transmitter) unit?
If you are using auto, did you switch on the AF360FGZII before you switch on the V6 II to TX mode?
Thanks!
Brand Manager
Here's an example:
Before attempting any of the above, first run a factory reset on all your V6 II transceivers so you can be sure you starting off fresh.
For the camera side, if you are running PEN.A.xxx firmware and you don't have any on-camera flash mounted, there's no auto-detect per se because PEN.A.xxx only works with Pentax cameras. So in case you are using an old film camera that only has a center hot shoe contact pin, you will have to manually select .
If you do have an on-camera flash, say your Pentax AF360FGZ the V6 II TX will auto-detect it and apply an AUTO flash profile and you get TTL and HSS too for the on-camera flash. If you have a non-Pentax flash you will only get manual power control and HSS.
Hope this helps... Thanks!
Brand Manager
Thanks for the tips and video, though you may have meant this one (for pass-through TTL)?
Anyway, having followed your recommendations, with PEN.A.002 the AF-360FFZ II still would not fire on the K-1 through the V6II in any position of its head (while the zoom does work).
Again with PEN.A.001 it fires OK in on-camera TTL and HSS in all positions except the front straight one.
Cheers.
Same thing is happening with PEN.A.003 update. The AF-360FFZII on the V6ii on the K-1 does NOT fire anywhere, anyhow...
Again - back to PEN.A.001 which is OK when the front straight position is avoided...
Would love to find out why before investing further in the system...
Any ideas anyone?
Is my setup any different than yours?
Thank you.
Brand Manager
Thanks for replying! The video is exhaustive enough except it features the K-3II, not the K-1 which is my case.)
Maybe it is a peculiarity of my copy of the K-1, but with very much the same setup as yours (except the abovementioned K-3II), I cannot make the AF-360FGZII fire on PEN.A.003 in the on-camera position with TTL-through being ON. In any positions of its head. Despite repeated factory resets, checks all-over - nothing doing.
Cheers.
PS Just for the statistics sake maybe - the behaviour of PEN.A.003 (on-camera with TTL-through) with another two speedlightes:
SIGMA 610 DG SUPER - works quite nicely in TTL in the straight position of its head, and overexposes in any other position - which is, unfortunately, typical and normal for this flash even when mounted directly onto the camera. And even HSS seems to work.
PENTAX AF-201 - does NOT fire in any way on the V6II. Which was the case with PEN.A.001 already as far as I remember. It is probably a feature of the flash - not compatible for TTL-through.
On an RX V6II it fires and gives correct exposures and is more controllable than direclty on-camera (which has been already discussed in another thread).
PPS Getting more and more puzzled - if you could test AF-360FGZII exactly on the K-1 some day...
Totally forgot we have a K-1
Work as expected!
Maybe get your V6 II checked? Only if you have a second V6 II transceiver you can check against that. But having PEN.A.001 work may just prove the hot shoe connection isn't stable, and it worked sometimes?
Thanks!
Brand Manager