Activity Feed › Discussion Forums › GNSS & Geodesy › Crash course on connecting to NYSNet using Magnet w/ FC5000
Crash course on connecting to NYSNet using Magnet w/ FC5000
Posted by mark-flora on October 8, 2018 at 1:56 pmWe finally upgraded to Topcon Magnet and a FC5000 and was wondering if someone good give me a quick run down on how to connect to NYSNet while using my phone as a hot spot?
I’ve tried going through the job configurations of Network VRS, but can’t seem to figure out how to make everything work. Any help would be much appreciated.
mark-flora replied 5 years, 6 months ago 4 Members · 20 Replies- 20 Replies
1. Before attempting any configuration set up in Magnet Field, establish the Wi-Fi connection between the phone and the FC-5000.
2. In Magnet, you will need to create a “Network rover profile.” To do this, from the main menu, go to Configure, and on the Configuration Menu, select, “Survey.
3. There should already be a “My Network RTK” configuration in the software that you can edit. When I go to that screen in Magnet, the first screen allows me to give the profile a unique name if I prefer. For “Type” you will select “Network RTK” from the pulldown menu. Corrections should be “VRS.” Hit Next.
4. Select the brand of receiver, presumably Topcon or Sokkia.
5. On the next screen, you will specify the exact receiver model you are using, as well as the Elevation Mask. The Antenna will be the same as the Receiver model, presuming you are using an integrated receiver. If you are using a 2 meter rod, you can enter 2M and it will change it to US Survey Feet for you.
6. The next screen is labeled “Rover Radio” and in here, you should check the “Controller” box. When you do so, it will change the “Type” and “Model” boxes to “Internal Cellular” and “Existing Network Connection” respectively, which are appropriate to your scenario.
7. The next screen is labeled “Internet Address” and it is here you will enter the IP address and the Port. This information should be entered as in this example: 170.143.36.58:8002 (this is the address for the TN DOT network) Just note that the IP address and the Port you are assigned to use are entered in the same field, separated by a : (full colon)
8. The Label in this field is whatever name you choose to call this correction service. It is important to click “Add New” AFTER you enter the IP and Port to save the information where you can give a name that means something to you.
9. In the next screen, you will enter the User ID and password that was assigned to you. Some networks do not require this but most do.
10. The final screen the receiver configuration that pertains to setting up to use a network rover allows you to input a Lat/Long for GGA. This is a new wrinkle for version 5.1 and I am not familiar with it but it does not seem to matter for public networks.
The rest of the settings are for general configurations settings.
Survey in good health!
Once you have created the profile and go to connect, you will select the “Network Rover” profile you created before. You are asked to specify a GPS and/or Optical instrument you intend to use when you setup your job.
You will then select “Connect” on the Main Menu in Magnet Field.
Specify “Connect to Rover” and it will initiate the Bluetooth search, or you can check the “Connect to last” box.
When the receiver connection is established, Magnet will then go to the internet connection and open the IP connection. Assuming that information is correct, and the connection is established, you will then need to select a “Mount Point.” The Mount Point is the reference network connection that you are going to use. This can either be a single base or a VRS connection. Magnet displays the list of available mount points by whatever names the network has assigned to them.
Typically, you will either connect to the nearest station, or VRS. You would only want to connect to the “Nearest” or “Closest” if you are, say, less than 10 miles from the reference station. If you are further than that, you would be better off to select VRS as your connection option.
Is 170.3.245.18:8080 the correct address for NYSNet?
I??m connected to the server now, but it is staying in autonomous mode and won??t go fixed.
also not sure which mount point I should be choosing.
I do not know about the IP address, but if I am not mistaken, the NY network is a Trimble network and 8080 is a typical port number for their networks. I would be looking for a Mount Point that has RTCM3 in the description.
I would expect that their designations would include something such as “Closest” for a single baseline connection, or VRS (Trimble proprietary designation) for a modeled network solution.
Mark,
Did you create a new account with NYSNET?
The correct is rtn.dot.ny.gov:8080
If you have GPS/GLONASS/GALILEO the correct mount point is net_msm, if not the use netcell_imax_RTCM3x
Be certain to always use Datum NAD83_NO_TRANS
NYSNET is not a VRS, use MAC. I suggest not using “nearest” mount point, it has no network corrections.
- Posted by: leegreen
Mark,
Did you create a new account with NYSNET?
The correct is rtn.dot.ny.gov:8080
If you have GPS/GLONASS/GALILEO the correct mount point is net_msm, if not the use netcell_imax_RTCM3x
Be certain to always use Datum NAD83_NO_TRANS
NYSNET is not a VRS, use MAC. I suggest not using “nearest” mount point, it has no network corrections.
Thanks Lee. I got it working now after reading your message and changing the settings to what you said.
Only thing I’m not sure of is if I’m using the “nearest point” setting or not. I’m using netcell_imax_RTCM3x as a mount point.
Yes, netcell_imax_RTCM3x as a mount point is correct for GPS and Glonass. You would have to purchase an OAF to enable Galileo on your GR5. It is not available for GR3.
I’m using the net.msm mount with Sokkia GCX3 and get 18 to 24 SV’s.
Net.msm means Network Multiple Single Messaging. Which means it would get all SV’s on singles, including L5, Galieo and BDS.
Yeah I had looked into upgrading to the Galileo OAF on our GR5??s, but the cost was a little too salty for me. It was around $1500 for each. Seems a little steep for what it is, but I??ve heard that it works quite well so I??m not sure.
Anyway, I??ve got everything working now thanks to everyone??s help. Tomorrow I??ll do some checking to make sure it??s all good. Thanks again Lee and Jerry. I never would have figured that out on my own.
Thanks Lee.
Looks as if my thought that NY was a Trimble network was either out of date, or simply always incorrect. It is always best to get advice from someone with direct experience.
NYSNET has always been a Leica RTN, not VRS. They just updated to MSM last week.
Re: Adding US L5 or Galileo to your GR-5…
I do not know what impact this will have on OAF pricing but if history is an indication, the prices on the OAF upgrades to add L5 tracking or the Galileo and/ or Bei Dou signal tracking for Topcon GR-5 receivers and GR-5 receivers is likely to change in the near future. With the release of the HiPer VR, the whole enchilada of signals is bundled in one OAF at a significantly lower price than the GR-5 or HiPer HR.
Last time something like this came around was when the GRS-1 network rover was released, Topcon had to rethink their pricing for the GLONASS option and it resulted in a roughly 2/3 price cut for the GLONASS option.
Of course, as yet there has been no mention of this but with the price disparity between those three receivers, I look for Topcon to have to do something if they want to be able to sell the GR-5 hand HiPer HR units.
Jerry,
I purchase my hyper-v from Topcon 5 years ago. I have the original article that said that they would support the Galileo and compass. Topcon has since changed the specs on the hyper-v and removed Galileo and compass. This seems to be false advertising to me. What are your thoughts?
A release from Topcon? Or a magazine Article?
It was a release from Topcon on their website. Which has silently been changed to not include Galileo and Compass (aka BDS).
But you can still find other sites listed below with links stating Galileo/BDS and even L5 are available in the Hiper V.
http://gpsworld.com/hiper-v-featuring-vanguard-technology-offered-by-topcon/
So I did some checking yesterday with our NYSNet setup and I’m coming up with a 3.21′ difference from our control (-3.17′ in Northing, 0.53′ in Easting, and -1.69′ in Height). Control was confirmed by both OPUS solution, and Post Processing with results being within 0.01′ in both Northing and Easting.
Any ideas on why I’m getting this much of an error? It must be some setting that I have incorrect in the job configuration I’m guessing.
Yes, I have an idea.
I wish you would contact me for some formal training. You are wasting a lot of time and money learning this by trial and error.
!
!
!
!
!
!
You most likely selected Datum NAD2011 in Magnet Field. As mentioned earlier in this thread you MUST use Datum NAD83_NO_TRANS. This often equates to 3.78ft difference. NYSNET has already corrected for NAD2011, you are applying the correction again.
You can make the Datum change in Magnet Field job, and the software we recompute all the raw data.
If that does not work, then check your units. US Survey feet vs International Feet.
I am using NAD83_NO_TRANS and still have the difference between the two and I am using US Survey feet for units.
Do I still want the Projection in SPC83-New York (Central), or should that be set to none?
Then you have something else incorrect.
Just yesterday I compared a 3 hour OPUS with a NYSNET RTN, and it matched within 0.04′.
Lee, I started to reply but sending out 3 HiPer V systems and GT-500 robots plus Uncle Bill Gates deciding my computer MUST reboot to complete installing updates killed my post.
I would not ascribe motive to the incorrect statements in the initial ad slicks for the HiPer V. But I too saw that same thing in print. Everything about the HiPer V should be capable of supporting L5 and Galileo at least because the chip in the HiPer V is the same as what is in the GR-5. But it does not support anything other than GPS and GLONASS and I believe that is simply because the actual GPS antenna inside the receiver does not have the required elements to receive those signals. And to be fair, when the HiPer V was released there was effectively nothing to track but the two constellations the V supports.
I did another test yesterday and everything is working correctly now. I’m getting a difference of less than .03′ horizontal and .05′ vertical.
Only thing I can think of is that I didn’t give it enough time to solve. I noticed yesterday that it said it was fixed, but it took upwards of a minute until it was agreeing with the control. Thanks again for the help.
Log in to reply.