The PW standard operating platform would make perfect sense, but 'that small part of the code' which deals with all the input from Nikon cameras and output to Nikon speedlights and conversly all the input from Canon cameras and output to Canon speedlights seperately, are exactly that, they are completely seperate.
If a problem exists with TTL preflash on a Nikon D3 or D3s with a Nikon version TT1, an AC3 and a Nikon version TT5 with an SB900, no amount of checking Canon versions will help anywhere, apart from other Canon combinations.
I've no doubt there'll be a new firmware update addition to Nikon v3 to make it compatible with Richards equipment.. but that won't impact on any Canon usability at all as it's the Nikon translation that's at fault not the Canon one.
As with people it's all in the communication. If the message is garbled or imperfect then both systems would have the issue. Checking both systems can provide valuable info as to where to look for the problem. You'll agree that the software that controls the settings and manages the firmware is the same for both Nikon and Canon? What that should tell you is that there is an upper layer that works the same for both units.
But - let's just agree to have different opinions about how it works. I'll agree you have an opinion and likewise for me. I've not made any judgements on how useful your posts have been and I would appreciate likewise.
HappyCamp wrote:
So what was the work around? Is it the turning VR on and off?
Thanks!
HappyCamp,
Sorry taking so long to get back. The current problem I am having was gross over exposures with an AC3 in the Mini shooting in iTTL (Nikon). The preflash was not being read correctly by the camera. If I removed the AC3 from the Mini, the iTTL exposure was fine. The PW work around was to raise the FEC on the flash unit(s) to +3. Using the Mini and AC3 combination, the exposure is not impacted, but the preflash output is increased significantly. This is working for me now.
The VR issue is something that was going on several months back where you would get black frames if you turned VR on or off. I miss-spoke when I said the problem was still there. Sorry UK and PW.
BubbaJon wrote:
As with people it's all in the communication. If the message is garbled or imperfect then both systems would have the issue. Checking both systems can provide valuable info as to where to look for the problem. You'll agree that the software that controls the settings and manages the firmware is the same for both Nikon and Canon? What that should tell you is that there is an upper layer that works the same for both units.
But - let's just agree to have different opinions about how it works. I'll agree you have an opinion and likewise for me. I've not made any judgements on how useful your posts have been and I would appreciate likewise....Show more →
As much as I would like to leave this, this is exacly the issue. It has nothing to do with the PW hardware and it's 'upper level' but everything to do with the Canon and Nikon firmware differences.
I'm sure that along the way the upper levels get tweeked, but when the Nikon commands are not being understood, and those commands not being communicated correctly it's hardly surprising the communication doesn't work.
Ironically, the problem in Richards case is an AC3 which can't understand and transmit commands received from a TT1 to a TT5... (yet a TT1 - TT5 alone works) ALL within the PW system, so does that mean the AC3 is faulty and they all need recalling - or is the Nikon firmware faulty?
I shoot Canon and my system wouldn't fire with the AC3 mounted when turned on. I had to remove it, get it to fire, then put the AC3 back on. Sometimes it would work, sometimes not. It was fine before the firmware update.
I am having a problem with my AC3 and Pocket Wizard System after updating to rev 3.00 firmware for Nikon Mini and Flex. I am using a D3 and a D3s plus SB900 flash units. The problem occurs when the AC3 is installed on the Mini. The flash unit fires at max output, the flash pilot light blinks (under exposed) and the flash indicates the exposure is 3 stops down, when it is actually completely blown out. If I remove the AC3, the system works perfectly. Also, if I use an SU800 instead of the AC3, I get the same blown out image and the under exposure warning. This happens with any combination of flex and SB900. Even a flex on camera with the AC3 causes the problem. If I place the AC3 in Manual, the system works as expected. I have tried rear and normal sync with no change.
I have new batteries in everything and there does not appear to be a connection problem.
After much troubleshooting, I have learned the problem centers around the preflash. If I move the flash unit very close to the subject, (6 ft) everything works fine. If I move 10 ft away, changing nothing else.....blown image. If I zoom the flash head to 200mm, it works until I move back to 12 ft. then blown image. All of this is done in a dimly lit room with the camera set for 1/160, f5.6, and ISO 800. The ambient exposure is 4 stops down from that so it would be a 100% flash exposure. It would appear the AC3 or anything on the Mini hot shoe is changing the preflash output or timing in such a way as to cause the exposure system to over expose the image.
I have sent an email to the Beta Lab to see if it is possible to roll back the firmware. Has anyone else experienced any problems with Nikon, the AC3 and firmware rev 3?
I've been looking around on the web for anybody else mentioning the problems you reported with the AC3 after the firmware update, but funny enough there's not much buzz on this subject.
Since many of the reactions in this thread so far came from Canon shooters, I did a test myself to add some more info from a Nikon shooter.
As the results with a D3 were already found out by you, I used a D2X for my shots. Set up was 2 SB800's on TT5's in a white umbrella on a lightstand, camera as said a D2X with a 70-300VR (so I could take close up's and more or less have an identical composition and thus metering for the testshots) with a TT5 with and without a AC3
Ended up with similar results as you already reported.
With the SB800's set on Manual by the AC3 on a TT5 on the camera (as the PW manual dictates. the SB800 themselves were still in the 'normal' TTL setting as if used standard on a body) on the camera, exposure was consistent with the SB800's at varying distances (obviously I had to reduce power when the SB800's were closer to the subject)
With only the TT5 on the camera and shooting TTL, exposure with the SB800's was correct and consistent.
With the AC3 on A and shooting TTL, exposure was correct with the SB800's close by (tested them at appox 5 feet and at 8 feet). But with the SB800's at 18 feet, things got heavily overexposed as seen on the LCD screen, and confirmed by the histogram (and later checked on the computer).
I have a SU-800 lying around but as the results with the AC3 were in line with your findins I saw no need to check that too (testing equipment is not my favourite part of photography)
I must admit that for my intended type of shooting the issues mentioned are not a big thing as I rarely put my flash more then 8 feet from the subject, but when you want to lighten a big room and shoot the flashes in TTL I can see there's a big problem waiting to rear its ugly head
So I guess this is another firmware hickup and assume that as things worked with the previous version, PW will come with a fix/update shortly.
Thanks for checking.....the AC3 is not the only problem. You will get the same result with a SB900/ 800 or SU800 acting as a master.
I guess my big question is "What are the Beta Testers doing?" This is a basic operation of the entire system and no Beta Tester reported it?
Thanks for taking the time to test it,
Richard K.
Hi Richard
just received a mail from PW they've released a software update which : ' specifically address the preflash issue you mentioned. It's version 3.003 and you can install it by connecting a radio and clicking the "Check for Updates" button.'
Haven't had time to upload and check it, but their all in all speedy reaction confirms the good impression I have from PW already.
