Noisebridge - User contributions [en]

Meeting Notes 2018 08 07

2018-08-08T01:12:49Z

Juul:

[[Category:Meeting Notes]]

== Introductions (name, pronouns, deets) ==

== Participation ==

== Safespace ==

== Announcements ==

* (juul from sudoroom writes): Noisebridge and sudo room, Counter Culture Labs and the greater Omni Commons (and possibly BioCurious) have a cross-space ban policy. When someone is banned from a space for a violation of the safe space policy then they are auto-banned from the other spaces as well. Spaces can grant exceptions to one of these bans for their own space if they don't agree with the reasons for the ban. We have a mailing list that a few members from each space is part of which is used to communicate these bans, as well as incidents of concern that all spaces should be made aware of. Currently the people from noisebridge on this list seem to be no longer active and this resulted in a person on the noisebridge 86 list who was banned for safe space reasons showing up at sudo room and counter culture labs several times before someone noticed. Please contact marc@juul.io with the people who should be added to the safer spaces mailing list so we can avoid this in the future. These should be trusted noisebridge members who are actively co-organizing the space. -- juul

== Philanthropy ==

== Membership ==

== Consensus Items ==

== Discussion ==

== Money ==

Last meeting

2018-08-08T01:12:25Z

Juul: Redirected page to Meeting Notes 2018 07 31

#REDIRECT [[Meeting_Notes_2018_07_31]]

Last meeting

2018-08-08T01:11:44Z

Juul: Redirected page to Meeting Notes 2018 08 07

#REDIRECT [[Meeting_Notes_2018_08_07]]

Last meeting

2018-08-08T01:11:08Z

Juul: Redirected page to Meeting Notes 2018 07 31

#REDIRECT [[Meeting_Notes_2018_07_31]]

Meeting Notes 2018 08 07

2018-08-08T00:54:44Z

Juul: Created page with " == Introductions (name, pronouns, deets) == == Participation == == Safespace == == Announcements == * (juul from sudoroom writes): Noisebridge and sudo room, Counter Cult..."

== Introductions (name, pronouns, deets) ==

== Participation ==

== Safespace ==

== Announcements ==

* (juul from sudoroom writes): Noisebridge and sudo room, Counter Culture Labs and the greater Omni Commons (and possibly BioCurious) have a cross-space ban policy. When someone is banned from a space for a violation of the safe space policy then they are auto-banned from the other spaces as well. Spaces can grant exceptions to one of these bans for their own space if they don't agree with the reasons for the ban. We have a mailing list that a few members from each space is part of which is used to communicate these bans, as well as incidents of concern that all spaces should be made aware of. Currently the people from noisebridge on this list seem to be no longer active and this resulted in a person on the noisebridge 86 list who was banned for safe space reasons showing up at sudo room and counter culture labs several times before someone noticed. Please contact marc@juul.io with the people who should be added to the safer spaces mailing list so we can avoid this in the future. These should be trusted noisebridge members who are actively co-organizing the space. -- juul

== Philanthropy ==

== Membership ==

== Consensus Items ==

== Discussion ==

== Money ==

5MoF/2018/01 18

2018-01-19T03:42:02Z

Juul:

[[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 James Ricci (@James on Slack)

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

Alt. juul - [http://fread.ink/ fread.ink] - a free and open GNU/Linux distro for e-ink ebook readers

Alt.

Alt.

5MoF/2018/01 18

2018-01-19T03:41:43Z

Juul:

[[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 James Ricci (@James on Slack)

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

Alt. juul - [fread.ink http://fread.ink/] - a free and open GNU/Linux distro for e-ink ebook readers

Alt.

Alt.

User:Juul

2017-04-04T10:39:48Z

Juul: Created page with "See my [https://sudoroom.org/wiki/User:Juul sudo room page]"

See my [https://sudoroom.org/wiki/User:Juul sudo room page]

NoisebridgeChinaTrip7

2017-04-04T10:38:50Z

Juul: /* People interested in going on the Hacker Trip to China #7, 2017: */

= NOISEBRIDGE HACKER TRIP TO CHINA #7 -- Tentative Start Date: 11-October-2017, in (Shanghai? city TBD) -- Tentative End Date: 1-November-2017, in (Beijing? city TBD)=

[[File:HTTC2014WelcomeHackers.jpg|thumb|right|Trip #4 Welcome to China!, Beijing]]

[[File:KungFuHacking_Nov_2013.jpg|thumb|right|Trip #3 Kung Fu Hacking: Hackers In Residence Kickoff event at Tsinghua University, Beijing]]

[[File:petrochemical_university.jpg|thumb|right|Trip #2 Visit to Petrochemical Univeristy, Beijing]]

[[File:Beijing_Oct_2009.jpg|thumb|right|Trip #1 Jingshan Park, Beijing]]

[[File:Shenzhen_Oct_2016.jpg|thumb|right|Trip #5 Visit to Seeed Studio's factory, Shenzhen]]

[[File:Zhenzhou_Oct_2016.jpg|thumb|right|Trip #5 Presentations at Zhenzhou High School #2, Zhengzhou]]

== Previous Hacker Trips To China ==
::''This will be the 7th Noisebridge Hacker Trip To China.'' 
::'''''(The dates are set, but the itinerary is open to change.)'''''
::''In previous years' Hacker Trip To China, we've visited cities that currently have a hackerspace, visited my manufacturer, Seeed Studio, and other manufacturers. We also visited Tsinghua University, considered the most prestigious university in China, and other schools -- all of which have now starting hackerspaces. China continues to explode with hackerspaces! We also went to the International Exhibition of Inventions Kunshan (IEIK 2014), near Shanghai. And everywhere we went, we were shown around by local geeks, to see what they thought was interesting where they live. Also, wherever we went, those of us interested gave talks, presentations, workshops, and demos. In 2016 we gave presentations at NY University - Shanghai, DFRobot (an open hardware company in Shanghai), Shanghai Maker Carnival, Zhengzhou High School Number 2, "Second Generation and Start-ups" conference in Hangzhou.'' 

::''You can see info on the [[ChinaTrip|Hacker Trip To China 2009]],'' 
::''[[NoisebridgeChinaTrip2|Hacker Trip To China 2011]]'' 
::''[[NoisebridgeChinaTrip3|Hacker Trip To China 2013]]'' 
::''[[NoisebridgeChinaTrip4|Hacker Trip To China 2014]]'' 
::''[[NoisebridgeChinaTrip5|Hacker Trip To China 2015]]'' 
::''[[NoisebridgeChinaTrip6|Hacker Trip To China 2016]],'' 

::-- [[User:Maltman23|Mitch]].

== This year's Hacker Trip To China ==
'''When:''' Tentatively 11-October-2017 (Shanghai?) through tentatively 1-November-2017 (Beijing?).

'''Flight, transportation, and hotel Info''': We were each be on our own to book our own air fare to meet in our starting city (tentatively Shanghai) on 11-October (tentatively), and fly home from out ending city (tentatively Beijing) on 1-November (tentatively). Of course, you can decide to come and go as you please. 

I'll organized the itinerary and the hotels and other transport. I'll pay in advance for some of this, and you can pay me back when we're in China. 

'''Where:''' In each of the cities we will go to, we'll visit some of their local hackerspace(s), and will be shown around by local geeks to see what interested them where they live. We'll also have plenty of time to do "normal" (and spectacular) tourist things too! 

'''Here's some possible places we might visit, leaving plenty of room for the serendipity that makes our Hacker Trip To China truly unique and memorable:''' 
* We may start our trip by meeting in '''Shanghai''' on 11-October-2017. In Shanghai we will visit [http://www.etonnet.com/ my manufacturer (Etonnet)] that I have used for [http://www.tvbgone.com TV-B-Gone] remote controls and [http://www.neurodreamer.com NeuroDreamer] sleep masks, where we will all get to see how products are made, from start to finish, learning how manufacturing works. We will also visit [http://xinchejian.com/ XinCheJian] hackerspace in Shanghai. If there is another [http://www.shanghaimakercarnival.com/ Shanghai Maker Carnival] while we are in town, we will be welcomed there, and we will have a table where we can all show off our projects and give workshops (if you like). We can also visit companies started by hardware hacker geeks, such as [http://www.dfrobot.com/ DFRobot]. We can also visit the [http://www.flickr.com/photos/maltman23/4064240200/in/set-72157622640069902/ Shanghai electronics mall] (a smaller version of the famous electronics mall we will later visit in Shenzhen).
* We may go from Shanghai to '''Hong Kong''' and visit [http://www.dimsumlabs.com/ Dim Sum Labs] hackerspace. We'll also see lots of other cool stuff in Hong Kong. 
* Then we may go across the border to mainland China again, to '''Shenzhen''' to visit [http://www.chaihuo.org/ Chaihuo Makerspace], [http://www.szdiy.org/ SZDIY] hackerspace, [http://litchee.cn/en/ Litchee Lab], and a few other hackerspaces, some of which are real, and hundreds of which are brand new (this year) over-the-top bizarre government-started places where they want to create "the next Apple" (we won't visit them all!). If there is another [http://www.makerfaireshenzhen.com/english Maker Faire Shenzhen] while we are in town, we will be welcomed there, and will be given a booth where we can all show off our projects and give workshops (if you like). We will also visit [http://www.seeedstudio.com Seeed Studio] - the open source hardware company - to meet the cool folks there and to see their manufacturing facilities. We may meet with the founders of [http://dangerousprototypes.com/ Dangerous Prototypes] - another open source hardware company. We'll also visit other manufacturers, to see where all the things we use in our daily lives come from (such as springs, cables, PCBs, packaging, etc., etc.). Of course, we'll also visit the famous (and totally awesome!) [http://www.evilmadscientist.com/article.php/shenzhen/print Huaqiangbei electronics market] in Shenzhen (where, we may again be shown around by a professional buyer from Deal Extreme (dx.com). 
* We may then make our way to '''Beijing''' where we may visit [http://www.bjmakerspace.com/ Beijing Makerspace], and other hackerspaces. We'll also visit Tsinghua University, where they built the world's largest hackerspace last year, and where I've been hacker in residence. Beijing has lots and lots of way amazing stuff to visit and be a part of!

For most of us, our trip will end at the end of three weeks, as many people on our trip will fly home from our last city on (tentatively) 1-November-2017.

''I will probably be in Beijing, as hacker in residence at Tsinghua University for the 6 weeks preceding out Hacker Trip To China 2017. Everyone is welcome to join me in Beijing for any or all of this residency. (And, of course, everyone is free to arrive and leave whenever you like.) 
I will tentatively be flying home from Beijing on 2-November. ''

'''Cost:''' For the Hacker Trip To China 2016, I paid $1,997 total (for 4 weeks), including air fare from SF, food, lodging, transportation, and everything -- including some electronics stuff and some clothing that I bought. 
''As in past years, part of this year's trip may be paid for by Tsinghua University and other places that invite us to give presentations.''

'''#hashtag:''' [https://twitter.com/hashtag/httc2017 #httc2017]      (Hacker Trip To China 2017)

 
 

== Possible itinerary outline for Hacker Trip to China 7 ==

''Everyone is welcome to join me while I am hacker in residence at Tsinghua University from 31-August through 10-October.'' 
'''The start and end dates are set, but the rest of the itinerary is open to change:'''
''10-October-2017 -- '''Leave home''' for '''Shanghai''' (arrive in Shanghai on 11-October)''
''11-October-2016 -- We all tentatively meet in '''Shanghai''' -- hotel: Le Tour Traveler's Rest''
'''11-October to 17-October -- Shanghai'''
'''17-October to 19-October -- Hong Kong'''
'''19-October to 24-October -- Shenzhen'''
'''24-October to 28-October -- Beijing''' ''
''1-November-2016 -- '''fly home''' (arrive NA or EU on same day)''

 
 
 
 
 

== Photos from Hacker Trip To China 2016==
<gallery>
File:HTTC2016Shanghai.jpg
File:HTTC2016Zhenzhou.jpg
File:HTTC2016Shenzhen.jpg
File:HTTC2016Beijing.jpg
File:HTTC2016Hangzhou.jpg
File:HTTC2016Beijing2.jpg
</gallery>

Mitch's photos from [https://www.flickr.com/photos/maltman23/sets/72157672475058474/ Shanghai, Oct-2016] 
Mitch's photos from [https://www.flickr.com/photos/maltman23/sets/72157674645655612/ Zhengzhou, Oct-2016] 
Mitch's photos from [https://www.flickr.com/photos/maltman23/sets/72157676024748146/ Shenzhen, Oct-2016] 
Mitch's photos from [https://www.flickr.com/photos/maltman23/sets/72157676142107066/ Beijing, Oct-2016] 
Mitch's photos from [https://www.flickr.com/photos/maltman23/sets/72157676144570756/ Hangzhou, Oct-2016] 
Mitch's photos from [https://www.flickr.com/photos/maltman23/sets/72157672603805234/ Beijing Set 2, Oct-2016] 

[https://www.flickr.com/photos/maltman23/collections/72157674928976010/ Mitch's photos all in one place]

 
 
 
 

== Photos from Hacker Trip to China 2015==
<gallery>
File:HTTC2015HongKongNeon.jpg
File:HTTC2015ShenzhenFactory.jpg
File:HTTC2015ShanghaiTempleMall.jpg
File:HTTC2015BeijingDoor.jpg
File:HTTC2015HangzhouTemple.jpg
File:HTTC2015BeijingShop.jpg
File:HTTC2015SuzhouUmbrellas.jpg
</gallery>

Mitch's photos from [https://www.flickr.com/photos/maltman23/sets/72157659076735178 Hong Kong, Oct-2015] 
Mitch's photos from [https://www.flickr.com/photos/maltman23/sets/72157660026965949 Shenzhen, Oct-2015] 
Mitch's photos from [https://www.flickr.com/photos/maltman23/sets/72157660038275888 Shanghai, Oct-2015] 
Mitch's photos from [https://www.flickr.com/photos/maltman23/sets/72157658114137264 Beijing, Oct-2015] 
Mitch's photos from [https://www.flickr.com/photos/maltman23/albums/72157660424228042 YiWu & Hangzhou, Oct-2015] 
Mitch's photos from [https://www.flickr.com/photos/maltman23/albums/72157660650175925 Beijing Set 2, Oct-2015] 
Mitch's photos from [https://www.flickr.com/photos/maltman23/albums/72157658310336814 Shanghai & Suzhou, Oct-2015] 

[https://www.flickr.com/photos/maltman23/collections/72157660374807166/ Mitch's photos all in one place]

 
[https://picasaweb.google.com/dtharn/ChinaInOctober2015?feat=directlink Dave's photos]

 
Blake's photos:
* [https://www.flickr.com/photos/cwlcks/sets/72157662429341996 Hong Kong!]
* [https://www.flickr.com/photos/cwlcks/albums/72157660150285384 Shenzen!]
* [https://www.flickr.com/photos/cwlcks/albums/72157661790873029 Shanghai!]
* [https://www.flickr.com/photos/cwlcks/albums/72157660153522904 Beijing!]
 

Torrey's photos from [https://www.flickr.com/gp/torrey/Q840rT Hong Kong] 
Torrey's photos from [https://www.flickr.com/gp/torrey/yLo903 Shenzhen] 
Torrey's photos from [https://flic.kr/s/aHskqNiQeX Beijing] 
Torrey's photos from [https://flic.kr/s/aHskrE55NX Shanghai] 

 
 
 
 

== Photos from Hacker Trip to China 2014==
<gallery>
File:HTTC2014WelcomeHackers.jpg
File:HTTC20143Nod_b.jpg
File:HTTC2014AiWeiWei.jpg
File:HTTC2014BeijingLGBTcentre.jpg
File:HTTC2014Brooms.jpg
File:HTTC2014CableFactory.jpg
File:HTTC2014ChaiHuo.jpg
File:HTTC2014GiantSewing.jpg
File:HTTC2014Huaqianbei.jpg
File:HTTC2014IEIK2014.jpg
File:HTTC2014SeeedStudio.jpg
File:HTTC2014Shanghai.jpg
File:HTTC2014Tianjin.jpg
File:HTTC2014Tienanmen.jpg
File:HTTC2014TrainConvenienceStore.jpg
File:HTTC2014TsinghuaMakersDay.jpg
File:HTTC20143Nod.jpg
File:HTTC2014XinCheJian.jpg
</gallery>

Mitch's photos from [https://www.flickr.com/photos/maltman23/sets/72157646894397704/ Beijing, Nov-2014] 
Mitch's photos from [https://www.flickr.com/photos/maltman23/sets/72157648975298719/ Shanghai, Nov-2014] 
Mitch's photos from [https://www.flickr.com/photos/maltman23/sets/72157648981933060/ Shenzhen, Nov-2014] 
Mitch's photos from [https://www.flickr.com/photos/maltman23/sets/72157649396351315/ Kunshan, Nov-2014] 
Mitch's photos from [https://www.flickr.com/photos/maltman23/sets/72157649148594118/ Shanghai (2), Nov-2014] 
Mitch's photos from [https://www.flickr.com/photos/maltman23/sets/72157649146775640/ Beijing (2), Nov-2014] 
Mitch's photos from [https://www.flickr.com/photos/maltman23/sets/72157649146987360/ Tianjin, Nov-2014] 
Mitch's photos from [https://www.flickr.com/photos/maltman23/sets/72157647372474753/ Beijing (3), Nov-2014] 
Mitch's photos from [https://www.flickr.com/photos/maltman23/sets/72157649287546450/ Singapore, Dec-2014] 

== You will Need a Chinese Visa!! ==
To go to China, you needed to get a visa!

Everyone should get a multiple-entry Tourist L visa (if you only get a single-entry visa, you won't be able to go to Hong Kong).

* And to get a visa, you need to have a passport that is valid ''at least'' 12 months after you planned to fly away from China (so, e.g., if you are leaving China on 1-November-2017, then your passport needs to be valid through 31-October-2017). Your passport must also have at least ''one entirely blank page''.

* You also need:
** a printout of a filled-out [http://www.china-embassy.org/eng/visas/fd/W020130830801798289342.pdf Visa Application Form V. 2013 of the People's Republic of China] (after we have everything we need I'll email you my filled out form as an example to follow).
** a copy of the information pages of your passport.
** a copy of your most Chinese visa (if you have been to China before).
** one 2"x2" recent color photo (not a printout).
** a screenshot or printout of hotel reservation confirmation (I'll email this to you when I have this).
** a copy of your airline tickets (both to and from China).

* For US citizens, the visa cost $140 (much cheaper for other nationalities). Starting this year, US citizens can get a multiple-entry visa, good for 10 years. We should all apply for a Tourist L visa.

You can pay the fee by Visa, MasterCard, Money Order, Cashier's Check or Company Check. ''Cash or Personal checks are not acceptable.''

To get a visa, you can go to your local Chinese consulate. No appointment is required. You go in one day, and it will be ready for pick up 4 business days later. My experience is that it takes about an hour the first day, and takes only a few minutes to pick up the visa a few days later. (2 to 3 business-day and 1 business day/same-day express service is available for $20 or $30.) 
''NOTE: The Chinese consulates are all closed for holidays on: 27-30 January, 29-30 May, 30-May, 9-June, 4-July, 4-September, 2-October, 9-October and other dates: 
[http://www.chinaconsulatesf.org/eng/lszj/t1424287.htm 2017 Chinese Consulate Holiday Schedule]''
 
(Citizens of US and Europe ''do not'' need a separate visa for Hong Kong.)
 

= Previous Noisebridge China Trips =
''If you're curious about the previous Noisebridge China Trips, they have their own wiki pages:'' 
[[ChinaTrip|Hacker Trip To China 2009]] 
          That first Noisebridge China Trip was inspired by Bunny Huang's [http://www.evilmadscientist.com/article.php/shenzhen/print "geek tour"]. 
 
[[NoisebridgeChinaTrip2|Hacker Trip To China 2011]] 
 
[[NoisebridgeChinaTrip3|Hacker Trip to China 2013]]
 
[[NoisebridgeChinaTrip4|Hacker Trip to China 2014]]
 
[[NoisebridgeChinaTrip5|Hacker Trip to China 2015]]
 
[[NoisebridgeChinaTrip6|Hacker Trip to China 2016]]

--[[user: maltman23 | Mitch]].

= People interested in going on the Hacker Trip to China #7, 2017: =


'''Below is a list of people interested in going on this year's Hacker Trip To China.'''
 


'''You do not need to be a member of Noisebridge to go on this trip!'''
 

'''Please email me if you have any questions, or if you would like to meet up with us on the trip:''' 
''mitch *AT* CornfieldElectronics *DOT* com''

The trip is limited to 20 people total (including Mitch) 
-- the first 19 people (after Mitch) who are either there already, or who bought tickets to meet in our Trip's starting city (tentatively Shanghai) on or before 11-October-2017 are the people who are in this Trip        (which probably means flying away from home on or before 10-October) 


Note: Many people have gotten good deals on their plane fares (including me) with the help of my friend Vlad at:        [http://www.flystein.com/ Flystein] Feel free to email me, and I'll send your email to Vlad, who will be happy to help you with your flights.
 

{| style="color:green; background-color:#ffffcc;" cellpadding="10" cellspacing="0" border="1"
!
! Name
! Purchased flight?
! Flight info
|-
|1
|[[user: maltman23 | Mitch Altman]]
|align="center"|no
|Arrive: Beijing on (date TBD)
|-
|2
|[[user: keymistress | Gloria Chiang]]
|align="center"|no
|Arrive: 'Beijing on (date TBD)
|-
|3
|[[user:juul|Marc Juul]]
|align="center"|no
|Arrive: Beijing on (date TBD)
|-
|4
|''your name here''
|align="center"|no
|Arrive: ''your arrival date and city here''
|-
|5
|''your name here''
|align="center"|no
|Arrive: ''your arrival date and city here''
|-
|6
|''your name here''
|align="center"|no
|Arrive: ''your arrival date and city here''
|-
|7
|''your name here''
|align="center"|no
|Arrive: ''your arrival date and city here''
|-
|8
|''your name here''
|align="center"|no
|Arrive: ''your arrival date and city here''
|-
|9
|''your name here''
|align="center"|no
|Arrive: ''your arrival date and city here''
|-
|10
|''your name here''
|align="center"|no
|Arrive: ''your arrival date and city here''
|-
|11
|''your name here''
|align="center"|no
|Arrive: ''your arrival date and city here''
|-
|12
|''your name here''
|align="center"|no
|Arrive: ''your arrival date and city here''
|-
|13
|''your name here''
|align="center"|no
|Arrive: ''your arrival date and city here''
|-
|14
|''your name here''
|align="center"|no
|Arrive: ''your arrival date and city here''
|-
|15
|''your name here''
|align="center"|no
|Arrive: ''your arrival date and city here''
|-
|16
|''your name here''
|align="center"|no
|Arrive: ''your arrival date and city here''
|-
|17
|''your name here''
|align="center"|no
|Arrive: ''your arrival date and city here''
|-
|18
|''your name here''
|align="center"|no
|Arrive: ''your arrival date and city here''
|-
|19
|''your name here''
|align="center"|no
|Arrive: ''your arrival date and city here''
|-
|20
|''your name here''
|align="center"|no
|Arrive: ''your arrival date and city here''
|-
|}

[[Category:Travel]]
[[Category:Projects]]

Sparky

2013-12-02T14:00:21Z

Juul: /* Where projects are the units going to? */

== The donation ==
[[File:Sparky1.jpg|200px|thumb|right|A donated Meraki "Sparky" board]]
[[File:Sparky2.jpg|200px|thumb|right|Back of PCB]]
A bunch of Meraki Outdoor "Sparky" units were [https://www.noisebridge.net/pipermail/noisebridge-discuss/2013-November/040754.html donated to Noisebridge].

''"Built to withstand everything from hackers to extreme temperatures, water, sand, and dust."'' [https://web.archive.org/web/20090221170958/http://meraki.com/products_services/hardware/outdoor/]

MIT Article referring to a "SF Mesh" http://www.technologyreview.com/hack/410322/meraki-outdoor/

Old press release for Meraki's [https://meraki.cisco.com/blog/2008/09/free-the-net-san-francisco-makes-great-progress/ "Free The Net"] SF mesh

meraki.com
* Archived version of Outdoor
** https://web.archive.org/web/20090221170958/http://meraki.com/products_services/hardware/outdoor/
* Archived version of "Solar"
** https://web.archive.org/web/20090224095706/http://meraki.com/products_services/hardware/solar_overview

== Documentation ==

=== Specs ===

* Atheros AR2317@180Mhz
* 32 MB RAM
* 8 MB Flash
* 802.11B/G
* POE support
* 4.5-18V
[http://www.dd-wrt.com/wiki/index.php/Supported_Devices#Meraki Source]

==== Typical Coverage Radius ====
* Indoor: 150-250ft (50-80m)
* Outdoor: 500-1000ft (150-350m)
* Outdoor with high-gain antenna: 0.6-5mi (1-8km)

==== Radio ====
* 200 mW (23 dBm) peak transmission power*
* Enhanced receive sensitivity
* External RP-SMA connector
* 802.11 b/g (1 - 54 Mbps)
* 2 dBi omni-directional antenna included

==== Power ====
* 5 - 22 V DC
* Power Over Ethernet, 12 - 22 V (non 802.3af )
* Power consumption: 12 W max; 3 W typical
* 15 V/0.8 A DC power adapter included
* Power Over Ethernet injector included

==== Environment ====
* Operating temperature: 14° F – 122° F (-10° C – 50° C)
* IP - 66 environmental rating

==== Interfaces / Ports ====
* Two 10/100 Mbps auto-crossover Ethernet ports:
automatically detects PC or gateway operation
* Signal strength LED
* Headers for 3.3v Serial / GPIO

Source: Meraki Data Sheet [https://meraki.cisco.com/lib/pdf/meraki_datasheet_outdoor.pdf]

=== FCC Forms ===
* Ad Hoc Declaration: https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=855552
* Construction Photos - https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=855555
* Internal Photos - https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=855556
* RF Exposure - https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=855561
* Test Report 1 - https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=855563
* Test Report 2 - https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=855564
* Test Setup Photos - https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=855565
* User Manual - https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=855566

=== Manuals ===
* https://meraki.cisco.com/lib/pdf/meraki_setup_outdoor.pdf

=== Components ===

* Hynix256M (16Mx16bit) SDRAM Memory "HY57V561620FTP-H" (U11) [http://www.datasheetdir.com/go-HYNIX-HY57V561620FTP.pdf]
* "SS54" (D2, D3, D4) [http://www.alldatasheet.com/datasheet-pdf/pdf/222984/HY/SS54.html]

=== Firmware ===

* [http://motescope.cs.berkeley.edu/meraki-default.php Stock] - commands, details
* [http://wiki.openwrt.org/oldwiki/openwrtdocs/hardware/meraki OpenWRT install details]
* [http://motescope.cs.berkeley.edu/meraki-openwrt.php OpenWRT Easyflash] - utilities for simple flashing of Meraki Mini (unknown compatibility with Outdoor)
* [https://dev.cloudtrax.com/projects/dev/wiki AP51-flash] flashing tool

== Flashing OpenWRT ==

Other Meraki routers have port 9000 open for telnet console connections for two seconds during bootup, but these boards do not. The router's RedBoot tries to load a .elf file via tftp during bootup. This file could contain a different RedBoot with tcp console enabled, but unfortunately I ([[User:Juul|Juul]] ([[User talk:Juul|talk]])) have not been able to get the built-in RedBoot to accept any .elf files (even ones compiled from Merakis RedBoot source code, which they have released). The files are only ever partially retrieved with no useful errors given on client or server.

This means that we have to use the 3.3v serial port on the routers to gain console access.

*[[User:Juul|Juul]] ([[User talk:Juul|talk]]) has written [https://github.com/sudomesh/merakiflasher a script to flash these routers using serial and ethernet].
:This is a work in progress but should be barely usable.

== Watchdog problems! ==

The hardware watchdog is enabled per default and reboots the board every 5 minutes. This is why it takes 20+ minutes and four reboots to flash the router.

OpenWRT and Linux's watchdog support for the AR2317 chipset apparently is not functioning per default in OpenWRT Attitude Adjustment (possibly not in any version). This means the router will still reboot every 5 minutes after you flash with OpenWRT.

The watchdog support is supposed to work like so:

*Kernel driver creates /dev/watchdog as interfaces between hardware watchdog and userland
*watchdog daemon which is part of busybox writes null characters to /dev/watchdog periodically

The kernel code to support the watchdog is in linux-3.3.8/drivers/watchdog/ar2315-wtd.c and the memory mapped register addresses should be the same for the AR2317 as for the AR2317. The code appears to be compiled into OpenWRT Attitude Adjustment. Perhaps it is not loading because it only activates for AR2315 hardware? or perhaps some flag needs to be set at compile time?

== Startup ==
via serial port
<pre>
Ethernet eth0: MAC address 00:18:0a:50:00:00
IP: 192.168.84.1/255.255.255.0, Gateway: 0.0.0.0
Default server: 192.168.84.9

RedBoot(tm) bootstrap and debug environment [ROMRAM]
Non-certified release, version v1.3.0 - built 10:45:15, Aug 27 2007

Copyright (C) 2000, 2001, 2002, 2003, 2004 Red Hat, Inc.

Board: ap61
RAM: 0x80000000-0x82000000, [0x8003ddd0-0x80fe1000] available
FLASH: 0xa8000000 - 0xa87e0000, 128 blocks of 0x00010000 bytes each.
== Executing boot script in 2.000 seconds - enter ^C to abort
RedBoot> check_mac
** Error: Illegal command: "check_mac"
RedBoot> load art_ap51.elf
Using default protocol (TFTP)
__udp_sendto: Can't find address of server
Can't load 'art_ap51.elf': some sort of network error
RedBoot> go
No entry point known - aborted
RedBoot> fis load stage2
RedBoot> exec
Now booting linux kernel:
Base address 0x80030000 Entry 0x80100000
Cmdline :
starting stage2
reading flash at 0xa8150000 - 0xa842f859.....................done
Calculating CRC... 0xd1bfe2e4 - matches
decompressing....................done
starting linux
[ 0.000] Linux version 2.6.16.16-meraki-mini (roby@roby) (gcc version 3.4.6 (OpenWrt-2.0)) #2 Mon Apr 21 14:09:33 PDT 2008
[ 0.000] CPU revision is: 00019064
[ 0.000] Determined physical RAM map:
[ 0.000] memory: 02000000 @ 00000000 (usable)
[ 0.000] Built 1 zonelists
[ 0.000] Kernel command line:
[ 0.000] Primary instruction cache 16kB, physically tagged, 4-way, linesize 16 bytes.
[ 0.000] Primary data cache 16kB, 4-way, linesize 16 bytes.
[ 0.000] Synthesized TLB refill handler (20 instructions).
[ 0.000] Synthesized TLB load handler fastpath (32 instructions).
[ 0.000] Synthesized TLB store handler fastpath (32 instructions).
[ 0.000] Synthesized TLB modify handler fastpath (31 instructions).
[ 0.000] PID hash table entries: 256 (order: 8, 4096 bytes)
[ 0.000] Using 92.000 MHz high precision timer.
[ 0.001] Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
[ 0.004] Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
[ 0.011] Memory: 20280k/32768k available (2038k kernel code, 12472k reserved, 401k data, 9328k init, 0k highmem)
[ 0.031] Mount-cache hash table entries: 512
[ 0.034] Checking for 'wait' instruction... available.
[ 0.037] unpacking initramfs....done
[ 0.769] NET: Registered protocol family 16
[ 0.828] Algorithmics/MIPS FPU Emulator v1.5
[ 2.269] JFFS2 version 2.2. (NAND) (C) 2001-2003 Red Hat, Inc.
[ 2.270] Initializing Cryptographic API
[ 2.271] io scheduler noop registered
[ 2.272] io scheduler anticipatory registered (default)
[ 2.274] io scheduler deadline registered
[ 2.275] io scheduler cfq registered
[ 2.300] watchdog hb: 90 ISR: 0x21 IMR: 0x8 WD : 0xa340fe12 WDC: 0x0
[ 2.305] ar2315_wdt_init using heartbeat 90 s cycles 3600000000
[ 2.306] watchdog hb: 90 ISR: 0x21 IMR: 0x88 WD : 0xd68d192e WDC: 0x0
[ 2.315] Serial: 8250/16550 driver $Revision: 1.90 $ 1 ports, IRQ sharing disabled
[ 2.320] serial8250: ttyS0 at MMIO 0xb1100003 (irq = 37) is a 16550A
[ 2.475] phyID=0x00071023
[ 2.476] Found ADM6996FC. phyID=0x00071023.
[ 2.539] eth0: Dropping NETIF_F_SG since no checksum feature.
[ 2.617] eth0: Atheros AR2313: 00:18:0a:50:00:00, irq 4
[ 2.619] eth1: Dropping NETIF_F_SG since no checksum feature.
[ 2.687] eth1: Atheros AR2313: 00:18:0a:50:00:00, irq 4
[ 2.767] tun: Universal TUN/TAP device driver, 1.6
[ 2.768] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
[ 2.846] MTD driver for SPI flash.
[ 2.847] spiflash: Probing for Serial flash ...
[ 2.848] spiflash: Found SPI serial Flash.
[ 2.849] 8388608: size
[ 2.850] RedBoot partition parsing not available
[ 2.851] Creating 7 MTD partitions on "spiflash":
[ 2.852] 0x00000000-0x00030000 : "RedBoot"
[ 3.084] 0x00030000-0x00050000 : "stage2"
[ 3.317] 0x00050000-0x00150000 : "/storage"
[ 3.549] 0x00150000-0x00490000 : "part1"
[ 3.689] eth0: Configuring MAC for full duplex
[ 3.766] 0x00490000-0x007d0000 : "part2"
[ 4.000] 0x007d0000-0x007e0000 : "redboot config"
[ 4.232] 0x007e0000-0x00800000 : "board config"
[ 4.681] oprofile: using timer interrupt.
[ 4.682] Netfilter messages via NETLINK v0.30.
[ 4.683] NET: Registered protocol family 2
[ 4.700] IP route cache hash table entries: 512 (order: -1, 2048 bytes)
[ 4.703] TCP established hash table entries: 2048 (order: 2, 16384 bytes)
[ 4.704] TCP bind hash table entries: 2048 (order: 2, 16384 bytes)
[ 4.705] TCP: Hash tables configured (established 2048 bind 2048)
[ 4.706] TCP reno registered
[ 4.707] ip_conntrack version 2.4 (256 buckets, 2048 max) - 232 bytes per conntrack
[ 4.760] ctnetlink v0.90: registering with nfnetlink.
[ 4.761] ip_conntrack_pptp version 3.1 loaded
[ 4.762] ip_nat_pptp version 3.0 loaded
[ 4.763] ip_tables: (C) 2000-2006 Netfilter Core Team
[ 4.906] ClusterIP Version 0.8 loaded successfully
[ 4.907] TCP bic registered
[ 4.908] NET: Registered protocol family 1
[ 4.909] NET: Registered protocol family 17
[ 4.981] Bridge firewalling registered
[ 4.989] Freeing unused kernel memory: 9328k freed

init started: BusyBox v1.1.0 (2008.04.19-00:26+0000) multi-call binary

Please press Enter to activate this console.

BusyBox v1.1.0 (2008.04.19-00:26+0000) Built-in shell (ash)
Enter 'help' for a list of built-in commands.

Welcome to Meraki.

Usage of this device is governed by Meraki's End User License
Agreement, available at http://meraki.com/legal.
(none):/#
init-boot: boot 3 build 8-16504 board ar531x mac 00:18:0A:50:00:00
[ 10.209] ar2315_wdt: starting watchdog w/timeout 90 seconds
[ 10.210] watchdog hb: 90 ISR: 0x20 IMR: 0x89 WD : 0xd690d504 WDC: 0x0
[ 10.310] ath_hal: module license 'Proprietary' taints kernel.
[ 10.406] ath_hal: 0.9.17.1 (AR5212, AR5312, RF5112, RF2316, RF2317, TX_DESC_SWAP)
[ 10.910] ath_rate_sample: 1.2 (svn 16289)
[ 11.300] ath_ahb: 0.9.4.5 (svn 16289)
[ 11.437] wifi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
[ 11.441] wifi0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps
[ 11.449] wifi0: H/W encryption support: WEP AES AES_CCM TKIP
[ 11.452] wifi0: mac 11.0 phy 4.8 radio 8.6
[ 11.454] wifi0: Use hw queue 1 for WME_AC_BE traffic
[ 11.455] wifi0: Use hw queue 0 for WME_AC_BK traffic
[ 11.456] wifi0: Use hw queue 2 for WME_AC_VI traffic
[ 11.457] wifi0: Use hw queue 3 for WME_AC_VO traffic
[ 11.458] wifi0: Use hw queue 8 for CAB traffic
[ 11.459] wifi0: Use hw queue 9 for beacons
[ 11.460] couldn't load module 'wlan_scan_sta' (-89)
[ 11.462] unable to load wlan_scan_sta
[ 11.561] wifi0: Atheros 2317 WiSoC: mem=0xb0000000, irq=3
[ 15.390] click: starting router thread pid 437 (81b22900)
[ 15.525] wlan: mac acl policy registered
[ 20.414] couldn't load module 'wlan_scan_monitor' (-89)
[ 20.415] unable to load wlan_scan_monitor

ls
LAST_BOOT_COUNT MERAKI_SERIAL lib usr
MERAKI_ARCH bin proc var
MERAKI_BOARD click sbin www
MERAKI_BUILD dev storage
MERAKI_IP etc sys
MERAKI_MAC init tmp

</pre>
== Where projects are the units going to? ==

* Dana wants to [https://www.noisebridge.net/pipermail/noisebridge-discuss/2013-November/040757.html take 20 units] for a community project ''(I'm in possession of 14 units as of 2013.11.27. If any go unused I will return them for other uses. ~ dana)''
* Sudoroom is interested in [https://www.noisebridge.net/pipermail/noisebridge-discuss/2013-November/040764.html all the units] for their open mesh networking project.
*Dan would like at least 1 outdoor version and 5-10 boards to provide wifi in the Mission around Noisebridge. https://openwireless.org nodes
* Adrian wants several to [https://www.noisebridge.net/pipermail/noisebridge-discuss/2013-November/040755.html improve Atheros support] in FreeBSD
* Jof wants boards for [https://www.noisebridge.net/pipermail/noisebridge-discuss/2013-November/040756.html mesh testing]
* [[User:Thex|J.C.]] has 2 boards for testing.
* Sudomesh has moved the majority of these to a slightly less public location as per [https://www.noisebridge.net/pipermail/noisebridge-discuss/2013-November/040764.html email suggestion] and no objections after three days. Need to count them.

Sparky

2013-12-02T13:59:40Z

Juul: /* Where projects are the units going to? */

Sparky

2013-12-02T13:54:09Z

Juul:

BioBoard/Documentation/PC Software

2011-05-03T19:32:19Z

Juul:

= Introduction =

The PC software has two parts:

*[https://github.com/BioBridge/BioBoardLogServer The logging daemon]
*[https://github.com/BioBridge/BioBoardSite The web application]

The logging daemon receives data from the Arduino and logs it to a database. The Arduino can be connected either directly over USB or, if you have an [http://www.arduino.cc/en/Main/ArduinoEthernetShield Ethnernet Shield], over a local network or the Internet.

The web application lets you create new projects and view graphs of the logged data.

= Software setup =

To get started, you should first install the software. There is an installation guide on [https://github.com/BioBridge/BioBoardSite the web app's github page] (scroll down to find it). Right now the installation guide is specific to Ubuntu Linux, though it should work for Debian and other Debian-based Linux distributions as well. The software is written in Ruby, so it should run on other operating systems such as Windows and OS X, though we are still working on the installation guides for these.

After verifying that everything works, you should create a new project in the web app. Make sure the web app is running (as per the [https://github.com/BioBridge/BioBoardSite install guide]), point your web-browser to [http://localhost:3000/ http://localhost:3000/] and click the "Start a new project!"-button. Name the project by filling out the "<give your project a name>" textbox.

[[File:BioBoardAppMainPage.png|thumb|300px|The web app main page.]]

Now, you need to ensure that the project name as specified in the Arduino sketch is the same as the name of your project. To change the name in the Arduino sketch you need to find the line where the ProjectName" variable is assigned a string, and change that string to the project name. The only constraint is that the name cannot contain any exclamation marks. Remember to upload your sketch to the Arduino if you change it.

[[File:BioBoardAppNewProject.png|thumb|300px|Page for a new BioBoard project.]]

= Connecting the BioBoard =

There are two ways of connecting the BioBoard to the log server. One is to connect the Arduino to the computer running the logserver using USB. The other is to use an Arduino Ethernet Shield to connect over a local network or the Internet. First of all, make sure the log server is running, as described in the [https://github.com/BioBridge/BioBoardSite installation guide].

== Connecting using USB ==

When using USB, you need to start an additional serial forwarder program that reads the data from the connected Arduino and sends it to the log server. This step will be eliminated in future versions of the software. The serial forwarder is included with the log server. After starting the log server, make sure the baud rate is set to 19200:

<code>
sudo stty -F /dev/ttyUSB0 19200
</code>

then do:

<code>
cd BioBoardLogServer/

./serial_forwarder.rb
</code>

and let it run for as long as the log server runs. If your Arduino is not connected at /dev/ttyUSB0, then you need to change this in the serial_forwarder.rb program and in the above command.

Now connect the BioBoard to the USB port of the computer running the log server and hit the reset button on the Arduino. The Arduino will immediately start sending data from the connected probes and sending it the log server which will log the data in thedatabase.

== Connecting using the Ethernet Shield ==

The code for using the Ethernet Shield has not been integrated with the rest of the Arduino code yet, but if you've used an Ethernet Shield before it should be fairly straight-forward. Instead of sending data over the serial connection, you need to modify the program to connect using TCP on port 9090 to the computer where the log server is running and send the data over that connection.

= Using the software =

Now you are ready to view the graphs generated from the probe data. If you still have the page for your new project loaded in the browser, simply hit the browser refresh button, otherwise go to [http://localhost:3000/ http://localhost:3000/] and click the project name under "Existing projects".

You should now see your graphs, one for each probe. You can toggle the graphs on and off. Features such as adjusting the x and y-axis scales are coming soon!

[[File:BioBoardAppGraphs.png|thumb|300px|Example of a project page displaying graphs for logged Temperature and NIR data.]]

Don't worry about shutting down the serial forwarder, log server or web app. All your data will be there next time you start it up. Your entire database is stored in the file BioBoardSite/db/dev.sqlite so if you want to back it up, simply shut down the log server and make a copy of that file.

BioBoard/Documentation/PC Software

2011-05-03T08:26:45Z

Juul: /* Software setup */

= Introduction =

The PC software has two parts:

*[https://github.com/BioBridge/BioBoardLogServer The logging daemon]
*[https://github.com/BioBridge/BioBoardSite The web application]

The logging daemon receives data from the Arduino and logs it to a database. The Arduino can be connected either directly over USB or, if you have an [http://www.arduino.cc/en/Main/ArduinoEthernetShield Ethnernet Shield], over a local network or the Internet.

The web application lets you create new projects and view graphs of the logged data.

= Software setup =

To get started, you should first install the software. There is an installation guide on [https://github.com/BioBridge/BioBoardSite the web app's github page] (scroll down to find it). Right now the installation guide is specific to Ubuntu Linux, though it should work for Debian and other Debian-based Linux distributions as well. The software is written in Ruby, so it should run on other operating systems such as Windows and OS X, though we are still working on the installation guides for these.

After verifying that everything works, you should create a new project in the web app. Make sure the web app is running (as per the [https://github.com/BioBridge/BioBoardSite install guide]), point your web-browser to [http://localhost:3000/ http://localhost:3000/] and click the "Start a new project!"-button. Name the project by filling out the "<give your project a name>" textbox.

[[File:BioBoardAppMainPage.png|thumb|300px|The web app main page.]]

Now, you need to ensure that the project name as specified in the Arduino sketch is the same as the name of your project. To change the name in the Arduino sketch you need to find the line where the ProjectName" variable is assigned a string, and change that string to the project name. The only constraint is that the name cannot contain any exclamation marks. Remember to upload your sketch to the Arduino if you change it.

[[File:BioBoardAppNewProject.png|thumb|300px|Page for a new BioBoard project.]]

= Connecting the BioBoard =

There are two ways of connecting the BioBoard to the log server. One is to connect the Arduino to the computer running the logserver using USB. The other is to use an Arduino Ethernet Shield to connect over a local network or the Internet. First of all, make sure the log server is running, as described in the [https://github.com/BioBridge/BioBoardSite installation guide].

== Connecting using USB ==

When using USB, you need to start an additional serial forwarder program that reads the data from the connected Arduino and sends it to the log server. This step will be eliminated in future versions of the software. The serial forwarder is included with the log server. After starting the log server, do:

<code>
cd BioBoardLogServer/

./serial_forwarder.rb
</code>

and let it run for as long as the log server runs.

Now connect the BioBoard to the USB port of the computer running the log server and hit the reset button on the Arduino. The Arduino will immediately start sending data from the connected probes and sending it the log server which will log the data in the database.

== Connecting using the Ethernet Shield ==

The code for using the Ethernet Shield has not been integrated with the rest of the Arduino code yet, but if you've used an Ethernet Shield before it should be fairly straight-forward. Instead of sending data over the serial connection, you need to modify the program to connect using TCP on port 9090 to the computer where the log server is running and send the data over that connection.

= Using the software =

Now you are ready to view the graphs generated from the probe data. If you still have the page for your new project loaded in the browser, simply hit the browser refresh button, otherwise go to [http://localhost:3000/ http://localhost:3000/] and click the project name under "Existing projects".

You should now see your graphs, one for each probe. You can toggle the graphs on and off. Features such as adjusting the x and y-axis scales are coming soon!

[[File:BioBoardAppGraphs.png|thumb|300px|Example of a project page displaying graphs for logged Temperature and NIR data.]]

Don't worry about shutting down the serial forwarder, log server or web app. All your data will be there next time you start it up. Your entire database is stored in the file BioBoardSite/db/dev.sqlite so if you want to back it up, simply shut down the log server and make a copy of that file.

BioBoard/Documentation/PC Software

2011-05-03T07:15:01Z

Juul: /* Using the software */

= Introduction =

The PC software has two parts:

*[https://github.com/BioBridge/BioBoardLogServer The logging daemon]
*[https://github.com/BioBridge/BioBoardSite The web application]

The logging daemon receives data from the Arduino and logs it to a database. The Arduino can be connected either directly over USB or, if you have an [http://www.arduino.cc/en/Main/ArduinoEthernetShield Ethnernet Shield], over a local network or the Internet.

The web application lets you create new projects and view graphs of the logged data.

= Software setup =

To get started, you should first install the software. There is an installation guide on [https://github.com/BioBridge/BioBoardSite the web app's github page] (scroll down to find it). Right now the installation guide is specific to Ubuntu Linux, though it should work for Debian and other Debian-based Linux distributions as well. The software is written in Ruby, so it should run on other operating systems such as Windows and OS X, though we are still working on the installation guides for these.

After verifying that everything works, you should create a new project in the web app. Make sure the web app is running (as per the [https://github.com/BioBridge/BioBoardSite install guide]), point your web-browser to [http://localhost:3000/ http://localhost:3000/] and click the "Start a new project!"-button. Name the project by filling out the "<give your project a name>" textbox.

[[File:BioBoardAppMainPage.png|thumb|300px|The web app main page.]]

Now, you need to ensure that the project name as specified in the Arduino sketch is the same as the name of your project. The only constraint is that the name cannot contain any exclamation marks. Remember to upload your sketch to the Arduino if you change it.

[[File:BioBoardAppNewProject.png|thumb|300px|Page for a new BioBoard project.]]

= Connecting the BioBoard =

There are two ways of connecting the BioBoard to the log server. One is to connect the Arduino to the computer running the logserver using USB. The other is to use an Arduino Ethernet Shield to connect over a local network or the Internet. First of all, make sure the log server is running, as described in the [https://github.com/BioBridge/BioBoardSite installation guide].

== Connecting using USB ==

When using USB, you need to start an additional serial forwarder program that reads the data from the connected Arduino and sends it to the log server. This step will be eliminated in future versions of the software. The serial forwarder is included with the log server. After starting the log server, do:

<code>
cd BioBoardLogServer/

./serial_forwarder.rb
</code>

and let it run for as long as the log server runs.

Now connect the BioBoard to the USB port of the computer running the log server and hit the reset button on the Arduino. The Arduino will immediately start sending data from the connected probes and sending it the log server which will log the data in the database.

== Connecting using the Ethernet Shield ==

The code for using the Ethernet Shield has not been integrated with the rest of the Arduino code yet, but if you've used an Ethernet Shield before it should be fairly straight-forward. Instead of sending data over the serial connection, you need to modify the program to connect using TCP on port 9090 to the computer where the log server is running and send the data over that connection.

= Using the software =

Now you are ready to view the graphs generated from the probe data. If you still have the page for your new project loaded in the browser, simply hit the browser refresh button, otherwise go to [http://localhost:3000/ http://localhost:3000/] and click the project name under "Existing projects".

You should now see your graphs, one for each probe. You can toggle the graphs on and off. Features such as adjusting the x and y-axis scales are coming soon!

[[File:BioBoardAppGraphs.png|thumb|300px|Example of a project page displaying graphs for logged Temperature and NIR data.]]

Don't worry about shutting down the serial forwarder, log server or web app. All your data will be there next time you start it up. Your entire database is stored in the file BioBoardSite/db/dev.sqlite so if you want to back it up, simply shut down the log server and make a copy of that file.

BioBoard/Documentation/PC Software

2011-05-03T07:14:13Z

Juul: /* Software setup */

= Introduction =

The PC software has two parts:

*[https://github.com/BioBridge/BioBoardLogServer The logging daemon]
*[https://github.com/BioBridge/BioBoardSite The web application]

The logging daemon receives data from the Arduino and logs it to a database. The Arduino can be connected either directly over USB or, if you have an [http://www.arduino.cc/en/Main/ArduinoEthernetShield Ethnernet Shield], over a local network or the Internet.

The web application lets you create new projects and view graphs of the logged data.

= Software setup =

To get started, you should first install the software. There is an installation guide on [https://github.com/BioBridge/BioBoardSite the web app's github page] (scroll down to find it). Right now the installation guide is specific to Ubuntu Linux, though it should work for Debian and other Debian-based Linux distributions as well. The software is written in Ruby, so it should run on other operating systems such as Windows and OS X, though we are still working on the installation guides for these.

After verifying that everything works, you should create a new project in the web app. Make sure the web app is running (as per the [https://github.com/BioBridge/BioBoardSite install guide]), point your web-browser to [http://localhost:3000/ http://localhost:3000/] and click the "Start a new project!"-button. Name the project by filling out the "<give your project a name>" textbox.

[[File:BioBoardAppMainPage.png|thumb|300px|The web app main page.]]

Now, you need to ensure that the project name as specified in the Arduino sketch is the same as the name of your project. The only constraint is that the name cannot contain any exclamation marks. Remember to upload your sketch to the Arduino if you change it.

[[File:BioBoardAppNewProject.png|thumb|300px|Page for a new BioBoard project.]]

= Connecting the BioBoard =

There are two ways of connecting the BioBoard to the log server. One is to connect the Arduino to the computer running the logserver using USB. The other is to use an Arduino Ethernet Shield to connect over a local network or the Internet. First of all, make sure the log server is running, as described in the [https://github.com/BioBridge/BioBoardSite installation guide].

== Connecting using USB ==

When using USB, you need to start an additional serial forwarder program that reads the data from the connected Arduino and sends it to the log server. This step will be eliminated in future versions of the software. The serial forwarder is included with the log server. After starting the log server, do:

<code>
cd BioBoardLogServer/

./serial_forwarder.rb
</code>

and let it run for as long as the log server runs.

Now connect the BioBoard to the USB port of the computer running the log server and hit the reset button on the Arduino. The Arduino will immediately start sending data from the connected probes and sending it the log server which will log the data in the database.

== Connecting using the Ethernet Shield ==

The code for using the Ethernet Shield has not been integrated with the rest of the Arduino code yet, but if you've used an Ethernet Shield before it should be fairly straight-forward. Instead of sending data over the serial connection, you need to modify the program to connect using TCP on port 9090 to the computer where the log server is running and send the data over that connection.

= Using the software =

Now you are ready to view the graphs generated from the probe data. If you still have the page for your new project loaded in the browser, simply hit the browser refresh button, otherwise go to [http://localhost:3000/ http://localhost:3000/] and click the project name under "Existing projects".

You should now see your graphs, one for each probe. You can toggle the graphs on and off. Features such as adjusting the x and y-axis scales are coming soon!

Don't worry about shutting down the serial forwarder, log server or web app. All your data will be there next time you start it up. Your entire database is stored in the file BioBoardSite/db/dev.sqlite so if you want to back it up, simply shut down the log server and make a copy of that file.

BioBoard/Documentation/PC Software

2011-05-03T07:13:06Z

Juul: /* Software setup */

= Introduction =

The PC software has two parts:

*[https://github.com/BioBridge/BioBoardLogServer The logging daemon]
*[https://github.com/BioBridge/BioBoardSite The web application]

The logging daemon receives data from the Arduino and logs it to a database. The Arduino can be connected either directly over USB or, if you have an [http://www.arduino.cc/en/Main/ArduinoEthernetShield Ethnernet Shield], over a local network or the Internet.

The web application lets you create new projects and view graphs of the logged data.

= Software setup =

To get started, you should first install the software. There is an installation guide on [https://github.com/BioBridge/BioBoardSite the web app's github page] (scroll down to find it). Right now the installation guide is specific to Ubuntu Linux, though it should work for Debian and other Debian-based Linux distributions as well. The software is written in Ruby, so it should run on other operating systems such as Windows and OS X, though we are still working on the installation guides for these.

After verifying that everything works, you should create a new project in the web app. Make sure the web app is running (as per the [https://github.com/BioBridge/BioBoardSite install guide]), point your web-browser to [http://localhost:3000/ http://localhost:3000/] and click the "Start a new project!"-button. Name the project by filling out the "<give your project a name>" textbox.

[[File:BioBoardAppMainPage.png|thumb|300px|The web app main page.]]

Now, you need to ensure that the project name as specified in the Arduino sketch is the same as the name of your project. The only constraint is that the name cannot contain any exclamation marks. Remember to upload your sketch to the Arduino if you change it.

= Connecting the BioBoard =

There are two ways of connecting the BioBoard to the log server. One is to connect the Arduino to the computer running the logserver using USB. The other is to use an Arduino Ethernet Shield to connect over a local network or the Internet. First of all, make sure the log server is running, as described in the [https://github.com/BioBridge/BioBoardSite installation guide].

== Connecting using USB ==

When using USB, you need to start an additional serial forwarder program that reads the data from the connected Arduino and sends it to the log server. This step will be eliminated in future versions of the software. The serial forwarder is included with the log server. After starting the log server, do:

<code>
cd BioBoardLogServer/

./serial_forwarder.rb
</code>

and let it run for as long as the log server runs.

Now connect the BioBoard to the USB port of the computer running the log server and hit the reset button on the Arduino. The Arduino will immediately start sending data from the connected probes and sending it the log server which will log the data in the database.

== Connecting using the Ethernet Shield ==

The code for using the Ethernet Shield has not been integrated with the rest of the Arduino code yet, but if you've used an Ethernet Shield before it should be fairly straight-forward. Instead of sending data over the serial connection, you need to modify the program to connect using TCP on port 9090 to the computer where the log server is running and send the data over that connection.

= Using the software =

Now you are ready to view the graphs generated from the probe data. If you still have the page for your new project loaded in the browser, simply hit the browser refresh button, otherwise go to [http://localhost:3000/ http://localhost:3000/] and click the project name under "Existing projects".

You should now see your graphs, one for each probe. You can toggle the graphs on and off. Features such as adjusting the x and y-axis scales are coming soon!

Don't worry about shutting down the serial forwarder, log server or web app. All your data will be there next time you start it up. Your entire database is stored in the file BioBoardSite/db/dev.sqlite so if you want to back it up, simply shut down the log server and make a copy of that file.

File:BioBoardAppGraphs.png

2011-05-03T07:07:35Z

Juul: An example of the graphs generated by the BioBoard web app

An example of the graphs generated by the BioBoard web app

File:BioBoardAppNewProject.png

2011-05-03T07:05:58Z

Juul: The new project page in the BioBoard web app

The new project page in the BioBoard web app

File:BioBoardAppMainPage.png

2011-05-03T07:05:07Z

Juul: The main page of the BioBoard web app

The main page of the BioBoard web app

BioBoard/Documentation/PC Software

2011-05-03T07:04:10Z

Juul: /* Setup */

= Introduction =

The PC software has two parts:

*[https://github.com/BioBridge/BioBoardLogServer The logging daemon]
*[https://github.com/BioBridge/BioBoardSite The web application]

The logging daemon receives data from the Arduino and logs it to a database. The Arduino can be connected either directly over USB or, if you have an [http://www.arduino.cc/en/Main/ArduinoEthernetShield Ethnernet Shield], over a local network or the Internet.

The web application lets you create new projects and view graphs of the logged data.

= Software setup =

To get started, you should first install the software. There is an installation guide on [https://github.com/BioBridge/BioBoardSite the web app's github page] (scroll down to find it). Right now the installation guide is specific to Ubuntu Linux, though it should work for Debian and other Debian-based Linux distributions as well. The software is written in Ruby, so it should run on other operating systems such as Windows and OS X, though we are still working on the installation guides for these.

After verifying that everything works, you should create a new project in the web app. Make sure the web app is running (as per the [https://github.com/BioBridge/BioBoardSite install guide]), point your web-browser to [http://localhost:3000/ http://localhost:3000/] and click the "Start a new project!"-button. Name the project by filling out the "<give your project a name>" textbox.

Now, you need to ensure that the project name as specified in the Arduino sketch is the same as the name of your project. The only constraint is that the name cannot contain any exclamation marks. Remember to upload your sketch to the Arduino if you change it.

= Connecting the BioBoard =

There are two ways of connecting the BioBoard to the log server. One is to connect the Arduino to the computer running the logserver using USB. The other is to use an Arduino Ethernet Shield to connect over a local network or the Internet. First of all, make sure the log server is running, as described in the [https://github.com/BioBridge/BioBoardSite installation guide].

== Connecting using USB ==

When using USB, you need to start an additional serial forwarder program that reads the data from the connected Arduino and sends it to the log server. This step will be eliminated in future versions of the software. The serial forwarder is included with the log server. After starting the log server, do:

<code>
cd BioBoardLogServer/

./serial_forwarder.rb
</code>

and let it run for as long as the log server runs.

Now connect the BioBoard to the USB port of the computer running the log server and hit the reset button on the Arduino. The Arduino will immediately start sending data from the connected probes and sending it the log server which will log the data in the database.

== Connecting using the Ethernet Shield ==

The code for using the Ethernet Shield has not been integrated with the rest of the Arduino code yet, but if you've used an Ethernet Shield before it should be fairly straight-forward. Instead of sending data over the serial connection, you need to modify the program to connect using TCP on port 9090 to the computer where the log server is running and send the data over that connection.

= Using the software =

Now you are ready to view the graphs generated from the probe data. If you still have the page for your new project loaded in the browser, simply hit the browser refresh button, otherwise go to [http://localhost:3000/ http://localhost:3000/] and click the project name under "Existing projects".

You should now see your graphs, one for each probe. You can toggle the graphs on and off. Features such as adjusting the x and y-axis scales are coming soon!

Don't worry about shutting down the serial forwarder, log server or web app. All your data will be there next time you start it up. Your entire database is stored in the file BioBoardSite/db/dev.sqlite so if you want to back it up, simply shut down the log server and make a copy of that file.

BioBoard/Documentation/PC Software

2011-05-03T06:36:43Z

Juul: Created page with '= Introduction = The PC software has two parts: *[https://github.com/BioBridge/BioBoardLogServer The logging daemon] *[https://github.com/BioBridge/BioBoardSite The web applica…'

BioBoard/Documentation

2011-05-03T06:18:14Z

Juul:

BioBoard documentation wikis

*[[BioBoard/Documentation/Temperature]]
*[[BioBoard/Documentation/pH]]
*[[BioBoard/Documentation/Oxygen]]
*[[BioBoard/Documentation/Optical loss]]
*[[BioBoard/Documentation/Arduino]]
*[[BioBoard/Documentation/PC Software]]

BioBridge/Software

2011-03-29T05:22:40Z

Juul: Created page with '= Design = Rails 3 app with sqlite as default backend. Previously logged data retrieved through ActiveRecord. Flot for plotting. Home-brewed simple EventMachine-based Comet se…'

= Design =

Rails 3 app with sqlite as default backend. Previously logged data retrieved through ActiveRecord. Flot for plotting.

Home-brewed simple EventMachine-based Comet server that also acts as the logging server that the EtherShield-equipped Arduino board sends its data to. As data comes in it is sent to all connected clients and simultaneously logged to the database using rails ActiveRecord.

Data sent by arduino will be simple semi-colon separated values.

The end.

BioBoard/Equipment

2011-03-20T20:38:16Z

Juul: /* Controller and data transmission */

=Sensors=

We need to decide whether to build them ourselves or whether to buy them ready-made and just worry about assembling the bits and making everything communicate. Important considerations would be affordability, accessibility and required precision.

==Thermocouple==

Commercial probes are available from approx. $20 upwards
*[http://www.omega.com/ppt/pptsc.asp?ref=HTTC36 Hollow Tube Thermocouple Probe] $19

There is also a somewhat sketchy [http://www.instructables.com/id/Making-A-Thermocouple/ Instructable] for how to build one - at approx. $15, it’s not going to be much cheaper, though, so choosing the DIY version would be mostly for the educational benefit of actually building it (almost) from scratch.

==pH-meter==

Maybe we can buy one of these (or similar), break them open and figure out how to read the output from an arduino:

*[http://www.heavydutysupplies.com/servlet/the-15/Checker,-HI-98103,-HI98103/Detail HANNA Instruments HI 98103] $55
*[http://www.amazon.com/Milwaukee-pH600-Portable-pH-meter/dp/B004CZ8632 Milwaukee pH600] $20 - doesn't look like it needs specific buffers for calibration, but the accuracy is probably not great. Maybe it's enough, though.
*[http://www.google.com/products/catalog?hl=en&q=ph+electrode&sqi=2&cid=15011737823946485839&os=sellers# Google shopping results] approx. $40 upwards
*[http://www.pulseinstruments.net/sotaphelectrode.aspx SOTA pH Electrode] $100 - expensive, but so so sweet: designed for continuous measurement, and comes with any kind of connector.

You can also get little tester units, such as this [http://www.jencostore.com/ph-meter/ph-testers.html?price=1%2C100 Jenco 610 pH tester] for $30 - perhaps it could be hacked?

There’s also the option of attempting to build one ourselves using
[http://www.ph-meter.info/pH-meter-construction this] (or a similar) schematic with the Arduino instead of a voltmeter - not necessarily cheaper, although it’d certainly be both fun and informative.

==Dissolved oxygen (DO) probes==

*[http://www.vernier.com/probes/do-bta.html DO-BTA Dissolved Oxygen Sensor] $209 - cheapest commercial product I could find.

In this case, it seems relatively safe to assume that bulding one ourselves would be cheaper. There is an illustration [http://www.cebtechservices.com/probe&sensorA.htm here] of how a DO probe is constructed, but whether we can actually build one or not is of course another question.

==Living biomass==

This is still an open question on all fronts. Don’t know how much such a sensor would cost, if we’d be able to hack one, and whether building one ourselves is actually a real option.

=Controller and data transmission=

Is Arduino going to be our platform?

Here's a possible design: An arduino hooked up to a bunch of different probes and in turn hooked up to either an ether/wifi shield or a full linux box (I've previously used the excellent and tiny 1 watt [http://bifferos.bizhat.com/ biffer board] in this manner). As data comes in it should be timestamped, categorized (pH, temperature, etc) and sent (via shield or pc) to a server somewhere on the internet using e.g. JSON over HTTP post. The server would run a custom web app (e.g. Rails) that receives data, logs it to a database and generates graphs on demand. Add a Comet server and the graphs could be live-updated as the data comes in. We could add features that lets new users sign up and get a unique key which they use when transmitting their own data to the JSON web service on our server. The server then uses the key to associate the data with the user, and the user can look at their graphs and share them with others. We can implement the "export to CSV" on the server side, allowing users to analyze the data using the tool of their choice. If we put all of the code on github, then others can easily fork the code and add their own features. To me, the hardest part of this project will be finding/building cheap measurement probes that are accurate enough (how accurate is enough?) and require little or no calibration. - ([[User:Juul|Juul]])

==Sensor data collection==

Which board would be optimal for our purposes? Does this depend on the sensors?

==Wireless data transmission==

How? Immediate suggestion would be ethernet shield, but others options are available and perhaps preferable.

=Data logging and visualization=

==Log==

Data should be recorded at regular intervals; ‘smoothing’ by logging average values over each interval rather than point values may also be an option. Export to a simple spread sheet arranged to make later data analysis and visualization easy - how to do this?
:I suggest that we use a simple data serialization format like JSON for logging the data, and then include an "export to CSV" function where you can select the data you want exported (pH, temperature, etc). This should allow people to use a variety of programming languages and data analysis tools without a lot of work on their part or ours - ([[User:Juul|Juul]]).

==Graphic visualization==

It would be awesome to have the visuals built in from the beginning, as good graphics will greatly increase people's understanding of the correlations between the factors we measure.

==Website==

A virtual space for the collaboration, organization and publication of the project. So far, this wiki seems to work well for our collaboration and organization purposes, but it may not be the best platform for presenting, sharing and comparing data?
:I could do a quick Rails site with some live graphing and throw the code on github. We could keep it really simple for the first version, but encourage people to add functionality for collaboration. - ([[User:Juul|Juul]])

BioBoard/Equipment

2011-03-20T20:23:17Z

Juul: /* Website */

=Sensors=

We need to decide whether to build them ourselves or whether to buy them ready-made and just worry about assembling the bits and making everything communicate. Important considerations would be affordability, accessibility and required precision.

==Thermocouple==

Commercial probes are available from approx. $20 upwards
*[http://www.omega.com/ppt/pptsc.asp?ref=HTTC36 Hollow Tube Thermocouple Probe] $19

There is also a somewhat sketchy [http://www.instructables.com/id/Making-A-Thermocouple/ Instructable] for how to build one - at approx. $15, it’s not going to be much cheaper, though, so choosing the DIY version would be mostly for the educational benefit of actually building it (almost) from scratch.

==pH-meter==

Maybe we can buy one of these (or similar), break them open and figure out how to read the output from an arduino:

*[http://www.heavydutysupplies.com/servlet/the-15/Checker,-HI-98103,-HI98103/Detail HANNA Instruments HI 98103] $55
*[http://www.amazon.com/Milwaukee-pH600-Portable-pH-meter/dp/B004CZ8632 Milwaukee pH600] $20 - doesn't look like it needs specific buffers for calibration, but the accuracy is probably not great. Maybe it's enough, though.
*[http://www.google.com/products/catalog?hl=en&q=ph+electrode&sqi=2&cid=15011737823946485839&os=sellers# Google shopping results] approx. $40 upwards
*[http://www.pulseinstruments.net/sotaphelectrode.aspx SOTA pH Electrode] $100 - expensive, but so so sweet: designed for continuous measurement, and comes with any kind of connector.

You can also get little tester units, such as this [http://www.jencostore.com/ph-meter/ph-testers.html?price=1%2C100 Jenco 610 pH tester] for $30 - perhaps it could be hacked?

There’s also the option of attempting to build one ourselves using
[http://www.ph-meter.info/pH-meter-construction this] (or a similar) schematic with the Arduino instead of a voltmeter - not necessarily cheaper, although it’d certainly be both fun and informative.

==Dissolved oxygen (DO) probes==

*[http://www.vernier.com/probes/do-bta.html DO-BTA Dissolved Oxygen Sensor] $209 - cheapest commercial product I could find.

In this case, it seems relatively safe to assume that bulding one ourselves would be cheaper. There is an illustration [http://www.cebtechservices.com/probe&sensorA.htm here] of how a DO probe is constructed, but whether we can actually build one or not is of course another question.

==Living biomass==

This is still an open question on all fronts. Don’t know how much such a sensor would cost, if we’d be able to hack one, and whether building one ourselves is actually a real option.

=Controller and data transmission=

Is Arduino going to be our platform?

==Sensor data collection==

Which board would be optimal for our purposes? Does this depend on the sensors?

==Wireless data transmission==

How? Immediate suggestion would be ethernet shield, but others options are available and perhaps preferable.

=Data logging and visualization=

==Log==

Data should be recorded at regular intervals; ‘smoothing’ by logging average values over each interval rather than point values may also be an option. Export to a simple spread sheet arranged to make later data analysis and visualization easy - how to do this?
:I suggest that we use a simple data serialization format like JSON for logging the data, and then include an "export to CSV" function where you can select the data you want exported (pH, temperature, etc). This should allow people to use a variety of programming languages and data analysis tools without a lot of work on their part or ours - ([[User:Juul|Juul]]).

==Graphic visualization==

It would be awesome to have the visuals built in from the beginning, as good graphics will greatly increase people's understanding of the correlations between the factors we measure.

==Website==

A virtual space for the collaboration, organization and publication of the project. So far, this wiki seems to work well for our collaboration and organization purposes, but it may not be the best platform for presenting, sharing and comparing data?
:I could do a quick Rails site with some live graphing and throw the code on github. We could keep it really simple for the first version, but encourage people to add functionality for collaboration. - ([[User:Juul|Juul]])

BioBoard/Equipment

2011-03-20T20:21:18Z

Juul: /* Log */

=Sensors=

We need to decide whether to build them ourselves or whether to buy them ready-made and just worry about assembling the bits and making everything communicate. Important considerations would be affordability, accessibility and required precision.

==Thermocouple==

Commercial probes are available from approx. $20 upwards
*[http://www.omega.com/ppt/pptsc.asp?ref=HTTC36 Hollow Tube Thermocouple Probe] $19

There is also a somewhat sketchy [http://www.instructables.com/id/Making-A-Thermocouple/ Instructable] for how to build one - at approx. $15, it’s not going to be much cheaper, though, so choosing the DIY version would be mostly for the educational benefit of actually building it (almost) from scratch.

==pH-meter==

Maybe we can buy one of these (or similar), break them open and figure out how to read the output from an arduino:

*[http://www.heavydutysupplies.com/servlet/the-15/Checker,-HI-98103,-HI98103/Detail HANNA Instruments HI 98103] $55
*[http://www.amazon.com/Milwaukee-pH600-Portable-pH-meter/dp/B004CZ8632 Milwaukee pH600] $20 - doesn't look like it needs specific buffers for calibration, but the accuracy is probably not great. Maybe it's enough, though.
*[http://www.google.com/products/catalog?hl=en&q=ph+electrode&sqi=2&cid=15011737823946485839&os=sellers# Google shopping results] approx. $40 upwards
*[http://www.pulseinstruments.net/sotaphelectrode.aspx SOTA pH Electrode] $100 - expensive, but so so sweet: designed for continuous measurement, and comes with any kind of connector.

You can also get little tester units, such as this [http://www.jencostore.com/ph-meter/ph-testers.html?price=1%2C100 Jenco 610 pH tester] for $30 - perhaps it could be hacked?

There’s also the option of attempting to build one ourselves using
[http://www.ph-meter.info/pH-meter-construction this] (or a similar) schematic with the Arduino instead of a voltmeter - not necessarily cheaper, although it’d certainly be both fun and informative.

==Dissolved oxygen (DO) probes==

*[http://www.vernier.com/probes/do-bta.html DO-BTA Dissolved Oxygen Sensor] $209 - cheapest commercial product I could find.

In this case, it seems relatively safe to assume that bulding one ourselves would be cheaper. There is an illustration [http://www.cebtechservices.com/probe&sensorA.htm here] of how a DO probe is constructed, but whether we can actually build one or not is of course another question.

==Living biomass==

This is still an open question on all fronts. Don’t know how much such a sensor would cost, if we’d be able to hack one, and whether building one ourselves is actually a real option.

=Controller and data transmission=

Is Arduino going to be our platform?

==Sensor data collection==

Which board would be optimal for our purposes? Does this depend on the sensors?

==Wireless data transmission==

How? Immediate suggestion would be ethernet shield, but others options are available and perhaps preferable.

=Data logging and visualization=

==Log==

Data should be recorded at regular intervals; ‘smoothing’ by logging average values over each interval rather than point values may also be an option. Export to a simple spread sheet arranged to make later data analysis and visualization easy - how to do this?
:I suggest that we use a simple data serialization format like JSON for logging the data, and then include an "export to CSV" function where you can select the data you want exported (pH, temperature, etc). This should allow people to use a variety of programming languages and data analysis tools without a lot of work on their part or ours - ([[User:Juul|Juul]]).

==Graphic visualization==

It would be awesome to have the visuals built in from the beginning, as good graphics will greatly increase people's understanding of the correlations between the factors we measure.

==Website==

A virtual space for the collaboration, organization and publication of the project. So far, this wiki seems to work well for our collaboration and organization purposes, but it may not be the best platform for presenting, sharing and comparing data?

BioBoard/Equipment

2011-03-11T03:43:15Z

Juul: Created page with ' = pH meters = Maybe we can buy one of these (or similar), break them open and figure out how to read the output from an arduino: *[http://www.heavydutysupplies.com/servlet/the…'

= pH meters =

Maybe we can buy one of these (or similar), break them open and figure out how to read the output from an arduino:

*[http://www.heavydutysupplies.com/servlet/the-15/Checker,-HI-98103,-HI98103/Detail HANNA Instruments HI 98103] $55
*[http://www.amazon.com/Milwaukee-pH600-Portable-pH-meter/dp/B004CZ8632 Milwaukee pH600] $20

The second one doesn't look like it needs specific buffers for calibration, but the accuracy is probably not great. Maybe it's enough though.

BioBridge

2011-03-11T03:38:59Z

Juul: Created page with 'This is BioBridge. We indend to participate in the Hackerspace Challenge. More info to come. Sub-pages so far: *BioBridge/Equipment'

This is BioBridge.

We indend to participate in the Hackerspace Challenge.

More info to come.

Sub-pages so far:

*[[BioBridge/Equipment]]