User Tools

Site Tools


en:infra-convert:dev:export:dfd

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revision Both sides next revision
en:infra-convert:dev:export:dfd [2020/01/14 11:17]
me
en:infra-convert:dev:export:dfd [2022/04/06 14:27]
me [File header]
Line 19: Line 19:
 > **Info** We recommend that you favor the JSONV1 format over the DFD format to connect to your software package. It includes more transferable information and supports all characteristics of #​@IC_HTML@#​.\\ \\ You can trigger the export in the start parameter file; see Configuration and Import > Startup Parameter File > [[en:​infra-convert:​dev:​parameter#​Export quality test plans and stamped drawings]]. > **Info** We recommend that you favor the JSONV1 format over the DFD format to connect to your software package. It includes more transferable information and supports all characteristics of #​@IC_HTML@#​.\\ \\ You can trigger the export in the start parameter file; see Configuration and Import > Startup Parameter File > [[en:​infra-convert:​dev:​parameter#​Export quality test plans and stamped drawings]].
  
-<WRAP group> +\\ 
-<WRAP column 61%> +
- +
-You can find a complete example of a DFD export file here: Appendix > [[en:​infra-convert:​dev:​export:​dfd_beispiel|Example quality test plan export file DFD]]. +
- +
-</​WRAP>​ +
-<WRAP column 33%> +
- +
-[[en:​infra-convert:​dev:​export:​dfd_beispiel|{{ :​en:​infra-convert:​dev:​dfd_exportdatei_beispiel.png?​nolink&​250 |}}]] +
- +
-</​WRAP>​ +
-</​WRAP>​+
  
 <WRAP noprint> <WRAP noprint>
Line 52: Line 41:
 <WRAP column 40%> <WRAP column 40%>
  
-Contains data that pertain to the entire file.+Contains ​general test plan data
 + 
 +The values are queried from the user interface during export. With the Pro version (and from program version 2.10.0), the test plan attributes can be defined in advance, saved and thus also exported on triggering via start parameter call.
  
-Apart from the total number of characteristics,​ the values are queried when saving in #​@IC_HTML@#​. ​The file header is repeated at the beginning of each sub-test ​plan for a merged file.+The file header is repeated at the beginning of each subtest ​plan for a merged file.
  
 > **See also** > **See also**
Line 123: Line 114:
 K2121/1 1 K2121/1 1
 K2243/1 930-1200-406-V2-2.jpg K2243/1 930-1200-406-V2-2.jpg
 +K2507/1 B
 +K2508/1 4
 K2800/1 Stamp ID K2800/1 Stamp ID
 K2801/1 A K2801/1 A
Line 152: Line 145:
 ^ K2121 |  I  |  1  | Type of the upper value (0 = no limit; 1 = limit value; 2 = natural limit) | ^ K2121 |  I  |  1  | Type of the upper value (0 = no limit; 1 = limit value; 2 = natural limit) |
 ^ K2243 |  A  |  80  | File name of the drawing on which the characteristic is located | ^ K2243 |  A  |  80  | File name of the drawing on which the characteristic is located |
 +^ K2507 |  A  |  2  | [[en:​infra-convert:​user:​interface:​feature|Field letter]] Drawing |
 +^ K2508 |  I  |  3  | [[e:​ninfra-convert:​user:​interface:​feature|Field number]] Zeichnung |
 ^ K2800 |  A  |  50  | Name for field K2802, static: "Stamp ID"\\ Q-DAS: "User field name 1" | ^ K2800 |  A  |  50  | Name for field K2802, static: "Stamp ID"\\ Q-DAS: "User field name 1" |
 ^ K2801 |  A  |  1  | Data type of field K2802, static: "​A"​\\ Q-DAS: "User field type 1" | ^ K2801 |  A  |  1  | Data type of field K2802, static: "​A"​\\ Q-DAS: "User field type 1" |
en/infra-convert/dev/export/dfd.txt · Last modified: 2024/01/23 11:34 by me