The following items describe the conversion conventions used by the Smart Instrumentation Fisher interface when transferring data from Smart Instrumentation to Fisher and back.
-
For outlet line parameters, Smart Instrumentation uses specification custom fields.
-
When exporting line data to ASCII delimited files, Smart Instrumentation uses the same values for outlet line parameters as for input line parameters if the following Fisher fields contain a null value:
-
pipeoutletdiameter
-
outpipelinesize
-
outpipelinesched
-
-
For the otherconditionname Fisher field, Smart Instrumentation automatically assigns the constant value: Shut-Off.
-
When importing new line data, make sure the ansi_din Smart Instrumentation field data complies with the following convention:
-
If the pipelineuom Fisher field value is in (inches), set the ansi_din field to A.
-
If the pipelineuom field value is mm, set the ansi_din field to D.
-
-
The following Smart Instrumentation-to-Fisher fluid phase relations apply:
|
Smart Instrumentation (pd_fluid_phase field) |
Fisher (fluidstate field) |
|---|---|
|
L |
Liquid |
|
W |
Water |
|
G |
Gas |
|
S |
Vapor |
-
The source text file profile is defined in the odbc.ini registry folder.
-
When you install Smart Instrumentation, you can also install the predefined ASCII file profile for use with Fisher.
-
You must define your own Microsoft driver using the Windows ODBC Data Source Administrator.
-
When defining a profile for Fisher data, make sure you use a comma delimiter and the Column Names option.
If you change an instrument type that was exported from Smart Instrumentation in the Fisher interface before re-importing it to Smart Instrumentation, the new instrument type will be created in Smart Instrumentation. You can avoid this by modifying the appropriate Fisher import links.