Why do I get XCP internal error: timeout expired?

Hi,

I have tried to follow this example, but using a Cube Orange instead, which I set up using this guide except on Ubuntu instead of Windows.

But somewhere I messed something up. When I try to run "monitor & tune" on the board, I get the following error:

0 of 1 models built (1 models already up to date)
Build duration: 0h 1m 15.535s
action: EXT_INIT
Creating Target Handler (XCP on Serial)...
Build directory: /home/soren/heavy_duty/matlab/untitled_ert_rtw
Serial Port Name: /dev/ttyUSB0
Baud Rate: 57600
action: EXT_CONNECT
Connecting to the target...
External Mode Open Protocol Connect command failed
Caused by:
Could not connect to target application: XCP internal error: timeout expired, in response to XCP CONNECT command 

I have determined it seems like the problem is with the communication between Cube Orange using Telem 1 on the Pixhawk (where I have the FTDI serial converter in). I have tried using different baud rates but can't determine what exactly is the problem with the connection.

[Hasan Khanzada]

@Søren Let me know if you were able to solve this issue ?

@Arun Mathamkode I have tried all the solutions you have mentioed in the comments

but i am still getting the same error as mentioned in this post.

[Søren]

Unfortunately I never managed to solve it. I had other task to do, didn't spend a lot more time on the issue

Answer 1

[Arun Mathamkode]

TELEM1 serial port are fundamentally designed for MAVLink communication and by default MAVLink is enabled in this port. You can consider trying to connect using GPS2 port (/dev/ttyS5). Makesure that parameters GPS_1_CONFIG or GPS_2_CONFIG is not set to enable GPS2 as a GPS port.

[Søren]

I tried to disable the MAVLink communication on TELEM1, to see if that works. But I can try to test it on GPS2 port instead.

[Søren]

@Arun Mathamkode I have tried connecting to GPS2 port instead, but I still get the exact same error as before.

[Arun Mathamkode]

You can consider setting baud rate as 115200, instead of the default value. Also ensure that the FTDI host COM port value is correctly entered in the External mode tab in Simulink Configuration Parameter window.

[Salvatore Matteo Mennea]

@Søren Have you found a solution? I'm facing the exact same problem

[Salvatore Matteo Mennea]

@Arun Mathamkode I've tried all the solution you have written in the post but I have the same error.

I'm using win 10 and Pixhawk 6x with matlab 2023b

[Seunghyun Lee]

I also have samm error.

I used XCP on TEL1 of Cube Orage. It means device name as /dev/ttyS0 on Cube hardware.

But, There's no serial port name on host side in linux. I guess it must be /dev//ttyUSB0 in linux(COMx in windows). However, It doesn't work.

Definately, I made sure that the MAV_CONFIG0 parameset is not set.