After my "crash course" on DDEC ECM's I have a small problem still bugging me.
When using the DDDL Software, I would launch the app, the LEDS on my Inline 6 unit would go from Red to Green and the J1708 and CAN lights start flashing (normal) but the app would not connect to the ECM, (NO ECM FOUND) error.
Now if I ran the diagnostic software for the Inline 6 the CAN would connect at 16 mbps
Any ideas why the software wouldnt connect? I'm connecting to something, my only though is that the alison transmission has been spliced onto both communication ports..
I have one on the shifter panel (Which i'm 99% certain is for the tranny)
The other port is in the engine bay, with a broken switch marked (DDR)..
Looking over the DDEC IV install guides the standard "Vehicle Interface Harness" has a J1708 connection at the very end..
The ECM blanks out the Communications Harness Connector on the ECM (If I wired this to a 6 pin - Deutch could i connect direcly eliminating any wiring problems elsewhere)?
Thanks, Moose
Under the tools tab/options/interface are able to find your interface device? I don't know anything about the inline 6. I was thinking the inline 6 is a Cummins interface.
Ken
The Inline 6 is a Cummins interface mine only works with the 9 pin connector
The Inline is a cummins but you can buy the 6 pin to 25m DB plug (which I have)
The DDDL software supports the units as its in the list under "connections"
The software loads and connects to the inline, as stated it connects to "something" as the J1708 and CAN lights go green..
The boxes are pretty much all the same as most ECM's talk the same J1708 Protocol.
The later Allison's (I think any of the 6 speeds) uses 1939 for communication . I don't think 1939 is required for them to function properly maybe just a throttle position sensor, Clifford knows the details. I think you'd have other problems if the 1708 and 1939 were spliced together.
"The ECM blanks out the Communications Harness Connector on the ECM (If I wired this to a 6 pin - Deutsch could I connect directly eliminating any wiring problems elsewhere)?"
If you're talking about the connector pictured in the DDEC IV 1939 connector JPG I don't know. I always use the 1587 lines. If you try using the 1939 CAN bus for diagnostic communications it will need a 120 ohm terminating resistor across the lines. If that connector is not currently in use that means you have no 1939 connection to anything. I don't know if you have DDEC III or IV. 1939 was not available on the early DDEC III
Ken
Disclaimer: I'm not a DDEC expert
Do you have a Detroit or a Cummins engine?
Jack
Hey All,
Jack - Detroit (D50)
I've found the pin outs on the "Vehicle Interface Connector" but i suspect there's an issue with those lines.. The Pro-Driver will sometimes work, sometimes not.
However I do connect to something, if the line was complete broken then I would get a data connection.
So I guess the next step would be is building a connector to go from (Image 3-15) to a female 6 Pin Deutch plug that i could plug in directly (I'm assuming this is how the shops connect to the ECMs)
or even just run wires from the plug directly into my male 6 pin.
It's just strange how i'm getting an initial connection but the software will not enter the ECM.
I hear there's some software called Eaton Power Ranger that will tell me what data is being received (I maybe able to distinguish the protocol being received) and eliminate if there's some x-over from the TCM unit.. I know its a long shot but I get the same results if I use the engine bay 6 pin or the one of the shifter box in the cockpit..
Any DD guys, how do you connect up to your ecm? how does the software behave?
I use the the Nexiq USB link. It also has data bus monitoring, you can watch the addresses move across the bus, but I don't know how to determine if the addresses are corrupt are good. I think it also has a logging feature. Faulty addresses may be obvious, I've never looked for them. It works on any Detroit from II to 10, Cats, Allison, Cummins and more. I've never had a problem connecting to anything. If your Prodriver drops outs then you may have a wiring problem and connecting directly to the ECM probably won't help unless you disconnect the rest of the harness any only have your diagnostics on the 1587 connection. If don't have a problem soldering a couple of wires back together that would a simple test to see if the problem is your interface or the harness.
What software are you using to view the addresses?
I should have purchased the Nexiq instead of the inline I'm thinking.. its also half the price!
The software came with the Nexiq. Couple screen shots are attached. I'm curious why you chose a Cummins adapter. I did a lot of research before buying an adapter and the Nexiq was always at the top of the list with the Dearborn being a close second or equal to.
Looks like I can also download that software..
I chose the Inline because they claimed "full compatibility"
It also was one of the most durable and even came with a nice box ;)
I do however see a NexIQ purchase in the very near future.
Nexiq has new one out now. I'm guessing it has more CAN lines. As manufactures keep adding more modules, more communication lines are needed.
As the complexity of a system nears infinity the time between failures approaches zero.
Ken
I heard today that new Nexiq is having problems. So don't run out and buy the newest one.
You may want to try one of the older version of the DDDL.
Jack