Nissin Di700 (Nikon) on top of V6 makes flash display blink
well the title sort of says it... I recently got a couple of V6 to connect my Nissin Di700 to my D750. I am trying to debug some misfires but that is a topic for V6 Problems... I'm aware of the D750 hotshoe situation..
Here's the question: In order to rule out the V6 <-> Di700 connection, is it normal or expected behaviour for the Nissin flash to alternate and blink every couple of seconds? Is there anything I should be aware of regarding this combo? V6 firmware is up to date, flash is on TTL, flash is switched on before the V6 is set to RX...
It's normal as the Di700 requires a signal every so often to confirm that there is indeed an established connection with a camera, otherwise it would go into power saving mode. A manual flash trigger like the V6 won't be doing this on its own so we had to build that into the flash profile.
why are you concluding that the Di700 / V6 combo doesn't work?
I understood Antonio as saying that they built in regular communication with the flash into the flash profile so that the Di700 does not go to sleep.
Have you tried to fire the Di700 at different power levels using a remote V6 transmitter and the latter's power level dial and test button?
I then focused on the Di700 and the blinking pattern since I subjectively got the impression, that
- The new hotshoe of the D750 might play a role in all this, but not necessarily in this particular case or setup (since I testfired from the V6s test button and still got misfires on the Di700 / V6)
- Di700 <=> V6 communication works as designed according to Antonio
- Doublechecked channels, groups, tried different power levels, range levels on the V6s
It's a problem rooted in the Di700 and at the moment this cannot be fixed by firmware update.
FYI the flash requires a signal every 0.5s so the V6 needs to sends a signal at that interval. However the signal from the V6 is extremely short and your chances of hitting it with a trigger signal is very low and you should only occassionally
We look forward to fixing this problem in our next model.
Thanks again for your understanding.