Sat
16
Nov
2019
As an alternative to radio transmission of RTK corrections to a receiver, Carlson has developed Listen-Listen, a cloud-based data-over-IP solution. Listen-Listen requires an internet connection at the base and rover. The internet connection can be from fixed-line broadband, cellular modems in the GNSS base and rover, data collectors, or Hot-Spots.
Fixed or static IP address sims are not required. In addition, multiple rovers can simultaneously connect to a single base using Listen-Listen. It is fully hosted and computed on AWS-based processors and data center, which ensures almost 100 percent up-time.
Traditional onboard UHF radios are generally limited to one-watt power output, which gives a one- to two-kilometer range at best. 35-watt radios give you more range but typically under 5 kilometers with additional complication. Radio is also subject to terrain obstructions such as hills, buildings and dense tree cover. As long as there is a cellular signal, there is no restriction on communication range, Carlson’s Listen-Listen works at 5, 10, 20, and even 30-kilometer base lines.
Both easy-to-use and -configure with Carlson SurvCE or SurvPC data collection software, Listen-Listen requires inputting just one four-digit port number at the base station and a four-digit port number at the rover. There is no need to match frequencies, listen for interference, or check a number of other parameters required for UHF communication. Listen-Listen is a subscription-based service. It works with Carlson’s BRx6 GNSS receiver as a base station and with any rover that is compatible with SurvCE or SurvPC and support RTK corrections by direct IP.
Locate your base in a central location, at a safe/secure location, or over that known point that would not normally be in radio range. I just recently worked on a project that was a 7-mile corridor. I would locate the base at one end in a protected area over one of the primary control points and have a connection over the entire project.
Because of the ease and flexibility of setup, Listen-Listen could be you primary communication vehicle. Radio would be the backup.
Thu
10
Oct
2019
FCC LICENSING OF GNSS/RTK SURVEY RECEIVERS EQUIPPED WITH 450-470 UHF RADIOS (and using 35w repeaters)
Recently I purchased new Carlson BRx6+ receivers to replace Hemisphere S320 receivers. The S320 was equipped with 900Mhz, frequency hopping radios that did not require an FCC license. The BRx6 receivers are equipped with UHF radios which do require an FCC license. It is illegal to operate a UHF radio in the 450-470 Mhz. frequency regardless of the power used. The fines, if caught, can be significant.
I could find very little information about setting up the radios, about the appropriate frequencies to use, or about FCC licensing in either the equipment manuals or on equipment supplier websites. We at US Survey Supply are willing to help our customers setup their equipment but it is the responsibility of the customer to obtain the license with approved frequencies. There are companies that will help (for a fee) with the license application process. Or, you could potential do it yourself using the FCC ULS (Universal Licensing System). I had been told that the licensing process was difficult but decided that I should at least try and do it myself.
I am a licensed Ham, so consequently I have a FRN number and knew where to start. I logged on to the FCC License Manager: https://wireless2.fcc.gov/UlsEntry/licManager/login.jsp
Most of the information you need for the application is obvious. However, the license application is for a wide variety of license types. I went back to the internet to try and find specific information that was appropriate for radios furnished with UHF GPS/RTK equipment. There were several questions on the application where the answers were not obvious or easily found within the FCC website. Here are areas where I had problems:
I was able to make it through the application with no obvious errors (The FCC application process goes thru a review at the end to identify inappropriate responses in the application) When I got to the fee page ($170) I stopped. Even though I had passed the review process, it was apparent, that I did not understand some of the questions and responses in the application.
During my research to find answers for the application I had discovered that there were companies that would help you get your license, for an additional fee. I also discovered, talking to one of these companies, that they use a “Frequency Coordinator” in the process.
One of the questions on the FCC application referred to “frequency coordination”. Researching information on the FCC website, I did discover that there is a requirement, in some cases, for “frequency coordination”, as part of the application process. I did find a list of frequency coordinators in the FCC online information and picked the one that was geographically near me, Forest Industries Telecommunications (FIT). FIT is a non-profit organization and one of their services is to assist companies and individuals to obtain an FCC license. During my search thru the internet, Forest Industries Telecommunications (FIT), was the only company that had listed a category for GNSS/RTK operation.
I called FIT and started a conversation with Dave Smith. He was very willing to answer all my questions and, consequently, give me all the information I needed to correctly fill out the FCC application. The following are a few key issues that we discussed:
At this point in the conversation I became a little confused by these last two points. Land surveying was not a fixed base operation. Companies and individuals in the business of Land Surveying or others that use GNSS/RTK receivers routinely operate in a large geographic area. I know of several companies and individuals that operate in several states and in many large urban regions. If they need a specific frequency, tied to a fixed location, to operate within a 50-mile radius every time they setup a GNSS/RTK Base, that could be a large number of frequencies. This appeared to me to be an unreasonable and unrealistic requirement. It was at this point that I learned the following:
Historically there were a series of non-itinerant “approved frequencies” that could be licensed to surveyors without being location specific (issued for use statewide or nationwide) and did not require frequency coordination. These non-itinerant frequencies would normally require frequency coordination as a fixed base operation but had historically been approved for GNSS/RTK operation. There are literally thousands of licenses issued to surveyors that have been approved with these frequencies. Approximately two years ago, the FCC changed their “policy” and would no longer approve new applications that included these non-itinerate frequencies without the required frequency coordination.
This change was made without any formal notice or public input. The FCC just stopped approving new applications with the historic “understanding” that had been the case for many years. These thousands of existing licenses that were approved with these allowed frequencies will probably be allowed to operate in accordance with their current license and will probably be “Grandfathered-in” in any subsequent renewal. For those of us applying for new licenses, we will be required to follow the regulations for GNSS/RTK operation as described in points 9 & 10 above.
This change makes it more difficult for companies and individuals using GNSS/RTK receivers to be licensed with all of the appropriate frequencies that would be needed within their geographic area of operation. This change would also increase the use of itinerate frequencies when they are outside any of their licensed fixed base frequencies. The itinerate frequencies are heavily used in urban areas by many different users using voice as-well-as data communications. Also, there are just a small number (8) of itinerate frequencies that allow wattage up to and including the typical 35-watt repeaters and base radios used by land surveyors.
There are several issues that will impact the land surveying community resulting from this change in FCC policy.
Based on this information I decided to use FIT for the FCC application process. In consultation with Dave Smith we decided on the following: