- This topic has 7 replies, 1 voice, and was last updated 2 days, 7 hours ago by .
2019-08-17 at 14:01 #3199DariusGuest
Anybody tried to trigger just one transmitter? My setup is 1 transmitter connected to Arduino output, one receiver plugged into the camera’s sync port. Then on cameras hotshoe I have another transmitter which is set to controll all my flashes in separate group. Looks like it’s working perfect and you could save some code and outputs. Ease to attache additional speedlites, just set then on that group.
All flashes are always triggered by camera.
I’m using Godox. And funny thing, that I’m using Canons versions on cables, and only need Sony version on hotshoe.2019-08-17 at 14:47 #3200MartynGuest
Try using the flash separate to the camera. I have a radio trigger attached to FT1 which triggers 4 flashes guns.
The normal method is to use a dark environment (does not need to be pitch black):
– activate camera (either bulb or longer shutter speed)
– make drops
– trigger flash(es)
– let shutter close
In this way it is the flashes that take the photo.
There is normally too much lag when triggering the camera. You also do not normally get a fast shutter speed. With my Canon, I have found the delay from trigger to shutter is not always the same.2019-08-17 at 20:43 #3202DariusGuest
One more question – did you ever use 9 drops ? How it looks like ?
I cannot imagine that 🙂2019-08-18 at 03:20 #3203MartynGuest
The only time I have used 9 drops was when I was trying to get 3 separate collisions/sequences in a line at the same time. I never got it to work though.2019-08-18 at 22:10 #3207DariusGuest
Martyn, I’m trying to make my own dropper and then found your project. Very nice.
I’m thinking about simple code, simple interface. Any drop is released one by one in sequence and I thought that delay() is enough for that..
What is the point of counting millis ?2019-08-19 at 07:26 #3210MartynKeymaster
When starting all the devices I checked used the same technique; drop; delay;drop;delay and I used this method for an an early version of the dropController. I as progressed I found it difficult to get the drops I wanted due to how the Arduino handles delays. Switching to start and size times means you can have multiply drops active at the same time and it gives more control over the drops. For example, should you want, with the dropController you can have 9 drops all active at the same time. This is not possible using delay().
The Arduino delay() command blocks the code meaning the Arduino can not do anything else while it is waiting. If you want to know more about this look in to “Arduino delay”, “Arduino blink without delay” and “Arduino doing more than one thing at the same time”.2019-10-18 at 13:27 #3613DariusGuest
Hi Martin again.
Question about flash outputs.
All flashes could get signal from only one output, where transmitter could be connected.
We could savesome space on pcb, and some code 🙂
Are there any benefits to have separate outputs?2019-10-19 at 02:33 #3614MartynKeymaster
For normal drop photos I use one flash trigger connected to a wireless remote. The multiply flash triggers came about from my experiments with multiple flash times used on one collision. Prior to adding the extra triggers I used a separate flash delay circuit.
FT3 may be developed to be a general purpose control, I like the idea of using it to control a light but have not got round to implementing it yet.