Driver parameters - Revision history

Andrey.filippov: /* Example 2 - Changing analog gain of red color component of the sensor */

2007-10-17T07:43:41Z

Example 2 - Changing analog gain of red color component of the sensor

← Older revision		Revision as of 07:43, 17 October 2007
Line 56:		Line 56:
	When you change parameter that applies to the sensor (like, for example, gain of read color component):		When you change parameter that applies to the sensor (like, for example, gain of read color component):
	299 #define P_GAINR 46 /* R channel gain (mono gain) 8.8 0x100 - 1.0 */		299 #define P_GAINR 46 /* R channel gain (mono gain) 8.8 0x100 - 1.0 */

	<nowiki>http://<camera_ip>:81/senspars.php?cmd=write&addr=46&data=0x100</nowiki> -0x100 (256) means gain of 1.0		<nowiki>http://<camera_ip>:81/senspars.php?cmd=write&addr=46&data=0x100</nowiki> -0x100 (256) means gain of 1.0
	you will need to write a special register (P_UPDATE) with value "1" - apply the changes without interrupting acquisition or compression of the images (value "3" will restart the sensor and/or compressor). For some parameters (like changing image size) the restarting of the image acquisition/compression is required else it will most likely result in corrupted image		you will need to write a special register (P_UPDATE) with value "1" - apply the changes without interrupting acquisition or compression of the images (value "3" will restart the sensor and/or compressor). For some parameters (like changing image size) the restarting of the image acquisition/compression is required else it will most likely result in corrupted image

Andrey.filippov at 07:43, 17 October 2007

2007-10-17T07:43:21Z

← Older revision		Revision as of 07:43, 17 October 2007
Line 35:		Line 35:
	That data will be actually written to location 1024+54, at 54 there still be the current parameter value (in this example - 70%)		That data will be actually written to location 1024+54, at 54 there still be the current parameter value (in this example - 70%)

	<nowiki>http://<camera_ip>:81/senspars.php?cmd=read&addr=54</nowiki> will show:		<nowiki>http://<camera_ip>:81/senspars.php?cmd=read&addr=54</nowiki>
			It will show:
	54(0x36):70(0x46)		54(0x36):70(0x46)

	and only		and only

	<nowiki>http://<camera_ip>:81/senspars.php?cmd=read&addr=1078</nowiki> will immediately ~~get~~ the new value:		<nowiki>http://<camera_ip>:81/senspars.php?cmd=read&addr=1078</nowiki>
			will immediately return the new value:
	1078(0x436):100(0x64)		1078(0x436):100(0x64)

Line 46:		Line 48:
	<nowiki>http://192.168.0.9:81/compressor.php?cmd=run</nowiki>		<nowiki>http://192.168.0.9:81/compressor.php?cmd=run</nowiki>
	That will apply the change and if you try again		That will apply the change and if you try again
	<nowiki>http://<camera_ip>:81/senspars.php?cmd=read&addr=54</nowiki> - it will show the new value:		<nowiki>http://<camera_ip>:81/senspars.php?cmd=read&addr=54</nowiki>
			it will show the new value:
	54(0x36):100(0x64)		54(0x36):100(0x64)

Line 55:		Line 58:
	<nowiki>http://<camera_ip>:81/senspars.php?cmd=write&addr=46&data=0x100</nowiki> -0x100 (256) means gain of 1.0		<nowiki>http://<camera_ip>:81/senspars.php?cmd=write&addr=46&data=0x100</nowiki> -0x100 (256) means gain of 1.0
	you will need to write a special register (P_UPDATE) with value "1" - apply the changes without interrupting acquisition or compression of the images (value "3" will restart the sensor and/or compressor). For some parameters (like changing image size) the restarting of the image acquisition/compression is required else it will most likely result in corrupted image		you will need to write a special register (P_UPDATE) with value "1" - apply the changes without interrupting acquisition or compression of the images (value "3" will restart the sensor and/or compressor). For some parameters (like changing image size) the restarting of the image acquisition/compression is required else it will most likely result in corrupted image
	<nowiki>http://<camera_ip>:81/senspars.php?cmd=write&addr=0&data=1</nowiki> - after that the read command		<nowiki>http://<camera_ip>:81/senspars.php?cmd=write&addr=0&data=1</nowiki>
	<nowiki>http://<camera_ip>:81/senspars.php?cmd=read&addr=46</nowiki> will show the new value ~~fro~~ P_GAINR:		after that the read command
			<nowiki>http://<camera_ip>:81/senspars.php?cmd=read&addr=46</nowiki>
			will show the new value of the P_GAINR:
	46(0x2e):256(0x100)		46(0x2e):256(0x100)

	The [[Adjusting_sensor_clock_phase]] page shows how to use [http://elphel.cvs.sourceforge.net/elphel/elphel353-7.1/apps/ccd/senspars.php?view=markup senspars.php] to adjust the sensor clock phase to compensate for custom flex cables (different length) between the camera main board ([[10353]]) and the sensor front end (i.e. [[10338]])		The [[Adjusting_sensor_clock_phase]] page shows how to use [http://elphel.cvs.sourceforge.net/elphel/elphel353-7.1/apps/ccd/senspars.php?view=markup senspars.php] to adjust the sensor clock phase to compensate for custom flex cables (different length) between the camera main board ([[10353]]) and the sensor front end (i.e. [[10338]])

Andrey.filippov at 07:40, 17 October 2007

2007-10-17T07:40:50Z

← Older revision		Revision as of 07:40, 17 October 2007
Line 25:		Line 25:
	* cmd=write&addr=ra&data=rd - write rd to register ra		* cmd=write&addr=ra&data=rd - write rd to register ra
	Right now it is the very early state of the code, the numeric values of registers have to be (manually) looked up in [http://elphel.cvs.sourceforge.net/elphel/elphel353-7.1/os/linux-2.6-tag--devboard-R2_10-4/include/asm-cris/elphel/c313a.h c313a.h], the result of the read operations is just HTML code (TODO: XML data), write operations return empty page.		Right now it is the very early state of the code, the numeric values of registers have to be (manually) looked up in [http://elphel.cvs.sourceforge.net/elphel/elphel353-7.1/os/linux-2.6-tag--devboard-R2_10-4/include/asm-cris/elphel/c313a.h c313a.h], the result of the read operations is just HTML code (TODO: XML data), write operations return empty page.
			==== Example 1 - Changing JPEG compression quality ====
	But it already works. Here is an example of changing the JPEG compression quality to 100% (no quantization loss):		But it already works. Here is an example of changing the JPEG compression quality to 100% (no quantization loss):

Line 48:		Line 48:
	<nowiki>http://<camera_ip>:81/senspars.php?cmd=read&addr=54</nowiki> - it will show the new value:		<nowiki>http://<camera_ip>:81/senspars.php?cmd=read&addr=54</nowiki> - it will show the new value:
	54(0x36):100(0x64)		54(0x36):100(0x64)

			==== Example 2 - Changing analog gain of red color component of the sensor ====

	When you change parameter that applies to the sensor (like, for example, gain of read color component):		When you change parameter that applies to the sensor (like, for example, gain of read color component):

Andrey.filippov at 07:38, 17 October 2007

2007-10-17T07:38:28Z

← Older revision		Revision as of 07:38, 17 October 2007
Line 1:		Line 1:
	== History ==		=== History ===
	From the very first Elphel camera (Model 303) camera driver maintained data array that was accessible by the applications through IOCTL calls. Total number of elements (32-bit data words) was 64 (limited by address bits designated for that purpose in IOCTL command map, the indexes are defined in the [http://elphel.cvs.sourceforge.net/elphel/elphel353-7.1/os/linux-2.6-tag--devboard-R2_10-4/include/asm-cris/elphel/c313a.h?view=markup c313a.h](names starting with P_ ). Most (but not all) of the elements are represented in two arrays - imageParamsW[] and imageParamsR[], first (W for "write") having the data passed by the applications through IOCTL (example from the [http://elphel.cvs.sourceforge.net/elphel/elphel353-7.1/apps/ccam/ccam.c?view=markup ccam.c] - described in [[Ccam.cgi]]. The next line passes compression quality received as part of the GET request to the driver:		From the very first Elphel camera (Model 303) camera driver maintained data array that was accessible by the applications through IOCTL calls. Total number of elements (32-bit data words) was 64 (limited by address bits designated for that purpose in IOCTL command map, the indexes are defined in the [http://elphel.cvs.sourceforge.net/elphel/elphel353-7.1/os/linux-2.6-tag--devboard-R2_10-4/include/asm-cris/elphel/c313a.h?view=markup c313a.h](names starting with P_ ). Most (but not all) of the elements are represented in two arrays - imageParamsW[] and imageParamsR[], first (W for "write") having the data passed by the applications through IOCTL (example from the [http://elphel.cvs.sourceforge.net/elphel/elphel353-7.1/apps/ccam/ccam.c?view=markup ccam.c] - described in [[Ccam.cgi]]. The next line passes compression quality received as part of the GET request to the driver:

Line 12:		Line 12:
	These arrays and parameter definitions were changing with the new camera models, new sensors features that became available, new additions to the FPGA code. Address space of just 64 locations was too small and we have to eliminate older parameters and combine several in a single 32-bit word.		These arrays and parameter definitions were changing with the new camera models, new sensors features that became available, new additions to the FPGA code. Address space of just 64 locations was too small and we have to eliminate older parameters and combine several in a single 32-bit word.

	== Read/write/lseek vs. ioctl ==		=== Read/write/lseek vs. ioctl ===

	When the model 353 started to support PHP it became important to have those camera driver parameters to be accessible from the PHP programs. And with the desire to increase the address space we expanded imageParamsR[] and imageParamsW[] arrays to 1024 elements (4096 bytes) each and now they can be read/written as form/to a character device (''/dev/sensorpars''). Both arrays are combined together into a single 8192 byte file where the first 4096 (1024 of 32-bit words) correspond to the imageParamsR[], and the second - to imageParamsW[], but writing to the first half (to imageParamsR[]) effectively writes to the corresponding element of imageParamsW[] (that is 4096 bytes after), so writing to the byte 4 is the same as writing to the byte 4+4096=4100.		When the model 353 started to support PHP it became important to have those camera driver parameters to be accessible from the PHP programs. And with the desire to increase the address space we expanded imageParamsR[] and imageParamsW[] arrays to 1024 elements (4096 bytes) each and now they can be read/written as form/to a character device (''/dev/sensorpars''). Both arrays are combined together into a single 8192 byte file where the first 4096 (1024 of 32-bit words) correspond to the imageParamsR[], and the second - to imageParamsW[], but writing to the first half (to imageParamsR[]) effectively writes to the corresponding element of imageParamsW[] (that is 4096 bytes after), so writing to the byte 4 is the same as writing to the byte 4+4096=4100.

	== Using [http://elphel.cvs.sourceforge.net/elphel/elphel353-7.1/apps/ccd/senspars.php?view=markup senspars.php] to access driver parameters ==		=== Using [http://elphel.cvs.sourceforge.net/elphel/elphel353-7.1/apps/ccd/senspars.php?view=markup senspars.php] to access driver parameters ===

	There is a simple PHP script that demonstrates access to the camera driver parameters from the PHP code. If the URL is opened without any parameters:		There is a simple PHP script that demonstrates access to the camera driver parameters from the PHP code. If the URL is opened without any parameters:

Andrey.filippov at 05:36, 17 October 2007

2007-10-17T05:36:56Z

← Older revision		Revision as of 05:36, 17 October 2007
Line 54:		Line 54:
	you will need to write a special register (P_UPDATE) with value "1" - apply the changes without interrupting acquisition or compression of the images (value "3" will restart the sensor and/or compressor). For some parameters (like changing image size) the restarting of the image acquisition/compression is required else it will most likely result in corrupted image		you will need to write a special register (P_UPDATE) with value "1" - apply the changes without interrupting acquisition or compression of the images (value "3" will restart the sensor and/or compressor). For some parameters (like changing image size) the restarting of the image acquisition/compression is required else it will most likely result in corrupted image
	<nowiki>http://<camera_ip>:81/senspars.php?cmd=write&addr=0&data=1</nowiki> - after that the read command		<nowiki>http://<camera_ip>:81/senspars.php?cmd=write&addr=0&data=1</nowiki> - after that the read command
	<nowiki>http://<camera_ip>:81/senspars.php?cmd=read&addr=46</nowiki> ~~- it~~ will show the new value:		<nowiki>http://<camera_ip>:81/senspars.php?cmd=read&addr=46</nowiki> will show the new value fro P_GAINR:
	46(0x2e):256(0x100)		46(0x2e):256(0x100)

			The [[Adjusting_sensor_clock_phase]] page shows how to use [http://elphel.cvs.sourceforge.net/elphel/elphel353-7.1/apps/ccd/senspars.php?view=markup senspars.php] to adjust the sensor clock phase to compensate for custom flex cables (different length) between the camera main board ([[10353]]) and the sensor front end (i.e. [[10338]])

Andrey.filippov at 05:32, 17 October 2007

2007-10-17T05:32:02Z

← Older revision		Revision as of 05:32, 17 October 2007
Line 47:		Line 47:
	That will apply the change and if you try again		That will apply the change and if you try again
	<nowiki>http://<camera_ip>:81/senspars.php?cmd=read&addr=54</nowiki> - it will show the new value:		<nowiki>http://<camera_ip>:81/senspars.php?cmd=read&addr=54</nowiki> - it will show the new value:
	54(0x36)::100(0x64)		54(0x36):100(0x64)

			When you change parameter that applies to the sensor (like, for example, gain of read color component):
	3. ~~Now~~ write a special register (P_UPDATE) with value "3" - ~~it will immediately~~ apply the changes ~~and restart FPGA compressor~~ (value "1" will ~~apply changes without restarting~~ sensor or compressor ~~- with~~ some parameters it ~~can~~ result in corrupted image ~~or even no image at all):~~		299 #define P_GAINR 46 /* R channel gain (mono gain) 8.8 0x100 - 1.0 */
	<nowiki>http://<camera_ip>:81/senspars.php?cmd=write&addr=0&data=3</nowiki> -~~(opens empty page)~~		<nowiki>http://<camera_ip>:81/senspars.php?cmd=write&addr=46&data=0x100</nowiki> -0x100 (256) means gain of 1.0
			you will need to write a special register (P_UPDATE) with value "1" - apply the changes without interrupting acquisition or compression of the images (value "3" will restart the sensor and/or compressor). For some parameters (like changing image size) the restarting of the image acquisition/compression is required else it will most likely result in corrupted image
	~~Next time the image will be compressed~~ it will ~~use~~ the new value ~~for JPEG quality and then~~ (~~not before~~) ~~the value of the "current" JPEG quality will be updated.~~		<nowiki>http://<camera_ip>:81/senspars.php?cmd=write&addr=0&data=1</nowiki> - after that the read command
			<nowiki>http://<camera_ip>:81/senspars.php?cmd=read&addr=46</nowiki> - it will show the new value:
			46(0x2e):256(0x100)

Andrey.filippov at 05:19, 17 October 2007

2007-10-17T05:19:01Z

← Older revision		Revision as of 05:19, 17 October 2007
Line 42:		Line 42:
	<nowiki>http://<camera_ip>:81/senspars.php?cmd=read&addr=1078</nowiki> will immediately get the new value:		<nowiki>http://<camera_ip>:81/senspars.php?cmd=read&addr=1078</nowiki> will immediately get the new value:
	1078(0x436):100(0x64)		1078(0x436):100(0x64)

			3. JPEG quality value controls compressor, not the sensor (or sensor-related part of the FPGA), it is processed when the compressor is programmed. To apply it you may start (or re-start) the compressor with the command
			<nowiki>http://192.168.0.9:81/compressor.php?cmd=run</nowiki>
			That will apply the change and if you try again
			<nowiki>http://<camera_ip>:81/senspars.php?cmd=read&addr=54</nowiki> - it will show the new value:
			54(0x36)::100(0x64)


	3. Now write a special register (P_UPDATE) with value "3" - it will immediately apply the changes and restart FPGA compressor (value "1" will apply changes without restarting sensor or compressor - with some parameters it can result in corrupted image or even no image at all):		3. Now write a special register (P_UPDATE) with value "3" - it will immediately apply the changes and restart FPGA compressor (value "1" will apply changes without restarting sensor or compressor - with some parameters it can result in corrupted image or even no image at all):
	<nowiki>http://<camera_ip>:81/senspars.php?cmd=write&addr=0&data=3</nowiki> -(opens empty page)		<nowiki>http://<camera_ip>:81/senspars.php?cmd=write&addr=0&data=3</nowiki> -(opens empty page)

	Next time the image will be compressed it will use the new value for JPEG quality and then (not before) the value of the "current" JPEG quality will be updated.		Next time the image will be compressed it will use the new value for JPEG quality and then (not before) the value of the "current" JPEG quality will be updated.

Andrey.filippov at 05:09, 17 October 2007

2007-10-17T05:09:39Z

@@ Line 28: / Line 28: @@
 But it already works. Here is an example of changing the JPEG compression quality to 100% (no quantization loss):
-# looking into [http://elphel.cvs.sourceforge.net/elphel/elphel353-7.1/os/linux-2.6-tag--devboard-R2_10-4/include/asm-cris/elphel/c313a.h c313a.h]
+. looking into [http://elphel.cvs.sourceforge.net/elphel/elphel353-7.1/os/linux-2.6-tag--devboard-R2_10-4/include/asm-cris/elphel/c313a.h c313a.h]
 #define P_QUALITY       54 // JPEG IMAGE QUALITY
-# making access to the following URL:
+. making access to the following URL:
-  <nowiki>http://<camera_ip>:81/senspars.php?cmd=write&addr=54&data=100</nowiki>
+  <nowiki>http://<camera_ip>:81/senspars.php?cmd=write&addr=54&data=100</nowiki> -(opens empty page)

Andrey.filippov at 04:50, 17 October 2007

2007-10-17T04:50:11Z

@@ Line 8: / Line 8: @@
     ImageWidth =  ioctl(data_fd, _CCCMD( CCAM_RPARS , P_ACTUAL_WIDTH ), 0);
-Some elements are readonly (like P_SENSOR that returns the type of the sensor used in the camera), others (P_UPDATE) initiate actions when written to.
+Some elements are read only (like P_SENSOR that returns the type of the sensor used in the camera), others (P_UPDATE) initiate actions when written to.
 These arrays and parameter definitions were changing with the new camera models, new sensors features that became available, new additions to the FPGA code. Address space of just 64 locations was too small and we have to eliminate older parameters and combine several in a single 32-bit word.
@@ Line 15: / Line 15: @@
 When the  model 353 started to support PHP it became important to have those camera driver parameters to be accessible from the PHP programs. And with the desire to increase the address space we expanded imageParamsR[] and imageParamsW[] arrays to 1024 elements (4096 bytes) each and now they can be read/written as form/to a character device (''/dev/sensorpars''). Both arrays are combined together into a single 8192 byte file where the first 4096 (1024 of 32-bit words) correspond to the imageParamsR[], and the second - to imageParamsW[], but writing to the first half (to imageParamsR[]) effectively writes to the corresponding element of imageParamsW[] (that is 4096 bytes after), so writing to the byte 4 is the same as writing to the byte 4+4096=4100.

Andrey.filippov at 04:01, 17 October 2007

2007-10-17T04:01:35Z

← Older revision		Revision as of 04:01, 17 October 2007
Line 8:		Line 8:
	1136 ImageWidth = ioctl(data_fd, _CCCMD( CCAM_RPARS , P_ACTUAL_WIDTH ), 0);		1136 ImageWidth = ioctl(data_fd, _CCCMD( CCAM_RPARS , P_ACTUAL_WIDTH ), 0);

	Some elements are readonly (like P_SENSOR that returns the type of the sensor used in the camera), others (P_UPDATE) initiate actions when written.		Some elements are readonly (like P_SENSOR that returns the type of the sensor used in the camera), others (P_UPDATE) initiate actions when written to.

	These arrays and parameter definitions were changing with the new camera models, new sensors features that became available, new additions to the FPGA code. Address space of just 64 locations was too small and we have to eliminate older parameters and combine several in a single 32-bit word.		These arrays and parameter definitions were changing with the new camera models, new sensors features that became available, new additions to the FPGA code. Address space of just 64 locations was too small and we have to eliminate older parameters and combine several in a single 32-bit word.

	== Read/write/lseek vs. ioctl ==		== Read/write/lseek vs. ioctl ==

			When the model 353 started to support PHP it became important to have those camera driver parameters to be accessible from the PHP programs. And with the desire to increase the address space we expanded imageParamsR[] and imageParamsW[] arrays to 1024 elements (4096 bytes) each and now they can be read/written as form/to a character device (''/dev/sensorpars''). Both arrays are combined together into a single 8192 byte file where the first 4096 (1024 of 32-bit words) correspond to the imageParamsR[], and the second - to imageParamsW[], but writing to the first half (to imageParamsR[]) effectively writes to the corresponding element of imageParamsW[] (that is 4096 bytes after), so writing to the byte 4 is the same as writing to the byte 4+4096=4100.