Rand McNally ELD-50 and DC 200(s) Support Thread

Mark ... Should we be logged off driver connect before doing the update and does it matter whether or not we are synched with the ELD ? Thanks for your help.

 

I know I haven't griped in a while here, but here's an update:

Whether it's Rand McNalley's fault, Android's, Freightliner's or mine I'm only compliant 5/6 days.
So unless I'm a ball player, I'm only batting at 70%. Okaaayyy,,,

Come to find out, I am by FAR the most compliant driver at my company. From guys yanking out the ELDs, to guys who have screwed up their logs so badly, they'd face LESS fines if found w/out a logbook,,, possibly w/out a license.

Oh it makes my brain hurt.

So at this point, it doesn't matter how well *I'm* doing, because with 60-70% of my fellow drivers FLAGRANTLY non-compliant, the odds are pretty good we're eventually going to be put out of service.

*sigh*

I hope I'm eligible for unemployment.

 

Hi there I am a small company with two trucks using the ELD50 with the Overdryve 8 pro. Both drivers are having connection issues. It works great for a couple of days then the Driver Connect app cannot connect to the ELD50. They uninstall the app and reinstall and in 90% of the time it will work again but only for a couple of days. We updated the app a couple weeks ago to the newest version. Can you please help me with this.

Sherry

 

One thing to try is to turn off your wifi and Bluetooth on your device then open the app and allow IT to turn on your Bluetooth for you. It's an odd bug, but it sometimes forgets itself and conflicts the connection.

The nuclear fix is to go into the apps folder on the system (you're running an android right?) and either "clear cache" or "clear data" (make sure all of your logs are certified currently before doing it because there's a possibility of wiping out your history)

Really the best thing is to use a dedicated device so there isn't any interference from other apps.
(I shudder at the thought of people using their personal phones with this software)

Messing around I found a sub-folder (couldn't tell you where I found it, I forgot) where the program stores voluminous amounts of error codes. Like every SINGLE instance of a missed connection to the engine computer. I don't know if that's what fills up the data cache or what but I've gone on average about two weeks between "cleanings" and at most 3 weeks. I drive local/regional so my truck gets shut off at least 2 days a week and I don't idle most nights.

Is it a factor? Honestly I don't know, but I do seem to be having slightly more reliability than our OTR drivers.

 

I purchased the TND740 and ELD 50. All I have to say is Rand McNally needs to do what ever it takes to get rid of their problems they have. I am not bashing but there are problems. I have had my share of them and don`t really know what to expect when I start back up after being off for a week or more. FMCSA has already spoken, if not compliant you will pay the cost, no exceptions. I would hate to have to make a change cause I really like my 740 but.

 

Still no response from RM. My cousin bought one of these pos and its not working for him either.

 

Interesting detail I've noticed,

The ELD can detect if you open the driver's door.

Since our trucks sit (a lot) if the ELD is unused and the truck is off for a period of time the ELD will go to "sleep" (the indicator will go solid blue). But once you open the door the ELD will begin flashing it's startup sequence.

Now it probably doesn't do anything now, but at least when connected with a Freightliner the software knows when you open the driver's door. So if they ever want to upgrade and use the door sensor to enforce Sleeper Berth compliance?

Use the passenger side. It doesn't seem to notice. (Yet?)