9,040
edits
Line 162: | Line 162: | ||
* '''CAN Mode: '''The Mode one defines the protocol to be used. Most of CAN bus uses 11 bits protocol. | * '''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. | * '''Baud Rate:''' The Baud rate one defines the speed of the bus. 500 Mb/s is the most common baud rate for automotive application. | ||
CAN-Bus is great source of data easily collected into cars, 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 CAN-Bus. | |||
[[Image:Release_note_16.png|framed|none]] | |||
With OR36<sub>2</sub> and OR38<sub>2</sub>, a CAN-Bus interface is available as an option. 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 (NVGate V6.70) allowing their collection by the hardware. | |||
First the Bus protocol and speed have to be informed. These parameters are entered in the ''Front-end/CAN settings module in the ASB.''The Mode one defines the protocol to be used. Most of CAN bus uses 11 bits protocol. | |||
[[Image:Release_note_17.png|framed|none]] | |||
<br>The Baud rate one defines the speed of the bus. 500 Mb/s is the most common baud rate for automotive application | |||
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). | |||
CAN parameters configurations are saved in a model, workbook or project and are easily recalled for further utilization. | |||
=====Remote Control===== | =====Remote Control===== | ||
This module defines the content of some of the remote control (option) screens. The values of the following settings will configure the remote control display. | This module defines the content of some of the remote control (option) screens. The values of the following settings will configure the remote control display. |