Does AZ smartnet run on RTCM corrections? Just wondering why you wouldn’t use trimble’s proprietary correction format (CMR)? I know here, in MN, the Trimble users in our office use Trimble corrections. We do, however, need to use RTCM for the few that run Topcon equipment, since that is the correction type they are built to use. I feel like you said you are using an R12. I would love to hear the reasoning behind this decision. I like to learn.
Hi Justin- For Trimble and many other users, SmartNet (which is operated by Hexagon AB, the parent company of Leica Geosystems) recommends RTCM in most of their Connection and Configuration documentation. Because RTCM is a more "open source" type of broadcast whose details have been agreed upon by a large consortium of users, countries, and manufacturers, it is pretty commonly used in networks that are trying to maintain compatibility with a wide variety of receiver types and manufacturers. This also helps avoid hassles associated with proprietary data messages whose exact details manufacturers may, or may not, wish to fully disclose or make available to other organizations, potentially precluding other manufacturers from operating successfully or fully utilizing certain features and broadcast contents.
Does AZ smartnet run on RTCM corrections? Just wondering why you wouldn’t use trimble’s proprietary correction format (CMR)?
I know here, in MN, the Trimble users in our office use Trimble corrections. We do, however, need to use RTCM for the few that run Topcon equipment, since that is the correction type they are built to use. I feel like you said you are using an R12. I would love to hear the reasoning behind this decision. I like to learn.
Hi Justin- For Trimble and many other users, SmartNet (which is operated by Hexagon AB, the parent company of Leica Geosystems) recommends RTCM in most of their Connection and Configuration documentation. Because RTCM is a more "open source" type of broadcast whose details have been agreed upon by a large consortium of users, countries, and manufacturers, it is pretty commonly used in networks that are trying to maintain compatibility with a wide variety of receiver types and manufacturers. This also helps avoid hassles associated with proprietary data messages whose exact details manufacturers may, or may not, wish to fully disclose or make available to other organizations, potentially precluding other manufacturers from operating successfully or fully utilizing certain features and broadcast contents.