CODE

ERROR

-999999999

Invalid input. This usually means an element/node/time index is out of range or something similar that has a range line DOF (1-6) or Local Node number (1-3).

-999999998

Invalid Database. This is returned when the database is invalid - if it cannot find an instance of the file is usually a good reason for this error.

-999999997

Invalid Filename Characters. This is when you have characters in the path or filename that is not valid such as a semi-colon or colon except as a drive separator.

-999999996

Invalid Parameter Number. If a parameter number is passed onto PLGetValue that is out of range, this is returned.

-999999995

Time Index Out Of Range. If you pass in an invalid time index then you get this error. The time index should be between 1 and the maximum number of solution times.

-999999994

No Contact Surfaces. There are no contact surfaces defined for the specified guide.

-999999993

Invalid Set Name. Making a call to one of the set operations but specifying an invalid set name (e.g. entering "All   " instead of "All") will return this error.

-999999992

Statistics Not Available. Statistics are unavailable for the specified parameters.

-999999991

Database Name Empty. The filename supplied for a database is actually an empty string.

-999999990

No Data For Parameter. This error code is returned typically when the parameter is missing from the database. A good example of this is velocity and acceleration in the Motion database which typically is not output as default.

-999999989

Old Database File. This error code is returned when validating the database and indicates the database has been updated since the last set of results was viewed. To address this, highlighting the contents of the filename cell and pressing return will update. However, if the references to the database do not reference the results of the database call PLUpdateHeaderIfChanged then this may not refresh the database. In this case, excel must be closed to clear the database cache.

-999999988

Item Index is out of range. This error code is used specifically by PLGetValue since the item index may refer to an element, a guide or a node index. If you use the specific calls instead an error code indicating the correct index type will be returned.

-999999987

Node Index Out of Range. The specified node index is not between 1 and Number of nodes as indicated by PLGetNodeCount.

-999999986

Element Index Out of Range. The specified element index is not between 1 and number of elements as indicated by PLGetElementCount.

-999999985

DOF or LOC Out Of Range. This error code is used by PLGetValue to indicate the DOFNo parameter is not in the valid range based on the parameter. This could be Degrees of Freedom (1-6 or 1-7 for Motion parameters), a Local Node Number (1-3) or something else depending on the specifics of the parameter. Calling a specific named parameter routine will return a more accurate error code.

-999999984

DOF Out of Range. The Degrees of Freedom value is not valid - it is typically 1-6 or 1-7 for Kinematic functions/parameters.

-999999983

Local Node Out of Range. The Local Node Number is not valid - it is typically in the range 1-3.

-999999982

Invalid Guide Index. The guide index is not between 1 and the number of guides indicated by PLGetGuideCount.

-999999982

Invalid Guide Index. The guide index is not between 1 and the number of guides indicated by PLGetGuideCount.

-999999981

No Auxiliary Surface. There is no auxiliary surface defined for the guide (Flat/Articulated guides only).

-999999980

Unable To Read Value. This is associated with the inability to get a force or motion value from the database. It is unlikely to occur but if this error code is returned it may indicate a fault in the database file itself.

-999999979

PLGetNaiveStandardDeviation function failed. Use the PLGetStandardDeviation function instead. Likely cause is very small variation in the sample.