My experience is that the Metz 52 AF-1 works perfectly on the K5 hotshoe, but does not communicate correctly with the camera in slave P-TTL mode. It overexposes by many stops! However, it works absolutely perfectly on my son's K30.
In order to get it to expose properly in slave P-TTL mode with the flash quite close to the subject, I found I had to:
1. Correct the 52 AF-1 by two stops (-2 EV)
2. Correct the camera's built-in flash by -2EV in the flash settings; and
3. Set the camera sensitivity correction to -2 EV.
All three of these are usually necessary; I set them up as one of the programmable User modes. With the flash much further away, these corrections were too extreme, and could be dialled back somewhat.
I wasn't sure if this was just my K5 behaving this way. As I said, it works fine with the K30. However, today I tried it with another K5 in a camera repair shop, and the result was the same; extreme overexposure.
So, it seems the 52 AF-1 and K5 don't communicate properly. I hope this is something that will be corrected with a Metz firmware update at some stage (there has been no new firmware release for the 52 AF-1 since it came on the market). Is anyone at Metz listening?
By the way, does anyone understand why (according to the diagram in the back of the manual) the 52 AF-1's wireless TTL sensor is on the BACK of the unit, just under the touchscreen?
Last edited by Paul the Sunman; 07-25-2013 at 09:40 PM.
Reason: Correction
Similar Threads 
