Hello
I've been running Dashboss successfully in my Excursion for about a year, and lately have been having trouble with it, initially with connecting to my phone, and then after a firmware update, with getting proper readings.
I tried the suggestions I could find online and when none of those helped I reached out to Dashboss support. I have nothing but good things to say about DB customer service, very quick response, but we seem to have concluded that the trouble must be in my truck. Without going into too much detail about the troubleshooting process, it only half works in my Excursion for monitoring PIDs.

I'm also having engine troubles, and had just gotten a CEL so decided to check codes, but the scan showed no codes. We dug out the old Super Chips reader that came with the truck and it picked up 4 codes.

Right around that time, my friend showed up with her 2007 Jeep, so I plugged DB into that, and it worked fine - showed live values for all gauges, and pulled up a couple of DTCs.

And finally, this past weekend we bought a "new" 2006 F350, and DB worked flawlessly in it.

Do you have any insight into what this means for my Excursion? Would you expect that my mechanic will be able to get readings, or is this going to have to be addressed first?

Thanks

 

What did you do in the troubleshooting steps.

I take it you do have power to the port.
Have you looked at the PCM to see if you might of
had rodents chewing on the wires?

We are going to have to do some network testing and
without IDS it gets harder.

Are you getting any codes?

 

Largely copied and pasted from my emails to Dashboss support:
"I started not being able to connect at all, and having just done an iOS update (10.3.3) on my iPhone 5s, I brought the DB Gateway in to the house to do a firmware update.
Once the firmware update was done I was able to connect, but had to re-establish the connection for every drive. And after a few days of that I once again was unable to connect.
I looked at the troubleshooting advice on the DB website and first tried the easy steps - powered down the phone, "Forget this Device", and reconnect. There was no improvement so I tried a Level 1 reset. After that process, I was able to connect but none of the 6.0 PIDS were available. I found a switch in the Config menu to Force Ford VIN, and after that I could search for and find the 6.0 PIDS, but I can only get 6 of the slots on the gauges screen to show any readings. The rest all say N/A.
I then tried a Level 2 reset, but I can still only get 6 gauges to work.

I remembered another detail about a weird occurrence while I was trying various "fixes?" The FICM main volts slot was flickering rapidly back and forth between 48.5 and N/A, just for a few seconds and then settled on N/A.

And I have a new detail to add. I know I'm having issues with the vehicle, (most likely head gaskets) and today my check engine light came on. I tried to read the code, and it went through what I assume is the normal scanning process - a progress wheel showed percentage of the scan, and it took about a minute or less. But it said there were no codes found.

Scanned it with the Super Chips scanner we had stashed away and got
P0403
P0405
P1260
P0269"

I haven't yet started the vehicle since then, so I can't tell you if there are any new codes. I might be able to go for a drive a little later today. Maybe to my mechanic and his IDS.

Ken at DB mentioned a few possibilities - a timing or sequence issue, wiring or ECU getting flaky, a bad ground in the harness...

Rodents are always a possibility, but I don't see any evidence of them. Our cat is pretty good at keeping the population in check, there's no visibly frayed or chewed wires.

 

How are your batteries?
Dirty grounds could cause issues. I would clean
the batteries and the cables and see if that helps.
While you have the driver side battery out for a good
cleaning unplug and plug back in each of the PCM
connectors. That should reseat the pins. Also take a look
for signs of any corrosion on the plugs.

Is the EGR valve installed in this engine or was it removed?
You have 2 DTCs for the valve and 1 #3 contribution.
The one that is making a lot of look at me signs to me
is the PATS code that is coming up. >>> P1260 - Theft Detected.
I don't have the correct book right in front of me so I used Google
to find that.

 

Network issues can be a pain but it sounds like you may have one. Terminating resistors may be a suspect. Check this thread. The origonal posters instrument panel issues aren't the same as your issues but start reading about post #8.

https://www.ford-trucks.com/forums/1...t-cluster.html

 

Finally got a chance to take the Excursion out for a little drive, and DB worked just fine. What the heck? I hadn't done anything other than look at the wires and wiggle a few of them.
Thanks for the link, Rusty. A lot of that goes over my head, but from the sounds of it the OP was having a lot of issues. My vehicle is running great, unless a network issue can cause or mimic blown head gaskets. All other electrical systems are ok, just the OBDII port as far as I can tell.

It also read codes for me when I got back, still EGR related. Yes, my EGR is still intact, and I'm not sure, but a delete may be part of the plan for next week. New codes today, but all EGR related:

Current DTCs
Power Train Code: P0407
Exhaust Gas Recirculation Sensor "B" Circuit Low
Power Train Code: P0488
Exhaust Gas Recirculation (EGR) Throttle Control Circuit A Range/Performance

Historical DTCs
Power Train Code: P0407
Exhaust Gas Recirculation Sensor "B" Circuit Low
Power Train Code: P0488
Exhaust Gas Recirculation (EGR) Throttle Control Circuit A Range/Performance

 

I haven't confirmed this yet, but I've seen that code a few times. I think it happens when I let the kids start the truck and their hand slips before they get the key turned all the way.

 

When you have some time go out and trace the harness from the EGR valve
down to where it is joined by the others. Is it soft and mushy? Likely the diesel
and oil have taken there toll on the wires. You might find the EGR issue hiding
under the tape at that location.

 

Sorry if the link or post was confusing. As I said, the OP in that thread had different issues than you are having, and of course it has nothing to do with headgaskets etc. If the DashBoss continues to give you trouble though, (and as you said the truck is the likely suspect) the resistance test at the OBD port and verifying power at the correct pin would be a good starting place. The discussion did get a little deep but both of the guys trying to help are Ford Tech's and very knowledgable.

 

No need to apologize - I like to learn, and Im not sure I would have tracked that down. I'll be sure to refer back to this if the issue crops up again. Reps sent

 

I have not looked to see if this is the same thing that Rusty posted the link to.
I happened to be looking for something else and thought you might find this useful.

Here is the original article link.

https://www.autoserviceworld.com/car...work-problems/

 

I'll be sure to report back here when I have more info. I'm avoiding driving it right now due to the head gasket and EGR issues I'm having. I've let my mechanic know that I've had some difficulty with the OBDII, in case his equipment can't connect properly either. Now to wait for a spot in the shop to open up.