Ah CAMCORDER! Now I understand the reluctance to modify.
You may have said that before, I've been rather under the weather this
weekend, I may have missed it.
This is why the subject line said "revisited". I asked some questions
about this project in its initial incarnation a while ago. At that time
it was purely for camcorder use.
The original project - and it's going up on my web site soon, I promise-
was either:
a) to store telemetry data on the audio track of a camcorder,
synchronized with the image, or
b) to devise some reasonably solid method for putting sync marks onto
the videotape, so that a (flash or HDD-based) log could be
cross-referenced to the video stream.
The design restriction is: minimum possible reverse-engineering of the
cameras in use. It's acceptable to put a few patch wires into the
switches and buttons so they can be controlled remotely. It's NOT
acceptable to reverse-engineer any part of the analog or digital signal
paths inside the device and tap in anywhere, since there's no guarantee
that any particular tap-point will be available in a different model of
camera.
The circuit controls either a camcorder or a digital still camera (DSC)
over either async serial or SPI. For example, in powerdown mode it
disconnects the main power input to the camcorder. When the vehicle's
main controller requests it to start recording, it:
* applies power to the camcorder's battery terminals
* activates outputs that set the camera's mode switch to "record"
* "presses" the record button
* monitors the REC LED and signals back to the host if that LED goes out
(which signifies end-of-tape).
It can do similar tricks with a DSC. Someone pointed out to me that the
DSC control functions would be even more useful if there was a way of
recording the telemetry stream (since it's being sent out anyway, may as
well use it). Audio cassettes are by far the best and easiest way of
doing this. So that's why I'm looking at the problem. Seems like I have
it almost solved.