Go Down

Topic: Netduino (Read 10 times) previous topic - next topic

Coding Badly

I can think of three big differences between the two...

1. Garbage collector.  There are a few forum participants who are big fans of FEZ.  I've asked how the garbage collector effects the application and the answer has been vague.  In the extreme case, the application stops running while the garbage collector does its thing.  In the best case, the garbage collector and the application run in parallel but this could still starve the application.

2. Libraries.  If the Netduino lacks support for a piece of hardware you want to use it is very likely you will be the one writing the library.  My experience with Microsoft in these situations has been annoying.  Typically, their documentation is incomplete so a great deal of time is spent researching basic things (e.g. What is valid for this parameter?  Why does this API call return this error code?).

3. Delivery / Final Product.  It is possible to get an application working on an Arduino, remove the processor, do a bit of soldering, and have a stand-alone product.  For a few dollars the processor can be replaced and the whole process repeated.  It is very unlikely the same thing can be done with the Netduino (or FEZ).

There are certainly some things that an Arduino is not going to be able to do.  My attitude is: use the best tool for the job.


Good points Coding, especially number three.

Its just that i am extremely fond of C# - though i learned a good deal of C with Arduino..
The thing just is i like the environment of VS much more than the Arduino IDE (thats why i dont use it anymore) and this, together with C# is just wonderful.. but then again, your points are more than valid...
Believe me, Mike, I calculated the odds of this succeeding against the odds I was doing something incredibly stupid[ch8230] and I went ahead


Why is it that people come out with things like this, saying how much more powerful it is then the Arduino (which computationally it is), then limit the whole affair by making it the same pinout as the Arduino?

The number of pins on an UNO (and previous models!) are limited because the chip itself doesn't have that many more. Even the Arduino team provided most of the outputs on the Mega versions, which to be honest is where I see most of these "Arduino replacements" competing.

Why not, to keep shield compatibility, have the pins where the Arduino shields normally are, then run a second set of pins on the outside of those. That way the board is only marginally bigger then the Arduino, keeps the compatibility with existing shields, yet allows access to the additional IOs. Maybe it hasn't been done as there may not be enough space on the board. If that is the case then okay, but why not put a header at the bottom to break out the rest of the pins, even if it means making the board longer?

As already mentioned, if you are planning to say it is compatible/replacement then it should also use the Arduino's multi-platform language and environment. After all both are open source are they not?

I have been looking at the mBed system. It isn't trying to be a Arduino wannabe, maintains much of the power and outputs of the ARM and is multi-platform (if only because it is all online). The problem I have with the mBed is that it is online only, I guess because they are using ARMs commercial compiler and this is an easy way to only have to buy one copy! :lol:

Sorry to rant a bit there :-[ I love the Arduino for its ease of use, both hardware and software working together and not having to jump around different programs plus the great documentation which has actually allowed me to have a greater understanding of C (more then I have ever had from reading books about it :-)). I used to do PICs but the Arduino has killed that off because I got tired of programming a chip then having to remove it from the programmer, then put it into my test board etc etc. I do really want to get one of these ARM based versions but none have what I have come to love about the Arduino and I don't want to have to learn a variant of C as I am just getting my head around C itself  ;D


Personally, I think the Netduino is awesome.  I love C# and I think that Visual Sutio 2010 is the best programming environment available.  I like that it's 32 bit and beefed up a bit and is compatible with existing arduino shields.  Plus, being able to program it in C# is a huge plus.  

As soon as I heard about it, I ordered one and loaded up the development tools.  I've already ported my code from C to C# and am ready to testit out once the thing arrives.

I think the release of this is one of the great things about an open platform.  SOmeone can take it in a new direction.  IF you aren't interested in this new direction, stick with Wiring and the Arduino environment, if you like C# and want to go that route, go ahead.

THanks Secret Labs.


Netduino was cheaper than FEZ - until FEZ came out with Panda.  I recently purchased a Netduino and a Panda.  Both are good environments with solid support and a good forum.

My take is FEZ is more mature but I also like the netduino community as well - so not taking anything away from netduino.

I was able to port over code pretty easily (small apps).  If you need raw pin speed - neither one is good.  Outside the pitifully slow pin write speeds - they seem like a nice alternative if you need more memory than a mega provides.

Personally .. I am going to buy go with a mega and see if I get over my arduino limits that way before I continue down the MS path.  

That said .. I can say in under a week, the move into this environment was not bad and in some cases is was "freegin easy".  If you are working with standard SPI and the like, you may not hit the same speed issues I did.

Pretty interesting movement - jump in if it feels right - It won't hurt :)

Go Up