for a while I have been having logs of any length (> 5 minutes) fail with a disconnect of the GCS…multiple different autopilots…QGC desktop downloads them 100% of the time…very consistent…MP 1.2.77.1 build 1.3.8180.19597…was doing it for several previous versions also…thought it must be a Win10 or PC issue, but QGC is 100% reliable…MAVproxy on my Linux box also is 100% effective in downloading logs…anyone else experiencing this?
can you please provide missionplanner.log from c:\programdata\missionplanner directly after this event has happened
looking at the log looks like a usb power issue to me
thanks…but I dont understand why on the same PC port, using QGC to download the logs does not have the same problem…and why the disconnect only occurs during log downloads when using Mission Planner…strange
can you verify with another usb cable / cable and port?
Playing around with cables, and ports, I think it may be a marginal power issue on my desktops front ports…if I use a powered hub, I dont seem to get the disconnects…, however, it still does not explain why its not an issue downloading with desktop QGC vs Mission Planner on those ports…why would MP way of downloading logs increase the power demand from the FC?..
it could be to do with round trip latency, ie MP is more intence in it log download. but now im 100% guessing. also from the log you posted i see other usb devices disapear and reapear as well, not just the FC
well if something is causing a brown out, every port on the controllers interface will have the issue also I would guess
just more details as well
this is what i see in the log
2022-06-17 18:21:06,403 INFO MissionPlanner.MainV2 - Interface \?\USB#VID_05E3&PID_0749#000000001532#{a5dcbf10-6530-11d2-901f-00c04fb951ed} (D:\a\MissionPlanner\MissionPlanner\MainV2.cs:4555) [Base Thread]
2022-06-17 18:21:06,404 INFO MissionPlanner.MainV2 - Device Change 537 DBT_DEVICEREMOVECOMPLETE 725540133664 (D:\a\MissionPlanner\MissionPlanner\MainV2.cs:4572) [Base Thread]
2022-06-17 18:21:06,695 INFO MissionPlanner.MainV2 - Device Change 537 DBT_DEVNODES_CHANGED 0 (D:\a\MissionPlanner\MissionPlanner\MainV2.cs:4572) [Base Thread]
2022-06-17 18:21:06,696 INFO MissionPlanner.MainV2 - Device Change 537 DBT_DEVICEREMOVECOMPLETE 725540133840 (D:\a\MissionPlanner\MissionPlanner\MainV2.cs:4572) [Base Thread]
2022-06-17 18:21:07,029 DEBUG MissionPlanner.Program - FirstChanceException in: System (D:\a\MissionPlanner\MissionPlanner\Program.cs:501) [5]
System.IO.IOException: A device which does not exist was specified.at System.IO.Ports.InternalResources.WinIOError(Int32 errorCode, String str)
2022-06-17 18:21:07,030 ERROR MissionPlanner.MainV2 - System.IO.IOException: A device which does not exist was specified.at System.IO.Ports.InternalResources.WinIOError(Int32 errorCode, String str)
at System.IO.Ports.SerialStream.EndWrite(IAsyncResult asyncResult)
at System.IO.Ports.SerialStream.Write(Byte array, Int32 offset, Int32 count, Int32 timeout)
at System.IO.Ports.SerialPort.Write(Byte buffer, Int32 offset, Int32 count)
at MissionPlanner.Comms.WinSerialPort.MissionPlanner.Comms.ICommsSerial.Write(Byte buffer, Int32 offset, Int32 count)
at MissionPlanner.Comms.SerialPort.Write(Byte buffer, Int32 offset, Int32 count) in D:\a\MissionPlanner\MissionPlanner\ExtLibs\Comms\CommsSerialPort.cs:line 183
at MissionPlanner.MAVLinkInterface.generatePacket(Int32 messageType, Object indata, Int32 sysid, Int32 compid, Boolean forcemavlink2, Boolean forcesigning) in D:\a\MissionPlanner\MissionPlanner\ExtLibs\ArduPilot\Mavlink\MAVLinkInterface.cs:line 1315
at MissionPlanner.MAVLinkInterface.sendPacket(Object indata, Int32 sysid, Int32 compid) in D:\a\MissionPlanner\MissionPlanner\ExtLibs\ArduPilot\Mavlink\MAVLinkInterface.cs:line 1106
at MissionPlanner.MainV2.d__131.MoveNext() in D:\a\MissionPlanner\MissionPlanner\MainV2.cs:line 3032 (D:\a\MissionPlanner\MissionPlanner\MainV2.cs:3032) [5]
what this is saying is that
the USB device = DBT_DEVICEREMOVECOMPLETE
disapeared
And then mission planner throws an exception
System.IO.IOException: A device which does not exist was specified.
which is fair, as the usb device just vanished from under its nose