Noisebridge - User contributions [en]

5MoF/2018/06 21

2018-06-22T02:09:34Z

Mschmick:

[[Category:5MoF]]

<big><big>5MoF - June 21, 2018 8:00pm</big></big>

<big>EXPERIMENTAL LIVE Simulcast with toorcamp!</big>

Put your name and title of your presentation - additionally a link if anyone wants to learn more.

'''Optionally include contact details such as a user page.'''

0. [[User:Ⅹ|Ⅹ]] -- Is this thing on (LIVE from [https://toorcamp.toorcon.net/ toorcamp]) **

1. Don on Shutterfire

2. Step on Power Harvesting Challenge & Workshop

3. Amplifying Activism with Pursuance - @elimisteve

4. Custom gears with a 5-axis CNC - mschmick

5.

6.

7.

8.

9.

** pending technical difficulties

5MoF/2018/02 15

2018-02-13T05:36:07Z

Mschmick: Undo revision 64906 by DetailOriented (talk)

[[Category:5MoF]]

<big><big>5MoF - February 15, 2018 (8:00pm)</big></big>

Put your name and title of your presentation - additionally a link if anyone wants to learn more.

'''Please also include contact details so that organisers can notify you in case the event needs to be canceled or postponed. A user page with details suffices.'''

1. Lamina - Portable power supplies, more info at [[https://blog.kaibots.com/2017/07/17/new-product-announcement/ Blog]]

3. Patrick (xcorr on slack) - A very NoiseBridge proposal

2. Captain Morgan - Any color button

4. mschmick - [[User:Mschmick|RESTful Robots]]

5. Henner - Fun with Glow-in-the-Dark stuff

6.

7.

8.

9.

10.

User:Mschmick

2018-02-13T05:27:51Z

Mschmick: Undo revision 64908 by DetailOriented (talk)

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.

----

'''''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!

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
# apply realtime logic
# run actuators, etc to change state

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

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)
* Virtual clock
* 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]

User:Mschmick

2018-02-12T22:48:32Z

Mschmick:

User:Mschmick

2018-02-09T21:16:46Z

Mschmick:

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.

----

'''''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):

# gather data from sensors and telemetry
# apply realtime logic
# run actuators, etc to change state

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

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)
* Virtual clock
* 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]

User:Mschmick

2018-02-09T21:16:00Z

Mschmick:

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.

----

'''''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):

# gather data from sensors and telemetry
# apply realtime logic
# run actuators, etc to change state

''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 (line-of-sight) video (RasPi cam, mplayer)
* ingest drone telemetry @50 Hz
* downsample to Birdhouse @5 Hz (REST updates)
* read sensors: light, weather, audio, video (ZeroMQ pub/sub)
* logic & logging (e.g. waypoint math for LOS aiming and geofence detection)
* re-aim LOS camera at drone
* run "close" sequence (5X motors, lights)
* serve file from network share (smb)
* 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:

* HAL (hardware abstraction library)
* Virtual clock
* 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]

User:Mschmick

2018-02-09T19:55:16Z

Mschmick:

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.

----

'''''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):

# gather data from sensors and telemetry
# apply realtime logic
# run actuators, etc to change state

''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 (line-of-sight) video (RasPi cam, mplayer)
* ingest drone telemetry @50 Hz
* downsample to Birdhouse @5 Hz (REST updates)
* read sensors: light, weather, audio, video (ZeroMQ pub/sub)
* logic & logging (e.g. waypoint math for LOS aiming and geofence detection)
* re-aim LOS camera at drone
* run "close" sequence (5X motors, lights)
* serve file from network share (smb)
* 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:

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

User:Mschmick

2018-02-09T19:53:12Z

Mschmick:

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.

----

'''''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):

# gather data from sensors and telemetry
# apply realtime logic
# run actuators, etc to change state

''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 (line-of-sight) video (RasPi cam, mplayer)
* ingest drone telemetry @50 Hz
* downsample to Birdhouse @5 Hz (REST updates)
* read sensors: light, weather, audio, video (ZeroMQ pub/sub)
* logic & logging (e.g. waypoint math for LOS aiming and geofence detection)
* re-aim LOS camera at drone
* run "close" sequence (5X motors, lights)
* serve file from network share (smb)
* 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:

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

5MoF/2018/02 15

2018-02-09T19:43:56Z

Mschmick:

[[Category:5MoF]]

<big><big>5MoF - February 15, 2018 (8:00pm)</big></big>

Put your name and title of your presentation - additionally a link if anyone wants to learn more.

'''Please also include contact details so that organisers can notify you in case the event needs to be canceled or postponed. A user page with details suffices.'''

1. Lamina - Yasu

3. Patrick (xcorr on slack) - A very NoiseBridge proposal

2. Captain Morgan - Any color button

4. mschmick - [[User:Mschmick|RESTful Robots]]

5.

6.

7.

8.

9.

10.

User:Mschmick

2018-02-09T19:35:38Z

Mschmick:

Hi, Mark here. I'm building a robot for drones: http://www.flyingchair.co (prototype stage).

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.

----

'''''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):

# gather data from sensors and telemetry
# apply realtime logic
# run actuators, etc to change state

''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 (line-of-sight) video (RasPi cam, mplayer)
* ingest drone telemetry @50 Hz
* downsample to Birdhouse @5 Hz (REST updates)
* read sensors: light, weather, audio, video (ZeroMQ pub/sub)
* logic & logging (e.g. waypoint math for LOS aiming and geofence detection)
* re-aim LOS camera at drone
* run "close" sequence (5X motors, lights)
* serve file from network share (smb)
* 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:

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

User:Mschmick

2018-02-09T18:47:23Z

Mschmick:

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.

----

'''''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):

# gather data from sensors and telemetry
# apply realtime logic
# run actuators, etc to change state

''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 (line-of-sight) video (RasPi cam, mplayer)
* ingest drone telemetry @50 Hz
* downsample to Birdhouse @5 Hz (REST updates)
* read sensors: light, weather, audio, video (ZeroMQ pub/sub)
* logic & logging (e.g. waypoint math for LOS aiming and geofence detection)
* re-aim LOS camera at drone
* run "close" sequence (5X motors, lights)
* serve file from network share (smb)
* 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:

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

User:Mschmick

2018-02-08T01:05:48Z

Mschmick:

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.

----

'''''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):

# gather data from sensors and telemetry
# apply realtime logic
# 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.

* stream LOS video (RasPi cam, mplayer)
* ingest drone telemetry @50Hz
* down-sample to Birdhouse @5Hz (REST updates)
* read sensors: light, weather, audio, video (0MQ pub/sub)
* logic & logging
* track LOS camera on drone
* run "close" sequence (5X motors, lights)
* serve file from network share (smb)
* 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:

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

User:Mschmick

2018-02-08T00:30:07Z

Mschmick: Created page with "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 su..."

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.

----

'''''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 call Birdhouse a "robot" since it does run an autonomous event loop (no human UI):

# gather data from sensors and telemetry
# apply realtime logic
# 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.

* stream LOS video (RasPi cam, mplayer)
* ingest drone telemetry @50Hz
* down-sample to Birdhouse @5Hz (REST updates)
* read sensors: light, weather, audio, video (0MQ pub/sub)
* logic & logging
* track LOS camera on drone
* run "close" sequence (5X motors, lights)
* serve file from network share (smb)
* 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:

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

5MoF/2018/02 15

2018-02-07T18:12:57Z

Mschmick:

[[Category:5MoF]]

<big><big>5MoF - February 15, 2018 (8:00pm)</big></big>

Put your name and title of your presentation - additionally a link if anyone wants to learn more.

'''Please also include contact details so that organisers can notify you in case the event needs to be canceled or postponed. A user page with details suffices.'''

1. Lamina - Yasu

3. Patrick (xcorr on slack) - A very NoiseBridge proposal

2. Captain Morgan - Any color button

4. mschmick - RESTful Robots

5.

6.

7.

8.

9.

10.

5MoF/2018/01 18

2018-01-18T11:39:04Z

Mschmick:

[[Category:5MoF]]

Put your name and title of your presentation - additionally a link if anyone wants to learn more.

'''Please also include contact details so that organisers can notify you in case the event needs to be canceled or postponed. A user page with details suffices.'''

1. [[SPIKE BLOK+]] When outlets attack! - [[User:Ⅹ|Ⅹ]]

3. Any Color Button - morgan

2. Lab Bio - rikke

4. Leela Maps - Leela

5. Ruth Grace Wong -- basics of knitwear manufacturing (ruthgrace on slack and my full name at gmail.com for email)

6. Zach R. -- [[Macbook / Apple Logic Board Repairs with a Fuckin' Microscope]]. (revoltrightnow [a t ] g ma yl)

7. Decentralized AI + Summit -- Dang! @dpg

8. Super Massive Biodynamic Quantum Computing at the World's Fair / Maker Fair - Leo Madrid

9. Bug Farming - Tequila Ray Snorkel (slack by same name) and ?

10. Lee Azzarello - Making music with your computer and SuperCollider

Alt.

Alt.

Alt.