Monthly Archives: December 2019

Urgent: SurvCE: Version 6: Bad GEOID 18

This is an IMPORTANT ANNOUNCEMENT concerning GEOID18 and SurvCE. 
The NGS published a bad GEOID18 implementation on their website earlier this year. The error was discovered / announced yeseterday Monday 9 December 2019.
Many / most vendors utilized the errant GEOID files posted on the NGS site to build their GEOID files, including Carlson Software.
I have verified that the GEOID 18 file distributed with SurvCE Version 6 contains the errant grid points (about 1 in 500 points is incorrect, with a 6 cm maximum error.)
This PDF shows how to check if you are using the errant GEOID in SurvCE:
I believe that your best course of action is to revert to GEOID12B at this point.
Carlson will release an updated GEOID soon, however it may be difficult to jump on this wagon again.

 

Leave a comment

Filed under Uncategorized

WMDC + Windows Defender Firewall: RNDIS

If you have watched my video (https://youtu.be/VHI4dwVbGbI ) and read the accompanying document ( http://igage.com/v/bin/WMDC_Win10_CreatorsEdition_Fix_RevB.pdf ) then you should have some idea that WMDC is disabled by default in Windows 10 and you have to ‘do some stuff’ to make it work again.

When you uncheck the box, instead of using RNDIS the connection is made by a virtual serial port service.

RNDIS is an embedded USB RNDIS host class driver provides a virtual Ethernet link over USB. Remote Network Driver Interface Standard (RNDIS) is a Microsoft proprietary protocol.

Unchecking the box is easy and results in a working system most of the time.

However, checking the box makes data transfers MUCH more reliable and over 3 times faster in most instances.

The problem with checking the box is most firewalls actively block WMDC over RNDIS.

The linked document shows how to edit the Windows Defender Firewall to allow WMDC to work….  [ continue reading: WMDC_RNDIS_007 ]

Leave a comment

Filed under Uncategorized

UHF Radio Range Problems

Your Base / Rover RTK pair used to have great radio range … but something has changed and now you can only go a short distance from the base before the rover loses lock.

This is a common complaint and there are several standard issues that contribute to this issue:

  • Multiple Users on Same Frequency
  • Receiver (Rover) Sensitivity Setting
  • Base Output Power
  • CSMA Throttling
  • Bad Antennas
  • Bad Antenna Connectors
  • Internal COAX Failures

For some extra background and solutions, checkout this FAQ [ iGx_RadioRangeProblems_003 ]

Leave a comment

Filed under Uncategorized