Features and Improvements
- Auxiliary Files (SCRIPT and DATA Sections): Added concise variable names DynamicFormatting objects
- Case Information Displays: Cleaned up the field descriptions and column headers for DynamicFormatting objects.
- Contingency Analysis Tool: OPENCBS and CLOSECBS contingency actions that are not able to identify breakers will now open or close the device meant to be acted upon by breakers. This will allow the same contingency definitions to be used in full topology cases containing all breakers and hybrid or planning models that do not contain breakers for all devices.
- Data Checks: Added new ability to define DataCheck objects. These objects allow you to define by name an object that examines a particular ObjectType with a particular Criteria and then automatically builds a dialog showing you all objects that meet these data checks. In addition the Data Check dialog also provides summaries of counts of objects meeting (or not meeting) these data checks by aggregation objects of Area, Zone, Owner, and DataMaintainer.
- Power Flow Solution: When on island based AGC control and an island does not have any controllable generators, the message in the log will now indicate which island by showing the number of the island slack bus.
- Transient Stability: Added AC5C exciter model
- Transient Stability: Added AC7C exciter model
- Transient Stability: Added AC8C exciter model
- Contingency Analysis: When using OPENCBS and CLOSECBS contingency actions and contingencies contain multiple devices that end up using the same set of breakers, it was possible that the actions were not properly performed if the original actions were defined with different Model Criteria, Status, Arming Criteria, Arming Status, or Time Delay. Breaker actions were not being included for all of these different combinations. This has been fixed.
- Data Checks: Added new ability to define DataCheck objects. These objects allow you to define by name an object that examines a particular ObjectType with a particular Criteria and then automatically builds a dialog showing you all objects that meet these data checks. In addition the Data Check dialog also provides summaries of counts of objects meeting (or not meeting) these data checks by aggregation objects of Area, Zone, Owner, and DataMaintainer.
- File Formats: When loading an EPC file, if a DC system has exactly 2 converters, 2 dc buses, and 1 dc line, then Simulator creates a 2 terminal DC line object. There was a bug with this conversion for determining the metered end of the two-terminal DCTransmissionLIne if the first bus listed in the EPC file DC line record was the inverter bus instead of the rectifier. This has been fixed.
- File Formats: Reading the same RAW, EPC, or Areva CSV file by different Simulator instances could cause an error because the same file could not be read simultaneously. There doesn't need to be a restriction on separate instances of Simulator reading the same file, so this restriction has been removed.
- Power Flow Solution: Fixed power flow solution failure in situations when the DC transmission line control resulted in the tap ratio oscillating between two values where one tap resulted in the firing angle being just below the minimum firing angle and the second tap resulted in the firing angle being safely above the minimum firing angle. In some situations this could resulted in the voltage control loop of the power flow solution oscillating between these two states. Simulator will now automatically pick the DC tap value that results in the firing angle being above the minimum firing angle.
- Power Flow Solution: When changing topology to combine viable islands together, the loss percentage for the new island is determined from the loss percentage of the islands that were previously viable. The percentage was being chosen somewhat randomly and could result in picking a loss percentage that was not appropriate for the new island. This would result in a failed power flow solution. Now the loss percentage is chosen from the original island that had the most load.
- Power Flow Solution: Fixed an bug in which svsmo2 were oscillating and were not stopping the movement of the shunt in the power flow solution.
- Power Flow Solution: Fixed bug that would not check if SVSMO2 type SVCs need to operate if other non-SVC shunts had moved in the same voltage control loop.
- PV and QV Curve (PVQV) Tool: Fixed a bug that would prevent the individual curve files from being created during a QV run. These files are used to save memory when using the option to Save Results to File.