Windows 10 and Pixhawk problems

Hello.

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.

Thanks

Ben

You need to be a member of diydrones to add comments!

Join diydrones

Email me when people reply –

Replies

  • Can you please upload this file somewhere since the specified page no longer exists!

    djtrickee said:

    I had to reinstall the drivers. I used this link and am now able to connect via both USB and wirelessly whereas earlier I was only able to connect wirelessly.

    http://pixhawk.org/static/px4driver.msi

    Windows 10 and Pixhawk problems
    Hello. 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 follo…
  • How do you do it? I have not seen any virtual port... PX4 PMU com4

    Thanks in advance

    • I had to reinstall the drivers. I used this link and am now able to connect via both USB and wirelessly whereas earlier I was only able to connect wirelessly.

      http://pixhawk.org/static/px4driver.msi

  • Hi Ben.

    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.

    Hi all.....
    I've been having a real time of it. (Pixhawk and 3.2.1FW)

    Having just returned from holiday and taken out my quad for a spin (previously working perfectly), I was rather irritated to find that I could not connect via the 3DR radio with my Android device, nor could I arm the Pixhawk, as there was no satelite fix (open playing field) and the OSD was receiving no telemetry at all.

    Having returned home in disgust, I tried without success to connect with MP.
    So I decided to reinstall the copter firmware having overwritten with plane 3.3.1.

    With firmware loaded, I then tried to connect and got failure after failure, mainly due to 'Access denied to 
    Com1 port'. Despite the serial port showing in the device manager, and working.

    So I tried clearing the port register using regedit, with little luck, and then tried connecting with APM planner, eventually succeeding, only by going the "wizard' route.....

    This has all proved to be very tedious indeed, and I wonder why it should suddenly be so difficult to connect to the Pixhawk..... Even on my laptop.
    Has anybody else suffered the same frustration?

    Any wisdom would be most welcome!. Best DP
    Subsequent to this post I dug out my APM 2.6 to see whether there was a connection problem with that FC, but it connected first attempt......
    Let's hope that someone can throw some light on this!
    Best DP.
  • MR60

    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 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.

  • Hello

    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... :-)

  • Developer

    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.

  • you might find something here

    http://diydrones.com/forum/topics/mission-planner-for-windows-10?co...

This reply was deleted.

Activity

DIY Robocars via Twitter
RT @TinkerGen_: "The Tinkergen MARK ($199) is my new favorite starter robocar. It’s got everything — computer vision, deep learning, sensor…
Nov 23
DIY Robocars via Twitter
Nov 23
DIY Robocars via Twitter
RT @roboton_io: Join our FREE Sumo Competition 🤖🏆 👉 https://roboton.io/ranking/vsc2020 #sumo #robot #edtech #competition #games4ed https://t.co/WOx…
Nov 16
DIY Drones via Twitter
First impressions of Tinkergen MARK robocar https://ift.tt/36IeZHc
Nov 16
DIY Robocars via Twitter
Our review of the @TinkerGen_ MARK robocar, which is the best on the market right now https://diyrobocars.com/2020/11/15/first-impressions-of-tinkergen-mark-robocar/ https://t.co/ENIlU5SfZ2
Nov 15
DIY Robocars via Twitter
RT @Ingmar_Stapel: I have now explained the OpenBot project in great detail on my blog with 12 articles step by step. I hope you enjoy read…
Nov 15
DIY Robocars via Twitter
RT @DAVGtech: This is a must attend. Click the link, follow link to read the story, sign up. #chaos2020 #digitalconnection #digitalworld ht…
Nov 15
DIY Robocars via Twitter
RT @a1k0n: Got a new chassis for outdoor races (hobbyking Quantum Vandal) but I totally didn't expect that it might cause problems for my g…
Nov 11
DIY Drones via Twitter
First impressions of the Intel OpenBot https://ift.tt/36qkVV4
Nov 10
DIY Robocars via Twitter
Nov 9
DIY Robocars via Twitter
Excellent use of cardboard instead of 3D printing! https://twitter.com/Ingmar_Stapel/status/1324960595318333441
Nov 7
DIY Robocars via Twitter
RT @chr1sa: We've got a record 50 teams competing in this month's @DIYRobocars @donkey_car virtual AI car race. Starting today at 10:00am…
Nov 7
DIY Robocars via Twitter
Nov 6
DIY Robocars via Twitter
RT @a1k0n: Car's view, using a fisheye camera. The ceiling light tracking algorithm gave me some ideas to improve ConeSLAM, and having grou…
Nov 5
DIY Robocars via Twitter
RT @a1k0n: To get ground truth I measured the rug, found the pixel coordinates of its corners, calibrated my phone camera with my standard…
Nov 5
DIY Robocars via Twitter
RT @a1k0n: @DIYRobocars is back in December, but outside. Time to reinvestigate ConeSLAM! I rigged up a quick and dirty ground-truth captur…
Nov 5
More…