null

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

 

 

 

  1. Unable to render {include} The included page could not be found.

  2. Bad Touch Screen

     

    Problem:

    The touchscreen is not responding to touch.

    Solution:

    NOTE: The unit might seem like it is locked up but the physical buttons underneath the display are working.

    1. Log out of the DriverTech unit by pressing the blue power button.
    2. Power the unit off by pressing the Power button once more -- leave turned off for about 2 minutes.
    3. Check connections on the back of the screen to make sure there is nothing loose.
    4. Then power the unit back on, by again pressing the Power button.
    5. If the issue persists: remove power from the unit via either the fuse or the battery kill switch.
    6. Keep the power disconnected for 5 minutes
    7. Bring the unit back up and test the touchscreen
    8. If the issue persists remove power via either the fuse or battery kill switch for 30 minutes
    9. Bring the unit back up and test the touchscreen
    10. If the touchscreen is still inoperable, clean it using this procedure.
      1. Power down the unit
      2. With a damp cloth, with finger pressure, wipe from the top-left over to the top-right
      3. Continue the process row-by-row until the bottom-right is reached.
      4. Clean out the edges next to the bezel
      5. Power the unit back up
    11. If the screen is still not responding to touch, it will need to be brought into a shop.
    12. A USB keyboard and/or mouse may be used as a temporary workaround to this issue while the unit is awaiting shop repair.

    Related articles

    Back to The Top

    Home

  3. BSOD (Blue Screen of Death)

     

    Problem:

    Screen has a blue background with white text.

    Solution:

    1. Press and hold the Power button - leave turned off for about 2 minutes. If the unit does not respond, move on to the next step below.
    2. Disconnect power to the TruckPC for about 2 minutes.
    3. As a last resort- if the problem persists, disconnect power to the TruckPC for about 30 minutes.
      1. Unplug power from TruckPC or flip the battery kill switch.

    4. Please inform your in office personnel, your shop or, call technical support.

     

    Related articles

     Back to The Top

    Home

  4. Unable to render {include} The included page could not be found.

  5. Co-Pilot Error Messages

     

    Problem:

    There are error messages when you open the Co-Pilot application.

    Solution:

    1. Have the driver Log out of the device.
    2. Then press the power button      
                        .
    3. Once the unit has gone to a black screen, wait 30 seconds then power it back on.
    4. Log on when asked to submit your Driver ID.
    5. If the problem continues to occur Inform ALK/Copilot of the issue.
    6. This link (http://copilotpro.com/us/contact/) and filling out their form.
    7. You can also reach them over the phone at: 609.683.0220 or 877.573.0138

    Related articles

    Back to The Top

    Home

     

     

  6. CoPilot is Showing UTC time

     

    Problem:

    Co-Pilot's time zone is set to UTC.

    Solution:

    1. This is a setting in CoPilot, and will need to be configured within the application.
    2. If you need help configuring the CoPilot application, please contact ALK by going to:
    3. This link (http://copilotpro.com/us/contact/) and filling out their form.
    4. You can also reach them over the phone at: 609.683.0220 or 877.573.0138

    Related articles

    Back to The Top

    Home

  7. Copilot Not Getting GPS While GPS Locations are Working

     

    Problem:

    The unit's GPS appears to be functioning but Co-Pilot is not showing the correct location.

    Solution:

    1. Please call ALK to report Issue.
    2. This link (http://copilotpro.com/us/contact/) and filling out their form.
    3. You can also reach them over the phone at: 609.683.0220 or 877.573.0138

    Related articles

     Back to The Top

    Home

  8. Unable to render {include} The included page could not be found.

  9. Could Not Reimage


    Problem:

    Could Not Reimage

    Solution:

    1. IMPORTANT NOTE: Never unplug the Reimager while the unit is on. Turn off the unit before unplugging the Reimaging device.

    2. If you have a 3 piece system(Antenna, Display, CPU) installed, do not plug into the Display to try to reimage

      1. DO NOT USE the DISPLAY'S USB PORTS, plug directly into the CPU.

    3. You are most likely experiencing USB port connection issues.

    4. Check the USB connections

    5. Try a USB cable that you know works
    6. Try another USB port

    Related articles

     Back to The Top

    Home

  10. Device Auto Logging Driver Off


    Problem:

    The driver is being logged off of the unit automatically.

    Solution:

    1. Log into FleetWatcher.
    2. Go to Reports > Events and Positions.
    3. Click on the Driver Code button and enter the Driver Code
    4. Click on the Calendar icon located near the middle of the page and select appropriate date range
    5. Click Gets Results
    6. Check to see if there is more than one truck number in the Vehicle Column
    7. If the 2 Vehicles are located in 2 completely different locations and the driver could not have possibly been in both places within a reasonable amount of time, you now have reason to believe 2 drivers are using the same Driver Code.
    8. Change the Driver Code or research why both drivers are using this one Driver Code.

    Related articles

     Back to The Top

    Home

  11. Froze While Booting Up

     

    Problem:

    The unit is locking up while it is trying to start up

    Solution:

    1. Do not unplug the screen, remove, or unplug power without a DriverTech support technician on the phone as this may cause further damage.
    2. Press and hold the On/Off button for 30 seconds or until the unit turns off.
    3. If you are a shop technician, re-imaging should resolve the issue.
    4. If unit does not turn off using the On/Off button, please call DriverTech Technical Support.

    Related articles

     Back to The Top

    Home

     

     

     

  12. Improper Boot Device

     

    Problem:

    A black screen with gray lettering, part of which states "No bootable device" or "Insert proper boot media"

    Solution:

    1. Turn the truck's ignition off.
    2. Disconnect power to the TruckPC for 2 minutes.
    3. Reconnect power to the TruckPC.
    4. Press the power button to turn the unit back on.
    5. As a last resort- if the problem persists, disconnect power to the TruckPC for about 30 minutes.
      1. Unplug power from TruckPC or flip the battery kill switch.
    6. Reconnect power to the TruckPC.
    7. Press the power button to turn the unit back on.
    8. If the problem persists, the TruckPC needs to be replaced.

    Related articles

      

     Back to The Top

    Home

  13. Intelliroute Icon Not Working

     

    Problem:

    Unit does not open the Intelliroute Application when pressing on the Intelliroute Icon

    Solution:

    1. This would indicate that Intelliroute has stopped working and would need to be reinstalled
    2. Intelliroute is installed from a USB stick

    3. If the issue has not been resolved, please call technical support.

       

    Related articles

     Back to The Top

    Home

  14. JBUS Locked Up

     

    Problem:

    The JBUS is no longer being recognized or is not recording ECM Data(aka. Engine Data).

    Solution:

    1. Turn the truck ignition off.
    2. Log out of the DriverTech unit.
    3. Press and hold the power button.    
                          .
    4. Once the unit has gone to a black screen, wait 30 seconds then power it back on.
    5. Log in with your Driver Code.
    6. Touch the System Info button then the Diagnostics tab then the JBUS tab.
    7. Turn on the truck Engine and wait 2 minutes.
    8. You may see this message, -JBUS Data present, missing parameters -. This is an acceptable message.
    9. You should see the RPM field changing, if you do, the unit is most likely working properly.
    10. To confirm, run a JBUS audit.
    11. If everything on the screen is properly reporting, the issue is resolved.

    Related articles

     Back to The Top

    Home

     

     

  15. Logs Have Been Removed

     

    Problem:

    The driver's logs can no longer be found

    Solution:

    1. Find out whether or not the truck was at a shop recently and was re-imaged.
      1. Re-imaging the unit will wipe out all current data stored on the unit, and if this data hasn't been uploaded to FleetWatcher, there is a chance this data will not be recoverable.
      2. Make sure Logs are uploaded to FleetWatcher before re-imaging the TruckPC.
    2. Check to see if the driver switched trucks around the time logs were lost.
      1. If the driver switched trucks improperly, various issues can occur-
        1. Driver is still logged into old truck and therefore logs were not sent up to the backend, and upon logging into to the new truck no data is found and it pulls down blank or missing info.
        2. When the driver logged out of the old truck the unit was not communicating and therefore any data not sent to the back end can't send up, and upon logging into to the new truck no data is found and it pulls down blank or missing info.
        3. The driver didn't go to "HOS Logs" à "Options" à "Change Trucks" before logging out. As this helps to secure data be properly stored to the backend.
    3. If none of the above issues are the cause, please call in to technical support.

    Related articles

     Back to The Top

    Home

     

 

Add FAQ from Template

  1. A-B
  2. C
  3. D
  4. E
  5. F
  6. G-H
  7. I-J
  8. K-L
  9. M
  10. N-O
  11. P-Q
  12. R
  13. S
  14. T
  15. U-V
  16. W-Z
  17. 0-9

 

Back to The Top

  • No labels