Programming 363 - Revision history

Vsouthwick: /* Sensor board control (10347) */

2008-10-30T20:21:57Z

Sensor board control (10347)

← Older revision		Revision as of 20:21, 30 October 2008
Line 2:		Line 2:
	This article reflects the current state of the software to operate Elphel model 363 camera, including synchronizing of multiple cameras. Not all the software is in the final state, but - anyway.		This article reflects the current state of the software to operate Elphel model 363 camera, including synchronizing of multiple cameras. Not all the software is in the final state, but - anyway.
	===Sensor board control (10347)===		===Sensor board control (10347)===
	CCD sensor front end in the model 363 camera consists of a sandwich of the two PCBs - [[10347]] - FPGA-based timing/interface module and [[10342]] - analog sensor front end. In addition to the 10342 board, 10347 controls optional mechanical shutters, it has interface connectors ~~fro~~ some 35-mm motorized lenses, opto-isloated I/O for synchronization and general purpose 5VDC output that can be used to turn on fan or drive other circuitry.		CCD sensor front end in the model 363 camera consists of a sandwich of the two PCBs - [[10347]] - FPGA-based timing/interface module and [[10342]] - analog sensor front end. In addition to the 10342 board, 10347 controls optional mechanical shutters, it has interface connectors for some 35-mm motorized lenses, opto-isloated I/O for synchronization and general purpose 5VDC output that can be used to turn on fan or drive other circuitry.

	This board is controlled from the processor board ([10353]) through a 2-wire serial interface, there is [http://elphel.cvs.sourceforge.net/elphel/elphel353-7.1/apps/ccd/init347.php?view=markup init347.php] (can be reached as <nowiki>http://<camera_ip>:81/init347.php</nowiki>) that sets initial values to the sensor registers (commented in the code), including main and mechanical shutter sequencers. This script is called automatically during camera initialization, it can be used as a sample for custom PHP applications to control the acquisition parameters, for manual changing parameters I would recommend copying it (or modified version) to RAM-disk based TMPFS (ftp to /var/html directory in the camera) - it will be availble as <nowiki>http://<camera_ip>:81/var/init347.php</nowiki> (or you may rename it as you wish, preserving .php extention, of course)		This board is controlled from the processor board ([10353]) through a 2-wire serial interface, there is [http://elphel.cvs.sourceforge.net/elphel/elphel353-7.1/apps/ccd/init347.php?view=markup init347.php] (can be reached as <nowiki>http://<camera_ip>:81/init347.php</nowiki>) that sets initial values to the sensor registers (commented in the code), including main and mechanical shutter sequencers. This script is called automatically during camera initialization, it can be used as a sample for custom PHP applications to control the acquisition parameters, for manual changing parameters I would recommend copying it (or modified version) to RAM-disk based TMPFS (ftp to /var/html directory in the camera) - it will be availble as <nowiki>http://<camera_ip>:81/var/init347.php</nowiki> (or you may rename it as you wish, preserving .php extention, of course)
Line 9:		Line 9:

	Current version of init347.php looks for the mechanical shutter sequencer program (0x200-0x27f for odd/all exposures, 0x280-0x2ff - for even ones) and if it is empty - programs default sequence (will not change existent sequence). Mechanical shutter sequencer operates independently of the main one, it only starts at the moment defined by the main sequencer. There is a separate program [http://elphel.cvs.sourceforge.net/elphel/elphel353-7.1/apps/ccd/mshutter.php?view=markup mshutter.php] that allows to edit the sequence(s) in a human-readable/writable form - the init347.php contains just codes for the [http://elphel.cvs.sourceforge.net/elphel/elphel353-7.1/fpga/x347/shutter_seq.v?view=markup shutter_seq.v] - each word include the 8-bit output code for the shutter control board (10368) and duration that code should stay on the output.		Current version of init347.php looks for the mechanical shutter sequencer program (0x200-0x27f for odd/all exposures, 0x280-0x2ff - for even ones) and if it is empty - programs default sequence (will not change existent sequence). Mechanical shutter sequencer operates independently of the main one, it only starts at the moment defined by the main sequencer. There is a separate program [http://elphel.cvs.sourceforge.net/elphel/elphel353-7.1/apps/ccd/mshutter.php?view=markup mshutter.php] that allows to edit the sequence(s) in a human-readable/writable form - the init347.php contains just codes for the [http://elphel.cvs.sourceforge.net/elphel/elphel353-7.1/fpga/x347/shutter_seq.v?view=markup shutter_seq.v] - each word include the 8-bit output code for the shutter control board (10368) and duration that code should stay on the output.

	=== Programming the CPU board [[10353]] to receive/compress images ===		=== Programming the CPU board [[10353]] to receive/compress images ===
	This part of the code is not redesigned yet to support CCD imagers, it was intended for the CMOS sensors originally. So currently you may just use the [[ccam.cgi]] interface to acquire an image (the frame dimensions should match those specified for the sensor in init347.php or equivalents), some parameters currently have no effect (like "e=" - exposure time) - it will be fixed in the future, others are needed (JPEG compression quality, image size, bit width, color type (monochrome/color/jp4), gamma, color saturation. The following url should open the image and initialize [[10353]] board FPGA to acquire/compress images and place them into [[Circbuf\|circbuf]]:		This part of the code is not redesigned yet to support CCD imagers, it was intended for the CMOS sensors originally. So currently you may just use the [[ccam.cgi]] interface to acquire an image (the frame dimensions should match those specified for the sensor in init347.php or equivalents), some parameters currently have no effect (like "e=" - exposure time) - it will be fixed in the future, others are needed (JPEG compression quality, image size, bit width, color type (monochrome/color/jp4), gamma, color saturation. The following url should open the image and initialize [[10353]] board FPGA to acquire/compress images and place them into [[Circbuf\|circbuf]]:

Andrey.filippov: /* Combining everything together */

2007-10-11T09:57:27Z

Combining everything together

@@ Line 44: / Line 44: @@
 #* ''<nowiki>wget "http://<camera2_ip>:81/admin-bin/ccam.cgi?opt=*vhc&ww=4008&wh=2676&bit=8&iq=95&byr=0&gam=99&rscale=1&bscale=1&e=1" -O /dev/null</nowiki>''
 #*  ...
 #* ''<nowiki>wget "http://<cameraN_ip>:81/admin-bin/ccam.cgi?opt=*vhc&ww=4008&wh=2676&bit=8&iq=95&byr=0&gam=99&rscale=1&bscale=1&e=1" -O /dev/null</nowiki>''
 #Start image acquisition processes on the host to repetitively read images, one per each camera. It can be something like
 #* ''<nowiki>wget "http://<camera1_ip>:8081/torp/wait/img/next/save" -O camera1_$(NUM).jp4</nowiki>''
@@ Line 50: / Line 60: @@
 #*  ...
 #* ''<nowiki>wget "http://<cameraN_ip>:8081/torp/wait/img/next/save" -O cameraN_$(NUM).jp4</nowiki>''
+#Loop: Start a process on each camera to detect end of image acquisition. Optionally it is possible to watch just one camera if the settings are the same (possibly adding some uncertainty time that is one CCD cleaning cycle period of the sequencer):

Andrey.filippov: /* Combining everything together */

2007-10-11T09:35:28Z

Combining everything together

← Older revision		Revision as of 09:35, 11 October 2007
Line 40:		Line 40:
	#Modify shutter sequence with '''<nowiki>http://<camera_ip>:81/mshutter.php</nowiki>''', if needed. Updated sequence can be embedded in the init347.php that is automatically executed each time camera starts up		#Modify shutter sequence with '''<nowiki>http://<camera_ip>:81/mshutter.php</nowiki>''', if needed. Updated sequence can be embedded in the init347.php that is automatically executed each time camera starts up
	#Update camera settings with custom script, based on init347.php. Do not use constants for the main sequencer addresses as they may change at any time - read table at the end of sequencer program memory		#Update camera settings with custom script, based on init347.php. Do not use constants for the main sequencer addresses as they may change at any time - read table at the end of sequencer program memory
	#Acquire one image from each camera, discard result: ''<nowiki>wget "http://<camera1_ip>:81/admin-bin/ccam.cgi?opt=vhc&ww=4008&wh=2676&bit=8&iq=95&byr=0&gam=99&rscale=1&bscale=1&e=1" -O /dev/null</nowiki>'', ''<nowiki>wget "http://<camera2_ip>:81/admin-bin/ccam.cgi?opt=vhc&ww=4008&wh=2676&bit=8&iq=95&byr=0&gam=99&rscale=1&bscale=1&e=1" -O /dev/null</nowiki>'' ~~and so on for each camera~~		#Acquire one image from each camera, discard result:
	#Start image acquisition processes on the host to repetitively read images, one per each camera. It can be something like ''<nowiki>wget "http://<camera1_ip>:8081/torp/wait/img/next/save" -O camera1_$(NUM).jp4</nowiki>'', ''<nowiki>wget "http://<camera2_ip>:8081/torp/wait/img/next/save" -O camera2_$(NUM).jp4</nowiki>'' ~~and so on~~		#* ''<nowiki>wget "http://<camera1_ip>:81/admin-bin/ccam.cgi?opt=*vhc&ww=4008&wh=2676&bit=8&iq=95&byr=0&gam=99&rscale=1&bscale=1&e=1" -O /dev/null</nowiki>'',
			#* ''<nowiki>wget "http://<camera2_ip>:81/admin-bin/ccam.cgi?opt=*vhc&ww=4008&wh=2676&bit=8&iq=95&byr=0&gam=99&rscale=1&bscale=1&e=1" -O /dev/null</nowiki>''
			#* ...
			#* ''<nowiki>wget "http://<cameraN_ip>:81/admin-bin/ccam.cgi?opt=*vhc&ww=4008&wh=2676&bit=8&iq=95&byr=0&gam=99&rscale=1&bscale=1&e=1" -O /dev/null</nowiki>''
			#Start image acquisition processes on the host to repetitively read images, one per each camera. It can be something like
			#* ''<nowiki>wget "http://<camera1_ip>:8081/torp/wait/img/next/save" -O camera1_$(NUM).jp4</nowiki>''
			#* ''<nowiki>wget "http://<camera2_ip>:8081/torp/wait/img/next/save" -O camera2_$(NUM).jp4</nowiki>''
			#* ...
			#* ''<nowiki>wget "http://<cameraN_ip>:8081/torp/wait/img/next/save" -O cameraN_$(NUM).jp4</nowiki>''
	#		#

Andrey.filippov at 09:32, 11 October 2007

2007-10-11T09:32:31Z

← Older revision		Revision as of 09:32, 11 October 2007
Line 38:		Line 38:

	Here is a sample algorithm to run simultaneous acquisition on several camera modules, one of them being the master one (the one that has its fan output connected to all trigger inputs (including its own).		Here is a sample algorithm to run simultaneous acquisition on several camera modules, one of them being the master one (the one that has its fan output connected to all trigger inputs (including its own).
			#Modify shutter sequence with '''<nowiki>http://<camera_ip>:81/mshutter.php</nowiki>''', if needed. Updated sequence can be embedded in the init347.php that is automatically executed each time camera starts up
			#Update camera settings with custom script, based on init347.php. Do not use constants for the main sequencer addresses as they may change at any time - read table at the end of sequencer program memory
			#Acquire one image from each camera, discard result: ''<nowiki>wget "http://<camera1_ip>:81/admin-bin/ccam.cgi?opt=vhc&ww=4008&wh=2676&bit=8&iq=95&byr=0&gam=99&rscale=1&bscale=1&e=1" -O /dev/null</nowiki>'', ''<nowiki>wget "http://<camera2_ip>:81/admin-bin/ccam.cgi?opt=vhc&ww=4008&wh=2676&bit=8&iq=95&byr=0&gam=99&rscale=1&bscale=1&e=1" -O /dev/null</nowiki>'' and so on for each camera
			#Start image acquisition processes on the host to repetitively read images, one per each camera. It can be something like ''<nowiki>wget "http://<camera1_ip>:8081/torp/wait/img/next/save" -O camera1_$(NUM).jp4</nowiki>'', ''<nowiki>wget "http://<camera2_ip>:8081/torp/wait/img/next/save" -O camera2_$(NUM).jp4</nowiki>'' and so on
			#

Andrey.filippov at 09:14, 11 October 2007

2007-10-11T09:14:23Z

← Older revision		Revision as of 09:14, 11 October 2007
Line 33:		Line 33:
	*'''<nowiki>http://<camera_ip>:81/trig.php?cmd=disarm</nowiki>''' - after this command camera will ignore incoming signals on external trigger input		*'''<nowiki>http://<camera_ip>:81/trig.php?cmd=disarm</nowiki>''' - after this command camera will ignore incoming signals on external trigger input
	*'''<nowiki>http://<camera_ip>:81/trig.php?cmd=single</nowiki>''' - arm camera for one external trigger only. It will auto disarm after processing a single input trigger pulse		*'''<nowiki>http://<camera_ip>:81/trig.php?cmd=single</nowiki>''' - arm camera for one external trigger only. It will auto disarm after processing a single input trigger pulse
	*'''<nowiki>http://<camera_ip>:81/trig.php?cmd=fireall</nowiki>''' - generate external trigger out pulse on a "fan" output. If several cameras have their trigger inputs connected to this output (pins 2 connected directly, pin 1 on has inline 360 Ohm resistor at each input branch) _AND_ each of them is armed _AND_ each of them is programmed (ccam.cgi) _AND_ each of them is in constant compression mode (compressor.php) then that command is all what is needed to trigger all ~~teh~~ cameras in parallel (required individual delays can be implemented in teh sequencer code).		*'''<nowiki>http://<camera_ip>:81/trig.php?cmd=fireall</nowiki>''' - generate external trigger out pulse on a "fan" output. If several cameras have their trigger inputs connected to this output (pins 2 connected directly, pin 1 on has inline 360 Ohm resistor at each input branch) _AND_ each of them is armed _AND_ each of them is programmed (ccam.cgi) _AND_ each of them is in constant compression mode (compressor.php) then that command is all what is needed to trigger all the cameras in parallel (required individual delays can be implemented in teh sequencer code).

			=== Combining everything together ===

			Here is a sample algorithm to run simultaneous acquisition on several camera modules, one of them being the master one (the one that has its fan output connected to all trigger inputs (including its own).

Andrey.filippov: /* [http://elphel.cvs.sourceforge.net/elphel/elphel353-7.1/apps/ccd/trig.php?view=markup trig.php] - sensor board triggering */

2007-10-11T09:10:29Z

[http://elphel.cvs.sourceforge.net/elphel/elphel353-7.1/apps/ccd/trig.php?view=markup trig.php] - sensor board triggering

← Older revision		Revision as of 09:10, 11 October 2007
Line 29:		Line 29:
	*generating output signal (on the "fan" connector) that can be used to trigger other (and this too) cameras.		*generating output signal (on the "fan" connector) that can be used to trigger other (and this too) cameras.
	So here are the commands:		So here are the commands:
	*<nowiki>~~'''~~http://<camera_ip>:81/trig.php?cmd=immed</nowiki>''' - software triggering of the camera (there is a >1 second delay for the first image after long timeout - the timeout time is controlled by init347.php, it can be set to "forever on".		*'''<nowiki>http://<camera_ip>:81/trig.php?cmd=immed</nowiki>''' - software triggering of the camera (there is a >1 second delay for the first image after long timeout - the timeout time is controlled by init347.php, it can be set to "forever on".
	*<nowiki>~~'''~~http://<camera_ip>:81/trig.php?cmd=arm</nowiki>''' - Prepare camera to be triggered through an external input. One such command is enough for any number of trigger pulses - each will trigger a new image acquisition (if they are far enough to allow for the whole frame to be transferred)		*'''<nowiki>http://<camera_ip>:81/trig.php?cmd=arm</nowiki>''' - Prepare camera to be triggered through an external input. One such command is enough for any number of trigger pulses - each will trigger a new image acquisition (if they are far enough to allow for the whole frame to be transferred)
	*<nowiki>~~'''~~http://<camera_ip>:81/trig.php?cmd=disarm~~'''~~</nowiki> - after this command camera will ignore incoming signals on external trigger input		*'''<nowiki>http://<camera_ip>:81/trig.php?cmd=disarm</nowiki>''' - after this command camera will ignore incoming signals on external trigger input
	*<nowiki>~~'''~~http://<camera_ip>:81/trig.php?cmd=single~~'''~~</nowiki> - arm camera for one external trigger only. It will auto disarm after processing a single input trigger pulse		*'''<nowiki>http://<camera_ip>:81/trig.php?cmd=single</nowiki>''' - arm camera for one external trigger only. It will auto disarm after processing a single input trigger pulse
	*<nowiki>~~'''~~http://<camera_ip>:81/trig.php?cmd=fireall~~'''~~</nowiki> - generate external trigger out pulse on a "fan" output. If several cameras have their trigger inputs connected to this output (pins 2 connected directly, pin 1 on has inline 360 Ohm resistor at each input branch) _AND_ each of them is armed _AND_ each of them is programmed (ccam.cgi) _AND_ each of them is in constant compression mode (compressor.php) then that command is all what is needed to trigger all teh cameras in parallel (required individual delays can be implemented in teh sequencer code).		*'''<nowiki>http://<camera_ip>:81/trig.php?cmd=fireall</nowiki>''' - generate external trigger out pulse on a "fan" output. If several cameras have their trigger inputs connected to this output (pins 2 connected directly, pin 1 on has inline 360 Ohm resistor at each input branch) _AND_ each of them is armed _AND_ each of them is programmed (ccam.cgi) _AND_ each of them is in constant compression mode (compressor.php) then that command is all what is needed to trigger all teh cameras in parallel (required individual delays can be implemented in teh sequencer code).

Andrey.filippov: /* [http://elphel.cvs.sourceforge.net/elphel/elphel353-7.1/apps/ccd/trig.php?view=markup trig.php] - sensor board triggering */

2007-10-11T09:09:34Z

[http://elphel.cvs.sourceforge.net/elphel/elphel353-7.1/apps/ccd/trig.php?view=markup trig.php] - sensor board triggering

← Older revision		Revision as of 09:09, 11 October 2007
Line 29:		Line 29:
	*generating output signal (on the "fan" connector) that can be used to trigger other (and this too) cameras.		*generating output signal (on the "fan" connector) that can be used to trigger other (and this too) cameras.
	So here are the commands:		So here are the commands:
	*<nowiki>http://<camera_ip>:81/trig.php?cmd=immed</nowiki> - software triggering of the camera (there is a >1 second delay for the first image after long timeout - the timeout time is controlled by init347.php, it can be set to "forever on".		*<nowiki>'''http://<camera_ip>:81/trig.php?cmd=immed</nowiki>''' - software triggering of the camera (there is a >1 second delay for the first image after long timeout - the timeout time is controlled by init347.php, it can be set to "forever on".
	*<nowiki>http://<camera_ip>:81/trig.php?cmd=arm</nowiki> - Prepare camera to be triggered through an external input. One such command is enough for any number of trigger pulses - each will trigger a new image acquisition (if they are far enough to allow for the whole frame to be transferred)		*<nowiki>'''http://<camera_ip>:81/trig.php?cmd=arm</nowiki>''' - Prepare camera to be triggered through an external input. One such command is enough for any number of trigger pulses - each will trigger a new image acquisition (if they are far enough to allow for the whole frame to be transferred)
	*<nowiki>http://<camera_ip>:81/trig.php?cmd=disarm</nowiki> - after this command camera will ignore incoming signals on external trigger input		*<nowiki>'''http://<camera_ip>:81/trig.php?cmd=disarm'''</nowiki> - after this command camera will ignore incoming signals on external trigger input
	*<nowiki>http://<camera_ip>:81/trig.php?cmd=single</nowiki> - arm camera for one external trigger only. It will auto disarm after processing a single input trigger pulse		*<nowiki>'''http://<camera_ip>:81/trig.php?cmd=single'''</nowiki> - arm camera for one external trigger only. It will auto disarm after processing a single input trigger pulse
	*<nowiki>http://<camera_ip>:81/trig.php?cmd=fireall</nowiki> - generate external trigger out pulse on a "fan" output. If several cameras have their trigger inputs connected to this output (pins 2 connected directly, pin 1 on has inline 360 Ohm resistor at each input branch) _AND_ each of them is armed _AND_ each of them is programmed (ccam.cgi) _AND_ each of them is in constant compression mode (compressor.php) then that command is all what is needed to trigger all teh cameras in parallel (required individual delays can be implemented in teh sequencer code).		*<nowiki>'''http://<camera_ip>:81/trig.php?cmd=fireall'''</nowiki> - generate external trigger out pulse on a "fan" output. If several cameras have their trigger inputs connected to this output (pins 2 connected directly, pin 1 on has inline 360 Ohm resistor at each input branch) _AND_ each of them is armed _AND_ each of them is programmed (ccam.cgi) _AND_ each of them is in constant compression mode (compressor.php) then that command is all what is needed to trigger all teh cameras in parallel (required individual delays can be implemented in teh sequencer code).

Andrey.filippov at 09:08, 11 October 2007

2007-10-11T09:08:42Z

@@ Line 14: / Line 14: @@
 === Acquiring images and transferring them to the host ===
 After the FPGA is programmed to process the incoming sensor data you do not need to use ccam.cgi - only if any of the parameters above need to be changed, Later we'll develop new software to control acquisition process - most of the functionality can already be implemented in PHP, but several IOCTL-s (not PHP-friendly) are still required.
-Now the process of transferring images is separate from the image acquisition to the camera memory (a 19MB circular buffer [[Circbuf|circbuf]]). The acquired data can be asynchronously sent out as either individual JPEG images through [[Imgsrv|imgsrv server]] or as RTP/RTSP MJPEG-ecoded stream (not sure if it still works with that large images, maybe a few fixes are needed)
+Now the process of transferring images is separate from the image acquisition to the camera memory (a 19MB circular buffer [[Circbuf|circbuf]]). The acquired data can be asynchronously sent out as either individual JPEG images through [[Imgsrv|imgsrv server]] or as RTP/RTSP MJPEG-ecoded stream (not sure if it still works with that large images, maybe a few fixes are needed). Imgsrv server allows images/image metadata transferring, waiting for a new image to appear in the buffer, manipulating the frame read pointer. A sequence of commands can be sent in a single http request through url line (commands are separated by slashes, a list of commands is available if you just open the imgsrv URL <nowiki>http://<camera_ip>:8081</nowiki> without parameters.

Andrey.filippov at 08:26, 11 October 2007

2007-10-11T08:26:19Z

← Older revision		Revision as of 08:26, 11 October 2007
Line 12:		Line 12:
	This part of the code is not redesigned yet to support CCD imagers, it was intended for the CMOS sensors originally. So currently you may just use the [[ccam.cgi]] interface to acquire an image (the frame dimensions should match those specified for the sensor in init347.php or equivalents), some parameters currently have no effect (like "e=" - exposure time) - it will be fixed in the future, others are needed (JPEG compression quality, image size, bit width, color type (monochrome/color/jp4), gamma, color saturation. The following url should open the image and initialize [[10353]] board FPGA to acquire/compress images and place them into [[Circbuf\|circbuf]]:		This part of the code is not redesigned yet to support CCD imagers, it was intended for the CMOS sensors originally. So currently you may just use the [[ccam.cgi]] interface to acquire an image (the frame dimensions should match those specified for the sensor in init347.php or equivalents), some parameters currently have no effect (like "e=" - exposure time) - it will be fixed in the future, others are needed (JPEG compression quality, image size, bit width, color type (monochrome/color/jp4), gamma, color saturation. The following url should open the image and initialize [[10353]] board FPGA to acquire/compress images and place them into [[Circbuf\|circbuf]]:
	<nowiki>http://<camera_ip>:81/admin-bin/ccam.cgi?opt=*vhc&ww=4008&wh=2676&bit=8&iq=95&byr=0&gam=99&rscale=1&bscale=1&e=1</nowiki>		<nowiki>http://<camera_ip>:81/admin-bin/ccam.cgi?opt=*vhc&ww=4008&wh=2676&bit=8&iq=95&byr=0&gam=99&rscale=1&bscale=1&e=1</nowiki>
			=== Acquiring images and transferring them to the host ===
			After the FPGA is programmed to process the incoming sensor data you do not need to use ccam.cgi - only if any of the parameters above need to be changed, Later we'll develop new software to control acquisition process - most of the functionality can already be implemented in PHP, but several IOCTL-s (not PHP-friendly) are still required.
			Now the process of transferring images is separate from the image acquisition to the camera memory (a 19MB circular buffer [[Circbuf\|circbuf]]). The acquired data can be asynchronously sent out as either individual JPEG images through [[Imgsrv\|imgsrv server]] or as RTP/RTSP MJPEG-ecoded stream (not sure if it still works with that large images, maybe a few fixes are needed)

Andrey.filippov at 08:16, 11 October 2007

2007-10-11T08:16:31Z

← Older revision		Revision as of 08:16, 11 October 2007
Line 1:		Line 1:
	== Programming Model 363 Cameras/camera modules ==		== Programming Model 363 Cameras/camera modules ==
	This article reflects the current state of the software to operate Elphel model 363 camera, including synchronizing of multiple ~~camera~~. Not all the software is in the final state, but - anyway.		This article reflects the current state of the software to operate Elphel model 363 camera, including synchronizing of multiple cameras. Not all the software is in the final state, but - anyway.
	===Sensor board control (10347)===		===Sensor board control (10347)===
	CCD sensor front end in the model 363 camera consists of a sandwich of the two PCBs - [[10347]] - FPGA-based timing/interface module and [[10342]] - analog sensor front end. In addition to the 10342 board, 10347 controls optional mechanical shutters, it has interface connectors fro some 35-mm motorized lenses, opto-isloated I/O for synchronization and general purpose 5VDC output that can be used to turn on fan or drive other circuitry.		CCD sensor front end in the model 363 camera consists of a sandwich of the two PCBs - [[10347]] - FPGA-based timing/interface module and [[10342]] - analog sensor front end. In addition to the 10342 board, 10347 controls optional mechanical shutters, it has interface connectors fro some 35-mm motorized lenses, opto-isloated I/O for synchronization and general purpose 5VDC output that can be used to turn on fan or drive other circuitry.
Line 8:		Line 8:
	Process of acquiring images from the CCD image sensor is controlled by the sequencer with the program (manually assembled) in the register address space of 0x100..0x1ff (initialized by init347.php) ,the Verilog code of the sequencer that interprets this code is in the [http://elphel.cvs.sourceforge.net/elphel/elphel353-7.1/fpga/x347/seq_cpu.v?view=markup seq_cpu.v]. Tricky part is that some loop count values (including exposure time) are embedded in the code and the absolute addresses inevitably change when the sequencer code is modified. These addresses are needed for the other scripts to change variable parameters (i.e. exposure), so we use the top sequencer addresses as a table of externally needed addresses, 0x1ff holding program address of exposure count, 0x1fe - delay between the start of additional mechanical shutter sequencer and the start of exposure. More entries may be added in the future (i.e. delay between exposure and readout start to give time for mechanical shutter to close and overall trigger delay)		Process of acquiring images from the CCD image sensor is controlled by the sequencer with the program (manually assembled) in the register address space of 0x100..0x1ff (initialized by init347.php) ,the Verilog code of the sequencer that interprets this code is in the [http://elphel.cvs.sourceforge.net/elphel/elphel353-7.1/fpga/x347/seq_cpu.v?view=markup seq_cpu.v]. Tricky part is that some loop count values (including exposure time) are embedded in the code and the absolute addresses inevitably change when the sequencer code is modified. These addresses are needed for the other scripts to change variable parameters (i.e. exposure), so we use the top sequencer addresses as a table of externally needed addresses, 0x1ff holding program address of exposure count, 0x1fe - delay between the start of additional mechanical shutter sequencer and the start of exposure. More entries may be added in the future (i.e. delay between exposure and readout start to give time for mechanical shutter to close and overall trigger delay)

	Current version of init347.php looks for the mechanical shutter sequencer program (0x200-0x27f for odd/all exposures, 0x280-0x2ff - for even ones) and if it is empty - programs default sequence (will not change existent sequence). Mechanical shutter sequencer operates independently of the main one, it only starts at the moment defined by the main sequencer. There is a separate program [http://elphel.cvs.sourceforge.net/elphel/elphel353-7.1/apps/ccd/mshutter.php?view=markup mshutter.php] that allows to edit the sequence(s) in a human-readable form - the init347.php contains just codes for the [http://elphel.cvs.sourceforge.net/elphel/elphel353-7.1/fpga/x347/shutter_seq.v?view=markup shutter_seq.v] - each word include the 8-bit output code for the shutter control board (10368) and duration that code should stay on the output.		Current version of init347.php looks for the mechanical shutter sequencer program (0x200-0x27f for odd/all exposures, 0x280-0x2ff - for even ones) and if it is empty - programs default sequence (will not change existent sequence). Mechanical shutter sequencer operates independently of the main one, it only starts at the moment defined by the main sequencer. There is a separate program [http://elphel.cvs.sourceforge.net/elphel/elphel353-7.1/apps/ccd/mshutter.php?view=markup mshutter.php] that allows to edit the sequence(s) in a human-readable/writable form - the init347.php contains just codes for the [http://elphel.cvs.sourceforge.net/elphel/elphel353-7.1/fpga/x347/shutter_seq.v?view=markup shutter_seq.v] - each word include the 8-bit output code for the shutter control board (10368) and duration that code should stay on the output.
			=== Programming the CPU board [[10353]] to receive/compress images ===
			This part of the code is not redesigned yet to support CCD imagers, it was intended for the CMOS sensors originally. So currently you may just use the [[ccam.cgi]] interface to acquire an image (the frame dimensions should match those specified for the sensor in init347.php or equivalents), some parameters currently have no effect (like "e=" - exposure time) - it will be fixed in the future, others are needed (JPEG compression quality, image size, bit width, color type (monochrome/color/jp4), gamma, color saturation. The following url should open the image and initialize [[10353]] board FPGA to acquire/compress images and place them into [[Circbuf\|circbuf]]:
			<nowiki>http://<camera_ip>:81/admin-bin/ccam.cgi?opt=*vhc&ww=4008&wh=2676&bit=8&iq=95&byr=0&gam=99&rscale=1&bscale=1&e=1</nowiki>