Thanks Tesla500
Mechanical rotation events have an inherent inertial and frictional delay after the event "start" command signal is executed. The time or frame at which the motion command input signal is executed must be known Without a known event start time, there is no basis upon which to determine acceleration/deceleration behavior or capacity to optimize the behavior. Camera tools exist to delete frames after event is complete.
2 Potential workarounds come to mind:
1. Preferred work around: I purchased the switch cable w/push button S/W.
Hack the switch leads; connect to computer using opto-coupler FET circuit instructed with
computer that issues the rotational event motion command signal. My assumption is, since the
push button is a continuity interrupt to start recording, electronic switch closure can replace
the button. the external opto-coupled trigger circuit would have to be developed about
required electronic parameters & specs. Aspects such as impedance, trigger signal duration, 0-
6.6V or 5V TTL assumed to be supported?, amperage limits, etc.
Is KronTech willing to support this effort providing the BNC port electronic parameters to assist
in development of an opto-coupled triggering circuit?
This support a digitally integrated test environment.
2. Less preferred method - place a visual signal (LED) in the FOV with the LED actuating when
motion command signal is executed - The manual push button camera triggering would be
followed by motion command signal execution. this can be a manual actuation of both the
push button and motion execution or trigger delay technique which has not been conceived on
my part at this time.
Another question - how is data stored and retrieved from camera?
Please advise if Krontech can support info-sharing as detailed in #1 above.
Best Regards
pstest