FC_EcamToMultiCam - General Information
Type: |
Function |
Available as of: |
V1.0.3.0 |
Reading a file created using Motion Builder
NOTE:
The function FB_EcamToMultiCam only works correctly if the used data structures are saved with Pack_Mode = 1.
The function reads files generated by the Motion Builder Toolkit (<Name>.dat) and saves the data to a structure of type ST_MultiCam.
Input |
Data type |
Description |
---|---|---|
i_sFilename |
STRING[20] |
Name of the file <Name>.dat created by Motion Builder Motion Toolkit without the file extension "dat". |
Output |
Data type |
Description |
---|---|---|
q_etDiag |
General library-independent statement on the diagnostic. A value not equal to ET_Diag.Ok corresponds to an diagnostic message. |
|
q_etDiagExt |
POU-specific output on the diagnostic. q_etDiag = ET_Diag.Ok -> Status message q_etDiag <> ET_Diag.Ok -> Diagnostic message |
|
q_sMsg |
STRING[80] |
Event-triggered message which gives more detailed information on the diagnostic state. |
Input/Output |
Data type |
Description |
---|---|---|
iq_stMultiCamData |
Structure into which the converted data are saved. |
q_etDiag |
q_etDiagExt |
Enumeration value |
Description |
---|---|---|---|
OK |
0 |
Ok |
|
FileHandlingInvalid |
104 |
The file does not exist. |
|
FileHandlingInvalid |
106 |
Error detected when reading from file. |
|
FileHandlingInvalid |
105 |
Too many files are opened. |
|
UnexpectedProgramBehavior |
193 |
The checksum is invalid. |
|
UnexpectedProgramBehavior |
94 |
The number of profile points is invalid. |
|
UnexpectedProgramBehavior |
116 |
The profile is already in use. |
|
UnexpectedProgramBehavior |
257 |
The profile file is invalid. |
|
UnexpectedProgramBehavior |
258 |
The profile header is invalid. |
|
UnexpectedProgramBehavior |
127 |
The memory for tables from system profiles is full. |
|
UnexpectedProgramBehavior |
256 |
The profile was not found. |
|
UnexpectedProgramBehavior |
123 |
The system profile table is full. |
|
UnexpectedProgramBehavior |
1 |
An unintended detected error occurred during execution. |
Enumeration name: |
CheckSumInvalid |
Enumeration value: |
193 |
Description: |
The checksum is invalid. |
Issue |
Cause |
Solution |
---|---|---|
- |
A checksum error has been detected when loading the profile file for a user cam. |
Verify profile file, then generate and transmit it again. Verify data carrier for defects. q_sMsg gives more detailed information on the triggering CamPoint |
Enumeration name: |
FileNotExisting |
Enumeration value: |
104 |
Description: |
The file does not exist. |
Issue |
Cause |
Solution |
---|---|---|
- |
The file does not exist. |
Copy the file to the flash disk of the controller. |
- |
At the input i_sFilename, a file name has been applied that does not exist. |
Verify the file name at i_sFilename. |
Enumeration name: |
FileReadingInvalid |
Enumeration value: |
106 |
Description: |
Error detected when reading from file. |
Issue |
Cause |
Solution |
---|---|---|
- |
The file is damaged. |
Create the file again. |
Enumeration name: |
NumberProfilePointsInvalid |
Enumeration value: |
94 |
Description: |
The number of profile points is invalid. |
Issue |
Cause |
Solution |
---|---|---|
- |
The file data contain an invalid number of motion points. |
Create the file again. |
Enumeration name: |
Ok |
Enumeration value: |
0 |
Description: |
Ok |
The data of the Motion Builder file has been read successfully and written into the MultiCam structure.
Enumeration name: |
ProfileAlreadyInUse |
Enumeration value: |
116 |
Description: |
The profile is already in use. |
Issue |
Cause |
Solution |
---|---|---|
- |
The motion profile is already in use. |
Verify the motion data. |
Enumeration name: |
ProfileFileInvalid |
Enumeration value: |
257 |
Description: |
The profile file is invalid. |
Issue |
Cause |
Solution |
---|---|---|
- |
No file containing profile data has been transferred. |
Verify file |
- |
The transferred file is defective |
Create the file again |
Enumeration name: |
ProfileHeaderInvalid |
Enumeration value: |
258 |
Description: |
The profile header is invalid. |
Issue |
Cause |
Solution |
---|---|---|
- |
The file contains no valid profile data |
Verify file Create the file again |
Enumeration name: |
ProfileMemoryFull |
Enumeration value: |
127 |
Description: |
The memory for tables from system profiles is full. |
Issue |
Cause |
Solution |
---|---|---|
- |
The system profile memory is full. |
Delete any profiles that are no longer needed using the SystemInterface.FC_ProfileDelete function |
Enumeration name: |
ProfileNotFound |
Enumeration value: |
256 |
Description: |
The profile was not found. |
Issue |
Cause |
Solution |
---|---|---|
- |
No matching profile has been found. |
Verify the profile data. |
Enumeration name: |
ProfileTableFull |
Enumeration value: |
123 |
Description: |
The system profile table is full. |
Issue |
Cause |
Solution |
---|---|---|
- |
The maximum number of system profiles has been exceeded. |
Delete any profiles that are no longer needed using the SystemInterface.FC_ProfileDelete function |
Enumeration name: |
TooManyFilesOpen |
Enumeration value: |
105 |
Description: |
Too many files are opened. |
Issue |
Cause |
Solution |
---|---|---|
- |
Too many files are opened. |
Close files that are no longer needed using SystemInterface.FC_CloseFile. |
Enumeration name: |
UnexpectedFeedback |
Enumeration value: |
1 |
Description: |
An unintended detected error occurred during execution. |
Issue |
Cause |
Solution |
---|---|---|
- |
An error occurred in the internal execution. |
Please inform the support team about this error. |