8. Reference: Connector Pinouts and Cable Signal Mappings
This chapter contains complete pinouts for the connectors on the RAD-Galaxy, as well as those on the network interface cables used to attach to it. For your convenience, tables are also provided that show the mappings of signals between pin numbers on the connectors of each network cable. We’ve also created inter-cable signal mappings that show all of the signal flows on a configured device.
Note
Note: In most configurations, the LIN channel of the RADGalaxy is also used as the Ethernet Activation line for DoIP, the exception being when the neoVI FIRE 2 OBD Cable with DoIP support is used. Since this chapter is large and readers who reference individual cable pinouts may not see this note, a reminder has also been provided in places where relevant.
8.1. RAD-Galaxy Connector Pinouts
In this section we provide a complete list of the pinouts for the connectors on the RAD-Galaxy, as well as those on the network interface cables used to attach to it.
Note
The RAD-Galaxy channels and device labels still use the term BroadR-Reach (BR) since the device predates the formal 100BASE-T1 specification. As mentioned earlier in the manual, the RAD-Galaxy supports devices meeting either standard.
8.1.1. RAD-Galaxy Nano MQS 100BASE-T1 (BroadR-Reach) Connector 1 Pinout Details
A detailed description of the pinout of 100BASE-T1 (BroadR-Reach) Ethernet connector 1 can be found in Table 2. A close-up of the connector is shown in Figure 78.
Table 2: BroadR-Reach Connector 1 Pinout Details.
Figure 78: BroadR-Reach Ethernet Connector 1 with Pin Assignments.
8.1.2. RAD-Galaxy Nano MQS 100BASE-T1 (BroadR-Reach) Connector 2 Pinout Details
See Table 3 for the details on 100BASE-T1 (BroadR-Reach) Ethernet connector 2, and refer to Figure 79 for a close-up of the connector and its pin assignments.
Table 3: BroadR-Reach Connector 2 Pinout Details.
Figure 79: BroadR-Reach Ethernet Connector 2 with Pin Assignments.
8.1.3. RAD-Galaxy HD-26M Conventional Network Interface Connector Pinout Details
The details for the conventional network (CAN/MISC) DB-26M connector are shown in Table 4 and Figure 80.
Table 4: HD-26M CAN/MISC Conventional Network Interface Connector Pinout Details.
Figure 80: HD-26M CAN/MISC Conventional Network Interface Connector with Pin Assignments.
8.2. RAD-Galaxy Ethernet Cable Adapter Connector Pinouts and Signal Mapping
This cable, which is described and illustrated in Section 2.4, is the RAD-Galaxy’s primary attachment cable for all networks except 100BASE-T1. Its HD-26F connector attaches to the HD-26M on the RAD-Galaxy, and thus has the same pinout. Below are the pinouts for the other three connectors on this cable (HD-26M, DB-9F and RJ-45F) as well as a mapping table that shows how the signals on the various connectors are aligned.
8.2.1. HD-26M Connector
The HD-26M connector has the pin assignments shown in Table 14, with pin numbering the same as that shown in Figure 80.
Table 5: RAD-Galaxy Ethernet Cable Adapter DB-26M Connector Pinout.
8.2.2. DB-9F Connector
Table 6 shows the pin assignments for the DB-9F connector, with pin numbering illustrated in Table 19.
Table 6: RAD-Galaxy Ethernet Cable Adapter DB-9F Connector Pinout.
Figure 81: RAD-Galaxy Ethernet Cable Adapter DB-9F Connector with Pin Assignments. The pin numbers are printed right on this connector, but may be hard for some to see. Pin 1 is top right and the numbers increase going left in the top row to pin 5 top left. Pin 6 is bottom right and Pin 9 bottom left.
8.2.3. RJ-45F Connector
The RJ-45 jack follows standard Ethernet wiring conventions, but we’ve provided the pinout anyway in case you need it, in Table 7.
Table 7: RAD-Galaxy Ethernet Cable Adapter RJ-45F Connector Pinout.
8.2.4. Cable Signal Mapping
For easy reference, Table 8 shows the mapping of signals for the RAD-Galaxy Ethernet Cable Adapter, by pin order on the HD-26F that connects to the RAD-Galaxy. Note that DoIP Ethernet signals are not carried on that connector and so have been added at the bottom of the table.
Table 8: RAD-Galaxy Ethernet Cable Adapter Signal Mapping.
8.3. 6.3 neoVI FIRE 2 Ethernet Cable Adapter Connector Pinouts and Signal Mapping
This secondary cable usually sits between the RAD-Galaxy Ethernet Cable Adapter and conventional networks, and is described further in Section 2.4. Its HD-26F connector attaches to the HD-26M on the RAD-Galaxy Ethernet Cable Adapter, and thus has the same pinout as shown in Table 5. Below are the pinouts for the other connectors on this cable (DB-25M, DB- 9M and RJ-45F) as well as cable signal mapping table.
8.3.1. DB-25M Connector
The DB-25M connector has the pin assignments shown in Table 9, with pin numbering for the connector illustrated in Figure 82.
Table 9: neoVI FIRE 2 Ethernet Cable Adapter DB-25M Connector Pinout.
Figure 82: neoVI FIRE 2 Ethernet Cable Adapter DB-25M Connector with Pin Assignments.
8.3.2. DB-9M Connector
Table 10 shows the pin assignments for the DB-9M connector, with pin numbering illustrated in Figure 83.
Table 10: neoVI FIRE 2 Ethernet Cable Adapter DB-9M Connector Pinout.
Figure 83: neoVI FIRE 2 Ethernet Cable Adapter DB-9M Connector with Pin Assignments.
8.3.3. RJ-45F Connector
This is another standard Ethernet socket and uses the same pinout as that shown in Table 7.
8.4. neoVI-OBD-1 Cable Connector Pinouts and Signal Mapping
This OBD cable contains a DB-25 connector that mates to the DB-25 on the neoVI FIRE 2 Ethernet Cable Adapter and an OBD-II / J1962 connector for your vehicle or bench.
8.4.1. DB-25 Connector Pinout
Table 12 shows the pinout of the DB-25 connector on the neoVI-OBD-1 and signals when used with the RAD-Galaxy.
Table 12: neoVI-OBD-1 Cable DB-25 Connector Pinout.
8.4.2. OBD-II / J1962 Connector Pinout
Table 13 contains the standard pinout for the OBD-II / J1962 connector on this cable. Note that not all of the default signals are actually present when used with the RAD-Galaxy, such as J1850, but they are included for completeness.
Table 13: neoVI-OBD-1 Cable OBD-II / J1962 Connector Pinout. The table shows standard signals for the OBD-II connector; this includes protocols such as J1850 that are not supported by the RAD-Galaxy.
8.4.3. Cable Signal Mapping
Table 14 contains the mapping of signals for the neoVI-OBD-1 cable when used with the RADGalaxy. The signal names for both connectors are shown and the table is based on the OBD-II connector’s pin order. Note that signals on the OBD-II connector that are not used have been omitted from this table.
Table 14: neoVI-OBD-1 Cable Signal Mapping.
8.5. neoVI-OBD-MULTI (Regular and Right Angle) Cable Connector Pinouts and Signal Mapping
These two cables have the same pinouts and signal mappings, as they differ only in the physical construction of the OBD-II connector.
8.5.1. DB-25 Connector Pinout
Table 15 shows the pinout of the DB-25 connector on the neoVI-OBD-MULTI when used with the RAD-Galaxy.
Table 15: neoVI-OBD-MULTI Cable DB-25 Connector Pinout.
8.5.2. OBD-II / J1962 Connector Pinout
The pinout for the OBD-II / J1962 connector on this cable can be found in Table 16. All signals are again included for completeness but note that signals such as J1850 are not supported on the RAD-Galaxy.
Table 16: neoVI-OBD-MULTI Cable OBD-II / J1962 Connector Pinout. The table shows standard signals for the OBD-II connector; this includes J1850, which is not supported by the RAD-Galaxy.
8.5.3. Cable Signal Mapping
Table 17 contains the mapping of signals for the neoVI-OBD-MULTI regular and right angle cables. The signal names for both connectors are shown and the table is based on the OBD-II connector’s pin order. Note that signals on the OBD-II connector that are not used have been omitted from this table.
Table 17: neoVI-OBD-MULTI Cable Signal Mapping.
8.6. neoVI FIRE/RED J1939 Cable Connector Pinouts and Signal Mapping
This cable converts the neoVI DB-25 connector to a 9-pin Deutsch connector for use in commercial vehicles.
8.6.1. DB-25 Connector Pinout
Table 18 contains the pinout of the DB-25 connector when used with the RAD-Galaxy.
Table 18: neoVI FIRE/RED J1939 Cable DB-25 Connector Pinout.
8.6.2. Deutsch 9-Pin Connector Pinout
The pinout for the Deutsch connector on this cable is found in Table 19. All signals are again included for completeness but note that J1708 is not supported on the RAD-Galaxy.
Table 19: neoVI FIRE/RED J1939 Cable Deutsch 9-Pin Connector Pinout. The table shows standard signals for the Deutsch 9-pin connector; this includes J1708, which is not supported by the RAD-Galaxy.
8.6.3. Cable Signal Mapping
Table 20 contains the mapping of signals for the neoVI FIRE/RED J1939 cable. The signal names for both connectors are shown and the table is based on the Deutsch 9-pin connector’s pin order. Note that signals on the Deutsch 9-pin that are not used have been omitted from this table.
Table 20: neoVI FIRE/RED J1939 Cable Signal Mapping.
8.7. neoVI FIRE 2 OBD Cable with DoIP Support Connector Pinouts and Signal Mapping
This special OBD cable replaces the neoVI FIRE 2 Ethernet Cable Adapter and contains HD- 26, DB-25, DB-9 and OBD-II connectors. The HD-26 connector mates to the HD-26 on the RAD-Galaxy Ethernet Cable Adapter and uses the same pinout shown in Table 4; the other connectors are described below, along with a signal mapping table.
8.7.1. DB-25 Connector Pinout
Table 21 lists the pins of the DB-25 connector on this cable when used with the RAD-Galaxy. Note that the LIN channel pin does not need to be used for DoIP Ethernet Activate on this cable, though they are electrically connected.
Table 21: neoVI FIRE 2 OBD Cable with DoIP Support DB-25 Connector Pinout.
8.7.2. DB-9 Connector Pinout
Table 22 contains the pinout for the DB-9 connector. Note that the LIN channel pins do not need to be used for DoIP Ethernet Activate on this cable, though they are electrically connected.
Table 22: neoVI FIRE 2 OBD Cable with DoIP Support DB-9 Connector Pinout.
8.8. Signal Flow Map for Attachment of RAD-Galaxy Ethernet Cable Adapter and neoVI FIRE 2 Ethernet Cable Adapter
The RAD-Galaxy Ethernet Cable Adapter and neoVI FIRE 2 Ethernet Cable Adapter are both somewhat complex due to the number of connectors and signals they use. Table 10 is intended to help make the signal flow across these connectors easier to understand. It shows a full mapping of signals from the RAD-Galaxy’s CAN/MISC HD-26M connector when these two cables are attached. The color coding indicates the nature of the electrical connection (see legend that follows in Table 25).
Table 25: Signal Flow Map for Attachment of RAD-Galaxy Ethernet Cable Adapter and neoVI FIRE 2 Ethernet Cable Adapter.
Table 26: Signal Flow Map Color Legend
8.9. Signal Flow Map for Attachment of RAD-Galaxy Ethernet Cable Adapter and neoVI FIRE 2 OBD Cable with DoIP Support
Table 27 shows the signal flow map when the neoVI FIRE 2 OBD Cable with DoIP Support is used instead of the neoVI FIRE 2 Ethernet Cable Adapter.
Table 27: Signal Flow Map for Attachment of RAD-Galaxy Ethernet Cable Adapter and neoVI FIRE 2 OBD Cable with DoIP Support.