CTS-SAT-1-OBC-Firmware
Loading...
Searching...
No Matches
GNSS_bestxyza_response_t Struct Reference

This is the struct for the BESTXYZA Command response. Refer to page 515-517 of the OEM7 Commands and Logs Reference Manual. More...

#include <gnss_types.h>

Public Attributes

GNSS_solution_status_enum_t position_solution_status
 Position solution status.
 
GNSS_position_type_enum_t position_type
 Position type.
 
int64_t position_x_mm
 Documentation says the point coordinates come as a double. We store as an int64 because the earth's radius(6.10^6 m) and we are storing the values as millimeters which fits within an int64. Position coordinates in millimeters.
 
int64_t position_y_mm
 
int64_t position_z_mm
 
uint32_t position_x_std_mm
 Documentation says the standard deviation of the position coordinates come as a float. The standard deviation of the position coordinates in millimeters.
 
uint32_t position_y_std_mm
 
uint32_t position_z_std_mm
 
uint64_t differential_age_ms
 Differential age in seconds. Storing as a uint64 so as to capture the millisecond accuracy.
 
uint64_t solution_age_ms
 Solution age in seconds. Storing as a uint64 so as to capture the millisecond accuracy.
 
uint32_t crc
 32 bit CRC (ASCII and Binary only).
 

Detailed Description

This is the struct for the BESTXYZA Command response. Refer to page 515-517 of the OEM7 Commands and Logs Reference Manual.

Member Data Documentation

◆ crc

uint32_t GNSS_bestxyza_response_t::crc

32 bit CRC (ASCII and Binary only).

◆ differential_age_ms

uint64_t GNSS_bestxyza_response_t::differential_age_ms

Differential age in seconds. Storing as a uint64 so as to capture the millisecond accuracy.

◆ position_solution_status

GNSS_solution_status_enum_t GNSS_bestxyza_response_t::position_solution_status

Position solution status.

◆ position_type

GNSS_position_type_enum_t GNSS_bestxyza_response_t::position_type

Position type.

◆ position_x_mm

int64_t GNSS_bestxyza_response_t::position_x_mm

Documentation says the point coordinates come as a double. We store as an int64 because the earth's radius(6.10^6 m) and we are storing the values as millimeters which fits within an int64. Position coordinates in millimeters.

◆ position_x_std_mm

uint32_t GNSS_bestxyza_response_t::position_x_std_mm

Documentation says the standard deviation of the position coordinates come as a float. The standard deviation of the position coordinates in millimeters.

◆ position_y_mm

int64_t GNSS_bestxyza_response_t::position_y_mm

◆ position_y_std_mm

uint32_t GNSS_bestxyza_response_t::position_y_std_mm

◆ position_z_mm

int64_t GNSS_bestxyza_response_t::position_z_mm

◆ position_z_std_mm

uint32_t GNSS_bestxyza_response_t::position_z_std_mm

◆ solution_age_ms

uint64_t GNSS_bestxyza_response_t::solution_age_ms

Solution age in seconds. Storing as a uint64 so as to capture the millisecond accuracy.


The documentation for this struct was generated from the following file: