I’ve got a Cube-Orange (Device: CubePilot, Version: 5) and I can load the latest apj firmware with GQC (latest build from 2019-08-28 17:30:09 -0700) as well MP (Ver 1.3.68.1 build 1.3.7180.20891). However, I can’t get any of the later July or August fw to work with MP or GQC.
After successful flashing it’s still not connecting (disconnected the cube from USB after flashing has successfully completed, closed MP, reconnected Cube to USB and then started MP). I get the com port reported properly on my machine as “COM5 Cube H7 (COM5)”.
However, when I attempt to connect to the Orange Cube, it enters the 28sec timer count down after a few seconds and then fails at the end of the countdown with the message “No Heartbeat Packets Received”.
PS. Windows 10 reports com port driver as: “CubePilot”, dated: 10/04/2017, version “1.0.0.1”.
Going to “Device Manager” in Win10 and uninstalling (with removal of the driver) did instantly fix the problem without a reboot even necessary.
Windows and MP now reports two devices once the Orange Cube is plugged in:
“Cube Orange Mavlink (COMx)”
“Cube Orange SLCAN (COMy)”
MP as well as GQC are now working perfectly fine!
I hope this helps the next guy sorting out the driver issue on Windows OS. In this case the problem was that I installed a “stable” MP first and then updated MP with the latest beta and the latest MP driver msi.
I should have downloaded and started with a Beta/latest MP build from the get go as Windows 10 just stuck with the old driver Version 1.0.0.1 and never used the newer driver that installed minutes later.
OH! It was so late last night I forgot. I was able to load the Firmware over USB just fine. But after I loaded the firmware, I couldn’t actually get a mavlink connection to the Cube over USB. It worked fine over UDP from the companion computer, which is what I used for configuration and flight.
I have no doubt mine is old drivers as well. But the cube is no inside the Solo so I no longer have access to the USB port to test it.
Try an older version of master from around June time. They have been doing all sorts with the drivers and I have found June/July master builds most stable for the USB connection especially.
Latest master has been doing all sorts with the Orange especially.
Thanks Matt. I was finally able to install firmware with your suggestion. Still can’t connect to MP via USB with latest drivers - no heart beat error. Running Win7 and don’t have access to a Win10 machine at the moment to test.
My second Cube Orange exhibits exactly the same behavior. Both cubes were received yesterday from CubePilot. Using @Pedals2Paddles directions I am able to install the latest firmware, but can’t connect with MP or QGC. For fun, also tried the USB dongle and powering the Cubes in addition to the USB port - no joy.
MP has been uninstalled and reinstalled twice. Tried both the Current and Beta versions of MP. Removed and reinstalled the latest drivers several times. Going to pick up a Windows 10 lappy this afternoon and see if that makes a difference.
Windows 10 was a no-go. Win10 1709, Current version of MP and Beta both failed. Updated with latest drivers. After the driver update It just stalled on “Mavlink Connecting”. Reboot, etc.
The good news… connecting with a telemetry radio worked like a champ. Testing continues.
A shout out to @Matt.C as running driver clean, uninstalling the drivers and reinstalling them solved the problem on Win10. Evidently driver clean does not run (or appear to run) on Win7. On Win10 I had to click through numerous Windows security alerts for PnPUtil.exe. On Win7 - no response when clicked.
Windows 7 is now working, however - truly odd behavior.
Steps:
Delete CUBE H7 from device manager while the Cube Orange is connected with the option to delete the driver, then disconnect the Cube Orange.
Uninstall and reinstall the latest drivers.
Reconnect the Cube Orange - two entries will show up in “Other Devices” named CubeOrange-BL. The top entry will change to CubeOrange. You will see the message from windows notifying you that it is installing device drivers.
CubeOrange-BL will move to the Ports section and be named Cube Orange Mavlink (COMxx)
If the “CubeOrange-BL” in Other Devices" does not move to Ports after a few moments, right click on it, go into properties, click on the driver button and - do absolutely nothing else - for some unknown reason CubeOrange moves to Ports and is named Cube Orange SLCAN (COMxx)
I have now duplicated this behavior 5 times, at great risk to my sanity.
I have tried this process many times. But it doesn’t show the mavlink and other port. When I install new drivers it starts showing “usb serial drive(com3)”. When drivers are not installed it shows" cube- new drivers required(com3).
Any ideas as to how shall I solve this problem?