5. Hardware Setup

5.1. Hardware Hookup Diagrams

The hookup diagrams below show you at a glance how to physically connect your RAD-Galaxy to vehicle networks and your PC. There are three possible configurations depending on which OBD cable you are using, if any.

5.1.1. Basic Hardware Hookup Diagram (No OBD Cable)

Figure 44 illustrates the basic hookup of components for the RAD-Galaxy without an OBD cable. It shows the use of two fully-populated Nano MQS connectors for 100BASE-T1 (BroadR-Reach), the chained RAD-Galaxy Ethernet Cable Adapter and neoVI FIRE 2 Ethernet Cable Adapter, and two Ethernet cables connected for DoIP. We have shown the Nano MQS cable assemblies terminated with Molex Mini50 connectors, which are often used with 100BASE-T1; your cables may look different, depending on your application.

Note that the Ethernet Activation line for DoIP is shared with the LIN channel. It can be accessed through the DB-25M and DB-9M connectors on the neoVI FIRE 2 Ethernet Cable

Figure 44: RAD-Galaxy Basic Hookup Diagram.

5.1.2. OBD Hardware Hookup Diagram (neoVI-OBD-1 / neoVI-OBD-MULTI / neoVI-OBD-MULTI Right Angle / neoVI FIRE/RED J1939)

Figure 45 is the same as Figure 44 but with the addition of an OBD cable, which connects to the DB-25M connector of the neoVI FIRE 2 Ethernet Cable Adapter. Note that the appearance of the OBD cable may vary depending on what option you selected when ordering the RADGalaxy.

Again here, the Ethernet Activation line for DoIP is shared with the LIN channel. Since the DB-25M connector is used for the OBD cable, the signal can be accessed through the DB-9M connector on the neoVI FIRE 2 Ethernet Cable Adapter.

Figure 45: RAD-Galaxy Hookup Diagram with OBD (Most OBD Cables).

5.1.3. OBD Hardware Hookup Diagram (neoVI FIRE 2 OBD Cable with DoIP Support)

As mentioned earlier in the manual, when the neoVI FIRE 2 OBD Cable with DoIP Support is used it replaces the neoVI FIRE 2 Ethernet Cable Adapter. The result is as shown in Figure 46, which is the same as Figure 44 except that the RJ-45 socket and Ethernet cable have been replaced by an OBD-II connection that carries DoIP to the vehicle network. In this configuration the DoIP Ethernet Activation line is conveyed directly to the vehicle network through the OBD-II port.

Figure 46: RAD-Galaxy Hookup Diagram with OBD (neoVI FIRE 2 OBD Cable with DoIP Support).

5.1.4. Vehicle Network DoIP Ethernet Data Paths

A special path is used for the DoIP Ethernet connection on the RAD-Galaxy. It passes through the neoVI FIRE 2 Ethernet Cable Adapter (or neoVI FIRE 2 OBD Cable with DoIP Support if that is being used) and the RAD-Galaxy Ethernet Cable Adapter. However, data flows into and out of the RAD-Galaxy through its DAQ Ethernet port, rather than the CAN/MISC connector to which the RAD-Galaxy Ethernet Cable Adapter is attached.

Figure 47 shows the same basic hookup diagram from Figure 44 with the full DoIP Ethernet path highlighted in green, and Figure 48 shows the equivalent adaptation of Figure 46, applicable when using the neoVI FIRE 2 OBD Cable with DoIP Support.

As mentioned above, the Ethernet Activation line for DoIP is shared with the RAD-Galaxy’s LIN channel. It can be accessed through the DB-25M and DB-9M connectors on the neoVI FIRE 2 Ethernet Cable Adapter. When using the neoVI FIRE 2 OBD Cable with DoIP Support, the Ethernet Activation line goes through the OBD-II connector.

Figure 47: RAD-Galaxy Basic Hookup Diagram Showing Typical DoIP Ethernet Data Path.

Figure 48: RAD-Galaxy Basic Hookup Diagram Showing DoIP Ethernet Data Path (When Using neoVI FIRE 2 OBD Cable with DoIP Support).

5.2. Conventional Vehicle Network and Power Connections

Let’s start our hardware connections by attaching the conventional vehicle network cables to the RAD-Galaxy and our vehicle networks. This will also power up the device, since power input is provided via the HD-26M conventional vehicle network connector. Please follow these steps.

1. Attach the RAD-Galaxy Ethernet Cable Adapter to the RAD-Galaxy:

Attach the HD-26 female connector on the RAD-Galaxy Ethernet Cable Adapter to the HD-26 male connector on the RAD-Galaxy. Tighten the thumbscrews so the cable remains securely attached (Figure 49).

Figure 49: Connecting the RAD-Galaxy Ethernet Cable Adapter’s HD-26M Connector to the RAD-Galaxy.

2. Attach the neoVI FIRE 2 Ethernet Cable Adapter or neoVI FIRE 2 OBD Cable with DoIP Support to the RAD-Galaxy Ethernet Cable Adapter:

If using the neoVI FIRE 2 OBD Cable with DoIP Support, connect its HD-26F connector to the HD-26M of the cable you just connected in Step 1. Otherwise, connect the HD-26F of the neoVI FIRE 2 Ethernet Cable Adapter, as shown in Figure 50.

Figure 50: Connecting the neoVI FIRE 2 Ethernet Cable Adapter to the RAD-Galaxy Ethernet Cable Adapter.

3. (Optional) Attach the DB-25F Connector of the OBD Cable to the neoVI FIRE 2 Ethernet Cable Adapter:

If you are using an OBD cable other than the neoVI FIRE 2 OBD Cable with DoIP Support, attach its DB-25 connector to the mating connector on the neoVI FIRE 2 Ethernet Cable Adapter (which you connected in Step 2).

4. Attach the DB-25M or OBD-II Connector to the Vehicle Network:

If you attached an OBD cable in Step 2 or Step 3, connect its OBD-II connector to your vehicle network. If you are not using an OBD cable, instead attach the DB-25M of the neoVI FIRE 2 Ethernet Cable Adapter to your network.

5. (Optional) Attach DB-9 Connectors to Vehicle Network:

If necessary, connect the DB-9 connectors from the RAD-Galaxy Ethernet Cable Adapter and/or neoVI FIRE 2 Ethernet Cable Adapter to the appropriate mating connectors within your vehicle or bench network.

6. (Optional) Attach Ethernet Cables for DoIP: If using DoIP, you will need to follow these additional steps:

Connect one of the included standard Ethernet cables between the RJ-45 socket on the RAD-Galaxy Ethernet Cable Adapter and the DAQ RJ-45 port on the RADGalaxy (see Figure 9).

If you are using the neoVI FIRE 2 OBD Cable with DoIP Support, you are done. Otherwise, use the other Ethernet cable to link the RJ-45 socket of the neoVI FIRE 2 Ethernet Cable Adapter and the RJ-45 connection of your vehicle network. You will also need to make the appropriate connection for the Ethernet Activation line (found on the DB-25M and DB-9M of the neoVI FIRE 2 Ethernet Cable Adapter).

As soon as you connect the DB-25 or OBD-II connector, the RAD-Galaxy should power up. You will recognize this by seeing LEDs light up on the left side of the device (again, see Figure 9). If you see no activity after making the power connection, double-check your power supply, and if the problem persists, please see Chapter 6 for assistance.

5.3. 100BASE-T1 (BroadR-Reach) Network Connections

Now we will make the 100BASE-T1 (BroadR-Reach) connections between the RAD-Galaxy and our Automotive Ethernet network. Assuming that the correct cable assemblies have been made according to the instructions in Section 2.4, this is a straightforward process.

1. Attach Nano MQS Connectors to RAD-Galaxy:

Carefully slide the Nano MQS plugs of the cable assemblies you created into the matching sockets on the RAD-Galaxy (Figure 51). The connectors are keyed, and you should hear a slight click when the plug is correctly seated. Notice the release tab, which you will use if you want to remove the connector later on.

Figure 51: Connecting a Nano MQS Cable Plug to the RAD-Galaxy.

2. Connect 100BASE-T1 Cables to Vehicle Network:

Attach the terminated ends of the Nano MQS cable assemblies to your vehicle network. The exact means of doing this will depend on how the wires are terminated.

If you are planning to use the RAD-Galaxy as an active tap, remember to interpose the RADGalaxy connections between node and switch, or between two nodes, using matched pairs: 1+2, 3+4, 5+8, 7+6, 9+10 or 11+12. For example, if a node is connected to a switch port, then

if you attach BroadR-Reach channel 3 to the switch port, you should connect channel 4 to the node. For media converter operation, you can use any channel.

The RAD-Galaxy should now be fully connected to your vehicle or bench network.

5.4. PC Connection

Now we will connect the RAD-Galaxy to the PC. Since all data is conveyed over the same Ethernet link, this is actually very simple.

Note: The RAD-Galaxy was designed to be connected directly to a PC Ethernet port. Intrepid does not support using a conventional Ethernet switch between the RAD-Galaxy and the PC.

Since each of the RAD-Galaxy’s 12 Automotive Ethernet channels is capable of transporting up to 100 Mb/s of data bidirectionally, we strongly recommend using a PC with a Gigabit Ethernet controller. A 100 Mb/s Ethernet connection may be sufficient, however, for low-bandwidth applications.

1. Attach an Ethernet Cable to RAD-Galaxy:

Connect one end of a standard Ethernet cable to the RAD-Galaxy’s LAN port (Figure 52).

Figure 52: Connecting an Ethernet Cable to the RAD-Galaxy.

2. Attach the Ethernet Cable to the PC:

Attach the other end of the Ethernet cable to your PC’s Ethernet port.

If the supplied Ethernet cables are too short for your application, you can use a longer one, as long as it is certified for Gigabit Ethernet operation.