=Current Projects=

I am developing a [http://opensourceecology.org/wiki/OSE_Network_Plan_2014 network solution] to reduce latency issues when accessing project-critical resources online.

=Todo=
# Research localized file storage for Factor e Farm

=Friday April 4, 2014 - Social Media=

Today, I'm coordinating Marcin's AmA on Reddit. [http://www.reddit.com/r/OpenSourceEcology/comments/226smo/marcin_jakubowski_founder_of_open_source_ecology/ I have already begun promoting it here.] I will be using the following image to provide proof.

[[File:MarcinAmASelfie.png]]

=Thursday March 27, 2014 - Social Media=

I began planning Marcin's IAmA. It is tentatively scheduled for Friday, April 4, but I have asked Marcin to move it up a day to Thursday. As of this moment I am awaiting his response on the matter. I put together the description that will be used for visitors to the AmA. [[File:AMADescription.odt]]

=Wednesday March 26, 2014 - Social Media=

I updated the [http://www.reddit.com/r/OpenSourceEcology/ OSE Subreddit] with a number of links on the sidebar. I am going to begin posting content to the subreddit on a regular basis in an attempt to revitalize the community. The content will be gathered from the OSE blog, wiki, facebook page, and website, and will be used to promote the work being done by the organization.

=Thursday March 20, 2014 - OSE Network=
I've added some device set up rationale to [http://opensourceecology.org/wiki/OSE_Network_Plan_2014 my network plan for OSE]

=Wednesday March 19, 2014 - OSE Network=
I added some basic diagrams of the logical design for [http://opensourceecology.org/wiki/OSE_Network_Plan_2014 my network solution for OSE.] I also began adding a list of major obstacles facing this project.

=Tuesday March 18, 2014 - OSE Network=
I began work on [http://opensourceecology.org/wiki/OSE_Network_Plan_2014 a solution to OSE's network woes.] My next step is to plan the logical layout of the network. This will give me a much better understanding of hardware needs and how the wireless networks will be set up.

=Sat, March 15, 2014 - OSE Network=
I updated the [http://opensourceecology.org/wiki/OSE_Internet OSE Internet] page with the changes I made to the network while I was there, and emailed Marcin with the administration details for the network devices being used at Factor e Farm. From my work, I have discovered a method that could be used to provide a WiFi network to all locations and structures around the farm. I have begun researching how this could be deployed.

'''Internet Research'''

[http://internet.hughesnet.com/plans-and-pricing.html HughesNet] offers Satellite internet up to 15 Mbps, but has very low monthly data usage caps.

[http://www.bluefirebroadband.com/plans Blue Broadband] has a package that offers 6 Mbps for $125

This is all I can find for wireless internet services at the farm, and there are no other options for wired broadband.

'''Mesh Networking'''

[http://www.kcfreedom.net/ KC Freedom Network] is looking to grow a mesh network in Kansas City. It is still a very small project, but offers some potential for the future. Building a mesh network from KC would have some major challenges, and would require as many as 10 nodes to reach FeF.

It appears that getting faster speeds is not likely in the near future. This means the focus needs to be on making things more accessible over the LAN rather than relying on outside internet services.

=Thursday March 13, 2014 - OSE Network=
I spent the morning working on setting up a wireless bridge between the internet connection in the hut and the hab lab. I reconfigured the CenturyLink router/modem in the hut to release DHCP information every six hours to reduce the number of reserved addresses. It appears the router was trying to connect through the bridge using the address 192.168.0.254 which was already reserved on the Century Link modem by another device. It is likely that a specific IP address would need to be reserved for the TP-Link router on the Century Link modem.

I had issues getting the Tp-Link router set up as either a bridge or repeater and it was not appearing on the MAC access list of the Century Link modem in the hut. My suspision is the Linksys router is not properly relaying DHCP information between the Century Link modem and the TP-Link Router, but I don't have sufficient time availible to troubleshoot this issue further. Additionally, I'm not very familiar with the Tomato firmware that is installed on the device so I would need to research more about its operation in order to be capable of said troubleshooting. Currently, the TP-Link router is set to attempt a bridge to the HabLab network and to provide a LAN named HabLab2.

'''Update'''
I managed to configure the Linksys router to operate only as a switch and access point. The TP-Link router finally received an IP address from the Century Link router and I was able to communicate across their WiFi connection to the Internet.

=Wednesday March 12, 2014 - Soil Mixer=
Images of the soil mixer bucket v 1_1

[[File:SoilMixerBucket_v1_1.png|x200px]]

Soil Mixer Bucket v. 1_2

[[File:SoilMixerBucket_v1_2.png|x200px]]

=Tuesday March 11, 2014 - Soil Mixer=
Soil Mixer: I added a finger mount, lower mounting brackets, and began work on teeth for the front of the bucket. [[File:SoilMixer.skp]]

=Mon March 10, 2014=
I started designing the bucket for the soil mixer.
[[File:SoilMixer.skp]]

File:MarcinAmASelfie.png

2014-04-04T17:22:27Z

Benjamin Pearson:

2014-03-19T18:18:30Z

Benjamin Pearson:

OSE Network Plan 2014

2014-03-19T18:09:21Z

Benjamin Pearson:

OSE Network Plan 2014

2014-03-19T17:44:51Z

Benjamin Pearson:

OSE Network Plan 2014

2014-03-19T17:33:59Z

Benjamin Pearson:

Internet and Communications System

2014-03-19T00:19:20Z

Benjamin Pearson: /* Potential Solution */

=Live Video Feeds from OSE Workshops=
For future build workshops - including the Microhouse Workshop (April 18-23) and Brick Press Workshop (April 25-27) - we would like to involve remote collaborators in an immersive viewing experience. There are some limits with internet bandwidth and setup that make this a challenge. Yet this challenge is worth mastering, because OSE's One Day builds are exciting to see - and we want to push the limits of crowd collaboration. See, for example, what happened on December 18, 2012:

<html><iframe src="https://player.vimeo.com/video/56274521" width="500" height="281" frameborder="0" webkitAllowFullScreen mozallowfullscreen allowFullScreen></iframe> <p><a href="http://vimeo.com/56274521">Merry Christmas from OSE.</a> from <a href="http://vimeo.com/opensourceecology">Open Source Ecology</a> on <a href="http://vimeo.com">Vimeo</a>.</p></html>

==Issues==
Live Video Feeds from workshops are one way to generate further remote involvement in OSE's work. However, the issue is bandwidth. We currently have two 4Mb DSL lines at Factor e Farm, which are relatively stable - but when many people are using the system, it tends to bog down unexpectedly. Our immersion workshops require:

#Uplaods of pictures and videos in realtime to generate documentation
#Video link for Live Video Feeds.

The second part can be developed further into a platform where immersive, remote involvement can happen when a person at FeF walks around with a video camera, and lets remote viewers see what is going on at every step of a dynamic, parallel build process. Remote viewers could also provide feedback to the camera operator for camera angles and features to capture. Further, when the operator is highly skilled and informed about the project, an interesting narrative and documentary can be captured in realtime.

Key to success of this would be using the 2 dedicated internet lines for the immersion build events to the best of our capacity. This requires that we route both the internet lines to the workshop space. One is used for ongoing documentation - picture and video uploads - and the second one for the Live Video Feed narrative.

Keys to success in making this a great experience for a number of remote viewers are:

#Broadcast system that allows distribution to dozens of remote viewers in realtime
#Bandwidth being sufficient for crisp and clear video to be transmitted
#Content of the workshop being sufficiently rich and dynamic that the viewer finds significant value whenever s/he joins.
#The documentor/narrator at Factor e Farm being sufficiently informed that s/he is able to provide meaningful and captivating insights throughout the process
#Video recording for those who do not see the build in realtime

=Potential Solution=
I have begun outlining [http://opensourceecology.org/wiki/OSE_Network_Plan_2014 a plan to improve the network at FeF.]

=Links=
*[[OSE Internet]]

Internet and Communications System

2014-03-19T00:18:55Z

Benjamin Pearson: /* Potential Quality of Service (QoS) Solution */

=Live Video Feeds from OSE Workshops=
For future build workshops - including the Microhouse Workshop (April 18-23) and Brick Press Workshop (April 25-27) - we would like to involve remote collaborators in an immersive viewing experience. There are some limits with internet bandwidth and setup that make this a challenge. Yet this challenge is worth mastering, because OSE's One Day builds are exciting to see - and we want to push the limits of crowd collaboration. See, for example, what happened on December 18, 2012:

<html><iframe src="https://player.vimeo.com/video/56274521" width="500" height="281" frameborder="0" webkitAllowFullScreen mozallowfullscreen allowFullScreen></iframe> <p><a href="http://vimeo.com/56274521">Merry Christmas from OSE.</a> from <a href="http://vimeo.com/opensourceecology">Open Source Ecology</a> on <a href="http://vimeo.com">Vimeo</a>.</p></html>

==Issues==
Live Video Feeds from workshops are one way to generate further remote involvement in OSE's work. However, the issue is bandwidth. We currently have two 4Mb DSL lines at Factor e Farm, which are relatively stable - but when many people are using the system, it tends to bog down unexpectedly. Our immersion workshops require:

#Uplaods of pictures and videos in realtime to generate documentation
#Video link for Live Video Feeds.

The second part can be developed further into a platform where immersive, remote involvement can happen when a person at FeF walks around with a video camera, and lets remote viewers see what is going on at every step of a dynamic, parallel build process. Remote viewers could also provide feedback to the camera operator for camera angles and features to capture. Further, when the operator is highly skilled and informed about the project, an interesting narrative and documentary can be captured in realtime.

Key to success of this would be using the 2 dedicated internet lines for the immersion build events to the best of our capacity. This requires that we route both the internet lines to the workshop space. One is used for ongoing documentation - picture and video uploads - and the second one for the Live Video Feed narrative.

Keys to success in making this a great experience for a number of remote viewers are:

#Broadcast system that allows distribution to dozens of remote viewers in realtime
#Bandwidth being sufficient for crisp and clear video to be transmitted
#Content of the workshop being sufficiently rich and dynamic that the viewer finds significant value whenever s/he joins.
#The documentor/narrator at Factor e Farm being sufficiently informed that s/he is able to provide meaningful and captivating insights throughout the process
#Video recording for those who do not see the build in realtime

=Potential Solution=
I have begun outlining a plan to improve the network at FeF.

=Links=
*[[OSE Internet]]

Ben Lloyd Pearson Log

2014-03-19T00:01:49Z

Benjamin Pearson:

=Todo=
# Research localized file storage for Factor e Farm

=Tuesday March 18, 2014 - OSE Network=
I began work on [http://opensourceecology.org/wiki/OSE_Network_Plan_2014 a solution to OSE's network woes.] My next step is to plan the logical layout of the network. This will give me a much better understanding of hardware needs and how the wireless networks will be set up.

=Sat, March 15, 2014 - OSE Network=
I updated the [http://opensourceecology.org/wiki/OSE_Internet OSE Internet] page with the changes I made to the network while I was there, and emailed Marcin with the administration details for the network devices being used at Factor e Farm. From my work, I have discovered a method that could be used to provide a WiFi network to all locations and structures around the farm. I have begun researching how this could be deployed.

'''Internet Research'''

[http://internet.hughesnet.com/plans-and-pricing.html HughesNet] offers Satellite internet up to 15 Mbps, but has very low monthly data usage caps.

[http://www.bluefirebroadband.com/plans Blue Broadband] has a package that offers 6 Mbps for $125

This is all I can find for wireless internet services at the farm, and there are no other options for wired broadband.

'''Mesh Networking'''

[http://www.kcfreedom.net/ KC Freedom Network] is looking to grow a mesh network in Kansas City. It is still a very small project, but offers some potential for the future. Building a mesh network from KC would have some major challenges, and would require as many as 10 nodes to reach FeF.

It appears that getting faster speeds is not likely in the near future. This means the focus needs to be on making things more accessible over the LAN rather than relying on outside internet services.

=Thursday March 13, 2014 - OSE Network=
I spent the morning working on setting up a wireless bridge between the internet connection in the hut and the hab lab. I reconfigured the CenturyLink router/modem in the hut to release DHCP information every six hours to reduce the number of reserved addresses. It appears the router was trying to connect through the bridge using the address 192.168.0.254 which was already reserved on the Century Link modem by another device. It is likely that a specific IP address would need to be reserved for the TP-Link router on the Century Link modem.

I had issues getting the Tp-Link router set up as either a bridge or repeater and it was not appearing on the MAC access list of the Century Link modem in the hut. My suspision is the Linksys router is not properly relaying DHCP information between the Century Link modem and the TP-Link Router, but I don't have sufficient time availible to troubleshoot this issue further. Additionally, I'm not very familiar with the Tomato firmware that is installed on the device so I would need to research more about its operation in order to be capable of said troubleshooting. Currently, the TP-Link router is set to attempt a bridge to the HabLab network and to provide a LAN named HabLab2.

'''Update'''
I managed to configure the Linksys router to operate only as a switch and access point. The TP-Link router finally received an IP address from the Century Link router and I was able to communicate across their WiFi connection to the Internet.

=Wednesday March 12, 2014 - Soil Mixer=
Images of the soil mixer bucket v 1_1

[[File:SoilMixerBucket_v1_1.png|x200px]]

Soil Mixer Bucket v. 1_2

[[File:SoilMixerBucket_v1_2.png|x200px]]

=Tuesday March 11, 2014 - Soil Mixer=
Soil Mixer: I added a finger mount, lower mounting brackets, and began work on teeth for the front of the bucket. [[File:SoilMixer.skp]]

=Mon March 10, 2014=
I started designing the bucket for the soil mixer.
[[File:SoilMixer.skp]]

OSE Network Plan 2014

2014-03-18T23:58:13Z

Benjamin Pearson:

2014-03-13T13:39:07Z

Benjamin Pearson:

Ben Lloyd Pearson Log

2014-03-12T17:57:48Z

Benjamin Pearson: /* Wednesday March 12, 2014 - Soil Mixer */

=Todo=
# Make a Log
# Research OwnCloud deployment with Google Drive sync

=Wednesday March 12, 2014 - Soil Mixer=
Images of the soil mixer bucket v 1_1

[[File:SoilMixerBucket_v1_1.png|x200px]]

Soil Mixer Bucket v. 1_2

[[File:SoilMixerBucket_v1_2.png|x200px]]

=Tuesday March 11, 2014 - Soil Mixer=
Soil Mixer: I added a finger mount, lower mounting brackets, and began work on teeth for the front of the bucket. [[File:SoilMixer.skp]]

=Mon March 10, 2014=
I started designing the bucket for the soil mixer.
[[File:SoilMixer.skp]]

Ben Lloyd Pearson Log

2014-03-12T17:55:27Z

Benjamin Pearson: /* Wednesday March 12, 2014 - Soil Mixer */

=Todo=
# Make a Log
# Research OwnCloud deployment with Google Drive sync

=Wednesday March 12, 2014 - Soil Mixer=
Images of the soil mixer bucket v 1_1 [[File:SoilMixerBucket_v1_1.png|x200px]]
Soil Mixer Bucket v. 1_2 [[File:SoilMixerBucket_v1_2.png|x200px]]

=Tuesday March 11, 2014 - Soil Mixer=
Soil Mixer: I added a finger mount, lower mounting brackets, and began work on teeth for the front of the bucket. [[File:SoilMixer.skp]]

=Mon March 10, 2014=
I started designing the bucket for the soil mixer.
[[File:SoilMixer.skp]]

File:SoilMixerBucket v1 2.png

2014-03-12T17:54:53Z

Benjamin Pearson: