NVGate Transducer and Calibration - Revision history

Lmagimel at 09:51, 26 November 2024

2024-11-26T09:51:04Z

← Older revision		Revision as of 11:51, 26 November 2024
Line 1:		Line 1:
	[[category:NVGate]]		[[category:NVGate]]
			[[category:WikiOros]]
	==Transducer Database==		==Transducer Database==
	This group manages the transducers database which is used by NVGate to automatically setup the inputs and trace front-end status at measurement time.		This group manages the transducers database which is used by NVGate to automatically setup the inputs and trace front-end status at measurement time.

Lmagimel: /* Transducers Calibration */

2020-11-24T14:05:44Z

Transducers Calibration

← Older revision		Revision as of 16:05, 24 November 2020
Line 117:		Line 117:
	==Transducers Calibration==		==Transducers Calibration==
	[[Image:Reports_Tools_Ribbons_10.png\|framed\|none]]		[[Image:Reports_Tools_Ribbons_10.png\|framed\|none]]


	Manage the transducers calibration and automatic recognition prior to measurements:		Manage the transducers calibration and automatic recognition prior to measurements:

	*		* [[Image:Reports_Tools_Ribbons_312.png]] Calibration: Initiates the calibration procedure tool.
	[[Image:Reports_Tools_Ribbons_312.png]]
	Calibration: Initiates the calibration procedure tool.
	<br>All current analyses and recording must be stopped prior switching to calibration.		<br>All current analyses and recording must be stopped prior switching to calibration.

Line 174:		Line 171:
	[[Image:Reports_Tools_Ribbons_13.png]]NB: In case of 1-DSP analyzer with 4 inputs @ 51,2kHz connected to the octave plug-in, it is not possible to perform the calibration (DSP power limit reached). In such situation, down the sampling frequency to 25,6kHz or disconnecting the inputs from the octave plug-in for the time of the calibration will allow calibrating the sensors.		[[Image:Reports_Tools_Ribbons_13.png]]NB: In case of 1-DSP analyzer with 4 inputs @ 51,2kHz connected to the octave plug-in, it is not possible to perform the calibration (DSP power limit reached). In such situation, down the sampling frequency to 25,6kHz or disconnecting the inputs from the octave plug-in for the time of the calibration will allow calibrating the sensors.

	*		* [[Image:Reports_Tools_Ribbons_314.png]] Detect TEDS: Start the sequence for detecting transducers (or missing one) equipped with an electronic datasheet inside (TEDS: Transducer Electronic Data Sheet) connected to the front end.
	[[Image:Reports_Tools_Ribbons_314.png]]
	Detect TEDS: Start the sequence for detecting transducers (or missing one) equipped with an electronic datasheet inside (TEDS: Transducer Electronic Data Sheet) connected to the front end.

	As the TEDS sequence occurs automatically when an input coupling is set to ICP<nowiki>+</nowiki>TEDS, the Detect TEDS button is used for re-checking after transducers or cables modifications. The result of check will be visible on the warning window and may lead to add new transducers to the TDB.		As the TEDS sequence occurs automatically when an input coupling is set to ICP<nowiki>+</nowiki>TEDS, the Detect TEDS button is used for re-checking after transducers or cables modifications. The result of check will be visible on the warning window and may lead to add new transducers to the TDB.
Line 188:		Line 183:
	The content of the TEDS is used to fill the transducer properties. The data from the TEDS that have no correspondence in the ''transducer database'' are copied in the comment area. The name is proposed as the concatenation of type and serial number. User may change it.		The content of the TEDS is used to fill the transducer properties. The data from the TEDS that have no correspondence in the ''transducer database'' are copied in the comment area. The name is proposed as the concatenation of type and serial number. User may change it.

	[[Image:Reports_Tools_Ribbons_316.png\|~~framed~~\|none]]		[[Image:Reports_Tools_Ribbons_316.png\|700px\|none]]

	* A known transducer (existing in the database) is recognized in the corresponding input. NVGate® will notice it in the log window (which is popped up automatically).		* A known transducer (existing in the database) is recognized in the corresponding input. NVGate® will notice it in the log window (which is popped up automatically).
Line 239:		Line 234:
	The window below is displayed.		The window below is displayed.

	[[Image:Reports_Tools_Ribbons_11.png\|~~framed~~\|none]]		[[Image:Reports_Tools_Ribbons_11.png\|700px\|none]]

	The new transducer is added to the transducer database.		The new transducer is added to the transducer database.

Lmagimel: /* Transducer Database */

2020-11-24T14:04:34Z

Transducer Database

← Older revision		Revision as of 16:04, 24 November 2020
Line 73:		Line 73:
	* Default coupling: default coupling value that will be used when a new transducer is created. This value can be changed individually.		* Default coupling: default coupling value that will be used when a new transducer is created. This value can be changed individually.
	* Comment: Free text area		* Comment: Free text area
	*		* [[Image:Reports_Tools_Ribbons_260.png\|none]] History:
	[[Image:Reports_Tools_Ribbons_260.png~~\|framed~~\|none]]
	History:
	This tool is used to see how transducer sensitivity and offset change over time. Information about every calibration is displayed, making it easy for the user to see if the transducer behavior is constant.		This tool is used to see how transducer sensitivity and offset change over time. Information about every calibration is displayed, making it easy for the user to see if the transducer behavior is constant.

Line 86:		Line 84:
	It is used to select the sensitivity graph, the offset graph or both. It is also possible to hide/display the factory values. There is also a marker to highlight the calibration.		It is used to select the sensitivity graph, the offset graph or both. It is also possible to hide/display the factory values. There is also a marker to highlight the calibration.

	*		* [[Image:Reports_Tools_Ribbons_262.png]] Merge multiple transducer databases into one. The merged TDB is the one currently used by NVGate (file: ''transducers.tdb'' located in the ''NVGate.exe'' directory)
	[[Image:Reports_Tools_Ribbons_262.png]]
	Merge multiple transducer databases into one. The merged TDB is the one currently used by NVGate (file: ''transducers.tdb'' located in the ''NVGate.exe'' directory)
	Clicking on ''Merge'' open the database to merge browser. Both native (.cdb) and comma separated values (.txt) formats are available. For the csv, the format is the same as the export one, with one line per transducer.		Clicking on ''Merge'' open the database to merge browser. Both native (.cdb) and comma separated values (.txt) formats are available. For the csv, the format is the same as the export one, with one line per transducer.

	In case of conflict (the same transducer does not features the same setup in the 2 databases) a specific dialog box is proposed.		In case of conflict (the same transducer does not features the same setup in the 2 databases) a specific dialog box is proposed.

	[[Image:Reports_Tools_Ribbons_263.png\|~~framed~~\|none]]		[[Image:Reports_Tools_Ribbons_263.png\|700px\|none]]

	Only conflict lines are displayed.		Only conflict lines are displayed.
Line 111:		Line 107:
	[[Image:Reports_Tools_Ribbons_264.png\|framed\|none]]		[[Image:Reports_Tools_Ribbons_264.png\|framed\|none]]

	*		* [[Image:Reports_Tools_Ribbons_265.png]] Export: Allows exporting the current database (file: ''transducers.tdb'' located in the ''NVGate.exe'' directory) in csv format.
	[[Image:Reports_Tools_Ribbons_265.png]]
	Export: Allows exporting the current database (file: ''transducers.tdb'' located in the ''NVGate.exe'' directory) in csv format.

	The exported file contains one line per transducer with the following field.		The exported file contains one line per transducer with the following field.

	[[Image:Reports_Tools_Ribbons_266.png\|~~framed~~\|none]]		[[Image:Reports_Tools_Ribbons_266.png\|700px\|none]]

	Only the latest site calibration information are exported in the txt file.		Only the latest site calibration information are exported in the txt file.

Lmagimel at 14:03, 24 November 2020

2020-11-24T14:03:11Z

← Older revision		Revision as of 16:03, 24 November 2020
Line 1:		Line 1:
	[[category:NVGate]]		[[category:NVGate]]

	==Transducer Database==		==Transducer Database==
	This group manages the transducers database which is used by NVGate to automatically setup the inputs and trace front-end status at measurement time.		This group manages the transducers database which is used by NVGate to automatically setup the inputs and trace front-end status at measurement time.

Lmagimel: /* Transducers Calibration */

2020-11-24T14:02:47Z

Transducers Calibration

← Older revision		Revision as of 16:02, 24 November 2020
Line 122:		Line 122:
	Only the latest site calibration information are exported in the txt file.		Only the latest site calibration information are exported in the txt file.

	~~===~~==Transducers Calibration~~===~~==		==Transducers Calibration==
	[[Image:Reports_Tools_Ribbons_10.png\|framed\|none]]		[[Image:Reports_Tools_Ribbons_10.png\|framed\|none]]

Lmagimel at 14:02, 24 November 2020

2020-11-24T14:02:23Z

← Older revision		Revision as of 16:02, 24 November 2020
Line 1:		Line 1:
	[[category:NVGate]]		[[category:NVGate]]

	~~===~~==Transducer Database~~===~~==		==Transducer Database==
	This group manages the transducers database which is used by NVGate to automatically setup the inputs and trace front-end status at measurement time.		This group manages the transducers database which is used by NVGate to automatically setup the inputs and trace front-end status at measurement time.

Lmagimel: /* Transducer Database */

2020-11-24T14:02:12Z

Transducer Database

← Older revision		Revision as of 16:02, 24 November 2020
Line 4:		Line 4:
	This group manages the transducers database which is used by NVGate to automatically setup the inputs and trace front-end status at measurement time.		This group manages the transducers database which is used by NVGate to automatically setup the inputs and trace front-end status at measurement time.

	*
	[[Image:Reports_Tools_Ribbons_255.png\|framed\|none]]		[[Image:Reports_Tools_Ribbons_255.png\|framed\|none]]

	Database: Opens the transducer database dialog		Database: Opens the transducer database dialog
	The left side displays all the transducers in the database in a tree form. They are grouped by type. For each type of transducer, there is a default transducer. The right side displays the information about the selected transducer.		The left side displays all the transducers in the database in a tree form. They are grouped by type. For each type of transducer, there is a default transducer. The right side displays the information about the selected transducer.
Line 18:		Line 18:
	** '''Note:''' you need to restart NVGate to apply this new transducer on an Input.		** '''Note:''' you need to restart NVGate to apply this new transducer on an Input.

	[[Image:Reports_Tools_Ribbons_257.png\|~~framed~~\|none]]		[[Image:Reports_Tools_Ribbons_257.png\|700px\|none]]

	* Transducer type: Can be a pre-defined type (microphone, accelerometer...) or a user-defined type.		* Transducer type: Can be a pre-defined type (microphone, accelerometer...) or a user-defined type.

Lmagimel at 06:53, 25 September 2020

2020-09-25T06:53:17Z

← Older revision		Revision as of 08:53, 25 September 2020
Line 1:		Line 1:
			[[category:NVGate]]

	=====Transducer Database=====		=====Transducer Database=====
	This group manages the transducers database which is used by NVGate to automatically setup the inputs and trace front-end status at measurement time.		This group manages the transducers database which is used by NVGate to automatically setup the inputs and trace front-end status at measurement time.

Lmagimel: /* Transducers Calibration */

2020-06-18T08:04:42Z

Transducers Calibration

← Older revision		Revision as of 10:04, 18 June 2020
Line 177:		Line 177:
	* Calibrate: Starts the calibration. The analyzer detects the maximum level, checks that frequency is near the calibrator frequency, and determines the new sensitivity.		* Calibrate: Starts the calibration. The analyzer detects the maximum level, checks that frequency is near the calibrator frequency, and determines the new sensitivity.

	[[Image:Reports_Tools_Ribbons_13.png]]		[[Image:Reports_Tools_Ribbons_13.png]]NB: In case of 1-DSP analyzer with 4 inputs @ 51,2kHz connected to the octave plug-in, it is not possible to perform the calibration (DSP power limit reached). In such situation, down the sampling frequency to 25,6kHz or disconnecting the inputs from the octave plug-in for the time of the calibration will allow calibrating the sensors.

	NB: In case of 1-DSP analyzer with 4 inputs @ 51,2kHz connected to the octave plug-in, it is not possible to perform the calibration (DSP power limit reached). In such situation, down the sampling frequency to 25,6kHz or disconnecting the inputs from the octave plug-in for the time of the calibration will allow calibrating the sensors.

	*		*

NIcolasAegerter: /* Transducer Database */

2020-06-17T08:30:22Z

Transducer Database

← Older revision		Revision as of 10:30, 17 June 2020
Line 14:		Line 14:
	* ''Modify'': This button is not available when a default transducer is selected. It is used to modify the characteristics of the transducer. Clicking on the modify or new button opens the transducer definition dialog box:		* ''Modify'': This button is not available when a default transducer is selected. It is used to modify the characteristics of the transducer. Clicking on the modify or new button opens the transducer definition dialog box:
	* ''Transucer type / New'': Create a new type of transducer.<br>		* ''Transucer type / New'': Create a new type of transducer.<br>
	* '''Note:''' you need to restart NVGate to apply this new transducer on an Input.		** '''Note:''' you need to restart NVGate to apply this new transducer on an Input.

	[[Image:Reports_Tools_Ribbons_257.png\|framed\|none]]		[[Image:Reports_Tools_Ribbons_257.png\|framed\|none]]