Cube Black: USB not working, but wireless telemetry and firmware flashing does

ArduCopter Copter 4.6
1

Hi, after a longer time, I need to change some things on my Cube Black. The problem is that it doesn’t connect via USB to mission planner anymore. In device manager it is appearing as ProfiCNC CUBE F4 FMU, and sometimes as PX4 FMU. I tested different USB cables. After it didn’t work, I tried to upload the latest firmware. It worked without problems.

I can connect via wireless telemetry link to the copter without issues. That is where i validated that firmware flashing really worked, the copter is on V4.6.3 (92b0cd78). I also did a parameter reset via Mission Planner (clicked “Reset to Defaults”) to remove any accidental misconfiguration of the USB port. But the issue remains.

Does anyone know what is going on here? Thanks you!!

This is what mission planner reports:

INFO MissionPlanner.MAVLinkInterface - Packet failed signature but passed crc

Das Zeitlimit für die Semaphore wurde erreicht.

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 C:\Users\mich1\Desktop\CubePilot\MissionPlanner\ExtLibs\Comms\CommsSerialPort.cs:line 187
at MissionPlanner.MAVLinkInterface.generatePacket(Int32 messageType, Object indata, Int32 sysid, Int32 compid, Boolean forcemavlink2, Boolean forcesigning) in C:\Users\mich1\Desktop\CubePilot\MissionPlanner\ExtLibs\ArduPilot\Mavlink\MAVLinkInterface.cs:line 1442
at MissionPlanner.MAVLinkInterface.sendPacket(Object indata, Int32 sysid, Int32 compid) in C:\Users\mich1\Desktop\CubePilot\MissionPlanner\ExtLibs\ArduPilot\Mavlink\MAVLinkInterface.cs:line 1231
at MissionPlanner.MAVLinkInterface.d__162.MoveNext() in C:\Users\mich1\Desktop\CubePilot\MissionPlanner\ExtLibs\ArduPilot\Mavlink\MAVLinkInterface.cs:line 1161
— End of stack trace from previous location where exception was thrown —
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at MissionPlanner.Utilities.Extensions.<>c__DisplayClass1_01.<<AwaitSync>b__0>d.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at MissionPlanner.Utilities.Extensions.AwaitSync[T](Task1 infunc)
at MissionPlanner.MAVLinkInterface.OpenBg(IProgressReporterDialogue PRsender, Boolean getparams) in C:\Users\mich1\Desktop\CubePilot\MissionPlanner\ExtLibs\ArduPilot\Mavlink\MAVLinkInterface.cs:line 960
at MissionPlanner.Controls.ProgressReporterDialogue.RunBackgroundOperation(Object o) in C:\Users\mich1\Desktop\CubePilot\MissionPlanner\ExtLibs\Controls\ProgressReporterDialogue.cs:line 111

2

In Windows Device Manager, set View/Show hidden devices - this makes it easy to see what’s going on.
Check that an active COM port for something else is not conflicting with your Cube or Ardupilot COM port. Some software creates an active com port even if the matching hardware is not physically connected.

You can have multiple devices all using the same COM port, but not at the same time. I usually set all flight controllers to use COM4 (for example) then I dont have to find the correct connection in MissionPlanner.

3

Hi, thanks for your feedback! There did not seem to be a conflict of com ports. But the problem is solved:

I had already tried two different computers, and both didn’t work. Now I additionally tried my personal laptop, and it suddenly worked. This is strange.