Publicité
One must have at least Monitor rights to perform this task.
The curves will be too big to be retrieved with a single command. As a consequence, the
data will be split in chunk. The server is specifying the size of those chunks and is warning
the client of how many of those chunks will need to be transferred to get the complete
curve.
It has the following prototype:
int CommandClient_RequestCurveEx(int
The CurveDescriptor is made out of the NumberOfChunks and ChunkSize as defined in
the protocol.
The Trigger Value to be used is here provided as a string and is converted by the DLL to
the type specified by TriggerValue_Type.
It can take some time between the moment of the request and the time where the first
data gets available.
IMPORTANT NOTE:
-
Number of periods is "1" by default
-
Trigger function is reserved for future use : "0" by default
6.2.5.2 CommandClient_RequestCurve
This is a simplified version of the CommandClient_RequestCurveEx command where
triggering is disabled.
It has the following prototype:
int CommandClient_RequestCurve(int
6.2.5.3 CommandClient_ReleaseCurve
This function is telling the RVT to stop getting data for the given curve.
If the curve was requested by a single client, the curve is not made available anymore for
the client and the slot is freed.
If the curve was requested by multiple clients, the freeing is only made when the last
client releases the curve.
Note that the effect of this command may not be immediate.
72 – Windows communication DLL for PQ-Link protocol ç RVT communication
SourceID,
unsigned char
NumberOfPeriods,
unsigned char
TriggerEnable,
int
TriggerSource_ID,
int
TriggerSource_Offset,
unsigned char
TriggerComparator,
unsigned char
TriggerValue_Type,
char
*TriggerValue_ValueString,
int
*CurveDescriptor);
SourceID,
unsigned char
NumberOfPeriods,
int
*CurveDescriptor);
Publicité
