Virtual Instrument - Revision history

Logmanoriginal: Move to :Category:VIs

2024-08-07T16:49:10Z

← Older revision		Revision as of 16:49, 7 August 2024
Line 33:		Line 33:

	[[Category:LabVIEW fundamentals]]		[[Category:LabVIEW fundamentals]]
	[[Category:VI]]		[[Category:VIs]]

Mefistotelis: /* The VI File Format */

2020-05-31T10:44:28Z

The VI File Format

← Older revision		Revision as of 10:44, 31 May 2020
Line 24:		Line 24:
	==The VI File Format==		==The VI File Format==

	VIs are saved as ''*.vi'' files, in a proprietary binary [[Resource Container]] format, defined by [[National Instruments]] - the makers of [[LabVIEW]]. The format is a container, storing a group of Resources with 4-character identifiers.		VIs are saved as ''*.vi'' files, in a proprietary binary [[Resource Container]] format, defined by [[National Instruments]] - the makers of [[LabVIEW]]. The format is a container, storing a group of [[Resource_Container#Known_Resources\|Resources]] with 4-character identifiers.

	A big change in VI format happened in LV version 8.0 - the place where [[Type descriptor\|Type descriptors]] are defined was changed. Before, '''TD'''s were defined in-place where they were needed; with 8.0, a new resource ''VCTP'' (''VI Consolidated Types'') was introduced, and all '''TD'''s were moved there. Outside ''VCTP'', '''TD'''s are now identified by ''TypeID'' - index within the consolidated types table.		A big change in VI format happened in LV version 8.0 - the place where [[Type descriptor\|Type descriptors]] are defined was changed. Before, '''TD'''s were defined in-place where they were needed; with 8.0, a new resource ''VCTP'' (''VI Consolidated Types'') was introduced, and all '''TD'''s were moved there. Outside ''VCTP'', '''TD'''s are now identified by ''TypeID'' - index within the consolidated types table.

Mefistotelis: link to separate page on RSRC format

2020-05-31T10:31:37Z

link to separate page on RSRC format

Show changes

Mefistotelis: /* The VI File Format */

2020-05-31T10:18:13Z

The VI File Format

← Older revision		Revision as of 10:18, 31 May 2020
Line 28:		Line 28:
	The format is a container, storing a group or Resources. Resources have 4-character identifier assigned, and the 4-character identifier for the whole container is ''RSRC''. Actually, most files used by LabVIEW have that ''RSRC'' format, only the specific Resources stored inside are different. The files with that header include ''.vi'', ''.ctl'', ''.mnu'', ''.llb'', ''.dlog'', ''.ctt'', ''.vit'', ''.xctl'', ''*.uir'', and many other files created with, or internally used by, LabVIEW.		The format is a container, storing a group or Resources. Resources have 4-character identifier assigned, and the 4-character identifier for the whole container is ''RSRC''. Actually, most files used by LabVIEW have that ''RSRC'' format, only the specific Resources stored inside are different. The files with that header include ''.vi'', ''.ctl'', ''.mnu'', ''.llb'', ''.dlog'', ''.ctt'', ''.vit'', ''.xctl'', ''*.uir'', and many other files created with, or internally used by, LabVIEW.

	The resources stored within have their identifiers often identical to those in ''Resource fork'' format, but many new ones are also ~~introduces~~. Some resources have multiple variations, as their structure changed between versions of LabVIEW.		The resources stored within have their identifiers often identical to those in ''Resource fork'' format, but many new ones are also introduced. Some resources have multiple variations, as their structure changed between versions of LabVIEW.

	A big change in VI format happened in LV version 8.0 - the place where [[Type descriptor\|Type descriptors]] are defined was changed. Before, '''TD'''s were defined in-place where they were needed; with 8.0, a new resource ''VCTP'' (''VI Consolidated Types'') was introduced, and all '''TD'''s were moved there. Outside ''VCTP'', '''TD'''s are now identified by ''TypeID'' - index within the consolidated types table.		A big change in VI format happened in LV version 8.0 - the place where [[Type descriptor\|Type descriptors]] are defined was changed. Before, '''TD'''s were defined in-place where they were needed; with 8.0, a new resource ''VCTP'' (''VI Consolidated Types'') was introduced, and all '''TD'''s were moved there. Outside ''VCTP'', '''TD'''s are now identified by ''TypeID'' - index within the consolidated types table.

Mefistotelis: /* Known Resources */

2020-05-31T10:12:21Z

Known Resources

← Older revision		Revision as of 10:12, 31 May 2020
Line 239:		Line 239:
	\|PNGI		\|PNGI
	\|PNG Image		\|PNG Image
	\|		\|Stores a bitmap picture in [https://en.wikipedia.org/wiki/Portable_Network_Graphics PNG format].
	\|-		\|-
	\|MNGI		\|MNGI
	\|MNG Image		\|MNG Image
	\|		\|While PNGs become quite popular, their animated counterpart, [https://en.wikipedia.org/wiki/Multiple-image_Network_Graphics MNG format], never really caught on.
	\|-		\|-
	\|ICON		\|ICON
Line 251:		Line 251:
	\|ICN#		\|ICN#
	\|Icon Large Double 32x64 1bpp		\|Icon Large Double 32x64 1bpp
	\|		\|Usually used to store one icon in two versions (ie. disabled and active).
	\|-		\|-
	\|ics#		\|ics#
Line 259:		Line 259:
	\|CURS		\|CURS
	\|Cursor 16x34 1bpp		\|Cursor 16x34 1bpp
	\|		\|Usually used to store one cursor in two versions (ie. disabled and active).
	\|-		\|-
	\|ics4		\|ics4
Line 287:		Line 287:
	\|LVzp		\|LVzp
	\|LabView Zipped Program tree		\|LabView Zipped Program tree
	\|		\|A whole application compressed to ZIP file.
	\|-		\|-
	\|PRT		\|PRT

Mefistotelis: list of resources

2020-05-31T10:04:11Z

list of resources

Show changes

Mefistotelis: file format chapter to really discuss the format

2020-05-31T09:42:15Z

file format chapter to really discuss the format

← Older revision		Revision as of 09:42, 31 May 2020
Line 3:		Line 3:
	The term Virtual Instrument is a play off of the fact that LabVIEW applications are designed for writing software that simulates the functionality of instruments -- rather than being a physical instrument on a laboratory bench, they are virtual and exist in software.		The term Virtual Instrument is a play off of the fact that LabVIEW applications are designed for writing software that simulates the functionality of instruments -- rather than being a physical instrument on a laboratory bench, they are virtual and exist in software.

	==~~The~~ VI ~~File Format~~==		==Content of a VI file==
	~~VIs are saved as ''*.vi'' files in a proprietary binary format defined by [[National Instruments]], the makers of [[LabVIEW]].~~ By default, a VI contains two kinds of code: the graphical source code that you edit and a compiled version of this code that LabVIEW uses to run the VI.
			By default, a VI contains two kinds of code: the graphical source code that you edit and a compiled version of this code that LabVIEW uses to run the VI.

	The graphical source code includes the:		The graphical source code includes the:
	*[[Front Panel]]		*[[Front Panel]]
	*[[Block Diagram]]		*[[Block Diagram]]
			*[[Data Space]]
	*[[Connector Pane]]		*[[Connector Pane]]
	*[[VI_Icons\|Icon]]		*[[VI_Icons\|Icon]]
Line 19:		Line 21:

	To avoid this problem, Starting in [[LabVIEW 2010]], [[LabVIEW]] allows you to separate compiled code from the graphical source code of a VI, thereby creating source-only VIs. After you separate the compiled code from a VI, LabVIEW still compiles the VI when you modify subVIs. However, LabVIEW stores the recompiled version of the code in a [[Compiled Object Cache\|compiled object cache]] rather than in the VI in [[Source Code Control\|source code control]]. Because the VI in [[Source Code Control\|source code control]] does not change, you no longer have to check the VI out of source control when you change subVIs.		To avoid this problem, Starting in [[LabVIEW 2010]], [[LabVIEW]] allows you to separate compiled code from the graphical source code of a VI, thereby creating source-only VIs. After you separate the compiled code from a VI, LabVIEW still compiles the VI when you modify subVIs. However, LabVIEW stores the recompiled version of the code in a [[Compiled Object Cache\|compiled object cache]] rather than in the VI in [[Source Code Control\|source code control]]. Because the VI in [[Source Code Control\|source code control]] does not change, you no longer have to check the VI out of source control when you change subVIs.

			==The VI File Format==

			VIs are saved as ''*.vi'' files, in a proprietary binary format defined by [[National Instruments]], the makers of [[LabVIEW]]. The format is strongly inspired by [https://en.wikipedia.org/wiki/Resource_fork Mac OS Resource Fork format], as LabVIEW was originally created for that platform, and ported to other OSes later, at version 2.5.

			The format is a container, storing a group or Resources. Resources have 4-character identifier assigned, and the 4-character identifier for the whole container is ''RSRC''. Actually, most files used by LabVIEW have that ''RSRC'' format, only the specific Resources stored inside are different. The files with that header include ''.vi'', ''.ctl'', ''.mnu'', ''.dlog'', ''.ctt'', ''.vit'', ''.xctl'', ''.uir'', and many other files created with, or internally used by, LabVIEW.

			The resources stored within have their identifiers often identical to those in ''Resource fork'' format, but many new ones are also introduces. Some resources have multiple variations, as their structure changed between versions of LabVIEW.

			A big change in VI format happened in LV version 8.0 - the place where [[Type descriptors]] are defined was changed. Before, '''TD'''s were defined in-place where they were needed; with 8.0, a new resource ''VCTP'' (''VI Consolidated Types'') was introduced, and all '''TD'''s were moved there. Outside ''VCTP'', '''TD'''s are now identified by ''TypeID'' - index within the consolidated types table.

	==See Also==		==See Also==

Q: Category reorg

2020-05-09T04:59:11Z

Category reorg

← Older revision		Revision as of 04:59, 9 May 2020
Line 25:		Line 25:

	[[Category:LabVIEW fundamentals]]		[[Category:LabVIEW fundamentals]]
	[[Category:~~Development Environment~~]]		[[Category:VI]]

Q: Category reorg

2020-05-08T13:01:36Z

Category reorg

← Older revision		Revision as of 13:01, 8 May 2020
Line 25:		Line 25:

	[[Category:LabVIEW fundamentals]]		[[Category:LabVIEW fundamentals]]
			[[Category:Development Environment]]

Q at 01:15, 8 May 2020

2020-05-08T01:15:53Z

← Older revision		Revision as of 01:15, 8 May 2020
Line 1:		Line 1:
	The '''VI''', or <u>V</u>irtual <u>I</u>nstrument, is the basic building block of programs written in the [[G]] Language. It is similar to a function or subroutine in other programming languages. It includes the [[Front Panel]] (containing [[Controls]] and [[Indicators]]), the [[Block Diagram]] (containing Control Terminals, Wires, and Structures and various other [[GObject]] nodes), the VI's [[Icon]] and its [[Connector Pane]] (as well as compiled executable code which is hidden behind the scenes).		The '''VI''', or <u>V</u>irtual <u>I</u>nstrument, is the basic building block of programs written in the [[G]] Language. It is similar to a function or subroutine in other programming languages. It includes the [[Front Panel]] (containing [[Controls]] and [[Indicators]]), the [[Block Diagram]] (containing Control Terminals, Wires, and Structures and various other [[GObject class\|GObject]] nodes), the VI's [[Icon]] and its [[Connector Pane]] (as well as compiled executable code which is hidden behind the scenes).

	The term Virtual Instrument is a play off of the fact that LabVIEW applications are designed for writing software that simulates the functionality of instruments -- rather than being a physical instrument on a laboratory bench, they are virtual and exist in software.		The term Virtual Instrument is a play off of the fact that LabVIEW applications are designed for writing software that simulates the functionality of instruments -- rather than being a physical instrument on a laboratory bench, they are virtual and exist in software.
Line 23:		Line 23:
	*[[Separating Compiled Code]]		*[[Separating Compiled Code]]
	*[[NI LabVIEW Compiler]]		*[[NI LabVIEW Compiler]]

	~~[[Category:LabVIEW fundamentals]]~~
	~~[[Category:LabVIEW fundamentals]]~~

	[[Category:LabVIEW fundamentals]]		[[Category:LabVIEW fundamentals]]