so, you think your safe with the elog and hos.

Note the bold....That's part of the point for many here who don't have APU's....

And again...

I'd like anyone DOT...Company Safety Officers...To explain to us why an O/O on his "34" must log on line 4 to wash or maintain their own rig...Even if the rig is parked in their own driveway....

 

You still have to wash a rig once in while right?

 

That part of the rules has been in there for years. Nothing new.

The guys in Minnesota try to trick you into it by talking about how clean the truck is and when you washed it.

 

Or they get in a fatal accident, even if it might not be their fault, and their investigation finds out the driver swiped a card at a place that the log says he wasn't there. Elogs are no different than paper logs, you can "adjust" them if you want to. The FMCSA needs to pull their heads out of their ___________ to see that this is being done already.

 

Hence...Why I like my loose-leaf logs.....
When I'm home....I take my "34"....Log it as such and....The truck is "Self-Cleaning" and "Self-maintaining"....

Hell...When one pays the price of a small house for a rig....That's the least the ##### things could do for us....

 

Everything I heard about them....The Single-Pony O/O's won't have the "Edit Button" on their EOBR's...

Since as everyone has told me...."You don't own the data".....

 

From what I have read, there will be an edit button available. However, it will not be a true edit button. It will still retain the previous information, the new changed information, the time of the original event, the time of the change and who performed it.

 

PeopleNet currently does this.

[TABLE]
[TR]
[TD="class: sec, bgcolor: #E0E0E0"]EVENT[/TD]
[TD="class: sec, bgcolor: #E0E0E0"]DELTA[/TD]
[TD="class: sec, bgcolor: #E0E0E0"]LOG TIME[/TD]
[TD="class: sec, bgcolor: #E0E0E0"]CREATED TIME[/TD]
[TD="class: sec, bgcolor: #E0E0E0"]LOC / INFO[/TD]
[TD="class: sec, bgcolor: #E0E0E0"]REMARKS[/TD]
[TD="class: sec, bgcolor: #E0E0E0"]ODOMETER[/TD]
[TD="class: sec, bgcolor: #E0E0E0"]CREATED BY[/TD]
[/TR]
[/TABLE]


You get your
Event: duty status change, log in, log out, inspections, etc, etc.
Delta: time between events
Log Time: will give you the date and time of the event.
Created Time: gives you the date and time the event is created on the log
LOC/INFO: gives the GPS coordinates and the corresponding location nearest for whatever city and state
Remarks: shows whatever the driver typed in to go along with the event.
Odometer: Shows odometer reading, only reports beginning and end of day, unless PC is used then shows starting, exceeding company policy, and ending odometer
Create By: indicates who created the log entry, driver, system or specific person.

When a log is edited the original entry stays in black, the correction shows in red along with the name of the person that made the correction. This entry gets times stamped to show what time the correction reflects on the log, what time the person created the entry. Makes you think twice about fudging someones logs.

 

I've been written up for not having duplicates. I'm O/O like you.

 

KY tried that "why dont you have duplicatses?"once on me

i said i tripscan them to the office after every trip

he was satisfied