Elphel Camera Sandbox - Revision history

Andrey.filippov at 04:10, 2 June 2008

2008-06-02T04:10:13Z

← Older revision		Revision as of 04:10, 2 June 2008
Line 11:		Line 11:

	* a router/firewall		* a router/firewall
	* a manageable POE switch: Linksys SRW2008MP		<s>* a manageable POE switch: Linksys SRW2008MP</s> - did not work reliably, use our regular midspan PS with remote power on/off relay
	* a PC with an HD, x86 CPU 2 GB RAM, 2 network cards, DVDROM		* a PC with an HD, x86 CPU 2 GB RAM, 2 network cards, DVDROM
	* different combinations of Elphel 3xx cameras connected to the POE switch		* different combinations of Elphel 3xx cameras connected to the POE switch

Polto: /* Elphel Network Cameras */

2008-04-23T04:10:57Z

Elphel Network Cameras

← Older revision		Revision as of 04:10, 23 April 2008
Line 33:		Line 33:
	Different models or combinations of boards can be connected to the switch.		Different models or combinations of boards can be connected to the switch.

	Actually one Elphel 353 camera is available:		Actually one Elphel 353 camera with IDE zif HD connected to 10349 board is available:
	http://~~demo1~~.~~stvs~~.~~ch:3580~~		http://sandboxcam1.elphel.com

	~~fpt~~ and telnet are ~~also~~ available ~~on port 3521 and 3523~~.		HTTP, FTP and telnet are available.

Polto at 20:39, 11 April 2008

2008-04-11T20:39:10Z

← Older revision		Revision as of 20:39, 11 April 2008
Line 1:		Line 1:
	[[Image:Sandbox.jpg\|thumb\|Elphel Camera Sandbox connection ~~schema~~]]		[[Image:Sandbox.jpg\|thumb\|Elphel Camera Sandbox connection diagram]]

Polto: /* The server */

2008-04-10T23:00:08Z

The server

← Older revision		Revision as of 23:00, 10 April 2008
Line 18:		Line 18:
	=The server=		=The server=

	The server will run a modified version of [ElphelSoftwareKit]		The server will run a modified version of [[ElphelSoftwareKit]]

	the distribution ~~should~~ be modified to allow:		the distribution is be modified to allow:

	* to reserve an exclusive access to sandbox of a camera or of a LiveDVD distribution or both		* to reserve an exclusive access to sandbox of a camera or of a LiveDVD distribution or both
Line 28:		Line 28:
	* reboot a LiveDVD session		* reboot a LiveDVD session
	* bug report		* bug report


	=Elphel Network Cameras=		=Elphel Network Cameras=

Polto: /* Hardware */

2008-04-10T22:58:34Z

Hardware

← Older revision		Revision as of 22:58, 10 April 2008
Line 10:		Line 10:
	Our Sandbox is based on:		Our Sandbox is based on:

	* a router~~: Linksys WRT54GL 1.1 under OpenWrt GNU~~/~~Linux~~		* a router/firewall
	* a manageable POE switch: Linksys ~~SRW208P~~		* a manageable POE switch: Linksys SRW2008MP
	* a ~~server~~ with ~~at least one~~ HD, x86 CPU 1 GB RAM, 1 network cards, DVDROM		* a PC with an HD, x86 CPU 2 GB RAM, 2 network cards, DVDROM
	* different combinations of Elphel 3xx cameras connected to the POE switch		* different combinations of Elphel 3xx cameras connected to the POE switch
			** one Elphel 353 connected to the POE switch and by serial console to the PC for debugging

	=The server=		=The server=

Polto at 00:47, 17 December 2007

2007-12-17T00:47:18Z

← Older revision		Revision as of 00:47, 17 December 2007
Line 1:		Line 1:
	[[Image:Sandbox.jpg\|thumb\|Elphel Camera Sandbox connection schema]]		[[Image:Sandbox.jpg\|thumb\|Elphel Camera Sandbox connection schema]]

	This section describe ~~some ideas on~~ how to ~~build a~~ Sandbox of Elphel 3xx Network Reconfigurable Cameras.
			This section describe how to use the Sandbox of Elphel 3xx Network Reconfigurable Cameras.

	Please feel free to contribute and discuss on the proposed architecture.		Please feel free to contribute and discuss on the proposed architecture.

	=~~Needed hardware~~=		=Hardware=

	~~To build our~~ Sandbox ~~we need~~:		Our Sandbox is based on:

	* a manageable POE switch		* a router: Linksys WRT54GL 1.1 under OpenWrt GNU/Linux
	* a server with at least one HD, ~~Core2duo~~ CPU ~~suporting VT instructions, 4~~ GB RAM, 2 network cards, DVDROM		* a manageable POE switch: Linksys SRW208P
			* a server with at least one HD, x86 CPU 1 GB RAM, 1 network cards, DVDROM
	* different combinations of Elphel 3xx cameras connected to the POE switch		* different combinations of Elphel 3xx cameras connected to the POE switch

	=The server=		=The server=

	The server will ~~be installed under some virtualisation solution. (the reason for CPU supporting VT) We can use Xen, Vmware, virtualbox, Bosh, KVM, ...~~		The server will run a modified version of [ElphelSoftwareKit]

	~~Virtualisation will allow us~~ a ~~flexible way to manage LiveDVD sessions .~~

	~~The server will comport minimum 3 virtual servers:~~

	~~==Resident web server==~~

	~~In fact it's not only a web server. It's just a installed virtual server with a global interface and scripts~~ to ~~control the Sandbox.~~		the distribution should be modified to allow:

	~~The web interface should present those futures:~~		* to reserve an exclusive access to sandbox of a camera or of a LiveDVD distribution or both


	* to reserve an access to sandbox of a camera or of a LiveDVD distribution or both.
	* control the firewall and open or close connections to cameras / virtual servers.
	* control the POE switch (power up/down cameras, why not some statistics from the switch, like traffic, POE consumption, ...)		* control the POE switch (power up/down cameras, why not some statistics from the switch, like traffic, POE consumption, ...)
	* soft (reflash.php) and hard ("pressed" button and power up/down)		* soft (reflash.php) and hard ("pressed" button and power up/down)
	* store/restore users/developers configs from cameras / LiveDVD on ~~the resident~~ server.		* store/restore users/developers configs from cameras / LiveDVD on some server
	* reboot a LiveDVD session		* reboot a LiveDVD session
	* bug report		* bug report

	~~==Firewall==~~

	~~What's why the computer need 2 network cards, one of the virtual servers will act as firewall. He will be connected to both Internet and the dedicated Sandbox network.~~

	~~A part of the firewall rules will be controlled truth the global web interface to allow temporary connection to chosen cameras and Virtual servers.~~

	~~==LiveDVD==~~

	~~Where can be one or more LiveDVD running modified versions of Knoppix or Ubuntu.~~

	~~The LiveDVD session can be saved/restored/reseted truth the global web interface~~

	~~Some HD space is temporary dedicated for compilation and recording tests.~~

	=Elphel Network Cameras=		=Elphel Network Cameras=
Line 54:		Line 33:
	Different models or combinations of boards can be connected to the switch.		Different models or combinations of boards can be connected to the switch.

	~~We can map on the switch different ports to different VLANs and map them to different LiveDVD sessions.~~		Actually one Elphel 353 camera is available:
			http://demo1.stvs.ch:3580

	~~=Hardware reflashing unit=~~

	~~This is just an idea.~~

	~~Andrey, pls tell me if it's realistic and how to do it.~~

	~~The idea is to connect a 10333 / 10353 + some custom board connected under the button to allow to simulate button pressure on~~ one ~~or several cameras truth network. Coupled with the POE control it's a perfect solution to reflash a~~ camera ~~what is not correctly booted or configured...~~
	~~--[[User:Polto\|Polto]] 21:31, 30 November 2007 (CST)~~

	I believe it is enough to program "without button" and consider requirement to reflash as an abnormal condition (maybe analyzing logs can help to find out - what went wrong). So that will require human attention that I believe is ~~OK in that case.--[[User~~:~~Andrey.filippov\|Andrey.filippov]] 21:31, 30 November 2007 (CST)~~


	~~Ok, we can start like what. But it is sufficient to miss a something for example in init scripts or in network config to make it unavailable.~~
	~~--[[User~~:~~Polto\|Polto]] 21:58, 30 November 2007 (CST)~~

	~~== Buttonless camera ==~~
	Actually, thank you. I thought a little bit and our next camera revision will have no buttons at all. Four small components taking the same PCB area as a switch will do the job (2 capacitors, dual diode and a MOSFET transistor). To turn camera in programming mode you'll have to power-cycle it ~5 times (in a minute or so). A very simple and robust solution, no problems with broken buttons, easy to do manually or with the PoE switch, will not happen accidentally.--[[User:Andrey.~~filippov\|Andrey~~.~~filippov]] 23~~:~~28, 30 November 2007 (CST)~~

	~~wow! :) --[[User:Polto\|Polto]] 06:14, 1 December 2007 (CST)~~		fpt and telnet are also available on port 3521 and 3523.

Polto: /* Buttonless camera */

2007-12-01T12:14:39Z

Buttonless camera

← Older revision		Revision as of 12:14, 1 December 2007
Line 74:		Line 74:
	== Buttonless camera ==		== Buttonless camera ==
	Actually, thank you. I thought a little bit and our next camera revision will have no buttons at all. Four small components taking the same PCB area as a switch will do the job (2 capacitors, dual diode and a MOSFET transistor). To turn camera in programming mode you'll have to power-cycle it ~5 times (in a minute or so). A very simple and robust solution, no problems with broken buttons, easy to do manually or with the PoE switch, will not happen accidentally.--[[User:Andrey.filippov\|Andrey.filippov]] 23:28, 30 November 2007 (CST)		Actually, thank you. I thought a little bit and our next camera revision will have no buttons at all. Four small components taking the same PCB area as a switch will do the job (2 capacitors, dual diode and a MOSFET transistor). To turn camera in programming mode you'll have to power-cycle it ~5 times (in a minute or so). A very simple and robust solution, no problems with broken buttons, easy to do manually or with the PoE switch, will not happen accidentally.--[[User:Andrey.filippov\|Andrey.filippov]] 23:28, 30 November 2007 (CST)

			wow! :) --[[User:Polto\|Polto]] 06:14, 1 December 2007 (CST)

Andrey.filippov: /* buttonless camera */

2007-12-01T05:30:30Z

buttonless camera

← Older revision		Revision as of 05:30, 1 December 2007
Line 72:		Line 72:
	--[[User:Polto\|Polto]] 21:58, 30 November 2007 (CST)		--[[User:Polto\|Polto]] 21:58, 30 November 2007 (CST)

	== ~~buttonless~~ camera ==		== Buttonless camera ==
	Actually, thank you. I thought a little bit and our next camera revision will have no buttons at all. Four small components taking the same PCB area as a switch will do the job (2 capacitors, dual diode and a MOSFET transistor). To turn camera in programming mode you'll have to power-cycle it ~5 times (in a minute or so). A very simple and robust solution, no problems with broken buttons, easy to do manually or with the PoE switch, will not happen accidentally.--[[User:Andrey.filippov\|Andrey.filippov]] 23:28, 30 November 2007 (CST)		Actually, thank you. I thought a little bit and our next camera revision will have no buttons at all. Four small components taking the same PCB area as a switch will do the job (2 capacitors, dual diode and a MOSFET transistor). To turn camera in programming mode you'll have to power-cycle it ~5 times (in a minute or so). A very simple and robust solution, no problems with broken buttons, easy to do manually or with the PoE switch, will not happen accidentally.--[[User:Andrey.filippov\|Andrey.filippov]] 23:28, 30 November 2007 (CST)

Andrey.filippov: /* buttonless camera */

2007-12-01T05:29:37Z

buttonless camera

← Older revision		Revision as of 05:29, 1 December 2007
Line 73:		Line 73:

	== buttonless camera ==		== buttonless camera ==
	Actually, thank you. I thought a little bit and our next camera revision will have no buttons at all. Four small components taking the same PCB area as a switch will do the job (2 capacitors, dual diode and a MOSFET transistor). To turn camera in programming mode you'll have to power-cycle it ~5 times (in a minute or so). A very simple and robust solution, no problems with broken buttons, easy to do manually or with the switch, will not happen accidentally.--[[User:Andrey.filippov\|Andrey.filippov]] 23:28, 30 November 2007 (CST)		Actually, thank you. I thought a little bit and our next camera revision will have no buttons at all. Four small components taking the same PCB area as a switch will do the job (2 capacitors, dual diode and a MOSFET transistor). To turn camera in programming mode you'll have to power-cycle it ~5 times (in a minute or so). A very simple and robust solution, no problems with broken buttons, easy to do manually or with the PoE switch, will not happen accidentally.--[[User:Andrey.filippov\|Andrey.filippov]] 23:28, 30 November 2007 (CST)

Andrey.filippov: /* Hardware reflashing unit */

2007-12-01T05:28:54Z

Hardware reflashing unit

← Older revision		Revision as of 05:28, 1 December 2007
Line 72:		Line 72:
	--[[User:Polto\|Polto]] 21:58, 30 November 2007 (CST)		--[[User:Polto\|Polto]] 21:58, 30 November 2007 (CST)

			== buttonless camera ==
	Actually, thank you. I thought a little bit and our next camera revision will have no buttons at all. Four small components taking the same PCB area as a switch will do the job (2 capacitors, dual diode and a MOSFET transistor). To turn camera in programming mode you'll have to power-cycle it ~5 times (in a minute or so). A very simple and robust solution, no problems with broken buttons, easy to do manually or with the switch, will not happen accidentally.--[[User:Andrey.filippov\|Andrey.filippov]] 23:28, 30 November 2007 (CST)		Actually, thank you. I thought a little bit and our next camera revision will have no buttons at all. Four small components taking the same PCB area as a switch will do the job (2 capacitors, dual diode and a MOSFET transistor). To turn camera in programming mode you'll have to power-cycle it ~5 times (in a minute or so). A very simple and robust solution, no problems with broken buttons, easy to do manually or with the switch, will not happen accidentally.--[[User:Andrey.filippov\|Andrey.filippov]] 23:28, 30 November 2007 (CST)