Trimble Inc. 10950 Manual De Usuario
Alloy GNSS reference receiver User Guide
107
Overview
This section describes the Programmatic Interface which is a method of remotely controlling a
Trimble GNSS receiver using easily generated text-based commands. This interface exists in parallel
to the Graphical User Interface (GUI) that is accessible through the HTTP and HTTPS ports of the
receiver. The GUI interface uses HTML web pages to provide visual, point-and-click access to all
information and controls on the system. It is designed to be interactive with the user, and is not
well suited for automating remote control tasks. The Programmatic Interface provides a matching
functionality using a more machine friendly method. It accepts easily generated, text-based
commands as requests to the GNSS receiver. The GNSS receiver responds with simple, plain-text
answers that are easily interpreted by an automatic process.
Trimble GNSS receiver using easily generated text-based commands. This interface exists in parallel
to the Graphical User Interface (GUI) that is accessible through the HTTP and HTTPS ports of the
receiver. The GUI interface uses HTML web pages to provide visual, point-and-click access to all
information and controls on the system. It is designed to be interactive with the user, and is not
well suited for automating remote control tasks. The Programmatic Interface provides a matching
functionality using a more machine friendly method. It accepts easily generated, text-based
commands as requests to the GNSS receiver. The GNSS receiver responds with simple, plain-text
answers that are easily interpreted by an automatic process.
Programmatic commands are submitted to the GNSS receiver using the same TCP/IP channels used
by the GUI-browser interface. They both use the HTTP or HTTPS protocol to submit CGI requests
encoded in URLs. Response documents are then returned to the remote computer using the same
channels. The only differences between GUI requests and Programmatic requests are the exact
URLs used and the types of responses returned.
by the GUI-browser interface. They both use the HTTP or HTTPS protocol to submit CGI requests
encoded in URLs. Response documents are then returned to the remote computer using the same
channels. The only differences between GUI requests and Programmatic requests are the exact
URLs used and the types of responses returned.
Secure operations using the Programmatic Interface are available in two ways. First, the interface
can be accessed through the HTTPS protocol, which encrypts all transactions. This prevents anyone
from observing the interactions. Note that the commands can be accessed over the unencrypted
HTTP port as well, which is not encrypted.
can be accessed through the HTTPS protocol, which encrypts all transactions. This prevents anyone
from observing the interactions. Note that the commands can be accessed over the unencrypted
HTTP port as well, which is not encrypted.
The second level of security is provided by the HTTP Security mechanism. All programmatic
commands are handled through the web server inside the GNSS Receiver. This security has three
levels:
commands are handled through the web server inside the GNSS Receiver. This security has three
levels:
State
Access
Disabled
Any user can execute any programmatic command.
Enabled
A valid user account must be supplied with each Programmatic
Interface request. The capabilities for that account may limit the types
of requests that the user can make.
Interface request. The capabilities for that account may limit the types
of requests that the user can make.
Enabled With
Many commands can be executed without providing a username and
Anonymous Access
account. These would be primarily "show" commands that will not
alter the configuration of the system. The capabilities of the
anonymous user can be customized to include file download and file
deletion. However, Programmatic Commands beyond that limited
scope are not allowed unless an authorized account name and
password are used.
alter the configuration of the system. The capabilities of the
anonymous user can be customized to include file download and file
deletion. However, Programmatic Commands beyond that limited
scope are not allowed unless an authorized account name and
password are used.
Note that HTTP Security is NOT enabled by default. You must set Enabled or Enabled-With-
Anonymous-Access restrictions before accounts and passwords will be required for the
Programmatic Interface. See sample code later in this document for examples of how you can
encode your requests when a Security mode is enabled.