As a long time compulsive tinkerer in many different areas, I've been following this thread with interest. One question I have in this matter of the apparent variation of speed at different positions in the frame: have you done any tests of repeatability at the same position? To me it seems likely that some varieties of old mechanical shutters, especially focal planes, thanks to both wear and dirt, could potentially vary a lot between actuations. It would be cool to be able to check two or three locations during a single pass (which I suspect is probably where your two sensors were headed). I suppose capturing the data from multiple sources might be more of a challenge.
I have had urges to get into the Arduino/Raspberry Pi stuff, but having once made a living playing with embedded systems, I'm afraid I'll disappear into my basement workshop and never be seen again.
Hi DW,
It is good to know others have been following the thread, please shout out & say hi.
Yes, I have taken multiple shutter readings at one location and it is surprising how inaccurate Zenits are

)
So I take multiple samples at each point & take an average.
I have also tried a more modern Canon T70 with a vertical multiple blade shutter & this gives far more consistent results, variation of only 0.1mS in any one place, but even this camera shows a difference in exposure from one side of the frame to the other, below are a couple of outputs as shown on the pc screen, which gives far more info than the LCD
-----laser at bottom of T70 shutter-------------------
Laser1 Start: 105821328
Laser1 Stop : 105825204
shutter Speed Microseconds : 3876
shutter Speed Milliseconds : 3.876
shutter Speed Seconds : 0.004
shutter Speed fraction : 1/258.00
shutter Speed fraction : 1/258
---------------------------------------------------------------
----laser at top of T70 shutter---------------------
Laser1 Start: 141819928
Laser1 Stop : 141824052
shutter Speed Microseconds : 4124
shutter Speed Milliseconds : 4.124
shutter Speed Seconds : 0.004
shutter Speed fraction : 1/242.48
shutter Speed fraction : 1/242
------------------------------------------------------------
Using two lasers was a good idea (and probably still is) as it halved the number of tests required and was able to calculate the travel time of each curtain. However, as I was getting wildly different results between first & second curtain, decided to use just one laser, in case timing errors were being introduced by the code.
Arduinos are very addictive

)
I purchased a kit to make a trigger timer, the kit was quite good, but analogue based, using 555 timers & pots to change the values. Whilst it worked fine, it took ages to set up each time, having to fine tune each dial.
So along comes Arduino and with just a Nano & LCD, was able to make a digital readout, which showed what the delays were, making setting up again a breeze. I did offer the idea & code to the manufacturer for free, but after initial communication, the offer was not taken up. Happy to supply details if anybody has this device & wants to add the digital display.
Next was to make my own timer-trigger device using an Arduino. This turned into a monster (did I say Arduino's are addictive?

)
It has inputs for sound, light, lasers, all breaking or making.
Not only does it fire the flash after a user set delay, it will also open the camera shutter if the shutter latency is lower than the delay time (warns you if it is not)
It can control three high current outputs, in my case solenoids, which open/close period can be controlled, multiple times in one exposure.
Water drop photos for example, rather than just having the blob coming back out of the water, having a second water drip to hit the first as it rises, gives the exploding crown effect.
Sorry, getting well off topic here
Second water drop coming down, hitting first (on its way up) creates the crown
Arduino digital readout added to an analogue camera timer product.