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.