Difference between revisions of "Talk:Wishlist"
(another use case for camera as motor/servo controller) |
|||
| (One intermediate revision by one other user not shown) | |||
| Line 2: | Line 2: | ||
*Flash mode for rolling shutter | *Flash mode for rolling shutter | ||
*Lens distortion hardware correction | *Lens distortion hardware correction | ||
| − | |||
| − | |||
- | - | ||
| Line 10: | Line 8: | ||
Or should an flash occur immediately after the reset of sensor or, if an flash occurred in a random point in time, the sensor has to deliver 2 consecutive frames. | Or should an flash occur immediately after the reset of sensor or, if an flash occurred in a random point in time, the sensor has to deliver 2 consecutive frames. | ||
And knowing the time when an flash of joining them. | And knowing the time when an flash of joining them. | ||
| + | |||
| + | ''It is possible right now with [[10369]] using [[10369#J15_-_SYNC_.28external.29 | external optoisolated I/O]]. It can produce a pulse to trigger a flash or accept external trigger (in that case there should be sufficient delay between the pulse and a flash - at least equal to a full frame readout/erase time - 1/15sec for the full frame''--[[User:Andrey.filippov|Andrey.filippov]] 09:13, 28 October 2008 (CDT) | ||
*Lens distortion hardware correction | *Lens distortion hardware correction | ||
http://en.wikipedia.org/wiki/Image_distortion | http://en.wikipedia.org/wiki/Image_distortion | ||
| + | |||
| + | == camera as motor controller == | ||
| + | Why would you want the camera to be a motor/servo controller? | ||
Why would you want the camera to be a motor/servo controller? | Why would you want the camera to be a motor/servo controller? | ||
Why not? is easy. And cam can be funny base for robot. | Why not? is easy. And cam can be funny base for robot. | ||
| + | |||
| + | Because it seems the least silly of these 3 options: | ||
| + | * Run 2 Ethernet cables up a long pole, one connected to the camera, one connected to a pan-tilt-zoom motor/servo controller | ||
| + | * Run 1 Ethernet cable up a long pole, connected to a Ethernet hub, with 2 very short Ethernet cables connecting the hub to the camera and the PZT motor/servo controller. | ||
| + | * Run 1 Ethernet cable up a long pole, connected to the camera, and a short cable for the camera to drive the PZT motors. | ||
Latest revision as of 15:28, 14 April 2009
Interesting suggestions Kimstick! Could you please give us more details what you mean with :
- Flash mode for rolling shutter
- Lens distortion hardware correction
-
- Flash mode for rolling shutter
The flash should be synchronized with the image sensor. Or should an flash occur immediately after the reset of sensor or, if an flash occurred in a random point in time, the sensor has to deliver 2 consecutive frames. And knowing the time when an flash of joining them.
It is possible right now with 10369 using external optoisolated I/O. It can produce a pulse to trigger a flash or accept external trigger (in that case there should be sufficient delay between the pulse and a flash - at least equal to a full frame readout/erase time - 1/15sec for the full frame--Andrey.filippov 09:13, 28 October 2008 (CDT)
- Lens distortion hardware correction
http://en.wikipedia.org/wiki/Image_distortion
camera as motor controller
Why would you want the camera to be a motor/servo controller? Why would you want the camera to be a motor/servo controller?
Why not? is easy. And cam can be funny base for robot.
Because it seems the least silly of these 3 options:
- Run 2 Ethernet cables up a long pole, one connected to the camera, one connected to a pan-tilt-zoom motor/servo controller
- Run 1 Ethernet cable up a long pole, connected to a Ethernet hub, with 2 very short Ethernet cables connecting the hub to the camera and the PZT motor/servo controller.
- Run 1 Ethernet cable up a long pole, connected to the camera, and a short cable for the camera to drive the PZT motors.
