Member for

13 years 6 months

Comments

Forum comment

Took me all day to cook this idea up apparently: What else has an LCD and a keypad that we already interface with Fido? A cell phone! I think that the first run should be programmable via cell phone with an *optional* LCD display so that you can check temp without texting when you're physically near the device. The cell phone that initially texts Fido will become the "owner" and will need to confirm reprograms from different phone with an option of relinquishing ownership. A hard reset will also allow Fido to get a new owner. A shield with keypad and LCD can be a later elaboration on Fido v1. Sound reasonable?
Forum comment

The [RGB LCD Shield Kit](https://www.adafruit.com/products/714) not only reduces pins to the two I2C pins, which is the exact same as the [I2C backpack](https://www.adafruit.com/products/292) we're currently using, but it also has buttons! The [port expander](https://www.adafruit.com/products/732) used on the RGB shield seems like it could handle our keypad just as easily as it could handle those 5 buttons, plus it's not a surface mount device (SMD) so it's big enough for a hobbyist to wire up easily. It would probably end up costing the same if we build on our shield since we could then drop the I2C backpack since our shield will handle that too; downside is that it will be more difficult to make. LEDs would work to let you know that the device is running and in alarm mode or not, but I think that it basically reduces the "reprogrammable on the fly" feature of our product to none since how can you input a temperature or a phone number using just an LED for feedback? It would require teaching users some kind of color code for numbers and that doesn't sound user friendly at all. Plus, how do they know if they're reprogramming the bounds or the phone number or something else? Stripping down the device to no LCD and no keypad is definitely a cheaper alternative though.
Forum comment

Thanks for the summary RJ - this is all right on! 1 is pretty straightforward and requires no more development based on our current objectives. 2 is definitely an option, would require very little extra development but requires a lot of wire even if you want to hook up two neigboring greenhouses to one Fido since you basically have to find a relatively central location and then run three wires to each sensor - luckily these are digital sensors so the resistance in the wire isn't an issue as long the signal still makes it through. 3 is also technically viable but as you pointed out, is quite a big change on the development side. How do we tackle the "wireless" part of the sensors? Xbees? WiFi? something else? The money spent making these things wireless would probably be at least as much as simply building seperate Fidos. This is a type of architecture I am foreseeing for the wireless node system that relays data via internet, however!
Forum comment

I included an example on the Tool page of a [project](../tools/fido-greenhouse-monitoring-text-message-alerts#wiki) that I'm currently working on where I link to a wiki about myself (vain, I know). I'll try to explain it here though. Currently, you can format your forum posts, wiki entries, and the main body of tools using Markdown Syntax or HTML - those are two common syntax that you may run into in lots of places on the web. Markdown is especially convenient for links. This is how you do a link for Farmhack: \[FarmHack\]\(http://www.farmhack.org\) Now when you're pointing someone to other places on the site, there's an even shorter way to give links! Let's say I want to point you to the tool page like I did above, I wrote: \[project\]\(../tools/fido-greenhouse-monitoring-text-message-alerts\). The "." prefix is basically a way of telling the browser to go from where I am (farmhack.org/forum) and adding another "." to it backs it up to the parent directory (farmhack.org). Then you continue to write the URL how you normally would.
Forum comment

I've noticed this issue too when uploading files although I was able to recover my text when I hit the back button. I tried multiple times until it went through and eventually it worked... I have no idea what could be causing it but RJ might have an idea when he has a minute!