Variants - Revision history

Harald Friedrich: /* General */

2025-10-06T13:54:49Z

General

← Older revision		Revision as of 15:54, 6 October 2025
Line 1:		Line 1:
	== General ==		== General ==

	Often it is necessary to handle different variants (options) of assembly within one project. This will have influence on your purchasing needs. TARGET 3001! allows to handle 256 variants of a project. This can be variants of assembly or variants referring to different properties of components.<br><br>		Often it is necessary to handle different variants (options) of assembly within one project. This will have influence on your purchasing needs. TARGET 3001! allows to handle 256 variants of a project. This can be variants of assembly or variants referring to different properties of components. If you want to use the feature "Variants", you have to declare at least two variants.<br><br>
	'''Here it is always about different (variant) component assembly. The produced PCB is always the same!'''<br>		'''Here it is always about different (variant) component assembly. The produced PCB is always the same!'''<br>

Harald Friedrich at 07:43, 22 October 2021

2021-10-22T07:43:59Z

← Older revision		Revision as of 09:43, 22 October 2021
Line 1:		Line 1:
	== General ==		== General ==

	Often it is necessary to handle different variants (options) of assembly within one project. This will have influence on your purchasing needs. TARGET 3001! allows to handle 256 variants of a project. This can be variants of assembly or variants referring to different properties of components.		Often it is necessary to handle different variants (options) of assembly within one project. This will have influence on your purchasing needs. TARGET 3001! allows to handle 256 variants of a project. This can be variants of assembly or variants referring to different properties of components.<br><br>
			'''Here it is always about different (variant) component assembly. The produced PCB is always the same!'''<br>

	== Handling of variants by any component of the project ==		== Handling of variants by any component of the project ==

Markus Friedrich: /* Variants and different Bills of material (BoM) */

2017-03-14T12:11:55Z

Variants and different Bills of material (BoM)

← Older revision		Revision as of 14:11, 14 March 2017
Line 36:		Line 36:
	Imagine IC3,7442, a BCD converter shall be mounted in all variants. But we must recognize two variants of purchase regarding this component. We keep the naming of the variants "normal" and "special".		Imagine IC3,7442, a BCD converter shall be mounted in all variants. But we must recognize two variants of purchase regarding this component. We keep the naming of the variants "normal" and "special".

	In variant "normal" the component shall achieve the value 7442_x and shall be purchased at the distributor DigiKey with ordering number 1234567. In variant "special" the component shall achieve the value 7442_ y and shall be purchased at Farnell using ordering number 999111. Later we want to give out bills of material having the component's properties listed according to the variant ~~selected for~~ to give it to ~~the~~ purchasing department. First we define this component "assembled" in both variants, "normal" and "special". Double click on the handle cross and open the dialog "Change Symbols". Use the "Variants" button for setting the component assembled in all variants (tick the box "The component is used in this variant" an all variants).<br>		In variant "normal" the component shall achieve the value 7442_x and shall be purchased at the distributor DigiKey with ordering number 1234567. In variant "special" the component shall achieve the value 7442_ y and shall be purchased at Farnell using ordering number 999111. Later we want to give out bills of material having the component's properties listed according to the selected variant in order to give it to our purchasing department. First we define this component "assembled" in both variants, "normal" and "special". Double click on the handle cross and open the dialog "Change Symbols". Use the "Variants" button for setting the component assembled in all variants (tick the box "The component is used in this variant" an all variants).<br>

	[[Image:e_Varianten8.jpg\|none]]		[[Image:e_Varianten8.jpg\|none]]
Line 79:		Line 79:

	The BoMs can be printed and/or edited by any texteditor or spreadsheet.<br>		The BoMs can be printed and/or edited by any texteditor or spreadsheet.<br>




	== Variants and Gerber data ==		== Variants and Gerber data ==

Markus Friedrich at 12:07, 14 March 2017

2017-03-14T12:07:04Z

← Older revision		Revision as of 14:07, 14 March 2017
Line 28:		Line 28:
	[[Image:e_var5.jpg\|none]]<br><br><br><br>		[[Image:e_var5.jpg\|none]]<br><br><br><br>

	~~== Control variants by the use of the Hierarchy browser ==~~

	~~Only for versions older than V13.3.0.62!~~

	~~Highlight in the hierarchy browser (find it on the left edge of your screen by click on [[Image:HierBrwsArrow.jpg]] by [[Mousekeys\|'''M1''']] "Variants":<br>~~

	~~[[Image:e_Varianten1.jpg\|none]]~~

	~~Now click [[Mousekeys\|'''M2''']] for to select "Properties" within the context menu. Within the following dialog you can name variants as desired:<br>~~

	~~[[Image:e_Varianten2.jpg\|none]]~~

	~~In the hierarchy browser now click '''[[M1]]''' within "Components" upon the varying component and then [[Mousekeys\|'''M2''']] to reach menu "Properties":<br>~~

	~~[[Image:e_Varianten3.jpg\|none]]~~

	~~The variants in which the component is proposed to appear can now be defined:<br>~~

	~~[[Image:e_Varianten4.jpg\|none]]~~

	~~Component C10 eg. shall not be assembled within the variant named "normal". The outline of the component appears in hatched line.<br>~~

	~~[[Image:e_Varianten5.jpg\|none]]~~

	== Variants and different Bills of material (BoM) ==		== Variants and different Bills of material (BoM) ==

Markus Friedrich: /* Control variants by the use of the Hierarchy browser */

2017-03-14T12:06:17Z

Control variants by the use of the Hierarchy browser

← Older revision		Revision as of 14:06, 14 March 2017
Line 30:		Line 30:
	== Control variants by the use of the Hierarchy browser ==		== Control variants by the use of the Hierarchy browser ==

	Only for ~~TARGET 3001! -~~ versions older than V13.3.0.62!		Only for versions older than V13.3.0.62!

	Highlight in the hierarchy browser (find it on the left edge of your screen by click on [[Image:HierBrwsArrow.jpg]] by [[Mousekeys\|'''M1''']] "Variants":<br>		Highlight in the hierarchy browser (find it on the left edge of your screen by click on [[Image:HierBrwsArrow.jpg]] by [[Mousekeys\|'''M1''']] "Variants":<br>

Markus Friedrich: /* Handling of variants by any component of the project */

2017-03-14T12:05:12Z

Handling of variants by any component of the project

← Older revision		Revision as of 14:05, 14 March 2017
Line 26:		Line 26:
	Which variant we currently work in can be controlled by the "variants navigator" top right of the screen. It can be seen only if variants really do exist.<br>		Which variant we currently work in can be controlled by the "variants navigator" top right of the screen. It can be seen only if variants really do exist.<br>

	[[Image:e_var5.jpg\|none]]		[[Image:e_var5.jpg\|none]]<br><br><br><br>

	== Control variants by the use of the Hierarchy browser ==		== Control variants by the use of the Hierarchy browser ==

Markus Friedrich: /* Handling of variants by any component of the project */

2017-03-14T11:47:11Z

Handling of variants by any component of the project

← Older revision		Revision as of 13:47, 14 March 2017
Line 16:		Line 16:
	[[Image:e_var2.jpg\|none]]<br><br>		[[Image:e_var2.jpg\|none]]<br><br>

	The variant "0,<all>" is a view over all variants. It can not be renamed. Now we click on the pull down button and select variant "1, <unused>". We click on the button "Rename variant" and give it the name "normal". We see in the same dialog, that the box "The component is used in this variant" is checked. We must uncheck it because we don't want to have this component assembled in variant "normal".<br>		The variant "0,<all>" is a view over all variants. It can not be renamed. Now we click on the pull down button and select variant "1, <unused>". We click on the button "Rename variant" and give it the name "normal". We see in the same dialog, that the box "The component is used in this variant" is checked. We must uncheck it because we don't want to have this component assembled in variant "normal".<br><br>

	[[Image:e_var3.jpg\|none]]<br><br>		[[Image:e_var3.jpg\|none]]<br><br>

	We create a second variant named "special", but here we leave this box checked because in this variant the component shall be assembled. The outlines of the component appear in hatched line immediately. ~~this~~ is a visual hint that the component is not assembled in all variants.<br>		We create a second variant named "special", but here we leave this box checked because in this variant the component shall be assembled. The outlines of the component appear in hatched line immediately. This is a visual hint that the component is not assembled in all variants.<br><br>

	[[Image:e_var4.jpg\|none]]<br><br>		[[Image:e_var4.jpg\|none]]<br><br>

Markus Friedrich: /* Handling of variants by any component of the project */

2017-03-14T11:00:10Z

Handling of variants by any component of the project

← Older revision		Revision as of 13:00, 14 March 2017
Line 8:		Line 8:
	For example in a project the component IC2, 93LC56 shall be not assembled within the variant named "normal", but it shall be assembled in a second variant named "special".		For example in a project the component IC2, 93LC56 shall be not assembled within the variant named "normal", but it shall be assembled in a second variant named "special".

	We doubleclick the handle cross of the component and open the dialog: "Change Symbols".<br>		We doubleclick the handle cross of the component and open the dialog: "Change Symbols".<br><br>

	[[Image:e_var1.jpg\|none]]		[[Image:e_var1.jpg\|none]]<br><br>

	A click on button "Variants" opens the dialog for the naming of the variants and for the definition within which of the variants the component shall be assembled or not.<br>		A click on button "Variants" opens the dialog for the naming of the variants and for the definition within which of the variants the component shall be assembled or not.<br><br>

	[[Image:e_var2.jpg\|none]]		[[Image:e_var2.jpg\|none]]<br><br>

	The variant "0,<all>" is a view over all variants. It can not be renamed. Now we click on the pull down button and select variant "1, <unused>". We click on the button "Rename variant" and give it the name "normal". We see in the same dialog, that the box "The component is used in this variant" is checked. We must uncheck it because we don't want to have this component assembled in variant "normal".<br>		The variant "0,<all>" is a view over all variants. It can not be renamed. Now we click on the pull down button and select variant "1, <unused>". We click on the button "Rename variant" and give it the name "normal". We see in the same dialog, that the box "The component is used in this variant" is checked. We must uncheck it because we don't want to have this component assembled in variant "normal".<br>

	[[Image:e_var3.jpg\|none]]		[[Image:e_var3.jpg\|none]]<br><br>

	We create a second variant named "special", but here we leave this box checked because in this variant the component shall be assembled. The outlines of the component appear in hatched line immediately. this is a visual hint that the component is not assembled in all variants.<br>		We create a second variant named "special", but here we leave this box checked because in this variant the component shall be assembled. The outlines of the component appear in hatched line immediately. this is a visual hint that the component is not assembled in all variants.<br>

	[[Image:e_var4.jpg\|none]]		[[Image:e_var4.jpg\|none]]<br><br>

	Which variant we currently work in can be controlled by the "variants navigator" top right of the screen. It can be seen only if variants really do exist.<br>		Which variant we currently work in can be controlled by the "variants navigator" top right of the screen. It can be seen only if variants really do exist.<br>

Markus Friedrich: /* Handling of variants by any component of the project */

2010-06-11T10:45:21Z

Handling of variants by any component of the project

New page

== General ==

Often it is necessary to handle different variants (options) of assembly within one project. This will have influence on your purchasing needs. TARGET 3001! allows to handle 256 variants of a project. This can be variants of assembly or variants referring to different properties of components.

== Handling of variants by any component of the project ==

For example in a project the component IC2, 93LC56 shall be not assembled within the variant named "normal", but it shall be assembled in a second variant named "special".

We doubleclick the handle cross of the component and open the dialog: "Change Symbols". 

[[Image:e_var1.jpg|none]]

A click on button "Variants" opens the dialog for the naming of the variants and for the definition within which of the variants the component shall be assembled or not. 

[[Image:e_var2.jpg|none]]

The variant "0,<all>" is a view over all variants. It can not be renamed. Now we click on the pull down button and select variant "1, <unused>". We click on the button "Rename variant" and give it the name "normal". We see in the same dialog, that the box "The component is used in this variant" is checked. We must uncheck it because we don't want to have this component assembled in variant "normal". 

[[Image:e_var3.jpg|none]]

We create a second variant named "special", but here we leave this box checked because in this variant the component shall be assembled. The outlines of the component appear in hatched line immediately. this is a visual hint that the component is not assembled in all variants. 

[[Image:e_var4.jpg|none]]

Which variant we currently work in can be controlled by the "variants navigator" top right of the screen. It can be seen only if variants really do exist. 

[[Image:e_var5.jpg|none]]

== Control variants by the use of the Hierarchy browser ==

Only for TARGET 3001! - versions older than V13.3.0.62!

Highlight in the hierarchy browser (find it on the left edge of your screen by click on [[Image:HierBrwsArrow.jpg]] by [[Mousekeys|'''M1''']] "Variants": 

[[Image:e_Varianten1.jpg|none]]

Now click [[Mousekeys|'''M2''']] for to select "Properties" within the context menu. Within the following dialog you can name variants as desired: 

[[Image:e_Varianten2.jpg|none]]

In the hierarchy browser now click '''[[M1]]''' within "Components" upon the varying component and then [[Mousekeys|'''M2''']] to reach menu "Properties": 

[[Image:e_Varianten3.jpg|none]]

The variants in which the component is proposed to appear can now be defined: 

[[Image:e_Varianten4.jpg|none]]

Component C10 eg. shall not be assembled within the variant named "normal". The outline of the component appears in hatched line. 

[[Image:e_Varianten5.jpg|none]]

== Variants and different Bills of material (BoM) ==

Handle different "Values and Article numbers" of variant components in the component's "Properties" e.g. for generation of variant bills of material. 

Imagine IC3,7442, a BCD converter shall be mounted in all variants. But we must recognize two variants of purchase regarding this component. We keep the naming of the variants "normal" and "special".

In variant "normal" the component shall achieve the value 7442_x and shall be purchased at the distributor DigiKey with ordering number 1234567. In variant "special" the component shall achieve the value 7442_ y and shall be purchased at Farnell using ordering number 999111. Later we want to give out bills of material having the component's properties listed according to the variant selected for to give it to the purchasing department. First we define this component "assembled" in both variants, "normal" and "special". Double click on the handle cross and open the dialog "Change Symbols". Use the "Variants" button for setting the component assembled in all variants (tick the box "The component is used in this variant" an all variants). 

[[Image:e_Varianten8.jpg|none]]

The lower part of the dialog now allows the edition of components properties related to different variants: 

[[Image:e_Varianten9.jpg|none]]

We see that if no variant name is selected (=all) the appearance of the component in general is shown.

Now we select variant 1, "normal", from the Pull-Down Menu. We add the property "Article DigiKey" and the Digits 1234567 for the Article number to the blank fields. First click on a new row into the properties list. If you are unsure how to name a property correctly, please see in the pull down menu of the components properties in general and just copy. A further field is for the varying component value, which we enter as 7442_x. Value means "component value" in this case. After confirmation by OK and closing of the dialog, you can visualize the variant value, if you choose the variant "normal" in the schematic above right: 

[[Image:e_Varianten10.jpg|none]]

The same we do regarding this component for the variant 2, "special" but we want to assign the property "Article Farnell", the digits "999111" and the property "Value" "93LC56_y". We check the result: 

[[Image:e_Varianten11.jpg|none]]

We see that the component shows the value 7442_y in variant named "special", as desired. Now what about the bills of material (BoM) which you like to hand out to your purchaser? We must now generate a BoM for each variant, a BoM "normal" and a BoM "special". We find this function in: 

[[Image:e_Varianten12.jpg|none]]

After selection of "Output Bill of Material..." a browser opens which asks for a storage directory and a name for the BoM we are about to generate. So we open a test-directory and add the word "normal" to the name suggestion and press OK. 

[[Image:e_Varianten13.jpg|none]]

Now the dialog for edition of the BoM opens. First we choose variant "normal", in the lower area of the dialog to define, for which variant the BoM is meant. We are able to select from the list of properties those ones we intend to give out to our BoM. We reduce the selection to the properties ARTICLE DIGIKEY and ARTICLE FARNELL, which we'd like to have listed for the variant "normal". Component Value, variant too, is ticked already in the upper area of the dialog. 

[[Image:e_Varianten14.jpg|none]]

A click on OK shows the BoM of the variant "normal" with all its specialties. 

[[Image:e_Varianten15.jpg|none]]

The same we do to get the BoM for variant "special": 

[[Image:e_Varianten16.jpg|none]]

Result: 

[[Image:e_Varianten17.jpg|none]]

The BoMs can be printed and/or edited by any texteditor or spreadsheet. 

== Variants and Gerber data ==

Independently from having set up different variants of assembly only one set of Gerber data is created. This is because you have only one skin (image) of tracks and pads and things in the layout. Variant assembling is done using one genuine layout. So you do not get various sets of gerber data but only one.

.
[[de:Varianten]]
[[fr:Variantes]]
[[category:About TARGET 3001!]]