# of Wiki Edits: 113
# of Forum topics submitted: 16
# of Comments: 64
| Title | Edited on | Edit message | ||
|---|---|---|---|---|
| FarmHack Event Tool | Friday, January 25, 2013 - 15:46 | View changes | View current version | |
| FarmHack Event Tool | Sunday, January 20, 2013 - 17:09 | View changes | View current version | |
| electronic flame weeder ignition/electronic LP solenoid on/off | Thursday, January 10, 2013 - 12:56 | View changes | View current version | |
| electronic flame weeder ignition/electronic LP solenoid on/off | Thursday, January 10, 2013 - 12:46 | View changes | View current version | |
| electronic flame weeder ignition/electronic LP solenoid on/off | Thursday, January 10, 2013 - 12:44 | View changes | View current version | |
| electronic flame weeder ignition/electronic LP solenoid on/off | Thursday, January 10, 2013 - 11:09 | View changes | View current version | |
| electronic flame weeder ignition/electronic LP solenoid on/off | Thursday, January 10, 2013 - 10:50 | View changes | View current version | |
| electronic flame weeder ignition/electronic LP solenoid on/off | Thursday, January 10, 2013 - 10:47 | View changes | View current version | |
| Greenhouse Monitoring with Text Message Alerts | Friday, November 16, 2012 - 09:17 | View changes | View current version | |
| Greenhouse Monitoring with Text Message Alerts | Friday, November 16, 2012 - 09:15 | View changes | View current version |
| In 50 characters or less... | Posted by |
Post date |
Last comment | Number of Comments | # of Comments new to you | |
|---|---|---|---|---|---|---|
| Simplifying the Site for New Users | Louis | Friday, May 17, 2013 - 10:48 | Thursday, May 23, 2013 - 11:51 | 6 | ||
| Rover Sketch? | Louis | Sunday, January 20, 2013 - 11:20 | Sunday, January 20, 2013 - 11:20 | |||
|
|
Notes from the Open-Source Hardware Summit 2012 | Louis | Monday, October 1, 2012 - 11:33 | Monday, October 1, 2012 - 11:33 | ||
|
|
#Tags Don't Link to Topic | Louis | Wednesday, August 8, 2012 - 00:58 | Tuesday, October 2, 2012 - 15:16 | 1 | |
|
|
Fido for Sale (Coming Soon) | Louis | Friday, June 29, 2012 - 10:01 | Thursday, July 5, 2012 - 17:40 | 2 | |
|
|
Camera Trigger | Louis | Wednesday, June 6, 2012 - 09:38 | Wednesday, June 6, 2012 - 09:38 | ||
|
|
Temperature Sensor Talk | Louis | Sunday, May 20, 2012 - 13:42 | Sunday, May 20, 2012 - 13:42 | ||
|
|
Anybody find a green jacket Hard Wear at the Essex Grange? | Louis | Monday, April 30, 2012 - 11:50 | Sunday, November 4, 2012 - 22:02 | 4 | |
|
|
Local Zigbee Network on a Farm | Louis | Saturday, April 28, 2012 - 15:06 | Sunday, September 2, 2012 - 22:29 | 12 | |
|
|
Pushing Arduino Memory | Louis | Friday, April 6, 2012 - 00:04 | Sunday, April 8, 2012 - 20:07 | 1 |
Hi Jeff,
It's great to see that there are some standard being put into motion, both locally managed and with global connections!
It looks like the NEFKE is in development but how would I go about finding out the specifications so I could potentially export my data in that format? Are they still being developed? Will the exporting be periodic data-dumps or will the system be setup for dynamic data sharing?
Hi Terry
You are welcome to post this project on your website - hopefully with a reference back to here :)
Something we've been investigating are ways to allow sites to share source to the same project. Kind of like the way branching and forking work in GitHub (we're actually exploring that as the back-end) - that way I could easily merge edits from your branch on ArduinoInfo. RJ might come along and tell you more about that.
Anyway, about collaboration, I'd love any contributions you'd have to the tool page here. I was planning to go through and try to simplify the page as much as possible soon anyway. I'd really appreciate your perspective on the general structure since you've no doubt spent a lot of type thinking about how tutorials need to be written.
--Louis
This is something that I'm trying to position Apitronics to help with. Since many farms will have identical sensors deployed, the sensor specifications will be open of course, and the location will be paired with all the data being gathered, I think it could be a great component to the platform being proposed.
I would love to be part of this discussion and to hear what the research needs are. I will have my own practical uses for the data (primarily building physical models for simulations and automation) but I would love to know how to make the datasets more accessible to others.
Hi there Wyatt! Welcome
That Batt-Latch has a wild price tag! Depending on the application, you could probably hack something together with an Arduino and a servo or something. Looks like that device can hold a lot of pressure though so matching that may be tough. And then there's waterproofing...
Have you ever played with Arduino?
The other devices you speak about are a little bit outside of my domain but somebody may come along with some ideas!
I wonder if there is a kind of balance that can be had. I think a traditional licensing model could end up being more trouble than its worth. Companies like Apple spend more on legal fees than R&D!
One solution is that the developer try to maintain an online storefront, but to outsource actual production and fulfillment as much as possible. Perhaps this means a one month lead-time for these types of mechanical projects.
Granted that it takes more involvement than licensing, but it gives the developer a stronger "brand-name" helping them compete against possible knock-offs. It benefits the developer too because they have direct customer contact and feedback this way. Its certainly money well spent compared to legal fees.
Work could then still be released open-source, but periodically allowing the developer to arrange parternships for distribution. Openness for physical tools is less of a catalyst for parallel development since they have more barriers than that of software. Generating an identical build to someone else's is exceedingly difficult. On the other hand, providing kits so that co-developers can exist may be a revenue stream in itself.
This looks very cool! Looking at things, I understand you space issue. Bladders or something to store water beneath the pallets seems a good idea. Hanging something from the hoops inside might block the sun for your plants though?
Maybe you could design a system to circulate water outside during the day to capture sunlight and heat.
So you're doing:
Panel -(1)-> 12V Battery -(2)-> 115V AC -(3)-> Appliances
Seems like you have (2) and (3) pretty well figured out. The inverter is definitely right I take it the bucket and base both have standard outlets for 115-120V AC.
I would wonder about (1) on the input side (the output to the battery makes sense). Specifically, what are the min and max voltage panel inputs it expects? Have you selected a panel that matches that?
Now that all the voltages line up, I would think about watts/current (remember, Watts = Current * Voltage). How often does the heater and pad need to be on? How many watts do they consume when they are on?
Given your charger, you can only draw 5W from the solar panels, regardless of voltage. If you always had 5W from solar panels and always had your appliances on, you would need to make sure you only drew 5W, not the 400W maximum that it is rated for.
But your panels aren't always on and I doubt your appliances draw THAT much current, so do the calculation of how much sun you can expect and how much current you will be drawing. You will probably want a timer so that you can switch the appliances on and off.
Also, just a thought, have you looked at solar water heaters? You might get away with more that way. The reason is, all this conversion of electricity gives you an efficiency drops. It's too bad that most appliances need 120V AC because they end up rectifying it and using DC locally. It would be nice to regulate the 12V DC another DC level rather than going DC-AC-DC.
Irrigation Caddy ($180):
Hardware:
- ethernet cable based
- wire up to 10 valves (including master)
UI:
- browser based
- allows user to create up to 4 programs that can then have up to 5 start times
Above is my summary of irrigation caddy. It does seem to have some of the elements that we discussed, but it doesn't include sensors and it is all wired. EZ-VRC (with its own subscription and which isn't even accepting new subscribers) might fill that void but now you have two seperate user interfaces, one for irrigation control and one for sensors. How do you use the sensors to dictate your watering schedule? Build a layer on top of both UI? Not to mention that you're cloud-dependant with this EZ-VRC. Same deal with bringing in wireless - you'd have to hack a black-box and figure out how it works so that you could integrate an Xbee.
The end-result is you've cobbled together a few proprietary devices to make the device you actually want. That solution isn't optimized and it's not scalable. It might work fine for one person and it might work especially fine for Andy since you have everything wired up already, but I am interested in developing an application that can easily be replicated and expanded upon.
An Arduino could definitely be used to do something along these lines. The trick is figuring out how to sense the depth of your tank. Here's one of the first google results I came across which uses pressure sensors.
Then you have to find a way to get the 5V Arduino to actuate your pumps... Relays and such will probably be needed.
Sounds like you wouldn't require an SMS alarm system so you could make a cheaper and more simple system fairly easily. If you wanted to add an alarm though, following the Fido tutorial related to the phone may help.
If you don't know much about Arduinos or electronics, don't worry - it's easy to get started. Adafruit has a great learning system.
RJ and I will be getting in late (11pm or midnight) on Friday night. Two questions:
1) Anybody care to host us? We'll have sleeping pads and sleeping bags so a floor indoors would be fantastic! Email me: thiery.louis@gmail.com
2) If not, how does the Ecovillage camping work? Is there a contact person for that?
Sounds intriguing! I would love to hear about it. Is any documentation still up?
My 5 passenger car will be leaving around 6pm in an effort to meet Ithaca, NY before midnight. Entertainment for the driver, gas, and a lack of farting are expected of passengers.
0. Louis
1. RJ
2.
3.
4.
Hi Andy,
This sounds very interesting to me. I'm currently developing a general purpose long-range, weather-proofed, sensing and automation board. The communication options will include Zigbee (local wireless protocol, longer range, lower bandwith than WiFi) and 3G. The idea is to have real-time monitoring as well as user-determined logic (if sensor A reads above threshold X, do action 1) and schedules.
I would love to hear about this application and any others you may think up. Initially, I was actually thinking more along the lines of your post below which talks about the motorized flaps.
--Louis
Thanks for bringing this up. The component [you mention](https://www.adafruit.com/products/735) is the same that I used and it will do the trick! I edited the tool page to include this.
Thanks for the feedback, Josh! I've fixed up the tool page to try to make things more clear. Here is the section that I think is relevant to your question:
Download the libraries above and unzip them. There should be three individual folders, each containing at least two files, one with a .h suffix and one with a .cpp suffix. Open your Arduino sketchbook folder. If there is already a folder there called libraries, place the library folder in there. If not, create a folder called libraries in the sketchbook folder, and drop the library folder in there. Then re-start the Arduino programming environment, and you should see your new library in the Sketch > Import Library menu.
Once your libraries are properly installed, you should have access to all the relevant code from your Arduino IDE. Please let me know if that *doesn't* clear things up - I'd like to do everything I can to make it easier for folks to build these things!
Good find! To save on anchor costs, I reckon at most three need GPS.
But turn-around does eliminate the need for synchronization at least...
Synchronization won't be too bad since distance will be easier to calculate (even without GPS) since both sides have good & identical clocks. Actually, it would be neat to do this without GPS which makes this system entirely relative until you take some global references from GPS!
Hey guys,
Sorry I'm probably late to the game but I have been tied up moving into a new apartment and office last week. This discussion has made great reading material though!
Just to make sure I've understood, it's settled that a good clock is only needed on the anchor station? Seems like this turn-around technique is a nice solution and will yield an absolute answer for each individual anchor (ie: it will tell you node 32 is 50m away).
I just wanted to offer another idea which I thought came up in one of the discussion threads but I can't seem to find and that's to use ratios:
If you have 3 anchors and they all receive the SAME signal from a node, they will have three different times when they clocked in the message (let's say, 00:01, 00:02, 00:03). The differential in time received will help determine the relative difference of the node (that is, if the node is distance X away from node 3, then it is 2x/3 from node 2, and x/3 from node 1 - a unique point satisfies that relation). I like the turn-around method better since it immediately yields absolute distance and doesn't require synchronization but if that becomes a problem for technical reasons, this could be another approach.
The datalogging shield from Adafruit includes an integrated circuit that provides a Real-Time Clock (RTC). It gets the current time when you upload code. It will use the coin battery to maintain accurate time when the shield is not getting powered.
If you notice that the time isn't being kept properly, it may be the coin battery that doesn't have a decent contact. I had that problem because I didn't put a significant enough blob on the circuit board. Let me know if you are having any issues and I can help you troubleshoot!
The datalogging shield from Adafruit includes an integrated circuit that provides a Real-Time Clock (RTC). It gets the current time when you upload code. It will use the coin battery to maintain accurate time when the shield is not getting powered.
If you notice that the time isn't being kept properly, it may be the coin battery that doesn't have a decent contact. I had that problem because I didn't put a significant enough blob on the circuit board. Let me know if you are having any issues and I can help you troubleshoot!
Indeed! Seems like a good design alternative for those that don't have easy cell phone access. I think also warrants a spot in the documentation at least as a note for now. Perhaps somebody will implement it and provide a little tutorial!
Good point!
I think that would be nice to include in the tutorial. I can write it up when I have a minute unless you'd like to.
PS: Welcome to the community!
Also, I like the sound of the
Also, I like the sound of the categories you listed. Thanks, Dan!