Quote:
Originally Posted by Redbaron57
Is it conceivable that a solar panel could prevent transfer case actuator faults by maintaining the battery voltage?
|
I've had 160W of solar panels on the roof for ~50Kkm (~140Kkm on the clock now.). They're charging two optimas, so night-time open circuit voltage is around ~12.7-12.9V, during daylight they're usually float-charging around 13.8V.
I haven't had any FDCM/actuator faults, but I also don't have the N23 update
.
That-said; I'm not sure how the 5V circuit is regulated, but it's hard to image it being affected by a low "12V". The additional current drawn regulating 5V from 11V instead of an expected 13V (just for example.) should be insignificant for automotive components.
It'd also only be an issue when the FDCM first powers-up, prior to the alternator energising.
Quote:
Originally Posted by Redbaron57
I want the equipment to detect and clear Diagnostic Trouble Codes myself. The dash display apparently only shows generic OBD2 faults. It doesn’t display any of my active codes. I have OBD2 Bluetooth dongles that communicate with my Windows laptop but have been unable to find software that detects and clears Jeep transmission codes. Torque Pro, for about $5 downloaded to my Android phone, is the only software I found that detected my 5 active powertrain codes via a dongle. It does not find or clear the two transmission codes C1405 and C140F caused by the N23 update. It trialled at least four Windows software applications (OBDwiz, TouchScan, ScanMaster and ScanTool - maybe others I forgot). None of these could even detect a disconnected air flow meter or faulty glow plugs that Torque Pro detected. I would be delighted to hear from anyone who knows of affordable software that is fully compatible with the Jeep, because I am sick of requesting refunds for software that didn't live-up to the seller's claim. (I did spot an iPhone app for Jeep analysis but I have not tried it because I don't own any suitable hardware.)
|
Our jeeps are tricky; not all codes are escalated to the PCM as true DTCs, and when they are, not all or accurate details are included.
ie, the PCM may report a DTC such as "Transmission solenoid 1 voltage high" (that's not a real DTC btw), and the TCM (transmission control module.) may be holding it's own code(s) with the "real" details of that DTC.
Basically at the end of the day, for software to read, clear and understand all the codes reliably, a fair-bit of money needs to change hands (eventually finding it's way Chrysler.) for the protocol & code specs - Which means that cheap software is unlikely.
It's possible to figure things out without the Chrysler specs, but it's a minefield so if a software developer went down that path it'd most-likely end up costing more.
SuperChips seem to have the best position in the market, good investment IMO.
Quote:
Originally Posted by Clarky
|
I have a Flashpaq 3875, if you want to see if it can clear the N23 codes first. According to chatter on the US forums it works for the hemi.
Have you heard of anyone trying it on the CRD yet?
If the codes are stored & cleared in the FDCM (rather than the TCM.), it might work, since the FDCM setup is the same between the Hemis and CRDs. Otherwise probably wouldn't work if the TCM is involved, since it's integrated with the PCM in the hemis and a separate module in the CRDs.