3. A Tour of RAD-Galaxy Hardware
Let’s now take a quick tour of the RAD-Galaxy. We’ll examine the device from all sides, showing its external components and explaining what each does. This will help you become more familiar with the unit so you can more easily set up, configure and use it.
Like many Intrepid products, the RAD-Galaxy is designed so that all of its connectors are located on its sides, making the device easier to use in cramped quarters. We’ll refer to these as the left side and right side of the unit, as oriented when facing the device with its top label text readable.
Warning
The RAD-Galaxy is a complex device that does not contain any user-serviceable parts. Do not attempt to open the case of the RAD-Galaxy unless specifically instructed to do so by an Intrepid Control Systems technician, or you risk possible injury or damage to the unit.
3.1. Case and Overall Design
The RAD-Galaxy is enclosed in a sturdy black-anodized metal case. The device has been designed and tested for in-vehicle use, and is operational in a temperature range from -40°C to +85°C. An overall view of the RAD-Galaxy can be seen in Figure 7.
Connectors and ports are often a point of failure with hardware devices. To ensure that the RAD-Galaxy provides you with years of reliable service, Intrepid has ruggedized the physical interfaces on the device by using reinforced metal connectors.
To further protect the device against bumps and drops, it has blue rubber bumpers on both ends. These bumpers are removable, but there is no need to do this under normal circumstances, and we recommend that you leave them in place.
Figure 7: Overview of the RAD-Galaxy.
The bottom of the RAD-Galaxy contains useful reference information, including the device serial number, pinouts of its HD-26 and Nano MQS BroadR-Reach connectors, and Intrepid’s contact information (Figure 8). Pinouts for all RAD-Galaxy connectors and cables can be found in Chapter 6.
Figure 8: RAD-Galaxy Bottom View Showing Connector Pinouts.
3.2. Device Connectors and Indicators
The left side of the RAD-Galaxy contains several components: a set of USB connectors, a pair of RJ-45 Ethernet jacks, two LED arrays and a covered slot for the device’s SD card (Figure 9).
Figure 9: RAD-Galaxy Left Side View.
3.2.1. 8-LED Status Indicator Array
These LED indicators (bottom left) are used to convey status information.
LEDs #1 and #2
One or both of the left two LEDs (which we will call #1 and #2) will always be flashing, with their pattern indicating the mode of the device. The interpretation of the LEDs depends on whether or not a CoreMini script (which may be a VehicleScape standalone logging script) is present in the device. Table 1 shows the possible combinations.
| LED #1 | LED #2 | CoreMini Present? | Description |
| Off | Off | – | RAD-Galaxy is powered off. |
| Off | Flashing | No | Device is offline (idle) with no CoreMini or standalone logging script active. |
| Flashing (Alternating) | No | Device is online (for monitoring traffic or transmitting messages in Vehicle Spy) with no CoreMini or standalone logging script active. | |
| Flashing | Off | Yes | A CoreMini script (including a possible VehicleScape logging script) is active, but logging is not taking place. |
| Flashing | Flashing | Yes | A VehicleScape logging script is running and actively logging data; the flash rate of LED #2 indicates how rapidly data is being logged. |
LED #3
This is the Trigger LED. When doing standalone logging with a CoreMini script, this LED will flash when a trigger event occurs.
LEDs #4-8
The other 5 LEDs currently have no preprogrammed function. However, they can be employed by CoreMini scripts to convey arbitrary information to the user of the RAD-Galaxy.
Bootloader Mode
You may occasionally see all 8 LEDs flashing synchronously. This means the device is in bootloader mode, which should only happen when flashing the RAD-Galaxy’s firmware (see 4.2).
3.2.2. 12-LED 100BASE-T1 (BroadR-Reach) Link/Activity LED Array
On the right is a set of 12 green LEDs arranged in a 4x3 matrix and labeled from 1 to 12. Each LED lights up solid to indicate that the corresponding 100BASE-T1 channel in the RAD-Galaxy has made a connection to another node. While a connection is active the LED will flash, with the flash speed proportional to the rate at which data is being transferred.
3.2.3. Device Connectors
USB Connectors
These connectors are currently reserved for internal and future use.
RJ-45 Jacks
The lower jack, with the label “LAN”, is the main link over which traffic flows between the RADGalaxy and the PC to which it is connected. The upper jack is used for DoIP. Both sockets have activity LEDs that will flash when traffic is being sent or received by the RAD-Galaxy.
SD Card Slot and Cover
At the bottom right is an L-shaped metal cover secured by a Phillips-head screw. Removing the cover allows the preinstalled SD card to be removed or replaced.
3.3. Network Connectors
This side of the RAD-Galaxy contains its vehicle network interface connectors (Figure 10).
Figure 10: RAD-Galaxy Right Side View.
3.3.1. BroadR-Reach Nano MQS Connector Sockets
These two sockets are where the cables that connect to Automotive Ethernet networks are attached after they are assembled from the included Nano MQS socket plugs and crimp contacts.
Each connector interfaces 3 pairs (6 channels) of Automotive Ethernet to the RAD-Galaxy. The channels and pairs are distributed as follows:
- Connector 1: Pair 1 (Channels 1+2), Pair 4 (Channels 6+7), Pair 6 (Channels 11+12).
- Connector 2: Pair 2 (Channels 3+4), Pair 3 (Channels 5+8), Pair 5 (Channels 9+10).
3.3.2. HD-26 Conventional Network Interface Connector (CAN/MISC)
This male, high-density, 26-pin D-subminiature connector is the primary means by which the RAD-Galaxy interfaces with conventional vehicle networks, and also may provide the mechanism for its DoIP functionality. This connector provides primary power to the unit as well.
The pinout of this connector can be found Table 5.
AIN 1/AIN 2 - Differential Analog Input
The RAD-Galaxy measures the differential voltage between AIN1 (upper voltage) and AIN2 (lower voltage). If a differential measurement is not needed, AIN2 must be grounded for proper operation. This input is mutually exclusive with the PWMIO.
| AIN 1 (Differential +) | 0V - 40V |
| AIN 2 (Differential -) | 0V - (<AIN1) |
| Resolution | 24.4 mV |
| Sampling Rate | ~1kHz |
| Supported Vehicle Spy Function Block Operations | GetVal Analog Input Value |
Warning
Under all circumstances, AIN2 must be at a lower voltage than AIN1. Failing to meet this requirements will result in malfunction and possibly permanent damage to the RAD-Galaxy.
AOUT 1: Analog Output
RAD-Galaxy has a single analog output with the following specifications.
| Output Voltage Range | 0-5V |
| Output Resolution | 1.22 mV |
| Max Output Current | 30mA |
| Slew Rate | 1.8V/µS |
| Supported Vehicle Spy Function Block Operations | SetVal Analog Output Value |
| GetVal Analog Output Value |
PWMIO: PWM Input
The RAD-Galaxy has 2 PWM Inputs with the following specifications. These inputs are mutually exclusive with the Analog Input and PWM Outputs.
| Logic Threshold | ~3.3V |
| Max Frequency | 5 kHz |
| Frequency Resolution | 0.1 Hz |
| Duty Cycle Resolution | 0.10% |
| Supported Vehicle Spy Function Block Operations | Set PWM Output Value |
| Set PWM Output Frequency | |
| Set PWM Output Duty Cycle | |
| Get PWM Output Value | |
| Get PWM Output Frequency | |
| Get PWM Output Duty Cycle | |
| Get PWM Output Period | |
| Set IO “state” | |
| Set IO “output/direction” |
PWM Outputs
The RAD-Galaxy has 2 PWM Outputs with the following specifications. These inputs are mutually exclusive with the Analog Input and PWM Inputs.
| V High (min) | TBD |
| Max Current | TBD |
| Max Frequency | 5 kHz |
| Duty Cycle Resolution | 0.1 Hz |
| Supported Vehicle Spy Function Block Operations | Set PWM Output Value |
| Set PWM Output Frequency | |
| Set PWM Output Duty Cycle | |
| Get PWM Output Value | |
| Get PWM Output Frequency | |
| Get PWM Output Duty Cycle | |
| Get PWM Output Period | |
| Set IO “state” | |
| Set IO “output/direction” |
3.4. Included Cables and Cable Assembly
The RAD-Galaxy ships with three cables for conventional vehicle networks, and the special components necessary to make the cable assemblies used for Automotive Ethernet networks. Depending on your vehicle network configuration, you may need to modify the included hardware, or supplement it to suit your needs.
This section briefly describes each of the cables and how they are used. More detailed instructions for hooking up the RAD-Galaxy, including these cables, is provided in Chapter 3. Full pinouts for all RAD-Galaxy connectors and cable connectors can be found in Chapter 6.
3.4.1. RAD-Galaxy Ethernet Cable Adapter (HD-26F to HD-26M + DB-9F + RJ-45F)
This is the RAD-Galaxy’s primary breakout cable for conventional vehicle networks, and can be seen in Figure 11. It attaches to the male CAN/MISC HD-26M connector seen in Figure 10. The three connectors on the other end of the cable are used as follows:
- HD-26M: This connector is a conduit for attaching the neoVI FIRE 2 Ethernet Cable Adapter described below (and sometimes the neoVI FIRE 2 OBD Cable with DoIP Support).
- DB-9F: This connector carries the RAD-Galaxy’s LIN traffic along with its miscellaneous I/O channels (coming soon). The LIN channel may also be used for Ethernet Activate for DoIP.
- RJ-45F: This Ethernet socket is used to attach a standard Ethernet cable that loops back to the RAD-Galaxy’s DAQ port for use with DoIP. Note that even though this cable connects to the RAD-Galaxy’s HD-26M connector, these Ethernet signals do not go through it; this is discussed further in Section 3.3.
DC input power is provided to the RAD-Galaxy through this cable, carried on pin 19 of the HD-26F and HD-26M connectors.
Figure 11: RAD-Galaxy Ethernet Cable Adapter (HD-26F to HD-26M + DB-9F + RJ-45F).
3.4.2. neoVI FIRE 2 Ethernet Cable Adapter (HD-26F to DB-25M + DB-9M + RJ-45F)
This secondary cable (Figure 12) attaches to the primary cable to make it easy to link the RADGalaxy to a vehicle network and provide power to it. As the name suggests, this cable is also used on Intrepid’s neoVI FIRE 2 vehicle interface product; the RAD-Galaxy was designed to be compatible with it.
This cable also facilitates the connection of four of the conventional OBD-II cables and provides a conventional Ethernet link for DoIP using an RJ-45 connection. When the neoVI FIRE 2 OBD Cable with DoIP Support is used, that cable replaces this one rather than attaching to it, allowing DoIP through the OBD-II connector instead of RJ-45. (See below for details on the OBD cable options for the RAD-Galaxy.)
The HD-26F connector on this cable attaches to the HD-26M on the RAD-Galaxy Cable Adapter. The other three connectors are used as follows:
- DB-25M: The primary connection to conventional (non-Ethernet) vehicle networks, and the source of DC power to the RAD-Galaxy. This connector can also be used to attachan OBD-II cable if needed.
- DB-9M: This connector contains the RAD-Galaxy’s LIN channel (coming soon). Note that it is not wired with miscellaneous I/O channels like the DB-9F on the RAD-Galaxy Cable Adapter. The LIN channel may also be used as an Ethernet activation line for DoIP.
- RJ-45F: Used to connect to an Ethernet port on the vehicle network, typically for DoIP. As mentioned above, the signals here are routed to the RJ-45F on the RAD-Galaxy Cable Adapter when the two cables are connected together.
DC power must be provided on pin 25 of the DB-25M connector for the RAD-Galaxy to function. See Chapter 6 for more details.
Figure 12: neoVI FIRE 2 Ethernet Cable Adapter (HD-26F to DB-25M + DB-9M + RJ-45F).
3.4.3. OBD Cables
The RAD-Galaxy comes with your choice of one of five OBD cables, which can be used to interface the device to a vehicle or bench OBD-II port. Four of these cables attach to the DB-25 connector on the neoVI FIRE 2 Ethernet Cable Adapter, while the fifth actually takes the place of that cable, connecting directly to the RAD-Galaxy. Section 3.3 contains hookup diagrams that show you how these cables fit together, as well as step-by-step instructions for connecting them to the RAD-Galaxy and your vehicle or bench. neoVI-OBD-1 Cable This cable, which has a red OBD-II connector, is used primarily for General Motors vehicles. It can be seen in Figure 13.
Figure 13: neoVI-OBD-1 Cable.
3.4.4. neoVI-OBD-MULTI Cable
This cable has a standard black OBD-II connector and is suitable for use with the vehicles of most OEMs. It is pictured in Figure 14.
Figure 14: neoVI-OBD-MULTI Cable.
3.4.5. neoVI-OBD-MULTI Right Angle Cable
This is the same as the neoVI-OBD-MULTI cable but terminates with a right-angled OBD II connector for vehicles where this is required. A picture of the cable is shown in Figure 15.
Figure 15: neoVI-OBD-MULTI Right Angle Cable.
3.4.6. neoVI FIRE/RED J1939 Cable
This cable terminates in a round 9-pin Deutsch connector for use in commercial vehicles (Figure 16).
Figure 16: neoVI FIRE/RED J1939 Cable.
3.4.7. neoVI FIRE 2 OBD Cable with DoIP Support
This special cable attaches to the HD-26M connector on the RAD-Galaxy Ethernet Cable Adapter in place of the regular neoVI FIRE 2 Ethernet Cable Adapter. It contains DB-25M and DB-9 connectors for connection to vehicle networks, like the cable it replaces, but instead of an RJ-45 socket, has an OBD-II connector wired for DoIP use (including an Ethernet Activation line). It is illustrated in Figure 17.
Figure 17: FIRE 2 OBD Cable with DoIP Support.
3.4.8. Automotive Ethernet (100BASE-T1 / BroadR-Reach) Cable Assemblies
Specific cables for Automotive Ethernet are not included with the RAD-Galaxy for two reasons. First, Automotive Ethernet does not specify an industry-standard cable and connector type. Second, termination and connector requirements vary from one application to another, so it makes sense for each company to create the cables/harnesses needed for its own networks.
To support its 12 100BASE-T1 connections, the RAD-Galaxy uses a pair of 20-pin Nano MQS style connector sets made by TE Connectivity, which are designed for vehicle use. The part number of the male connector within the RAD-Galaxy is 2177367-3, while the matching female plugs (supplied) are TE Connectivity part number 2177588-1. The crimp contacts that fit into the plugs are TE part number 2-2112449-1; 28 of these are provided with the RAD-Galaxy (the 24 required for the 12 channels, plus 4 spares).
You will need to create two cable assemblies for the 100BASE-T1 connections using the supplied plugs and contacts. To secure the contacts within the plug, you will need a special Nano MQS crimping tool, TE Connectivity part number 4-1579014-0. This device can be purchased from various electronic component suppliers or directly from Intrepid Control Systems. Each of the two cable assemblies will have 12 connections for 6 AE channels, with the contacts arranged according to the pinout on the bottom of the RAD-Galaxy. This information is also provided for your convenience in Chapter 6. An example of an assembled Nano MQS plug with attached cables can be seen in Figure 18.
The other ends of the 12 wires coming from each of the Nano MQS plugs should be terminated according to the needs of your vehicle network or bench application.
Be sure to label each of the wires and/or termination connectors with the appropriate RADGalaxy 100BASE-T1 channel number. This will allow you to easily link the connectors to the correct devices in your network.
Figure 18: Nano MQS Plug with Attached Cables.
3.4.9. Ethernet Cables
Two standard Ethernet cables are provided to connect the RAD-Galaxy to the PC and to the DoIP jack on the RAD Galaxy Ethernet Cable Adapter. You will need to provide a third Ethernet cable of the appropriate length to connect to your vehicle or bench for DoIP use, if required by your application.