One-line errors and warnings
Typical one-line errors are:
- CSV formatting errors
- Files required by the logic engine are locked or open in another process
- Non-existent tags are specified in CSV conditions
- Not running the Computer Setup Wizard for the runtime project
Communication errors
When communication errors occur, the object that has lost communications gives an "unknown" status, which is graphically represented in the one-line animation.
Objects in the one-line should be defined to display the communication errors as a different color. The errors are calculated using the quality of a tag. If a tag or point becomes invalid, it is assumed that the communication is also offline. When this occurs, the graphical objects (buses, breaker, and sources) should change to the pre-set "unknown status" color; the array position 255 in the graphic.
Error logging
The most common CSV file errors are logged to the Run project in a file named AdvOneLineStatusLog.txt. The file can contain several messages. By default, only exceptions are logged.
The following table lists these errors and their descriptions:
| Error message | Description |
|---|---|
|
Main Execution Loop Unexpected Failure |
The main logic loop has thrown an exception that has not been handled by other error messages. |
|
AdvOneLineDebugBus.Csv is locked |
Another process or user has this required CSV file locked. Confirm that you do not have the file open. |
|
Power Operation Running Project Path: "PATH" Does not Exist. Please Shutdown your Project and Try Running your Computer Setup Wizard |
The Citect.ini "Run" parameter has an invalid project path that does not exist. Run the Computer Setup Wizard, and this path should be corrected. |
|
Power Operation Running Project Path Not Specified. Please Shutdown your Project and Try Running your Computer Setup Wizard |
This problem is almost exclusively caused by not running the Computer Setup Wizard. |
|
PLSCADA is not in runtime |
You must have your project running before you execute the AdvOneLine.exe file. |
|
Failed to Establish Connection with CTAPI. PLSEngine.establishPLSConnection (FAILED CONNECTION) |
This error message indicates the PLS API connection has unexpectedly been disconnected. |
|
Required CSV file is locked |
The CSV file specified (AdvOneLine.csv) is locked by another process or user. Confirm that you do not have the file open. |
|
Invalid prefix located in CSVParser.FormatCSVData |
The CSV parser has detected an invalid component prefix. This error message should not occur. |
|
ERROR: Duplicate Component Name Encountered |
Check the CSV file to confirm that you do not have two sources, meters, or breakers with the same component number. |
|
ERROR: Invalid Node1 Number Encountered |
In the Bus1 column, you have a node that is not a number between 1 and 1000. |
|
ERROR: Invalid Node2 Number Encountered |
In the Bus2 column, you have a node that is not a number between 1 and 1000. |
|
ERROR: Node Not Specified |
You have a component without a Bus1 or Bus2 specified. |
|
ERROR: Invalid Condition String Encountered (MESSAGE) |
You have a syntax error in your condition column. Read the message. It will give details about the syntax error, the line on which it occurred, and (if applicable) the character at which it occurred. |
|
One or more of the tags specified in your CSV file do not exist in your Power Operation Runtime project |
Examine your CSV file. Either add the tags listed above the error message, or remove the tags from the CSV |