DGPS - Revision history

Xp31 at 15:27, 5 July 2020

2020-07-05T15:27:30Z

← Older revision		Revision as of 09:27, 5 July 2020
Line 52:		Line 52:
	* Check firmware "view / Messages View / UBX / MON (Monitor) / VER (version)"		* Check firmware "view / Messages View / UBX / MON (Monitor) / VER (version)"
	* Set default settings view / Configuration View / ..."		* Set default settings view / Configuration View / ..."
	* Set output messages "view / Configuration View / Msg (Messages)": UART1 <br />01-02 NAV-~~POSLLH~~ (send), 01-12 NAV-~~VELNED (send), 01-03 NAV-STATUS~~ (send), 01-30 NAV-SVINFO (send)~~,01-06 NAV-SOL (send),~~<br />~~01-3C NAV-RELPOSNED (send), 02-32 RXM-RTCM (send) (CFG send)~~		* Set output messages "view / Configuration View / Msg (Messages)": UART1 <br />01-05 NAV-PVT (send), 01-06 NAV-SOL (send), 01-30 NAV-SVINFO (send)<br />
	* Set model type "view / Configuration View / NAV5 (Navigation 5)": <br />Dynamic Model : 7-Airborne < 2g (send) (CFG send)		* Set model type "view / Configuration View / NAV5 (Navigation 5)": <br />Dynamic Model : 7-Airborne < 2g (send) (CFG send)
	* Set interface "view / Configuration View / PORT": <br />Target: UART1, Protocol in: 5-RTCM3, Protocol out: 0-UBX (send), Baudrate: 115200 (send) (CFG send)		* Set interface "view / Configuration View / PORT": <br />Target: UART1, Protocol in: 5-RTCM3, Protocol out: 0-UBX (send), Baudrate: 115200 (send) (CFG send)

Xp31 at 16:42, 3 July 2020

2020-07-03T16:42:17Z

← Older revision		Revision as of 10:42, 3 July 2020
Line 40:		Line 40:
	* Check firmware "view / Messages View / UBX / MON (Monitor) / VER (version)"		* Check firmware "view / Messages View / UBX / MON (Monitor) / VER (version)"
	* Set default settings view / Configuration View / ..."		* Set default settings view / Configuration View / ..."
	* Set output messages "view / Configuration View / Msg (Messages)": USB <br />F5-05 RTCM3.2 1005 (send), F5-4D RTCM3.2 1077 (send), F5-4D RTCM3.2 1087 (send) (CFG send)		* Set output messages "view / Configuration View / Msg (Messages)": USB <br />F5-05 RTCM3.2 1005 (send), F5-4D RTCM3.2 1077 (send), F5-4D RTCM3.2 1087 (send), 01-3B NAV_SVIN (send), (CFG send)
	* Set model type "view / Configuration View / NAV5 (Navigation 5)": <br />Dynamic Model : 2-Stationnary (send) (CFG send)		* Set model type "view / Configuration View / NAV5 (Navigation 5)": <br />Dynamic Model : 2-Stationnary (send) (CFG send)
	* Set interface "view / Configuration View / PORT": <br />Target: USB, Protocol in: none, Protocol out: 5-RTCM3 (send) (CFG send)		* Set interface "view / Configuration View / PORT": <br />Target: USB, Protocol in: none, Protocol out: 0+1+5 - UBX+NMEA+RTCM3 (send) (CFG send)
	* Set acquisition rate "view / Configuration View / RATE (Rates)"<br />Target: Measurement period :1000 (ms) (send) (CFG send)		* Set acquisition rate "view / Configuration View / RATE (Rates)"<br />Target: Measurement period :1000 (ms) (send) (CFG send)
	* Set position type "view / Configuration View / TMODE3 (Time Mode 3)"		* Set position type "view / Configuration View / TMODE3 (Time Mode 3)"

Xp31: Todo

2020-06-16T07:54:40Z

Todo

← Older revision		Revision as of 01:54, 16 June 2020
Line 76:		Line 76:
	== External RTK Ground Station ==		== External RTK Ground Station ==
	(Working Draft)<br />With this implementation, the RTK ground application runs in a separate machine (ex."Raspberry Pi"), providing a wireless "hotspot" access to the ground station laptop (GCS). This is a more operational way to use the system, as the RTK station is located outside, and ground station laptops can be located inside.		(Working Draft)<br />With this implementation, the RTK ground application runs in a separate machine (ex."Raspberry Pi"), providing a wireless "hotspot" access to the ground station laptop (GCS). This is a more operational way to use the system, as the RTK station is located outside, and ground station laptops can be located inside.
			TODO

	'''Implementation'''		'''Implementation'''

	Install a debian		Install a debian

Xp31: /* External RTK Ground Station */

2017-03-04T14:32:52Z

External RTK Ground Station

← Older revision		Revision as of 08:32, 4 March 2017
Line 75:		Line 75:

	== External RTK Ground Station ==		== External RTK Ground Station ==
	(Working Draft)<br />With this implementation, the RTK ground application runs in a separate machine (ex."Raspberry Pi"), providing a wireless "hotspot" access~~. The~~ ground station laptop (GCS) ~~use a wifi connection to the "hotspot"~~. This is a more operational way to use the system, as the RTK station is located outside, and ground station laptops can be located inside.		(Working Draft)<br />With this implementation, the RTK ground application runs in a separate machine (ex."Raspberry Pi"), providing a wireless "hotspot" access to the ground station laptop (GCS). This is a more operational way to use the system, as the RTK station is located outside, and ground station laptops can be located inside.

	'''Implementation'''		'''Implementation'''

	Install a debian		Install a debian

Xp31 at 14:31, 4 March 2017

2017-03-04T14:31:20Z

← Older revision		Revision as of 08:31, 4 March 2017
Line 75:		Line 75:

	== External RTK Ground Station ==		== External RTK Ground Station ==
	(Working Draft)		(Working Draft)<br />With this implementation, the RTK ground application runs in a separate machine (ex."Raspberry Pi"), providing a wireless "hotspot" access. The ground station laptop (GCS) use a wifi connection to the "hotspot". This is a more operational way to use the system, as the RTK station is located outside, and ground station laptops can be located inside.
	With this implementation, the RTK ground application runs in a separate machine (ex."Raspberry Pi"), providing a wireless "hotspot" access. The ground station laptop (GCS) use a wifi connection to the "hotspot". This is a more operational way to use the system, as the RTK station is located outside, and ground station laptops can be located inside.
			'''Implementation'''

	Install a debian		Install a debian

Xp31: /* External RTK Ground Station */

2017-03-04T14:29:30Z

External RTK Ground Station

← Older revision		Revision as of 08:29, 4 March 2017
Line 76:		Line 76:
	== External RTK Ground Station ==		== External RTK Ground Station ==
	(Working Draft)		(Working Draft)
	With this implementation, the RTK ground application runs in a separate machine (ex."Raspberry Pi"), ~~running~~ a wireless "hotspot".		With this implementation, the RTK ground application runs in a separate machine (ex."Raspberry Pi"), providing a wireless "hotspot" access. The ground station laptop (GCS) use a wifi connection to the "hotspot". This is a more operational way to use the system, as the RTK station is located outside, and ground station laptops can be located inside.
	This is a more operational way to use
	~~- an external TYK~~

	~~the ground station laptop (GCS) is use~~ a ~~wifi connection to an external RTK station located outside.~~		Install a debian

	~~This implementation use a "Raspberry Pi" to get the ground data and send~~

Xp31 at 14:22, 4 March 2017

2017-03-04T14:22:29Z

← Older revision		Revision as of 08:22, 4 March 2017
Line 74:		Line 74:


	== External RTK Ground Station == (Working Draft)		== External RTK Ground Station ==
			(Working Draft)
	With this implementation, the RTK ground application runs in a separate machine (ex."Raspberry Pi"), running a wireless "hotspot".		With this implementation, the RTK ground application runs in a separate machine (ex."Raspberry Pi"), running a wireless "hotspot".
	This is a more operational way to use		This is a more operational way to use
			- an external TYK

	the ground station laptop (GCS) is use a wifi connection to an external RTK station located outside.		the ground station laptop (GCS) is use a wifi connection to an external RTK station located outside.

	This implementation use a "Raspberry Pi" to get the ground data and send		This implementation use a "Raspberry Pi" to get the ground data and send

Xp31: /* External RTK Ground Station */

2017-03-04T14:21:11Z

External RTK Ground Station

← Older revision		Revision as of 08:21, 4 March 2017
Line 74:		Line 74:


	== External RTK Ground Station ==		== External RTK Ground Station == (Working Draft)
	(Working Draft)		With this implementation, the RTK ground application runs in a separate machine (ex."Raspberry Pi"), running a wireless "hotspot".
	With this implementation, the ground station laptop (GCS) is use a wifi connection to an external RTK station located outside.		This is a more operational way to use

			the ground station laptop (GCS) is use a wifi connection to an external RTK station located outside.

	This implementation use a "Raspberry Pi" to get the ground data and send		This implementation use a "Raspberry Pi" to get the ground data and send

Xp31: /* External RTK Ground Station */

2017-03-04T13:52:02Z

External RTK Ground Station

← Older revision		Revision as of 07:52, 4 March 2017
Line 75:		Line 75:

	== External RTK Ground Station ==		== External RTK Ground Station ==
			(Working Draft)
			With this implementation, the ground station laptop (GCS) is use a wifi connection to an external RTK station located outside.

	This implementation		This implementation use a "Raspberry Pi" to get the ground data and send

Xp31 at 13:45, 4 March 2017

2017-03-04T13:45:41Z

← Older revision		Revision as of 07:45, 4 March 2017
Line 23:		Line 23:
	Datalink: to not duplicate radio links the ground and board Ublox use the paparazzi telemetry.		Datalink: to not duplicate radio links the ground and board Ublox use the paparazzi telemetry.

	* on the ground side, the NEO-M8OP-2 is connected to the laptop using the USB connector (should be /dev/ttyAVCMX). The "rtcm2ivy" ground application (sw/ground_segment/misc/rtcm2ivy) broadcast the RTCM data from the ground ublox to the IVY bus. The paparazzi server (sw/ground_segment/tmtc/server) gets the data from the IVY bus and send it to the rover (mobiles) using the telemetry (sw/ground_segment/tmtc/link -d /dev/paparazzi/xbee -transport xbee -s 57600)		* on the ground side, the NEO-M8OP-2 is connected to the laptop using the USB connector (should be /dev/ttyAVCMX). The "rtcm2ivy" ground application (sw/ground_segment/misc/rtcm2ivy) broadcast the RTCM data from the ground ublox to the IVY bus. The paparazzi server (sw/ground_segment/tmtc/server) gets the data from the IVY bus and send it to the rover (mobiles) using the telemetry (sw/ground_segment/tmtc/link -d /dev/paparazzi/xbee -transport xbee -s 57600). All rovers (mobile) linked to the same ground station receive the RTCM data.

	* on the rover (mobile) side, the NEO-M8P is connected to the autopilot using the UART. The ublox input RTCM3 message coming from the ground, and output UBX (position) messages to the autopilot. The u-Blox can have three status: 3D, DGPS, RTK		* on the rover (mobile) side, the NEO-M8P is connected to the autopilot using the UART. The ublox input RTCM3 message coming from the ground, and output UBX (position) messages to the autopilot. The u-Blox can have three status: 3D, DGPS, RTK