Hi,
I’m trying to connect my cube to Mission planner.
I can the COM Port on my computer but Mavlink block and failed when I launch the connection.
I follow this tuto https://ardupilot.org/planner/docs/common-connect-mission-planner-autopilot.html
with a baudrate at 115200.
The cube is only linked to the GPS and the buzzer.
I make the connection with the micro USB on the side . I’ve tried multiple USB cable.
Is there a tips to debug the problem ?
Hi,
I work on W10 pro 1909(Last version update)
When I remove the driver unplug the cube and plug it back, the cube appears directly as COM23 with a bus name “CubeBlack-BL” .
The driver install pilots for
Arduino LLC
ChibiOS
Hex Technology Limited
Holybro
3D Robotics
NXP
ST
u-blox
Laser Navigation
And after install the peripheral name change to
ProfiCNC CUBE F4-FMU(COM23)
I never see Cube Orange.
I’ve made made the right-click uninstall.
When you install the driver you can remove it too.
After reboot and reinstall
I can’t install the firmware because I can’t connect the cube.
I’ve remove manually all the driver installer by the driver application.
Reboot
Plug unplug
Reinstall driver.
It still the same
I don’t know what to do.
If I try to open this serial port with another application it crash .
Is someone have a trick because it is the third days at the first step.
I’ve installed and uninstalled this driver about ten times .
I’ve tried to removed it manually .
Nothing change.
It is always “ProfiCNC CUBE F4-FMU”.
I’ve tried on other computer . The result is the same.
Is there some logs somewhere to see something, or test IHM for the cube ?
The problem come from the cube. The Serial COM created is a fake because I can’t open the COM with putty.
Is there some other drivers ?
I use W10 like most of people .
When I connect the cube the light is green during half second and became orange the right led blink during 3 sec and that the led stay orange and ON.
if it says “ProfiCNC CUBE F4-FMU”
then the driver is not being uninstalled.
the MSI i linked to has a drivercleaner.exe in it, that trys to remove all older drivers. it needs to be run as admin to do this
When I launch the msi in admin mode it jump directly at the end of the installer.
it is a shame to run the msi in admin mode , you have to add this key in the register
HKEY_CLASSES_ROOT\Msi.Package\shell\runas\command
“%SystemRoot%\System32\msiexec.exe” /a “%1” %*
the problem is the same , I can see all the driver package still installed on my computer even if I do a remove in the driver installer in normal mode.
I try IObit uninstaller to remove correctly the driver, reboot and plug the cube.
I never get the orange name.
At first step there is something in the windows driver or in the VID PID of the cube .