nikhilgupta10
commented
7 years ago nikhilgupta10 imported these comments from Sourceforge: "t-hardy":- status: assigned --> closed ,
"t-hardy":Completed work on power-factor correction control mode for inverter object.,
"t-hardy":- status: closed --> reopened ,
"t-hardy":Bug found relating to the ew_pf_reg_status\ being used without initialization. Found as a runtime exception on Visual C++ in inverter.cpp.
Don't know what is causing this or why it wasn't caught before. I'm having the model that generated the error sent over so I can see if I can replicate it and determine why it slipped through.,
"t-hardy":gcc (MinGW compiler) has a compile time flag (-Wuninitialized) that checks for uninitialized variables and, had it been used, would have caught this error.
Corrected problem; passes gcc uninitialized variable check.,
"t-hardy":- status: reopened --> closed ,
"dchassin":- Milestone: Unscheduled --> Knothole Interim ,
"andyfisher":This has already been integrated into Trunk,
OMF has requested a power-factor control mode similar to the load-following mode. This is not volt-var regulation but simply adding (or removing) VARs to the network based on the power-factor at a given node and the response limits of the inverter. This mode will operate in parallel to the traditional inverter control modes (load-following, constant PQ,...),