Openni "One or more of the following nodes could not be enumerated"

user968049 picture user968049 · Nov 11, 2011 · Viewed 8.4k times · Source

I have installed the latest version of openni and NITE in the following order:

Openni 1.3.4.6 unstable development edition x64 NITE 1.4.2.5 unstable develeopment edition x64 Avin2 sensor kinect x64 from ../platforms/win32 directory

I use windows 7 64bit and I have connected Kinect and not using mock nodes. When i try to run an error: "One or more of the following nodes could not be enumerated"

My modules.xml contents are:

<Modules>
    <Module path="C:\OpenNI\Bin64\nimRecorder64.dll" />
    <Module path="C:\OpenNI\Bin64\nimMockNodes64.dll" />
    <Module path="C:\OpenNI\Bin64\nimCodecs64.dll" />
    <Module path="C:\PrimeSense\NITE\Features_1_3_1\Bin64\XnVFeatures64_1_3_1.dll" configDir="C:\PrimeSense\NITE\Features_1_3_1\Data" />
    <Module path="C:\PrimeSense\NITE\Features_1_4_1\Bin64\XnVFeatures64_1_4_1.dll" configDir="C:\PrimeSense\NITE\Features_1_4_1\Data" />
    <Module path="C:\PrimeSense\NITE\Features_1_4_2\Bin64\XnVFeatures64_1_4_2.dll" configDir="C:\PrimeSense\NITE\Features_1_4_2\Data" />
    <Module path="C:\PrimeSense\NITE\Hands_1_3_1\Bin64\XnVHandGenerator64_1_3_1.dll" configDir="C:\PrimeSense\NITE\Hands_1_3_1\Data" />
    <Module path="C:\PrimeSense\NITE\Hands_1_4_1\Bin64\XnVHandGenerator64_1_4_1.dll" configDir="C:\PrimeSense\NITE\Hands_1_4_1\Data" />
    <Module path="C:\PrimeSense\NITE\Hands_1_4_2\Bin64\XnVHandGenerator64_1_4_2.dll" configDir="C:\PrimeSense\NITE\Hands_1_4_2\Data" />
</Modules>

I also tried using the previous version of OpenNI and NITE with the same result. I also entered the license key in SamplesConfig.xml and it has no other changes. It has production nodes for image and depth and thats all.

I would like to know if Avin2 sensor kinect drivers work with latest versions of openni. Whats the order of installation and what driver do i install to make kinect work with openni 1.3.4.6 ?

thanks

-Siddharth

Answer

Alessandro Pezzato picture Alessandro Pezzato · Nov 12, 2011
  1. Check all dll are existing
  2. Check your license key is correct (some modules need a valid license key). Register it with niReg command
  3. Check all configDir are existing, readable, with their config files inside
  4. Stop your program immediatly after context.InitFromXmlFile(strFileName, scriptNode, pErrors) (so you can do next step)
  5. Comment all Module nodes. The error should disapper, but now you have a non working program.
  6. One by one, decomment modules and test if the error appears. Now you know what is the bad module.