Skip to content

Add rinex triple-frequency, add rinex nav, fix rinex obsevation issues#47

Open
Raviu56 wants to merge 1 commit into
google:masterfrom
Raviu56:patch-1
Open

Add rinex triple-frequency, add rinex nav, fix rinex obsevation issues#47
Raviu56 wants to merge 1 commit into
google:masterfrom
Raviu56:patch-1

Conversation

@Raviu56

@Raviu56 Raviu56 commented Jun 12, 2024

Copy link
Copy Markdown

Hello,
I had to do this as issues are not enabled on this repo.
Issues in GnssLogger - latest version - briefly:

  1. rinex output miss triple frequency like for Beidou on Xiaomi 11 phone flavors for example, it logs only 2 frequencies.
  2. Despite having nav/navigation messages in many Android phones - Redmi 11 Pro+ 5G for example- , no rinex nav output is supported
  3. rinex log in many cases have errors which can be found using gfzrnx -finp gnss_log_2024_06_03_15_05_12.24o -fout /dev/null -chk -vo 3 -vosc 3 for example, commons errors are;
 wrong MARKER NAME in header >Google GnssLogger<
incomplete epoch record
 mismatch of number of satellites(33) and records got(32)
 missing mandatory header label >SYS / PHASE SHIFT<
 format error (dot-check) for prn C43 (length 133 / 8 values)
 repair of input header label > GLONASS SLOT / FRQ #< to >GLONASS SLOT / FRQ #<
  unsupported header label >-1 GLONASS SLOT / FRQ #< found, trying to correct !
  unsupported header label >-1 GLONASS SLOT / FRQ #< for version 3.03 !
  1. Also I think you log some info as rinex 3.03 format, which are introduced into 3.04/3.05 and later.

@google-cla

google-cla Bot commented Jun 12, 2024

Copy link
Copy Markdown

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

@CUMTdestiny

CUMTdestiny commented Jun 12, 2024 via email

Copy link
Copy Markdown

@barbeau

barbeau commented Jun 13, 2024

Copy link
Copy Markdown
Contributor

@Raviu56 Thanks for the report! Could you please open separate issues for each of these items at https://buganizer.corp.google.com/issues/new?component=313183&template=1021001, including sample RINEX files, so we can take a closer look?

@Raviu56

Raviu56 commented Jun 23, 2024

Copy link
Copy Markdown
Author

@barbeau It's exclusive for googlers, @google.com

@barbeau

barbeau commented Jun 23, 2024

Copy link
Copy Markdown
Contributor

Whoops, sorry, wrong link! Please use this instead - https://issuetracker.google.com/issues/new?component=313183&template=0

@Raviu56

Raviu56 commented Jun 23, 2024

Copy link
Copy Markdown
Author

Registration is too complicated and asks for many personal info, even if I use my non-gmail email and it's confirmed by code, sorry, I cannot proceed.

@barbeau

barbeau commented Jun 24, 2024

Copy link
Copy Markdown
Contributor

Ok, let's try to do this in the comments here then.

  1. Despite having nav/navigation messages in many Android phones - Redmi 11 Pro+ 5G for example- , no rinex nav output is supported

GnssLogger currently only supports RINEX observations output

  1. Also I think you log some info as rinex 3.03 format, which are introduced into 3.04/3.05 and later.

This will be resolved in the next release of GnssLogger.

For the other issues, could you please add a comment (1 per issue) for each of them with more details, including sample RINEX files?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants