Difference between revisions of "NVGate Front End"

Jump to navigation Jump to search

NVGate Front End (view source)

Revision as of 13:40, 6 May 2020

2,437 bytes removed ,  13:40, 6 May 2020
→‎CAN Bus
Line 152: Line 152:
* '''Detect TEDS: '''Run a TEDS detection. The analyzer detects if a TEDS transducer is connected to an input with the ICP TEDS coupling. All the characteristics of the transducer are detected and it automatically appears in the transducer database.
* '''Detect TEDS: '''Run a TEDS detection. The analyzer detects if a TEDS transducer is connected to an input with the ICP TEDS coupling. All the characteristics of the transducer are detected and it automatically appears in the transducer database.
* '''Bridge Auto-zero:''' The Bridge Xpod features an automatic bridge balancing using voltage offset injection. The bridge balancing process duration is about 20 sec. Process information are provided in the NVGate status bar (bottom left). After balancing, the Offset compensation is modified according to the requested compensation voltage.
* '''Bridge Auto-zero:''' The Bridge Xpod features an automatic bridge balancing using voltage offset injection. The bridge balancing process duration is about 20 sec. Process information are provided in the NVGate status bar (bottom left). After balancing, the Offset compensation is modified according to the requested compensation voltage.
==CAN Bus==
Car Area Network (CAN) bus is great source of data easily collected into vehicles, jet engines and power generation machineries. This Network provides real-time parameters that can be used to correlate measurements and/or evaluate their influence. As an example, the correlation of noise and vibration with the engine load is a typical application of CAN parameter acquisition. For this application, the engine load is collected from the ECU through the CANBus.
The hardware consists of an interface box which is adapted to the CAN-Bus impedance and a High speed serial cable (1 and 3 meters) connected to the new analyzer<nowiki>’</nowiki>s high speed serial port. When connected to a CAN-bus the parameter encoding has to be setup in the software allowing their collection by the hardware.
[[Image:Release_note_16.png|framed|none]]
When connected to a CAN-bus the parameter encoding has to be setup in the software allowing their collection by the hardware.
* '''CAN Mode: '''The Mode one defines the protocol to be used. Most of CAN bus uses 11 bits protocol.
* '''Baud Rate:''' The Baud rate one defines the speed of the bus. 500 Mb/s is the most common baud rate for automotive application.
[[Image:Release_note_17.png|framed|none]]
Then each CAN parameter is declared in the CAN input list. One CAN inputs corresponds to one parameter from the CAN bus. The CAN inputs are enabled like the DC inputs.
[[Image:Release_note_18.png|framed|none]]
The CAN inputs operate likes DC inputs they can:
* Be recorded with the recorder plug-in
* Monitored by view meter or front end profiles
* Saved into profiles (waterfall)
* Used as waterfall<nowiki>'</nowiki>s parameters
* Trigger level and delta level events
At least, the parameter format is setup in the CAN-inputs module. These format settings define where and how the parameter is encoded in one CAN message:
[[Image:Release_note_19.png|framed|none]]
Up to 24 CAN parameters are available. Note that as the maximum recorded channels is 38, it is not possible to records all standards inputs (32 inputs <nowiki>+</nowiki> 4 aux. <nowiki>+</nowiki> 2 triggers) plus all CAN inputs (24 CAN parameters).
We are able to '''import CanBus .dbc file''' to automatically import the settings. [[NVGate_Tools:_CanBus_Import_.dbc|Read his page.]]
CAN parameters configurations are saved in a model, workbook or project and are easily recalled for further utilization.


==Remote Control==
==Remote Control==
Retrieved from "https://wiki.oros.com/index.php?title=Special:MobileDiff/3769"

Navigation menu