- Created by Support, last modified on Aug 03, 2016
You are viewing an old version of this page. View the current version.
Compare with Current View Page History
« Previous Version 26 Next »
- 70 hr Violation Goes Away After Midnight — Reason 70 hour violation went away after midnight
- Bad Touch Screen — How to troubleshoot a bad touchscreen issue
- BSOD (Blue Screen of Death) — Quick fix for a BSOD issue at the TruckPC
- Can't retrieve Modem Identification — Describes what to do when unable to communicate due to "Can't retrieve modem Identification"
- FleetWatcher, Cannot See Driver — How to add a driver to FW
- Co-Pilot Error Messages — Fixing co-pilot error messages
- CoPilot is Showing UTC time — This page is to help when your Co-Pilot is showing in UTC time rather than Local time
- Copilot Not Getting GPS While GPS Locations are Working — CoPilot not getting GPS when unit is receiving GPS signal
- FleetWatcher, Unable to find a Truck — How to locate/find a truck in FW
- Could Not Reimage — Troubleshooting a Reimager
- Device Auto Logging Driver Off — Shows how to research 2 drivers possibly using the same Driver Code
- Froze While Booting Up — What to do when the TPC unit freezes while booting up
- Green Power light is on - Display is Blank — Troubleshooting steps for when the green LED light is ON, but the display does not appear to be on
- Improper Boot Device — What to do when receiving the Improper Boot Device error
- Intelliroute Icon Not Working — Steps to fix Intelliroute when it will not open.
- JBUS Locked Up — What to do when the Unit is not recording Engine Data
- Logs Have Been Removed — What to do if HOS logs are missing on the unit.
- No cell - MS is not currently searching - Dispatcher — Troubleshooting when receiving "MS is not currently searching" message in Cell Diagnostics as a in office person
- No cell - MS is not currently searching - Driver — Troubleshooting when receiving "MS is not currently searching" message in Cell Diagnostics as a Driver
- No cell - Unable to Send or Receive Messages — How to troubleshoot a no cell issue.
- No Communication — Troubleshooting steps for a unit that is unable to communicate via cell and/or wifi.
- No GPS — Troubleshooting steps if you are unable to get a GPS signal
- No Power — Troubleshooting steps if your unit is unable to power up
- Printer Issues — Printer is not working correctly when trying to print from the TruckPC
- Unable to send Email to and from the Unit — How to troubleshoot an issue where you are unable to send Email to and from the unit
- Unit Turns Off While Driving — What to do when your unit is rebooting while driving
- Watchdog — Information when the TPC unit is experiencing Watchdog errors
- White Display — For when your unit is only showing a blank white screen on the display
- HOS 6_0 Hours of Service reference card_v03 — Reference Card for new HOS in DTCore 6.0
70 hr Violation Goes Away After Midnight
Problem:
A violation that was recorded on the driver's logs has been removed after midnight.
Solution:
This is currently intended functionality. The day will be marked in FleetWatcher as previously containing a violation with an icon that has a white X inside a yellow circle.
Related articles
-
Page:
-
Page:
-
Page:
-
Page:
-
Page:
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.
- Log out of the DriverTech unit by pressing the blue power button.
- Power the unit off by pressing the Power button once more -- leave turned off for about 2 minutes.
- Check connections on the back of the screen to make sure there is nothing loose.
- Then power the unit back on, by again pressing the Power button.
- If the issue persists: remove power from the unit via either the fuse or the battery kill switch.
- Keep the power disconnected for 5 minutes
- Bring the unit back up and test the touchscreen
- If the issue persists remove power via either the fuse or battery kill switch for 30 minutes
- Bring the unit back up and test the touchscreen
- If the touchscreen is still inoperable, clean it using this procedure.
- Power down the unit
- With a damp cloth, with finger pressure, wipe from the top-left over to the top-right
- Continue the process row-by-row until the bottom-right is reached.
- Clean out the edges next to the bezel
- Power the unit back up
- If the screen is still not responding to touch, it will need to be brought into a shop.
- 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
-
Page:
-
Page:
-
Page:
-
Page:
-
Page:
BSOD (Blue Screen of Death)
Problem:
Screen has a blue background with white text.
Solution:
- 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.
- Disconnect power to the TruckPC for about 2 minutes.
- As a last resort- if the problem persists, disconnect power to the TruckPC for about 30 minutes.
- Unplug power from TruckPC or flip the battery kill switch.
Please inform your in office personnel, your shop or, call technical support.
Related articles
-
Page:
-
Page:
-
Page:
-
Page:
-
Page:
- 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.
- Unable to render {include} The included page could not be found.
Co-Pilot Error Messages
Problem:
There are error messages when you open the Co-Pilot application.
Solution:
- Have the driver Log out of the device.
- Then press the power button
. - Once the unit has gone to a black screen, wait 30 seconds then power it back on.
- Log on when asked to submit your Driver ID.
- If the problem continues to occur Inform ALK/Copilot of the issue.
- This link (http://copilotpro.com/us/contact/) and filling out their form.
- You can also reach them over the phone at: 609.683.0220 or 877.573.0138
Related articles
-
Page:
-
Page:
-
Page:
-
Page:
-
Page:
CoPilot is Showing UTC time
Problem:
Co-Pilot's time zone is set to UTC.
Solution:
- This is a setting in CoPilot, and will need to be configured within the application.
- If you need help configuring the CoPilot application, please contact ALK by going to:
- This link (http://copilotpro.com/us/contact/) and filling out their form.
- You can also reach them over the phone at: 609.683.0220 or 877.573.0138
Related articles
-
Page:
-
Page:
-
Page:
-
Page:
-
Page:
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:
- Please call ALK to report Issue.
- This link (http://copilotpro.com/us/contact/) and filling out their form.
- You can also reach them over the phone at: 609.683.0220 or 877.573.0138
Related articles
-
Page:
-
Page:
-
Page:
-
Page:
-
Page:
- Unable to render {include} The included page could not be found.
Could Not Reimage
Problem:
Could Not Reimage
Solution:
IMPORTANT NOTE: Never unplug the Reimager while the unit is on. Turn off the unit before unplugging the Reimaging device.
If you have a 3 piece system(Antenna, Display, CPU) installed, do not plug into the Display to try to reimage
DO NOT USE the DISPLAY'S USB PORTS, plug directly into the CPU.
You are most likely experiencing USB port connection issues.
Check the USB connections
- Try a USB cable that you know works
- Try another USB port
Related articles
-
Page:
-
Page:
-
Page:
-
Page:
-
Page:
- Question:
The JBUS data information is not recording on my TruckPC. What should I do?
Answer:
- Check your connection: Make sure the truck’s ignition is on.
- Restart the engine.
- If you have a Rev6 unit and a truck that is 2010 or newer, make sure the TruckPC is connected to the J1939 connections for accurate and correct JBUS readings
- Restart the device.
- Restart the device by first logging off, then pressing the Power button to shut off the device. Once the device has been shut off, press the Power button again. This will cause the device to reset and reconnect.
- You can also try unplugging the device from your J-bus and re-plugging it while the device is powered off, or checking the Diagnostics tab under the Sys Info icon on the Menu of your TruckPC
Related articles
-
Page:
-
Page:
-
Page:
-
Page:
-
Page:
Restart the device: Restart the device by first logging off, then pressing the Power button to shut off the device. Once the device has been shut off, press the Power button again. This will cause the device to reset and reconnect. - Question:
What constitutes a long/mid/short idle in the reporting?
Answer:
Short, Middle and Long idle are not configurable.
- Short idle is 15 minutes of idle and less,
- Mid idle is between 15 and 90 minutes.
- Long Idle is 90 or more minutes of idle time.
Related articles
-
Page:
-
Page:
-
Page:
-
Page:
-
Page:
- Question:
Why are violations from a different month showing up in my report for the month I chose?
Answer:
The violations report gets all violations by both HOS LogDate and by HOS SubmittedOn/RecordedOn time.
It’s like this in case a previous log is created/edited &submitted later in time, also if you edit a previous log later and introduce a violation.
Related articles
-
Page:
-
Page:
-
Page:
-
Page:
-
Page:
-
- Question:
Why is my unit shutting down while I'm driving?
Answer:
Possibly this issue is linked to a cabling issue with the Power Cable
Some situations require a new power cable or changing the location from which we connect to Constant Power and Ground in the truck.Related articles
-
Page:
-
Page:
-
Page:
-
Page:
-
Page:
-
- Question:
Why was I put on the drive line before I started driving?
Answer:
The TruckPC knows if the wheels are rolling or not. When it senses driving, it marks the time that the driving started internally in memory, but it doesn't display it until the driver drives the minimum required miles (configurable). Once it hits that minimum mile mark, the system puts the driver on the drive line at the time the wheels originally started moving. A 5 minute period of no motion is required to reset the driving started time
In almost all cases of this event, the unit had detected driving previously, but was not given a full 5 minute period of no motion to reset the driving started time
Related articles
-
Page:
-
Page:
-
Page:
-
Page:
-
Page:
-
- Unable to render {include} The included page could not be found.
- Unable to render {include} The included page could not be found.
- Unable to render {include} The included page could not be found.
- Question:
How can I change the backlight/volume on my TruckPC?
Answer:
- To adjust the backlight or volume on your device, select the SysInfo icon on the TruckPC Main Menu. This will bring you to a Settings tab.
- Here, you can select to adjust the screen’s brightness/volume by touching the Down and Up buttons. You can also touch and draw your finger across the percentage box.
- Touching "Low" for the backlight settings dims the screen to 1%.
- Touching "Off/Mute" will shut off the backlight/volume completely.
- If you have touched "Off" on the backlight, press the physical button that says "Menu" to bring the screen back up to the same brightness it was at BEFORE the "Off" button was touched.
Related articles
-
Page:
-
Page:
-
Page:
-
Page:
-
Page:
- To adjust the backlight or volume on your device, select the SysInfo icon on the TruckPC Main Menu. This will bring you to a Settings tab.
- Question:
How does Daylight Savings Time (DST) work with my ELOGs?
Answer:
Spring:
At 11 PM Terminal Time (time on the unit) on the night before the time change, the time device will lock out any duty status changes for one hour. Then, at 12 AM (Terminal Time), the device will automatically jump one hour ahead to display 1 AM on the morning of the day of the time change. This time shift is designed to be seamless.
- During the time change, the black notification area of the HOS screen will feature a message stating: "Please wait while software adjusts for time change. This will complete in XX:XX (countdown to reset completion)."
Fall:
- At 12 AM Terminal time (time on the unit the unit will be locked for one full hour until 1AM. The time on the unit will start AGAIN at 12 AM, starting a "Second" 12 AM. This will indicate that the time change has completed. Please note that the time change will occur based on the driver's terminal time (the time on the unit). This time shift is designed to be seamless; no interaction from the driver is needed.
- During the time change, the black notification area of the HOS screen will feature a message stating: "Please wait while software adjusts for time change. This will complete in XX:XX (countdown to reset completion)."
Note:
Please note that the system will prevent any changes to status while the time change occurs. If there's a need to log out during the time change, the system will move to default status and will not allow changes to another status. After the time change is complete, the system will unlock and status changes can be made.
Please note that the time change will occur based on a driver's terminal time and whether or not that location participates in Daylight Savings Time. All hours of service (HOS) rule timers will stay the same, and no time will be lost or added to the driver's logs.
The best course of action, if possible, is to go Off Duty and allow the device to reset through Saturday night and Sunday morning. This will yield perfectly normal results with no intervention from drivers or managers. If a driver attempts to change duty status during the lockout time, an administrator will need to edit the log from FleetWatcher
If you forget to go off-duty over the time change weekend we recommend the following:
- Do not edit anything on the Sunday of the time change
- Add an Off-duty status at 00:01 on the Monday after the time change
- Download your logs for the last 8 days
- Use paper logs starting from Sunday of the time change
- Disconnect power from the unit for the next 34 hours
- PLEASE ENSURE THAT YOUR CURRENT STATUS IS OFF-DUTY
- Reconnect power after 34 hours and continue using the unit from there
Notes from Mike S for Spring 2017 DST:
From: Mike Stephenson Sent: Friday, March 10, 2017 11:35 AM To: Support Subject: RE: Time Change
Here’s what I found:
(all times are based on the unit)
- At 11:00 the unit goes on lockdown.
- At 12:00 the graph moves, the time adds 1 hour. (See screenshots below)
- At 01:00 the unit time changes to 02:00
Thanks,
Mike
Related articles
-
Page:
-
Page:
-
Page:
-
Page:
-
Page:
- Question:
How does the TruckPC detect driving?
Answer:
- The TruckPC knows if the wheels are rolling or not. When it senses driving, it marks the time that the driving started, but it doesn't display it until the driver drives the minimum required miles (configurable). Once it hits that minimum mile mark, the TruckPC puts the driver on the drive line at the time the wheels originally started moving. (i.e. If you start driving at 12:00, and reach the minimum required miles at 12:05, the TruckPC will put you on the drive line at 12:00)
- When the wheels stop moving, the TruckPC marks it internally in memory without displaying it or moving the driver off the drive line until 5 minutes have elapsed. This is to prevent the TruckPC from going to On-duty every time the driver stops at a light or stop sign. Once the 5 minutes have elapsed, the system marks the time that the wheels stopped moving as "On-Duty" on the driver's log.
There is a "driver lockout" period of 10 seconds (this is configurable on the Web Portal by in office personnel) where the driver cannot change his status after the wheels have stopped moving. In other words, if the driver stops moving at 12:00:00 he is locked out until 12:00:10.
Related articles
-
Page:
-
Page:
-
Page:
-
Page:
-
Page:
-
- Question:
How does unassigned driving work?
Answer:
- Unassigned Driving occurs when driving occurs on the vehicle without anyone being logged in.
- The Unassigned driving segment will be sent into FleetWatcher once the Driving segment has been completed.
- Once the driving segment reaches FleetWatcher, it is put in the Unassigned Driving Report.
- Once in the report, the Unassigned Driving segment on the unit will send information once a driver has answered the question (which appears as a pop-up window on the unit).
- The answer to the question will determine what happens to the Driving Segment that is already in FleetWatcher.
- If the driver answers "Yes" to the question FleetWatcher will then place that segment into the driver's logs under the drive-line.
- If the driver answers "No" to the question the unit will continue to ask the question to any other drivers who log-in to the unit.
If the driver cancels the question then the driver will continue to be asked the question for the canceled segment every time to the driver enters HOS.
Related articles
-
Page:
-
Page:
-
Page:
-
Page:
-
Page:
- Unable to render {include} The included page could not be found.
- Question:
If I turn the TruckPC off and start driving, will it record my drive time?
Answer:
No, but once it senses that ignition is ON, the TruckPC will automatically turn itself on.
Furthermore, the TruckPC will detect that the vehicle is moving. Since you're not logged in, it will be recorded as Unassigned Driving.
Related articles
-
Page:
-
Page:
-
Page:
-
Page:
-
Page:
-
- Question:
I received a low memory warning. What should I do?
Answer:
This warning appears when the device has been in use for a long time. Simply turn it off and turn it back on again to clear the memory. This will not affect the address book or any data you have saved on the device.
Related articles
-
Page:
-
Page:
-
Page:
-
Page:
-
Page:
-
- Question:
The JBUS data information is not recording on my TruckPC. What should I do?
Answer:
- Check your connection: Make sure the truck’s ignition is on.
- Restart the engine.
- If you have a Rev6 unit and a truck that is 2010 or newer, make sure the TruckPC is connected to the J1939 connections for accurate and correct JBUS readings
- Restart the device.
- Restart the device by first logging off, then pressing the Power button to shut off the device. Once the device has been shut off, press the Power button again. This will cause the device to reset and reconnect.
- You can also try unplugging the device from your J-bus and re-plugging it while the device is powered off, or checking the Diagnostics tab under the Sys Info icon on the Menu of your TruckPC
Related articles
-
Page:
-
Page:
-
Page:
-
Page:
-
Page:
Restart the device: Restart the device by first logging off, then pressing the Power button to shut off the device. Once the device has been shut off, press the Power button again. This will cause the device to reset and reconnect. - Question:
What constitutes a long/mid/short idle in the reporting?
Answer:
Short, Middle and Long idle are not configurable.
- Short idle is 15 minutes of idle and less,
- Mid idle is between 15 and 90 minutes.
- Long Idle is 90 or more minutes of idle time.
Related articles
-
Page:
-
Page:
-
Page:
-
Page:
-
Page:
- Question:
Why are violations from a different month showing up in my report for the month I chose?
Answer:
The violations report gets all violations by both HOS LogDate and by HOS SubmittedOn/RecordedOn time.
It’s like this in case a previous log is created/edited &submitted later in time, also if you edit a previous log later and introduce a violation.
Related articles
-
Page:
-
Page:
-
Page:
-
Page:
-
Page:
-
- Question:
Why is my unit shutting down while I'm driving?
Answer:
Possibly this issue is linked to a cabling issue with the Power Cable
Some situations require a new power cable or changing the location from which we connect to Constant Power and Ground in the truck.Related articles
-
Page:
-
Page:
-
Page:
-
Page:
-
Page:
-
- Question:
Why was I put on the drive line before I started driving?
Answer:
The TruckPC knows if the wheels are rolling or not. When it senses driving, it marks the time that the driving started internally in memory, but it doesn't display it until the driver drives the minimum required miles (configurable). Once it hits that minimum mile mark, the system puts the driver on the drive line at the time the wheels originally started moving. A 5 minute period of no motion is required to reset the driving started time
In almost all cases of this event, the unit had detected driving previously, but was not given a full 5 minute period of no motion to reset the driving started time
Related articles
-
Page:
-
Page:
-
Page:
-
Page:
-
Page:
-
- Unable to render {include} The included page could not be found.
-
A-B
-
C
-
D
-
E
-
F
-
G-H
-
I-J
-
K-L
-
M
-
N-O
-
P-Q
-
R
-
S
-
T
-
U-V
-
W-Z
-
0-9
- No labels