Plenty stuff here that would get you tickets if you showed it on a paper log. Hope the DOT gives you a break for the falsified information showing up on these things.
Mine has done that. It's also decided it would not record drive time at all. It's also decided to make a **** load of off duty time driving time when it couldn't figure a location as I rolled out. It has frozen. Best of all It's had days where it recorded ok but split my mileage into 5 or 6 random segments that didn't add up at all.
Auditor: "So your ELD malfunctioned for a few days in January?"Supposedly the cops have been "trained"
You could declare the thing broken, switch to paper, and for serious CYA, email the problem to the ELD vendor instead of calling them. Print out a copy of all emails in advance concerning the problem for the flatfeet for if and when the decide to give you the 3rd degree.
Quite the conundrum, eh?
In 8 days the problem disappears as far as the roadside guys are concerned, but retain all paperwork in your files against the possibility of a compliance audit.
And exactly why would you contact an ELD vendor except to resolve the issue?
*tit for tat removed*
Ok, let's see....
You really think that just documenting an ELD issue and then just continuing to run said unit isn't going to raise a red flag? Especially if it involves an apparent HOS issue? With your background especially, you know how short-sighted bureaucrats can be, and that's not an area I'd want to be taking a lot of risk with assuming they will understand the situation. <humor>
Is that better, with the humor turned off?
View attachment 43098
IP, I'm looking at this from the point of view of an auditor. If it's a one time thing, and obvious that there weren't HOS issues, no big deal. But if this is a recurring issue and the unit is never changed out, wouldn't you start wondering what was being pulled? It seems to me as if this would be an easy way to try and hide violations, say running a few hours down the road because a shipper hung you up in the dock for half the day. A few emails would sure make it looked a lot more legit. I've known guys to go to ridiculous lengths to make cheating on paper work, and this would be even easier to create a fake trail.And exactly why would you contact an ELD vendor except to resolve the issue?
Come on, you're smarter than this.
I'll have to try that "Rmsil" thing.There's a good deal of ELD functionality residing on a vendor's server, depending on the system architecture, as well. So while a given problem may lie in the hardware, it can also be part of the supporting software. You're going to have to deal with the vendors technical support at some point - if for no other reason than to arrange for return of faulty hardware.
What I'm suggesting (and I was attempting to do this without writing a couple editions worth of the Encyclopedia Britannia) was that just making a phone call to a vendor is not enough. As we all know, gubbermint auditors aren't the brightest bulbs in the pack. When it comes to regulatory issues, the existence of a phone call can be disputed - to your detriment. Rmsil leaves a chain of documentation that's much harder to dispute. Having copies of emails to your ELD vendor available not only for a roadside moron, but down the road for some numbnuts auditor in a compliance audit may well be the difference between getting rid of a nuisance, or extracting yourself from a regulatory nightmare.