Trimble NetR9 Receiver - Current Firmware Version - 5.37


Critical Note:

Data can be permanently lost during a firmware update. Before updating the firmware on any receiver, download and backup any data files stored on the receiver's internal memory.

We also recommend saving a clone file of the receiver's configuration before applying a firmware update.

We recommend that all users install this update as soon as practical, or if any of the features noted in the release notes below are of particular importance. All new receivers should be deployed with the latest version installed.

Due to critical security and functionality flaws that have been addressed  we recommend that all receivers running firmware versions earlier than 5.22 be updated immediately .

Users who enable Voltage and Temperature Logging, available with firmware version 5.03, will experience translation errors with Teqc versions built on or before 23 Jun 2015. If logging Voltage and Temperature is required, users should install the latest version of Teqc.

The update may be installed through the web interface and applied safely using a remote connection. If your receiver's firmware warranty date is expired you should contact Trimble. Warranty requested from Trimble.

NetR9 Firmware V5.37 (~6.3MB)

Trimble NetR9 Resource Page

UNAVCO standard configuration file for the NetR9  

Specific information regarding the use of NetR9 for Polar Applications is available at the Remote Station Engineering Page

New features or changes between 5.33 and 5.37:

New Features and Changes NTRIP Caster Login Security
►  Supports up to 30 unique different logins instead of the traditional standard eight logins.
►  Improved the security features in the NTRIP Caster by limiting total the amount of logins a user can have when accessing the Ntrip caster when setting up a login.
►  Fixed issues with NTRIP Caster stalls in the web interface.

Data Logging
►  Upgraded internal T02 to RINEX converter to include more GLONASS observables in the RINEX Files.
►  FTP Push enhancements with zipped Hatanaka for better data transfers.
►  RINEX 3.02/3.03 file naming improvements with Glonass observables.
►  Download and convert multiple files at one instance in the web interface.
Data formats
►  Better tracking capability for Galileo E5A and E5B MSM7 tracking observables.
►  Supports tracking and data logging of QZSS PRN 199.
►  Enhancements with auto select for RTX beams for better quality with improvements with longitude positions.

Web interface
►  Fixed page display loading errors with Internet ExplorerTM and Microsoft EdgeTM .
►  Added more information in the MSS summary configuration in regards to RTX configurations.
►  The AutoReboot timer function has been shifted to the Receiver Reset page. The receiver can reboot at given times specified by the reboot settings. The auto reboot timer also provides a method to recover from the unlikely occurrence that a NetR9 receiver is unable to communicate without a forced system restart).
 

New features or changes between 5.30 and 5.33:

New Features and Changes NTRIP Caster Login Security

►  Supports up to 30 unique different logins instead of the traditional standard eight logins.
►  Improved the security features in the NTRIP Caster by limiting total the amount of logins a user can have when accessing the Ntrip caster when setting up a login.
►  Fixed issues with NTRIP Caster stalls in the web interface.

Data Logging
►  Upgraded internal T02 to RINEX converter to include more GLONASS observables in the RINEX Files.
►  FTP Push enhancements with zipped Hatanaka for better data transfers.
►  RINEX 3.02/3.03 file naming improvements with Glonass observables.
►  Download and convert multiple files at one instance in the web interface.
Data formats

►  Better tracking capability for Galileo E5A and E5B MSM7 tracking observables.
►  Supports tracking and data logging of QZSS PRN 199.
►  Enhancements with auto select for RTX beams for better quality with improvements with longitude positions.

Web interface
►  Fixed page display loading errors with Internet ExplorerTM and Microsoft EdgeTM .
►  Added more information in the MSS summary configuration in regards to RTX configurations.
►  The AutoReboot timer function has been shifted to the Receiver Reset page. The receiver can reboot at given times specified by the reboot settings. The auto reboot timer also provides a method to recover from the unlikely occurrence that a NetR9 receiver is unable to communicate without a forced system restart).

New features or changes between 5.22 and 5.30:

Web User Interface and Front Panel
The Met-Tilt configuration page now displays returned results showing the command sent, time sent, returned result, and time of result.

Power
The AutoReboot Watchdog routine is now available on the Reset web page. If this feature is enabled, the receiver will restart or cycle power if no commands are received within a specified period of time.
• Status
– If enabled, this line shows “Enabled” followed by the time remaining. If disabled, the status line shows “Disabled”. This field is updated every 5 seconds and will change if the configuration is changed through the programmatic interface.
• Enable
– Enable/disable the watchdog.
• Timeout
– Timeout period after which a restart or power cycle is performed. The timeout is entered here in minutes as a more convenient unit than seconds, although the programmatic interface uses seconds.
• Cycle Power
– Enable for a power cycle using a 60 second sleep operation or disable for a simple reset.
• OK
– Sets the new configuration and resets the AutoReboot Watchdog timer. If the Timeout value is out of range, the OK operation fails but the Timeout field is filled in with the nearest min/max acceptable value.
• Cancel
– Leaves the web page without changing the configuration or current AutoReboot watchdog timer value.

Programmatic Interface
Sending the SET command always resets the watchdog timer when enabled. The full command format is as follows where the “minutes” parameter is required and the “cyclePower” parameter is optional.
SET command format
• prog/set?autoreboot&minutes=TIMEOUT&cyclePower=ENABLE
• minutes=TIMEOUT
Watchdog timer timeout value in minutes. Use “0” to disable. Must fall in the range from 30 minutes to 43200 minutes (30 days).
• cyclePower=ENABLE
The “cyclePower” value is optional and may take on a value of “0” to perform a simple restart or “1” to trigger a power cycle with a 60 second sleep interval. Omitting this parameter results in a restart with no power cycle.
SHOW command format
The format of the SHOW command is as follows.
prog/show?autoreboot
Example usage
• Enabled for 30 days with a simple restart:
AutoReboot minutes=43200 cyclePower=0 secondsRemaining=2591246
• Enabled for 30 minutes with a power cycle:
AutoReboot minutes=30 cyclePower=1 secondsRemaining=1795
• Disabled:
AutoReboot minutes=0 cyclePower=0 secondsRemaining=0
General
• Updated list of supported antenna models.
Tr a c k i n g
• Improved handling of Galileo almanac and ephemeris data.
• EVEREST™ multipath mitigation updated to account for GNSS modernization.
• Improved cycle slips on GPS L5 and GLONASS G2P.
• General updates for EGNOS satellite list.
• Improved handling of inter-frequency bias values.

New features or changes between 5.20 and 5.22:

   Tracking

    Improved QZSS LEX tracking.
    Improved Galileo E5A/B tracking and SNR reporting.
    Improved handling of clock steering data for position fixes.

    Data logging

    RINEX v3.02/3.03 now include ‘GLONASS Slot / FRQ #’ header records.
    RINEX files now record the receiver type in header records as ‘TRIMBLE NETR9’.
    Addresses issue in firmware version 5.20 that may cause RINEX observables to be omitted from files.
    Corrects Hatanaka compressed files to use the correct file extension of ‘*.CRX’.
    RINEX version 3 long filenaming convention updates:
        –  Resolves incorrect day of year.
        –  Resolves incorrect file start times.
        –  Now uses ‘01D’ for the file duration of one day.  Previously, this was recorded as ‘24H’.
    Resolves failed FTP Push operations. Previously, if a FTP Push operation to one FTP server failed, pushes to alternate FTP servers may hang.
    Corrects Hatanaka compressed files to use the correct file extension of ‘*.CRX’.
    RINEX version 3 long filenaming convention updates:
        –  Resolves incorrect day of year.
        –  Resolves incorrect file start times.
        –  Nowuses‘01D’forthefiledurationofoneday.Previously,thiswasrecordedas‘24H’.
    Resolves failed FTP Push operations. Previously, if a FTP Push operation to one FTP server failed, pushes to alternate FTP servers may hang.
    Improved read/write operations to internal memory, which improves memory stability and protects against memory corruption.

UNAVCO NOTE:   This improvement is expected to fix the "No Space" bug that can occasionally disable the internal memory, but Trimble has also implemented a "Watchdog" that will automatically reboot the receiver if a "No Space" condition is encountered.  The reboot is triggered under the following circumstances:
     - Auto-delete must be enabled on internal memory.
     - At least one data logging session must be configured and enabled.
     - Time must be known to ensure the power cycle wake up time routines can operate.
A power cycle is performed if the reported file space is 0KB for at least an hour. If a power cycle is required, a warning message is logged to memory and the receiver is programmed to shut down for 60 seconds and then restart. If a shutdown/sleep operation fails, it will be tried again a minute later. No more than 10 power cycle attempts are made.
We recommend that users monitor their receivers for unexpected reboots and report them to Trimble if suspicious behavior is encountered.  The new UNAVCO configuration file contains Email client and Email alert settings to accomplish this.

Web interface and front panel

        Improved XML formatting of various web interface pages.
        Resolves issue where a factory reset would not change the HTTPS port to default values.
        Resolves issue where static IP addresses may not be applied when installing from a clone file.
        Improved ‘Clear Satellite Data’ routine to prevent rare occurrence of data being stored and not cleared after the command was sent.
        Resolves issue where RTX solutions may not be produced after starting an application file.
        Additional data logging Programmatic Interface support for the following commands:
            –  /prog/show?sessions
            Returns configuration of currently defined sessions.
            –  /prog/show?session&name=Test
            Returns configuration of requested session.
            –  /prog/set?session&name=Test&enable=yes
            Enable can be 'yes' or 'no'. If yes, then the session can log data, when its schedule allows. If no, then the Session is created, but logging not enabled. The default value for a new session is 'yes'.
            –  /prog/set?session&name=Test&schedule=continuous
            Schedule determines when the session can be run. There are four possible types:
                –  Continuous – Logs continuously, breaking the data into separate files of the specified duration.
                –  Daily@hh:mm – Starts every day at the specified hours (hh, from 00 to 23) and minutes (mm, from 00 to 59).
                –  Once@YYYY.MM.DD.hh:mm – Runs one time only, starting at the given Year (YYYY), Month (MM), Day (DD), hours (hh) and minutes (mm). The month range is 1 to 12. The day range is 1 to 31.
                –  Manual – Runs for the specified duration, starting when the user enables the session. When finished, the session automatically disables itself.
                For those schedules that require dates or times, the formats must be as shown. An invalid date or time will cause the command to be rejected. The default schedule for a new session is 'Continuous'.
            –  /prog/set?session&name=Test&duration=60
            Duration is the data logging time for this Session, in minutes. For continuous logging sessions, it describes the length of the individual files. The default value for a new session is 60 minutes. Valid duration range from is from 1 to 1440 minutes.
            –  /prog/set?session&name=Test&measInterval=15
            This describes the GNSS measurement logging interval, in seconds. Valid settings are: 0.02, 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10, 15, 30, 60, 300 and 600. The value can also be set to '0' or 'off' to disable measurement logging. The default for a new session is 1 second.
            –  /prog/set?session&name=Test&volttempinterval=300
            This describes the logging interval of temperature and voltage records, in seconds. Valid settings are: 1, 2, 5, 10, 15, 30, 60, 300, and 600. The default for a new session is 300 seconds.
            –  /prog/set?session&name=Test&filesystem=internal
            Filesystem can be ‘internal’ or ‘external. If internal, the created session will be logged to internal memory. If external, the created session will be logged to an external USB drive, if present.
            –  /prog/set?session&name=Test&pathstyle=sessiondate
            Defines the folder structure for the logging session. Variables are:
            – Flat
            – Date
            – DateSession
            – SessionDate
            – YYYYMM
            – YYYYMMDD
            – YYYYMMSession
            – YYYYMMDDSession
            –  /prog/set?session&name=Test&namestyle=systjjjh
            Defines the file naming convention for the created session. Variables are: – SystJJJh
            – SystJJJhmm
            – YYMMDDhh
            – YYMMDDhhmm
            – System____YYYYMMDDHHmm – SystYYYYMMDDHHmm
            Filenaming conventions using the ‘#’ symbol are not supported at this time, though are available via the web interface.
            –  /prog/set?session&name=Test&ftppush=1
            Allows FTP Push to be enabled and selects which FTP server to use. Variables are:
                –  0 = FTP Push Disabled
                –  1 = FTPServer #1
                –  2 = FTPServer #2
                –  3 = FTPServer #3
                –  /prog/set?session&name=Test&posInterval=60
                This describes the position logging interval, in seconds. Valid settings are: 0.02, 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10, 15, 30, 60, 300, and 600. The value can also be set to '0' or 'off' to disable position logging. The default for a new session is 60 seconds.
            –  /prog/set?session&name=Test&ftppush=1&FTPConvertType=4
            Specifies which file format should be used for FTP Push routines. Variables are:
                –  0 = None (FTP T01/T02 files)
                –  42 = T01/T02/T04 file & Zipped V3.03 RINEX (Observables & Combined Ephemeris)
                –  19 = T01/T02 file & Zipped V3.02 RINEX (Observable & Ephemeris)
                –  17 = T01/T02 file & Zipped V3.00 RINEX (Observable & Ephemeris)
                –  18 = T01/T02 file & Zipped V2.12 RINEX with QZSS Extensions (Observable & Ephemeris)
                –  16 = T01/T02 file & Zipped V2.11 RINEX (Observable & Ephemeris)
                –  14 = Google Earth – Lines
                –  15 = Google Earth – Lines and Points
                –  40 = Zipped V3.03 RINEX (Observables & Combined Ephemeris)
                –  41 = Zipped V3.03 Hatanaka RINEX (Observables & Combined Ephemeris)
                –  26 = Zipped V3.02 RINEX (Observable & Ephemeris)
                –  29 = Zipped V3.02 Hatanaka RINEX (Observable & Ephemeris)
                –  4 = Zipped V3.00 RINEX (Observable & Ephemeris)
                –  10 = Zipped V3.00 Hatanaka RINEX (Observable & Ephemeris)
                –  20 = Zipped V2.12 RINEX with QZSS Extensions (Observable & Ephemeris)
                –  23 = Zipped V2.12 Hatanaka RINEX with QZSS Extensions (Observable & Ephemeris)
                –  1 = Zipped V2.11 RINEX (Observable & Ephemeris)
                –  7 = Zipped V2.11 Hatanaka RINEX (Observable & Ephemeris)
                –  13 = BINEX
            –  /prog/set?session&name=Test&suffix=A
            Values are 'a'-'z', and 'A'-'Z'. The suffix is a single, lower-case or upper-case letter, which is used as an identifying character in file names generated by this session. The default for a new session is 'D'.
            –  /prog/set?session&name=Test&smoothranges=no
            –  /prog/set?session&name=Test&smoothphases=no
            Enables or disables the ‘Smooth Phase’ option. The default value is ‘No’. Variables: Yes | No
            –  /prog/set?session&name=Test&includedoppler=yes
            Enables or disables the logging of Doppler values. The default value is ‘No’. Variables: Yes | No
            –  /prog/set?session&name=Test&logcorrections=no
            Enables or disables the logging of received corrections. The default value is ‘No’. Variables: Yes | No
            –  /prog/set?session&name=Test&lograwnavdata=no
            Enables or disables the logging of raw navigation data. The default value is ‘No’. Variables: Yes | No
            –  /prog/set?session&name=Test&logsbasdata=no
            Enables or disables the logging of SBAS data. The default value is ‘No’. Variables: Yes | No
            –  /prog/set?session&name=Test&emailpush=yes&emailconverttype=26&emailtoaddress=trimble@trimble.com
            Specifies parameters for Email Push routines. Variables: Yes | No. Conversion parameters are the same as previously listed for FTP Push. The ‘Email to Address’ variable is the destination email address.
            –  /prog/set?session&name=Test&yearInFtpZipFileName=no
            Defines if the FTP Zip filenames have the year added to the filename. Variables: Yes | No.  
            –   /prog/set?session&name=Test&autodelete=yes
            Enables or disables ‘Auto Delete’ option. Variables: Yes | No.
            –  /prog/set?session&name=Test&poolmode=stop&poolsize=2
            Specifies logging pool operation. The first variable is the pool mode. Variables include Stop, Delete, or Off. The second variable is the pool size in MB.
            –  /prog/delete?session&name=Test
            Deletes the requested session.
            Additional power control Programmatic Interface support for the following commands:
                –  /prog/show?powercontrols
                Returns the current power settings including the power on volts, power off volts, power down override setting, UPS setting and timeout value, and Power over Ethernet setting.
                –  /prog/set?powercontrols&upvolts=11.8
                Sets the power on voltage. Range: 10.8 V to 15.0 V. Default: 11.8 V.
                –  /prog/set?powercontrols&downvolts=10.8
                Sets the power off voltage. Range: 9.5 V to 15.0 V. Default: 10.5 V.
                –  /prog/set?powercontrols&powerdownoverride=yes
                Enables or disables the ‘Shutdown Override’ feature. Variables: Yes | No.
                –  /prog/set?powercontrols&ups=35
                Enables the internal battery UPS. ‘Enabled’ will turn this feature on, otherwise the UPS timeout value must be specified in units of seconds. Range: 35 to 600 seconds.
                –  /prog/set?powercontrolsðernetpower=yes
                Controls Power over Ethernet setting. Variables: Yes | No.
                Enables or disables the ‘Smooth Pseudorange’ option. The default value is ‘No’. Variables: Yes | No
            Additional charging control Programmatic Interface support for the following commands:
                –  /prog/show?chargingcontrols
                Returns current charging controls.
                –  /prog/set?chargingcontrols&mode=always&minvolts=12.0
                    –  Defines variables for charging controls.
                    –  ‘Mode’ variables: Never|WhenOn|WhenOff|Always
                    –  ‘minVolts’ variables: 10.8 V to 15.0 V. Default: 12.0 V
                    –  ‘ethernetCharging’ variables: yes|no

New features or changes between 5.15 and 5.20:

Ge ne ral

Networking and Security

Tracking

Data Logging

Data Formats

Web User Interface and Front Panel

New features or changes between 5.10 and 5.14:

General

Data Formats

Data Logging

Tracking

Networking and Security

Web Interface and Front Panel

New features or changes between 5.03 and 5.10:

General

Data Formats

Data Logging

Tracking

Networking and Security

New features or changes between 5.01 and 5.03:

General

Data Formats

Data Logging

Tracking

Networking and security

Power

Web interface and front panel

New features or changes between 4.93 and 5.01:

General

Data Formats

Data Logging

Tracking

Positioning

Networking and Security

Web Interface and Front Panel

New features or changes between 4.85 and 4.93:

General

Data formats

Data logging

Tracking

Networking and security

Application files

Web Interface and Front Panel

Known Issues

Upgrade Procedure

Make sure that the receiver firmware warranty date is 1 May 2014 or later.

Use one of the following methods:

New features or changes between 4.70 and 4.85:

General

Data formats

Data logging

Tracking

Power

Application files

Networking and security

Web interface and front panel

New features or changes between 4.62 and 4.70:

General

Data formats

Data logging

Tracking

OminSTAR

Application files

Networking

Web User Interface and front panel

  1. Now allows for simultaneous input and output of correction messages.
  2. Shows separate RTK motion state and receiver motion state only when the Position Monitoring option bit is installed. When Position Monitoring is enabled, the RTK engine motion state is set to kinematic while the receiver motion state remains as configured. The RTK engine motion state status appears in the Receiver Configuration / Position page. When the position monitor is disabled, the RTK motion state is set back to the receiver motion state.

  3. Shows the reference position entered in the position monitoring page in the position graph if it is different from the reference station position in the reference station page.

  4. When Position Monitoring is enabled, it suppresses front panel warning message if receiving and transmitting correction messages at the same time.

 

New features or changes between 4.61 and 4.62:

General

Data formats

Tracking

Power

New features or changes between 4.60 and 4.61:

General

Data formats

Data logging

Tracking 

Networking

Web Interface and Front Panel

New features or changes between 4.48 and 4.60:

General

Data formats

Data logging

Tracking

OmniSTAR

Application files

Networking

Web interface and front panel

New features or changes between 4.46 and 4.48:

Data formats

Data logging

Tracking

Networking

New features or changes between 4.43 and 4.46:

General

Data formats

Data logging

Power

Tracking

Networking

Web interface and front panel

 

 

Future versions with additional features for the NetR8 and NetR9 are under active development by Trimble with input from UNAVCO, and future versions will be evaluated by UNAVCO staff on a continuing basis. If you have features you'd like to see added or questions about the use of version 5.20 contact Freddy Blume



Article ID: 768
Created On: Mon, Aug 17, 2015 at 8:46 PM
Last Updated On: Thu, Jan 3, 2019 at 8:59 PM
Authored by: Henry Berglund [berglund@unavco.org]

Online URL: https://kb.unavco.org/kb/article/trimble-netr9-receiver-current-firmware-version-5-37-768.html