
NetDuino Quadrocopter
#61
Posted 31 January 2011 - 12:56 PM
#62
Posted 07 February 2011 - 04:11 PM
#63
Posted 07 February 2011 - 04:22 PM
Not sure you remember me amidst the crowd of excited devs there, but I showed you videos on my phone of some two-wheeled bots running around on my kitchen table (and not falling off).
Hi Dan, good to meet you again.

Does anyone have experience using the Critical Velocity gyro/accelerometer shield with Netduino? http://www.criticalv...?itemid=shield6
I just glanced at the datasheets, and it looks like all of them output 3.3V signals--so electrically they should be fine. [And even if they output 5V digital signals...you'd still be fine. It's just >3.3V analog signals that you should avoid.]
That said, it looks like the product has been discontinued.
On the broader shield compatibility question:
1. Netduino's analog pins read signals from 0-3.3V, not 0-5V like the AVR used on Arduino. If a shield outputs analog signals, it may need to be modified slightly to output less voltage. Not usually an issue.
2. Netduino's digital pins _are_ 5V tolerant--so electrically pretty much all Arduino shield should work.
3. You will need a driver for some Arduino shields (either C# or C/C++ code). As a corollary, there are a lot of native C drivers written for Arduino (not using Arduino's Processing language)...they just need to be ported to 32-bit ARM.
Welcome to the Netduino community, Dan.
Chris
#64
Posted 07 February 2011 - 04:34 PM
#65
Posted 08 February 2011 - 02:49 AM
#66
Posted 08 February 2011 - 04:25 AM
#67
Posted 08 February 2011 - 05:35 AM
#68
Posted 08 February 2011 - 05:54 PM
#69
Posted 10 February 2011 - 04:48 PM
9DoF (non stick) is not suitable in any way for quad flight without highly optimized firmware. The AHRS FW is not nearly capable of it.
You mean because of the refresh frequency and the fact that it is sending data as ASCII?
Miha Markic, Microsoft MVP C#
Righthand .net consulting and software development
http://blog.rthand.com/
#70
Posted 10 February 2011 - 05:53 PM
#71
Posted 12 February 2011 - 11:16 AM
There are several reasons:
A: As you point out, the stock FS is ASCII. Very, very inefficient
B: The FW is not set up at all for immediate Ask/tell response
C: Even when modded to ask/tell, the IMU will only respond every 25ms, without architecture changes.
I am curios about C, what architecture changes you have in mind?
Miha Markic, Microsoft MVP C#
Righthand .net consulting and software development
http://blog.rthand.com/
#72
Posted 12 February 2011 - 04:31 PM
I am curios about C, what architecture changes you have in mind?
Totally changing the way the 9DoF firmware works.... Frankly, there's not much in there I see fit to really keep other than the math.
#73
Posted 13 February 2011 - 10:33 AM
Totally changing the way the 9DoF firmware works.... Frankly, there's not much in there I see fit to really keep other than the math.
Ah, so you are talking about code. Great.

Miha Markic, Microsoft MVP C#
Righthand .net consulting and software development
http://blog.rthand.com/
#74
Posted 13 February 2011 - 04:00 PM
#75
Posted 17 October 2012 - 03:39 PM
#76
Posted 17 October 2012 - 05:51 PM
Not sure it this project died but there is a rather nice example on The Wolf Bytes blog. You can also find forum postings in the Netduino Go! forum.Hi, did this project die or has it moved?
regards,
Mark
To be or not to be = 0xFF
Blogging about Netduino, .NET, STM8S and STM32 and generally waffling on about life
Follow @nevynuk on Twitter
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users