From bart.ciastkowski at septentrio.com Wed Oct 2 17:43:45 2019 From: bart.ciastkowski at septentrio.com (Bart Ciastkowski) Date: Thu, 3 Oct 2019 00:43:45 +0000 Subject: [IGSSTATION-7756] Re: Firmware Availability Notice for PolaRx5 Family of GNSS Receivers, version 5.3.0 In-Reply-To: References: Message-ID: Hi, I have another update for you in regards to 5.3.0 and upcoming FW releases. This has also been communicated to Unavco?s Project Management. We have encountered a problem with the sftp protocol in FW version 5.3.0. Please read the below to assess impact. Let me know if you had any questions. Firstly this is our FW release schedule in the upcoming weeks: 1. Provide (if requested), within 2 weeks, FW version 5.3x beta release containing issues found in 5.3.0 (see additional information below) 2. Gather feedback and increase in-house test coverage to finalize FW version 5.3.1 release 3. Produce FW version 5.3.1 generally available release containing 5.3x beta release fixes only 4. Produce FW version 5.3.2 generally available release sometime in November containing additional features planned originally for 5.3.1 Additional information about issues found in FW version 5.3.0 that will be addressed in 5.3x beta release: * Sftp issue * sftp session cannot be established and the following errors are reported: usr/libexec/sftp-server: error while loading shared libraries: libatomic.so.1: cannot open shared object file: No such file or directory * Rinex conversion issue * with the -X option of sbf2rin, it is possible to include the channel number in RINEX. When the -X option is enabled and the first observation type is missing (e.g. the receiver tracks L2C but not L1CA), all observations are discarded in the RINEX file. This has remained undetected so far as the -X option is rarely used and the first observation type is typically available -- this issue was not present in 5.2.0. * Met sensors issue * when using the web interface to communicate with an external sensor, sending %%CR to a sensor the character is not properly replaced by a carriage return; as a temporary workaround, %%%SSN_CR can be sent instead of %%CR. This does not concern most customers -- this issue was not present in 5.2.0. Additional information about 5.2.0 that I have communicated previously: * 5.2.0 has an issue preventing the automatic deletion of logged data at the scheduled interval. * Nonetheless, by default the receiver automatically deletes old files from the disk that is becoming full. The files are deleted by Priority set via setLogSession command and then by age ? by default all files are medium priority so priority typically does not play a role. The receiver only stops logging, which again is not the default behavior, when StopLogging action is issued via the DiskFullAction command. Upgrading Firmware notes * One cannot jump directly from let say 5.1.2 --> 5.3.0, and using this example must upgrade firstly to 5.2.0 Please let me know if you have any questions or require further assistance. Best Regards, Bart Ciastkowski Applications Engineering and Technical Support Manager? t. +1-424-398-2000 e. bart.ciastkowski at septentrio.com 23848 Hawthorne Blvd #200 Torrance, CA 90505, USA From: Bart Ciastkowski Sent: Friday, September 27, 2019 12:01 PM To: igsmail at igs.org; igsstation at lists.igs.org; Frederick Blume Cc: Jim Normandeau ; Septentrio Support ; Francesca Clemente Subject: Firmware Availability Notice for PolaRx5 Family of GNSS Receivers, version 5.3.0 To All, We would like to bring to your attention that firmware version 5.3.0 for PolaRx5 Family of GNSS Receivers is generally available for download on our website at https://www.septentrio.com/en/support/polarx. There you will find firmware upgrade files along with release notes. On top of bringing new functionalities, this release fixes an issue ? present in version 5.2.0 - preventing the automatic deletion of logged data at the scheduled interval. Please note that by default the receiver automatically deletes old files from the disk that is becoming full. The files are deleted by Priority set via setLogSession command and then by age ? by default all files are medium priority so priority typically does not play a role. The receiver only stops logging, which again is not the default behavior, when StopLogging action is issued via the DiskFullAction command. You are all encouraged to upgrade to 5.3.0. Please contact support at septentrio.com for any questions or concerns you might have. Best Regards, Bart Ciastkowski Applications Engineering and Technical Support Manager? t. +1-424-398-2000 e. bart.ciastkowski at septentrio.com 23848 Hawthorne Blvd #200 Torrance, CA 90505, USA -------------- next part -------------- An HTML attachment was scrubbed... URL: