![]() |
ALPHA-VISION® Windows: Request.ini |
The "Request.ini" file is a text file in ASCII-Format. It may be created
or modified by an appropriate text editor.
The Ini-File must be completely filled in for the actual case in use.
Incomplete or incorrect entries may lead to errors or deficiencies in the
results.
The local Ini-File of the computer differs depending on the run mode.
| Entry | Type | Description / Example | Default | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Application | string |
Defines whether the program opens a window when starting or is
displayed as an icon in the task bar only.
Possible entries:
Example
Application=Window |
Icon | ||||||||||||
| Port | string |
Possible entries:
Example
Port=ACI |
|||||||||||||
| DoFile | string |
Name (inclusive the extension ‘.do’) and, where required, the
path to the project file to be read.
In RAS-Mode that entry contains the name of the Host-Drive, path and name of the project file (*.do) to be read. Example
DoFile=\\D at OS\Request\Test.do |
|||||||||||||
| IRQ | integer |
The interrupt the interface is controlled by –
Possible entries:
Example
IRQ=3 |
|||||||||||||
| Data | string |
Configuration parameters for the serial interface (always 3
characters).
Note:
The definitions must match with the entries on the remote computers.
Example
Data=8N1 |
|||||||||||||
| BaudRate | integer |
Defines the baud rate for the serial interface.
Note:
The definitions must match with the entry on the remote computers.
Example
BaudRate=19200 |
|||||||||||||
| ReceiveBufferSize | integer |
Block size in kByte
Possible entries:
Example
ReceiveBufferSize=2 |
1 | ||||||||||||
| Ras | integer |
(RAS)
Setting the RAS-Mode when loading the Ini-File via the "OPEN-INI-FILE"
–Button.
Possible entries:
WARNING
An active Ini-File entry might overwrite the parameters set by the
command line.
Example
Ras=1 |
|||||||||||||
| PointToPoint | string |
(RAS)
Defines the interface for the data transfer between the PCs. Any serial
or parallel interface may be used.
Possible entries:
Example
PointToPoint=COM1_TO_OS |
|||||||||||||
| IniFilePath | string |
(RAS)
Definition of the remote Ini-File from which the entries in sections
[Events] and [MpData] should be read.
The entries contain the drive name on the Host, the path and the name of the Ini-File, including the extension ‘.ini’. Example
IniFilePath=\\D on OS\Request\Test.ini |
| Entry | Type | Description / Example | Default | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| DoIt | integer |
Requesting event data
Possible entries:
Note:
Definition 1 should only be used if a complete Event-Log is really needed;
since an Event-Log easily contains several thousand entries a complete
synchronization will increase the workload of the PCs on program start
accordingly.
Example
DoIt=1 |
|||||||||
| FileName | string |
Name (including path, excluding extension) of the file the
event data are written to.
Without defining a path, the file is written to the same folder the program ‘Request.exe’ is located in. WARNING
If the defined path is invalid the file is not written.
Example
FileName=C:\Ev_Data\Alarms |
|||||||||
| NoOfRecords | string |
Defines the number of records after that a new file is started.
The new file gets the same name and the extension number is
increased by 1.
(<File name>.001, <File name>.002 etc.)
Possible entries:
Example
NoOfRecords=500 |
|||||||||
| DataType | string |
Data format the file is written in, see also
transmitting data: Formats of Data
Possible entries:
Example
DataType=SDF |
|||||||||
| Delimiter | integer |
A maximal 3 digits long decimal value out of the ASCII-Table as
a delimiter in a event file.
Note:
Only valid if defined in Data Type ASCII.
Example of a typically setup:
Example
Delimiter=44 |
|||||||||
| SendEOL | string |
Definition for End of Record
Note:
Only valid if as data type ASCII or SDF is defined.
Possible entries:
Example
SendEOL=1 |
|||||||||
| Col | string |
<Keyword 1>, <Format 1>;.......;
<Keyword n>,<Format n>
Defines which fields should be transmitted with which parameters.
Note:
For Data Type ASCII or SDF 'C' is the only valid format.
Example
Col=Arch_Type, C2; Arch_ObjectNo, C5; Arch_PrvStatus, C5; |
| Entry | Type | Description / Example | Default | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| DoIt | integer |
Requesting data of Measuring Points
Possible entries:
Example
DoIt=1 |
|||||||||
| FileName | string |
Name (including path and extension) of the file the requested data
should be written to.
Without defining a path, the file is written to the same folder the program ‘Request.exe’ is located in. WARNING
If the defined path is invalid the file is not written.
Example
FileName=C:\Mp_Data\MPDAT.TXT |
|||||||||
| DataType | string |
Data format the file is written in, see also
transmitting data: Formats of Data
Possible entries:
Example
DataType=SDF |
|||||||||
| Delimiter | integer |
A maximal 3 digits long decimal value out of the ASCII-Table as
a delimiter in a event file.
Note:
Only valid if defined in Data Type ASCII.
Example of a typically setup:
Example
Delimiter=44 |
|||||||||
| SendEOL | string |
Definition for End of Record
Note:
Only valid if as data type ASCII or SDF is defined.
Possible entries:
Example
SendEOL=1 |
|||||||||
| StartHour - StartMin - IntervalHour - IntervalSec | integer |
Start and interval times for cyclic data transmission from the
Measuring Points.
Note:
All defined times refer to times on the Clients (PCs)!
Example
StartHour=12 StartMin=00 IntervalHour=04 IntervalSec=20 |
|||||||||
| Col | string |
<Keyword 1>, <Format 1>;.......;
<Keyword n>,<Format n>
Defines which fields should be transmitted with which parameters.
Example
Col=PointId, C9; Description, C30; Value, C9; |
|||||||||
| OBJECTS | integer |
Number of objects resp. data records to be transferred.
The value aids the user but is not of any relevance for the program Example
OBJECTS=30 |
|||||||||
| OBJ.nnnn | integer |
List of the PointIds for the data records to be transferred.
Note:
It is possible to transfer several thousands Measuring Points, but think
about the resources needed on the OS and the time consumed by the
transaction.
Example
OBJ.0000=011004,011006,011007,012006,013004,013006,013007,014004, OBJ.0001=014006,014007,021004,022005,031014,031015,031008,031009, OBJ.0002=041003,041004,041102, |