Advanced IP Camera - Revision history

Sambuca: Updated to current development

2012-08-10T10:44:06Z

Updated to current development

←Older revision		Revision as of 10:44, 10 August 2012
Line 14:		Line 14:
	* Generic Output on camera [1]		* Generic Output on camera [1]
	* Zoom and Pan (not tested)		* Zoom and Pan (not tested)
	[1] Using the "url" method, see below for details.		[1] Using the "url", "urlPoll" or "httpserver" method, see below for details.


	This device template is not meant to be used directly, even though it can. The idea is that this template describes the available options that the Advanced_IP_Camera binary supports, and a device template for a specific make and model should specify the correct options for that device. See the D-Link DCS-2121 template as example of how to create a template for a specific camera model.		This device template is not meant to be used directly, even though it can. The idea is that this template describes the available options that the Advanced_IP_Camera binary supports, and a device template for a specific make and model should specify the correct options for that device. See the D-Link DCS-2121 or IPCAM02 template as example of how to create a template for a specific camera model.


	~~'''This device template is current under development and what is described here may not be accurate!'''~~

	=Creating a device template based on Advanced IP Camera=		=Creating a device template based on Advanced IP Camera=
Line 44:		Line 42:
	* Configuration: specify what method to use to access the cameras events (motion detection, input changes etc.)		* Configuration: specify what method to use to access the cameras events (motion detection, input changes etc.)
	The available options are (this is an example)		The available options are (this is an example)
	eventMethod1=[url,httpserver,ftpserver,smtpserver] (only url currently implemented)		eventMethod1=[url,urlPoll,httpserver,ftpserver,smtpserver] (only url,urlPoll and httpserver currently implemented)
	eventURL1=[/cgi/web_event.cgi\|localhost:25\|~~localhost:~~8080]		eventURL1=[/cgi/web_event.cgi\|localhost:25\|8080]
			eventInterval1=10
	controlURL=/cgi-bin/camctrl.cgi?		controlURL=/cgi-bin/camctrl.cgi?
	panUpCmd=move=up		panUpCmd=move=up
Line 61:		Line 60:
	===Methods===		===Methods===
	Methods are different ways that the camera provides access to event and control data. There are a few types:		Methods are different ways that the camera provides access to event and control data. There are a few types:
	* url : control/data by means of accessing an url on the camera		* url : control/data by means of accessing an url on the camera. This type should be used when the camera supports keeping the connection open and sending more data as it becomes available.
	* httpserver : camera will send data to a specified http server ~~address (not implemented yet)~~		* urlPoll : control/data by access an url on the camera, and this needs to polled regulary (specify using eventInterval1=<seconds>), because the camera will close the connection after it has sent its data
	* ftpserver : camera will send data to a specified ftp server ~~address~~ (not implemented yet and unsure about its usefulness)		* httpserver : camera will send data to a specified http server port
	* smtpserver : camera will send data to a specified smtp server ~~address~~ (not implemented yet and unsure about its usefulness)		* ftpserver : camera will send data to a specified ftp server port (not implemented yet and unsure about its usefulness)
			* smtpserver : camera will send data to a specified smtp server port (not implemented yet and unsure about its usefulness)
	All these are valid for data/events, but only url is used for control.		All these are valid for data/events, but only url is used for control.

Line 79:		Line 79:
	The device templates currently working with the Advanced IP Camera is Motion Detector, Generic Sensor and Generic Input Output.		The device templates currently working with the Advanced IP Camera is Motion Detector, Generic Sensor and Generic Input Output.

	See the D-Link DCS-2121 template for an example.		See the D-Link DCS-2121 or IPCAM02 template for an example.

			'''You need to use only : or line breaks in your configuration, mixing both is not supported'''

	==== Motion detectors ====		==== Motion detectors ====
Line 117:		Line 119:

	==Current Plans==		==Current Plans==
	~~Short term plans are to add support for pan/tilt/zoom configuration.~~		The medium-term plans are to add support for other types of event methods - ways that the camera informs us about changes in state. Their usefullness must be evaluated first - and as always, if there are no requests for it, there will be no support either.

	The medium-term plans are to add support for other types of event methods - ways that the camera informs us about changes in state. ~~The~~ first ~~on the list is to implement~~ support ~~for cameras that connect to a http server when motion is detected~~.

	The medium/long-term plans are to look into video and audio support. Many cameras have a microphone and a speaker. It will be interesting to see if this can be used in LinuxMCE.		The medium/long-term plans are to look into video and audio support. Many cameras have a microphone and a speaker. It will be interesting to see if this can be used in LinuxMCE.

Sambuca at 11:24, 1 August 2012

2012-08-01T11:24:36Z

←Older revision		Revision as of 11:24, 1 August 2012
Line 13:		Line 13:
	* Generic Sensor inputs on camera [1]		* Generic Sensor inputs on camera [1]
	* Generic Output on camera [1]		* Generic Output on camera [1]
			* Zoom and Pan (not tested)
	[1] Using the "url" method, see below for details.		[1] Using the "url" method, see below for details.

Line 45:		Line 46:
	eventMethod1=[url,httpserver,ftpserver,smtpserver] (only url currently implemented)		eventMethod1=[url,httpserver,ftpserver,smtpserver] (only url currently implemented)
	eventURL1=[/cgi/web_event.cgi\|localhost:25\|localhost:8080]		eventURL1=[/cgi/web_event.cgi\|localhost:25\|localhost:8080]
			controlURL=/cgi-bin/camctrl.cgi?
			panUpCmd=move=up
			panDownCmd=move=down
			- similar for left and right
			zoomInCmd=zoom=in
			- same for out

	If you have several different methods, use eventMethod2, eventURL2 etc...		If you have several different methods, use eventMethod2, eventURL2 etc...

			The panUpCmd, zoomInCmd and similar are appended to the controlURL. The controlURL is not required, and thus it is possible to use a completely different url to control pan and zoom.

			All URLs are relative to the root of the device. So the example above will for a pan up, result in a request to http://x.x.x.x/cgi-bin/camctrl.cgi?move=up and includes the authentication (username and password) specified, if any.

	===Methods===		===Methods===

Sambuca at 10:39, 19 July 2012

2012-07-19T10:39:28Z

←Older revision		Revision as of 10:39, 19 July 2012
Line 47:		Line 47:

	If you have several different methods, use eventMethod2, eventURL2 etc...		If you have several different methods, use eventMethod2, eventURL2 etc...

			===Methods===
			Methods are different ways that the camera provides access to event and control data. There are a few types:
			* url : control/data by means of accessing an url on the camera
			* httpserver : camera will send data to a specified http server address (not implemented yet)
			* ftpserver : camera will send data to a specified ftp server address (not implemented yet and unsure about its usefulness)
			* smtpserver : camera will send data to a specified smtp server address (not implemented yet and unsure about its usefulness)
			All these are valid for data/events, but only url is used for control.

	==Commands and events==		==Commands and events==
Line 59:		Line 67:

	The device templates currently working with the Advanced IP Camera is Motion Detector, Generic Sensor and Generic Input Output.		The device templates currently working with the Advanced IP Camera is Motion Detector, Generic Sensor and Generic Input Output.

			See the D-Link DCS-2121 template for an example.

	==== Motion detectors ====		==== Motion detectors ====
	Motion detectors use the Capabilities data to describe how to look for ~~events. The D-Link camera sends all events on a http connection that stays open, so we can look for a specific string that triggers the~~ events.		Motion detectors use the Capabilities data to describe how to look for events.
	Example on capabilities configuration:		Example on capabilities configuration:
	method=1		method=1

Sambuca: /* Introduction */

2012-07-19T10:32:16Z

Introduction

←Older revision		Revision as of 10:32, 19 July 2012
Line 6:		Line 6:
	=Introduction=		=Introduction=
	The Advanced IP Camera is a generic device template which aims to utilize more features of modern IP cameras than GSD templates can.		The Advanced IP Camera is a generic device template which aims to utilize more features of modern IP cameras than GSD templates can.

	~~'''This device template is current under development and what is described here may not be accurate!'''~~


	Currently working:		Currently working:
	* Image retrieval		* Image retrieval
	* Motion detection events ~~(for D-Link cameras - DCS-2121 used when developing)~~		* Motion detection events [1]
	* Generic Sensor inputs on camera ~~(D-Link)~~		* Generic Sensor inputs on camera [1]
	* Generic Output on camera ~~(D-Link)~~		* Generic Output on camera [1]
			[1] Using the "url" method, see below for details.


	This device template is not meant to be used directly, even though it can. The idea is that this template describes the available options that the Advanced_IP_Camera binary supports, and a device template for a specific make and model should specify the correct options for that device. See the D-Link DCS-2121 template as example (to be ~~made).~~		This device template is not meant to be used directly, even though it can. The idea is that this template describes the available options that the Advanced_IP_Camera binary supports, and a device template for a specific make and model should specify the correct options for that device. See the D-Link DCS-2121 template as example of how to create a template for a specific camera model.


			'''This device template is current under development and what is described here may not be accurate!'''

	=Creating a device template based on Advanced IP Camera=		=Creating a device template based on Advanced IP Camera=

Sambuca: /* Current Plans */

2012-07-19T10:29:41Z

Current Plans

←Older revision		Revision as of 10:29, 19 July 2012
Line 94:		Line 94:

	==Current Plans==		==Current Plans==
	The ~~short~~-term plans are to add support for other types of event methods - ways that the camera informs us about changes in state. The first on the list is to implement support for cameras that connect to a http server when motion is detected.		Short term plans are to add support for pan/tilt/zoom configuration.

			The medium-term plans are to add support for other types of event methods - ways that the camera informs us about changes in state. The first on the list is to implement support for cameras that connect to a http server when motion is detected.

	The medium/long-term plans are to look into video and audio support. Many cameras have a microphone and a speaker. It will be interesting to see if this can be used in LinuxMCE.		The medium/long-term plans are to look into video and audio support. Many cameras have a microphone and a speaker. It will be interesting to see if this can be used in LinuxMCE.

Sambuca at 22:44, 18 July 2012

2012-07-18T22:44:21Z

←Older revision		Revision as of 22:44, 18 July 2012
Line 54:		Line 54:

	===Device data for children===		===Device data for children===
	Device data for children can be specified as a list of <PK_DeviceData>\|<DataValue>\|<PK_DeviceData>\|<DataValue>\|...etc		Device data for children can be specified as a list of <PK_DeviceData>\|<DataValue>\|<PK_DeviceData>\|<DataValue>\|...etc. Line breaks in the examples below can be replaced by : when entering the "extra" related device data field.

	The device templates currently working with the Advanced IP Camera is Motion Detector, Generic Sensor and Generic Input Output.		The device templates currently working with the Advanced IP Camera is Motion Detector, Generic Sensor and Generic Input Output.
Line 97:		Line 97:

	The medium/long-term plans are to look into video and audio support. Many cameras have a microphone and a speaker. It will be interesting to see if this can be used in LinuxMCE.		The medium/long-term plans are to look into video and audio support. Many cameras have a microphone and a speaker. It will be interesting to see if this can be used in LinuxMCE.

			=Notes=
			IP Cameras use (afaik) changes in the image/video stream to detect motion. This can be a disadvantage compared to regular PIR (Passive Infrared detectors). While PIRs only detect rapid temperature changes in a particular area, like when a human body(warm body) moves in front of the detector, an IP camera will signal that motion is detected when the image changes from one frame to another. This implies that it does not need to be a warm body motion, but rather any motion at all. It could be a bird flying past your window, or your curtain swaying in the wind. This is probably not what you want, but unfortunately, it is a limitation of image-motion-based camera.

			Using the motion wrapper on any analog or IP camera will also result in the same behaviour as pure IP camera motion detection.

			So consider your use case and find out what is best suited, a motion-detection capable IP camera, or a PIR, or perhaps even a combination.

Sambuca: Updated to current development

2012-07-18T21:49:47Z

Updated to current development

@@ Line 13: / Line 13: @@
 * Image retrieval
 * Motion detection events (for D-Link cameras  - DCS-2121 used when developing)
@@ Line 32: / Line 34: @@
 Other data are optional and depends on what features your camera has.
 Options:
 * AuthUser: Username to authenticate to the camera
 * AuthPassword: Password to authenticate to the camera
@@ Line 40: / Line 41: @@
 * Configuration: specify what method to use to access the cameras events (motion detection, input changes etc.)
 The available options are (this is an example)
-  eventMethod1=[url,httpserver,ftpserver,smtpserver]
+  eventMethod1=[url,httpserver,ftpserver,smtpserver] (only url currently implemented)
   eventURL1=[/cgi/web_event.cgi|localhost:25|localhost:8080]
 If you have several different methods, use eventMethod2, eventURL2 etc...
@@ Line 56: / Line 56: @@
 Device data for children can be specified as a list of <PK_DeviceData>|<DataValue>|<PK_DeviceData>|<DataValue>|...etc
 Motion detectors use the Capabilities data to describe how to look for events. The D-Link camera sends all events on a http connection that stays open, so we can look for a specific string that triggers the events.
 Example on capabilities configuration:
@@ Line 66: / Line 69: @@
 It uses the "pattern" trigger method, which simply checks for the existence of patternOn and patternOff to trigger on/off or sensor tripped changes.
 =Development notes=
 I'm looking for information about how other types of cameras implement events and camera controls. To be able to support as many types of camera manufacturers, we need to find out what support we need to implement. So if you want your particular camera supported, either send me a camera to test, or post the required data here.

Sambuca: /* Device data for children */

2012-06-29T13:05:04Z

Device data for children

←Older revision		Revision as of 13:05, 29 June 2012
Line 57:		Line 57:

	Motion detectors use the Capabilities data to describe how to look for events. The D-Link camera sends all events on a http connection that stays open, so we can look for a specific string that triggers the events.		Motion detectors use the Capabilities data to describe how to look for events. The D-Link camera sends all events on a http connection that stays open, so we can look for a specific string that triggers the events.
			Example on capabilities configuration:
			method=1
			triggerMethod=pattern
			patternOn=motiondetected=1
			patternOff=motiondetected=0

			This says that this device is using the eventMethod 1 defined in the camera device.

			It uses the "pattern" trigger method, which simply checks for the existence of patternOn and patternOff to trigger on/off or sensor tripped changes.

	=Development notes=		=Development notes=
	I'm looking for information about how other types of cameras implement events and camera controls. To be able to support as many types of camera manufacturers, we need to find out what support we need to implement. So if you want your particular camera supported, either send me a camera to test, or post the required data here.		I'm looking for information about how other types of cameras implement events and camera controls. To be able to support as many types of camera manufacturers, we need to find out what support we need to implement. So if you want your particular camera supported, either send me a camera to test, or post the required data here.

Sambuca: /* Device data for the template */

2012-06-29T12:52:30Z

Device data for the template

←Older revision		Revision as of 12:52, 29 June 2012
Line 40:		Line 40:
	* Configuration: specify what method to use to access the cameras events (motion detection, input changes etc.)		* Configuration: specify what method to use to access the cameras events (motion detection, input changes etc.)
	The available options are (this is an example)		The available options are (this is an example)
	eventMethod1=[url,httpserver,ftpserver,smtpserver]		eventMethod1=[url,httpserver,ftpserver,smtpserver]
	eventURL1=[/cgi/web_event.cgi\|localhost:25\|localhost:8080]		eventURL1=[/cgi/web_event.cgi\|localhost:25\|localhost:8080]
	controlURL1=[/dev/gpioCtrl.cgi]		controlURL1=[/dev/gpioCtrl.cgi]

	If you have several different methods, use eventMethod2, eventURL2 etc...		If you have several different methods, use eventMethod2, eventURL2 etc...

Sambuca at 12:52, 29 June 2012

2012-06-29T12:52:13Z

←Older revision		Revision as of 12:52, 29 June 2012
Line 38:		Line 38:
	* Video Settings: URL where video can be retrieved from the camera		* Video Settings: URL where video can be retrieved from the camera
	* Control path: URL to control the camera		* Control path: URL to control the camera
			* Configuration: specify what method to use to access the cameras events (motion detection, input changes etc.)
			The available options are (this is an example)
			eventMethod1=[url,httpserver,ftpserver,smtpserver]
			eventURL1=[/cgi/web_event.cgi\|localhost:25\|localhost:8080]
			controlURL1=[/dev/gpioCtrl.cgi]

			If you have several different methods, use eventMethod2, eventURL2 etc...

	==Commands and events==		==Commands and events==