Changes to QC logging parameters

I cant tell if there are any changes. I log off duty at shipper, and drove around looking for a empty. It still showed me I was off duty. Just morning at the truck stop, I had parked where the POV park. I drove around to the fuel island to get fuel and it still showed I was off duty.

 

No changes to ours here, its still acting the exact same as it always has.

 

It's still using the old thresholds. It's just that if you get mty and go to guard shack and get thru quickly, go roughly a mile and it switches to driving, the time will start from the time you moved with mty. This morning, I did pretrip, went off duty, screwed around a little, then took off, the time on drive line started as soon as pretrip was done, when wheels started moving. If I would have stayed off duty for 5 min or more drive time would have started later. Just keep track of your thresholds.

 

The message I got was the Qualcomm will start an imaginary clock as soon as your wheels turn. For that clock not to go into drive time you have to stop for 5 mins.

Edit.
my bad I missed that this was Schneider
I presume it would be the same with all QC users

 

Been testing a bit today. More to do though. Can say pulling out of a dock to shut the doors then shutting truck down to shut them didnt kick me on drive line at that time I pulled out. Noted the time I started the truck and released the brakes to actually leave. So far on one try that didnt start the drive clock pulling from a dock. At least on the graph. Gonna have them emailed again to see the text version tonight.

Also noticed it hasn't been the actual distance driven but as the crow flys distance away from starting point.

 

Nosing in...but, guys we had Peoplenet in the oil patch too. I know there may be differences, but this stuff is "manageable". Like anything else electronic, it has to be toyed with a bit, but you will learn the tricks. You're not going to be able to cheat it really, but you can keep it from costing you legitimate time. It's not a lot of time lost either way, but you'll learn it.

It was a little different out in the patch and different trucks seemed to have different thresholds, but with mine, I could drive exactly 5/10 mile before it threw up a "change to driving" window. The only option was to select YES, or just keep driving and it would automatically show driving from the point of movement. BUT, if you stopped ( I didn't have to slam on the brakes, just ease to the side of a lease road or county road and stop...in gear, clutched, foot on the brake), the "change to driving" message would go away in about 20 seconds an return me to previous status. I could go exactly another 5/10 and do it again. Obviously, you guys don't have the luxury of being in the middle of nowhere on a dirt road, but in the parking lot or shipper/reciever lot, you'll probably find that you have options. Just find the thresholds and work it accordingly.

 

The main time this will be an issue is when you are leaving a shipper/receiver and roll out into an area that has 5 million stop lights and hit them all while red. On Peoplenet as I got to that last light I would manually change over to the drive line and that would keep it from backtracking me to the 15 minutes I sat at the previous lights.

 

It still records it as drive time even though we don't see it on mcp 200.

When SNI pulls up a daily report of log activity it now shows exactly when where and how far and long you moved before it officially changes to drive time. The only time it shows on actual logs is when the threshold has been met.

 

I lost time today...approximately 40 minutes...someone has got to teach me something. ..I'm driving faster than I ever have...