URGENT NOTICE for users of Spectra SP80, PM500, PM800, PF500, PF800, PM120, MM120

Spectra Geospatial has released a notification that these receivers:

SP80, PM500, PM800, PF500, PF800, PM120, MM120

are unable to report positions because of an errant GLONASS ephemeris issue.

A firmware fix for the SP80 is available now. You can download it with this link: [ Version 3.45 ]

A fix for the remaining legacy devices is planned and should be available soon.

If you have an affected receiver you probably noticed problems beginning last Friday. There is a chance that the SP60 and SP20 are also affected as they share a common engine with the SP80, however the factory has not confirmed this.

Please note that this is not an official notice from the factory, this is a courtesy ‘heads up’.


Filed under Uncategorized

GNSS Issues October 1 2019

Several reports of anomalies yesterday (Monday 30 Sept 2019)  and today (Tuesday 1 October 2019).

  1. SP80: these receivers track, then loose tracking, then reset engines if running firmware prior to 3.39. So firmware update is mandatory.
  2. Some Trimble Engines: we have observed BD970 engines with older (~5.25) not floating or fixing. An engine reset with new ephemeris download appears to fix.
  3. ProMark 500’s are seeing a ‘215’ error after booting. There is a chance that turning off GLONASS tracking (in SurvCE see ‘Equip: GPS Rover: Receiver (tab): Advanced’) will fix this issue.
  4. ORGN and INCORS (and probably all Spider based servers) are reporting GLONASS related issues.

I can’t find any buzz online, but enough complaints to know there is an issue.

Leave a comment

Filed under Uncategorized

Galileo GNSS System: Complete Failure on 11 July 2019

It appears that the Galileo GNSS system has failed (the entire constellation). The official [ status page : https://www.gsc-europa.eu/system-status/Constellation-Information ] lists all SV’s as degraded.

The start of the (hopefully temporary failure) is listed as 01:00 11 July 2019 UTC.

The NAGU [ https://www.gsc-europa.eu/notice-advisory-to-galileo-users-nagu-2019025 ] has details.

All my test receivers are tracking but not using GAL, I have confirmed similar status in Europe.

This will be a good chance to appreciate the system going forward. Hopefully it gets fixed soon.


Leave a comment

Filed under Uncategorized

End of Customer Support Update

Ref:  [ https://blog.ashgps.com/2019/04/18/the-end-of-non-customer-support/ ]

‘The End of Non-Customer” blog entry that generated the most feedback of any blog entry on this blog. Actually more feedback than all other entries combined.

Most of the new comments are non-customers asking for help with ProMark / MobileMapper 100 / 120 receivers in doing the update! ( Here are my [ step-by-step instructions ]. ) I am deleting these requests because I think they are demeaning to the requesting person. So, in response to a blog entry that says no more endless support for equipment that we did not sell for customers that we will not possibly sell to in the future; the response is demands for more free assistance.

O.M.G. Obviously there is a problem here.

But I want to make one thing clear: if you purchased equipment from iGage we will support you in anyway we can. Don’t hesitate to call us! If you purchase equipment from us, we provide great support.

Again: if you purchased your equipment elsewhere, call YOUR dealer. We are NOT YOUR DEALER. We don’t WANT to be your dealer. You already made this choice, we did not participate in the decision.


1 Comment

Filed under Uncategorized

Fixing Verizon Jetpack and iPhone Issues with Data Collectors

Which data collector you ask? A: all the data collectors that we sell.

Verizon JetPack Issue

Windows Mobile based data collectors have a hard time connecting or staying connected to Verizon Jetpacks (Mi-Fi Hotspots).

More data: customer says “it used to work just fine, but … now it won’t connect or looses connection frequently.”

Apparent answer: Verizon pushed a Firmware update that added or changed the default security or made a change the the protocol implementation.

The Solution: log into the Jetpack as an administrator from a computer. (You can connect by Wi-Fi to the Jetpack, then browse to the address typically. The administrator password is on one of the display screens.)

Browse to the Wi-Fi settings screen, then select the ‘Primary Network’ tab:


Find the ‘Security:’ drop down. It will be set to WPA2. Change it to WPA/WPA2. (Note: None works great, but …). Click on Save Changes.

Item #2: Make sure the SSID is simple. I don’t know what the rules are, but I think it is safe that an SSID like “Mark’s JetPack-01” is not OK. Keep the SSID really simple like “MARKJP” using all upper case letters and numbers with no punctuation marks. (This is especially true on iPhones where the default SSID would be “Mark’s iPhone” but the ‘ (apostrophe) is a multi-byte character that Windows Mobile does not support.

Finally: On the data collector, remove settings for the Jetpack, then reconnect.

Problem solved typically.

But, I don’t know if this makes your Jetpack feel insecure or not. We should worry about that.

iPhone SSID

One some iPhones the default SSDI is the iPhone owner’s name. Like:

‘Mark’s iPhone’

However the “‘” between the k and s is a multi-byte character. Some devices (like the Data Collectors) reduce the apostrophe to a simpler single byte ASCII character. This prevents the collector from reconnecting to the phone.

The solution is to change the SSID of the iPhone to something simple. I reccomend:


No spaces, not mixed case, no spaces, no funny characters.

You can get to this from ‘Settings: General: About …’


Leave a comment

Filed under Uncategorized

Two Feet Forward

Did you watch Dr. Michael Dennis’s ‘Fate of the US-Survey Foot’ webinar? If not, you should. Here is the link:


As always, Dr. Dennis knocks it out of the park. A Geodetic Rock Star. This webinar should be shown at the beginning of every survey course series and every GIS course taught in the USA.


Leave a comment

Filed under Uncategorized

The End of Non-Customer Support

Effective Thursday 18 April 2019 I (Mark Silver) will no longer entertain helping non-customers with issues on equipment that iGage Mapping Corporation did not sell. In addition, iGage will no longer sell accessories, batteries, cables, equipment outside of the United States.

The Back-Story

Since March I have fielded as many as 50 email / phone questions per day from non-customers asking about WNRO (Week Number Roll Over) issues. Since the beginning of April I have gotten over 20 questions per day requesting help with installing updated firmware on receivers, post-processing 1999 dated files. Yesterday I was up until 11:30 pm responding to these queries. Of the 20+ questions yesterday only one was from an iGage customer who purchased the equipment in question from iGage.

Some of the questions come from customers who purchased equipment elsewhere, but have purchased a battery or cable from iGage in the past. Purchasing a cable for a ProMark 500 does not entitle you to support for that ProMark 500 receiver. And if the cable worked when you received it 5 years ago, our warranty has expired and we bear no responsibility for supporting you if it appears to not work today.

All of these non-customer questions share a common thread: the equipment/software was purchased from another dealer who is out of business or no longer will provide support for the equipment that they previously sold.

iGage Customers

If you purchased equipment from iGage, I am happy to support that equipment as best I can (keep in mind that most of the questions at hand are about 7+ year  old equipment.) However, I will ONLY support equipment that iGage sold directly or through one of our sub-dealers. So if you purchased multiple receivers from multiple sources, I am not going to help you with the equipment not purchased here.

What if you are willing to pay for support?

Well, that is great, but I will not support equipment that iGage did not sell. I don’t care if you are willing to pay for support.

An alternative is to return the equipment to the original company and purchase replacement equipment from iGage.


Too harsh of  response? Perhaps, but by continuing to spend 8+ hours per day supporting non-customers I am putting the company that I work for at risk of failure. We survive by selling equipment and providing the best support and service that we can. Please consider purchasing equipment from us if you expect us to provide you support and service.


Filed under Uncategorized

Magellen Professional, Ashtech, Spectra Precision, Spectra Geospatial GNSS Receivers and GPS Week Number Rollover – April 2019

This is an URGENT NOTICE for users of the following GNSS receivers:

ProFlex 500, ProFlex 800
MobileMapper 100, 120
ProMark 100, 120, 200, 220, 700, 800
SP 20, 60, 80, 90m

The notice also includes information for users of:

ProMark 700
MobileMapper 300
EPOCH 10, 25, 35, 50

If you are using any of these receivers, you MUST update firmware prior to April 6th 2019 or your receivers will stop working at (about) midnight UTC the morning of April 7th 2019.

Specific Instructions, with links to updated firmware can be found in this Official Spectra Geospatial ‘Support Note’:


(The following note is from Mark Silver and does not reflect an official position from the factory.)

No official information is available from the factory regarding ProMark 3, ProMark 2 or earlier receivers. Since the ProMark 100 receiver is a descendant of the ProMark 3 and all subsequent devices (ProMark 120, ProMark 500, ProMark 800 and SP80/60) have mandatory firmware updates it is my guess that the PM2/PM3 receivers will fail on rollover. In addition, I believe that the desktop tool ‘GNSS Solutions’ will probably also fail.

Will the failure be catastrophic? Perhaps not. In the case of static files from ProMark 3 receivers it may be possible to ‘fix’ them using a software shim tool to modify RINEX dates.

To put the ProMark 3 in perspective, I do not believe that we have any working PM3’s at iGage to play with at this point (and the search for them may prompt a needed shelf cleaning and subsequent dumpster fill.) I will disclose that I have received more calls from ProMark 3 users worried about WNRO than any other device. So I do realize that there are many PM3’s in daily use.

I would caution everyone that while some receivers have been tested using GPS/GNSS simulators, the process of constructing simulation files is VERY complicated. Normally the simulators use signals that are recorded and then replayed. So there might be additional complications discovered after April 7th.

In any case, I plan to spend Sunday April 7th pulling old receivers and testing them at the office. Hopefully it will be an uneventful, sunny, spring day.

Good tracking to all,

Mark Silver


Filed under Uncategorized

Carlson Formated Argentina IGN GEOID Modelo AR16

He convertido el archivo para usted.

Descargar desde esta ubicación web: http://alltopo.com/out/ms/GEOIDE-Ar16/

Ambos formatos de Carlson están disponibles, creo que el formato .GSB es superior.

Aquí hay una visualización:


Leave a comment

Filed under Uncategorized

Another SurvCE Grid to Ground & Localization Resource

Here is a great resource for Grid-to-Ground and Localization in Carlson SurvCE (specifically Version 5.08)

[ SurvCE_LocalizationG2G_Rev014 ]

Index to the PDF:

Localization & Grid to Ground Scale Factors in SurvCE. 1

Grid-to-Ground. 1

Localizations. 1

Reusing last localization? Clean slate!. 1

001 Start a new job at 10,000, 10,000; use Geodetic North at Ground based at a chosen parcel corner. 2

002 Stat a new job, following a historic plat, matching the original basis-of-bearing but holding exact ground measurements. 5

003 Start a new job, using a custom Low Distortion Projection, based at a central location at the job. Choose the correct projection scale factor so that distances are ground. 6

004 Using the previous job, with LDP geodetic basis of bearings and ground distances (10,000, 10,000.) Hand enter a couple of NGS Control Points using the published geodetic positions. 10

005 Start a new job, retracing an existing survey. Initially use a few points to ‘get on the system’ then after finding the remaining corners, do a multipoint calibration looking for blunders. 11

006 Mix total station shots with GPS measurements at Grid. 14

007 Choose an appropriate Combined Scale Factor based on Job corners. Set a Geodetic (True North) BOB system at the job center. (Tricky because you need raw data at Job Center.). 16

008 Network Leveraging of Localization. 19

01:: I just collected 1,200 GPS field shots in the wrong state plane zone!. 27

02:: I just collected a ton of GPS data in international feet, it should have been US Survey Feet!. 28

03:: I collected a day’s worth of data using an autonomous base position, I would like to convert it to a true base position. 29

Adjusting Data Stored with an Autonomous Base to an OPUS Position. 29

03B:: How to read a GNSS Raw File. 35

GNSS Base. 35

.REF File Description. 36

.RW5 Base File Description. 37

04:: I did not store the base position as a point when I did a ‘Read GPS’, can I extract the base position from the raw file (.RW5) or the ref file (.ref)?. 38

05:: I localized on two points at this job and stored a ton of existing features. Now I realize that one of my control points was actually an offset. How do I save my work?. 38

06:: I just stored a shot with a 40000 foot HI!  39

Leave a comment

Filed under Uncategorized