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

Issues with Survey Master 2.9 with facet v3.3 #431

Closed
amlago opened this issue Mar 31, 2023 · 9 comments
Closed

Issues with Survey Master 2.9 with facet v3.3 #431

amlago opened this issue Mar 31, 2023 · 9 comments

Comments

@amlago
Copy link

amlago commented Mar 31, 2023

Issues with Survey Master 2.9 with facet v3.3

I work with survey master 2.9 and Facet v3.2.
Everything works very well, it connects quickly and I see the coordinates of the point and the precision given by the Facet on the cell phone screen.

With version 3.3 the Facet connects to Survey master, but the coordinates of the point do not appear and the precision remains as a constant number on the Survey master screen and does not match what was reported by the Facet.
I don't know what changed from version 3.2 to version 3.3

@nseidle
Copy link
Member

nseidle commented Apr 24, 2023

I can only get v2.8.2 from here. Looks like I could get v2.9 from here but the v2.8.2 app is telling me I can update to v3.0.0.

image

Above: Looks like they got rid of NMEA Device in v3.0.0. I'll try to load v2.9.

Ok, v2.9 operates the same as v2.8. Did you follow these directions? I had to remember to turn on four additional NMEA messages to get it to properly report the device location: GGA, GLL, GRS, GSA, GST, GSV, RMC, VTG, ZDA

image

I was able to get RTK Fix using the v3.3 RC from April 24.

@amlago
Copy link
Author

amlago commented Apr 25, 2023

Hello.
I try with version 3.3 of 04/24 and update.
Thank you

@amlago
Copy link
Author

amlago commented Apr 25, 2023

With version 3.3 04/24 Survey Master works fine.
It does not show the base coordinates correctly but that problem already existed and it is a problem of the Survey master and not of the Facet.
Thank you

@nseidle
Copy link
Member

nseidle commented Apr 25, 2023

Glad to hear it's working! Closing this issue.

@nseidle nseidle closed this as completed Apr 25, 2023
@tonycanike
Copy link
Contributor

tonycanike commented Apr 26, 2023

@amlago do you have a theory about how Survey Master (connected to the Rover) would get the base coordinates to display? I'm interested in getting SurvPC to know the base coordinates when it's attached to the Rover. If SurvPC knows the base coordinates a number of very useful features become available - such as correcting survey-in base coordinates with more accurate coordinates on a later date and all the rover gathered coordinates can then be corrected by SurvPC.

I speculate - it's a wild guess - that perhaps if the rover forwarded the RTCM base position messages (eg 1005) from the base to the data collector then the data collector (SurvPC, Survey Master, etc.) would know the base position.

I wonder what the best way to test this idea would be.

  • create a file of $NMEA messages from a rover interleaved with RTCM 1005 from a base and play it back out to our data collectors?

  • can a Rover ZED be configured to forward certain RTCM it receives from the base on to the data collector? Is it as 'simple' as configuring the rover ZED to output RTCM 1005 on UART1? If it's getting RTCM from the radio connected to UART2, for example, would it forward them to UART1?

@amlago
Copy link
Author

amlago commented Apr 26, 2023

Hi, Tony.
I have had this problem that the apps do not recognize the base coordinates in Survey master and in SWMaps.
I do not understand why it is because in the message 1005 are the coordinates.
About SWMaps I wrote to the creator some time ago and in an update it was solved. It now displays the base coordinates correctly.
With respect to Survey master I have not had a solution and I think we will not because in the last update they eliminated the possibility of connecting by nmea device.
Regarding your application, I suppose it is the same problem with respect to 1005.
The apps correctly use the 1005 message to correct the coordinates of the points taken in the field, but they do not show you the base coordinates used.
It seems so simple......
I don't know how to correct it.
I am open to discuss the issue.
Greetings

@tonycanike
Copy link
Contributor

Hi Angel, how is SWMaps getting the RTCM 1005 messages?

Is this your configuration?

SparkFun Base --> External Radio --> space --> External Radio --> SparkFun Rover --> SWMaps

That's my configuration, except I use SurvPC instead of SWMaps. I would think the Rover needs to send RTCM 1005 to the SWMaps or SurvPC.

Tony.

@amlago
Copy link
Author

amlago commented Apr 28, 2023

Hi, Tony.
Swmaps receives the corrections by a built-in ntrip client, which it already comes with.
I give you corrections from 2 sources: 1) from the facet in base mode and sent to Rtk2go over wifi.

  1. from a cors network from my country Uruguay, called Regna-Rou from the Military Geographic Institute of Uruguay. It's free and it works pretty well.

Facet base--->Wifi---> rtk2go--->CHC I50---SWmaps
Regna-Rou--->Facet rover---->SWmaps

I am still investigating how to make Survey master read message 1005 or 1006 correctly if I use the Regna-Rou network.
I wrote them an email but did not get clear answers.

Regarding Swmaps I wrote to the creator and in an update he fixed it.

I think the solution is not in our hands, because the messages are correct, only that the apps we are using are not capable of interpreting them in the best way.
But I keep trying.....

@tonycanike
Copy link
Contributor

tonycanike commented Apr 28, 2023

So we both have this scenario in common

(RTCM source) ---> Facet Rover ---> SW Maps or SurvPC

I suspect that the Facet Rover does not forward the RTCM 1005, 1006, 1007 messages to the data collector with the $NMEA.

I believe the Rover consumes all the RTCM. I believe the Rover then generates the NMEA data stream. I speculate that the RTCM from the base does not get to the data collector.

I believe we need to ask @nseidle if the Facet can forward those RTCM messages to our data collector software.

I updated #405 to request forwarding the RTCM base position records to the data collector.

#405 originally requested two things: write the base position to the rover log file and somehow tell the data collector software where the base is. I separated the "write to logfile" part of the original #405 and moved that to #447 so there is one request per submitted issue.

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