Recently (from mid-August 2017 to September 6th when this article was written) various Microsoft periodic updates have also included replacing USB driver code.\u00a0 We have multiple reports of issues arising from this where after<\/em> the updates a previously working serial port (connected by way of an USB adapter) no longer runs or allows connections to SNIP<\/strong> <\/span>or to other devices.<\/p>\n Known effected drivers include at least:<\/p>\n We are unaware of any reports for devices using the CH340 chip set at this time.<\/p>\n We are unaware of any reports for devices using the uBlox 8M chip set at this time.<\/p>\n Fully reset the machine (power off and then on, and not just a reset).\u00a0 Once the machine has restarted and settled down, unplug all USB devices.\u00a0 Plug them back in.\u00a0 If your USB devices connect by way of a common HUB, you can simply disconnect them there.\u00a0 It appears that the act of restarting the USB drivers is required to complete the upgrade.\u00a0 Once this is done, all the machines which were reporting issues should again be fully functional.<\/p>\n <\/p>\n This helpful link<\/a> found on the rtklibexplorer<\/a> site which cater to folks using RTKLIB with uBlox chipsets. <\/p>\n <\/p>\n Recently (from August 2017 to September 6th when this article was written) various Microsoft updates also seem to have changed the default behavior on the stock machine firewall on both Windows 7 and 10 to no longer replying to PING commands from devices not local to your machine.\u00a0 The evidence of this is less clear.<\/p>\n You can seek for how to enable ping in Window 7<\/a> to find several useful articles.<\/p>\n PING (or Echo Request – ICMPv4-In<\/em>)\u00a0 <\/span>is a very good way to see quickly if the other machine itself is reachable.\u00a0 But if you are interested in seeing if a remote copy of the SNIP<\/strong><\/span> is up, simply enter its address and port on our monitoring tool<\/a>\u00a0\u00a0 If you see a table reply, the caster in question is operational.<\/p>\n <\/p>\n <\/p>\n When in doubt, cold start the suspect machine with no USB devices plugged in.\u00a0 Once up and stable, then plug in one device at a time, watching for the drivers to load.\u00a0 This may be enough to overcome the issue, but if not – at least it will tell you which device\/driver could not be created.<\/p>\n As a rule, do not allow a production machine running SNIP<\/strong> <\/span>to be automatically updated, or else when the re-start of the OS occurs, then SNIP<\/strong><\/span> (and perhaps other services you need) will be off line.<\/p>\n Connecting Ports \/ USB to your PC<\/a><\/p>\n\n
How to Overcome this<\/h3>\n
See Also:<\/h3>\n
\nThis is a great site full of useful an practical details on how to setup RTKLIB and get the most out of it.
\nThe gist of this article is that uBlox drivers have been at time caught in mother Microsoft issues as well.
\nAnd its moving to a new site which you can find at:\u00a0 http:\/\/rtkexplorer.com\/ <\/a><\/p>\n
\n
\n
\n
\n
\nPossible Firewall defaulting settings changes from Microsoft<\/h3>\n
\n
\n
\n
\n
\n\u00a0When in doubt<\/h3>\n
Related Knowledge Base Entries<\/h3>\n