DRB II Help--Making the SCI Cable, Need Pinouts
21 - 40 of 79 Posts
Your right.. and now I understand what you were referring to a little better.
I thought maybe they had to be posts to different threads.
Congrats on building the cable. If I saw this post earlier I would have commented that in my original drawing of the pins I think I reversed the pins, pin 1 is actually pin 7 and so on. This would have explained the issue you were having earlier trying to boot up the DRB, since that is what happened when I tried building the cable first.
I did notice on version 8 of the super cartridge, you have a DRB II Adapters menu. Any idea what that is? I don't have that on my version 7 cartridge.
I did notice on version 8 of the super cartridge, you have a DRB II Adapters menu. Any idea what that is? I don't have that on my version 7 cartridge.
Yeah the mirror nature of male, female pins kind of confused me.. until I got all the pieces put together.
Hacking a quick makeshift cable just didn't work.
Then I used a ohm meter to be sure ground was connected to ground on the DRB-II circuit board.. and therefore +12V had to be as far away from that as could be,
I made another YouTube video to demonstrate whats inside the DRB-II ADAPTERS menu
https://youtu.be/oW2MoqnSv7w
Joined
·
2 Posts
did you try Ebay?
Joined
·
2 Posts
what kind of car do you have?
Oh yes.. mostly eBay has moved on to the DRB-III and cables for that.
The DRB-II cables seem rather rare, they were considered consumables so if they didn't work many were thrown away rather than repaired.
But I'm still watching.
My Dad's vehicle is a Dodge 1989 Ram D250.
Digi-Key is pretty awesome (but so is Mouser) I ordered the USB to RS-232 (in a single cable connector with wire-ends) and the TINI Q-G (TA4FL) connector last Friday and it arrived Monday.
Here's a tip, scroll down when selecting the shipping to select the cheapest option by US Postal service it doesn't say it but if the package is light enough they'll nearly ship overnight.. just no guarantees. Still arrives in a well padded cardboard box or envelope in your mailbox.
This morning I took a few pictures and struggled with how to pull it apart and assemble it.
First here's what the mini-XLR looks like next to the PC/Printer plug on the DRB-II
![]()
And securely inserted
![]()
Next here's what the mini-XLR looks like next to the PC/Printer plug on the OTC4000E
![]()
And securely inserted
![]()
Removing the mini-XLR insert is very difficult and isn't described anywhere, here's how to do it, get a plastic pen
![]()
And use it to shove the insert backwards
![]()
It comes out and then falls apart into two pieces
![]()
I wouldn't worry after its assembled and the strain relief handle is screwed back on.. that should hold it in place, there is also a groove you can't see to properly align it in the housing with the quick release button on the side
The completed cable is a bit of an upgrade from 1988
This cable should have all the parts to connect to a modern USB 2.0 port on a PC and communicate natively with the DRB/OTC using RS-232 signals (beware that TTL RS-232 is not the same thing.. that was invented much later to be used with very small electronics and runs at smaller communications voltages.. this cable is different.. it runs at higher communications voltages and is deliberately "old school" compatible with traditional PC peripherals).
The Digi-Key cable here made by FTDI is something of a marvel.. I hope it works.
![]()
I have been reading the 1991 training guide for the DRB-II and it says the [Remote Connection: On] feature was intended for displaying menu options on an instructors screen and would significantly slow down the display of values.. bummer.
Still I plan to pursue it just to see if the GTC software can download recording sessions where the data might be captured faster. And perhaps the OTC4000E has improved software that overcame that. The OTC4000E seems somewhat superior in some ways. But it can never replaced the DRB-II because that is what the Powertrain manual and Service guide for the Light Weight Pickup D250 calls for.
However the OTC4000E was made by the same company that made the circuit board in the DRB-II and externally they are almost identical. (note: the cartridges are not interchangeable if only because the OTC4000E PathFinder-II and PathFinder-III cartridges are smaller in size and shape. The DRB-II cartridges are larger. The number of pins on the cartridges are different as well, the DRB-II cartridges have more pins.)
I'm sort of learning that the electronics in these "data readout boxes" or "monitors" was really slow relatively speaking.. and that could be why the DRB-II included the big red Volt-Ohm-Meter (VOM) connector on the top right.
The theory back then seemed to be.. that to "truly" test a sensor or other voltage varying device.. the digital data was either too slow or insufficient. So having a Digital VOM in the same device was convenient and handy. I also imagine it was useful when tracing out ground faults or short circuits. And digital "anything" in 1988 was kind of futuristic... lol.
[Footnote] The USB cable connector is "Clear" or "Transparent" because its suppose to have a red and green LED on the tiny circuit board that light up to indicate traffic.
Here's a tip, scroll down when selecting the shipping to select the cheapest option by US Postal service it doesn't say it but if the package is light enough they'll nearly ship overnight.. just no guarantees. Still arrives in a well padded cardboard box or envelope in your mailbox.
This morning I took a few pictures and struggled with how to pull it apart and assemble it.
First here's what the mini-XLR looks like next to the PC/Printer plug on the DRB-II
And securely inserted
Next here's what the mini-XLR looks like next to the PC/Printer plug on the OTC4000E
And securely inserted
Removing the mini-XLR insert is very difficult and isn't described anywhere, here's how to do it, get a plastic pen
And use it to shove the insert backwards
It comes out and then falls apart into two pieces
I wouldn't worry after its assembled and the strain relief handle is screwed back on.. that should hold it in place, there is also a groove you can't see to properly align it in the housing with the quick release button on the side
The completed cable is a bit of an upgrade from 1988
This cable should have all the parts to connect to a modern USB 2.0 port on a PC and communicate natively with the DRB/OTC using RS-232 signals (beware that TTL RS-232 is not the same thing.. that was invented much later to be used with very small electronics and runs at smaller communications voltages.. this cable is different.. it runs at higher communications voltages and is deliberately "old school" compatible with traditional PC peripherals).
The Digi-Key cable here made by FTDI is something of a marvel.. I hope it works.
I have been reading the 1991 training guide for the DRB-II and it says the [Remote Connection: On] feature was intended for displaying menu options on an instructors screen and would significantly slow down the display of values.. bummer.
Still I plan to pursue it just to see if the GTC software can download recording sessions where the data might be captured faster. And perhaps the OTC4000E has improved software that overcame that. The OTC4000E seems somewhat superior in some ways. But it can never replaced the DRB-II because that is what the Powertrain manual and Service guide for the Light Weight Pickup D250 calls for.
However the OTC4000E was made by the same company that made the circuit board in the DRB-II and externally they are almost identical. (note: the cartridges are not interchangeable if only because the OTC4000E PathFinder-II and PathFinder-III cartridges are smaller in size and shape. The DRB-II cartridges are larger. The number of pins on the cartridges are different as well, the DRB-II cartridges have more pins.)
I'm sort of learning that the electronics in these "data readout boxes" or "monitors" was really slow relatively speaking.. and that could be why the DRB-II included the big red Volt-Ohm-Meter (VOM) connector on the top right.
The theory back then seemed to be.. that to "truly" test a sensor or other voltage varying device.. the digital data was either too slow or insufficient. So having a Digital VOM in the same device was convenient and handy. I also imagine it was useful when tracing out ground faults or short circuits. And digital "anything" in 1988 was kind of futuristic... lol.
[Footnote] The USB cable connector is "Clear" or "Transparent" because its suppose to have a red and green LED on the tiny circuit board that light up to indicate traffic.
Excellent write up! If you can figure out a plug and play connector for the volt meter, that would be excellent. I haven't really looked into myself but I know with the right banana connector and lead, it can be made to work. Just have to put some time and research what will fit, which I haven't done yet.
I'm just guessing at this but the Elenco test leads have always been good to me. They cost a little more but are reasonable.
An Amazon search will turn some up:
Elenco Electronics TL-4 Electronic Test Lead
Those are "right angle" banana plugs, and its a set of black and red (you only need the red since the ground is through the vehicle) but you could think of it as having a backup.. or a complete "set".
People that use meters and stuff tend to pay more for probes and hang on to them separate from the equipment they use them on. Fluke users perhaps being the exception. But Fluke "only" users tend to buy things only once and expect an awful lot from their equipment and the accessories that come with them.
I do recall knowing a few electric meter collectors who swear by hanging their test leads up like bats in the belfry and oil them with silicone grease when not using them.. but to each their own.
If you prefer Alligator to Banana leads these should work:
Elenco Electronics TL-16 Banana to Large Alligator Test Lead
USB-2-RS232 Cable works
So I plugged it into the OTC-4000E with a PathFinder-III cartridge and started it up. The USB end was connected to a Netbook running WindowsXP and Hyperterminal.
As soon as I pressed [F2] [ 2 ] [ 2 ] the transparent USB connector started blinking Red/Green and the Hyperterminal window filled with stream of characters that formed a Menu.
Pressing various keys in Hyperterminal were accepted by the OTC-4000E like they were typed on the keypad of the OTC-4000E and vice versa.
I had started Hyperterminal at 8-N-1 (9600 BAUD)
YouTube video of the Cable working with the OTC-4000E
https://youtu.be/qvLifTC5vXo
![]()
I plugged the DRB-II into the same and got a bunch of jibberish without pressing anything on DRB-II startup.
So I switched to 8-N-1 (19200 BAUD) and got mostly intelligible characters. The stream was much faster however and it seemed the output was "re-painting" the entire Hyperterminal screen over and over.
The DRB-II did not accept any input from Hyperterminal however, it completely ignored pressing keys.
The DRB-II documentation I have comes from online and a training guide called "USING the DRB-II 1991" it has only one very small paragraph that indicates [remote display] defaults to off and is only used in Chrysler training sessions to display the instructors DRB-II on certain computers.
An engine diagnostic guide from 1989 only describes the DRB-II menus specifically related to diagnosing the powertrain.
So while the DRB-II I have apparently already had "saved" the configuration change to turn on remote display, that is not the norm.
Also there doesn't appear to be any other configuration parameters regarding bit, stop bit, parity or baud rates.
And the paragraph warned that leaving [remote display] turned on would significantly affect the speed with which the DRB-II display is updated with changes in monitored values.
So I plugged it into the OTC-4000E with a PathFinder-III cartridge and started it up. The USB end was connected to a Netbook running WindowsXP and Hyperterminal.
As soon as I pressed [F2] [ 2 ] [ 2 ] the transparent USB connector started blinking Red/Green and the Hyperterminal window filled with stream of characters that formed a Menu.
Pressing various keys in Hyperterminal were accepted by the OTC-4000E like they were typed on the keypad of the OTC-4000E and vice versa.
I had started Hyperterminal at 8-N-1 (9600 BAUD)
YouTube video of the Cable working with the OTC-4000E
https://youtu.be/qvLifTC5vXo
I plugged the DRB-II into the same and got a bunch of jibberish without pressing anything on DRB-II startup.
So I switched to 8-N-1 (19200 BAUD) and got mostly intelligible characters. The stream was much faster however and it seemed the output was "re-painting" the entire Hyperterminal screen over and over.
The DRB-II did not accept any input from Hyperterminal however, it completely ignored pressing keys.
The DRB-II documentation I have comes from online and a training guide called "USING the DRB-II 1991" it has only one very small paragraph that indicates [remote display] defaults to off and is only used in Chrysler training sessions to display the instructors DRB-II on certain computers.
An engine diagnostic guide from 1989 only describes the DRB-II menus specifically related to diagnosing the powertrain.
So while the DRB-II I have apparently already had "saved" the configuration change to turn on remote display, that is not the norm.
Also there doesn't appear to be any other configuration parameters regarding bit, stop bit, parity or baud rates.
And the paragraph warned that leaving [remote display] turned on would significantly affect the speed with which the DRB-II display is updated with changes in monitored values.
I know the DRB-III (DRB3) is usually recommended for communicating with ODB-II vehicles. But browsing Chryslers Patent portfolio I came across the following:
[This was filed in March 1994.]
[Which probably means the SuperCartridge V8.0 1996]
[would be ODB-II capable with the adapter.]
US Patent # 5555498 - US5555498.pdf
Future vehicles sold in the United States will be required
to provide a standardized diagnostic interface for scan tools.
This requirement is called
CARB/OBD-II (California Air Research Board/On Board Diagnostics II)
it applies to all new vehicles designed for the 1994 model year
and all new vehicles manufactured in the 1996 model year.
CARB/OBD-II offers a choice between several communications formats
including the ISO9141 communications format.
Use of the ISO9141 communications format will mean existing tools
such as the DRB-II, will be unable to communicate with
new vehicle computer systems.
There is a need for an interface to enable the DRB-II to communicate
with new vehicle computer systems.
SUMMARY OF THE INVENTION
This invention provides an interface as a physical adapter which allows
the use of the DRB-II with an ISO9141 communications (ODBC-II complaint)
engine and transmission controller network.
The adapter functions as a communications converter to be used with
the existing DRB-II diagnostic device.
The adapter enables bi-directional communications while conditioning
the signals entering and exiting the adapter and allows the diagnostic tool
to operate transparent of the adapter’s presence.
In so doing, the adapter provides two modes of communications support;
an SCI II mode and an ISO9141 mode.
----
Since SBEC is prominently mentioned versus SMEC (pre-ODB-II) my assumption is the added [menu] referring to "Adapters" in V8.0 version of the SuperCartridge, which is not in the V7.0 version of the SuperCartridge is for guiding the user with help menus to attach the proper adapter cable for ODB-II vehicles. And since MMC and JEEP are called out separately, it is possible the 16-way cable is for ODB-II connections (to Chrysler vehicles).
ODB-II was more about pulling information than really attempting to activate (or "acutate") circuits proprietary for a vehicle. So my guess would be with one of these "adapters" it would be about the same as a generic ODB-II scanner.
Mind you that does not mean it would upgrade an older pre-ODB-II vehicle such that you could use a generic scan tool with it. This is all about the newer Chrysler vehicles having to adopt ODB-II and keeping the ability to continue using the same old DRB-II as a scan tool and diagnostic tool on the newer Chrysler vehicles. Its not something of common usefulness. For example you would not want to use the DRB-II with the ODB-II adapter on a GMC vehicle.. which "electrically" it might be possible, but the Chrysler DRB-II would not know how to interpret the information coming from such a vehicle. In such a case the more generic "after market" tool maker OTC, Cornwell, Matco, Snap-On would be more likely to gather and provide wider coverage and interpretation of ODB-II information with their scan tools.
[This was filed in March 1994.]
[Which probably means the SuperCartridge V8.0 1996]
[would be ODB-II capable with the adapter.]
US Patent # 5555498 - US5555498.pdf
Future vehicles sold in the United States will be required
to provide a standardized diagnostic interface for scan tools.
This requirement is called
CARB/OBD-II (California Air Research Board/On Board Diagnostics II)
it applies to all new vehicles designed for the 1994 model year
and all new vehicles manufactured in the 1996 model year.
CARB/OBD-II offers a choice between several communications formats
including the ISO9141 communications format.
Use of the ISO9141 communications format will mean existing tools
such as the DRB-II, will be unable to communicate with
new vehicle computer systems.
There is a need for an interface to enable the DRB-II to communicate
with new vehicle computer systems.
SUMMARY OF THE INVENTION
This invention provides an interface as a physical adapter which allows
the use of the DRB-II with an ISO9141 communications (ODBC-II complaint)
engine and transmission controller network.
The adapter functions as a communications converter to be used with
the existing DRB-II diagnostic device.
The adapter enables bi-directional communications while conditioning
the signals entering and exiting the adapter and allows the diagnostic tool
to operate transparent of the adapter’s presence.
In so doing, the adapter provides two modes of communications support;
an SCI II mode and an ISO9141 mode.
----
Since SBEC is prominently mentioned versus SMEC (pre-ODB-II) my assumption is the added [menu] referring to "Adapters" in V8.0 version of the SuperCartridge, which is not in the V7.0 version of the SuperCartridge is for guiding the user with help menus to attach the proper adapter cable for ODB-II vehicles. And since MMC and JEEP are called out separately, it is possible the 16-way cable is for ODB-II connections (to Chrysler vehicles).
ODB-II was more about pulling information than really attempting to activate (or "acutate") circuits proprietary for a vehicle. So my guess would be with one of these "adapters" it would be about the same as a generic ODB-II scanner.
Mind you that does not mean it would upgrade an older pre-ODB-II vehicle such that you could use a generic scan tool with it. This is all about the newer Chrysler vehicles having to adopt ODB-II and keeping the ability to continue using the same old DRB-II as a scan tool and diagnostic tool on the newer Chrysler vehicles. Its not something of common usefulness. For example you would not want to use the DRB-II with the ODB-II adapter on a GMC vehicle.. which "electrically" it might be possible, but the Chrysler DRB-II would not know how to interpret the information coming from such a vehicle. In such a case the more generic "after market" tool maker OTC, Cornwell, Matco, Snap-On would be more likely to gather and provide wider coverage and interpretation of ODB-II information with their scan tools.
Hi! in this drawing pin 1 in one end matches pin 1 in the other end? i mean is a 1 to 1 2 to 2 conection and so on relation?Yes I did make the CCD/Airbag cable.
And pin 4 is the light green wire:
![]()
thanks for replying
Hi again! my DRB II cable is useless i am trying to set a DRB III diagnostic cable which looks similar but has 16 wires instead of 10. Doing more or less guessings on the order i made this cable to power on the DRB 2 scanner but is not retrieving any codes or information from the engine it hangs.
I'm not sure what your saying.
1. You made a DRB-II Six-way Engine Diagnostic Cable according to the Diagram in the picture?
2. You then tried to make a DRB III Engine Diagnostic Cable, which is similar but not the same. But neither the 6-pin SCI Engine Connector, nor the 8-pin DRB-II DIN Connector has 10 pins. The DRB-III Connector has 16-pins?
3. The DRB-II Engine Diagnostic Cable you made will power up the DRB-II but when you connect it to the Engine it does not pull any Diagnostic Codes or Information from the Engine?
It sounds like you have a DRB-II and built the cable, it would power up but not communicate with the vehicles engine.
It also sounds like you have a DRB-III and as a second project your trying to build an Engine Diagnostic Cable for it, but do not have a diagram for a DRB-III Engine Diagnostic Cable and tried to guess the pattern from the DRB-II Cable.
Is any of this correct?
1. You made a DRB-II Six-way Engine Diagnostic Cable according to the Diagram in the picture?
2. You then tried to make a DRB III Engine Diagnostic Cable, which is similar but not the same. But neither the 6-pin SCI Engine Connector, nor the 8-pin DRB-II DIN Connector has 10 pins. The DRB-III Connector has 16-pins?
3. The DRB-II Engine Diagnostic Cable you made will power up the DRB-II but when you connect it to the Engine it does not pull any Diagnostic Codes or Information from the Engine?
It sounds like you have a DRB-II and built the cable, it would power up but not communicate with the vehicles engine.
It also sounds like you have a DRB-III and as a second project your trying to build an Engine Diagnostic Cable for it, but do not have a diagram for a DRB-III Engine Diagnostic Cable and tried to guess the pattern from the DRB-II Cable.
Is any of this correct?
If it helps all of the DRB-III cable pin outs are diagramed and listed on pages 1-6, 1-7, 1-8 of the DRB-III Manual which is Online here DRB-III-Manual.pdf
All I had to do was Google it.
There are at least 3 Cables with a 16-pin Connector for the DRB-III.
The same diagrams for the DRB-II are not available online that I can see, but they are much simpler.
To jwillis84, Chrysler had a cartridge marked 98 Ultra V1.2 7-24-97 $CB56 53-200-9243 or something like that along with an OBD II looking connector for the DRB II for use in cars that were going to adopt the OBD II standard before 1996. See this post for more details:
http://www.turbododge.com/forums/f4...rysler-development-cartridge.html#post2507159
To ecaruci, the drawing represents the male end of a din 8 connector that plugs into the female end of the DRB. If you mirror image the pins, i.e. pin 7 is actually pin 1, the mirror image would be the pinouts of the female DRB connector. Use this to construct a cable using any generic din 8 connector and any spare SCI cable that you can cut up.
For my cable I bought a generic din 8 male cable, wired to a DB15 breakout box, which connects to my Actron scanner cable:
![]()
![]()
![]()
http://www.turbododge.com/forums/f4...rysler-development-cartridge.html#post2507159
To ecaruci, the drawing represents the male end of a din 8 connector that plugs into the female end of the DRB. If you mirror image the pins, i.e. pin 7 is actually pin 1, the mirror image would be the pinouts of the female DRB connector. Use this to construct a cable using any generic din 8 connector and any spare SCI cable that you can cut up.
For my cable I bought a generic din 8 male cable, wired to a DB15 breakout box, which connects to my Actron scanner cable:
Here's a YouTube Video I made about the DRB-II "engine cable" and how I'm going about making one from spare parts.
No expressed warranties or guarantees apply of course, if you try to follow in my foot steps "your on your own".
This is just meant to share the information.
Here's the Parts List for the cable I'm building. I quote high prices in the video but they're always falling in price. I didn't pay the high prices. Also I think a much cheaper cable can be built, but wanted to do it this way first.. and I'm debating what's the simplest least effort reliable cable that can be built - versus a more difficult to build less reliable, but cheaper cable..
OTC 212635 Chrysler SCI Connector to 8-Pin DIN
10.55
OTC 3305-72 DB-25 Power and 8-Pin DIN
18.00
839-1067-ND Digi-Key 8-Pin Male DIN to 6 ft shield cable
color coded wiring chart
12.98
970-25BPE-ND Digi-Key DB-25 Black Plastic Shell
2.55
225ME-ND Digi-Key DB-25 Male Pin Connector, Inline Solder Cups
1.31
DB25-G2 NIUTOP DB25 Male 2 Row Terminal Breakout Board (optional, only for development)
16.00
Bestek 12V Battery Clips and Aux Power Socket (optional)
9.00
No expressed warranties or guarantees apply of course, if you try to follow in my foot steps "your on your own".
This is just meant to share the information.
Here's the Parts List for the cable I'm building. I quote high prices in the video but they're always falling in price. I didn't pay the high prices. Also I think a much cheaper cable can be built, but wanted to do it this way first.. and I'm debating what's the simplest least effort reliable cable that can be built - versus a more difficult to build less reliable, but cheaper cable..
OTC 212635 Chrysler SCI Connector to 8-Pin DIN
10.55
OTC 3305-72 DB-25 Power and 8-Pin DIN
18.00
839-1067-ND Digi-Key 8-Pin Male DIN to 6 ft shield cable
color coded wiring chart
12.98
970-25BPE-ND Digi-Key DB-25 Black Plastic Shell
2.55
225ME-ND Digi-Key DB-25 Male Pin Connector, Inline Solder Cups
1.31
DB25-G2 NIUTOP DB25 Male 2 Row Terminal Breakout Board (optional, only for development)
16.00
Bestek 12V Battery Clips and Aux Power Socket (optional)
9.00
21 - 40 of 79 Posts
