Below are some of the more common issues encountered by CoPilot customers related to routing, as well as possible reasons for those issues. If you need additional help, please contact Technical Support by clicking the Submit Ticket button at the top of this screen. 

CONTENTS

• CoPilot provided incorrect routing
• Driver went to the wrong location or entrance
• Routes are not showing up in RouteReporter
• Route Modifiers (Avoids and Favors) don't seem to affect the route
• Driver went onto a restricted road, such as a road with a low bridge
• Route compliance (RouteReporter) shows fewer miles than the planned route
• The driver needs to take a different route because of an unexpected closure
• Custom Places are not appearing in CoPilot
• Routes are using roads that are farther away than necessary
• The driver was directed to an off ramp and then right back to an on ramp

CoPilot provided incorrect routing

Possible Causes

• FleetPortal, which ensures each instance of CoPilot has the correct settings, is not set up.
• FleetPortal's Configuration Profile was not set to prevent the driver from creating or editing a Vehicle Routing Profile or set to force the driver to select a profile each time before starting a route.
• Multiple Vehicle Routing Profiles were not set up in FleetPortal to account for various vehicle types. For example, you would want to have different profiles for a 53-foot trailer or twins versus a 48-foot semitrailer.
• The vehicle is not assigned to a Vehicle Group in FleetPortal.
• The device is using older maps or an older version of CoPilot. Check the app version and map version in the Vehicle Summary Report in FleetPortal.

Driver went to the wrong location or entrance

Possible Causes

• A bad address or bad GPS coordinates were entered in CoPilot. You can request a Trimble MAPS FastPass Analysis to check the quality of your location data. 
• The GPS coordinates entered were not at the truck entrance and CoPilot just routed to the address. You can create a Site in ContentTools with specific entrances and exits for trucks, as well as route paths to arrive at and depart from the Site. 
• The address entered in CoPilot does not fall within the Site created in ContentTools. You can expand the polygon around the perimeter of the Site in ContentTools to include that address, or make sure the address exactly matches the address for the custom Place associated with the Site. 

Routes are not showing up in RouteReporter

Possible Causes

• RouteReporter, the route compliance web tool, was not purchased or enabled at the time of your CoPilot purchase.
• The device is using an older version of CoPilot. Check the app version in the Vehicle Summary Report in FleetPortal.
• The driver is not hitting GO to start CoPilot navigation.
• Bad GPS data is being received from the CoPilot device (hardware unstable or failing).

Route Modifiers (Avoids and Favors) don't seem to affect the route

Possible Causes

• The device is using older maps with CoPilot. Check the map version in the Vehicle Summary Report in FleetPortal.
• The Route Modifier set is not assigned to the truck's Vehicle Group in FleetPortal. 
• You need to create more Avoids and more Favors to change the routing algorithm's behavior. For example, Avoids and Favors usually won't cause the algorithm to route a large truck on a primary (state) road rather than a freeway (interstate).

Driver went onto a restricted road, such as a road with a low bridge

Possible Causes

• If the driver followed the CoPilot route, then it might be related to older map data or an inappropriate Vehicle Routing Profile for the vehicle being driver. RouteReporter can be used to check which profile the driver was using and whether he or she followed the prescribed CoPilot route. You can check the map version in the Vehicle Summary Report in FleetPortal.
• If the driver ignored the route and turned off CoPilot, then the driver left themselves unprotected because CoPilot will alert them if navigation cannot safely continue.
• If Vehicle Routing Profile is valid and map data is new, then MapSure can be used to report the issue. Meanwhile, an Avoid can be created in ContentTools so other vehicles in the fleet do not take that road.

Route compliance (RouteReporter) shows fewer miles than the planned route

Possible Causes

• The driver turned off copilot for a portion of the trip or cancelled a trip or a stop in a trip.
• The driver took a different route from the planned route. The actual route taken can be viewed in RouteReporter.

The driver needs to take a different route because of an unexpected closure

Possible Solutions

• CoPilot can generate an alternate route on the device. 
• The driver can add a Waypoint to the route to avoid the closure.

Custom Places are not appearing in CoPilot

Possible Causes

• The device or vehicle is not assigned to a Vehicle Group in FleetPortal.
• The device is not communicating with FleetPortal. Check the app version in the Vehicle Summary Report in FleetPortal to see when the device was Last Connect to FleetPortal.

Routes are using roads that are farther away than necessary

Possible Cause

• Too many Favors in ContentTools are pulling routes over to those road. Adjust the Route Modifiers in ContentTools to remove some of those favors.

The driver was directed to an off ramp and then right back to an on ramp

Possible Cause

• The device is using older maps or an older version of CoPilot. Check the app version and map version in the Vehicle Summary Report in FleetPortal.