Edited HEARTBEAT id form 0 to 224 but unable to make connection, may be some CRC issue, any help?

QGroundControl Using QGroundControl
1

Edited HEARTBEAT id from 0 to 224 in mavlink_msg_heartbeat.h PX4, did same to mavlink_msg_heartbeat.h in QGC side. Now QGC is unable to connect to flight controller. May be some issue with CRC. What else I am missing.Below is my sample code from both PX4 and QGC’s mavlink_msg_heartbeat.h:

#define MAVLINK_MSG_ID_HEARTBEAT 224

MAVPACKED(
typedef struct __mavlink_heartbeat_t {
uint32_t custom_mode; /< A bitfield for use for autopilot-specific flags./
uint8_t type; /< Type of the MAV (quadrotor, helicopter, etc., up to 15 types, defined in MAV_TYPE ENUM)/
uint8_t autopilot; /< Autopilot type / class. defined in MAV_AUTOPILOT ENUM/
uint8_t base_mode; /< System mode bitfield, see MAV_MODE_FLAG ENUM in mavlink/include/mavlink_types.h/
uint8_t system_status; /< System status flag, see MAV_STATE ENUM/
uint8_t mavlink_version; /< MAVLink version, not writable by user, gets added by protocol because of magic data type: uint8_t_mavlink_version/
}) mavlink_heartbeat_t;

#define MAVLINK_MSG_ID_HEARTBEAT_LEN 9
#define MAVLINK_MSG_ID_HEARTBEAT_MIN_LEN 9
#define MAVLINK_MSG_ID_0_LEN 9
#define MAVLINK_MSG_ID_0_MIN_LEN 9

#define MAVLINK_MSG_ID_HEARTBEAT_CRC 86
#define MAVLINK_MSG_ID_0_CRC 86

2

It will be easier to find out the problem if you can debug and track down the decoding of heartbeat packet on QGC side.

3

I tried, I am getting MAVLINK_FRAMING_BAD_CRC error