USB detection issue with Pixhawk 2.4.8

Hi All,

I updated the firmware for Pixhawk 2.4.8 from Copter 4.1 to 4.5 and things went well. I aslo updated firmware to fmuv3

I decided to change some configuration using mission planner and when I connect the device again it doesn’t want to connect to my PC at all.

Note: I am using windows 10

I got this error :

Access to the port ‘COM5’ is denied.

at System.IO.Ports.InternalResources.WinIOError(Int32 errorCode, String str)
at System.IO.Ports.SerialStream…ctor(String portName, Int32 baudRate, Parity parity, Int32 dataBits, StopBits stopBits, Int32 readTimeout, Int32 writeTimeout, Handshake handshake, Boolean dtrEnable, Boolean rtsEnable, Boolean discardNull, Byte parityReplace)
at System.IO.Ports.SerialPort.Open()
at MissionPlanner.Comms.WinSerialPort.Open() in C:\Users\mich1\Desktop\CubePilot\MissionPlanner\ExtLibs\Comms\CommsSerialPort.cs:line 510
at MissionPlanner.Comms.SerialPort.Open() in C:\Users\mich1\Desktop\CubePilot\MissionPlanner\ExtLibs\Comms\CommsSerialPort.cs:line 148
at MissionPlanner.MAVLinkInterface.OpenBg(IProgressReporterDialogue PRsender, Boolean getparams) in C:\Users\mich1\Desktop\CubePilot\MissionPlanner\ExtLibs\ArduPilot\Mavlink\MAVLinkInterface.cs:line 886
at MissionPlanner.Controls.ProgressReporterDialogue.RunBackgroundOperation(Object o) in C:\Users\mich1\Desktop\CubePilot\MissionPlanner\ExtLibs\Controls\ProgressReporterDialogue.cs:line 111

The strange thing, the board can be identified as shown below

I used the same micro usb cable that I used for updating the firmware. The board blinks blue when I connect it.

I see com5 on my device manger as ardupilot com5

device manger

Hmm. Is there any other mission planners/serial links open in the background? QGC, mavproxy, putty, etc.

Also you can try to open MP in admin mode but not sure if this will help.

Also, what settings did you change? If there’s a chance you changed serial0_* params you may be unable to connect. If this is the case you will have to install a different vehicles firmware (if you have copter, go to rover, then back to copter). This will reset the parameters, so if you changed serial0 at all it will return it to default. But I’d save this option for last case as I don’t know if the error points to this, this may be a more PC side issue.

You can grab parameters from your last log file if you do go for it.

Thx for the answer.

I didn’t change any serial configuration. I just installed a new firmware and faced one problem.

Then I disconnected then connected again to set some configuration and I couldn’t.

I don’t have QGC, mavproxy or even putty installed. it is only the MP.