Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade to Reachview 3 and got lower frame rate and error message #19

Open
spcrobocar opened this issue May 1, 2022 · 4 comments
Open

Comments

@spcrobocar
Copy link

I have been using this repo for my Reach RS+/Reach M+ pair and it worked well. I could get RTK 14 frames per second.

However, today, I upgrade my iOS app to ReachView 3 and it, to my surprise, also upgraded my M+ firm ware. Now I only get 1 frame per second, and a lot of warning messages like this:

Regex didn't match, sentence not valid NMEA? Sentence was: '$GBGSA,A,3,,,,,,,,,,,,,17.0,2.8,16.72C'
[WARN] [1651443826.909854]: Regex didn't match, sentence not valid NMEA? Sentence was: '$GBGSA,A,3,,,,,,,,,,,,,17.0,2.8,16.7
2C'
[WARN] [1651443827.902889]: Regex didn't match, sentence not valid NMEA? Sentence was: '$GBGSA,A,3,,,,,,,,,,,,,17.0,2.8,16.7*2C'

How can I fix this?

@spcrobocar spcrobocar changed the title Upgrade to Reachview and get lower frame rate and error message Upgrade to Reachview 3 and got lower frame rate and error message May 1, 2022
@goldbattle
Copy link
Member

Do you have a screenshot on how you configure it in the app? What is the output configuration look like?

@spcrobocar
Copy link
Author

IMG_1986
IMG_1987
This is the RTK setting

@spcrobocar
Copy link
Author

IMG_1989
IMG_1990

This is "Position output" settings.

@oym1994
Copy link

oym1994 commented Nov 1, 2022

Have you solved this problem? I also met this problem.

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

No branches or pull requests

3 participants