Howdy y'all. I have an e450 that's the base of my RV. The manufacturer date of the chassis is November of 2003. The coach was manufactured in 2004, And it was sold is a 2005. Haha I love RVs

Okay so I have about a 2A current drain when the key is off. I started pulling fuses and identified a 1A draw on circuit 22, and a 1A draw on circuit 31.

Circuit 22 is a 15 amp circuit that's listed as: memory power radio, rear seat video control unit, battery saver relay, instrument cluster, courtesy lamp relay. I can immediately eliminate the rear seat video control unit because it doesn't exist. And the radio is aftermarket so my next step is going to be to actually fully disconnect the radio.

Circuit 31 is right headlamp low beam.

so I don't really know where to start in terms of things to start unplugging and look for current draws. Especially the headlight. is there some sort of control module on each headlight? since the RV was manufactured originally in Canada and sold in the US I did discover the Canadian option full-time headlight module. I disconnected it because I wasn't very fond of my headlights on 100% of the time. But other than that I haven't really made any other changes. Does anybody have any suggestions? I'm not real familiar with these platforms.

Thanks in advance!

 

The headlamps were on as a safety measure assuring that you were seen and hopefully preventing anyone from driving into you and saying ,I didn't see you.

The battery saver relay may not doing it's job and unfortunately it is part of the instrument cluster. It might be a good idea to confirm this with a good scan tool before replacing the cluster..

 

Meh If someone can't see a 36-ft long 14-ft tall white RV, then they probably shouldn't be driving. Besides that module look like it was on the verge of catching on fire. The thing was all split and cracked and had clear signs of heat stroke. So good riddance.

Tell me about this scan tool. Are you talking beyond a standard OBD2 scanner? The scan tool I have now has extended Ford scanning capabilities and doesn't report any problems. But maybe there's something beyond that?

 

There is no such thing as a std OBDll scanner, maybe a code reader, but a scan tool will usually check module health and report if there is any kind of problem.
Scan tools run anywhere from $2,000.00 to $6,000.00 depending on how much info you want. If you do have a scan tool check the module health and see what it shows.