6. The neoVI Explorer Configuration Utility

6.1. Starting and Using neoVI Explorer

This section will describe general features and the basics of using neoVI Explorer. It is the utility is used to connect to, manage and configure all of Intrepid Control Systems hardware. It is an integral part of Vehicle Spy, but for those not using Vehicle Spy software, it is also available as a stand alone application in the free ICS Hardware Installation kit

6.1.1. Starting neoVI Explorer from within Vehicle Spy

There are several ways to open neoVI Explorer from within VSpy. These are probably the two easiest, since they are accessible at all times:

Menu Item: Click the Setup menu and then select Hardware.
Hardware Setup Button: Click the button located in the main Vehicle Spy toolbar just under its menu (Figure below).

Note

neoVI Explorer cannot be launched when Vehicle Spy is online (even if in simulation mode). Attempting to do so, VSpy will display a prompt to either go offline and launch neoVI Explorer, or remain online and return to Vehicle Spy.

6.1.2. Starting neoVI Explorer as a Standalone Program

It is also possible to launch neoVI Explorer directly without opening Vehicle Spy. Open the Start Menu, navigate to the IntrepidCS folder, then under the Vehicle Spy 3 sub-folder, select neoVI Explorer (Figure below).

6.1.3. Starting neoVI Explorer as a Standalone Program

If the ICS Hardware Installation kit has been installed instead of Vehicle Spy, neoVI Explorer can be run from the Start Menu using the same basic process as described above. The only difference is the name of the sub-folder. The location of neoVI Explorer within the folder hierarchy can be seen in the figure below.

6.2. Interfacing with a device

6.2.1. Connecting to a device

When neoVI Explorer loads, it will start up with the first hardware device it can find selected in the menu pane on the left. Any connected devices should be listed here, along with its serial number. If a particular device is connected, but not seen among a list of other Intrepid devices, be sure to scroll down to look for it. If it is still not visible, this means its drivers have not been installed correctly, it is not powered properly, or there is a problem with the connection to the host computer.

To manage a device, click on its entry in the navigation pane (if it is not already highlighted) and then press the Connect button. After successfully connecting to the device, a “thumbs up” icon will be displayed next to the device’s name, and checkmarks will appear next to currently-enabled networks in the explorer area on the left. A message in the message box on the right will also read “<Your Device and Serial Number> settings have been read”. This indicates that neoVI Explorer has loaded the current settings from the unit.

The screen as a whole should appear similar to the screen shown below (but note that the device and version number shown below may be different).

_images/nVE_Screen.png — *Note that this screen varies in content between Intrepid devices.*

Searching for Devices

After attaching new hardware to a PC and starting neoVI Explorer, press the Search For Devices button at the bottom left of the dialog box to prompt the program to scan for new hardware to be managed.

Note

It is possible to click on various parameter groups at any time, but they will not show valid data until connected to the device. Remember also to connect to the device before making changes; Any changes made in neoVI Explorer with no device connected will be overwritten by a devices settings when it is connected.

6.2.2. Device Configuration

Writing and Reloading Settings

To avoid potential problems, neoVI Explorer will not save any changes to device parameters until instructed it to do so. This is done by pressing the Write Settings button, which will update the parameters within the firmware in the device. If unwanted changes were made, pressing the Read Settings button will reload the settings stored in the device, wiping out any modifications made in neoVI Explorer that had not yet been saved.

Reloading Device Defaults

To return all settings to factory defaults, press the Load Default Settings button. Note that pressing this button actually writes the defaults to the device first, and then reloads them automatically, so it is not necessary to also press Write Settings. The message area will display that defaults have been sent to the device and then read from it.

Disconnecting from the device

Press the Disconnect button to tell neoVI Explorer disconnect the device. This step is actually optional, because neoVI Explorer will disconnect from any connected devices when the program is closed.

Exiting neoVI Explorer

Like any Windows program, neoVI Explorer can be closed by clicking the “X” in the top right corner, or pressing the Alt+F4 key combination.

6.3. System Settings and Firmware Updates

The top two entries in the explorer window on the left side of neoVI Explorer contain system- wide settings that apply to all hardware devices, and information related to firmware updates.

6.3.1. System Settings

In the top branch of the tree in the left pane of neoVI Explorer there are several settings that can be enabled or disabled:

Enable Server: Turns on the neoVI Server feature, a background program that allows the hardware to be used by multiple applications at the same time.
Enable Low Latency: This is an advanced setting for applications where fast response is needed after transmission.
Enable Auto Update: When enabled, both neoVI Explorer and Vehicle Spy will automatically update firmware. If this box is not checked, firmware must be updated manually. (See below for details.)
Network Adapter Server: This is a feature that is used with Intrepid products having Ethernet ports. (It may not apply to your device.) With This feature enabled, the Ethernet ports on Intrepid hardware will enumerate as network interfaces in the operating system of the host computer. This server can be started and stopped in this window. There is also a checkbox to configure the server to start after booting of the computer.

6.3.2. Available Firmware

This is an informational page that shows which firmware versions are available in this version of neoVI Explorer for various Intrepid products. Note that some devices have multiple firmware programs that control different aspects of their operation;

6.3.3. Automatic and Manual Firmware Updates

Warning

While a device may appear to operate with incompatible firmware, proper and reliable operation cannot be guaranteed unless the version of firmware matches what is listed in Vehicle Spy

Firmware is essentially software that runs inside hardware and is required to enable the many capabilities of a device. New versions of firmware are created regularly by Intrepid’s engineers to implement new features and correct problems that have been identified.

Enable Auto Update is on by default and is recommended for most users. Each time a device connects neoVI Explorer or Vehicle Spy, the firmware will be checked, and if a newer version is available, the device will immediately be updated. If automatic updates is not enabled, it can be updated manually as needed. When new firmware is available, a red notification will be displayed on the initial connection screen, as shown below. Simply press the Manual Reflash button to update the firmware.

_images/Automatic-and-Manual-Firmware-Updates.png — *Note that this screen varies in content between Intrepid devices.*

6.3.4. The Firmware Update Process

During the firmware update process, the device will be placed into bootloader mode, indicated by all LEDs on the top label flashing synchronously. Normal LED flash patterns will resume when the update is complete and the device reboots. The progress of the firmware update operation is displayed in a dialog box as shown below. A message box on the right side of neoVI Explorer will also be displayed as the firmware program is sent to the device. When the process is complete the dialog box will disappear and another message will appear in neoVI Explorer to confirm that the update has finished. If any error messages are displayed or any other problems experienced updating the device’s firmware, please contact Customer Support for assistance.

Warning

Please take heed of the warning on the firmware update dialog box: leave the device connected and powered on for the entire firmware update process to avoid possible problems with the device.

6.4. General Settings and Product Details

These two areas of the device’s parameter setup provide information about the device and can be used to perform a few basic maintenance tasks.

6.4.1. General Settings

After connecting to the device, basic information about it will be displayed in the right-hand pane of the window:

The device’s serial number.
The firmware versions currently in the device, and an indication if new firmware is available.
A message showing that the hardware license for the device was recognized.
A current readout of the device’s real-time clock.

This information can be displayed again at any time by clicking the device’s name in the explorer navigation window, or the General Settings entry immediately below it.

The version(s) of the firmware for the device will be shown in black if it matches the firmware version within neoVI Explorer. If not, the current version and the newest available version will be shown in red to highlight that an update is available. (See the previous section for more about the update process.)

There are three buttons on this screen.

Manual Reflash (described in the previous section)
Read RTC button will reload the device’s internal time clock
Synchronize RTC will set the device’s clock to the same value as that of the PC.

6.4.2. Product Details

This is an informational area that provides technical data on the devices’s hardware and internal setup. This is generally only needed this if requested by Intrepid in order to facilitate support or troubleshooting. The Copy To Clipboard button can be used to copy all of the information to the Windows Clipboard to be pasted into an email or file.

6.5. CAN Network Settings

6.5.1. CAN Networks

This area of neoVI Explorer is used to enable, disable and configure the High Speed CAN channels. Each channel has an entry under the “CAN” group (which cannot be clicked itself). The current status of each channel is shown next to its name; a green checkmark indicates that the channel is enabled, while a red X means it is disabled. The figure below shows an example of the CAN channels area, with HS CAN enabled and HS CAN2 disabled.

All of the CAN channels have the same parameters, which can be configured using the controls in the right-hand pane; the default settings are shown below.

Enabled: Place a checkmark in this box to enable the channel, or clear the checkmark to disable it. When disabled, all of the other parameter controls are disabled (grayed out).

Specify by Baud: This is a master control that determines whether the operation of the channel is controlled by a numeric baud rate, or is calculated from lower-level timing parameters. When checked, the Baud Rate and CAN FD Baud Rate drop-down boxes are enabled and the various TQ, Sync and BRP-1 entries are disabled. When unchecked, this is reversed. Specifying by baud rate is the default, and is recommended except for advanced users with special requirements.

Baud Rate: When Specify by Baud is selected, choose a baud rate for the channel from the drop-down box below. The default value is 500000.

CAN Timing Settings: When Specify by Baud is deselected, the operation of the CAN channel is based on these five settings: TQ SEG1, TQ SEG2, TQ Prop, Sync, BRP-1. These settings are for advanced users and normally should be left at their default values.

CAN FD Baud Rate: When Specify by Baud is selected, choose a baud rate for the data phase of CAN FD messages. The default value is 2000000.

CAN FD Timing Settings: When Specify by Baud is deselected, use these settings (TQ SEG1, TQ SEG2, TQ Prop, Sync, BRP-1) for the data phase of CAN FD messages. These parameters are for advanced users and normally should be left at their default values.

Mode: The operating mode of the channel; choose from one of these four options:

Normal: Normal operation (default).
Disable: Channel is disabled.
Listen Only: This channel only receives messages, with no transmissions, and also no error frames generated nor acknowledgments sent.

Bit Rate Calculator: Press this button to launch the Intrepid Bit Timing Calculator.

6.5.2. ISO15765-2:

This page contains one setting: IFS Shift Register (shown below). Changing this from its default value of 0 causes time to be added to the Inner Frame Spacing of USDT frames transmitted by CoreMini scripts running in the FIRE 2. The number entered is multiplied by 6.4 µs to determine the time offset. The allowed range is -1563 to 1563.

6.6. Ethernet Port Configurations

With 3 different versions of Ethernet physical media on the RAD-Comet, it can be configured in several ways depending on the type of development or test required. This radio buttons on this screen configure how the ports are connected and used internally.

Following is a description of each configuration.

6.6.1. Independent Ports

In this mode, all 4 ports can be used independently to transmit and receive messages using VSPY or Intrepid’s open source APIs.

6.6.2. Ethernet Tap Modes

The RAD-Comet can be a bridge between 2 different Ethernet physical media. From that perspective it might be considered a media converter. The RAD-Comet can also it can mirror all the received traffic to a host computer or data logger, as well as inject traffic on any link. With these features, it can also be described as an Active Tap between the networks.

Vehicle Spy use with Active Taps:

Most use cases of Vehicle Spy display every message that is sent or received on a given network. In the case of active taps, the TX messages that are sent as a result of the active tap function are suppressed. (all TX messages from scripting or user interaction remain visible) The TX messages generated as part of the tapping function can be displayed by checking the box “Show TX Messages”.

T/T1S Tap (10/100/1000BASE-T <-> 10BASE-T1S)

In the following configuration, a standard Ethernet device (BASE-T) can be connected to a 10BASE-T1S device. Traffic passes freely between ETH01 and AE03 and is also mirrored to the PC along with precision timestamp information. The PC can also inject traffic on either of these ports. AE01 and AE02 can be used independently by the PC to send and receive Ethernet frames.

Store-and-Forward Operation

Similar to Ethernet switches, the RAD-Comet is a “store-and-forward” device. This means that a frame must ingress completely before it is forwarded out another port. This introduces a latency that varies based on the frame size, but it is unavoidable. In the case of the switch, it is required to confirm there is no data corruption before forwarding the frame. In the case of RAD-Comet, “cut-through” forwarding is not possible due to the 10BASE-T1S PLCA, where frames are sent on a schedule. Any frames received by RAD-Comet on other networks are asynchronous to the PLCA Transmit Opportunities and therefore must be buffered.

T1/T1S Tap (100BASE-T1 <-> 10BASE-T1S)

In the following configuration, a 100BASE-T1 device can be connected to a 10BASE-T1S device. Traffic passes freely between AE01 and AE02 and is also mirrored to the PC along with precision timestamp information. The PC can also inject traffic on either of these ports. ETH01 and AE03 can be used independently by the PC to send and receive Ethernet frames.

T1/T Tap (100BASE-T1 <-> 100/1000BASE-T)

With the RAD-Comet having both 100/1000BASE-T and 100BASE-T1 ports, it is only logical that we offer a configuration with them in a media converter configuration. Note that when bridging between 100BASE-T1 and 1000BASE-T, there is some buffering of messages, but frames may be lost if bursts of 1000BASE-T traffic exceed 100Mbps for a significant period of time.

6.7. PHY Configurations

6.7.1. 100BASE-T1 PHY Configuration (AE01)

From this screen the 88Q1010 100BASE-T1 PHY can be configured

Enabled

Each port can be independently enabled/disabled.

Link Speed & Duplex

The speed is fixed at 100Mbps, Full Duplex.

Link mode

The setting is related to the master or slave of the link to another PHY. This can also be configured to automatically determine if the PHY should be master or slave to establish a link with another PHY.

Enable TCP/IP

This must be enabled and configured for any applications using TCP/IP in the coremini scripts running on embedded processor of the RAD-Comet. This does not need to be enabled to use TCP/IP in VSPY.

6.7.2. 10BASE-T1S PHY Configuration (AE02)

From this screen the 10BASE-T1S PHY and PLCA can be configured

Enabled

Each port can be independently enabled/disabled.

Link Speed & Duplex

The speed is fixed at 10Mbps, Half Duplex.

Enable PLCA

This enabled PLCA for the PHY. When disabled, the PHY will operate in CSMA mode.

Enable Termination

For 10BASE-T1S, termination is required on

Local ID

Max Nodes

TX Opp Timer

Max Burst

Burst Timer

6.7.3. 10/100/1000BASE-T PHY Configuration (ETH01)

Enabled

Each port can be independently enabled/disabled.

Link Speed and Duplex

The speed and duplex of the port can be set to one of the following

Speed	Duplex
10Mbps	Full
10Mbps	Half
100Mbps	Full
100Mbps	Half
1000Mbps	Full
Auto Negotiation

Enable TCP/IP

This must be enabled and configured for any applications using TCP/IP in the coremini scripts running on embedded processor of the RAD-Comet. This does not need to be enabled to use TCP/IP in VSPY.

6.8. gPTP Time Synchronization

This device supports Generalized Precision Time Protocol as defined in IEEE 802.1AS. It can be configured to use the Standard profile or the Automotive profile as defined by the Avnu Alliance.

Note

Since this device is not a switch, only a single port may be enabled to support gPTP. This port may serve as a Grandmaster or as a clock slave to sync the device clock to a Grandmaster.

Typically the timestamp Physical Hardware Clock (PHC) of your device is synchronized with a host computer when connected. In cases where it is desireable for this clock to be synchronized with another clock source, gPTP can be enabled. The clock is automatically synchronized to Epoch Time when enabled and it is connected to a gPTP grandmaster.

Note

Erratic behavior may be observed if the Epoch Time of logged messages is prior to 1/1/2007.

gPTP is configured in the following interface.

_images/gPTP-Config.png — *Note that this screen varies in content between Intrepid devices.*

6.8.1. gPTP Settings

gPTP Endpoint Port	Select the Ethernet port of the device connected to a gPTP domain
gPTP Profile	Automotive: AVNU defined profile
gPTP Profile	Standard
Neighbor Prop Delay Threshold (Standard Profile Only)	Device will be identified as non-AS Capable if pDelay exceeds this value Default 800, but increased to 100000 to insure latency of active tap does not impact ability to connect stream. Can be set as high as 10000000 for the purposes of certain AVNU testing
Delay Request Interval	Period of Pdelay_Request
Sync Interval	Period of Sync/Followup messages
Announce Interval	Period of BCMA Announce message (Standard profile only)
PHC Sync Interval	Period the PHC (Physical Hardware Clock) is synchronized with the gPTP clock value. (This is the clock used for timestamping network messages.)
Enable Clock Syntonization	Slave clock will use rateratio to compensate for frequency offsets between its clock and others in the domain

Note

The interval of Delay Request Interval, Sync Interval, and Announce Interval are calculated using the value entered as follows:

Value = log2(Interval in Seconds)
Min =-5 / Max =22

6.8.2. Automotive Profile Settings (Avnu)

gPTP Role	Master
	Slave

6.8.3. Standard Profile Settings

Grandmaster Credentials (Reference IEEE-1588-2008 for attribute details)	Priority 1: 0-255, lower value = higher priority
	Clock Class: Attribute defining a clock’s TAI traceability
	Clock Accuracy
	Offset Scaled Log Variance: Attribute defining the stability of a clock
	Priority 2: 0-255, lower value = higher priority

6.9. ICS Time Sync

If multiple ICS devices are being used to log networks in parallel, the internal clocks used to timestamp the logged traffic can be synchronized in order to provide time-aligned logs. The following screen is used to configure this clock synchronization.

The devices synchronize using a private CAN network between them. This means no other DUTs or ECUs should be connected to this private CAN network. Each device must be configured from this screen to select which CAN network should be used for synchronization as well as if it is the clock master for all of the loggers or it is a clock slave.

Note

Exactly one device needs to be configured as a clock master when synchronizing clocks between multiple ICS loggers.

6.10. Performance Tests

The following are tests which can be used to characterize the bandwidth and latency between ICS hardware and its host computer. If problem is encountered with either of these, our Customer Support would be happy to help resolve it. Reference the end of this document for contact information.