Bill:
Parts of the Fantom SDK are intentionally obfuscated to protect NI's intellectual property, but the main idea is to offer an easy way for users such as yourself to leverage the Fantom framework. Hopefully I can help you understand how all the pieces fit together. Which files you need depends on whether you are writing C++ code or LabVIEW code.
If you're going with C++, there are headers included in the Fantom SDK (includes/fantom/*.h) to provide an interface for you to compile against. You're right that the example code provided is only included in the HTML and CHM formats, so you'll have to copy and paste into your own text file to compile that code yourself. Once you've gotten your code compiling, you'll need to link against the
*.lib file buried in the targets directory hierarchy (or the
*.framework for the Mac folks). You don't need the DLL until you're ready to run your code. Our assumption was that all Fantom SDK users would have already purchased and installed the LEGO MINDSTORMS NXT Software and Fantom driver, so we didn't provide a duplicate DLL in the Fantom SDK.
As Kjeld pointed out, though, we also included a LabVIEW interface for the Fantom driver. These are the VIs located in [includes/labview/...]. The LabVIEW interface happens to be platform specific, so be careful that you are using the right VIs for your target platform. (If you're developing cross-platform, use the macosx VIs.) If you choose to develop your application purely in LabVIEW, you won't need the header files or the *.lib file. But, you will need the DLL installed as you are developing. Otherwise, the Fantom VIs that access that DLL won't compile, and you'll be staring at broken arrows in all of your application VIs.
I hope this helps. Since we've started to stray a little from the original topic of Bluetooth logging, you might consider starting a new Fantom SDK discussion thread if you have additional questions.
------
James Blair
NI R&D
