Go Down

Topic: Arduino vs Netduino (Read 4591 times) previous topic - next topic

Si

Thanks for your views everyone.

I'm still undecided.

Si.
--
My New Arduino Book: http://www.arduinobook.com

Gadget999

I like the fact the net duino is .net compatible, however I think the arduino can also talk to microsoft studio

i like the fact it is 3 times faster and can support multi threading ?

however is it such a big deal using more than one arduino if they are so cheap ?

what else is out there that is fast and has lots of memory

robtillaart

Quote
what else is out there that is fast and has lots of memory

- FEZ Panda
- mbed
- Maple
to name a few
Rob Tillaart

Nederlandse sectie - http://arduino.cc/forum/index.php/board,77.0.html -
(Please do not PM for private consultancy)

robtillaart

Quote
I think a translation from Arduino to NETduino would be a great thing to have

.NET supports C++ as language so porting code from Arduino to NETduino is not 100% difficult. You need to define the main as it is defined in Arduino core

Code: [Select]
main()

  setup();
  while(1) loop();
}


and a part of the code will compile. More work will be the hardware IO, registers, in theory one only need to rewrite the HW abstraction layer once to be able to compile the libraries. But then still one would have a single thread .exe and miss the added value/posibilities of multithreading of the .NET platform. Still the result could be good enough for many sketches.

Personally I believe more in reuse at design and architecture level than at code level. The current trend of Model Driven Design which replaces coding more and more is a very powerfull one. See for example - http://www.verum.com/ - I don't expect it comes to Arduino soon, but I like to be proven wrong on this one ;)





Rob Tillaart

Nederlandse sectie - http://arduino.cc/forum/index.php/board,77.0.html -
(Please do not PM for private consultancy)

oscarcar

That sounds like UML. An enormous amount of time/effort gets put into the model IMO. There would be no time to actually tinker.

I don't think it's suited for anything that isn't a fully-blown large enterprise product.

robtillaart

Quote
I don't think it's suited for anything that isn't a fully-blown large enterprise product.


check nr 93 and up - http://www.devtopics.com/101-great-computer-programming-quotes/ -  :)

You are right that it is not afforable at this moment but the Arduino you are tinkering with, OMG, Nasa would loved it in the 60's. There are allready effort to develop graphical languages for arduino but these are not mature yet AFAIK.

With MDD you will tinker just at another abstraction level, An Arduino sketch is in fact the model (in C++)  of how you want the information flow to go. Functions you call like digitalRead() are abstractions of C++/ assembly calls ...



Rob Tillaart

Nederlandse sectie - http://arduino.cc/forum/index.php/board,77.0.html -
(Please do not PM for private consultancy)

knuckles

netduino has promise but a lousy toolchain ,but it has promise in the future sometime ,meanwhile stick with arduino

cjdelphi

Maybe netduino vs arduino due is a more of a fair match...

I prefer the hardware side over software and your basic Arduino uno allows me to quickly test and interface with older 5v chips like the 4000 series, eg blink with delay with nice clean edges,  otherwise I'd have to create a 555 or logic oscillator circuit calculate the capacitor and resistor value... well I used to before arduino! Lol

Using arduino to test logic chips, I find an uno to be like a swiss army knife, if I wanted to cut down a tree I'd swap the swiss army knife for a chainsaw, a due or higher.

Go Up