# Cannot connect QGroundControl to internal PX4 (VOXL2)

Source: https://forum.modalai.com/topic/1628/cannot-connect-qgroundcontrol-to-internal-px4-voxl2
Category: VOXL 2 and VOXL 2 Mini (https://forum.modalai.com/category/26/voxl-2-and-voxl-2-mini)
Tags: voxl-2
Posted: 2022-12-16 13:26:39 UTC by mlarsen
Replies: 2 · Views: 684

## mlarsen · 2022-12-16 13:26:39 UTC

Hi All,

I can't get QGroundControl to connect to the internal PX4. I ran voxl-vision-px4 to setup the mavlink connection. voxl inspect shows the following.

 Service Name         |  Enabled  |   Running   |  CPU Usage
---------------------------------------------------------------
 docker-autorun       | Disabled  | Not Running |
 docker-daemon        | Disabled  | Not Running |
 modallink-relink     | Disabled  | Not Running |
 voxl-camera-server   |  Enabled  | Not Running |
 voxl-cpu-monitor     | Disabled  | Not Running |
 voxl-dfs-server      | Disabled  | Not Running |
 voxl-imu-server      |  Enabled  |   Running   |     0.0
 voxl-mavlink-server  |  Enabled  |   Running   |     0.0
 voxl-modem           | Disabled  | Not Running |
 voxl-portal          | Disabled  | Not Running |
 voxl-px4-imu-server  | Disabled  | Not Running |
 voxl-px4             |  Enabled  |   Running   |     0.0
 voxl-qvio-server     | Disabled  | Not Running |
 voxl-remote-id       | Disabled  | Not Running |
 voxl-softap          | Disabled  | Not Running |
 voxl-static-ip       | Disabled  | Not Running |
 voxl-streamer        | Disabled  | Not Running |
 voxl-tag-detector    | Disabled  | Not Running |
 voxl-tflite-server   | Disabled  | Not Running |
 voxl-time-sync       | Disabled  | Not Running |
 voxl-vision-px4      |  Enabled  | Not Running |
 voxl-wait-for-fs     |  Enabled  |  Completed  |

The voxl-vision-px4.conf shows:

{
	"config_file_version":	1,
	"qgc_ip":	"10.4.107.57",
	"en_secondary_qgc":	false,
	"secondary_qgc_ip":	"192.168.1.214",
	"qgc_udp_port_number":	14550,
	"udp_mtu":	512,
	"en_localhost_mavlink_udp":	true,
	"localhost_udp_port_number":	14551,
	"vio_pipe":	"qvio",
	"en_vio":	true,
	"en_send_vio_to_qgc":	false,
	"en_reset_vio_if_initialized_inverted":	true,
	"vio_warmup_s":	3,
	"send_odom_while_failed":	false,
	"horizon_cal_tolerance":	0.5,
	"offboard_mode":	"off",
	"follow_tag_id":	0,
	"figure_eight_move_home":	true,
	"robot_radius":	0.300000011920929,
	"collision_sampling_dt":	0.1,
	"max_lookahead_distance":	1,
	"en_tag_fixed_frame":	false,
	"fixed_frame_filter_len":	5,
	"en_transform_mavlink_pos_setpoints_from_fixed_frame":	false,
	"en_voa":	true,
	"en_send_voa_to_qgc":	false,
	"voa_upper_bound_m":	-0.15000000596046448,
	"voa_lower_bound_m":	0.15000000596046448,
	"voa_memory_s":	1,
	"voa_inputs":	[{
			"enabled":	true,
			"type":	"point_cloud",
			"input_pipe":	"dfs_point_cloud",
			"frame":	"stereo_l"
		}, {
			"enabled":	true,
			"type":	"point_cloud",
			"input_pipe":	"stereo_front_pc",
			"frame":	"stereo_front_l"
		}, {
			"enabled":	true,
			"type":	"point_cloud",
			"input_pipe":	"stereo_rear_pc",
			"frame":	"stereo_rear_l"
		}, {
			"enabled":	true,
			"type":	"tof",
			"input_pipe":	"tof",
			"frame":	"tof"
		}, {
			"enabled":	true,
			"type":	"rangefinder",
			"input_pipe":	"rangefinders",
			"frame":	"body"
		}]
}

and the IP is correct. Nothing shows up at the QGroundControl client side.

## Reply by Chad Sweet (ModalAI staff) · 2022-12-19 19:07:42 UTC

Can you ```ping 192.168.1.214``` from the computer that you are running QGC to make sure there is proper network connectivity between the two?

## Reply by mlarsen · 2022-12-20 18:35:58 UTC (in reply to Chad Sweet)

@Chad-Sweet I haven't tried. However, I manage to get it working by doing a factory reset configuration of the VOXL2. Don't know why it made a difference though.