i recently brought kinect sensor. As per system requirement i purchase desktop . Now followed installation mentioned bellow link. I also downloaded verification link. when check installation it giving me below error. let me know how to sort it out
i already tried reinstal directx 11 download from Microsoft & restarted computer. but i found in device manager only one part is detected. kinect sensor information not avilable.
please let me know what wrong i am doing here
install link
kinect verifier link
You need to buy a faster GPU that supports DX11.
According to:
http://www.game-debate.com/hardware/?gid=326&graphics=GeForce%20210%201GB
http://www.tomshardware.co.uk/answers/id-2297019/play-directx-supported-games-geforce-210.html
your Geforce 210 only supports up to DX 10.1, as is also shown in
your first screenshot as Direct3d API version.
Related
I am trying to install the CUDA toolkit in order to be able to use Thundersvm in my personal computer.
However I keep getting the following message in the GUI installer:
"You already have a newer version of the NVIDIA Frameview SDK installed"
I read in the CUDA forums that this most probably results from having installed Geforce Experience (which I have installed). So I tried removing it from the Programs and Features windows panel. However I still got the error, so my guess is that the "Nvidia Corporation" folder was not removed.
In the same question, they also suggested performing a custom install. However I could not find any information on how to do a custom install of the CUDA toolkit. I would really appreciate if someone could explain how to do this custom install or safely remove the previous drivers. I thought of using DDU but I read that sometimes it may actually lead to trouble.
I had the same problem while I was trying to get TensorFlow to use my NVIDIA GTX1070 GPU for calculations. Here's what allowed me to perform the CUDA Toolkit installation on my Windows 10 machine.
As the error message in the installer says - you already have a newer Frameview SDK installed. It was the case for me.
Go to Settings/Uninstall or modify programs.
Remove the NVIDIA Frameview program. It should be there with GeForce Experience, PhysX, etc.
Uninstalling only this NVIDIA program didn't cause any driver problems for my machine and I was able to progress through the CUDA Toolkit installation.
I just met the same problem and fixed it now.
This problem occurred because you chose the default installation configuration, which might contain many installed parts. In my situation, I have installed NVIDIA Nsight Compute, which is the culprit during the first few installs.
Unchecking the redundant parts should be helpful.
I`m facing issue that with OSDK-ROS 3.7 and 3.8, I could not run demo_flight_control sample correctly
After api auto taking off in the simulator, the drone just stuck there. And there is command being published to the flight_control ENU topic.
The GPS based demo_mission has no issue. It can auto fly to the coordinate.
The hardware and firmware version I`m using is
STATUS/1 # parseDroneVersionInfo, L729: Hardware = A3
STATUS/1 # parseDroneVersionInfo, L730: Firmware = 3.3.8.47
The minimal sample for reproducing the issue is from here
https://github.com/dji-sdk/Onboard-SDK-ROS/tree/3.8/dji_sdk_demo/src
The flight_control issue is the same for OSDK (option b) and OSDK-ROS (default)
For Previous 3.3 3.5 3.6 I never encounter this before. I`ve send report to dev#dji.com. No response yet
I solve the problem by myself
On https://github.com/dji-sdk/Onboard-SDK-ROS/tree/3.7 and 3.8 reqires at least 1.7.6
But I can't find it 1.7.6 in the DJI assistant 2 firmware only 1.7.7 and 1.7.5. So I decided to use 1.7.7
But 1.7.7 does only work for GPS waypoint mission and does not support setpoint_generic based control
So the solution is to use 1.7.5 to get both GPS based mission and ros topic based velocity control working.
Below this version, the version control in the DJI system is hell with randomly labeled version. So you have to keep trial and error to get things up
Below is DJI Email response. Pretty useless but will provide some cue for others to debug the similar issue
Bruce Cheung （DJI）
Dear Shenghai,
Thank you for contacting DJI.
We cannot reproduce the problem you mentioned by using A3 with OSDK3.7 and 3.8
Can you try to take control authority directly? using /dji_sdk/sdk_control_authority
Also try publishing the /dji_sdk/flight_control_setpoint_ENUposition_yaw control command, do not use the sample.
Thank you for your understanding and support, hope you a delighted life.
Best Regards,
DJI SDK Support Team
Hi Bruce
I tried what you mentioned., use
FIrst launch sdk.launch
Then, rosservical call /dji_sdk/sdk_control_authority 1
And write a simple empty C++ script to publish to /dji_sdk/flight_control_setpoint_generic.
The result is the same. the drone is not moving in the DJI assistant2 simulator.
My theory is the A3 firmware version might be too high on GitHub https://github.com/dji-sdk/Onboard-SDK-ROS/tree/3.7
it says 3.7 and 3.8 support
A3/A3 Pro 1.7.6.0
But I can't find it 1.7.6 in the DJI assistant 2 firmware only 1.7.7 and 1.7.5. So I decided to use 1.7.7
Will this be the issue?
Its 11 pm in Singapore, I ll take two videos of sample and custom method tmr morning. I`ll upload the video to youtube. you can see from there.
Regards
Shenghai Yuan
a Kinect-Noob here.
My machine runs Windows 10 - x86
I connected my kinect v1 to computer after installing kinect runtime, kinect for windows drivers, SDKs and developer toolkit. It wont show anything on the kinect studio even when I ran kinect enabled app - 3D scan from windows store.
This is the screen shot of the drivers being properly installed
The processing example (called Point Cloud of OpenKinect processing library) code shows error as :
64 windows
There are no kinects, returning null
Earlier (5 weeks back) same code used to give output. During those 5 weeks, I updated windows 10.
I uninstalled and installed the whole kinect package (runtime, SDK, toolkit and drivers), but no results. Also, removed zigfu plugins (for primesense and OpenNI). Still no results
Any help is appreciated !
Thanks !!!
I am trying to use Kinect (the oldest one, the very first one released by Windows) and connect it to Matlab R2013b in a Windows 10 running laptop.
I've already followed the suggested steps and installed the Matlab Support package called "Kinect for Windows Runtime". This is supposed to instal the drivers needed to run the kinect on windows too.
enter image description here
However, as I use the command "imaqhwinfo", I get a warning saying that kinect is either not supported or no powered and this output:
AdaptorDllVersion: '8.2 (R2013b)'
AdaptorName: 'kinect'
DeviceIDs: {1x0 cell}
DeviceInfo: [1x0 struct]
I'd really appreciate if anyone could tell me what the error is or, tell me the configuration you used if you were able to use matlab and kinect.
Thank you in advance
I can't install the USB drivers for Microchip's Wireless Dev Board. The part number is "DM182017-1" for this kit.
I followed Microchip's instructions for downloading the USB driver, but the installer tool for USB provided doesn't work.
To see these instructions, Google the "MCS3142 Dual KeeLoq Encoder Wireless Remote Control Development Kit User's Guide" and scroll to section 8.2 in the PDF. This section provides several links for finding and downloading the installer tools.
The GUI downloads, both the KeyLoq encoder and decoder, downloaded just fine. For some reason, it was finicky about where it was downloaded. I fixed it by creating a folder on the desktop and changing the directory to that, but I don't know how that fixed anything.
I'm using a 64-bit Windows 7 OS, and am using the x64 installer tool that goes with that version. I created a ticket on Microchip's website, but they haven't gotten back to me yet. When I spoke to Microchip yesterday for a different issue, they admitted that this is a rather niche board.
There are a ton of files you need just to get started with this thing, and virtually no tutorials online beyond Microchip's documentation. Oh, and enjoy random freezing on your computer if you try to download the USB installer too many times. I had to restart my computer twice now.
Answered my own question. Looks like I didn't have admin privileges. Worked like a charm, and I can move on.