The error message dictionary provides a list of error messages and codes with an explanation of what can be triggering this message. The dictionary also provides the name of the unit generating this message, which can be helpful for identifying the declaration causing the issue.



Figure 1

Navigating the error dictionary


Message generator

Error code

Message

How to deal with it

Circuit.pas

7006

'tear_circuit','metis cannot start.',             'the metis program is not supported in fpc; tfilesearchreplace is unavailable.'

The user is trying to tear apart the circuit model either for creating sub-circuits or for using A-Diakoptics. This process required the Metis application within the OpenDSS Directory but is not there. Check if the file is in there and try again.

Circuit.pas

7007

'tear_circuit','the graph file is incorrect.',                   'metis cannot process the graph file because is incorrect' +                   '(the number of edges is incorrect).'

When tearing the circuit model using the incidence matrix produced by OpenDSS there was an issue. Metis returned an error message indicating that the graph is incorrect. Look for isolated areas and try again.

Circuit.pas

424

'tdsscircuit.addbus', 'busname for object "' + activecktelement.name + '" is null.',                  'error in definition of object.'

When declaring an element, it is important to provide an accurate description of the connection to the bus. This message signals that the bus definition is incorrect, either because it has special characters in the name such as dots (.) or spaces ( ) additional to the standard declaration. Review this features and try again.

CktElement.pas

751

'something is wrong.  got to base cktelement getcurrents for object:'+crlf+dssclassname+'.'+name,               'n/a',               'should not be able to get here. probable programming error.'

There was a problem calculating the active element’s currents, this can be triggered due to an issue in the last solution. There was no solution, or the voltage vector is equal to 0 at the connection points of the element. Check if the last solution converged and try again.

CktElement.pas

752

'something is wrong.  got to base cktelement getinjcurrents for object:'+crlf+dssclassname+'.'+name, '****',               'should not be able to get here. probable programming error.'

There was a problem retrieving the active element’s injection currents, this can be triggered due to an issue in the last solution. There was no solution, or the voltage vector is equal to 0 at the connection points of the element. Check if the last solution converged and try again. If the problem is not solved, there must be an internal issue that needs to be reviewed.

CktElement.pas

753

('improper call to injcurrents for element: ' + name + '.'), '****',        'called cktelement class base function instead of actual.'

The element declaration is not adequate or the procedure for retrieving the active element’s injection currents vector is not correct. This is an internal error and likely to be produced due to an error in the declaration/implementation of a new functionality.

DSSClass.pas

780

'reached base class of tdssclass for device "'+objname+'"',                   'n/a',                   'should be overridden.'

The element declared does not overrides the procedures/functions that should be part of the unit’s base. This error is triggered when creating new objects within OpenDSS and is telling the developer that the unit is incomplete, suggesting that one or several inherited procedures/functions need to be override.

DSSGlobals.pas

906

'makenewcircuit',                      'cannot create new circuit.',                      'max. circuits exceeded.'+crlf+                      '(max no. of circuits='+inttostr(maxcircuits)+')'

When cloning an existing circuit or compiling a new one in a different actor there is a limit in the number of threads (Actors) that can be created. In OpenDSS the limit is the number of threads available per processor, this to guarantee dedicated resources when doing things like Real-time. However, if users feel confident, they can remove this constraint from the code to generate their own versions. This is not critical, but a reminder of this constraint added.

DSSGlobals.pas

7000

'makenewcircuit',                      'cannot create new circuit.',                      'all the available cpus have being assigned'

When cloning an existing circuit or compiling a new one in a different actor there is a limit in the number of threads (Actors) that can be created. In OpenDSS the limit is the number of threads available per processor, this to guarantee dedicated resources when doing things like Real-time. However, if users feel confident, they can remove this constraint from the code to generate their own versions. This is not critical, but a reminder of this constraint added.

Feeder.pas

632

('getcurrents for feeder element: ' + name + '.'), e.message,        'inadequate storage allotted for circuit element?'

There was an error when allocating memory for one of the variables for a declared element. This error is an implementation error, meaning that one of the default values is not assigned or is not properly allocated when declaring the object.

Utilities.pas

704

'fireoffeditor.', e.message,                   'default editor correctly specified???'

The default text editor program does not exist or is not located at the given location. Check this out with the command set/get editor in OpenDSS.

Utilities.pas

709

'error opening '+filename+' for writing.', e.message, ' file protected or other file error.'

There was a problem opening/writing the file mentioned in the message. It is likely that the file is read only or is located at a protected location. If so, move the file to another public access location.

Utilities.pas

710

'error opening '+filename + ' for writing.', e.message, 'disk protected or other file error'

There was a problem opening/writing the file mentioned in the message. It is likely that the file is read only or is located at a protected location. If so, move the file to another public access location.

CapControl.pas

361

'capcontrol: "' + self.name + '"', 'capacitor element "'+ controlvars.capacitorname + '" not found.',                      ' element must be defined previously.'

The user is declaring a new capcontrol but the capacitor assigned for control does not exist in the active circuit. Check if there is a typo in the name of the capacitor provided and make sure the capacitor was declared before the capcontrol declaration.

CapControl.pas

362

'capcontrol.' + name + ':',                         'terminal no. "' +'" does not exist.',                         're-specify terminal no.'

The user is declaring a new capcontrol but the capacitor’s terminal assigned for control does not exist in the active circuit. Capacitors are 2 terminal elements, suggesting that the terminal value can only be 1 or 2. Check if there is a typo in the terminal number entered for the capacitor provided and make sure the capacitor was declared before the capcontrol declaration.

ESPVLControl.pas

371

'espvlcontrol: "' + name + '"',                                 'terminal no. "' +'" does not exist.',                                 're-specify terminal no.'

The user is declaring a new ESPVLControl but the controlled element’s terminal assigned for control does not exist in the active circuit. Check if there is a typo in the terminal number entered for the controlled element provided and make sure the element was declared before the ESPVLControl declaration.

ExpControl.pas

361

'expcontrol: "' + self.name + '"',              'controlled element "' + fpvsystemnamelist.strings[i-1] + '" not found.',              ' pvsystem object must be defined previously.'

The user is declaring a new ESPVLControl but the controlled element assigned for control does not exist in the active circuit. Check if there is a typo in the element’s name provided and make sure the element was declared before the ESPVLControl declaration.

GenController.pas

371

'gencontrol: "' + name + '"',                                 'terminal no. "' +'" does not exist.',                                 're-specify terminal no.'

The user is declaring a new GenControl but the controlled element’s terminal assigned for control does not exist in the active circuit. Check if there is a typo in the terminal number entered for the controlled element provided and make sure the element was declared before the GenControl declaration.

GenDispatcher.pas

371

'gendispatcher: "' + name + '"',                                 'terminal no. "' +'" does not exist.',                                 're-specify terminal no.'

The user is declaring a new GenDispatcher but the controlled element’s terminal assigned for control does not exist in the active circuit. Check if there is a typo in the terminal number entered for the controlled element provided and make sure the element was declared before the GenDispatcher declaration.

InvControl.pas

361

'invcontrol: "' + self.name + '"',                            'controlled element "' + fdernamelist.strings[i-1] + '" not found.',                            ' pvsystem or storage object must be defined previously.'

The user is declaring a new InvControl but the controlled element assigned for control purposes does not exist in the active circuit. Check if there is a typo in the element’s name provided and make sure the element was declared before the InvControl declaration. Also, make sure that the element is a PVSystem or Storage, provide the name using the class.name notation (e.g. Storage.myStorage).

Recloser.pas

392

'recloser: "' + name + '"',                                 'terminal no. "' +'" does not exist.',                                 're-specify terminal no.'

The user is declaring a new Recloser but the controlled element’s terminal assigned for control does not exist in the active circuit. Check if there is a typo in the terminal number entered for the controlled element provided and make sure the element was declared before the Recloser declaration.

Recloser.pas

393

'recloser: "' + self.name + '"', 'cktelement element "'+ elementname + '" not found.',                            ' element must be defined previously.'

The user is declaring a new Recloser, but the controlled element assigned for control purposes does not exist in the active circuit. Check if there is a typo in the element’s name provided and make sure the element was declared before the Recloser declaration. 

RegControl.pas

122

'regcontrol: "' + name + '"', 'winding no. "' +'" does not exist.',                                      'respecify monitored winding no.'

The user is declaring a new RegControl, but the controlled element’s winding assigned for control purposes does not exist in the active circuit. Check if there is a typo in the terminal number entered for the controlled element (transformer) provided and make sure the element was declared before the RegControl declaration.

RegControl.pas

123

'regcontrol: "' + self.name + '"', 'controlled regulator element "'+ elementname + '" is not a transformer.',                                  ' element must be defined previously.'

The user is declaring a new RegControl, but the controlled element assigned for control purposes is not a transformer. Check if there is a typo in the element name entered for the controlled element (transformer) provided and make sure the element was declared before the RegControl declaration.

RegControl.pas

124

'regcontrol: "' + self.name + '"', 'transformer element "'+ elementname + '" not found.',                         ' element must be defined previously.'

The user is declaring a new RegControl, but the controlled element’s winding assigned for control purposes does not exist in the active circuit. Check if there is a typo in the terminal number entered for the controlled element (transformer) provided and make sure the element was declared before the RegControl declaration.

Relay.pas

384

'relay: "' + name + '"',                                 'terminal no. "' +'" does not exist.',                                 're-specify terminal no.'

The user is declaring a new Relay, but the controlled element’s terminal assigned for control does not exist in the active circuit. Check if there is a typo in the terminal number entered for the controlled element provided and make sure the element was declared before the Relay declaration.

Relay.pas

387

'relay: "' + self.name + '"', 'cktelement element "'+ elementname + '" not found.',                            ' element must be defined previously.'

The user is declaring a new Relay, but the controlled element assigned for control purposes does not exist in the active circuit. Check if there is a typo in the element’s name provided and make sure the element was declared before the Relay declaration. 

Relay.pas

388

'relay: "' + name + '"',        'has type td21 with time step greater than one cycle.',        'reduce time step, or change type to distance.'

The user is declaring a new Relay, but the time steps are incorrectly set. Check the values and verify that the distances and time steps are consistent. See https://opendss.epri.com/DistanceRelay.html. 

StorageController.pas

371

'storagecontroller: "' + name + '"',                                 'terminal no. "' +'" does not exist.',                                 're-specify terminal no.'

The user is declaring a new StorageController, but the controlled element’s terminal assigned for control does not exist in the active circuit. Check if there is a typo in the terminal number entered for the controlled element provided and make sure the element was declared before the StorageController declaration.

SwtControl.pas

387

'swtcontrol: "' + self.name + '"', 'cktelement element "'+ elementname + '" not found.',             ' element must be defined previously.'

The user is declaring a new SwtControl, but the controlled element assigned for control purposes does not exist in the active circuit. Check if there is a typo in the element’s name provided and make sure the element was declared before the SwtControl declaration. 

UPFCControl.pas

371

'upfccontrol: "' + name + '"',                     'terminal no. "' +'" does not exist.',                     're-specify terminal no.'

The user is declaring a new UPFCControl, but the controlled element’s terminal assigned for control does not exist in the active circuit. Check if there is a typo in the terminal number entered for the controlled element provided and make sure the element was declared before the UPFCControl declaration.

VVControl.pas

 [elementterminal]

'vvccontrol: "' + name + '"',        'terminal no. "' + format('%-d'

The user is declaring a new VVControl, but the controlled element’s terminal assigned for control does not exist in the active circuit. Check if there is a typo in the terminal number entered for the controlled element provided and make sure the element was declared before the VVControl declaration.

VVControl.pas

361

'vvcontrol: "' + self.name + '"',      'controlled element "' + fgeneratornamelist.strings[0] + '" not found.',      ' element must be defined previously.'

The user is declaring a new VVCControl, but the controlled element assigned for control purposes does not exist in the active circuit. Check if there is a typo in the element’s name provided and make sure the element was declared before the VVCControl declaration. 

PVsystem.pas

568

'pvsystem object: "' + name + '" in getinjcurrents function.',                        e.message,                       'current buffer not big enough.'

When declaring a PVSystem, the number of phases was incorrectly entered, leading to an inaccurate memory allocation. This issue is unlikely, but if it happens, review the number of elements entered for the latest array-like property and try again. 

Storage.pas

568

'storage object: "' + name + '" in getinjcurrents function.',                    e.message,                   'current buffer not big enough.'

When declaring a Storage device, the number of phases was incorrectly entered, leading to an inaccurate memory allocation. This issue is unlikely, but if it happens, review the number of elements entered for the latest array-like property and try again. 

StorageController.pas

371

'storagecontroller: "' + name + '"',                                 'terminal no. "' +'" does not exist.',                                 're-specify terminal no.'

The user is declaring a new StorageController, but the controlled element’s terminal assigned for control does not exist in the active circuit. Check if there is a typo in the terminal number entered for the controlled element provided and make sure the element was declared before the StorageController declaration.

ExecCommands.pas

303

('processcommand'+crlf+'exception raised while processing dss command:'+ crlf + parser[activeactor].cmdstring),                      e.message,                      'error in command string or circuit data.' 

The latest command entered does not follow the OpenDSS conventions or makes no sense. Check for typos and make sure you are respecting the conventions. See https://opendss.epri.com/CommandSyntax.html .

ExecHelper.pas

244

'doredirect'+crlf+'error processing input stream in compile/redirect.',                            e.message,                            'error in file: "' + redirfile + '" or filename itself.'

When redirecting the compilation engine to another file, make sure it exists. This error means that the file cannot be found in the path specified. Also make sure that the program (OpenDSS) has access to that location in the hard drive.

ExecHelper.pas

255

'dopropertydump - opening '+ getoutputdirectory +' dss_propertydump.txt for writing in '+getcurrentdir, e.message, 'disk protected or other file error'

When writing files into the hard, make sure the destination exists. This error means that the file cannot be found/written in the path specified. Also make sure that the program (OpenDSS) has access to that location in the hard drive.

ExecHelper.pas

257

'dopropertydump - problem writing file.', e.message, 'file may be read only, in use, or disk full?'

When writing files into the hard, make sure the destination exists. This error means that the file cannot be found/written in the path specified. Also make sure that the program (OpenDSS) has access to that location in the hard drive.

HelpForm.pas

140

'problem writing file: ' + fname + '.', e.message, 'disk protected or other file error'

When writing files into the hard, make sure the destination exists. This error means that the file cannot be found/written in the path specified. Also make sure that the program (OpenDSS) has access to that location in the hard drive.

HelpForm.pas

141

'problem opening ' + fname + ' for writing.', e.message, 'disk protected or other file error'

When writing files into the hard, make sure the destination exists. This error means that the file cannot be found/written in the path specified. Also make sure that the program (OpenDSS) has access to that location in the hard drive.

Panel.pas

23704

'links to help files.', e.message,                   'browser not found of help files moved or not installed.'

Deprecated, you should never get there.

ConductorData.pas

400

'something is wrong.  got to base conductor getnumproperties for object:'+crlf+dssclassname+'.'+name,             'n/a',             'should not be able to get here. probable programming error.'

This is a programming error given code editing. Check the latest changes applied and if the modification was not made locally, reach out to the developer. 

EnergyMeter.pas

525

'energymeter: "' + self.name + '"', 'circuit element "'+ elementname + '" is not a power delivery (pd) element.',                        ' element must be a pd element.'

The user is declaring a new energy meter, but the element assigned for installing the instrument is not a power delivery element (Line, transformer, etc). Check if there is a typo in the element’s name provided and make sure the element was declared before the energy meter declaration. 

EnergyMeter.pas

524

'energymeter: "' + name + '"',                             'terminal no. "' + inttostr(meteredterminal)+'" does not exist.',                             'respecify terminal no.'

The user is declaring a new energy meter, but the controlled element’s terminal assigned for metering does not exist. Check if there is a typo in the terminal number entered for the observed element provided and make sure the element was declared before the energy meter declaration.

EnergyMeter.pas

525

'energymeter: "' + self.name + '"', 'circuit element "'+ elementname + '" not found.',                        ' element must be defined previously.'

The user is declaring a new energy meter, but the element assigned for installing the instrument does not exist in the active circuit. Check if there is a typo in the element’s name provided and make sure the element was declared before the energy meter declaration. 

fMonitor.pas

665

'fmonitor: "' + name + '"',                                 'terminal no. "' +'" does not exist.',                                 'respecify terminal no.'

The user is declaring a new fmonitor, but the controlled element’s terminal assigned for metering does not exist. Check if there is a typo in the terminal number entered for the observed element provided and make sure the element was declared before the fmonitor declaration.

fMonitor.pas

666

'monitor: "' + self.name + '"', 'circuit element "'+ elementname + '" not found.',                            ' element must be defined previously.'

The user is declaring a new monitor, but the element assigned for installing the instrument does not exist in the active circuit. Check if there is a typo in the element’s name provided and make sure the element was declared before the monitor declaration. 

Monitor.pas

665

'monitor: "' + name + '"',                                 'terminal no. "' +'" does not exist.',                                 'respecify terminal no.'

The user is declaring a new monitor, but the observed element’s terminal assigned for metering does not exist. Check if there is a typo in the terminal number entered for the observed element provided and make sure the element was declared before the monitor declaration.

Monitor.pas

670

'cannot open monitor file.',                    e.message,                    'monitor: "' + name + '"'

It is highly likely that the circuit model files are in a folder with read-only access. Move the circuit mode to a different public location where the program (OpenDSS) has read/write privileges. 

Monitor.pas

671

'cannot close monitor stream.',                    e.message,                    'monitor: "' + name + '"'

It is highly likely that the circuit model files are in a folder with read-only access. Move the circuit mode to a different public location where the program (OpenDSS) has read/write privileges. 

Sensor.pas

665

'sensor: "' + name + '"',                                 'terminal no. "' +'" does not exist.',                                 'respecify terminal no.'

The user is declaring a Sensor, but the observed element’s terminal assigned for metering does not exist. Check if there is a typo in the terminal number entered for the observed element provided and make sure the element was declared before the Sensor declaration.

Sensor.pas

666

'sensor: "' + self.name + '"', 'circuit element "'+ elementname + '" not found.',                            ' element must be defined previously.'

The user is declaring a new Sensor, but the controlled element assigned for control purposes does not exist in the active circuit. Check if there is a typo in the element’s name provided and make sure the element was declared before the Sensor declaration. 

Equivalent.pas

803

'tequivalentobj.calcyprim', 'matrix inversion error for equivalent "' + name + '"',                   'invalid impedance specified. replaced with small resistance.'

When calculating the Y primitive of an element it turned out to be not invertible. The issue can be the result of a bad selection of impedance values or a typo when entering them. Review the values entered and try again.

Equivalent.pas

805

('getcurrents for element: ' + name + '.'), e.message,        'inadequate storage allotted for circuit element.'

This is a programming error given code editing. Check the latest changes applied and if the modification was not made locally, reach out to the developer. 

generator.pas

568

'generator object: "' + name + '" in getinjcurrents function.',                    e.message,                   'current buffer not big enough.'

When declaring a new generator, the number of phases is not declared correctly, producing an error in the vector-like properties memory allocation. Getting here is very unlikely, review the values provided and if does not work, reach out to the developer. 

Generic5OrderMach.pas

568

'indmach012 object: "' + name + '" in getinjcurrents function.',                    e.message,                   'current buffer not big enough.'

When declaring a new IndMach012, the number of phases is not declared correctly, producing an error in the vector-like properties memory allocation. Getting here is very unlikely, review the values provided and if does not work, reach out to the developer. 

GICLine.pas

325

'tgiclineobj.calcyprim', 'matrix inversion error for gicline "' + name + '"',                   'invalid impedance specified. replaced with small resistance.'

When calculating the Y primitive of an element it turned out to be not invertible. The issue can be the result of a bad selection of impedance values or a typo when entering them. Review the values entered and try again.

GICLine.pas

327

('getcurrents for element: ' + name + '.'), e.message,        'inadequate storage allotted for circuit element.'

When declaring a new GICLine, the number of phases is not declared correctly, producing an error in the vector-like properties memory allocation. Getting here is very unlikely, review the values provided and if does not work, reach out to the developer. 

GICsource.pas

335

('getcurrents for gicsource element: ' + name + '.'), e.message,        'inadequate storage allotted for circuit element?'

When declaring a new GICLine, the number of phases is not declared correctly, producing an error in the vector-like properties memory allocation. Getting here is very unlikely, review the values provided and if does not work, reach out to the developer. 

Isource.pas

335

('getcurrents for isource element: ' + name + '.'), e.message,        'inadequate storage allotted for circuit element?'

When declaring a new ISource, the number of phases is not declared correctly, producing an error in the vector-like properties memory allocation. Getting here is very unlikely, review the values provided and if does not work, reach out to the developer. 

Load.pas

588

'load object: "' + name + '" in getinjcurrents function.',                    e.message,                   'current buffer may not big enough.'

When declaring a new Load, the number of phases is not declared correctly, producing an error in the vector-like properties memory allocation. Getting here is very unlikely, review the values provided and if does not work, reach out to the developer. 

PCElement.pas

640

'pcelement.injcurrents',('improper call to getinjcurrents for element: ' + name + '.'),        'called pcelement class virtual function instead of actual.'

The element declared does not overrides the procedures/functions that should be part of the unit’s base. This error is triggered when creating new objects within OpenDSS and is telling the developer that the unit is incomplete, suggesting that one or several inherited procedures/functions need to be override.

PCElement.pas

641

('getcurrents for element: ' + name + '.'), e.message,        'inadequate storage allotted for circuit element.'

The element declared does not overrides the procedures/functions that should be part of the unit’s base. This error is triggered when creating new objects within OpenDSS and is telling the developer that the unit is incomplete, suggesting that one or several inherited procedures/functions need to be override.

PVsystem.pas

327

('getcurrents for element: ' + name + '.'), e.message,            'inadequate storage allotted for circuit element.'

When declaring a new PVSystem, the number of phases is not declared correctly, producing an error in the vector-like properties memory allocation. Getting here is very unlikely, review the values provided and if does not work, reach out to the developer. 

PVsystem.pas

568

'pvsystem object: "' + name + '" in getinjcurrents function.', e.message, 'current buffer not big enough.'

When declaring a new PVSystem, the number of phases is not declared correctly, producing an error in the vector-like properties memory allocation. Getting here is very unlikely, review the values provided and if does not work, reach out to the developer. 

Storage.pas

327

('getcurrents for element: ' + name + '.'), e.message,          'inadequate storage allotted for circuit element.'

When declaring a new Storage, the number of phases is not declared correctly, producing an error in the vector-like properties memory allocation. Getting here is very unlikely, review the values provided and if does not work, reach out to the developer. 

Storage.pas

568

'storage object: "' + name + '" in getinjcurrents function.',                  e.message,                 'current buffer not big enough.'

When declaring a new Storage, the number of phases is not declared correctly, producing an error in the vector-like properties memory allocation. Getting here is very unlikely, review the values provided and if does not work, reach out to the developer. 

UPFC.pas

325

'tupfcobj.calcyprim', 'matrix inversion error for upfc "' + name + '"',                   'invalid impedance specified. replaced with small resistance.'

When calculating the Y primitive of an element it turned out to be not invertible. The issue can be the result of a bad selection of impedance values or a typo when entering them. Review the values entered and try again.

UPFC.pas

327

('getcurrents for element: ' + name + '.'), e.message,        'inadequate storage allotted for circuit element.'

When declaring a new UPFC, the number of phases is not declared correctly, producing an error in the vector-like properties memory allocation. Getting here is very unlikely, review the values provided and if does not work, reach out to the developer. 

vccs.pas

335

('getcurrents for vccs element: ' + name + '.'), e.message,        'inadequate storage allotted for circuit element?'

When declaring a new VCCS, the number of phases is not declared correctly, producing an error in the vector-like properties memory allocation. Getting here is very unlikely, review the values provided and if does not work, reach out to the developer. 

VSConverter.pas

327

('getcurrents for element: ' + name + '.'), e.message,        'inadequate storage allotted for circuit element.'

When declaring a new VSConverter, the number of phases is not declared correctly, producing an error in the vector-like properties memory allocation. Getting here is very unlikely, review the values provided and if does not work, reach out to the developer. 

VSource.pas

325

'tvsourceobj.calcyprim', 'matrix inversion error for vsource "' + name + '"',                   'invalid impedance specified. replaced with small resistance.'

When calculating the Y primitive of an element it turned out to be not invertible. The issue can be the result of a bad selection of impedance values or a typo when entering them. Review the values entered and try again.

VSource.pas

327

('getcurrents for element: ' + name + '.'), e.message,        'inadequate storage allotted for circuit element.'

When declaring a new VSource, the number of phases is not declared correctly, producing an error in the vector-like properties memory allocation. Getting here is very unlikely, review the values provided and if does not work, reach out to the developer. 

WindGen.pas

568

'windgen object: "' + name + '" in getinjcurrents function.',                    e.message,                   'current buffer not big enough.'

When declaring a new WindGen, the number of phases is not declared correctly, producing an error in the vector-like properties memory allocation. Getting here is very unlikely, review the values provided and if does not work, reach out to the developer. 

AutoTrans.pas

117

'tautotransobj.calcyprim', 'matrix inversion error for autotrans "' + name + '"',                    'invalid impedance specified. replaced with tiny conductance to ground.'

When calculating the Y primitive of an element it turned out to be not invertible. The issue can be the result of a bad selection of impedance values or a typo when entering them. Review the values entered and try again.

fuse.pas

404

'fuse: "' + name + '"',                                 'terminal no. "' +'" does not exist.',                                 're-specify terminal no.'

The user is declaring a fuse, but the observed element’s terminal assigned for metering does not exist. Check if there is a typo in the terminal number entered for the observed element provided and make sure the element was declared before the fuse declaration.

fuse.pas

405

'fuse: "' + self.name + '"', 'cktelement element "'+ elementname + '" not found.',                            ' element must be defined previously.'

The user is declaring a new fuse, but the controlled element assigned for control purposes does not exist in the active circuit. Check if there is a typo in the element’s name provided and make sure the element was declared before the fuse declaration. 

Line.pas

183

'tlineobj.calcyprim', 'matrix inversion error for line "' + name + '"',                         'invalid impedance specified. replaced with tiny conductance.'

When calculating the Y primitive of an element it turned out to be not invertible. The issue can be the result of a bad selection of impedance values or a typo when entering them. Review the values entered and try again.

PDElement.pas

660

('trying to get currents for element: ' + name + '.'), e.message,        'has the circuit been solved?'

There was a problem calculating the active element’s currents, this can be triggered due to an issue in the last solution. There was no solution, or the voltage vector is equal to 0 at the connection points of the element. Check if the last solution converged and try again.

Reactor.pas

234

'treactorobj.calcyprim', 'matrix inversion error for reactor "' + name + '"',                               'invalid impedance specified. replaced with tiny conductance.'

When calculating the Y primitive of an element it turned out to be not invertible. The issue can be the result of a bad selection of impedance values or a typo when entering them. Review the values entered and try again.

Reactor.pas

234

'treactorobj.calcyprim', 'matrix inversion error for reactor "' + name + '"',                               'invalid impedance specified. replaced with tiny conductance.'

When calculating the Y primitive of an element it turned out to be not invertible. The issue can be the result of a bad selection of impedance values or a typo when entering them. Review the values entered and try again.

Transformer.pas

117

'ttransformerobj.calcyprim', 'matrix inversion error for transformer "' + name + '"',                    'invalid impedance specified. replaced with tiny conductance to ground.'

When calculating the Y primitive of an element it turned out to be not invertible. The issue can be the result of a bad selection of impedance values or a typo when entering them. Review the values entered and try again.

DSSGraph.pas

45704

'showgraph.', e.message,                           'is dssview.exe correctly installed???'

The program DSSView.exe cannot be found in the OpenDSS installation folder. Without this program no plot commands can be executed.