The Netduino forums have been replaced by new forums at community.wildernesslabs.co.
This site has been preserved for archival purposes only
and the ability to make new accounts or posts has been turned off.
That is cool -- i think for this project, that might be cheating -- I think we'd need to get an ND+ playing the role of Yaler.
I have'mentioned in the my previous reply, we can get the led params from the link. So why do we even need the firewall stuff??
I am realy busy this week so I guess I'll have to wait couple of days more to get hands on..
I have'mentioned in the my previous reply, we can get the led params from the link. So why do we even need the firewall stuff??
I am realy busy this week so I guess I'll have to wait couple of days more to get hands on..
Vincent
My concern with your link is that it involves using an extra server to store and pass data that is not an netduino -- i think we should keep it as purely about the netduino plus as possible.
My concern with your link is that it involves using an extra server to store and pass data that is not an netduino -- i think we should keep it as purely about the netduino plus as possible.
Hey Bill,
Actually we will need a server anyway to list down all the ND+ devices ( I dont think a p2p network is feasible option). So what we can do is ,retrieve list of all ND+ and then connect then using sockets. But then nobody can predict if multiple ND+ are connected to one device and one trying to turn LED and other is trying to turn it off. I know this isnt much practicle. but just a thought...
my point is that I think an ND+ could (should?) play the role of the server. I do agree that most of the ND+ should be as bare bones as possible, so blinking an LED is a great starting point.
my point is that I think an ND+ could (should?) play the role of the server. I do agree that most of the ND+ should be as bare bones as possible, so blinking an LED is a great starting point.
I belive this can be done. In the given case we will need to rely on javascript for most of the operations and we will need to write the incomings to a file on SD card. I know this will re really really slow but doable.
Anybody wants to work on a small flat file db for ND? I dont think we can port sqlite to ND.
As a first step to get going how about a traditional server that Netduinos could start checking into? I thought the idea of a Google map overlay showing where all the Netduinos are was brilliant!
Once we have that working,we could then try using a Netduino as a server. Sort of crawl before you walk before you run....
The p2p idea is an interesting one. I like the idea of borrowing some ideas from the torrent protocol, where the central server (the tracker) is essentially just a phone book, telling you where the other clients (the peers) can be reached.
On another (related) note.
The devices could simply pass around data about their environment, (gps, temperature, humidity, barometric pressure, light intensity, true-random noise) then pass whatever they have around to the others (including the data they collected for everyone else), which would allow each individual Netduino to create it's own maps or charts.
On another (related) note.
The devices could simply pass around data about their environment, (gps, temperature, humidity, barometric pressure, light intensity, true-random noise) then pass whatever they have around to the others (including the data they collected for everyone else), which would allow each individual Netduino to create it's own maps or charts.
That could be difficult for two reasons. Not all of us have temp sensors, gps, ... Also memory issues with passing around lots of other people's data.
That could be difficult for two reasons. Not all of us have temp sensors, gps, ... Also memory issues with passing around lots of other people's data.
Maybe we can pass one character each?
I thought we'd specify a simple spec, something like {client:aaa.bbb.ccc.ddd,data:{gps:'12.233,92.259'}} (JSON is nice ), should be small enough to store several thousand records. Or even CSV (smaller but much harder to parse when you don't know all the params to expect). Further if you only have 1 sensor you send just that value, if you have 12 you send all 12.
I thought we'd specify a simple spec, something like {client:aaa.bbb.ccc.ddd,data:{gps:'12.233,92.259'}} (JSON is nice ), should be small enough to store several thousand records. Or even CSV (smaller but much harder to parse when you don't know all the params to expect). Further if you only have 1 sensor you send just that value, if you have 12 you send all 12.
Although it is nice that we think of all these complex things to do (send certain data), we still need to figure out how to actually get them to talk to each other, so if this is something that we are seriously doing (i want to!) we first need to decide on a method for the actual communication. Then we can all have a vote on what to send or whatnot.
Although it is nice that we think of all these complex things to do (send certain data), we still need to figure out how to actually get them to talk to each other, so if this is something that we are seriously doing (i want to!) we first need to decide on a method for the actual communication. Then we can all have a vote on what to send or whatnot.
I'd love to get it simpler than that. I'd dearly love my Netduino, after reading temp from a DS18B20 to simply send my website http://www.xxxxx.xxx/?A1234.
This may seem simple to a lot, but it's stumped me for days. I finally got my website to acccept, and parse and refresh the temp box on the mainpage with that line, but I can't get it sent.
I don't want complexity, and great options. I want just that line. Isn't it possible to have a method for ANY Netduino Plus, that when fed a URL , will send it?
Probably just whining, but after chasing one of my own stupid errors for two days, I'm beat !
Retired -stone sculptor -macro photographer- novice but avid Go player - Geek
I'd love to get it simpler than that. I'd dearly love my Netduino, after reading temp from a DS18B20 to simply send my website http://www.xxxxx.xxx/?A1234.
This may seem simple to a lot, but it's stumped me for days. I finally got my website to acccept, and parse and refresh the temp box on the mainpage with that line, but I can't get it sent.
Frank,
Have you looked at the SocketSample sample app which comes with the .NET MF 4.1 SDK? If you pass it that line as a URL, it should "request" that page--and you can just throw away the response. Make sure that you disable the proxy server in that sample.
Have you looked at the SocketSample sample app which comes with the .NET MF 4.1 SDK? If you pass it that line as a URL, it should "request" that page--and you can just throw away the response. Make sure that you disable the proxy server in that sample.
Chris
Never knew they were there ! Thanks, that should help, AND the new update to the Getting Started with the Internet of Things was just released at Safari and it looks like another great source of stuff I never knew !
Thanks Chris.
Retired -stone sculptor -macro photographer- novice but avid Go player - Geek
I was just wondering if this project got off the ground at all. I am interested but I have a Netduino with an Arduino Ethernet Shield. I think the central server as the gate keeper with all netduinos communicating over port 80 would be the easiest to get going. I have been experimenting with a simple publish/subscribe messaging system that might work well on this project, but it is in it's early stages. Currently my message broker is just a console application that accepts subscriptions and publications. When a publish message comes in it routes the message to any subscribers. This is working on an internal network with 1 netduino. My goal was to have multiple netduinos passing messages around in a home automation project. In it's current state it wouldn't be able to find netdunios behind a firewall unless someone had port forwarding enabled on their router. But it might be able to be modified to have the netduino open an outbound connection and keep the connection open while the server passes messages to it. Now I am starting to get a little too complicated though:)
In an effort to kickstart this and keep it simple, may I suggest we use a channel on ThingSpeak (www.thingspeak.com )?
They have a utorial on how to get a Netduino Plus to submit data, and it looks like it would be rather easy for us to share a channel that everyone could read and write to share and pass data.
What do you think?
PS: See seperate thread on ThingSpeak in this forum.
In an effort to kickstart this and keep it simple, may I suggest we use a channel on ThingSpeak (www.thingspeak.com )?
They have a utorial on how to get a Netduino Plus to submit data, and it looks like it would be rather easy for us to share a channel that everyone could read and write to share and pass data.
What do you think?
PS: See seperate thread on ThingSpeak in this forum.
As a first step to get going how about a traditional server that Netduinos could start checking into? I thought the idea of a Google map overlay showing where all the Netduinos are was brilliant!
Once we have that working,we could then try using a Netduino as a server. Sort of crawl before you walk before you run....
I like that idea... something that would do a mashup of Google or Bing maps... and your Netduino.
