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

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…

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.

Replies

Nikos April 18, 2019 at 10:01am

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…
Wilson Frias March 27, 2016 at 10:08pm

How do you do it? I have not seen any virtual port... PX4 PMU com4

Thanks in advance
- djtrickee > Wilson Frias May 19, 2016 at 2:03pm
  
  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
David Pulvermacher November 22, 2015 at 6:42am

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

Hugues November 22, 2015 at 1:15am

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.
Alex Wong November 20, 2015 at 11:25pm

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.
Patrick Poirier November 20, 2015 at 12:36pm

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

Michael Oborne November 20, 2015 at 6:55am

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.
Tony K November 19, 2015 at 6:47am

you might find something here

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

This reply was deleted.

Discussions

Windows 10 and Pixhawk problems

Replies

Activity