gutworks:

http://www.ebay.at/i...=item3ccabf4203

http://www.ebay.at/i...=item5d38c518a0

http://www.ebay.at/i...=item5d36fc4e5f

from what devie on it you read your values?

the gyroscope only tell you the degrees per seconds that its currently turned. so when no movement = no value

the accelerometer tells you its current oriantation (so when reading this you know its angles) and maybe more (i only used it for that: http://www.werkzeugz...017000266_1.jpg - just in digital form)

well, i have the cheapest imu, the gyroscope has a little bit of noise, but the rest of the sensors work as expected, so to know if they are accurate enough for you youd have to compare their datasheets.

i cant guarantee its original parts or just clones, they look original tho for me.

resistor.. did you use a pulldown?

Port.InterruptMode.InterruptEdgeHigh wants an external pulldown resistor.

Port.InterruptMode.InterruptEdgeLow wants an external or the internal pullup resistor.

edit: that doesent count for all devices, but most work that way

when using

InterruptEdgeLevelHigh or

InterruptEdgeLevelLow

you have to call clear interrupt afterwards.

it wount throw another interrupt till you cleared it

no.

the ones without Level clear themselfes

edit: using clear on non level even throws an error according to:

http://msdn.microsof...y/cc532335.aspx

you do not use Cpu.Pins for netduino -.-

netduino has the card detect implemented, and it even throws an interrupt when you enter a card (maybe, i guess) also when you remove it.

in the netmf pwm class you can set an invert boolean in the constructor, so you can use it normally, no matter if its anode or cathode.

first: yes thats only for the plus and plus2.

than: i meant its not Cpu.Pins its just Pins enum.

also, since this is in the plus/plus2 part of the board, i was talking about that.

for the pullups: id suggest using 4.7 kilo-ohm - that worked great for me.

when adding more devices you can lower that, but from my experience most modules have allready pullups included

i havent changed my 4.7k so far, and iam using like 5 devices on the i2c bus

So how does that help with my various errors?

it gives you some knowledge

since hanzibal allready told you about the card-detect pin ...

the try/catch approach you mentioned may work, but i think its better to

check if a sd card is in (set a boolean with the card-detect event, maybe there is allready one?)

and only write data when its actually in.

you sure its damaged? netduino can survice 12v, the regulator is actually rated much higher (but will get a heat problem when you draw too much current)

sure it is, at least my mini supports it. so i guess all v1 boards do so.

there is not that much netduino/netmf specific "commands" (functions) -

its mostly like coding in .net. many many functions are allready ported.

http://msdn.microsof...y/ee435793.aspx

heres a listing of all aviable functions

http://www.netduino....duino/specs.htm

16ma only on 3 pins.

its somehow sad that there are no good/visible links to the specs for the gen1 boards -.-

sry i have no idea what todo, but ping and program running tells me its not damaged.

IMO diving straight into the list of API's is just going to confuse you.

What might be better is to set a few goal applications that you want to make, and then learn new things as you confront challenges.

 

But best case would definitely be to get a basic C# book.

he mentioned he has the netduino book and that he is doing c# lessons, so what else would you point him to than the msdn ?

its also the only correct answer to his question about the functions.

i guess so, it says the min voltage is 3 volts for the inputs, wich netduino can supply.

its also opto coupled, so i like the design

when you want to drive a mosfet directly you have to watch out that its logic level, or it wount completly turn on, get hot and burn.

but this board avoids that with the couplers

my opinoin for the go: its a nice device, but lacking some modules, wonder when they will be aviable.

the plus/plus2 are good allround devices i would say, cos you can play with sd cards and ethernet.

if you are sure you will not want ethernet, the normal netduino or netduino 2 is also fine.

i personally love the mini, cos it fints in a breadboard, and its smaller than a normal size sd card

you can hook up a sd card to it, but ethernet is a pain, that never will work right.

i wonder whats the analoginput class your using is.

the microsoft one want AnalogChannels.yourpin and not Pins.yourpin.

secretlabs one, i _think_ (never used it) wants it the way you have it.

hehe thats a lot of questions, some i can answer:

Would it be possible to build something large? A robotic arm that could pick up things based on their color perhaps?

What would be required to make something like this happen?

first is a yes, second: yes, but it would be a slow arm, since color detection, and any graphical stuff requeis a lot of resources and horsepower.

it also depends on your coding skills.

third: the best way todo this would be connect the netduino to a pc, and let the pc calculate the color/whatever detection stuff

How do you run power to a large motor, but control the logic with Netduino?

you do that with a motor shield and an external power supply.

its made just for that - driving high power motors with the netduinos logic level outputs/pwm's

How would I interface with a sensor purchased from parallax such as the Ping?

sorry i cant tell you how you would do that - but i would read the datasheet, also the one for the netduino and see if its compatible.

than i would ask google or maybe here in the forums if anyone else has done that before - or - if its easy -

just write the code for it.

If I were to purchase a sensor, how would I create a way to interface with it if no documentation for it is available?

dont purchase it. get a cheap one from ebay, and before you buy it, ask google if datasheets are aviable in english/your language.

this one has a lot of very commons sensors/stuff, i ordered a lot from him

hm iam wondering why you bitbang the data, and not use the normal spi/i2c classes, that would be a lot faster and way less code, less errors and such. i dont have such a device so i cant try, but except some really exotic devices all is kinda "standard" that just works with netduino

- ofc the right code for accessing the right registers at the right time is still needed.

connected gnd together?

hmpf.. i thought what i said was clear..

use that:

AnalogInput pot = new AnalogInput(AnalogChannels.GPIO_PIN_A0);

2) why when i type the "SerialPort serialPort = new SerialPort("COM1", 4800, Parity.None, 8, StopBits.One);",

there are red line under the SerialPort.

you have to add a reference: Microsoft.SPOT.Hardware.SerialPort

maybe also system.io

and than using System.IO.Ports;

than your serialports will work.