Intrepid Control Systems neoVI FIRE 2 User manual

Intrepid Control Systems, Inc.
31601 Research Park Drive Madison Heights, MI 48071 USA
(ph) [phone] (fax) [phone]
www.intrepidcs.com www.aeta-rice.com
neoVI FIRE 2
Multi-Protocol Vehicle Network Interface
User’s Guide
Version 2.1 - October 10, 2016

neoVI FIRE 2 User’s Guide
i© 2016 Intrepid Control Systems, Inc.Version 2.1 - October 10, 2016
Version History
Version
Number Date Description / Major Changes
1.0 2016/01/06 Initial release.
2.0 2016/06/10
Revised package contents.
Added photos of FIRE 2 in box and accessories.
Removed mention of certain features that have not yet been implemented.
Added note on avoiding problems with third-party USB cables.
Rewrote section on included cables and options.
Added pictures of new cable options.
Added new images of cable connectors.
Updated software install screenshots.
Expanded hardware hookup diagram section
Revised existing hardware hookup diagram and added new ones for all OBD
cable options.
Rewrote instructions for cable connection to correspond to new cables.
Added many new pinout tables for new cables and connectors, and converted
section on cable pinouts to chapter due to size.
Added cable signal mapping tables to show signal correspondence between
connector pins on each cable.
Added contact information for international ICS oces.
2.1 2016/10/10
Corrected miscellaneous I/O hardware connections.
Corrected several pinout tables and claried that the neoVI FIRE 2 does not
support J1850 or J1708.
Updated contact information for international ICS oces.

neoVI FIRE 2 User’s Guide
ii © 2016 Intrepid Control Systems, Inc.Version 2.1 - October 10, 2016
Table of Contents
1 Introduction and Overview ..........................................................................................................................1
1.1 Introduction ................................................................................................................................................1
1.2 Package Contents......................................................................................................................................1
1.3 Operational Overview ................................................................................................................................4
1.4 Summary of Key Features .........................................................................................................................4
1.5 Hardware and Software Requirements......................................................................................................7
2 A Tour of neoVI FIRE2 Hardware...............................................................................................................8
2.1 Case and Overall Design ...........................................................................................................................8
2.2 Left Side Interfaces and Connectors........................................................................................................10
2.3 Right Side Interfaces and Connectors .....................................................................................................10
2.4 Membrane LED Display and Keypad.......................................................................................................12
2.5 Standard Cables and Cable Options .......................................................................................................15
3 Hardware and Software Setup .................................................................................................................23
3.1 Vehicle Spy and Driver Installation and Setup .........................................................................................23
3.2 Driver and API Support File Installation and Setup..................................................................................30
3.3 Hardware Hookup Diagrams....................................................................................................................36
3.4 Vehicle Network and Power Connections ................................................................................................39
3.5 PC Connection.........................................................................................................................................41
4 DeviceConguration .................................................................................................................................43
4.1 Starting and Using neoVI Explorer...........................................................................................................43
4.2 System Settings and Firmware Updates..................................................................................................46
4.3 General Settings and Product Details......................................................................................................48
4.4 Standard CAN Networks (HS CAN 1-5 and MS CAN).............................................................................50
4.5 Selectable CAN Networks........................................................................................................................52
4.6 LIN Networks (LIN1 to LIN4)....................................................................................................................54
4.7 MISC IO ...................................................................................................................................................55
4.8 Other Parameters ....................................................................................................................................56
5 Core Feature Operation ............................................................................................................................59
5.1 Monitoring Conventional Vehicle Networks..............................................................................................59
5.2 Transmitting on Conventional Vehicle Networks...................................................................................... 60
5.3 Interfacing to Automotive Ethernet (BroadR-Reach / 100BASE-T1)........................................................64
5.4 Using the Ethernet Interface for DoIP and XCP.......................................................................................65
5.5 Using Miscellaneous I/O Channels ..........................................................................................................65
5.6 Standalone Logging .................................................................................................................................65
5.7 CoreMini Scripting....................................................................................................................................65
6 Advanced Features....................................................................................................................................66
6.1 neoVI API .................................................................................................................................................66
6.2 USB Host .................................................................................................................................................66
7 Reference: Connector Pinouts and Cable Signal Mappings................................................................67
7.1 neoVI FIRE 2 Connector Pinouts.............................................................................................................67
7.2 FIRE 2 Ethernet Cable Adapter Connector Pinouts and Signal Mapping................................................69
7.3 neoVI-OBD-1 Cable Connector Pinouts and Signal Mapping..................................................................71
7.4 neoVI-OBD-MULTI (Regular and Right Angle) Cable Connector Pinouts and Signal Mapping............... 74
7.5 neoVI FIRE/RED J1939 Cable Connector Pinouts and Signal Mapping .................................................76
7.6 FIRE 2 OBD Cable with DoIP Support Connector Pinouts and Signal Mapping .....................................78

neoVI FIRE 2 User’s Guide
iii © 2016 Intrepid Control Systems, Inc.Version 2.1 - October 10, 2016
8 Support Contact Information.....................................................................................................................82
8.1 ICS United States Headquarters..............................................................................................................82
8.2 ICSInternationalOfces ..........................................................................................................................82

neoVI FIRE 2 User’s Guide
1© 2016 Intrepid Control Systems, Inc.Version 2.1 - October 10, 2016
1 Introduction and Overview
1.1 Introduction
Thank you for purchasing an Intrepid Control Systems neoVI FIRE 2 multi-network vehicle
network interface. The FIRE 2 is Intrepid’s fourth-generation general purpose interface tool,
providing access to multiple channels of CAN, LIN and other vehicle networks. The FIRE 2
can be used to monitor and transmit on networks, to create custom simulations for network
analysisandtroubleshooting,andforstandaloneloggingbasedonprecisespecications.
The FIRE 2 provides numerous evolutionary improvements over the very successful original
neoVI FIRE, including more CAN channels, greater performance, more robust case and
connectors, far larger script space, the ability to download data from the included SD card over
USB, and support for a wider input voltage range. It also adds new revolutionary features to
the world of vehicle networking tools, such as support for CAN FD, Automotive Ethernet and
DoIP, individual multi-color network activity LEDs, USB device hosting, and much more.
1.2 Package Contents
Your neoVI FIRE 2 package includes both hardware and software.
Hardware
You should receive the following:
• The neoVI FIRE 2 network interface device.
• A microSD card for data logging (already installed in the unit).
• A USB microSD card reader.
• An industry standard USB “A/B” cable to connect the FIRE 2 to a PC.
• A µDB-9 to DB-9 conversion cable.
• A FIRE 2 Ethernet Cable Adapter.
• YourchoiceofOBDcablefromamongveoptions(detailsareinSection 2.5).
You will also receive a “Getting Started” card to help you get going quickly with your device.
The FIRE 2 is packaged using a special cardboard insert with a plastic sheet molded over it
to hold it securely during shipment. Figure 1 shows how the device will appear in its box after
removing the “Getting Started” card.

neoVI FIRE 2 User’s Guide
2© 2016 Intrepid Control Systems, Inc.Version 2.1 - October 10, 2016
Figure 1: neoVI FIRE 2 in its Protective Insert.
Lift up the plastic sheet, remove the FIRE 2, and then fold back the cardboard upon which it
rested.Underneathyouwillndthecablesandotheraccessorieslistedabove.Pleaseremove,
unwrap and inspect all of the contents, an example of which is shown in Figure 2.
If anything is missing or damaged, please contact Intrepid for prompt assistance, using the
information in Chapter 8. Detailed instructions for attaching the cables to your hardware are
provided later in the document.
Note: While the USB cable in the FIRE 2 package uses industry
standard connectors and pinouts, not all USB cables are the
same. To ensure reliable operation, please use the cable included
with the FIRE 2. If you need to replace the original, be sure not to
use one longer than 6’ (2 m) or you may experience problems with
your hardware. If necessary, contact Intrepid for a replacement.

neoVI FIRE 2 User’s Guide
3© 2016 Intrepid Control Systems, Inc.Version 2.1 - October 10, 2016
Figure 2: neoVI FIRE 2 Package Contents. Starting top center with the FIRE 2 itself and going clockwise: µDB-9 to DB-9
conversion cable; USB cable; microSD card reader; FIRE 2 Ethernet Cable Adapter; neoVI-OBD-1 cable. The software/driver
CD can be found in the center. Note that the OBD cable you receive may differ from the one shown here.
Software
IntheFIRE2packageyouwillndasoftware/driverCDcontaining:
• A copy of Intrepid’s Vehicle Spy vehicle network software.
• Drivers for the neoVI FIRE 2.
• AnAPIinstallkitcontainingtheneoVIExplorerutilityforconguringthedevice.
• Documentation materials.
Intrepid’s Vehicle Spy (often abbreviated as VSpy) is the “Swiss army knife” of automotive
networking tools. It allows you to easily monitor and transmit on vehicle networks, and includes
capabilities for ECU simulation, data acquisition, scripting, diagnostics, data analysis and much
more.
The neoVI FIRE 2 and Vehicle Spy are designed to work together hand in hand, and we
recommend purchasing a VSpy license to go along with your new hardware. If you did so, then
a full copy of the software will be included on the software/driver CD. If you did not purchase

neoVI FIRE 2 User’s Guide
4© 2016 Intrepid Control Systems, Inc.Version 2.1 - October 10, 2016
Vehicle Spy, a trial version of the program will be provided instead, which allows access to
VSpy’s basic features.
It is also possible to control the neoVI FIRE 2 from within other software using one of the APIs
that the device supports.
1.3 Operational Overview
The neoVI FIRE 2 is a compact but powerful hardware tool for working with vehicle networks.
Its operation can broadly be broken down into three categories: network interfacing; data
acquisition and logging; and simulation and scripting.
Vehicle Network Interfacing
One primary function of the neoVI FIRE 2 is to act as an interface between vehicle networks
and a standard PC. Using the provided cables, you can connect the neoVI FIRE 2 to either
a bench test setup or an actual vehicle, and monitor live network activity. All channels are
captured simultaneously, and are hardware time-stamped with great accuracy. Data is
transferred by the neoVI FIRE 2 from attached networks over a USB connection, where it can
be viewed in software such as Vehicle Spy.
Data Acquisition and Standalone Logging
The FIRE 2 enables the acquisition of data from networks with precise control over collection
parameters. It is designed to operate not just when connected to a PC, but also in standalone
mode, running independently within a vehicle. You can write custom scripts that run in real
time, logging data to the included microSD card. This data can later be downloaded to the PC
for analysis, and this can be done conveniently over USB without the need to remove the card.
Simulation and Scripting
The neoVI FIRE 2 not only allows you to receive data from vehicle networks, but also to
transmitonthem.UsingVehicleSpyorothersoftwareyoucandenetransmitmessageswith
custom data and send them manually or on a schedule of your choosing. You can also write
intelligent scripts that implement arbitrary logic, and compile them into CoreMinis that run
within the device itself. This functionality allows you to create specialized test scenarios, and to
simulateECUsandgateways.ItisalsopossibletoreashECUsusingdatafromtheFIRE2’s
microSD card.
1.4 Summary of Key Features
WiththeneoVIFIRE2,we’vetalotofpowerandfunctionalityintoatoughlittlepackage.To
give you an idea of how much you can do with the FIRE 2, here’s a summary of the device’s
most important design, construction, operational and performance features.

neoVI FIRE 2 User’s Guide
5© 2016 Intrepid Control Systems, Inc.Version 2.1 - October 10, 2016
Construction, Controls and Cabling
• Compact design: 5.5” x 3.5” x 1.5” (14 x 9 x 4 cm).
• Light weight: less than 12 oz (340 g).
• Solid anodized aluminum case.
• Thick rubber end boots for shock protection.
• Ruggedized metal connectors.
• Cable interfaces on sides for easier connections.
• Multiple cable options for vehicle networks, including Ethernet, DoIP and OBD-II.
• Top membrane interface with network and logger status LEDs and two pushbuttons.
• Ability to control LEDs and pushbuttons in custom scripts.
Power and Performance
• Fourth-generation neoVI architecture, offering over ten times the performance of earlier
devices.
• Memoryupdatedto32MBandon-boardashto64MB,allowingmuchmorespacefor
scripting and buffering.
• Field-upgradeablermware.
• Support for 4.5V to 40V input power.
• Built-inve-seconduninterruptiblepowersupplytoensuregracefulshutdownonpower
loss.
• AbilitytoconguredeviceanddownloadSDcarddataonthedesktopusingonlyUSB
power.
• Lower power consumption than earlier generation devices.
Network Interfaces and Features
• 6 dedicated DW CAN channels (ISO 11898-2): 5 Dual Wire HS CAN, 1 Dual Wire MS
CAN.
• 2 selectable CAN channels: 2 additional Dual Wire HS CAN, or 2 Single Wire SW CAN,
or 2 Low Speed Fault Tolerant LSFT CAN (ISO 11898-3).
• All Dual Wire CAN channels have CAN FD support.
• Initial support for non-ISO CAN FD, with ISO CAN FD upgrade included when it is
available.

neoVI FIRE 2 User’s Guide
6© 2016 Intrepid Control Systems, Inc.Version 2.1 - October 10, 2016
• Software-programmable CAN termination.
• 4 LIN channels.
• 2MISCI/Ochannels,whichcanbeconguredasanalog/PWM.
• Software-congurableCANandLINchannelenables/disables,baudratesandother
parameters.
• 10/100 Ethernet with low power mode and activation line.
• Ethernet link usable for DoIP/XCP, or to connect to Automotive Ethernet (BroadR-Reach
/ 100BASE-T1) network through Intrepid RAD-Moon (sold separately).
• Real-time clock for 64-bit message timestamping.
Logging and Simulation
• Fully-programmable scripting and standalone logging functionality.
• SDcardloggingofalltrafc.
• Software-congurablesleepmode.
• Low power modes.
• Comatose support; device wakeup can be triggered by all 12 CAN transceivers, all 4
LIN channels, by USB or by the membrane keypad.
PC Interface and SD Card Support
• High-speed isolated USB connection protects PC from potential damage.
• Support for microSD cards up to 128 GB in size.
• Data can be unloaded from the microSD card via USB without the need to remove the
card, or via the included card reader.
• Download speeds of up to 3.2 MB/s.
• Firmware-based SD card presence and card door detector.
Advanced Features
• Device control by external software using three open APIs: neoVI DLL, SAE J2534, and
TMC RP1210 A/B.
• USB host slot for hardware expandability, such as powering a RAD-Moon or using a
neoVI MIC microphone/trigger pendant.

neoVI FIRE 2 User’s Guide
7© 2016 Intrepid Control Systems, Inc.Version 2.1 - October 10, 2016
1.5 Hardware and Software Requirements
Only a small amount of hardware is required to use the neoVI FIRE 2:
• A vehicle network, either within an actual vehicle or in a test bench environment.
• A DC power supply capable of providing 4.5V to 40V of DC power, with a nominal
current of 250 mA at 12V. Your network setup must include wiring capable of providing
this power on pin 25 of a female DB-25 connector that connects to a FIRE 2 cable; see
Chapter 7 for pinout details.
• A PC with an open standard USB 2.0 (or higher) port. You can use a USB hub, but we
recommendthatthisbeapoweredhubtoensurethatsufcientpowerisprovided.
Additional hardware may be required for some uses of the device:
• Interfacing to a BroadR-Reach (100BASE-T1) Automotive Ethernet network requires an
Intrepid RAD-Moon or similar media converter device.
• Additional cables may be needed, depending on the nature of the network to which the
neoVI FIRE 2 is being connected.
Intrepid’s Vehicle Spy Professional is recommended for use with the FIRE 2, and provides
everything you need to set up your hardware and use all of its capabilities. The setup program
for VSpy will also install the necessary drivers for your FIRE 2. If you do not have a VSpy
license, you can use the Vehicle Spy trial version for basic network interfacing and driver
setup. Drivers can also be set up using the API kit installer. All of this software can be found on
the disc that comes with the FIRE 2, or if necessary, can be downloaded from the Intrepid web
site at http://www.intrepidcs.com. Installation instructions can be found in Chapter 3.
PleaserefertotheVehicleSpydocumentationforitsmorespecicPChardwareandoperating
system requirements and recommendations. Note, however, that Vehicle Spy will run on most
modern Windows-based PCs.

neoVI FIRE 2 User’s Guide
8© 2016 Intrepid Control Systems, Inc.Version 2.1 - October 10, 2016
2 A Tour of neoVI FIRE2 Hardware
Let’s now take a short tour of the neoVI FIRE 2’s hardware. 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,congureanduseit.
Like many Intrepid products, the neoVI FIRE 2 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 neoVI FIRE 2 is a complex device that does not
contain any user-serviceable parts. Do not attempt to open the
caseoftheneoVIFIRE2unlessspecicallyinstructedtodosoby
an Intrepid Control Systems technician, or you risk possible injury
or damage to the unit.
2.1 Case and Overall Design
The neoVI FIRE 2 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 neoVI FIRE 2 can be seen in Figure 3.
Connectors and ports are often a point of failure with hardware devices. To ensure that the
neoVI FIRE 2 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 cyan-colored 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.

neoVI FIRE 2 User’s Guide
9© 2016 Intrepid Control Systems, Inc.Version 2.1 - October 10, 2016
Figure 3: Overview of the neoVI FIRE 2.
The bottom of the neoVI FIRE 2 contains useful reference information, including the device
serial number, pinouts of its HD-26 and µDB-9 connectors, and Intrepid’s contact information
(Figure 4). Pinouts for all FIRE 2 connectors and cables can be found in Chapter 7.
Figure 4: neoVI FIRE 2 Bottom View. Note that the FIRE 2’s miscellaneous I/O channels are “EMISC 1” and “EMISC 2”. (The
“MISC DIO 5” and “MISC DIO 6” entries will be removed in future FIRE 2 label printings.)

neoVI FIRE 2 User’s Guide
10 © 2016 Intrepid Control Systems, Inc.Version 2.1 - October 10, 2016
2.2 Left Side Interfaces and Connectors
The left side of the neoVI FIRE 2 contains two components: the HD-26 connector and a set of
red and green LEDs (Figure 5).
Figure 5: neoVI FIRE 2 Left Side View.
HD-26 Network Interface Connector
This male, high-density, 26-pin D-subminiature connector is the primary means by which
the neoVI FIRE 2 interfaces with vehicle networks. One of two network interface cables is
connected to this port, enabling CAN, LIN and Ethernet messages to be passed between the
network and the FIRE 2. This connector also provides primary power to the device.
Green and Red Status LEDs
You can determine the status of the neoVI FIRE 2 by observing the blink pattern of these two
LEDs. The patterns here will be identical to those seen in the keypad button LEDs on the
top membrane panel (explained in Section 2.4). The membrane LEDs will usually be more
convenient to use, but the traditional side panel LEDs have been preserved for those who are
accustomed to them from working with the original neoVI FIRE.
2.3 Right Side Interfaces and Connectors
This side of the neoVI FIRE 2 contains most of its connectors, ports and slots (Figure 6).

neoVI FIRE 2 User’s Guide
11 © 2016 Intrepid Control Systems, Inc.Version 2.1 - October 10, 2016
Figure 6: neoVI FIRE 2 Right Side View.
USB “B” Connector
This is the “square” connector for USB devices that use detachable cables. (The standard
“rectangular” connectors found on PCs are “A” connectors, which is why the cable supplied
with the neoVI FIRE 2 is often called a “USB A/B cable”.)
µDB-9 (Micro DB-9) Connector
This connector carries LIN and miscellaneous I/O signals to and from the FIRE 2. A micro DB-9
was used to allow the device to be made more compact; a provided cable converts from this
smaller connector to the standard DB-9 commonly used in the automotive industry.
USB Host Port
The USB “A” connector allows the FIRE 2 to act as a USB host, so other devices can plug into
it. Please see Section 6.2 for more details.
microSD Slot and Cover
This slot holds the microSD card that stores data logged or captured by the neoVI FIRE 2. It is
protected by a metal cover that prevents accidental ejection of the card and protects the slot
from dirt and debris.
You can download the contents of the installed microSD card over USB, or for larger data sets,
remove the card and use the provided external card reader.
Micro-SIM Slot and Cover
This slot can be used to hold a Micro-SIM card. Like the microSD card slot, it is covered with a
metal plate to protect it and the device.

neoVI FIRE 2 User’s Guide
12 © 2016 Intrepid Control Systems, Inc.Version 2.1 - October 10, 2016
2.4 Membrane LED Display and Keypad
One of the neoVI FIRE 2’s many improvements over the original neoVI FIRE is the addition of
a membrane LED display and keypad on top of the unit (Figure 7). The membrane contains 10
LEDs that provide immediate visual feedback about the status of the device, and two keypad
buttons that can be used to toggle the indicator mode and for other functions.
Figure 7: neoVI FIRE 2 Membrane LED Display and Keypad.
All of the LEDs and buttons are also scriptable: the buttons can be used for user input, and the
LEDs can be set to provide information from a CoreMini program running in the FIRE 2.
Keypad Buttons and LEDs
There are two keypad buttons on the neoVI FIRE 2’s top membrane: one with a blue computer
icon located near the top left, and one with a white car icon located near the bottom right.
Pressing either button toggles the meaning of the 8 RGB LEDs on the membrane as follows:
• Blue Button (Top Left): When pressed, activates the “blue set” of LED meanings: each
RGB LED shows the status of the network whose name appears in a blue label above
it. This set is active in the image in Figure 8.
• White Button (Bottom Right): When pressed, activates the “white set” of LED
meanings: each RGB LED shows information about a network or FIRE 2 function based
on the white icon or label below it.
ThebuttonsthemselvesalsocontainredandgreenLEDs,whichashinthesamepattern
as the red and green LEDs on the left side of the device (see Section 2.2). The illuminated

neoVI FIRE 2 User’s Guide
13 © 2016 Intrepid Control Systems, Inc.Version 2.1 - October 10, 2016
LEDs show which set of indicator meanings is active, and may also be more convenient for
monitoring general device status than the left-side LEDs.
The green and red status LEDs here, and on the side of the neoVI FIRE 2, show information
aboutitthroughanumberofashpatterns,whicharedescribedinTable 1.
Flash Pattern Description
Green LED ashing rapidly; red
LED off FIRE 2 is powered on but oine.
Green and red LEDs ashing
rapidly in alternating sequence
Device is powered and online with a PC running Vehicle Spy or
other software.
Red LED ashing rapidly; green
LED off FIRE 2 is running a CoreMini script.
Red LED ashing at constant rate;
green LED ashing intermittently
VehicleScape Standalone Logging is active; the ash rate of the
green LED reects the rate at which data is being logged.
Green LED ashes three times
slowly, red LED ashes once, then
cycle repeats
FIRE 2 is in bootloader mode. This normally occurs when new
rmware is being ashed to the device. See Section 4.2 for
more details.
Table 1: FIRE 2 Green/Red LED Flash Patterns.
Network/Logger Status RGB LEDs
The membrane contains 8 RGB (full color) LEDs in two rows of four. The meaning of each LED
changes depending on whether the upper left blue button has been pressed or the lower right
whitebutton,sothe8LEDsactuallyindicateatotalof16separatestatusconditions.Tond
the current meaning of each LED, check whether the white button or blue button has its LEDs
ashing,andthenrefertothelabelofthecorrespondingcolor(describedbelow).
Interpretation of RGB LED Colors
These are “RGB” LEDs because they contain separate red, green and blue elements. For
networks, each indicates a different aspect of the device’s overall status:
• Green: Device is transmitting messages on this channel.
• Blue: Device is receiving messages on this channel.
• Red: Device is detecting errors on this channel.
It is possible for more than one LED component to be lit, producing the following results:
• Green+Blue (Cyan): Device is transmitting and receiving on this channel.
• Green+Red (Yellow): Device is transmitting and detecting errors on this channel.
• Blue+Red (Magenta): Device is receiving and detecting errors on this channel.
• Green+Blue+Red (White): Device is transmitting, receiving and detecting errors on this
channel.

neoVI FIRE 2 User’s Guide
14 © 2016 Intrepid Control Systems, Inc.Version 2.1 - October 10, 2016
Figure 8 shows a photograph of the top membrane of a FIRE2 in active use, with the blue
setofstatusindicatorsactive,meaningthattransmissionsareoccurringonvechannelsand
errors on one.
As a further cue to network activity, the intensity of these LEDs is proportional to the amount of
trafconthecorrespondingnetwork.Slowertrafconanetworkwillcausethenetwork’sLED
toashmoredimly,whileheavytrafcwillcausetheLEDtobebrighter.Notethattheblink
rateremainsthesameregardlessoftrafclevel.
Figure 8: neoVI FIRE 2 Membrane LED Display and Keypad Showing Active LEDs. In this image, the blue set of LED
meanings is active, as indicated by the green LED being lit within the blue computer icon in the top left corner (this LED
alternates between green and red when the device is online). The other LEDs thus mean that the neoVI FIRE 2 is active and
transmittingontheHSCAN1,HSCAN2,MSCAN,HSCAN3andHSCAN4channels(inusetheseallashafewtimesper
second.)NotethattheLEDforHSCAN4isactuallyyellowish;itisashingbothabrightgreenandadimredtoindicateerrors
while transmitting on the HSCAN4 channel.
“Blue Set” LED Status Indicators
Table 2 lists the blue labels on the FIRE 2 membrane interface, and describes the meaning of
theLEDassociatedwitheachwhenthebluesetisselected(topleftkeypadbuttonashing).
The LEDs are listed from top to bottom, left to right, as seen looking at the membrane in its
usual orientation.

neoVI FIRE 2 User’s Guide
15 © 2016 Intrepid Control Systems, Inc.Version 2.1 - October 10, 2016
Label Description
HSCAN1 Transmit / receive / error status of HS CAN channel 1
HSCAN2 Transmit / receive / error status of HS CAN channel 2
MSCAN Transmit / receive / error status of MS CAN channel
HSCAN3 Transmit / receive / error status of HS CAN channel 3
HSCAN4 Transmit / receive / error status of HS CAN channel 4
DoIP Transmit / receive / error status of Ethernet channel
LINS Status of all LIN channels
CAN7
Transmit / receive / error status of HS CAN channel 6, SW
CAN channel 2, or LSFT CAN channel 1, depending on
CAN mode selected (see Section 4.5)
Table 2: FIRE 2 Top Membrane Blue Set LED Meanings.
“White Set” LED Status Indicators
Table 3 lists the white labels/icons on the FIRE 2 membrane interface, and describes the
meaning of the LEDs for each when the white set is selected (bottom right keypad button
ashing).AgaintheLEDsarelistedfromtoptobottom,lefttoright.
Label/Icon Description
CoreMini script active
Disk (solid state drive) activity
Data being uploaded
Logging a triggered collection
after the trigger condition has activated
GPS lock (using neoVI MIC2, available later in 2016)
General purpose, user-programmable
HSCAN5 Transmit / receive / error status of HS CAN channel 5
CAN8
Transmit / receive / error status of HS CAN channel 7, SW
CAN channel 1, or LSFT CAN channel 2, depending on
CAN mode selected (see Section 4.5)
Table 3: FIRE 2 Top Membrane White Set LED Meanings.
2.5 Standard Cables and Cable Options
As mentioned in Section 1.2, the FIRE 2 ships with several standard cables, as well as one of
veoptionalOBDcablesthatwasselectedwhenthedevicewasordered.We’llnowillustrate
these cables and describe each one’s use. Connector pinouts and cable signal tables for this
hardware can be found in Chapter 7 (except for the USB cable, which is industry standard).

neoVI FIRE 2 User’s Guide
16 © 2016 Intrepid Control Systems, Inc.Version 2.1 - October 10, 2016
USB “A/B” Cable
This is a standard cable is used to connect PCs or other hosts to USB devices that do not
have integrated cables (Figure 9). The detachable cable makes the FIRE 2 easier to transport
than would be the case if it were built in, and also allows the cable to be easily replaced if it is
ever damaged.
Figure 9: USB “A/B” Cable.
µDB-9 (Micro DB-9) to DB-9 Cable
As mentioned in Section 2.3, a µDB-9 connector was used on the FIRE 2 to allow it to be made
smaller. This is a “straight-through” cable that adapts the smaller connector to the regular DB-9
used in automotive applications. The cable can be seen in Figure 10, while a close-up of the
special µDB-9 connector is in Figure 11.