CoPilot includes a number of “Live” services that provide up-to-date information via the Internet.
These services may be paid subscriptions as part of the CoPilot license, such as ActiveTraffic, or free search functions.
CoPilot also uses Live services for an in-app user guide, news and updates. Unless disabled, CoPilot may also send anonymous positional location based messages to help enhance the map data at a later date.
This chart below includes the DNS addresses for CoPilot Web Service URLs that are recommended to be allowlisted to ensure information is received. It is recommended that the DNS is allowlisted as IP addresses are subject to change.
|Description of Service||URL||Port #||Direction|
|Billing, Content updates, GPS tracks, Map downloads||443||Request-Response|
|SSO Web Service||443||Request-Response|
|Authentication Web Service||443||Request-Response|
To restrict the connectivity present in CoPilot there are configuration values available limit these connections. As described on this page, there are a number of different use cases in which CoPilot may look to use an internet connection. This can range from licensing to map downloads or traffic information. Due to the range in services each of these can be restricted. Please note, if you have paid subscriptions such as ActiveTraffic using the restrict all connection will remove that functionality.
If you have any questions regarding the combination that you are looking to use please get in touch with your Trimble MAPS Account Manager.
[Messenger] "EnabledServices"=0 "SendPosition"=0
On CoPilot startup following a version update this config allows for the resume of support file download if they were not successful. This will not initiate the download any other time that on the first run following a version update and the download of support files are not complete.
This config will only allow downloads to take place when connected to a Wi-Fi network. Note that personal hotspots (MiFi) is considered as Wi-Fi. Best practice is to enable downloads only over Wi-Fi and set up an allowlist of Wi-Fi SSID’s to ensure only allowed networks are used. Set to =1 to enable.
A master connectivity configuration. If enabled and set to =1, CoPilot will never look to connect to a server, this includes traffic and if set, no traffic information will be retrieved if requested.
[Environment Settings] "BuildNoInternet"=0
A configuration that will prevent the download of languages, voices, themes and maps. In 10.9 when upgrading to a new version of CoPilot a request will be made to the server to download supporting files. If all of these files are not downloaded on first run CoPilot will ask via a popup to the user if the downloads should be resumed.
When upgrading CoPilot to a new version it will look to download support files. This config will not allow the download of any of the associated support files.
Follow the instructions below if you want to connect CoPilot to the internet via a proxy server.
CoPilot sets up the proxy using a config setting under the “HttpProxy” section in the product.cfg file. You need to specify the “Host” and “Port” of the proxy server. Some proxy servers require user authentication, and you also need to specify “UserName” and “Password.” Below is an example:
[HttpProxy] "Host"="192.168.1.9" "Port"=8080 "UserName"="e8fa39655ec712234f3843fb1303e34ec34ab8f5b388ac8db9e28dee8c2526cf" "Password"="e8fa39655ec712234f3843fb1303e34ec34ab8f5b388ac8db9e28dee8c2526cf"
The “Host” and “Port” can be added or modified directly in product.cfg or by using the CopilotMgr.setConfigurationSetting API. “UserName” and “Password” should be set using the CopilotMgr.setConfigurationSetting API.