I´d say I now have read all threads concerning win10 problems but not one seems like mine.
I´ve recently updated to win10 and have the following problem.
I can connect to my pixhawk via 3DR Radio on mavlink. This is good to get telemetry and parameters on an from the Pixhawk.
My problem is that i can`t get any connection if i directly connect to pixhawk via USB. My Mission planner neighter recognizes nor shows my Pixhawk in the connection tab. Usually it showed up as an additional com port under win7 but nothing happens now.
Here are some facts:
drivers installed, several times, also different versions -> so no prob with that
device manager recognizes Pixhawk and shows it
baud rate set to 11500 in device manager and also in mission planner
drivers are up to date
mission planner updated, also tried different earlier builds (complete uninstalled and reinstalled)
While trying to connect it says connection failed after one second
It´s pretty good to get a connection via the radio so i can fly and change settings, but i can`t download log files as it says "get log" timeout. Therefore I wanted to connect via USB but it doesn`t work.
I can connect to a friends Win7 laptop but thats no solution for the future.
Does someone have the right recommendation how to fix this problem.
you might find something here
does the pixhawk show up in device manager when you connect it.
also can you test on another pc to check usb is working correctly.
When I read:
"Usually it showed up as an additional com port under win7 but nothing happens now."
Sounds like you just have the first part of the installation completed (FTDI DRIVER).
Under Win10 you have to return on the device manager to complete the FTDI mapping of driver to a COM (VirtualCom) port. It might not be the case but you can give it a try... :-)
I updated to Win 10 but without any issues. If the com port is showing up in the device manager but not in Mission Planner try uninstalling/reinstalling MP or perhaps try updating to the beta version via the help page.
If Windows can see the com port but you can't connect to me it sounds more like something broke in the Mission planner/Windows side of things.
I can tell you that it does work so don't give up!!
Good luck!! and let us know how you go.
A shot in the dark but this happened to me in win 7, and incredibly it was solved after a reset and reinstallation of the Pixhawk firmware.
I posted this on the APM forum recently, which sounds as if there is some similarity...I cant help wondering whether it's a Windows problem generally with the Pixhawk.....In my case Windows XP on the laptop and Windows 7 on the desktop.
How do you do it? I have not seen any virtual port... PX4 PMU com4
Thanks in advance
Can you please upload this file somewhere since the specified page no longer exists!