I am looking to build a 5 DSLR camera triggering system using arduinos over our network.
Currently we have physical trigger cables so that we can trigger each DLSR camera without delay. Even though all the cameras are on the network and running Nikon capture pro, there is a small delay from hitting the "shoot button" in the software, and the camera actually capturing the image. The physical trigger is instantaneous.
Basically I'd like to eliminate the need to run dedicated triggering cable to the cameras, as all I want to run is power, and a couple of ethernet to each camera. I want to have the ability to trigger, and intelligently change camera timings through an arduino or similar ip connectible device, sometimes we may have a single trigger, but slight delays to each shot, like, take one immediately, then two slightly later....
The triggering needs to be done physically, but may be done via sensor, so having an arduino with each camera will give us lots of options.
In the control room we want to be able to trigger any of the cameras with physical buttons, much like you'd see in industrial applications, something that can really take a beating. So from these buttons I would expect to run them all into an arduino, and then that arduino communicates with the others to trigger them.
Signal flow is like this
Button in control room > arduino > internet > arduino > Nikon external trigger cable > Nikon Camera.
Some cameras will trigger at the same time, others with delays.
So my key question is: What is the latency of one ip connected arduino, triggering another?