Error Codes

NI-Industrial Communications for IEC 61850 15.0 Help

Edition Date: December 2015

Part Number: 373800D-01

»View Product Info
Download Help (Windows Only)

The IEC 61850 VIs can return the following error codes. Refer to the KnowledgeBase for more information about correcting errors in LabVIEW.

Code Description
−36298 Invalid name. The name contains one or more of the following reserved characters: /, $, ^, (, or ).
−36297 A duplicate IED name exists.
−36296 Invalid server refnum. Create an IED and search for valid servers in the IED.
−36295 The server is already started.
−36294 The server is not started. Call the Start Server VI and try again.
−36293 Unable to create the bundle. If the problem persists, contact NI technical support.
−36292 Unable to create the server point. If the problem persists, contact NI technical support.
−36291 Unable to create the bundle point. If the problem persists, contact NI technical support.
−36290 Unable to open the SCL file. Ensure the path to the SCL file is correct.
−36289 Failed to parse the SCL file. If the problem persists, contact NI technical support.
−36288 Failed to create the IED. Increase the logic device number by using the Create IED VI and try again.
−36287 Failed to add the report control block. If the problem persists, contact NI technical support.
−36286 Invalid DataSet definition. Refer to the SCL parsing information output for details.
−36285 Invalid DataSet member definition. Refer to the SCL parsing information output for details.
−36284 Unsupported data type(s) in DOI/DAI. Refer to the SCL parsing information output for details.
−36283 Unknown enum type. Refer to the SCL parsing information output for details.
−36282 Unknown enum value. Refer to the SCL parsing information output for details.
−36281 Unable to translate the type. Refer to the SCL parsing information output for details.
−36280 Invalid value. Refer to the SCL parsing information output for details.
−36279 The information of IED, Server, AP, LD, LNode, or DO is missing in the SCL file.
−36278 Unable to create the IED. If the problem persists, contact NI technical support.
−36277 Cannot create the bundle because the specified server points do not belong to the same server.
−36276 Invalid address type of point. Ensure the value of the type input is valid.
−36275 Invalid server point refnum. Search for valid server points on an existing server.
−36274 Invalid bundle refnum. Create a bundle and try again.
−36273 Invalid bundle point refnum. Create a bundle, add server points to the bundle, and try again.
−36272 Invalid data types for reading or writing. Ensure you use the correct polymorphic VI instance to read or write a point.
−36271 File path is too long. Refer to the NI-Industrial Communications for IEC 61850 Help for the maximum length of the Root Path property.
−36270 Cannot change this property when the server is started. Set the property before you start the server.
−36269 Cannot send reports when the server is not started. Start the server and try again.
−36268 Invalid OSI-TSEL. Refer to the NI-Industrial Communications for IEC 61850 Help for the format of OSI-TSEL.
−36267 Invalid OSI-SSEL. Refer to the NI-Industrial Communications for IEC 61850 Help for the format of OSI-SSEL.
−36266 Invalid OSI-PSEL. Refer to the NI-Industrial Communications for IEC 61850 Help for the format of OSI-PSEL.
−36265 Invalid IP address.
−36264 Invalid OSI-AP-Title. Refer to the NI-Industrial Communications for IEC 61850 Help for the format of OSI-AP-Title.
−36263 The identity length is too long. Refer to the NI-Industrial Communications for IEC 61850 Help for the maximum length of the Identity property.
−36262 Invalid IED refnum. Create a valid IED and try again.
−36261 Invalid OSI-AP-Invoke. Refer to the NI-Industrial Communications for IEC 61850 Help for the format of OSI-AP-Invoke.
−36260 Invalid OSI-AE-Qualifier. Refer to the NI-Industrial Communications for IEC 61850 Help for the format of OSI-AE-Qualifier.
−36259 Invalid OSI-AE-Invoke. Refer to the NI-Industrial Communications for IEC 61850 Help for the format of OSI-AE-Invoke.
−36258 Invalid buffer size. Refer to the NI-Industrial Communications for IEC 61850 Help for the range of the Buffer Size property.
−36257 Invalid Max SDU size. Refer to the NI-Industrial Communications for IEC 61850 Help for the range of the Max SDU Size property.
−36256 Invalid number of buffers. Refer to the NI-Industrial Communications for IEC 61850 Help for the range of the Number of Buffers property.
−36255 Invalid number of connections. Refer to the NI-Industrial Communications for IEC 61850 Help for the range of the Number of Connections property.
−36254 Invalid number of messages on input queue. Refer to the NI-Industrial Communications for IEC 61850 Help for the range of the Number of Messages on Input Queue property.
−36253 Invalid number of messages on output queue. Refer to the NI-Industrial Communications for IEC 61850 Help for the range of the Number of Messages on Output Queue property.
−36252 Invalid number of messages on queue. Refer to the NI-Industrial Communications for IEC 61850 Help for the range of the Number of Messages on Queue property.
−36251 A duplicate bundle name exists.
−36250 Invalid authentication type. Ensure the value of Authentication Type is one of None, Weak, Strong, Password, and Certificate.
−36249 Authentication user name is too long. Refer to the NI-Industrial Communications for IEC 61850 Help for the maximum length of the Authentication User property.
−36248 The size of the data array is not enough for reading data. Increase the size of the array and try again.
−36247 Cannot write data to the point because the data size exceeds the size of the point. Reduce the size of the data and try again.
−36246 The enum value that you want to write to the point is invalid. Ensure the enum value matches the definition of the enum.
−36245 Cannot allocate memory on your target. Refer to the SCL file and adjust the memory allocation parameters.
−36244 Invalid OSI mask. Refer to the NI-Industrial Communications for IEC 61850 Help for the range of the OSI Mask property.
−36243 Failed to start the server. Ensure your target has enough resources, such as memory and threads.
−36240 Cannot change the point to writable. Ensure the FC of this point is not read-only. Refer to the NI-Industrial Communications for IEC 61850 Help for the FC of points.
−36239 The target is out of memory.
−36238 Cannot resize the Max Objects per Request property. Ensure the target has enough memory.
−36237 Invalid max objects per request. Refer to the NI-Industrial Communications for IEC 61850 Help for the range of the Max Objects per Request property.
−36236 Failed to start the server. Ensure the IP address is correct, the port is not occupied by other applications, and the memory is enough.
−36235 Invalid point refnum.
−36234 The regular expression is incorrect.
−36233 The MMS address is invalid. Refer to the NI-Industrial Communications for IEC 61850 Help for the format of MMS addresses.
−36232 The length of password must be no longer than 80.
−36231 Invalid client refnum.
−36230 A duplicate client refnum name exists.
−36229 Unable to create the client refnum. If the problem persists, contact NI technical support.
−36228 Invalid TSEL of the client. Refer to the NI-Industrial Communications for IEC 61850 Help for the format of TSEL.
−36227 Invalid TSEL of the server. Refer to the NI-Industrial Communications for IEC 61850 Help for the format of TSEL.
−36226 Invalid SSEL of the client. Refer to the NI-Industrial Communications for IEC 61850 Help for the format of SSEL.
−36225 Invalid SSEL of the server. Refer to the NI-Industrial Communications for IEC 61850 Help for the format of SSEL.
−36224 Invalid PSEL of the client. Refer to the NI-Industrial Communications for IEC 61850 Help for the format of PSEL.
−36223 Invalid PSEL of the server. Refer to the NI-Industrial Communications for IEC 61850 Help for the format of PSEL.
−36222 Invalid AP-Invoke of the client. Refer to the NI-Industrial Communications for IEC 61850 Help for the format of AP-Invoke.
−36221 Invalid AP-Invoke of the server. Refer to the NI-Industrial Communications for IEC 61850 Help for the format of AP-Invoke.
−36220 Invalid AE-Qualifier of the client. Refer to the NI-Industrial Communications for IEC 61850 Help for the format of AE-Qualifier.
−36219 Invalid AE-Qualifier of the server. Refer to the NI-Industrial Communications for IEC 61850 Help for the format of AE-Qualifier.
−36218 Invalid AE-Invoke of the client. Refer to the NI-Industrial Communications for IEC 61850 Help for the format of AE-Invoke.
−36217 Invalid AE-Invoke of the server. Refer to the NI-Industrial Communications for IEC 61850 Help for the format of AE-Invoke.
−36216 Invalid AP-Title of the client. Refer to the NI-Industrial Communications for IEC 61850 Help for the format of AP-Title.
−36215 Invalid AP-Title of the server. Refer to the NI-Industrial Communications for IEC 61850 Help for the format of AP-Title.
−36214 The MMS address is not a valid address of a point. Refer to the NI-Industrial Communications for IEC 61850 Help for the format of MMS addresses.
−36213 A duplicate MMS address name exists.
−36212 The VI cannot find the point by using the MMS address.
−36211 NI-IndCom for IEC 61850 supports one-dimensional arrays only.
−36210 The type of LD, LN, FC, and DO must be structure.
−36209 The parent point of this point cannot be a leaf type point.
−36208 Some points are missing.
−36206 A duplicate data set address exists.
−36205 The VI cannot find the data set by using the MMS address.
−36204 The MMS address is not a valid address of a data set. Refer to the NI-Industrial Communications for IEC 61850 Help for the format of MMS addresses.
−36203 Cannot perform this action because an FCD or FCDA refers to non-existing points.
−36202 The data set does not include any FCDAs.
−36201 The address of FCD or FCDA does not comply with the IEC 61850 standard series.
−36200 The matching method must be wildcard (0) or regular expression (1).
−36199 The types of array elements are different.
−36198 Invalid remote server refnum.
−36197 Unable to create the remote server refnum. If the problem persists, contact National Instruments technical support.
−36196 A duplicate remote server name exists.
−36195 The remote server has been started already.
−36194 You must use the Send Command (Initiate) VI before sending requests to the server.
−36193 You cannot change remote server properties after the remoter server is started.
−36192 The remote server is destroyed while sending requests.
−36191 Failed to parse the response. If the problem persists, contact NI technical support.
−36190 The server refuses the initiation. Ensure the properties of Access Point are correct and the target server is started.
−36189 The maximum length of the SDO or DA names is 32 characters.
−36188 The dataset addresses input of the Send Command (DeletedNamedVariableList) VI cannot be an empty array.
−36187 Failed to open the file. Ensure the file path is correct.
−36186 The scope must be point and data set (0) or data set only (1).
−36185 Unable to create the report receiver refnum. If the problem persists, contact NI technical support.
−36184 Invalid report receiver refnum.
−36183 Cannot add report receivers to the same report ID.
−36182 The report point index is out of range. Check the point count of the specified FCDA entry.
−36181 A duplicate report receiver name exists.
−36180 The report receiver and the report parameter do not match each other.
−36179 The report does not contain the parameter. Ensure the parameter exists by checking the corresponding bit in OptFlds.
−36176 This entry does not exist in the report. Ensure the entry exists by using the Read Report (InclusionBitString) VI.
−36175 You must use the Dequeue Report VI to return the report before reading report data.
−36174 The report receiver is destroyed while dequeuing reports.
−36173 The report does not contain the LastApplError. Ensure the LastApplError exists by using the Read Report (Has LastApplError) VI.
−36172 The report does not contain any values. Ensure the values exist by using the Read Report (Has Values) VI.
−36170 Invalid IO handler refnum.
−36169 The packet buffer is insufficient to send requests. Enlarge the Rfc1006TsduSize and try again.
−36168 A duplicate IO handler refnum name exists.
−36167 All IO handlers must be in the same remote server when you send multiple requests.
−36166 You cannot read or write data when you wait for responses.
−36165 The request number exceeds the maximum request number of the remote server. Refer to the NI-Industrial Communications for IEC 61850 Help for the maximum request of the Maximum Data Requests property.
−36164 The IO handler cannot send any requests before receiving the response.
−36163 The IO handler type must be point or data set.
−36162 The type of the IO handler request must be read or write.
−36161 You cannot use the data set IO handler in multiple send requests.
−36160 Unsupported data type. Refer to the NI-Industrial Communications for IEC 61850 Help for the supported data types.
−36159 Unable to create the IO handler refnum. If the problem persists, contact NI technical support.
−36158 You cannot write to data sets.
−36157 The IO handler point index is out of range. Check the point count of the specified FCDA entry.
−36156 The type of some points in the response is not supported, such as bcd or objId.
−36155 The types of some points in the response do not match the local points.
−36152 The server or the client terminates the connection.
−36150 Exceeded the maximum number of pending requests. Refer to the Send Command VI topic of the NI-Industrial Communications for IEC 61850 Help for more information about this error.
−36147 The connection is closed. Check the network condition and ensure the target server is working correctly.
−36146 Cannot send requests when another thread is sending the conclude command.
−36145 Cannot send requests when another thread is sending the conclude command or the remote server is destroyed.
−36143 The timeout value must be 0 or greater.
−36142 Cannot send requests because the IO handlers in input array contain duplicate IO handlers.
−36140 The remote file path cannot be empty.
−36139 Cannot dequeue reports while another thread is dequeuing reports.
−36138 The report ID cannot be an empty string.
−36134 One or more leaf points have child points. Ensure that leaf points do not contain child points.
−36133 One or more points lack child points. Ensure that only leaf points do not contain child points.
−36132 The indentation level of one or more child points is incorrect.
−36131 The types of array elements in one or more child points are different.
−36130 Invalid adapter MAC address or invalid multicast MAC address. Refer to the NI-Industrial Communications for IEC 61850 Help for the format of the MAC address.
−36129 Invalid priority value. Refer to the NI-Industrial Communications for IEC 61850 Help for the valid priority values.
−36128 The point index is out of range. Check the point count in the specified FCDA entry.
−36127 Unable to create the GOOSE control block refnum. If the problem persists, contact National Instruments technical support.
−36126 Invalid GOOSE control block refnum.
−36125 Invalid GOOSE message retransmission strategy value. Refer to the NI-Industrial Communications for IEC 61850 Help for the valid retransmission strategy.
−36124 The Intervals array size in the Profile retransmission strategy exceeds the maximum array size. The maximum array size for Intervals is 30.
−36123 Cannot change the property for the GOOSE control block after you start the server. Set the property before you start the server.
−36122 Failed to start the GOOSE control block. Ensure that the adapter works and the size of the data set is less than or equal to 1,517 bytes.
−36121 The platform you are using has no GOOSE and SMV installed, or the platform does not support GOOSE and SMV. Refer to the NI-Industrial Communications for IEC 61850 Help for the platforms that support GOOSE and SMV.
−36120 The VI cannot find the adapter by using the adapter MAC address.
−36119 Failed to start the adapter. Possible reasons: the memory is not enough; the IEC 61850 is not properly installed.
−36118 Failed to start the GOOSE subscriber. Ensure that the adapter works, the GOOSE feature is installed, and no duplicate addressing exists. Refer to the NI-Industrial Communications for IEC 61850 Help for more information about the maximum number of GOOSE subscribers that you can create.
−36117 The GOOSE subscriber is already destroyed.
−36116 The GOOSE subscriber is already waiting for the GOOSE messages.
−36115 Failed to find any adapter. Possible reasons: no adapter exists on the target; the IEC 61850 is not properly installed.
−36114 The GOOSE point index is out of range. Check the point count in the specified FCDA entry.
−36113 The GOOSE entry index is out of range. Check the entry count in the GOOSE message.
−36112 Invalid GOOSE subscriber refnum.
−36111 Unable to create the GOOSE subscriber refnum. If the problem persists, contact NI technical support.
−36110 A duplicate GOOSE subscriber refnum name exists.
−36109 Failed to read the GOOSE messages or failed to send the command. Use the Wait for GOOSE VI to wait for the GOOSE messages before reading the GOOSE messages or before sending the GetGoReference and GetGOOSEElementNumber commands.
−36108 One or more domain names do not contain the IED name.
−36107 Failed to write to the file.
−36104 The remote server does not contain any data points. Use Send Command (Browse) VI before exporting the SCL file.
−36103 The path name of a GoCB within LLN0 is invalid.
−36102 Cannot send requests when the GOOSE subscriber is destroyed.
−36101 A duplicate state ID exists.
−36099 The GSE Management PDU is too large. Ensure that the size of the GSE Management PDU is smaller than or equal to 1,517 bytes.
−36097 Invalid application identifier. Refer to the NI-Industrial Communications for IEC 61850 Help for the valid application identifier.
−36096 The MemberOffsets in the GetGoReference command is out of range. Ensure that MemberOffsets is less than or equal to 512.
−36095 A duplicate SMV subscriber refnum name exists.
−36094 Invalid queue size. The queue size must be greater than or equal to the number of ASDUs.
−36093 Invalid SMV subscriber refnum.
−36092 Unable to create the SMV subscriber refnum. If the problem persists, contact NI technical support.
−36091 The number of ASDUs must be greater than or equal to 1.
−36090 Failed to start the SMV subscriber. Ensure that the adapter works, the SMV feature is installed, and no duplicate addressing exists. Refer to the NI-Industrial Communications for IEC 61850 Help for more information about the maximum number of SMV subscribers that you can create.
−36089 The SMV subscriber is already dequeuing the SMV messages or flushing the queue.
−36088 Failed to read the SMV messages. Use the Dequeue SMV VI to dequeue the SMV messages before reading the SMV messages.
−36087 Unsupported data type(s) in SMV. Refer to the NI-Industrial Communications for IEC 61850 Help for the supported data types.
−36086 The SMV point index is out of range. Check the point count in the dataset structure input of the Create SMV Subscriber VI.
−36085 Failed to create the SMV subscriber. Specify dataset structure and try again.
−36084 The SMV header information that you specify does not exist in the SMV message.
−36083 Unable to create the SMV control block refnum. If the problem persists, contact NI technical support.
−36082 Invalid SMV control block refnum.
−36081 Cannot change the property for the SMV control block after you start the server. Set the property before you start the server.
−36080 The SMV control block is already enqueuing the SMV message.
−36079 The value of the sample count type input must be either Increment or Reset.
−36078 The value of the sample synchronization type input must be either Not Synchronized, Local Synchronized, or Global Synchronized.
−36077 Failed to publish the SMV message. Ensure your target has enough memory and the network connection is correct.
−36076 Failed to start the SMV control block. Ensure your target has enough memory.
−36075 The SMV point index is out of range. Check the point count in the SCL file.
−36074 Failed to enqueue the SMV messages. Ensure all the data in this SMV control block is updated.
−36073 Invalid TCP port for the MMS connection.
−36016 The Section input of the Read Nodes VI must be IED or Communication.
−36015 Cannot read SCL nodes because the SCL file contains too many elements.
−36014 Failed to validate the imported SCL file. If the problem persists, contact NI technical support.
−36013 Invalid tag.
−36011 The computer is out of memory.
−36010 You must import an SCL file to the SCL engine before using other SCL VIs.
−36009 Failed to export the SCL file. Ensure the SCL file path is valid, the disk has enough free space, and you have the permission to write this file.
−36008 Failed to import the SCL file. Ensure the SCL file exists, the format of the SCL file is valid, and you have the permission to read this file.
−36007 A duplicate element name exists on the same hierarchy. Refer to the validation info output for details.
−36006 The name of the element cannot be empty. Ensure the name of element (IED, AP, LD, LN, DO, or DA) is not empty. Refer to the validation info output for details.
−36005 Invalid SCL engine. Ensure this engine exists.
−36004 A duplicate SCL engine name exists.
−36003 Invalid SCL engine name. Ensure the name does not contain reserved characters such as /, $, ^, (, or ).
−36002 Failed to destroy the SCL engine. If the problem persists, contact NI technical support.
−36001 Failed to create the SCL engine. If the problem persists, contact NI technical support.
−36000 You can use the SCL VIs on Windows only.
36000 A file with the same name already exists in this location. The SCL engine cannot overwrite the existing file.
36001 Duplicate instance names (DOI, SDI, DAI) under LN. This VI modifies the first instance only.
36272 Overflow occurs in the SMV subscriber. The rate of dequeuing SMV messages is lower than the rate of adding SMV messages to the queue.
36273 An MMS client disables the SMV control block. This VI does not send SMV messages.
36274 One or more data sets do not contain any FCDAs.
36275 The structure of the data objects in the remote server are not Common Data Class as defined in the IEC 61850 standard series. This VI generates customized data objects.
36276 One or more required points in the GOOSE control block or the report control block may have incorrect values.
36277 Unable to read the values for one or more required points in the GOOSE control block or the report control block. Possible reason: the server is disconnected or busy. This VI uses the default values for these required points.
36278 Unable to access the Identify service of the remote server. This VI uses the default values for the Identify information.
36279 An issue occurs when the VI sends the conclude command, but the NI-IndCom for IEC 61850 software is stopped.
36280 The data size exceeds the size of the point. Some data might be lost.
36281 The format of response does not comply with the IEC 61850 standard series. Part of the response is missing.
36282 Cannot get the whole structure of logic nodes. The structure of some logic nodes may be different from the server.
36283 The expected point size does not match the point size in the response. Some data might be lost.
36284 The connection is concluded or aborted.
36285 NI-IndCom for IEC 61850 ignores one or multiple points because the data types of these points are not supported.
36286 NI-IndCom for IEC 61850 ignores one or multiple data sets because these data sets are invalid.
36287 NI-IndCom for IEC 61850 ignores one or multiple points because these points are invalid.
36288 NI-IndCom for IEC 61850 supports only one-dimensional arrays and ignores multi-dimensional arrays.
36289 The type of LD, LN, FC, and DO must be structure. Otherwise, this VI ignores the LD, LN, FC, or DO.
36290 SCL parsing warning. Refer to the SCL parsing information output for details.
36292 The input time is before epoch time 1984-01-01 00:00:00. The software uses the epoch time instead of the input time.
36293 The input time is before epoch time 1970-01-01 00:00:00. The software uses the epoch time instead of the input time.
36294 The input data is larger than the maximum value of the point. The data is lost.
36295 The data contains invalid visible string characters.
36296 The data contains empty characters. The data is truncated at the first empty character.
36298 Authentication is not supported on this platform.
36299 Authentication types Weak, Strong, and Certificate are not supported. The software uses Password instead.

WAS THIS ARTICLE HELPFUL?

Not Helpful