FIRE VNET EP Module
- OBSOLETE -- substitute is FIRE2 VNET
- Must be factory installed into neoVI-Plasma or neoVI-ION.
OBSOLETE -- substitute is
At a glance
- CompatibilityOBSOLETE -- substitute is FIRE2 VNET The FIRE VNET EP Module adds functionality of a neoVI FIRE network adaptor to a neoVI PLASMA or other VNET-ready device while providing maximum performance and channel count
- Key interfaces1 Hz to 10 kHz or based on digital change; Sync Break Error State and Length, Sync Wave Error, Message ID parity, TFrameMax/Slave Not Responding, Checksum Error and Transmit Bit Errors.
- Included itemsNo bundled accessory list provided
- Lead timeCurrently Unavailable
- Country of originUS
The FIRE VNET EP Module is specially designed to provide the functionality of a neoVI FIRE network adaptor within a neoVI ION or PLASMA. The FIRE VNET can occupy any or all of the three VNET slots within a neoVI PLASMA or the two VNET slots within a neoVI ION.
Fully Isolated Network Adaptor with 8 x DWCAN, 5 x LIN, SW CAN, LSFT CAN – and much more!
The FIRE VNET provides maximum performance and channel count. One FIRE VNET has six dual-wire CAN channels and five LIN channels. Virtually every other common type of automotive network is supported in a single FIRE VNET as well. Lower speed and legacy busses such as SWCAN (single-wire), LSFT CAN (low speed fault tolerant), ISO 9141 and K-Line are also supported.
If you need more channels, or different channels, just install another VNET. The FIRE VNET is compatible with all other VNETs. You can mix and match up to three VNETs in a single neoVI PLASMA. Example configurations include:
- 18 x DWCAN and 15 x LIN (3 FIRE VNET EPs)
- 6 x DWCAN and 1 x FlexRay Network (1 FIRE VNET EP + 1 FlexRay VNET)
- 6 x DWCAN and 1 x MOST Network (1 FIRE VNET EP + 1 MOST VNET)
- 6 x DWCAN and 7 x Differential Inputs (1 FIRE VNET EP + 1 AIN VNET)
VNETs Operate Independently or Together
All VNETs are able to run their own scripts for data logging, simulation, or test execution. These scripts run independently of other active VNETs. Although they are independent, they record data with a single time stamp onto the neoVI ION and PLASMA’s SD Card.
VNETs Operate via USB or Wireless Interface
All VNETs are accessible via USB, similar to our popular neoVI network adaptors. They also are accessible and programmable via the neoVI ION / PLASMA’s wireless interfaces. This makes the neoVI PLASMA ideal whether you’re data logging in a remote area, on the test track, or running a test stand with multiple ECUs.
In case you prefer to write your own software, the FIRE VNET supports three open APIs:
- neoVI DLL API
- SAE J2534 API
- TMC RP1210 A/B API
The FIRE VNET EP includes a real-time scripting engine that is used to perform real-time messaging. For example, someone creating an application can load a script into the hardware and interface with the script variables allowing microsecond measurement and control. Also Vehicle Spy, through its Hardware Acceleration feature, can send real-time functions to the device such as periodic messaging, replay, or scripting.
Our Vehicle Spy software fully supports the FIRE VNET. You can use Vehicle Spy to monitor and transmit on all FIRE VNET EP networks simultaneously. The Vehicle Spy license from the neoVI PLASMA is required to configure stand-alone functions. Take advantage of the powerful VehicleScape DAQ interface to quickly load databases, select signals, and then auto-generate complex scripts. Send, start and stop scripts via USB or the WirelessneoVI.com server application. You can also leverage VehicleScape DAQ’s auto-generated scripts by modifying them to make a custom solution.
| Power Consumption (per VNET, typical) | 150 mA @ 14.4 VDC |
|---|---|
| Normal Sleep | 10 mA @ 12.0 VDC |
| Instant Wakeup | 27 mA @ 12.0 VDC |
| Comatose | 2 mA @ 12.0 VDC |
| Power Supply | 5.5-27 Volt Power Operation |
| Temperature Range | -40C to +85CWarranty: One Year Limited Warranty |
| Firmware | Field upgradable design (flash firmware) |
| General Purpose IO | 5 MISC IO. Digital : MISC 1-2 (0-5V). Digital/Analog(10-bit) : MISC 3-5 (0-3.3V). |
| General Purpose IO rate report interval | 1 Hz to 10 kHz or based on digital change |
| General Purpose IO Maximum Current Output (Sunk/Sourced) | 4mA |
| LIN Bus Monitor Mode identifies errors | Sync Break Error State and Length, Sync Wave Error, Message ID parity, TFrameMax/Slave Not Responding, Checksum Error and Transmit Bit Errors. |
| ECCN | EAR99 |
|---|---|
| Country of Origin | US |