Issues in OneLiner V15

We discovered and fixed the following issues in the program recently:

• A mislabeled parameter of the Check relay Operation Using Stepped Event command: Execute the Check | Relay Checking Parameters command. When the dialog box appears, look for the entry "Fault end of tap lines if the ratio Ztapped-Line/Zstudy-line exceeds (percent)" in the topmost "Checking Parameters" list.  The text "(percent)" was put there by mistake.  In other words, if you want OneLiner to check any tapped line that has at least one-quarter of the impedance of the study line, then you need to enter the ratio of 0.25.  The default value of 99 turns off this feature. The screen-capture picture below shows the checking parameter in question with the labeled ready corrected highlighted in yellow:

• Inaccurate fault solution from Converter Interfaced Resources (CIR) if the CIR's negative-sequence slope is not zero and you are simulating an unbalanced fault. In the fault solution, the positive-sequence reactive current should be 90 degrees ahead of the positive-sequence voltage. Because of a programming mistake, the positive-sequence is in phase with the positive-sequence voltage. 

The above issues had been addressed in OneLiner V15.5 Build 20205 and higher (The program build number is displayed in the OneLiner Help | About dialog box). Users should contact ASPEN support <support@aspeninc.com> to request a software update with the latest bug fixes.

• Only the first 12 characters in the bus name are recognized in the DXT and CHF data files import and export logic: All bus names that are longer than 12 characters are being truncated when the network is exported to a DXT file and also when the DXT or CHF files are imported in OneLiner. If your network contains buses with names having more than 12 characters, you should export/import the data in the OLX/ADX file format to avoid losing data.

The above issue had been resolved in OneLiner V15.5 Build 20807 and higher (The program build number is displayed in the OneLiner Help | About dialog box). Users should contact ASPEN support <support@aspeninc.com> to request a software update with the latest bug fixes.