Can you cheat an eLog?

Hmm interesting how I provoked a attitude related response from you. I am sorry I answered the OP's question by offering a complete example of how it is done.

Also I would like you to know that not everyone's trucking career is as great and perfectly planned as you claim that yours is. And that maybe just maybe a few of the drivers out there today are new and have not yet trained their body to sleep when they tell it to and might find something useful from my post as far as what to watch out for if their company asks them to do it this way.

Your attitude towards my post is unprovoked and unwelcome and certainly uncalled for.

Not to mention it has nothing to do with the topic but it's letting every one know you can be a jerk.

And I think you spelled wiener wrong.

 

why would you want to cheat on e logs if you could. That would be consider log falsifacation. which is huge fine, if LEO finds it. Is it really worth it?

 

And it would be darn difficult to use the excuse that it was human error like with a paper log.

 

True, it's not safer. But then, there is no mandate in the regs that you must sleep any time in the sleeper anyway. And unless the government starts mandating nanny cams in the truck to observe activity like sleep, it is a moot point. The only point of an EOBR is easier enforcement of HOS.

Stop light cameras at intersection are equally not about safety, but enforcement and revenue. And the list goes on and on....

 

Again, what is to elaborate? No the driver cannot change anything, and that is the point. Yes, the data can be altered by someone in dispatch... they do it all the time with errors. Therefore, the driver is taken out of the loop.

 

I really don't see why it would be worth it to cheat the e-log. All it does is put the driver in jeopardy of getting caught and fined, maybe fired.

 

Um hey, guess what, the underlying data is not to be altered under normal circumstances. That would take a computer hacker to do.

395.15 Has stated that the device and associated support systems are, to the maximum extent practicable, tamper-proof and do not permit the altering of the the information collected concerning the driver's hours of service....... and so on
395.16 not in effect yet but in the future to come has similar language.

In all cases of tampering I have seen the cheating/tampering whatever you want to call it is found. Yes you can cheat e-logs but any auditor worth a darn will be able to find the discrepancies.

Any purposefully made changes to a e-log also require it be an "annotation". Meaning the original required portion of information remains for side by side comparison. And most systems identify who made the annoations to the information.

Those who think that an eobr/e-log machine keeps everybody safe are dillusional. Most of what I have seen is that they help keep honest people honest.

Those that argue HOS, how much driving/working is too much, are just as silly because so many out there do fudge with logs, and some, don't really cheat, truthfully they log off duty or sleeper but didn't take the time to get the rest they should have. All the HOS reg's 395.? do is require a person have the time to obtain adequate rest.

It is 392.3 Ill or Fatigued Operator that would get you for not using that time to actually obtain the restorative sleep needed to continue.

If you were to step back and take a good honest look. It does get to be one big, merry go round, catch a tiger by his tail, dam if you do, dam if you don't, bunch of hooey.
Those that fail to recognize their own mental and physical limits and choose to drive when they shouldn't for any reason are those that bring shame to all drivers.

 

So you're saying that because it's is in the reg's the people in the office will not try to alter data?

I've heard of drivers driving around on line one in a metro area. Changed at dispatch. Is the driver then off the hook, if the data is altered?

I didn't think it was possible as well, until a driver from a company(it ends in England) addmitted to me that he does it all the time. Just requires a call to dispatch. Perhaps, the system has changes and no longer allows this, as my information is over a year old.