Good Night From II

DOT in Iowa has been bringing in Swift drivers to check logs.
My terminal told me this when I delivered near Kansas City and advised me to get them a fax number ASAP so they could send me my past 7 days.
And I went all the way through Iowa today, but got lucky.

I spoke to a Werner driver today. They are having the same problem and many of their drivers won't drive until it is fixed.

 

It's an omnitrac issue. All companies that have it are going thru the same issues.

 

Went to dispatch window in lathrop to see how I can get my last 8 days.
Guy said I only need 8 empty log sheets..lol
Said my dl can only issue them
That he not able too.
Didn't feel like arguing with him so just shook my head and walked out.
Before I left I rebooted system again and logs came back on so I left.
Got a few miles out and realized I forgot to certify my logs. So pulled over and logs back off again.
Wheeler ridge scale was the only one opened and I got a green light. Whew!!.
I thought the scales would have heard of the issues and pull everyone in.

 

Jurupa valley terminal.
Should have looked for a parking space t the t/a.
But being a bonehead I came here instead.
Yard Dog showed me where to park..down by the shop.
Got a message saying to reboot the Qualcomm. So I did.
Looks like it's working again.
Only thing it kept me on the driveline the whole time.
I was able to change status but I guess it didn't take it.

 

We were sent a message a couple hours ago to reboot the QC to fix things.
I did, and it seems fine now. I had powered down the whole truck for 6 minutes.
A few minutes ago a message from the same Telemetrics people that said to hold off on the reboot because things were still not working correctly.

90 minutes later, they send this message?
Please!

But my QC seems to be back to normal now. I don't have today's logs, they show off duty the whole time. But I kept a paper log today which I will scan in tomorrow.
I'm hoping the Swift people in charge of that will get things updated quickly on my QC.

I'm not sure I should certify anything until those paper logs are added in.

 

Got those same messages.
I went and rebooted it. Went into driver lounge to eat my dinner and watch last parts if football game.
Came back and turned it on and it's been working.
Went and certified everything since I can't edit driveline anyways.
Go in in the morning and ask dl if safety can fix it.

 

Did it even record changes for today?
Mine did not. It shows off duty since I shut down last night.

Since the date had been changed on the QC back to 2000, nothing that happened today should be logged as happening today.

Tomorrow morning I will wake up to a fresh 70 after a 34 hour reset, but I know it isn't true.

 

From what I was just told, this whole mess was because of the global GPS system being updated.

That is something I read about last week. Android phones that had an older OS would stop functioning in many ways because of this if they didn't get the newer OS installed prior to today.

It sounds too much like the big deal back in 2000 about the older BIOS chips in computers not being able to handle the rollover date.

 

Here you can see and print your last 7 days :

Company : swift
Driver : your code
Log in : last 4 ssn

DHM UI

 

It shows when i went offduty, then onduty for.pretrip, then driveline.
All other changes I made didn't work. So stayed on driveline for 9hr39m which gave me a violation message lol