{"id":8703,"date":"2023-03-02T22:08:17","date_gmt":"2023-03-02T22:08:17","guid":{"rendered":"https:\/\/www.use-snip.com\/kb\/?post_type=ht_kb&p=8703"},"modified":"2023-06-05T23:46:31","modified_gmt":"2023-06-05T23:46:31","slug":"release-3_09_00-changes","status":"publish","type":"ht_kb","link":"https:\/\/www.use-snip.com\/kb\/knowledge-base\/release-3_09_00-changes\/","title":{"rendered":"Release 3_09_00 Changes"},"content":{"rendered":"

What is new in the SNIP<\/span> 3_09_00 release<\/strong> – released March 02 2023
\n(updating the prior release of 3_08 issued on December 28th, 2022)<\/p>\n

This is the next production release of SNIP<\/strong><\/span> following the Rev 3_08 release.\u00a0 This release contains various major and <\/em>minor<\/em> improvements in response to user requests.<\/p>\n

This release supports both 32-bit and 64-bit installations on all Windows Platforms from Windows 7 to the current editions.\u00a0 It is STRONGLY<\/strong><\/span> recommended that all Windows 32\/64 SNIP<\/strong><\/span> installations now update to using this release.<\/p>\n

Changes in this release include<\/strong><\/h2>\n

Map Displays<\/strong><\/h3>\n

A recent change in the Google Map API (with the release of Revision 3.52) caused all SNIP<\/strong><\/span> Casters \u00a0to lose some basic map image abilities.\u00a0 The Maps for the WebAPI<\/a> and some other reports using maps were not affected.\u00a0 This release overcomes that by forcing the use of an older version of the API.\u00a0 In addition, a number of other stock Java scripts have been updated to use current releases. Further details on this problem (and how to fix it by hand if you do not care to upgrade your copy of SNIP<\/strong><\/span> at this time) can be found at: https:\/\/www.use-snip.com\/kb\/knowledge-base\/google-map-changes-updating\/<\/a><\/p>\n

A feature request to be able to control the radius used for the two transparent coverage circles drawn for \u201cL1-Only\u201d and \u201cL1+L2\u201d RTK coverage has now been implemented. \u00a0Under the document viewer menu Window<\/strong> is a new item called Settings<\/strong>. \u00a0When selected, a simple dialog box allows the operator to set the value for each in kilometers.\u00a0 Toggle the check boxes for L1 and\/or L2 found in the Map Legend to see the new values.\u00a0 It should be stressed these limits are just for general information and the results seen by any individual rover will vary based on other environmental factors. As the saying goes, your mileage may vary.<\/p>\n

\"\"<\/p>\n

Push-In Streams<\/strong><\/h3>\n

A new feature allows adding an \u201calias\u201d name to the Push-In reservations<\/a> for a Base Station.\u00a0 This supports the unusual use case where the mountPt name of the Pushed-In Base cannot be controlled by the NTRIP Caster<\/a> operator and another name is desired.\u00a0 A few reports now list both names when this feature is used.<\/p>\n

All Non-reserved Push-In connections are now always given a unique indexing value.\u00a0 This overcomes a problem experienced in the last release (mostly by Lite model users) where only the first Non-reserved Push-In connections could be selected.<\/p>\n

Push-Out Streams<\/strong><\/h3>\n

The directional arrows used to indicate various stream types<\/a> in other lists has been added to the list used in the Push-Out setup<\/a> dialog.<\/p>\n

Serial Streams<\/strong><\/h3>\n

The baud rate 4800 has been added to the supported rates in the serial setup dialog<\/a>.<\/p>\n

P.F.A.T.<\/strong><\/h3>\n

Corrected an indexing error in the PFAT Filter dialog<\/a> where checking on an individual message type would result in another message type being incorrectly selected.\u00a0 The problem manifested itself when there were some messages in the Base Station data stream that were sent at very slow rates – when they arrived the prior list order was disturbed.<\/p>\n

Misc. Improvements<\/strong><\/h3>\n