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. Unless otherwise noted, the URLs apply to both the DNS request and response.
|Description of Service||URL||Port #|
|Avoids and Favors||443|
|Authentication Web Service||443|
|Mobile Instruction File Downloads||443|
|Traffic (outside of NA), POI search, and Weather||443|
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. If you would like to restrict CoPilot’s internet connectivity, there are configuration values available to do so, as described below. 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 than 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. Note: This setting does not apply to Windows laptop versions of CoPilot, which cannot detect if a device is connected to the internet via Wi-Fi or a cellular network.
A master connectivity configuration. If enabled and set to =1, CoPilot will never look to connect to a server, and this includes traffic. 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.
In CoPilot 10.26.1.187 and later, configuration settings are available that allow you to specify which Wi-Fi networks CoPilot can use for tasks such as downloading map updates. These include
In order for these settings to work properly, CoPilot must have permission from the Android device to access GPS location data. Location data is required to get a hotspot’s Wi-Fi SSID—the first step in identifying a hotspot and determining whether CoPilot is allowed to access it. You can determine whether CoPilot is permitted to access location data by making sure the location icon (pin) is displayed at the top of the CoPilot screen.
WiFi filtering was introduced in CoPilot 10.26.1.187. Depending on your version of CoPilot, some additional steps are necessary to ensure CoPilot is accessing location data, and can identify an SSID for map downloads.
For CoPilot 10.26.1.192 and earlier
CoPilot must be in the device’s foreground, or running an active trip, in order to have access to GPS location data and download maps.
For CoPilot 10.26.1.300 and later
WifiFilterType are set, CoPilot must be brought to the foreground at least once in order to keep the GPS feed in the background when using the Wi-Fi filter feature. After that, the feature should work properly whether CoPilot is in the foreground or background.
Android 11 and later
If you find that Wi-Fi filtering is still not working with CoPilot in the background, it may be related to Android’s battery optimization feature. It limits which apps can use the device’s battery in the background.
In Android 11, make sure App can use battery in the background is turned on for CoPilot:
In Android 12 and later, make sure CoPilot has Unrestricted access to battery usage in the background:
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.