Touch Panels - Revision history

Dr jesus at 07:47, 2 March 2011

2011-03-02T07:47:30Z

← Older revision		Revision as of 00:47, 2 March 2011
Line 88:		Line 88:
	* Reboot the rest of the machines if you're happy.		* Reboot the rest of the machines if you're happy.
	* If nothing breaks after a while, do a hg commit in /netboot/config.		* If nothing breaks after a while, do a hg commit in /netboot/config.

			== Testing the image ==

			On stallion:
			qemu -net nic -net user,tftp=/netboot/tftpboot,bootfile=pxelinux.0,hostfwd=tcp::2223-:22 -curses -boot n

			On pony:
			sudo kvm -net nic -net tap -curses -boot n

AlSweigart at 06:09, 8 February 2011

2011-02-08T06:09:52Z

← Older revision		Revision as of 23:09, 7 February 2011
Line 8:		Line 8:

	There are 10x [http://www.parkytowers.me.uk/thin/Wyse3150SE/index.shtml Wyse 3150SE] thin clients available to drive the touch panels. The touch panels are made by iNexio and there is a custom XInput driver available for them in the source repository.		There are 10x [http://www.parkytowers.me.uk/thin/Wyse3150SE/index.shtml Wyse 3150SE] thin clients available to drive the touch panels. The touch panels are made by iNexio and there is a custom XInput driver available for them in the source repository.

			The [[Inexio]] touch panels have their own wiki page with more info.

	== Troubleshooting ==		== Troubleshooting ==

Dr jesus at 19:59, 20 January 2011

2011-01-20T19:59:27Z

← Older revision		Revision as of 12:59, 20 January 2011
Line 3:		Line 3:
	The system that runs the touchpanel laptop by the door (172.30.0.31) is required for opengate-www and opengate scripts to work. It is connected by parallel port to a relay which is linked into the door buzzer system.		The system that runs the touchpanel laptop by the door (172.30.0.31) is required for opengate-www and opengate scripts to work. It is connected by parallel port to a relay which is linked into the door buzzer system.

	~~This laptop runs uses~~ PXE boot and an image from a tftp server on [[Stallion]] to run~~{{verify}}~~. ~~It will not boot without~~ network ~~and this server on the remote system~~.		All the touch panel machines use PXE boot and an image from a tftp server on [[Stallion]] to run. They require network access to stallion to come up.

	Currently the boot image for the panel starts up linux, runs Iceweasel full screen and points to a URL on [[Pony]]. There's a neat extensible interface that provides information and control regarding things we currently have in the space.		Currently the boot image for the panel starts up linux, runs Iceweasel full screen and points to a URL on [[Pony]]. There's a neat extensible interface that provides information and control regarding things we currently have in the space.

	There are 10x [http://www.parkytowers.me.uk/thin/Wyse3150SE/index.shtml Wyse 3150SE] thin clients available to drive the touch panels. The touch panels are made by iNexio and there is a custom XInput driver available for them in the source repository.		There are 10x [http://www.parkytowers.me.uk/thin/Wyse3150SE/index.shtml Wyse 3150SE] thin clients available to drive the touch panels. The touch panels are made by iNexio and there is a custom XInput driver available for them in the source repository.

			== Troubleshooting ==

			Symptom: mouse cursor on the touch panel is flying around without any touch input.
			Resolution: Remove power to the touch panel and disconnect any USB cables, then plug the touch panel and USB cables back in.

	==Requirements==		==Requirements==

Dr jesus at 20:41, 19 January 2011

2011-01-19T20:41:16Z

← Older revision		Revision as of 13:41, 19 January 2011
Line 1:		Line 1:
	A bunch of folks worked on getting the touch panels working. Then another bunch of folks wanted to setup some sort of crazy control Noisebridge in case of a fire thing with it, [[SCADA]].		A bunch of folks worked on getting the touch panels working. Then another bunch of folks wanted to setup some sort of crazy control Noisebridge in case of a fire thing with it, [[SCADA]].

	The system that runs the touchpanel laptop ~~(thinkpad)~~ by the door (172.30.0.31) is required for opengate-www and opengate scripts to work. It is connected by parallel port to a relay which is linked into the door buzzer system.		The system that runs the touchpanel laptop by the door (172.30.0.31) is required for opengate-www and opengate scripts to work. It is connected by parallel port to a relay which is linked into the door buzzer system.

	This laptop runs uses PXE boot and an image from a tftp server on [[Stallion]] to run{{verify}}. It will not boot without network and this server on the remote system.		This laptop runs uses PXE boot and an image from a tftp server on [[Stallion]] to run{{verify}}. It will not boot without network and this server on the remote system.

	Currently the boot image for the panel starts up linux, runs Iceweasel full screen and points to a URL on [[Pony]]. There's a neat extensible interface that provides information and control regarding things we currently have in the space.		Currently the boot image for the panel starts up linux, runs Iceweasel full screen and points to a URL on [[Pony]]. There's a neat extensible interface that provides information and control regarding things we currently have in the space.

			There are 10x [http://www.parkytowers.me.uk/thin/Wyse3150SE/index.shtml Wyse 3150SE] thin clients available to drive the touch panels. The touch panels are made by iNexio and there is a custom XInput driver available for them in the source repository.

	==Requirements==		==Requirements==

Dr jesus: /* Build Procedures */

2011-01-19T20:34:09Z

Build Procedures

← Older revision		Revision as of 13:34, 19 January 2011
Line 67:		Line 67:
	=Build Procedures=		=Build Procedures=

	* Log into stallion and make changes to the files in /netboot/config.		The netboot environment is just debian-live. If you don't read [http://live.debian.net/manual/en/html/index.html the manual] you're likely to break something by accident. It's better to do development on your local machine using qemu and a copy of the config tree before executing the procedure below to push it out.

			* Log into stallion and make the changes you want to the files in /netboot/config as root.
			* cd /netboot/config
	* rm -rf binary* cache chroot		* rm -rf binary* cache chroot
	* sudo lh_build --force		* sudo lh_build --force
	* Back up the contents of /srv/debian-live		* Back up the contents of /srv/debian-live
			* '''Test your image''', see the manual for how to set up a test environment. It's simpler than you think.
	* If everything worked, move /netboot/binary/* and /netboot/tftpboot to /srv/debian-live		* If everything worked, move /netboot/binary/* and /netboot/tftpboot to /srv/debian-live
	* Reboot ~~all~~ the ~~netbooted~~ machines		* Reboot one of the lesser used netboot machines and do a sanity check, make sure your changes aren't causing the machines to run out of memory and invoke the OOM killer.
	* If ~~the results worked~~, do a hg commit in /netboot/config.		* Reboot the rest of the machines if you're happy.
			* If nothing breaks after a while, do a hg commit in /netboot/config.

SpammerHellDontDelete at 08:51, 12 January 2011

2011-01-12T08:51:41Z

← Older revision		Revision as of 01:51, 12 January 2011
Line 64:		Line 64:
	* http://cims.nyu.edu/~stucchio/software/djpirate/index.html		* http://cims.nyu.edu/~stucchio/software/djpirate/index.html
	* http://sourceforge.net/projects/mmpd/		* http://sourceforge.net/projects/mmpd/

			=Build Procedures=

			* Log into stallion and make changes to the files in /netboot/config.
			* rm -rf binary* cache chroot
			* sudo lh_build --force
			* Back up the contents of /srv/debian-live
			* If everything worked, move /netboot/binary/* and /netboot/tftpboot to /srv/debian-live
			* Reboot all the netbooted machines
			* If the results worked, do a hg commit in /netboot/config.

SpammerHellDontDelete: update current status of touch panels

2010-07-13T19:36:31Z

update current status of touch panels

← Older revision		Revision as of 12:36, 13 July 2010
Line 1:		Line 1:
	A bunch of folks worked on getting the touch panels working. Then another bunch of folks wanted to setup some sort of crazy control Noisebridge in case of a fire thing with it, [[SCADA]].		A bunch of folks worked on getting the touch panels working. Then another bunch of folks wanted to setup some sort of crazy control Noisebridge in case of a fire thing with it, [[SCADA]].

	~~Fast forward~~ a ~~few months,~~ the ~~touch panels really haven't gotten that much use out of them~~. Currently the boot image for the panel starts up linux, runs ~~Iceweasle~~ full screen and points to a URL on [[Pony]]. ~~All that~~'s ~~left is whipping some HTML together to make~~ a neat interface that provides information and control regarding things we currently have in the space.		The system that runs the touchpanel laptop (thinkpad) by the door (172.30.0.31) is required for opengate-www and opengate scripts to work. It is connected by parallel port to a relay which is linked into the door buzzer system.

			This laptop runs uses PXE boot and an image from a tftp server on [[Stallion]] to run{{verify}}. It will not boot without network and this server on the remote system.

			Currently the boot image for the panel starts up linux, runs Iceweasel full screen and points to a URL on [[Pony]]. There's a neat extensible interface that provides information and control regarding things we currently have in the space.

	==Requirements==		==Requirements==

Schoen: /* Back end */

2010-02-24T04:53:39Z

Back end

← Older revision		Revision as of 21:53, 23 February 2010
Line 9:		Line 9:

	===Back end===		===Back end===
	* ~~Apatche~~! Web apps!		* Apache! Web apps!
	** Everyone can write web pages!		** Everyone can write web pages!

Rubin110 at 00:56, 21 February 2010

2010-02-21T00:56:22Z

← Older revision		Revision as of 17:56, 20 February 2010
Line 46:		Line 46:
	* Scroll bars are going to be tricky		* Scroll bars are going to be tricky
	* Navigating to pages outside of the panel site might lead to the browser getting into a weird state. The dumb fix is to kill and restart the browser session every once in a while (3 hours sounds good).		* Navigating to pages outside of the panel site might lead to the browser getting into a weird state. The dumb fix is to kill and restart the browser session every once in a while (3 hours sounds good).

			==Installed Plugins==
			* Refresh2
			* autohide
			* Grab and Drag

	==Jukebox interfaces==		==Jukebox interfaces==

Rubin110 at 21:58, 18 February 2010

2010-02-18T21:58:41Z

← Older revision		Revision as of 14:58, 18 February 2010
Line 9:		Line 9:

	===Back end===		===Back end===
	* Web apps!		* Apatche! Web apps!
	* Everyone can write web pages!		** Everyone can write web pages!

	===Functionality===		===Functionality===