Arduino or Netduino
#1
Posted 07 September 2010 - 10:37 PM
#2
Posted 08 September 2010 - 12:53 AM
Today LED's, tomorrow, the world!!! Well, OK, maybe servos.
#3
Posted 08 September 2010 - 02:26 AM
#4
Posted 08 September 2010 - 02:35 PM
#5
Posted 08 September 2010 - 02:59 PM
Thank you Eric and Matt for your respective responses. In looking at this a little more I think I am going to do both :-) Once I have got beyond my "basics re-education" (spent last night playing with relays and transistors, etc like a little kid all over again!!!), I will probably purchase an Adruino and some shield (just for the fun of it). But then I figure that for the sake of $35 I can't go wrong by buying a Netduino as well and see where that leads. I am almost certain (hardly even need to look!) that I will much prefer the Netduino development environment so, after I have played with both for a while, it will be interesting to see which one "wins".
It seems to me that the challenge Netduino has right now is gaining a certain critical mass in terms of mindshare - books, community, web sites, etc. Get past that point and I hope it has a bright future.
By the way, out of interest, to what degree is Microsoft aware of / supporting this?
Thanks.
Mark
Mark, I would almost say that there's more "mindshare" for the .net micro framework devices than Arduino. Not as much in the hobbyist market yet but in embedded for sure. MS has continued to develop and improve the .NetMF (and much as I hate MS they seem to have done a good job here) and there are a couple of major providers of .NetMF embedded hardware like Secret Labs, GHI and others.
The main "drawback" to .net devices is the fact that it's not a real-time OS. For 98% of what people do with them this isn't an issue but for the 2% where it's an issue it's a REAL issue. Some of that can be taken care of with native code but it's something to think about.
Personally, as a network engineer/software guy, I prefer the .NetMF stuff because it's "easier" for me to work with.
There are also a couple of .NetMF books out there - one from MS called "Embedded Programming with the Microsoft .Net Micro Franework" and the other is "Expert .Net Micro Framework" from Apress. I prefer the second one personally.
#6
Posted 08 September 2010 - 03:22 PM
Thank you Greg. You make a good point about .NetMF and one I had not considered. Your response certainly interested me more in the potential of Netduino. And, of course, some more questions :-)Mark, I would almost say that there's more "mindshare" for the .net micro framework devices than Arduino. Not as much in the hobbyist market yet but in embedded for sure. MS has continued to develop and improve the .NetMF (and much as I hate MS they seem to have done a good job here) and there are a couple of major providers of .NetMF embedded hardware like Secret Labs, GHI and others.
The main "drawback" to .net devices is the fact that it's not a real-time OS. For 98% of what people do with them this isn't an issue but for the 2% where it's an issue it's a REAL issue. Some of that can be taken care of with native code but it's something to think about.
Personally, as a network engineer/software guy, I prefer the .NetMF stuff because it's "easier" for me to work with.
There are also a couple of .NetMF books out there - one from MS called "Embedded Programming with the Microsoft .Net Micro Franework" and the other is "Expert .Net Micro Framework" from Apress. I prefer the second one personally.
- What is the relationship between .NetMF and what I can use on the Netduino? Assuming hardware support, do I get the "full" .NetMF?
- Although I doubt I'll fall into the 2%, what is a good example of where I'd miss the benefits of a real-time OS?
- Can you put event handlers in context for me (I am used to this at a higher level, through ASP.Net)? I note that Netduino supports event handlers. Does Andruino not offer this (this would seem like a big deal to me, for detecting pin changes, etc)
- Can I assume that neither Netduino or Arduino offer multi-threading?
- Looking down the road a bit, let's say I get into Netduino and then want to do more. What is the logical next step?
Thanks again, Greg.
Mark
#7
Posted 08 September 2010 - 03:32 PM
Thank you Greg. You make a good point about .NetMF and one I had not considered. Your response certainly interested me more in the potential of Netduino. And, of course, some more questions :-)
- What is the relationship between .NetMF and what I can use on the Netduino? Assuming hardware support, do I get the "full" .NetMF?
- Although I doubt I'll fall into the 2%, what is a good example of where I'd miss the benefits of a real-time OS?
- Can you put event handlers in context for me (I am used to this at a higher level, through ASP.Net)? I note that Netduino supports event handlers. Does Andruino not offer this (this would seem like a big deal to me, for detecting pin changes, etc)
- Can I assume that neither Netduino or Arduino offer multi-threading?
- Looking down the road a bit, let's say I get into Netduino and then want to do more. What is the logical next step?
Thanks again, Greg.
Mark
I'm sure that Chris Walker will chime in here at some point with a lot more detail. He's a much better source than I am! I'm a simple network guy so I don't pretend to understand a lot of this stuff.
1. You can use the full .netMF but not everything is available in the firmware - I know there have been some posts about stuff not currently enabled so I'll let Chris provide details. I may be totally wrong on this point too.
2. Think of an event handler as just code waiting to execute. So you define an event handler and then go about your business in your code (threads). If an event is "raised" by the CLR then your handler executes. I believe (and again, I could be wrong) that event handlers spin up their own thread when they are raised.
3. The .NetMF is multi-threaded but it's cooperative (ie, 2 threads don't execute at the same time since the microcontroller isn't multi-core) - but they are distinct threads.
4. Depends on what you want to do - from a hardware perspective Chris Walker has said that Secret Labs is coming out with new products Real Soon Now. You can also look into the Fez line of .NetMF supporting microcontrollers (www.tinyclr.com). There's also no reason why you couldn't have more than one microcontroller in a project - just wire them together so they can talk to each other and keep going. Our biggest thing right now is getting microcontroller boards that actually expose all the IO pins. For example there's a lot more GPIO available on the ATMEL chip that isn't exposed on the board. That's one of the things we're ("we're" being the community) hoping Secret Labs addresses with new products - think of a Netduino mega with a lot more IO pins.
#8
Posted 08 September 2010 - 03:52 PM
Thanks Greg - very helpful again. Sorry that I wasn't clear on the event handler question. I am familar with the general concept of the event handler (as I mentioned, I use this a lot in the ASP.Net world). My question was more about whether I should expect this on both Netduino and Arduino. My guess is that the concept of an event handler is a very useful one in the physical computing world to allow a project to respond to external events from sensors, etc. The alternative to event handlers, I would assume, would be to have to loop/poll through pins and then respond by calling subroutines "manually" from the polling loop. If Netduino supports this and Arduino does not then that would be a rather large pull for me towards Netduino, since the event handler approach seems more efficient to me. But I may be grasping at straws - perhaps all such hobbyist platforms support event handers. Can you clarify?2. Think of an event handler as just code waiting to execute. So you define an event handler and then go about your business in your code (threads). If an event is "raised" by the CLR then your handler executes. I believe (and again, I could be wrong) that event handlers spin up their own thread when they are raised.
Good to know that co-operative multi-threaded support is available.
Beyond all this, I am really looking forward to coming up with the project idea that will really stimulate my interest. I work better with a "goal" and know I won't get to sucked in with a basic "flahs some LEDs" or "play Whack-A-Mole" type project :-)
Thanks again, Greg.
#9
Posted 08 September 2010 - 05:10 PM
#10
Posted 08 September 2010 - 05:11 PM
#11
Posted 09 September 2010 - 03:44 AM
#12
Posted 09 September 2010 - 04:50 AM
They both ran out yesterday--sorry about that. MakerSHED will be getting more within 2 business days. Proto-Advantage ships to both the USA and Canada (and I've heard that their shipping is very affordable).Anyone know when the shortage in the US will be addressed? Or if there are any other suppliers beyond Amazon and MakerShed?
You could use the Adafruit GPS shield (and even store data on its SD card using the new v4.1.1 alpha firmware). Check out the Compatible Shields and Accessories thread for a bunch more.One more thing - just to get me started I'd be interested in any suggestions for Arduino shields that might be worth ordering to increase the first impression "wow" factor :-) and happen to work fine with the Netduino. I'm interested in doing something (anything really, initially) beyond just lighting up an LED :-)
Looking forward to seeing what you build with your Netduino,
Chris
#13
Posted 09 September 2010 - 05:54 AM
#14
Posted 09 September 2010 - 06:10 AM
#15
Posted 09 September 2010 - 06:53 AM
Thanks again, Chris. I bit the bullet and both the Netduino and an AdaFruit protoshield are on their way to me. I'm eager to get them :-)Hi Mark,
Most of the proto-shields are similar. I don't know of any that won't work with the Netduino. We've used the Adafruit one here.
You can stack shields--you just can't use the same pins on different shields. For instance, if you use pin D2 (digital 2) on a shield, you can't also use that pin on a shield on top of it--or you'll get signal collisions.
Note that this only applies to stackable shields. Some 3rd-party shields are not stackable, as you'll note in their photos.
Chris
Thanks.
Mark
#16
Posted 09 September 2010 - 06:55 AM
We'll be here to celebrate your accomplishments along the wayThanks again, Chris. I bit the bullet and both the Netduino and an AdaFruit protoshield are on their way to me. I'm eager to get them :-)
Be sure to let us know when you get your gear, your first impressions, etc.
#17
Posted 10 September 2010 - 12:47 PM
Take a seat, I'll be right with you.
#18
Posted 10 September 2010 - 03:22 PM
Can you expand on this a little (bearing in mind I do not have a Netduino - mine is on on it's way - and have never even played with an Arduino).I would say, the biggest downer I have with the Netduino is the low sink / source capability of the pins. 8mA per pin IIRC. For all things digital, that's fine but I've used them for other things like the simple LED and using digital pins to power sensors (I can turn them on and off that way).
Is the implication that for "other" boards (Arduino) the current from the pins is often large enough to actually drive sensors and the like but, with Netduino, I'll need an additional power source whenever I have something hooked up to a pin that I'd like to control?
Thanks.
Mark
#19
Posted 10 September 2010 - 03:44 PM
Can you expand on this a little (bearing in mind I do not have a Netduino - mine is on on it's way - and have never even played with an Arduino).
Is the implication that for "other" boards (Arduino) the current from the pins is often large enough to actually drive sensors and the like but, with Netduino, I'll need an additional power source whenever I have something hooked up to a pin that I'd like to control?
Thanks.
Mark
Negative - I use all my sensors powered from the board - most have a Vcc input that you plug into the 5V or 3.3V pin depending (and also into GND). A few sensors will draw power straight from the GPIO pins, and also things like LEDs will do that. But sensors, almost universally, will power from the 5V or 3.3V power bus.
#20
Posted 10 September 2010 - 03:57 PM
Netduino (AT91SAM7X512) has the following output current capabilities:Can you expand on this a little (bearing in mind I do not have a Netduino - mine is on on it's way - and have never even played with an Arduino).
- 16 mA digital pins 2, 3, 7,
- 2 mA analog pins 0 - 3 (in digital mode)
- 8 mA other pins
- 200 mA total DC output current on all I/O lines of the package (absolute maximum rating)
- 40 mA per I/O pin
- 200 mA total DC current VCC - GND
You need a current booster (transistor, power shift register, Darlington array etc.) for Netduino to drive a device that draws more than the pin can provide - for example, you can safely drive a LED at 10 mA on digital pins 2, 3, 7, but you cannot drive (e.g.) 30~50 mA IR LED directly. Always check the datasheet (!)I'll need an additional power source whenever I have something hooked up to a pin that I'd like to control?
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users