Trimble NetR9 Receiver - Current Firmware Version - 5.37

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.

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.

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).

A full list of changes between firmware versions for the NetR9 can be viewed by downloading the release notes from the following links:

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.

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:

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.

Resolves RINEX v3 issue where a ‘-‘ symbol may be written into the SNR field.

Improved file system stability during power loss and shut down sequence.

Addition of SFTP client support. Within the ‘FTP Push’ web page, SFTP is now available for selection under the ‘Transfer Mode’ dropdown box. When selected, the default port will automatically be switched to Port 22 (user editable). Upon entering the connection details and performing a ‘Test’ of the connection, the algorithm and fingerprint provided by the remote server will be displayed, and the ‘Verify’ checkbox is enabled but remains unchecked. The user must click the Verify checkbox to enable remote host verification during transfers; otherwise the key submitted by the remote host will always be accepted. Users are encouraged to use HTTPS connections in combination with SFTP for secure transmission of all credentials. Also, it is strongly recommend users enable Email Alerts on the receiver to notify them if a transfer fails due to a new fingerprint being used by the remote FTP server.

Data Formats

Improved handling of BINEX streams containing observables for more than 40 satellites. Previously this could result in the receiver generating error logs.

NTRIP connections now support SSL/TLS connections.

Resolves issue of ‘Correction Delay’ not properly being applied to outgoing corrections, if enabled.

Expanded RTCM v3.2 MSM support to include types 1 through 7. When RTCM v3.2 is enabled, the receiver now provides a ‘Multiple Signal Message Settings’ section which allows the user to specify the MSM type (1-7), which constellations to include, and a ‘Streaming Mode’ option. Streaming Mode is by default disabled which results in only records necessary for RTK operation resulting in reduced bandwidth. If the RTCM v3.2 MSM stream is intended to be used for full reference station and observable records (raw data), then the Streaming Mode option should be enabled.

Resolves Programmatic Interface issue where the returned list of satellites may be truncated.

Resolves Programmatic Interface issue where the returned tracking information omitted a space.

Real time data output via TCP ports now supports ‘Disable Nagle Algorithm’ option. By default this option is disabled. When enabled, this option reduces the transmission time of packets, though will result in higher overhead and a greater number of overall packets being sent over the network. This feature is only recommended when users observe a network delay in the transmission of real time data.

Web User Interface and Front Panel

Minor Web UI updates for language usage.

Updates to improve web page rendering in various browsers.

‘TGIP’ references on web UI have been renamed to ‘RTXIP’.

DynDNS client now returns ‘ClientName, Username, or password might be wrong’ when invalid credentials are supplied. Previously this would return ‘Invalid response from DNS Server’.

‘OmniSTAR’ menu title renamed to ‘MSS Corrections’.

Resolves issue with position plots which could become corrupt over HTTPS connections.

NTRIP clone file configurations are now included within the 'Clone IP Port and I/O Configuration'. Previously these were included with the 'Clone Miscellaneous (Everything Else)' option.

New features or changes between 5.10 and 5.14:

General

Updated antenna libraries.

Resolves an issue whereby a device running the Windows 10 operating system and connected to a receiver via a USB 3.0 connection may not recognize the receiver.

Data Formats

Resolves delayed NMEA output issue when receiver is set to Synchronous mode.

Improved geoid handling in NMEA data.

Data Logging

Improved FTP Push routine to reduce risk of task getting hung on a single file.

Improved memory handling while converting logged data files.

Improved data logging to protect against very rare occurrence of dropped epochs.

Resolves antenna height rounding error of 0.1 mm in RINEX files.

Addresses issue whereby the data logging check box may not respond.

Addresses malformed RINEX v2.11 PGM / RUN BY / DATE header record.

RINEX now supports QZSS L1-SAIF observables.

Resolves issue whereby RINEX v3.03 did not contain QZSS data.

RINEX version 3.0x files:

Now include the GLONASS bias header record (GLONASS COD/PHS/BIS#).

Now adhere to the RINEX standard for header date format in observation files.

New features or changes between 5.03 and 5.10:

General

Data Formats

NMEA GGA: When using the RTX correction service, the Reference Station ID for the GGA string is 0002.

Data Logging

Support for RINEX version 3.03.

Tracking

Updated list of RTX satellites and frequencies.

Updated OmniSTAR® libraries.

Resolves a rare issue whereby a healthy satellite may be flagged as unhealthy.

Adds support for user-selectable signal tracking bandwidth. To view this feature, on the web page, select Receiver Configuration / Position. The options for this feature are as follows:

Wide: Use this option for high-dynamic applications to allow the signal tracking to compensate for a higher rate of change in the Doppler frequency that is caused by antenna movement. Wide bandwidth signal tracking allows more noise to pass through the filter to improve high-dynamic positioning.

Narrow (default setting for all NetR9 infrastructure platforms): Use this option for low-dynamic applications where only relatively small changes in Doppler frequency are expected from antenna movement. Narrow bandwidth signal tracking allows less noise to pass through the filter to improve low dynamic positioning with better accuracy.

Networking and Security

Resolves issue in the Safari browser that resulted in a warning message that the receiver is a possible phishing site.

Resolves issue of the FTP MDTM command returning an invalid date.

A new internal web-based login page is now available to eliminate browser inconsistencies.

New features or changes between 5.01 and 5.03:

General

Minor translation updates.

Crossing the CTS and RTS pins of the serial port during power up no longer forces the receiver into Remote Monitor mode.

Data Formats

The receiver will now output NMEA GGA for VRS solution use only without the full NMEA option being enabled.

Data Logging

Data logging session configuration now contains an option to enable the logging of voltage and temperature records. If this is enabled, these features will be logged in the T02 file and will be included in the resulting BINEX files created by the on-the-fly converter.

Tracking

General GNSS tracking and acquisition improvements.

Improved GNSS tracking for solutions not containing any GPS satellites.

Improved Beidou ephemeris decoding.

Updated OmniSTAR libraries.

Networking and security

NTRIP Client configurations will no longer be refused as a result of onboard IP filtering. Additionally, the IP address and port of the NTRIP Client will appear on the I/O Configuration webpage.

IP Quality of Service (go to Network Configuration / IP Filtering and QoS on the webpage) allows the user to specify which streams are a priority to the application, and allows a maximum bandwidth to be defined for non-priority use. All other remaining bandwidth beyond the non-priority bandwidth limit will be allocated to priority streams. This is designed to maximize the performance of priority streams in applications using limited bandwidth communication links.

Power

Power logic has been updated to address an issue whereby the receiver may not recognize power being applied seconds before shutting down if the internal battery UPS is disabled.

Web interface and front panel

On the Option Detail webpage, the OmniSTAR HP option has been renamed as Dual Frequency MSS.

Data Formats

Data Logging

The Reference Station Position may now be entered on the Web UI as either Cartesian or Geographical coordinates.

FTP Push now supports user configurable FTP ports.

The daily logging schedule has been corrected to now start a new file if the file duration value is set to 1440 minutes. Previously this would not trigger a new file, but logging would continue in the existing file.

Tracking

General GNSS tracking and acquisition improvements.

Updates to account for Beidou day-of-week numbering with regard to the upcoming leap second (30 June 2015).

An issue of receiver setting an incorrect time if powered on but not yet tracking satellites when a week rollover occurs has been resolved.

Updated OmniSTAR libraries.

Positioning

An issue whereby the receiver did not switch from an RTX based solution to a local base outputting CMR corrections has been resolved.

Improved RTK and RTX high-rate positioning.

Networking and Security

NTRIP clients: — Now support a wider range of extended ASCII characters within source tables. — Now support unpopulated bit-rate fields within source tables. — Now display extended error messages where available.

The NetR9 receiver now checks TCP/IP ports before assigning them to ensure that they are not already being used by other functions in the receiver.

FTP Push now supports user-configurable FTP ports.

Web Interface and Front Panel

The Reference Station Position may now be entered on the Web UI as either Cartesian or Geographical coordinates.

An antenna initialization issue that could result in broadcast corrections not accounting for the antenna phase center offset has been resolved.

An issue where the averaged position on the Reference Station page may display too many fields after the decimal place has been resolved.

New features or changes between 4.85 and 4.93:

General

Minor translation updates.

Updated antenna database.

Updated OmniSTAR libraries

Resolves issue whereby the receiver may not be able to check if firmware update is available.

RTCM MSM messages are now supported for GPS, Glonass, QZSS, and Beidou.

BINEX:

Identifier comment updated to BNX2.

0x7f-04 updated to correctly handle null observation records. Previously the record would be truncated when null observations were included.

NMEA:

GST updated to reflect the standard deviation of unit weight when the receiver is operating in an OmniSTAR solution type.

GGA string updated to send null positions when no position is available. Previously this would send zeroes.

GBS message updated to ensure satellites have a valid SV# before populating the message fields.

The NetR9 platform now supports RTP Storage Integrity data transmission protocol. This protocol allows BINEX data to be sent to network operation centers in real-time via UDP/IP. RTP-SI will automatically retransmit unacknowledged packets to create full data archives at the network operation center. The size of the near real-time queue (for unacknowledged packets) runs from approximately 12 seconds for 10 Hz data to approximately 50 seconds for 1 Hz of data. If after that time no acknowledgement is received, the data is stored to local disk and retransmitted once the link is re-established. This format allows for epoch-by-epoch storage integrity.

Data logging

FTP Push:

Now supports an Enhanced Day directory path style (RefData.YY/Month.MMM/Day.DD).

Now includes option to include the year within the naming of zip files. When the option is enabled, pushed files will appear as filename.yyO.zip, where yy is the year.

Changes to protect against the rare occurrence whereby the receiver will attempt to continuously resend a single file.

Resolves issue where the FTP Path style /type/yyyy/ddd/site would not correctly set the "type" (format) of the file being pushed.

Improved L5 multipath reporting. Previously this could show invalid multipath data for high elevation L5 SVs.

Networking and security

Primary and Secondary DNS values are now configurable via the front panel display within the Ethernet Configuration menu.

UDP Broadcast Transmit mode now allows for editing of the port number.

Reduction in memory usage by HTTP tasks.

Wget FTP command now handles wildcards (*.T02)

Improved handling of NTRIP Caster source tables.

Improved network stability.

Improved handling of web redirects.

Resolved issue that occurred where changing a Bluetooth® PIN code to a shorter PIN could create pairing issues.

Application files

Improved handling of GZIP clone files. Previously some browsers did not provide the required information in their header information for the receiver to recognize the file type.

Web Interface and Front Panel

When setting the Reference Position coordinate using the Here or Average routine, the resulting height now accounts for the antenna phase center offset and the height of the antenna. This is also true when using the Here position within the Position Monitoring routine. Previously the resulting height from these routines would be set to the height of the antenna phase center.

Position Monitor now allows you to suspend correction outputs while the position to monitor against is outside the user-defined threshold.

In the General page (below Receiver Configuration), a control is now available to force 1PPS output even if satellites are not tracked.

The Web UI has been updated to support full 12-character passwords.

On the Web UI / Receiver Configuration / Antenna page, you can now apply antenna corrections to the RTCM V3 stream. When enabled (default), the RTCM stream sends out ADVNULLANTENNA and normalizes the corrections. When this is turned off, the RTCM stream will include the IGS antenna name in the stream.

The Receiver Options webpage has been changed to reflect an Options overview, with detailed option bits available if you click Option Detail.

Position Monitoring now shows details on events displaying the solution type, time, duration, and offsets during the event. The event details appear on the Position Monitoring web page.

The Web UI has been updated to correctly handle the keychain authentication routine on the Safari internet browser.

Known Issues

This release contains updates for various signal processing changes. As a result of these changes, it is recommended that you test compatibility with external software packages before updating all equipment. Due to changes in the Beidou signal decoding, it is known that the Trimble PivotTM platform version 3.5.4 (or lower) will not decode Beidou observables. If required, please contact your local Trimble Sales Representative or Trimble Support for information on how to upgrade.

Upgrade Procedure

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

Use one of the following methods:

WinFlash utility: Use the latest version that is available with the version 4.93 Web package.

Receiver Web User Interface: Make sure that the receiver is already running firmware version 4.xx or later. Download and install the version 4.93 *.TIMG file.

New features or changes between 4.70 and 4.85:

General

Minor translation updates.

Updated OmniSTAR libraries

RTK engine processor usage further improved.

RTX engine updated to version 3.0, improving convergence times.

RTX initializations improved in challenging environments.

Data formats

Resolves issue of PPS signal being output at 256 microseconds at 3.3V per pulse. The PPS signal is now output at 8 microseconds at 3.3V per pulse.

Position Monitoring now displays the Delta offsets from the monitoring position.

Ephemeris output can be set to OFF from the I/O Configuration page for both QZSS and Beidou systems.

Web UI rendering improvements for newer browsers.

Resolves an issue where PPP initialization strings would not allow an "&" to be used.

Resolves issues where the Email Test button did not function on the first attempt.

The OmniSTAR serial number now appears on the front panel.

The Position we page now includes a line to indicate the status of the correction controls (ON/OFF).

New features or changes between 4.62 and 4.70:

General

General operating system stability improvements.

RTK engine processor usage reduced.

Minor translation updates.

Data formats

Improved QZSS almanac handling. This resolves a rare issue where a bad almanac could cause a gap in T02/RT27 data.

RTCM version 3 no longer waits for UTC offset data to output valid GPS RTCM data after all almanac and ephemeris data has been cleared.

BINEX: Improved handling of SBAS L5 observations; Web UI now requires BINEX measurements to be enabled before MetaData can be selected; Now outputs receiver ID upon initial connnection and every 30 minutes thereafter.

RT17/27 now outputs receiver ID upon initial connection and then every 30 minutes on the hour.

NEMA: Resolves one to two missing NMEA epoch when switching OmniSTAR modes; VRS operation now results in output of NMEA GGA to eight decimal places.

T02 files updated to support RTX derived positions.

Data logging

Resolves rare issue of logging memory not being recognized.

Improved QZSS almanac handling. This resolves a rare issue where a bad almanac could cause a gap in T02/RT27 data.

Resolves issue where RINEX version 3 ephemeris files could have an incorrect month listed in the header.

Email and FTP push data files now contain the exact same number of characters. Previously these would differ by one character.

Networking

Resolves rare issue where a firmware or clone file upload may fail over HTTPS.

Resolves issue where FTP Push functionality could get hung on a single file which was partially written to the FTP server.

Improved UPnP handling.

TCP/IP ports now support up to 50 TCP connections to a single port.

NTP Server and Client functionality split into two separate tasks to reduce dependencies.

Web User Interface and front panel

Updated Web User Interface (UI). The Web UI has been refreshed to maximize the screen area available to display data. The menu bar can now be hidden to further increase the available screen size. Additionally, the Web UI now uses a "cookie" to recall the last visited page, allowing you to return to it.

Position Monitoring updates:

Now allows for simultaneous input and output of correction messages.

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.

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.

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

Improved GUI bandwidth and rendering.

RINEX Header information no longer visible to anonymous access.

Updates to Correction Controls to resolve an issue where the receiver may not apply the settings and use the incorrect correction source.

Updates to the Daily Statistics email alert. Email now displays Current Statistics if the receiver has not ran for the full 24 hour period.

Firmware Upgrade Check feature now returns response to query showing either no upgrade available, upgrade available, or upgrade available but not in warranty.

New features or changes between 4.61 and 4.62:

General

Improved RTK correction manager to handle ephemeris records with no reference station IDs. Previously this could hinder initialization in specific configurations.

The NetR9 platform now supports Trimble RTX corrections through L-Band and TCP/IP delivery. P/N 97501-71 is required to enable this functionality.

Data formats

Resolves a rare issue where a serial port may drop incoming correction data.

Tracking

Enhanced ephemeris and almanac checks to ensure data validity

Power

Resolves a logic error that could cause the microcontroller to power off instead of entering sleep mode when the PoE was disabled and input voltage was below power-on voltage.

Improved power-on logic for low power/low current situations.

After multiple power-up failures, logic changed to persistently attempt to power unit on if the voltage is above power-on settings.

There is a new Shutdown Override feature on the Web UI under the Receiver Configuration / General menu. This feature will always keep the unit powered on if sufficent voltage is applied regardless of all other settings, commands, or front panel button inputs. Enabling this feature will override Data Logging/Power Saving, Application File Power-Up Timer settings, as well as the front panel power button.

Web Interface and Front Panel

New user-configurable option to supress all front panel warning messages from appearing. Previously, with the front panel display disabled, waring messages would appear. The default setting is "OFF".

New features or changes between 4.48 and 4.60:

General

Improved processor usage.

The Web Interface now shows the response from a met sensor or serial device in the I/O Configuration page. This allows users to determine the status of a serial connection without having to translate a data file (T02) or catch a binex stream. The following screen shot shows the response from a Vaisala WXT520 met sensor. Note: A bug has been reported in this new feature. The I/O Configuration page will continue to show the "Result" after the serial device has been disconnected. This could mislead a user in the status of a serial device.

Data formats

Updates to RT27 format handling of streaming ephemeris.

Data logging

Data logging memory pool size increased to 1TB to allow support of larger external USB drives. This was previously capped at 9999 MB.

Note: if you use a USB drive in excess of 10GB with large volumes of data and directories, more time is required for scanning. This may lead to undesired operations.

This release now supports up to 12 concurrent logging sessions.

Tracking

RAIM updated for improved Galileo and Compass support.

General updates for Compass tracking including satellite IDs.

OmniSTAR

Updated OmniSTAR library.

Application files

When installing a clone file, you can now apply the hostname record.

Networking

IP Filtering is now supported. The configuration for this feature is found on the Web UI–go to "Network Configuration / IP Filtering". This allows you to define up to five individual IP addresses, and assign a Netmask value to each of the IP addresses to allow a range within the specified IP address to connect to the receiver.

IP Filtering Notes:

IP Filtering will apply to all Ethernet and PPP connections.

Filtering is suppressed during the first 60 seconds of uptime to allow DHCP and other initialization to occur.

IP Filtering will not be enabled unless at least one valid IP address is defined.

The Web UI will warn you if an IP address is set that will prevent the computer used for the IP Filtering from communicating with the receiver.

IP Filtering is set to "Off" by default.

Improved NTP Server operational stability.

Web interface and front panel

Minor updates for browser rendering, caches, and displays.

Minor translations updates.

Resolves and issue where the front panel brightness settings are not saved when the receiver is rebooted.

Support for Trimble Internet Base Station Services (IBSS). The IBSS service simplifies the use and configuration of the Internet-baseed GNSS data.

The Firware webpage has been updated to show the Active Firware Warrant Date. To install the firmware, your receiver firmware warranty must be equal to or newer than this date.

New features or changes between 4.46 and 4.48:

Data formats

Logic updated in streaming and logged data formats validity (RT27/T02/BINEX). By default, all Infrastructure receivers are set with Ignore Health enabled. Under this condition, unhealthy observables are streamed and/or logged without having a valid ephemeris, provided that the measurement quality indicates a valid pseudorange is available. If Ignore Health is disabled, then the measurements must have a valid pseudorange, the satellite must be set Healthy, and the receiver must have a valid ephemeris.

Networking

New features or changes between 4.43 and 4.46:

General

Improved CPU management through reducing allocation to options not in use.

Data formats

BINEX record 0x7f-05 updated to include Doppler values for all satellites and signals.

BINEX record 0x7f-05 updated to include explicit ObsFlag bytes.

BINEX record 0x7f-05 updated to include Compass and GLONASS observation codes.

BINEX record 0x01-02 update to show GLONASS position/velocity values in kilometers instead of meters. Also updates for GLONASS slot IDs.

BINEX record 0x00-1f now shows antenna height to ARP.

BINEX record 0x01-01 updated GPS ephemeris week data.

BINEX streams include comment fields every 60 seconds to indicate the version BINEX implemented on the receiver. Logged BINEX will include on version comment per file. No comment fields indicate a firmware earlier than version 4.45. Version 4.45 and later include the BNX1 version number. Note – This version number is not an official BINEX version; it is a Trimble identifier included in the stream.

RT27 update to resolve missing position in RT27 record at week rollover.

TrimcommTM 0xb5 updates to handle serial port configuration changes.

Data logging

Full support for RINEX version 3.xx navigation files.

New support for on board conversions to RINEX version 2.12 and version 3.02 proposed formats. Please note these are only proposed formats at the time of the version 4.46 firmware release. As such, these are subject to change and are not fully supported by all software packages.

New power saving functionality for data logging sessions that enables the operator to define one or more logging sessions and have the receiver power down while not logging, to conserve power. It also enables the operator to set a predetermined wakeup period whereby the receiver will power on at a predetermined interval for a user-defined amount of time. This ensures the receiver will be accessible at a known time regardless of the data logging session schedule.

Power saving mode theory of operation: – The receiver must have the current time: Otherwise it will remain powered on until the time is set. – The receiver must have been powered on for at least 60 seconds prior to the power saving mode taking effect. – Power saving mode will power on the receiver 60 seconds prior to the scheduled data logging session to allow for power up, SV acquisition/tracking, and setting of time. – Power saving mode will not power off the receiver if there is less than two minutes left before the next scheduled power on time.

Power

Resolves an issue of power-on values being reset to default when power control routines are enhanced during a firmware upgrade.

Resolves a rare issue whereby the system may not save power routine settings if the receiver unexpectedly shuts down because the internal battery charger is disabled and completely drained.

Resolves several minor issues of specific web pages not rendering correctly in various browsers.

Addition of Compass controls in the Satellite Tracking Graph.

Resolves an issue of the Satellite Tracking Graph not appearing when tracking QZSS LEX signals.

Resolves an issue where the APC offset would be introduced to the antenna height field upon a receiver reset.

Updates to the antenna.ini file for the Web UI and front panel antenna selection menu. Adds support for the AG25 and resolves an issue where the Unknown External antenna option was not available.

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