Only trouble with those PING))) type sensors is that they are a bit tricky to interface with NETMF. You’ll have to use a Tristateport and your reads may be skewed a bit depending on how fast NETMF processes the interrupts.
This is a very good reason why we need a native level PulseIn() type method
the ping sensor driver works very good that is posted on fezzer. they go out to 3m only though. You should look into the maxbotix sensors Plenty goto that range and its a simple as reading a analog voltage, pwm or serial communication.
Thanks all!
I went trough the specification and it looks like all of your suggestion fit my needs.
Unfortunately they won’t be as plug and play as FEZ components
since, per my understanding they all require an handler written in native code.
Then the handler shall be interfaced to .net in someway. as Chris says, they look to be tricky
Hence, I guess the choice will be the easiest to interface. So far I am still understanding which one.
Do you know if there is any example of code for handler+ .net interface anywhere?
You don’t need handler (in native code) for I2C. It’s allready writen and implemented by GHI. All you need is 3 wires (Clock, data, ground) from sensor to board.