Date Reported: July 8, 2011
Status: Confirmed (7.0.0)
Problem: Default screen layout is not appropriate for all display sizes and resolutions.
Solution: The new STAR*NET 7 interface is extremely customizable, and can be setup in any layout that suits your workflow. Users are encouraged to experiment with different screen layouts to find what works best for their individual needs. Panels can be moved, resized, collapsed, closed, docked or floated. Fonts, sizes and colors can be changed. Large or Small toolbar icons can be displayed. Toolbars and menus are customizable. You have practically endless customization abilities!
Date Reported: July 8, 2011
Status: Confirmed (7.0.0)
Problem: Find Point tool does not work in conjunction with point aliases defined via the new .ALIAS inline option.
Solution: Currently the Find Point tool will only match exact point names, and does not consider point aliases at this time. We hope to expand the Find Point tool to include this functionality in a future update.
Date Reported: July 8, 2011
Status: Confirmed (7.0.0)
Problem: Printing may not default to specified paper size. For example, after selecting 11x17 in the Page Setup dialog then pressing Print it may be output to 8.5x11.
Solution: There is a bug which can cause the page size being printed onto to not match the page size specfied in the Page Setup dialog, which we will fix in a future update. Fortunately there is an easy and effective workaround - after pressing the Print button, when you select your printer you can then press the Properties button and specify your desired paper size again, the printout will then be exactly as desired.
Date Reported: July 8, 2011
Status: Potential/Unconfirmed (7.0.0)
Problem: Find Point tool may not find all results when double-clicking a point name in the output files.
Solution: The Find Point tool is a new and complex addition to STAR*NET. Throughout beta testing we identified and fixed several specific issues which could cause the Find Point tool to fail, and it is possible that there may be other specific issues that cause problems which were not identified. If you have a problem please submit a technical support ticket and attach your project and data files so that we can identify and fix any problems as quickly as possible.
Date Reported: July 20, 2011
Status: Confirmed (7.0.0), Fixed (7.1.0)
Problem: Leica GPS vectors may not import into STAR*NET 7 via the GPS Vector Importer, and "Incomplete Vector Data" errors result.
Workaround: STAR*NET V6 can be used as an effective workaround to import Leica vectors. Once imported, the project and its data files can then be used in V7 for running any adjustements. This issue will be fixed in the next update.
Solution: This issue has been fixed in the STAR*NET 7.1 update.
Date Reported: July 29, 2011
Status: Confirmed (7.0.0), Fixed (7.1.0)
Problem: Elev Diff (elevation difference, or delta-Z) values reported in the listing file are incorrect. This affects "Unadjusted Elev Diff" values reported in the "Traverse Closures of Unadjusted Observations" section of a 3D adjustemnt job, and "Elev Diff" values reported in the "Summary of Unadjusted Input Observations" and "Adjusted Observations and Residuals" sections of a Lev adjustment.
Workaround: This issue affects only the computed elevation difference values; the reported elevation values are correct. If you require these deltas, they can be accurately computed based on the elevations reported in any of the output files. This issue will be fixed in the next update.
Solution: This issue has been fixed in the STAR*NET 7.1 update.
Date Reported: August 10, 2011
Status: Confirmed (7.0.0), Fixed (7.1.0)
Problem: DXF files exported from a Grid project have incorrect elevations, the geoid seperation is applied incorrectly. Elevation values in all other output files are correct. This does not affect Local projects.
Solution: This issue has been fixed in the STAR*NET 7.1 update.
Date Reported: October 3, 2011
Status: Confirmed (7.1.0)
Problem: A network adjustment cannot be run under Windows XP Professional 64-bit Edition. There is no known workaround to use STAR*NET 7 under this operating system, and therefore is not included in our list of supported operating systems.
Workaround: MicroSurvey STAR*NET 6 can be used reliably under this operating system.
Solution: To use STAR*NET 7, a supported operating system is required.
Date Reported: January 4, 2012
Status: Confirmed (7.1.0), Fixed (7.2.0)
Problem: Geoid Modeling (if enabled in Project Options | Modeling) is not performed on GPS Sideshots (vectors that follow a ".GPS SS" inline option). If a project contains any GPS Sideshots, the geoid separation is not applied when computing the GPS Sideshot elevations. (Note, this does not affect the default GPS Network observations, it only affects vectors following a ".GPS SS" inline.)
Workaround: Avoid using any ".GPS SS" inlines in a project in which Geoid Modeling is enabled. Alternatively, disable the "Perform Geoid Modeling" option in a project containing any ".GPS SS" inline options.
Solution: This issue has been fixed in the STAR*NET 7.2 update.
Date Reported: October 22, 2012
Status: Confirmed (7.2.0), Fixed (7.2.2)
Problem: The STAR*JobXML conversion utility (Beta) for Trimble JobXML (*.jxl) files writes distance values without any prism offset applied.
Workaround: You can avoid this issue in STAR*NET 7.2.0/7.2.1 by using a zero-offset prism. Distance measurements for non-zero offsets should be manually corrected in the resulting .dat file.
Solution: This issue has been fixed in the STAR*NET 7.2.2 update.
Date Reported: February 25, 2013
Status: Confirmed (7.2.2), Fixed (8.0.0)
Problem: The latest version of STAR*NET was modified such that it can now import vectors in cases where a connection is not established with the reference receiver (for example, when using a VRS network connection, etc) but this can cause a problem with other conventional base-rover vectors, resulting in the reference position being named using its Reference ID (like "RefID0000_1")instead of its Point ID (like "1"), and without setting its antenna height.
Workaround: You can avoid this issue by continuing to use STAR*NET 7.2.0 or 7.2.1. Or, you can easily correct this by aliasing the Reference ID to the corresponding Point ID (like ".ALIAS NAME 1 RefID0000_1") and adding the reference antenna heights by inserting ".GPS ADDHIHT YourBaseAntennaHeight 0.0" before the first vector.
Solution: This issue has been fixed in the upcoming STAR*NET V8 update.
Brian Sloman
Comments