User:Mschmick - Revision history

Mschmick: Undo revision 64908 by DetailOriented (talk)

2018-02-13T05:27:51Z

Undo revision 64908 by DetailOriented (talk)

← Older revision		Revision as of 22:27, 12 February 2018
Line 1:		Line 1:
	~~[[File:DetailOriented.jpg]]~~
	Hi, Mark here. I'm building a robot for drones: http://www.flyingchair.co (prototype stage). Email me [mailto:mark@flyingchair.co here].		Hi, Mark here. I'm building a robot for drones: http://www.flyingchair.co (prototype stage). Email me [mailto:mark@flyingchair.co here].

DetailOriented at 05:08, 13 February 2018

2018-02-13T05:08:36Z

← Older revision		Revision as of 22:08, 12 February 2018
Line 1:		Line 1:
			[[File:DetailOriented.jpg]]
	Hi, Mark here. I'm building a robot for drones: http://www.flyingchair.co (prototype stage). Email me [mailto:mark@flyingchair.co here].		Hi, Mark here. I'm building a robot for drones: http://www.flyingchair.co (prototype stage). Email me [mailto:mark@flyingchair.co here].

Mschmick at 22:48, 12 February 2018

2018-02-12T22:48:32Z

← Older revision		Revision as of 15:48, 12 February 2018
Line 5:		Line 5:
	----		----

	'''''I'm building a robot called Birdhouse.''''' ~~Its~~ a ~~smart~~ launchpad for consumer drones like the Phantom ~~or Inspire, letting you remotely shelter, charge and fly~~. It looks like a breadbox (shelter / charge), and opens to a flight deck (launch / fly / land). In this talk I'll discuss the software stack I'm running since this is my first robot and I'm probably doing it wrong. Anyway, ~~this is~~ '''''one''''' non-ROS approach and I'm open to suggestions!		'''''I'm building a robot called Birdhouse,''''' a remote telepresence launchpad for consumer drones like the Phantom. It looks like a breadbox (shelter / charge), and opens to a flight deck (launch / fly / land). In this talk I'll discuss the software stack I'm running since this is my first robot and I'm probably doing it wrong. Anyway, here's '''''one''''' non-ROS approach and I'm open to suggestions!

	I call Birdhouse a "robot" since it ''does'' run an autonomous event loop (no human UI):		While it doesn't walk or fly, I call Birdhouse a "robot" since it '''''does''''' run an autonomous event loop (no human UI):

	# gather data from sensors and telemetry		# gather data from sensors and telemetry

Mschmick at 21:16, 9 February 2018

2018-02-09T21:16:46Z

← Older revision		Revision as of 14:16, 9 February 2018
Line 25:		Line 25:
	* serve web and REST requests (http)		* serve web and REST requests (http)

	The software architecture I'm proposing draws from a ~~variety~~ of OSS projects. It provides system services for general robotics like low-to-zero latency and high concurrency. On top of that I'm implementing some abstractions for dev-stage robotics:		The software architecture I'm proposing draws from a number of OSS projects. It provides system services for general robotics like low-to-zero latency and high concurrency. On top of that I'm implementing some abstractions for dev-stage robotics:

	* HAL (hardware abstraction library)		* HAL (hardware abstraction library)

Mschmick at 21:16, 9 February 2018

2018-02-09T21:16:00Z

← Older revision		Revision as of 14:16, 9 February 2018
Line 30:		Line 30:
	* Virtual clock		* Virtual clock
	* RESTful hardware singleton		* RESTful hardware singleton

			References: Python, [https://www.djangoproject.com Django], [http://www.django-rest-framework.org Django Rest Framework] (DRF), [http://django-q.readthedocs.io/en/latest/ Django Q] / [https://channels.readthedocs.io/en/latest/ Channels], [http://zeromq.org ZeroMQ], [https://www.nginx.com/resources/wiki/ NGINX], [http://uwsgi-docs.readthedocs.io/en/latest/ uWSGI]

Mschmick at 19:55, 9 February 2018

2018-02-09T19:55:16Z

← Older revision		Revision as of 12:55, 9 February 2018
Line 25:		Line 25:
	* serve web and REST requests (http)		* serve web and REST requests (http)

	The software architecture I'm proposing draws from a variety of OSS projects. It provides system services for general robotics like low-to-zero latency and high concurrency. On top of that I'm implementing some abstractions ~~particularly useful~~ for dev-stage robotics:		The software architecture I'm proposing draws from a variety of OSS projects. It provides system services for general robotics like low-to-zero latency and high concurrency. On top of that I'm implementing some abstractions for dev-stage robotics:

	* HAL (hardware abstraction library)		* HAL (hardware abstraction library)
	* Virtual clock		* Virtual clock
	* RESTful hardware singleton		* RESTful hardware singleton

Mschmick at 19:53, 9 February 2018

2018-02-09T19:53:12Z

← Older revision		Revision as of 12:53, 9 February 2018
Line 1:		Line 1:
	Hi, Mark here. I'm building a robot for drones: http://www.flyingchair.co (prototype stage).		Hi, Mark here. I'm building a robot for drones: http://www.flyingchair.co (prototype stage). Email me [mailto:mark@flyingchair.co here].

	Here's a summary of the '''RESTful Robots''' 5MoF talk I'm giving on Thur 2/15. If you have any suggestions or concentrations please let me know.		Here's a summary of the '''RESTful Robots''' 5MoF talk I'm giving on Thur 2/15. If you have any suggestions or concentrations please let me know.

Mschmick at 19:35, 9 February 2018

2018-02-09T19:35:38Z

← Older revision		Revision as of 12:35, 9 February 2018
Line 1:		Line 1:
	Hi, Mark here. I'm building a robot for drones: http://www.flyingchair.co (prototype stage).		Hi, Mark here. I'm building a robot for drones: http://www.flyingchair.co (prototype stage).

	Here's a summary of the 5MoF talk I'm ~~preparing for~~ Thur 2/15. If you have any suggestions or concentrations please let me know.		Here's a summary of the '''RESTful Robots''' 5MoF talk I'm giving on Thur 2/15. If you have any suggestions or concentrations please let me know.

	----		----

Mschmick at 18:47, 9 February 2018

2018-02-09T18:47:23Z

← Older revision		Revision as of 11:47, 9 February 2018
Line 5:		Line 5:
	----		----

	'''''I'm building a robot ~~for drones~~ called Birdhouse.''''' Its a smart launchpad for ~~commodity models~~ like the Phantom or Inspire, letting you remotely shelter, charge and fly. It looks like a breadbox (shelter/charge), and opens to a flight deck (launch/fly/land). In this talk I'~~d like to detail~~ the software stack I'm running since this is my first robot and I'm probably doing it wrong. Anyway, this is '''''one''''' non-ROS approach and I'm open to suggestions.		'''''I'm building a robot called Birdhouse.''''' Its a smart launchpad for consumer drones like the Phantom or Inspire, letting you remotely shelter, charge and fly. It looks like a breadbox (shelter / charge), and opens to a flight deck (launch / fly / land). In this talk I'll discuss the software stack I'm running since this is my first robot and I'm probably doing it wrong. Anyway, this is '''''one''''' non-ROS approach and I'm open to suggestions!

	I call Birdhouse a "robot" since it ''does'' run an autonomous event loop (no human UI):		I call Birdhouse a "robot" since it ''does'' run an autonomous event loop (no human UI):
Line 13:		Line 13:
	# run actuators, etc to change state		# run actuators, etc to change state

	To minimize pilot loading, ~~the~~ loop runs whenever props are spinning i.e. the pilot is piloting. It's a worst-case scenario and consequently a ~~good basis~~ for system requirements. Consider the ~~case below~~ of an outbound drone ~~that breaches~~ a departure geofence, ~~closing~~ Birdhouse ~~until you return.~~		''To minimize pilot loading, this loop runs whenever props are spinning '''i.e. the pilot is piloting.''''' It's a worst-case scenario and consequently a best-case for system requirements. Consider the scenario of an outbound drone breaching a departure geofence, signaling Birdhouse to close:

	* stream LOS video (RasPi cam, mplayer)		* stream LOS (line-of-sight) video (RasPi cam, mplayer)
	* ingest drone telemetry @~~50Hz~~		* ingest drone telemetry @50 Hz
	* ~~down-sample~~ to Birdhouse @~~5Hz~~ (REST updates)		* downsample to Birdhouse @5 Hz (REST updates)
	* read sensors: light, weather, audio, video (~~0MQ~~ pub/sub)		* read sensors: light, weather, audio, video (ZeroMQ pub/sub)
	* logic & logging		* logic & logging (e.g. waypoint math for LOS aiming and geofence detection)
	* ~~track~~ LOS camera on drone		* re-aim LOS camera at drone
	* run "close" sequence (5X motors, lights)		* run "close" sequence (5X motors, lights)
	* serve file from network share (smb)		* serve file from network share (smb)
	* serve web and REST requests (http)		* serve web and REST requests (http)

	The software architecture I'm proposing draws from a variety of OSS projects. It provides system services for general robotics like low-to-zero latency and high concurrency. On top of that I'~~ve implemented~~ some abstractions ~~that are~~ particularly useful for dev-stage robotics:		The software architecture I'm proposing draws from a variety of OSS projects. It provides system services for general robotics like low-to-zero latency and high concurrency. On top of that I'm implementing some abstractions particularly useful for dev-stage robotics:

	* HAL (hardware abstraction library)		* HAL (hardware abstraction library)
	* Virtual clock		* Virtual clock
	* RESTful hardware singleton		* RESTful hardware singleton

Mschmick at 01:05, 8 February 2018

2018-02-08T01:05:48Z

← Older revision		Revision as of 18:05, 7 February 2018
Line 5:		Line 5:
	----		----

	'''''I'm building a robot for drones called Birdhouse.''''' Its a smart launchpad for commodity models like the Phantom or Inspire, letting you remotely shelter, charge and fly. It looks like a breadbox (shelter/charge), and opens to a flight deck (launch/fly/land). In this talk I'd like to detail the software stack I'm running since this is my first robot and I'm probably doing it wrong. Anyway, this is ~~the~~ non-ROS ~~way I'm doing it but~~ I'm open to suggestions.		'''''I'm building a robot for drones called Birdhouse.''''' Its a smart launchpad for commodity models like the Phantom or Inspire, letting you remotely shelter, charge and fly. It looks like a breadbox (shelter/charge), and opens to a flight deck (launch/fly/land). In this talk I'd like to detail the software stack I'm running since this is my first robot and I'm probably doing it wrong. Anyway, this is '''''one''''' non-ROS approach and I'm open to suggestions.

	I call Birdhouse a "robot" since it does run an autonomous event loop (no human UI):		I call Birdhouse a "robot" since it ''does'' run an autonomous event loop (no human UI):

	# gather data from sensors and telemetry		# gather data from sensors and telemetry