More E-TTL info from Bill

As mentioned in a previous post, Bill Grundmann has been documenting his investigation into Canons E-TTL protocol.  Bill has just released a PDF summarising what he has found so far.

I’ve yet to go over it in detail, but for those looking at doing some E-TTL investigation of their own this document is a must.

http://billgrundmann.files.wordpress.com/2009/03/ettl_grundmann.pdf

Tests

Here’s are some initial non scientific test results of the prototype.

Sidenote: I had some fun testing these outside at night, everytime a car drove past I triggered the strobe, instant brake lights, hehe (The use of speed cameras are notorious here in Western Australia).

The Unit, both the master and slave are identical, personality is determined at powerup by pressing the trigger button if you want a master.
IMG_5569

Test Rig of slave mounted on a strobe.
IMG_5560

Running at 12500bps, camera syncs to 1/125 ~60m
12500

running at 9600bps, camera syncs to 1/100 ~120m
9600

Protocol

Protocol:

Full Detail can be found here on the wiki – http://wiki.everythingrobotics.com/index.php?title=Draft_Proposal

The trigger packet transmitted is 7 bytes long.  Preamble(3 bytes), Sync(2 bytes), trigger command (1 byte) and CRC byte.

The Preamble is used by the the RF module to tune the Receiver.

The Sync word is used by the RF modules receiver circuit to know when a valid transmission is occuring and not just interference.  This SYNC word can be used as a future PAN address, i.e. all your units are set to the same unique SYNC pattern then your units operating in the same area as other trigger units on the same frequency will not be triggered by your units and visa-versa.

If an invalid packet is detected by the CRC then the packet is dropped and the strobe will not fire.  This is where some future work can be done with forward Error Correction, so a corrupt packet could be rebuilt and still used by the slave, i.e. the strobe could still fire even if some corruption is detected.

Currently the slaves so not communicate back to the master in anyway.

Back – Firmware Triggr Home

Firmware

Firmware Details:

At the moment it’s pretty basic, but works!  Source is available via SVN (see download page)

The mode is set at powerup by pressing the manual trigger button. If pressed then mode is set to Master, default powerup is in slave mode (i.e.. do nothing). Master mode is identified by a single flash of the LED, Slave is a double flash. This way any of the units can be master or a slave.

Master mode sends a remote trigger command to the slaves when the manual trigger button is pressed, or a trigger signal is detected on the Trigger Input. The LED is light briefly when triggered.

Slaves will only trigger the local strobe if trigger test button is pressed, or a remote trigger command is received via RF. The status LED will light briefly when triggered by either of these means.

The Master will send out a keep-alive broadcast once every 5 seconds. The units LED (master and slaves) will blink briefly to indicated successful RF Link.

Back-Prototype Triggr Home Next – Protocol Details

StrobIt Triggr

Introduction

20/03/09 *UPDATE * This project now has a new home and is actively being developed on Google code project hosting http://code.google.com/p/strobit/

IMPORTANT    This page is no longer being being maintained please go to the new project page.

Welcome to the Strobit Triggr Project, an open source hackable wireless trigger used in photography lighting by using low cost strobe units triggered remotely via RF. This was started while trying to find a cost effective and reliable solution to the commercial alternatives out there. At one end of the market is the Ebay or Cactus Trigger, which is low cost but rather unreliable. At the other end of the market there is the industry standard, Pocket Wizards, very reliable, but very expensive (i.e. way out of my price range).

What I wanted to do was to create an open platform that anyone can easily build for a low cost and then be expand upon by the community. The pair of prototypes I’ve built were a proof of concept that I can get a camera to trigger a strobe unit reliably at a low cost. From early tests it appears that I’ve succeeded in my goal, but further testing is required.

triggr0103

Project Status :

– Prototype successfully working in single master/slave configuration !

– (20/03/2009) Project now has a home at Google Code – http://code.google.com/p/strobit/

Still Todo:

  • Specifications
  • Hardware Design
    • Schematics
    • PCB
  • Software Design
    • Wireless
    • User Interface
    • Protocol
  • Hardware Prototype

License

The strobit hardware design is covered by The TAPR Open Hardware License. Please see http://www.tapr.org/ohl.html for further details.

Schematics:

Strobit Triggr Block Diagram Strobit Triggr Topology StrobIt Triggr Schematic

Prototype Details

Firmware Description

Protocol Description

Downloads – Files associated with the project

Tests – Tests done so Far

In the Wild – Version of this trigger made by others

I’m toying with the idea of putting together a low cost kit for the enthusiast. i.e. PCB, pre-programmed PIC, etc. So we could all benefit with a bulk order of the components. If your interested please email me using the contact form the top menu or use the mailing list signup on the right to give me an indication of numbers interested. Once I finaliaze the design and get some idea of numbers I’ll get a better idea of price. At the moment it will only be available in kit form due to FCC and other Licensing regulations.

Future Improvements:

  • Higher Sync Speed.
  • Frequency Hopping.
  • Forward Error Correction.
  • Power management.
  • UI to change settings, Channel etc.
  • Save settings in Flash memory.