Eobrd mileage doesn't match truck mileage

I will miss loose leaf paper log book

 

Giving the ELD a try...BIT...the ELD is not recording correct daily miles driven...anybody else having issues with this?

 

Ok...just got off the phone with Jim @ Blue Ink Tech.

Here's my issue:

Tuesday ELD logged 184 miles driven. Driver actually drove for 302 miles...

Wednesday (yesterday) ELD logged 164 miles driven. Driver actually drove for 269 miles.

The odometer reading is also off. Truck actually has 629K miles. ELD is showing 83425. That part doesn't really "matter" to me. But how in the world can BIT attempt to charge for IFTA reporting if the miles driven are NOT correct???

Jim says it's just "the way it is" because of the mandate and having to go "by the engine miles." Makes sense for the odometer reading. But shouldn't daily miles driven be accurate????

BIT was attractive to our business because it's very simple and there are no ongoing monthly fees. It's recording duty status and time correctly, but these miles are nuts!

 

Their response is typical for the no monthly fee programs. Ask yourself how are they going to be able to sustain their business model once the rush for hardware is over and their revenue stream dries up.

As for your mileage not matching actual miles driven, their answer of it is what it is because the mandate is written that way is baloney. It also is grounds for a log violation since the miles driven must be reasonable close to the time driven, just like on paper. The mileage vs. time driven is still one of the metrics used to verify log accuracy. Additionally, the mileage discrepancy opens you up to all sorts of libility for tax issues regarding your IFTA and IRP mileage reporting.

 

When you first hook up the ELD to the ECM and you enter the truck information it will ask you if it's correct. If the ODO reading is not correct, change it then. If it isn't recording mileage properly you can edit that on the back office side.
If it isn't recording proper mileage, check that driver's logs and make sure it's actually recording the proper duty status. It might not be flipping to drive when it's supposed to once the truck starts moving. Mine did that a lot in the beginning until, after reporting it, they put out a software update.
I'm not so sure what the dash says really matters, as long as the ELD matches the ECM you should be fine.
If you have an AOBRD that isn't ECM connected and is relying on GPS data alone, it is probably an issue with device itself.
The ECM connected ones either have their own wifi or rely on your device's Bluetooth. The Bluetooth ones have connectivity problems. I had that problem too and after a software update that was resolved. It would lose connection several times during the day while driving and not record miles. Bluetooth is the most common with the bring your own device options.

 

Using a Rand McNalley and yeah it's not even close. I have no idea how it's going to record IFTA because it seems to only record ECM miles (and poorly at that) there doesn't seem to be any tie in to the GPS feature.

One week to go, better find that lawyer now, I'm sure Rand and I will be having words in the future.

 

Which ELD and which receiving device?

Mark

 

See what happens when people in office want to complicate things?

Now you got to line up ECM miles to odometers and what not......

Just keep adding more stuff....... SMH

 

Truck: '13 Cascadia with a Detroit
ELD: RM DC 200
Tablet: Digiland running Android 7.0

Supposedly there was a reflash coming last Tuesday night to fix some issues. Unfortunately I've come down with pneumonia and I'll be out of the truck the rest of the week. But on Monday the software threw an error code and all my clocks froze. Everything from 6am on was useless.