From: Zi Y. P. <pz...@um...> - 2013-01-25 19:34:43
|
Hi all, Anybody has any experience/success with integrating VN-100 with Gumstix, either via SPI or UART? New to gumstix, would appreciate any advice! |
From: Chris G <chr...@qi...> - 2013-01-28 21:27:24
|
I've interfaced a VN-100 using a UART with a different processor, not a Gumstix. It was a while ago, but if I remember right, VectorNav provides a good ANSI C reference driver along with math libraries and so on-- check the bottom of [1] and the "Embedded Firmware Library User Manual" at [2]. There are some blanks to fill in in the code, but the documentation is actually pretty good. It was too long ago for me to remember many details, but there you have it. As long as you have your UART or SPI bus working (and with the appropriate level shifters), you should be all set. [1] http://www.vectornav.com/products/vn100-rug?id=78 [2] http://www.vectornav.com/products/vn100-rug?id=55 -- View this message in context: http://gumstix.8.n6.nabble.com/VectorNav-VN-100-IMU-with-Gumstix-tp4966623p4966637.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Curtis O. <cur...@fl...> - 2013-01-28 21:36:41
|
On Mon, Jan 28, 2013 at 3:27 PM, Chris G <chr...@qi...>wrote: > I've interfaced a VN-100 using a UART with a different processor, not a > Gumstix. It was a while ago, but if I remember right, VectorNav provides a > good ANSI C reference driver along with math libraries and so on-- check > the > bottom of [1] and the "Embedded Firmware Library User Manual" at [2]. There > are some blanks to fill in in the code, but the documentation is actually > pretty good. It was too long ago for me to remember many details, but there > you have it. > > As long as you have your UART or SPI bus working (and with the appropriate > level shifters), you should be all set. > > [1] http://www.vectornav.com/products/vn100-rug?id=78 > [2] http://www.vectornav.com/products/vn100-rug?id=55 I'll second that. The uart interface is really straightforward. From my experience, I would suggest using that unless you have a very compelling reason you must use SPI. If you start with the uart interface and your life will be much easier. I've implemented the SPI interface as well, but it involved an awful lot of work and learning and experimentation (for me) to get up to speed on many of the subtle performance and timing nuances of doing SPI in Linux not to mention tearing my hear out for quite a while over some basic hardware connectivity and level shifting issues (buying bus pirate to debug, etc. etc.) It was one of those situations where I had to learn and figure out really much more than I wanted to about SPI. You are dealing then with kernel space vs. user space and bottlenecks and performance issues start popping up all over the place. I'd say more, but all this happened > 6 months ago so this is about all I remember without going back and digging through code and hardware again. Scott @ jumpnowtek.com provides some marvelous SPI tutorials so that's where I'd suggest you start if you ignore my first advice about sticking with the uart interface. :-) Regards, Curt. -- Curtis Olson: http://www.atiak.com - http://aem.umn.edu/~uav/ http://www.flightgear.org - http://gallinazo.flightgear.org |