Intrepid Control Systems RAD-Galaxy User Manual page 25

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 RAD-
Galaxy 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 attach
an 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.
Version 1.2 - November 28, 2017
RAD-Galaxy User's Guide
21 © 2016 Intrepid Control Systems, Inc.