Methodic Configurator won't connect to cubeorange+

Not sure if I’m doing something wrong, but when I start using the tool, the system can see the cube but doesn’t seem to be able to fetch params in order to initialize the tool and compare incoming settings with existing settings. Below is the tool output.

2024-11-18 12:39:50,498 - INFO - Available connection ports are:
2024-11-18 12:39:50,498 - INFO - COM22 - Cube Orange+ SLCAN (COM22)
2024-11-18 12:39:50,498 - INFO - COM21 - Cube Orange+ Mavlink (COM21)
2024-11-18 12:39:50,498 - INFO - tcp:127.0.0.1:5760 - tcp:127.0.0.1:5760
2024-11-18 12:39:50,498 - INFO - udp:127.0.0.1:14550 - udp:127.0.0.1:14550
2024-11-18 12:39:50,498 - INFO - Will connect to COM21
2024-11-18 12:39:53,069 - INFO - Will connect to COM21
2024-11-18 12:39:53,069 - WARNING - Connection failed: could not open port 'COM21': PermissionError(13, 'Access is denied.', None, 5)
2024-11-18 12:39:53,069 - ERROR - Failed to connect after 3 attempts.
2024-11-18 12:40:02,119 - INFO - Will connect to COM21
2024-11-18 12:40:03,158 - INFO - Autopilot type ArduPilot - Plane/Copter/Rover/Sub/Tracker, https://ardupilot.org
2024-11-18 12:40:03,158 - INFO - Vehicle type: Hexarotor running ArduCopter firmware
2024-11-18 12:40:04,678 - INFO - FC banner ArduCopter V4.3.7 (c8506ed4)
2024-11-18 12:40:04,680 - INFO - FC banner CubeOrangePlus 00200021 31315101 37383337
2024-11-18 12:40:04,680 - INFO - FC banner RCOut: PWM:1-12
2024-11-18 12:40:04,680 - INFO - FC banner Frame: HEXA/X
2024-11-18 12:40:04,680 - WARNING - FC product mismatch: CubeOrangePlus (BANNER) != CubeOrange+ (AUTOPILOT_VERSION)
2024-11-18 12:40:04,775 - INFO - Firmware Version: 4.3.7 official
2024-11-18 12:40:04,775 - INFO - Firmware first 8 hex bytes of the FC git hash: c8506ed4
2024-11-18 12:40:04,775 - INFO - Firmware first 8 hex bytes of the ChibiOS git hash: a97ccb41
2024-11-18 12:40:04,775 - INFO - Flight Controller HW / board version: 69664768
2024-11-18 12:40:04,775 - INFO - Flight Controller USB vendor ID: CubePilot
2024-11-18 12:40:04,775 - INFO - Flight Controller USB product ID: CubeOrangePlus
2024-11-18 12:40:04,839 - INFO - MAVFTP is supported by the COM21 flight controller
2024-11-18 12:40:04,839 - INFO - FTP: wrong MAVLink target 255 component 190. Will discard message
2024-11-18 12:40:08,542 - INFO - FTP: wrong MAVLink target 255 component 190. Will discard message
2024-11-18 12:40:09,548 - INFO - FTP: wrong MAVLink target 255 component 190. Will discard message
2024-11-18 12:40:09,548 - INFO - FTP: wrong MAVLink target 255 component 190. Will discard message
2024-11-18 12:40:10,562 - INFO - FTP: wrong MAVLink target 255 component 190. Will discard message
2024-11-18 12:40:10,562 - INFO - FTP: wrong MAVLink target 255 component 190. Will discard message
2024-11-18 12:40:11,564 - ERROR - FTP: no parameter file handler
2024-11-18 12:40:15,265 - ERROR - mavlink_packet failed, generic error
2024-11-18 12:52:45,701 - INFO - Selected template directory: C:\ProgramData\.ardupilot_methodic_configurator\vehicle_templates\ArduCopter\FETtec-5
2024-11-18 12:54:45,514 - INFO - Vehicle component data saved successfully.
2024-11-18 12:54:45,672 - INFO - No last uploaded file found. Starting with the first file..
2024-11-18 12:54:45,854 - WARNING - In file 'configuration_steps_ArduCopter.json': '02_imu_temperature_calibration_setup.param' derived parameter 'INS_LOG_BAT_MASK' could not be computed: 'fc_parameters' not found, is an FC connected?
2024-11-18 12:57:11,237 - WARNING - No parameter was selected for upload, will not upload any parameter
2024-11-18 12:57:23,802 - WARNING - No parameter was selected for upload, will not upload any parameter
2024-11-18 12:57:47,796 - WARNING - No parameter was selected for upload, will not upload any parameter
2024-11-18 12:57:51,010 - WARNING - No parameter was selected for upload, will not upload any parameter

Disconnect the gimbal, or whatever component 190 is, and try again.

255:190 looks like some other GCS or companion computer.

I thought so too, but as far as I could see there were no others connected or running

Looks like that component ID is reserved for mission planner, and it was running and interfering with this. We made sure it was closed when we started running the tool and it looks like we’re progressing past this

1 Like